Every smart city system-from water distribution to traffic management-relies on SCADA (Supervisory Control and Data Acquisition) to function smoothly. But what happens behind the scenes when a pressure sensor in a remote pipeline sends a reading to a control room operator 50 kilometers away? Understanding how data flows through a SCADA system, from the field devices to the operator’s screen, is essential for anyone working in smart infrastructure management.
Table of Contents
- Where SCADA data originates: the Remote Terminal Unit
- Communication protocols and data transmission
- Common SCADA protocols
- Transmission methods
- The communication front end: gateway to the host
- Error checking and data integrity
- Data processing at the host SCADA
- Conversion to engineering units
- Quality validation
- Limit checking and alarms
- Database storage and operator display
- The complete data flow cycle
Where SCADA data originates: the Remote Terminal Unit
The journey of SCADA data begins at the Remote Terminal Unit (RTU). An RTU is a microcontroller-based device deployed at field locations-pump stations, electrical substations, water treatment facilities-where it interfaces directly with physical equipment. RTUs connect to sensors and field instruments that monitor parameters like temperature, pressure, flow rates, and equipment status.
RTUs handle three primary types of input data:
Analog inputs represent continuously variable measurements. These include values like tank levels, pipeline pressures, motor speeds, and temperatures. The physical variable is first measured by a transducer, and the output passes through an analog-to-digital (A/D) converter in the RTU. This converter produces a digital number that the host computer can process.
Digital (status) inputs represent discrete states-a valve is either open or closed, a pump is either running or stopped. Some RTUs can detect multiple status changes between scans, and advanced units can time-stamp these changes to create a precise sequence of events (SOE) record.
Pulse (count) inputs track cumulative measurements. Pulse accumulators are commonly used to measure total energy consumption, or the volume of liquid or gas passing through a meter. Each time a unit of the measured quantity passes by, the detection device opens and closes a contact, and the pulse accumulator counts these contact changes.
Communication protocols and data transmission
Once the RTU has collected and digitized field data, it must transmit this information to the central SCADA system. The RTU encodes sensor inputs into protocol format and forwards them to the SCADA master station. This communication process is called telemetry.
Common SCADA protocols
SCADA systems use specialized communication protocols designed for industrial environments. The most widely used include:
DNP3 (Distributed Network Protocol) was originally designed for electric and water utilities. It facilitates reliable, secure data transmission between SCADA master stations and RTUs. DNP3 offers several key advantages: it works seamlessly with related protocols like Modbus, improves bandwidth efficiency through event-oriented data reporting, and includes robust error detection mechanisms that enhance transmission reliability.
Modbus RTU and Modbus TCP/IP remain among the most common protocols in industrial automation. Their simplicity and wide vendor support make them practical choices for many SCADA applications.
Transmission methods
The physical transmission medium varies based on site requirements and geography. SCADA systems have traditionally used combinations of radio and direct wired connections, though modern systems increasingly use Ethernet, cellular networks, and even satellite links for remote locations. For large systems like railways and power stations, SONET/SDH fiber optic networks are frequently employed.
Data can be transmitted in two ways. Polling is a command-and-response method where the master station periodically requests data from each RTU. Report-by-exception allows RTUs to transmit data spontaneously when values change beyond a defined threshold, optimizing bandwidth by avoiding unnecessary transmissions of unchanged data.
The communication front end: gateway to the host
Before data reaches the main SCADA server, it typically passes through a Communication Front End (CFE) or front-end processor. These intermediate devices perform several critical functions to minimize processing load on the host computer.
The CFE maintains scanning instructions provided by the host, allowing the system to request data with minimal communication overhead. It also handles reporting communication errors when RTUs do not respond or respond with errors. Perhaps most importantly, the CFE checks incoming data so the host receives only data that has changed since the previous scan.
Large SCADA installations typically run redundant front-end computers in a dual primary/secondary configuration. This ensures continuous scanning even if one front end fails, preventing data loss during equipment malfunctions.
Error checking and data integrity
Maintaining data integrity across potentially unreliable communication links is critical for SCADA operations. Multiple layers of error checking protect against data corruption.
At the protocol level, algorithms like CRC (Cyclic Redundancy Check) provide a high level of data security during transmission. CRC can detect transposition of bytes, insertion of data, and other transmission errors. Simpler methods like BCC (Block Check Character) offer medium-level security but cannot detect certain error types. SCADA network topology typically includes transport validation independent of content validation, adding another layer of protection.
DNP3 protocol provides additional safeguards through time synchronization with RTUs, reconstructing time-stamped variants of all data point objects through a sequence of events. This ensures all components within the SCADA system operate in harmony, maintaining data integrity and accuracy.
Data processing at the host SCADA
When raw data arrives at the host SCADA system, it undergoes several processing steps before becoming useful for operators.
Conversion to engineering units
Raw values from RTUs are just numbers-voltage levels or digital counts that mean little to human operators. The host system converts all analog values to floating point numbers and adjusts them to represent physical measurements in engineering units-megawatts, pounds per square inch, cubic feet per second, or degrees Celsius. Only in this form do values become meaningful for display and calculations.
For example, a temperature transducer might output a 4-20mA signal that the RTU converts to a digital value between 0 and 4095. The host SCADA applies scaling factors to convert this number to actual temperature in degrees, accounting for the sensor’s calibration range.
Quality validation
Upon receiving a value for an analog point, SCADA checks the validity against the IEEE standard to ensure it can safely use the value. Invalid values generate an alarm and are ignored. For very small values, SCADA rounds to zero.
The system also performs reasonability checks. If a value falls outside predefined reasonable limits-perhaps a temperature reading of 500ยฐC for a process that never exceeds 100ยฐC-SCADA considers the value unreasonable and ignores it, retaining the last known good value.
Limit checking and alarms
Valid data is compared against multiple types of limits stored in the database. Normal limits define the acceptable operating range; values outside this range trigger abnormal state indicators and can generate alarms. Forbidden range limits flag values within ranges where operation should be minimized. Rate-of-change limits detect if measurements are changing too rapidly between scans, potentially indicating sensor failures or process upsets.
The system applies deadband logic to prevent alarm chatter-a value that has exceeded a limit must return past the limit by at least the deadband amount before the system considers it normal again.
Database storage and operator display
Processed and validated data is stored in the SCADA database, often called the real-time database or process database. Each measurement point has an associated record containing the current value, quality flags, timestamps, alarm states, and configuration parameters.
Data is compiled and formatted so that control room operators using the Human-Machine Interface (HMI) can make supervisory decisions to adjust or override normal RTU controls. Quality flags travel with the data, allowing operators to quickly identify which values are good, suspect, old, or manually replaced.
The best HMI systems present data as intuitive graphical representations-process diagrams, trend charts, geographic maps-with real-time values updating as new data arrives. Historical data is also typically stored in a separate historian database for trend analysis, reporting, and regulatory compliance.
The complete data flow cycle
The entire journey-from a sensor detecting a change in the field to an updated value appearing on an operator’s screen-typically completes in seconds. A scan group of high-priority measurements might update every two seconds, while less critical data refreshes every 10-30 seconds.
This continuous cycle of data acquisition, transmission, processing, and display enables operators to maintain real-time awareness of distributed infrastructure across entire cities or regions. The reliability of this data flow directly impacts the safety and efficiency of critical systems that millions of people depend on daily.
What do you think? Consider your city’s water or power infrastructure-how might delays or errors in SCADA data flow affect the services you rely on? What redundancy measures would you expect to protect critical systems?
References
- https://en.wikipedia.org/wiki/Remote_terminal_unit
- https://nathaniellindsey.gitbooks.io/scada-user-s-guide/content/overview_of_scada/how_scada_acquires_and_processes_data.html
- https://www.dpstele.com/scada/system-data-communication.php
- https://en.wikipedia.org/wiki/SCADA
- https://nathaniellindsey.gitbooks.io/scada-user-s-guide/content/overview_of_scada/scada_system_hardware.html
- https://www.scadalink.com/support/knowledge-base/an-introduction-to-scada/
Leave a Reply