Cloud SCADA: how it works, when it makes sense and what water and energy rules ask for
Cloud SCADA moves supervision to the cloud: data collection, the historian, alarms and dashboards. Control stays where it belongs, in the PLCs and RTUs at each site. Operators get the whole operation in a browser, and adding a new site takes a gateway instead of a new server.
What the rules ask of water and energy operators
Water, waste water and energy are sectors of high criticality under NIS2. Operators manage the risk to their systems with incident handling, business continuity and access control, and a significant incident gets an early warning within 24 hours and a notification within 72. In November 2026 Spain had not yet transposed the directive, but it already applies across the EU, and operators designated as critical under Law 8/2011 keep security and protection plans for each critical infrastructure.
Drinking water adds operational rules. Royal Decree 3/2023 asks for automatic, continuous disinfection, operational monitoring that shows treatment problems quickly, on-line turbidity at large plants and a Water Safety Plan with its records; the largest supply zones must have their corrective measures in place by 2 January 2027. In the United States, community water systems serving more than 3,300 people assess the risk to their automated systems and their monitoring practices, certify it to EPA and review it every 5 years. IEC 62443 and ISA-18.2 are the usual references for securing the control network and managing alarms.
| Who asks | What | Data that answers it |
|---|---|---|
| Essential services in the EU (NIS2) | Risk measures, warning in 24 h, notice in 72 h | Alarm and event history, access by role, audit trail |
| Drinking water in Spain (RD 3/2023) | Continuous disinfection, operational monitoring, safety plan | Turbidity, chlorine and pH logged with daily figures |
| Critical operators in Spain (Law 8/2011) | Security and protection plans | Telemetry, alarms and access records per site |
| US water systems (SDWA 1433) | Risk and resilience assessment every 5 years | How automated systems are monitored, with evidence |
The platform keeps the history and the alarm log and controls who does what; the risk assessments, the plans and the notifications stay with the operator.
Cloud SCADA vs on-premise SCADA
| On-premise SCADA | Cloud SCADA | |
|---|---|---|
| Where it runs | Servers in the plant or control room | A cloud platform, or your own data center |
| Access | Control room workstations, VPN for remote work | Browser and phone, with user roles |
| Adding a site | New servers, licenses and network links | A gateway or wireless sensors |
| Upfront cost | Hardware and licenses per server | Subscription per device or site |
| If the internet link drops | Keeps running locally | Local control keeps running and the remote view catches up when the link returns |
| Best fit | Fast closed-loop control in one plant | Supervising many plants and remote sites |
How the data gets to the cloud
- Field: PLCs, RTUs, meters and sensors, as they are today.
- Edge gateway: Reads Modbus, OPC UA or the PLC's own protocol and sends the data out over MQTT or HTTPS. More in how to integrate IoT with PLCs.
- Wireless sensors: Sites with no PLC join with battery-powered sensors, as in LoRaWAN SCADA.
- Platform: Historian, alarms, dashboards, reports and users, reachable from any browser.
Security
- Outbound connections only: The gateway opens the connection, so no inbound port is opened on the plant network.
- Encryption: Data travels over TLS from the gateway to the platform.
- Roles and permissions: Each user sees and changes only what their role allows, and every remote command is logged.
- Safety stays local: Interlocks and emergency stops never depend on the internet link.
Migrating without stopping the plant
Start read-only. Connect the gateway, mirror the tags that matter and run the cloud dashboards next to the current SCADA. Once alarms and reports match, move the teams that work remotely, and only then enable the remote commands you really need. The existing SCADA can stay as the local HMI for as long as you want.
For where SCADA is used today, see the five main applications of SCADA, with examples by sector and the most used software.
















