SCADA
SCADA stands for Supervisory Control And Data Acquisition. It is the architecture for monitoring and controlling geographically dispersed assets like pipelines, water utilities, electrical grids, and oil and gas wellheads. A SCADA system pulls data from remote RTUs or PLCs over a wide-area network into a central HMI and historian.
Read one of your own drawings.
Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.
PDF · DWG · DXF · TIFF · PNG · XLSX
SCADA emerged in the 1960s to solve a problem DCS was never designed for. How to monitor and operate assets that are kilometres or hundreds of kilometres apart. A refinery DCS can run on a deterministic gigabit network where every field signal is refreshed every few hundred milliseconds. A natural gas pipeline system with valve stations every 30 km cannot. SCADA builds around a different assumption. The field site has its own local controller, RTU or PLC, and the SCADA host in the central control room polls that controller over a wide-area link at intervals measured in seconds. The SCADA architecture therefore has three layers the DCS does not. The remote field site with its own local logic, the wide-area communications network, and the SCADA host that aggregates and presents data from all sites simultaneously. The SCADA host typically includes an HMI, operator displays, a historian, time-series storage, an alarm-management engine, and a reporting layer. The boundary between SCADA and DCS is cultural as much as technical. A modern DCS can supervise geographically distributed assets over OPC UA. A modern SCADA platform can run tight regulatory control. The terms reflect the original architectural intent and remain useful as shorthand for the polling-over-WAN topology versus the deterministic-bus topology.
How does SCADA differ from a DCS..
DCS is for densely-located, continuous-process plants where every controller is within a control building radius. SCADA is for sparsely-located, often-discrete-event assets where field sites are kilometres apart and the communications layer, radio, cellular, fibre, satellite is part of the architecture. SCADA networks tolerate latency that a DCS would not. SCADA polls field data at intervals while a DCS receives it continuously over a deterministic bus.
What are the common SCADA platforms..
Wonderware, now AVEVA, Inductive Automation Ignition, Siemens WinCC, GE iFix and CIMPLICITY, Schneider EcoStruxure ClearSCADA, Rockwell FactoryTalk View SE, OSIsoft PI System, as the historian layer that ties to SCADA front ends. For pipeline-specific SCADA. Emerson, Honeywell, and Telvent, Schneider have pipeline-tuned product lines.
How is a SCADA field site architected..
A typical SCADA field site has an RTU or PLC that reads local instruments, executes configured alarm limits and simple interlock logic, stores data between polls, and communicates back to the SCADA host on demand or on schedule. Instruments at the site follow the same signal conventions as a plant. PT-101 reads 4-20 mA from a pipeline pressure transmitter. FT-102 reads a turbine pulse count from a metering run. ZSO-501 and ZSC-502 confirm block valve positions. The I/O at each site maps to an RTU register or a PLC tag that the SCADA host polls by address. The site-level I/O list therefore includes the RTU register address or DNP3 point number alongside the standard signal-class and range columns used in plant I/O lists.
What protocols does a SCADA system use..
DNP3 is the dominant protocol in electrical and water utilities because it supports unsolicited reporting, time-stamped events, and data-integrity reporting over unreliable links. Modbus RTU over radio or cellular is common in pipeline and oil-and-gas production applications. IEC 60870-5-101 and -104 are the European electrical-utility equivalents. ICCP, IEC 60870-6 bridges SCADA systems between utility operators. Modern deployments increasingly use MQTT with Sparkplug B for the field-to-cloud leg, with OPC UA aggregating at a plant-level gateway. The communications layer is part of the SCADA I/O design and must be specified in the I/O list or a companion communications-mapping document.
How is SCADA secured against cyber attack..
SCADA systems face threats that DCS networks historically did not. Wide-area communications links, remote-access requirements for unmanned sites, and in some cases internet-exposed historian interfaces. The ISA, IEC 62443 standard defines a security lifecycle for industrial automation systems including SCADA. NERC CIP mandates cyber security requirements for bulk electric system control systems in North America. AWWA M2 and WaterISAC provide guidance for water-utility SCADA. The engineering consequence is that the SCADA I/O list and communications design must be reviewed against the facility's cyber security risk assessment before field deployment, and remote-access channels to RTUs must be secured rather than relying on physical isolation alone.
SCADA vs DCS at a glance.
Both architectures monitor and control industrial processes. They differ in geography, tightness of control, and the I/O list shape they expect.
| Aspect | SCADA | DCS |
|---|---|---|
| Geography | Geographically dispersed assets. Pipelines, water grids, wellheads, electrical substations | Single plant or facility. Refinery, petrochemical unit, power station |
| Communication | Wide-area network. Cellular, satellite, radio, fiber to remote sites | Local plant network. Control bus, fieldbus, dedicated Ethernet |
| Control style | Supervisory. Setpoints sent down to local RTUs and PLCs which close the loop locally | Tight closed-loop control with millisecond cycle times across the whole plant |
| Field controllers | RTUs, Remote Terminal Units and PLCs at each remote site | Distributed controllers on a unified DCS backbone, Emerson DeltaV, Honeywell Experion, Yokogawa CENTUM |
| Historian | Centralized historian aggregating data from many remote sites | Integrated DCS historian, often part of the controller backbone |
| Common protocols | DNP3, IEC 60870-5, Modbus over IP, MQTT, OPC UA | Proprietary DCS bus, Profibus DP, Profinet, Foundation Fieldbus, HART, OPC UA |
| Typical industries | Oil and gas midstream, water and wastewater, electrical T and D, rail | Refining, petrochemicals, pulp and paper, pharmaceutical, power generation |
| I/O list shape | RTU and site columns, polling interval, network endpoint | DCS controller cabinet, card slot, channel. Integrated alarm priority |
Frequently asked.
Is SCADA the same as an HMI.
An HMI is one component of a SCADA system, plus the data-acquisition layer that pulls from remote sites. A standalone HMI in a plant control room is part of a DCS or PLC architecture rather than a SCADA system.
Why is SCADA security a separate topic from plant control security.
Because the wide-area communications layer exposes remote sites to attack vectors that a closed plant network does not. Most SCADA security guidance, ISA, IEC 62443, NERC CIP for power, AWWA M2, WaterISAC for water utilities is targeted at the field-to-control-centre link and the remote-access workflows.
How does the I/O list differ for a SCADA project versus a DCS project.
A SCADA I/O list typically has fewer analog control loops and more discrete status and alarm points per site, with an additional column for the RTU address or DNP3, Modbus register mapping. Each site contributes its own I/O count. The master list aggregates across all sites and includes the communications path alongside the signal class.
Can a SCADA system execute closed-loop control.
Yes, but with limitations. SCADA polling latency, seconds to tens of seconds is too slow for tight regulatory loops like pressure control on a compressor. SCADA typically executes supervisory control. Setpoint adjustments, mode changes, start, stop commands sent down to the local RTU or PLC. The RTU or PLC runs the fast closed-loop at the site. The SCADA host supervises the overall operating strategy.
What is the difference between a SCADA historian and a DCS historian.
Functionally the same. Both store time-series process data at configured scan rates and provide query interfaces for reporting and analytics. In a SCADA system the historian aggregates data from many geographically dispersed sites. In a DCS the historian aggregates from the plant-internal I/O. OSIsoft PI, now AVEVA PI and Honeywell Uniformance are common on both architectures. The SCADA historian is often the first data source for enterprise analytics because it is the only system with data from the full pipeline or utility network.
What P&ID documents does a SCADA project produce.
For a pipeline or utility SCADA project, the P&ID equivalent is often a schematic flow diagram, SFD or a hydraulic profile drawing rather than a traditional P&ID. Individual valve sites may have a local P&ID for the site equipment. The field-site I/O list for that site is the instrument record. The master document tying sites together is often the SCADA configuration database rather than a single P&ID set.