The short answer
What Is SCADA?
SCADA stands for supervisory control and data acquisition. It is the software and communication layer that gathers data from PLCs and RTUs spread across a plant or a service area, displays it to operators, records it to a historian, raises alarms, and allows an operator to change setpoints or command equipment. SCADA supervises; the controllers do the actual real-time control.
Key points
- SCADA supervises and records. The PLC or RTU performs the control.
- A plant must be able to run, at least safely, when SCADA is down.
- The core pieces are a data server, operator clients, a historian, and an alarm subsystem.
- In water and wastewater the communication path to remote sites is usually the hardest part.
- Redundancy protects visibility and history, not the control itself.
The division of labor
This is the point people get wrong most often, and it has real consequences. The PLC at a lift station starts and stops the pumps. It does that from its own logic, using its own level input, on its own scan. SCADA watches. It shows an operator the wet well level, records it, alarms if it goes high, and lets the operator change a setpoint or take a pump out of service.
If the radio path fails, the lift station keeps pumping. The utility loses visibility, alarming, and history, which is serious, but sewage does not back up because a server rebooted. Any design where a communication loss stops the process should be treated as a defect unless there is a specific, documented reason for it.
What a SCADA system is made of
- I/O or data server
- Polls controllers and remote sites, maintains the current value of every tag, and serves those values to everything else. This is the piece that most affects perceived system health.
- Operator clients
- The displays operators work from, whether a dedicated workstation, a thin client, or a browser session.
- Historian
- Stores values over time so you can trend last night, compare this month to last, and produce regulatory reports.
- Alarm subsystem
- Evaluates conditions, maintains alarm state, records acknowledgement, and hands off to notification.
- Notification
- Callout, SMS, email, or voice for the alarms that need someone at 2 a.m. Often a separate product.
- Communication front end
- The drivers and hardware that reach controllers over Ethernet, serial, radio, or cellular. In a distributed utility this is where most of the engineering effort goes.
Tags, quality, and why "bad quality" matters
A SCADA tag carries more than a number. It carries a quality indicator that says whether the value can be trusted, and a timestamp saying when it was last confirmed.
This distinction is the difference between a display that misleads and one that tells the truth. When a remote site stops answering, its last known level does not become wrong, it becomes stale. A well-built display shows that value greyed, hatched, or marked, so an operator does not make a decision on a number from forty minutes ago believing it is live.
Architecture in a water or wastewater utility
A typical municipal system has a plant with a substantial local control network and dozens or hundreds of remote sites reached over licensed radio, cellular, or fiber. The plant side looks like a normal industrial network. The remote side is where the interesting constraints live: limited bandwidth, high latency, intermittent paths, and sites you cannot drive to quickly.
- Poll rates must respect the path. Polling forty radio sites every second will not work and does not help.
- Report-by-exception protocols like DNP3 fit constrained links far better than continuous polling.
- Timestamping at the remote site preserves event order when a path drops and recovers.
- Store-and-forward at the RTU means an outage costs you visibility, not history.
Redundancy: what it does and does not buy
Redundant SCADA servers protect against losing the supervisory layer. They do not make the process more reliable, because the process is not being controlled there. Understanding that keeps the money in the right place: a redundant server pair is worthwhile for a utility that depends on continuous visibility and history, but it is not a substitute for controllers that ride through a communication failure on their own.
Redundancy also has to be tested. A failover that has never been exercised is a hypothesis. Schedule a real switchover during a controlled window, watch what happens to alarms, history continuity, and client reconnection, and write down what actually occurred.
Terms that overlap
- SCADA
- Supervisory layer over geographically distributed or plant-wide equipment, with emphasis on data acquisition, history, and alarming.
- HMI
- The operator interface itself. A local HMI panel on a skid is an HMI without being SCADA. SCADA includes HMI as one part.
- DCS
- Distributed control system. Historically an integrated control and supervisory product for continuous process plants, with control and interface designed together. The functional boundary with a modern PLC-and-SCADA system has narrowed considerably.
- Historian
- The time-series database. Sometimes bundled with SCADA, sometimes a separate product serving several systems.
Frequently asked questions
- Does SCADA control the plant?
- Not directly. Controllers execute the control logic. SCADA supervises: it displays, records, alarms, and lets an operator adjust setpoints or issue commands that the controller then acts on.
- What happens if the SCADA server fails?
- In a correctly designed system, the process keeps running on controller logic while you lose visibility, alarming, and history. If equipment stops when SCADA stops, control logic that belongs in the controller is living in the wrong place.
- How often should SCADA poll a remote site?
- Fast enough that an operator can act on a change, slow enough that the communication path stays healthy. For a lift station on licensed radio, every fifteen to sixty seconds for analog values with immediate reporting of alarms and state changes is typical.
- What is the difference between SCADA and a historian?
- SCADA maintains current values and operator interaction. A historian stores values over time and answers questions about the past. They are frequently sold together but they solve different problems, and history requirements should be specified separately.
Related topics
- SCADA ArchitectureThe parts of a SCADA system and how data moves between them: I/O servers, the tag database, clients, the historian, the alarm server, and the topologies from a single panel PC to a redundant, distributed plant.
- ISA-18.2 Alarm ManagementThe lifecycle standard for alarm systems, the rate targets that define a workable system, and why alarm rationalization is the step nobody wants to fund.
- High Performance HMI DesignGrey backgrounds, reserved color, and displays designed to make abnormal conditions obvious rather than to look impressive in a demo.
- Frozen ValuesWhy a SCADA value stops changing while looking normal: the five layers where it can freeze, from a transmitter holding its output to a client that lost its server, how to find the layer by comparing each, and the heartbeat that makes a freeze announce itself.
- SCADA ServersWhat the servers in a SCADA system do and what a utility should expect of them: the I/O, alarm, historian, and client roles, physical versus virtual, redundancy, sizing, placement, backup, patching, licensing, and monitoring.
- SCADA ClientsThe workstations, browsers, and mobile devices operators use to see and control the system: thick, thin, web, and mobile clients, roles and permissions, where control is allowed from, workstation design, session policy, licensing, and failover behavior.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.