Use case · CONTROL CLOUD
For operators of many sites — water, energy, charging infrastructure, street furniture — where a control system of its own at every site does not pay off.
When conventional infrastructure becomes too expensive, software takes over: connect distributed assets, buildings and infrastructure over radio and open protocols to one central, cloud-native platform — control, visualisation and monitoring included.
Field example · Cool spots Vienna
60 distributed mist showers. Controlled centrally. Without a fixed power supply.
For Raintime, the control and web operation were built with logiccloud. LoRaWAN and MQTT connect the battery-powered sites to the central control and portal level.
From a single cool spot to scalable infrastructure — the same platform.
The principle
Raintime shows the principle: local assets, central intelligence.
The technology stays in the background. The benefit scales.
Customer benefit
What running CONTROL cloud-native concretely changes for distributed applications.
Battery operation and radio networking avoid costly power lines and groundworks.
All assets in view across sites, through one web portal.
Time-controlled functions act exactly when they are needed.
The status and function of every asset stay continuously visible.
The architecture carries over to further sites and applications.
Web-based access creates transparency regardless of location and device.
What works for mist showers works for any distributed equipment: HVAC, lighting, energy and load management or charging infrastructure.
Manage technical trades on one central platform, independent of manufacturer.
Analyse consumption, avoid load peaks, optimise self-consumption.
Run it in Europe or on-premises, with role-based access rights.
In the Raintime project, LoRaWAN connects the battery-powered sites and MQTT carries the data. CONTROL also speaks OPC UA, Modbus TCP/RTU and HTTP/REST — the full list is on the connectors page.
Not necessarily. With CONTROL Cloud the virtual PLC runs centrally; the sites deliver sensor data and receive switching commands over the network. Where a site has to keep working without a connection, the same app runs on an edge device on site.
If the logic runs centrally, a site without a connection cannot be controlled for that time. That is why everything that has to keep running on site belongs on an edge device at the site — we settle that when designing your application.
In licensed cloud operation, only users who have been assigned the role “View HMI”.