SCADA and Communication Verification: Points, Links and Latency

What it is

SCADA and communication verification is a functional check of the path between field equipment and the supervisory system that monitors and controls it. The devices at the field end are protective relays, meters, breaker and switch controls, transformer and regulator controllers, battery chargers, uninterruptible power systems and inverters. At the other end are a data acquisition or communication gateway, a local or remote terminal unit, and the control-room display or historian. Between them lie the links: serial or Ethernet cabling, fiber, radio or leased circuits, and the protocol that carries the data. The test works through the data points one by one. Status and alarm indications are changed at the source and watched at the destination, analog measurements are compared across the path, and remote commands are sent and confirmed at the equipment. The check also covers the communication links themselves, including addressing, link health indications, redundancy changeover and the delay between an event and its appearance on screen. It is performed at commissioning and again after changes to equipment, firmware, networks or point lists.

Why it is done

A control system is only as dependable as its data. A breaker that shows closed on the screen when it is open, an alarm that never arrives, an analog value scaled wrongly or a command that reaches the wrong device can each lead an operator to a wrong and sometimes dangerous decision. Many of these faults come from simple causes: a point mapped to the wrong address, a swapped bit, an inverted contact, a wrong scaling factor, a mismatch in communication settings, or a gateway configured from an out-of-date point list. They cannot be found by testing the equipment alone, because every device can be healthy while the data path is wrong. Communication delay also matters. Data that arrives too late can be useless for alarms and automatic functions, and links that silently fail leave operators looking at stale values that look normal. Verification at commissioning prevents these surprises, and periodic checks catch the drift that follows software changes, replaced devices and degraded cabling.

The principle

The principle is end-to-end proof of a mapped signal. Every point in a SCADA system is defined by a chain of mappings: the physical or internal state in the device, its position in the device's communication register or object, its address on the link, its translation by the gateway into the master's protocol, and its presentation on the display with a name, a scale and an alarm treatment. A fault anywhere in the chain produces a wrong or missing value. Verification therefore changes something real, or simulates it faithfully at the source, and confirms the matching change at every later stage. For measurements, a known value is applied or read at the device and compared with the value displayed, accounting for scaling and units. For controls, the command is issued from the supervisory side and the real operation is confirmed at the equipment, including the check-before-operate or select steps that a protocol may require. For links, the principle is to prove that the system recognizes a failure: a disconnected cable or a stopped device should produce a visible communication alarm, and a redundant path should take over as designed.

How it is performed

The work begins with the point list and the communication design: addresses, protocols, scaling, alarm settings and the identity of every device on each link. The equipment is placed in a safe test condition, with controls locked out where an operation could affect a live process, and the people at the control center and in the field agree on how they will coordinate. At the field end, statuses are changed by operating the device or by simulating the input, and the corresponding indication, time stamp and alarm are confirmed at the master. Analog values are checked by applying a known quantity, or by comparing with a reference, and reading the scaled value on the display. Commands are issued from the control center one at a time, with the operation confirmed at the device and the feedback seen on the screen. For links, the physical media are inspected, communication parameters are compared with the design, and the diagnostic counters of the gateway or device are examined for errors and retries. Latency is measured by timing the interval between a change at the source and its appearance at the destination, using the device's time-stamped event record or a test set. Redundancy is tested by removing a path or a device and watching for the alarm and the changeover. Conditions that affect the result, such as network load and the polling arrangement, are noted.

What is recorded

The record shows, in general terms, which points, commands and links were exercised and what was observed at each end. It captures the identity of the devices, gateways and communication media involved, the protocol and addressing used, the result of each status, analog and control check, the measured delay of the links, and the behavior of alarms and redundancy. The test equipment and its calibration status are listed, along with any point corrections, setting changes or equipment replaced during the work and the issues left open. Keeping the point list reference with the results gives the next test a ready baseline for comparison.

How results are judged

Verification of a communication system is largely judged on whether each point and command behaves exactly as the design says, and this page gives no numerical limit. Several shapes of criteria apply. Each status must show the true state and each alarm must appear, with the right priority and text. Each analog value must agree with the field value once scaling and units are taken into account, and each command must operate the intended device and no other. Communication links must report their health honestly and recover as designed when a path is lost. Delay must be short enough for the function that depends on the data, as set by the project's design and the manufacturer, and not by a rule on this page. Agreement with the point list and drawings is the final check. The communications and system checks for electrical equipment are covered in ANSI/NETA ATS-2025 for acceptance work and ANSI/NETA MTS-2023 for maintenance work; consult your own licensed copies for the requirements and the project specifications for the performance targets.

Variations

At acceptance the entire point list is proven, usually point by point, because nothing has yet been shown to work. In maintenance the check focuses on points that matter most and on anything that has changed, such as replaced devices, new firmware, altered networks or added points. Equipment class changes the details. Protective relays and meters expose rich data over digital protocols, so configuration and mapping carry most of the risk. Older equipment may use contact outputs and analog transducers, where wiring and scaling are the usual faults. Renewable plants and storage add inverter and plant controller data, and utility or operator interfaces with their own performance and security requirements. Gateways that convert between protocols deserve extra care, because a conversion error affects many points at once. Communication security settings, time synchronization and event ordering are also verified where the system depends on them. In every case, the procedure follows the system design and the manufacturers' instructions.