SCADA (supervisory control and data acquisition) is the software layer that collects data from PLCs, RTUs and sensors, shows the process to operators on HMI screens, raises alarms and lets operators send commands back to the field. The controllers run the process. SCADA lets people watch it, keep its history and step in, from one control room.
NIST describes SCADA systems as built to collect field information, bring it to a control center and display it to operators, so that a whole system can be monitored and controlled from one place in near real time (NIST SP 800-82r3, section 2.3.2). The term started with geographically spread assets such as pipelines, power grids and water networks. Today it is also used for the supervisory software on a single plant floor.
The components of a SCADA system
A SCADA system is a chain of devices, networks and software, and each link has its own job.
Field devices and sensors
Transmitters, switches, meters, valves and drives measure pressure, flow, level, temperature or position, and act on commands. Most of them talk to a controller over wired signals (for example 4-20 mA) or a fieldbus, not to SCADA directly.
PLCs and RTUs
A PLC (programmable logic controller) runs the control logic for a machine or process unit: it reads inputs, executes its program cycle after cycle and drives outputs. An RTU (remote terminal unit) does a similar job at a remote site, such as a pumping station or substation, and is built for slow or unreliable links. Either one keeps running the local process if the link to SCADA is lost.
Communication networks and protocols
The controllers and the SCADA servers talk over serial lines, Ethernet, radio, cellular or fibre, and over a protocol both sides understand:
- Modbus (RTU and TCP): simple register reads and writes, still the common denominator across vendors.
- OPC UA: a vendor-neutral standard with an information model, security and browsing of what a server offers.
- DNP3 (IEEE 1815): common in electric utilities and water, designed for telemetry over slow links, with time-stamped events.
- IEC 60870-5-104: the telecontrol standard widely used in power grids, the TCP/IP form of IEC 60870-5-101.
- MQTT: a lightweight publish-subscribe protocol, increasingly used to move data from the edge to SCADA and other consumers.
SCADA servers
The SCADA server (also called the control server or master station) polls the controllers or receives their reports, keeps the live value of every tag, evaluates alarm conditions and passes operator commands down. Larger systems run redundant servers.
HMI
The HMI (human-machine interface) is the operator's window: process graphics, faceplates for pumps and valves, trends and alarm lists.
Historian
The historian stores tag values with their timestamps over months or years, for trends, incident investigation and reports.
Alarm management
Alarms tell an operator that something needs action: a limit crossed, a device failed, a link lost. Alarm management covers priorities, acknowledgement, shelving and the review of nuisance alarms, so the important ones are not buried.
How SCADA works: from one sensor value to an operator action
Follow one value through the system: the discharge pressure of a pump in a water pumping station.
The transmitter turns the pressure into a current signal. The PLC or RTU reads it, scales it to bar, and uses it in its own logic, for example to stop the pump if the pressure goes far beyond its limit. That protection runs in the controller, whether or not SCADA is connected.
The SCADA server asks the controller for the value at a set interval, or the controller reports changes on its own, depending on the protocol. The server updates the tag, writes it to the historian and refreshes the pump graphic on the HMI.
When the pressure crosses the high alarm limit, the server raises an alarm with its priority and time. The operator acknowledges it, opens the trend, sees that the pressure has climbed for twenty minutes, and decides to start the standby pump. The command goes from the HMI through the server to the controller, which checks its interlocks before it runs the pump. The alarm, the acknowledgement and the command are all logged with the operator's name.
The operator decides, SCADA carries the decision, and the controller has the final say on whether it is safe. Every step depends on the network between them, which is why SCADA security is about networks as much as software.
SCADA vs PLC vs DCS vs MES vs an industrial data platform
These terms are often mixed up because the systems overlap and share data. The table separates them by job.
| System | What it does | Typical scope | Who uses it |
|---|---|---|---|
| PLC | Runs the control logic: reads inputs, executes the program, drives outputs | One machine, cell or process unit | Controls engineers and maintenance technicians |
| SCADA | Collects data from controllers, shows it on HMI screens, raises alarms, keeps history and passes operator commands | A plant, or many remote sites such as pipelines, grids and water networks | Control-room operators, shift supervisors, automation engineers |
| DCS | Controls a continuous process with integrated controllers, engineering tools and operator stations in one vendor system | One site, usually a process plant: refining, chemicals, power generation | Process operators and control engineers |
| MES | Manages production execution: orders, recipes, material tracking, quality records and performance | A plant's production operations | Production managers, planners, quality teams |
| Data platform (industrial, IIoT) | Collects data from many sources, gives it one structure, keeps history and delivers it to IT, analytics and cloud systems | Many lines, plants and systems, from OT to IT | Engineers, data and IT teams, operations managers |
NIST draws the SCADA and DCS line by geography and purpose: SCADA for dispersed assets where centralized data acquisition matters as much as control, DCS for production within one location, controlled through supervisory and local loops (NIST SP 800-82r3, sections 2.3.2 and 2.3.3). PLCs appear inside both. MES sits above them in the ISA-95 model, at the level of manufacturing operations management. In practice the products overlap.
Where SCADA is used
- Energy and utilities: power transmission and distribution, substations, renewable plants.
- Water and wastewater: pumping stations, reservoirs, treatment plants and distribution networks.
- Oil and gas: pipelines, compressor stations, wellheads and terminals.
- Manufacturing: production lines and the utilities behind them, such as compressed air, boilers and chillers.
- Buildings and campuses: heating, ventilation, power and lighting, usually through building automation systems that work on the same principles.
SCADA security
SCADA systems were long built for availability inside closed networks, and many field protocols assume a trusted link. Once SCADA is connected to the corporate network, remote access and the cloud, the network design carries much of the security.
- Network segmentation. Keep the OT network separate from the corporate network, with a DMZ between them so traffic does not pass directly from one to the other. NIST recommends firewall rules that only allow connections between adjacent levels, so business systems never talk straight to controllers (NIST SP 800-82r3, section 5.2.3.1).
- IEC 62443. The ISA/IEC 62443 series sets security requirements for industrial automation and control systems, for asset owners, integrators and product suppliers. IEC 62443-3-2 partitions a system into zones and conduits and assigns each a target security level; IEC 62443-2-1 covers the asset owner's security program.
- NIST SP 800-82r3. NIST's guide to OT security (September 2023) covers SCADA, DCS and PLC topologies, common threats, and countermeasures such as defense in depth, multi-factor authentication for remote access and disabling unused ports and services.
- Outbound-only data flows. When data has to leave the OT network, for a historian in IT, an MES or a cloud service, let the OT side open the connection outward instead of listening for inbound connections. Nothing outside can then open a session into the control network through that path. Unidirectional gateways (data diodes) are the hardware form of the same idea. This is not a complete answer: NIST notes that unmanaged outbound connections are a risk too and recommends outbound rules as strict as inbound ones.
The design for moving plant data to IT without opening the OT network is covered in IT/OT convergence: building a secure industrial bridge.
Where SCADA ends and a data platform begins
SCADA is good at its job: a validated control layer with alarm philosophy, operator training and tested command paths. That is why it stays.
What SCADA was not designed for is serving the same data to many consumers outside the control room. When MES, ERP, maintenance, energy reporting and cloud services each need plant data, the usual result is one point-to-point link per consumer: an OPC connection here, a SQL export there. Tag names follow each project's conventions, and history sits in one historian per site.
So plants add a data layer beside or above SCADA instead of stretching SCADA further:
- SCADA stays the control and operator layer. Screens, alarms for operators, commands and interlocks remain where they are.
- A data layer handles distribution. It reads from the controllers, or from the SCADA server itself over OPC UA, and publishes values in a Unified Namespace with a consistent structure across sites.
- History and delivery move with it. A historian for long-term data, and delivery to IT and cloud systems, each consumer with its own permissions.
This has costs. Two systems reading the same PLC add load to the controller, so read intervals need agreement. Tag names have to be mapped once. Someone has to own the namespace. For a single site where the SCADA historian already serves the few systems that need data, another layer may not be worth it. The longer argument, with the cases on both sides, is in SCADA and Unified Namespace: architectural roles.
Where Proxus fits
Proxus is an industrial data platform, not a SCADA. Its edge gateways read PLCs, CNCs, meters and OPC UA servers (a SCADA server's OPC UA interface included) over their native protocols. It publishes the values in a Unified Namespace, keeps them in a historian, and shows them on dashboards and trends, with alarms that operators acknowledge. Gateways open their connection outward to the hub, so nothing on the plant network has to accept connections from it (architecture). Proxus can write to devices, through paths you configure on purpose: form setpoints and write buttons with limits and a confirmation, and device-write steps in pipelines. Operator control of a process belongs in SCADA or an HMI. Where control is needed, Proxus runs alongside SCADA as the data layer. For sites that only need monitoring, alarms and reports, it can be the lighter option. See the platform, or try it on your own equipment.
Frequently Asked Questions
What does SCADA stand for?
SCADA stands for supervisory control and data acquisition. "Supervisory control" means operators oversee and adjust a process that controllers run. "Data acquisition" means collecting measurements and states from the field into one system.
What is the difference between SCADA and a PLC?
A PLC is a controller: it runs the logic that keeps one machine or process unit working, cycle after cycle, and keeps running if the network fails. SCADA is the supervisory software above many PLCs and RTUs: it collects their data, shows it to operators, raises alarms, stores history and sends operator commands to them.
Is SCADA software or hardware?
Both, depending on what is meant. SCADA software runs on servers and operator workstations: the SCADA server, the HMI, the historian and alarm management. A SCADA system also includes the hardware it depends on: controllers, RTUs, sensors and the network.
What is a SCADA system used for?
A SCADA system is used to monitor and control processes from a central place: power grids, water and wastewater networks, pipelines, production lines and building services. Operators use it to see the live state of the process, respond to alarms, change setpoints, start and stop equipment, and look at history.
What is the difference between SCADA and DCS?
SCADA was built for assets spread over a wide area, with central data acquisition over slow or unreliable links. A DCS controls a continuous process within one site, with controllers, engineering tools and operator stations integrated in one vendor system. The products overlap today, but the distinction still describes how each is used.
References
- NIST SP 800-82r3, Guide to Operational Technology (OT) Security (September 2023) - SCADA, DCS and PLC topologies (sections 2.3.2 to 2.3.4) and network segmentation (section 5.2.3.1). csrc.nist.gov
- NIST CSRC Glossary: supervisory control and data acquisition - The definition NIST uses, from SP 800-82r3. csrc.nist.gov
- ISA-95 / IEC 62264 - Enterprise-control integration and the levels from field devices to business planning. isa.org
- ISA/IEC 62443 series - Security for industrial automation and control systems. isa.org
- IEC 62443-3-2:2020 - Security risk assessment for system design: zones, conduits and target security levels. webstore.iec.ch
- IEC 62443-2-1:2024 - Security program requirements for IACS asset owners. webstore.iec.ch
- IEC 60870-5-104 - Telecontrol transmission protocol over standard transport profiles. webstore.iec.ch
- IEEE 1815 (DNP3) - Distributed Network Protocol for electric power systems communications. standards.ieee.org
- OPC UA Part 1: Overview and Concepts - OPC Foundation specification. reference.opcfoundation.org
- MQTT Version 5.0, OASIS Standard - The publish-subscribe protocol. docs.oasis-open.org
- Modbus Organization - The Modbus protocol and its specifications. modbus.org