PLC scan cycle and data sampling error
Before reading a PLC tag for AI, know where in the scan cycle the value was produced and which timestamp describes it.
SCADA systems supervise and control geographically distributed assets. A practical breakdown of their five core layers and how they fit together.
SCADA — supervisory control and data acquisition — is the system that lets operators monitor and control assets spread across a wide area: pumping stations, electrical substations, pipelines, water networks, wind farms. The defining feature is *geographic distribution* connected over long-distance communication.
A classic SCADA architecture has five layers:
Each RTU polls its local instruments and holds the latest values. The SCADA server polls the RTUs (or receives unsolicited reports) over the communication network. Data arrives at the server, is time-stamped and quality-checked, and is then: displayed on operator screens, written to the historian, and evaluated against alarms.
Control is usually supervisory: the operator or the server sends setpoints and commands down to the RTU, and the RTU handles the fast local loop. This split keeps the system resilient — if the communication link drops, the RTU keeps controlling its local process.
The lines blur — modern SCADA runs on the same servers and protocols as IIoT platforms — but the design requirements differ: SCADA must prioritize availability, deterministic polling, and operator workflows; IIoT prioritizes scale and analytics.