SCADA Systems for Water & Wastewater
How scada systems is delivered for water & wastewater — typical scope, applicable standards, and engineering considerations.
SCADA Systems for Water & Wastewater
SCADA systems for water and wastewater are not generic “monitoring software” projects. They are operational control platforms that must support continuous utility service, remote telemetry, alarm management, cybersecurity, maintainability, and regulatory reporting across treatment plants, pumping stations, reservoirs, lift stations, and distribution assets. In practice, the scope is defined by process criticality, asset geography, communications reliability, and the client’s operational model: centralized control room, distributed local operation, or a hybrid arrangement.
How the service is typically scoped
A well-scoped water/wastewater SCADA project starts with a functional narrative rather than a software list. The engineering team should define the control philosophy, alarm philosophy, tag list, network architecture, HMI standards, historian requirements, and handover data set. For utilities, scope often includes remote terminal units (RTUs) or PLCs, instrument integration, pump and valve control, tank level management, wet-weather overflow monitoring, energy metering, and secure remote access for maintenance teams.
Typical deliverables include:
- Functional Design Specification (FDS) or Control Narrative
- Cause-and-effect matrix for pumps, valves, and alarms
- I/O list and tag database
- SCADA architecture diagram and network segmentation concept
- HMI screen philosophy and graphics standards
- Alarm matrix with priorities, deadbands, delays, and acknowledgements
- Cybersecurity concept and remote access design
- Factory Acceptance Test (FAT) and Site Acceptance Test (SAT) procedures
- As-built documentation, backups, and operator training package
For European projects, the scope should also anticipate CE-related machine integration responsibilities where control panels, drives, or packaged skids are supplied as assemblies. Depending on the supply boundary, compliance may involve EN 60204-1 for electrical equipment of machines and EN 61439 for low-voltage switchgear and controlgear assemblies. If the SCADA system is part of machinery control, the risk assessment and safety-related control functions must align with EN ISO 12100 and EN ISO 13849-1 or IEC 62061 as applicable.
Applicable standards and compliance points
Water and wastewater SCADA systems sit at the intersection of automation, electrical, functional safety, and cybersecurity. The most relevant standards depend on the project scope, but the following are commonly referenced:
- IEC 61131-3 for PLC programming languages and software structure
- IEC 60204-1, Clause 9 and Clause 10, for control circuits and operator interface considerations in machinery-related control panels
- EN 61439-1 and EN 61439-2 for panel design, temperature rise, dielectric performance, and verification of assemblies
- IEC 62443 series for industrial cybersecurity; in particular IEC 62443-3-3 for system security requirements and IEC 62443-2-1 for security program requirements
- ISA-18.2 and IEC 62682 for alarm management lifecycle, rationalization, shelving, prioritization, and performance monitoring
- ISA-101 for HMI philosophy and high-performance operator graphics
- IEC 60870-5-104 or DNP3 where telecontrol protocols are used for remote stations, subject to utility practice and vendor compatibility
- NFPA 70 (NEC), especially Articles 110 and 250, where North American installations or hybrid projects require grounding and safe installation practices
Alarm handling is a frequent failure point in water utilities. ISA-18.2 and IEC 62682 require a lifecycle approach: alarm philosophy, rationalization, implementation, operation, maintenance, and audit. A practical project should define alarm deadbands, time delays, and priorities so that transient wet well levels or pump starts do not flood the operator with nuisance alarms. For HMI design, ISA-101 supports consistent navigation, color use, and situational awareness, reducing operator error during storm events or process upsets.
Typical engineering decisions
One of the first decisions is whether to use a centralized SCADA server architecture or a distributed edge architecture with local autonomy. In water and wastewater, local control must usually survive WAN loss, because pumping stations and lift stations cannot depend on continuous communications to remain operational. That means RTUs or PLCs should execute local sequences, with SCADA providing supervision, alarming, trending, and setpoint management rather than direct real-time dependency.
Communication media is another key decision. Fiber is preferred for plants and dense campuses; licensed radio, cellular VPN, or industrial Ethernet over public networks may be appropriate for remote stations. The design must consider latency, bandwidth, availability, and cybersecurity. IEC 62443 requires zoning and conduits concepts, so plant networks should be segmented into control, supervisory, and enterprise zones, with firewalls and controlled remote access.
Historian and reporting requirements also influence architecture. Utilities often need compliance logs, overflow events, pump run hours, energy consumption, and maintenance trends. Historian retention should be aligned with operational and regulatory needs, and time synchronization should be robust across all nodes using NTP or equivalent time services.
Small comparison: common SCADA delivery choices
| Decision area | Option A | Option B | Typical guidance |
|---|---|---|---|
| Control philosophy | Centralized control | Local autonomous control with supervisory SCADA | Prefer local autonomy for remote pumping and lift stations |
| Communications | Public cellular | Fiber or licensed radio | Use public cellular only with VPN, segmentation, and fallback logic |
| Alarm strategy | All events as alarms | Rationalized alarms with priorities | Follow ISA-18.2/IEC 62682 to reduce nuisance alarms |
| Cybersecurity | Flat network | Zones and conduits | Use IEC 62443 segmentation and controlled remote access |
Validation, testing, and handover
Validation should prove that the system performs safely and predictably under normal and abnormal conditions. FAT should verify software logic, graphics, alarms, trends, reports, and communications using simulation or emulation before site deployment. SAT should confirm instrument loop integrity, field device response, communications resilience, failover behavior, and operator workflow under real plant conditions.
A good validation plan includes point-to-point checks, loop checks, alarm testing, sequence testing, power-loss recovery tests, and cybersecurity verification. For example, if a pump is commanded from SCADA, the test should confirm permissives, interlocks, local/remote selection, start feedback, fault indication, and alarm generation. If a communications link fails, the system should demonstrate safe fallback behavior and store-and-forward event handling where required.
Documentation handover should include backup images, license files, network diagrams, password and access control procedures, spare parts recommendations, and a maintenance strategy. Operators should receive training on alarm acknowledgment, manual override, report generation, and recovery procedures after communications loss or server failure.
What good delivery looks like
In water and wastewater, a successful SCADA project is not defined by screen count or tag count. It is defined by operational reliability, alarm quality, cybersecurity posture, maintainable code, and clear ownership between process, electrical, and IT teams. The best projects are engineered so that the plant can continue to operate locally if the network is degraded, while still giving operators the visibility and control they need to manage assets efficiently and meet compliance obligations.
If you are planning a new utility SCADA system or modernizing an aging one, we can help scope the architecture, standards, deliverables, and validation plan for your site — discuss your project via /contact.
Other industries for SCADA Systems
Other services for Water & Wastewater
Frequently asked questions
What standards should a SCADA system for water and wastewater comply with on European projects?
For European projects, SCADA architectures are typically aligned with IEC 62443 for industrial cybersecurity, IEC 61131 for PLC programming, and IEC 60204-1 / EN 61439 where the project includes machine or control-panel interfaces. Water-sector projects may also need to demonstrate conformity with EN 15232 for building automation interfaces and local utility specifications, while functional safety elements should be assessed against IEC 61508 or IEC 61511 where applicable.
How should SCADA network segmentation be designed for a wastewater treatment plant with remote pumping stations?
A common design is to separate the plant control network, supervisory SCADA layer, and remote telemetry links into distinct zones and conduits, with firewalls or secure gateways between them in line with IEC 62443-3-2 and IEC 62443-3-3. Remote pumping stations should use authenticated VPN or private APN connectivity, and critical control functions should remain local at the PLC or RTU level so loss of comms does not stop process control.
What is the best PLC/RTU architecture for distributed water and wastewater assets?
For distributed assets such as booster stations, lift stations, and reservoir sites, a PLC or RTU with local autonomy, buffered alarms, and store-and-forward data handling is usually preferred over direct cloud-dependent control. The control hardware should support deterministic I/O scanning, watchdog diagnostics, and standard industrial protocols such as Modbus TCP, PROFINET, or OPC UA, depending on the project’s integration standard and cybersecurity requirements under IEC 62443.
Which instrumentation signals are most commonly integrated into SCADA for water and wastewater plants?
Typical signals include analog 4–20 mA or digital HART for level, flow, pressure, turbidity, pH, dissolved oxygen, conductivity, and chlorine residual, plus discrete statuses for pumps, valves, and MCC starters. Signal selection should reflect the instrument loop design, EMC environment, and panel wiring practices, with marshalling, isolation, and surge protection implemented in accordance with IEC 61000 and the applicable panel standard such as EN 61439.
How do you handle alarms and event management in a wastewater SCADA system to avoid nuisance alarms?
Alarm philosophy should define priorities, deadbands, delays, shelving rules, and operator response requirements before configuration, which is consistent with ISA 18.2 and IEC 62682. For wastewater plants, high-level wet well, pump fail, overflow risk, and analyzer fault alarms should be rationalized so that nuisance conditions do not mask true process upsets or cause alarm flooding during storm events.
What are the key cybersecurity requirements for SCADA in municipal water utilities?
Municipal water SCADA systems should implement role-based access control, MFA where feasible, asset inventory, patch management, secure remote access, logging, and backup/restore procedures, as described in IEC 62443 and commonly mapped to NIST practices. Network devices, PLCs, historians, and operator workstations should be hardened and segmented, and any remote maintenance path must be authenticated, encrypted, and auditable.
How should electrical panels be designed for SCADA-controlled pumping stations and treatment plants?
Panels should be built with proper segregation of power, control, and communication wiring, adequate short-circuit protection, labeled terminals, and environmental protection suited to the installation site. For European projects, EN 61439 is the key assembly standard for low-voltage switchgear and controlgear assemblies, while IEC 60204-1 is often used where machine-style control equipment is involved; EMC and surge protection should be addressed early to protect PLCs, HMIs, and network devices.
What is the recommended approach for historian, reporting, and compliance data in water and wastewater SCADA?
A historian should capture time-stamped process values, alarms, operator actions, and batch or event records with synchronized clocks, typically using NTP or PTP across the control system. For compliance and performance reporting, retention, auditability, and data integrity should be defined in the functional specification, with cybersecurity and access controls aligned to IEC 62443 and alarm/event practices aligned to ISA 18.2.