Connecting a relay to SCADA is not just plugging in a network cable. Every signal must travel from the relay to the operator screen correctly named, correctly mapped, with proper quality and time. This article describes the method used in SCADA integration projects, independent of the protocol (IEC 61850, IEC 104, DNP3 or Modbus).
Step 1: Collect information and prepare the IO list
- List of devices with model, firmware version and supported protocols
- ICD files, Modbus register maps and DNP3 device profiles
- Operator requirements: signal names, alarm priorities, grouping and naming standard
- The final IO list: signal ID, description, type (single point, double point, measurement, command), scaling and unit, deadband, source address and destination address
Step 2: Communication architecture
- Relays to gateway/RTU: IEC 61850, or Modbus/IEC 103 for legacy equipment.
- Gateway to control centre: IEC 104 or DNP3, preferably two channels and two gateways (hot standby).
- Local HMI: directly via MMS or through a data server.
- Time server: GPS with NTP/IRIG-B/PTP output for all devices.
Step 3: Signal mapping
Every signal must be checked four times: the source in the IED, the data set or register, the gateway point and the SCADA identifier.
| Type | Mapping notes |
|---|---|
| Single point (SP) | Define polarity (positive/negative logic) and debounce time |
| Double point (DP) | Four states: intermediate, open, closed, invalid; check the bit order |
| Measurement | Unit, CT/VT ratio, scale, deadband and permitted range |
| Command | SBO or direct, timeout, interlocking and user logging |
| Counter / energy | Register type (accumulating/delta), reset and time stamping |
Step 4: Factory (FAT) and site (SAT) acceptance tests
Status and alarm signals
- Apply a real or simulated change at the relay's digital input and watch HMI and SCADA
- Check names, colours, alarm priorities and state meanings
- Check time stamps and event order (SOE) by triggering several inputs at once
- Check quality bits: when communication is lost the signal must become "invalid", not stay at its last value
Measurements
- Inject current and voltage at several points (for example 20 %, 50 %, 100 % and 120 % of nominal)
- Compare the SCADA value with the injected value; permitted error is typically below 0.5 % to 1 %
- Check the sign of power (P and Q) and the current direction
Commands
- Open/close commands in local and remote mode, with and without interlocks
- Rejection of commands in invalid conditions (for example breaker in test position) with a proper error message
- Confirmation of feedback after execution and the total duration
- Command tests on an energised breaker require a work permit and coordination with the operator.
Communication reliability
- Unplug and restore network cables, switch off the main gateway and check automatic changeover to the standby
- Recovery after an outage: automatic general interrogation (GI) and delivery of buffered events
- Check both channels to the control centre and that losing one does not affect operation
Step 5: Time synchronisation
A time difference of several seconds between relays makes event analysis impossible. All IEDs must take their time from one reference source (GPS). During testing, give one event to several relays at once and read the difference between time stamps; the target is 1 ms for SOE and 1 µs for SV.
Step 6: Handover documentation
- Final (as-built) IO list, network diagram and IP addressing plan
- Configuration files (SCD, CID, gateway project and SCADA database) with version numbers
- Signed test sheets for each signal
- Troubleshooting guide and a list of passwords and access rights (handed over securely)
Recurring points in projects
- Before testing, save the relays' original configuration; a re-download can alter protection settings.
- In Modbus, pay attention to zero- or one-based addressing and word order of floating-point values.
- Give momentary signals a suitable hold time so SCADA does not miss them.
- Identical, unambiguous naming in every layer makes fault finding quick.
Conclusion
Successful integration is the result of accurate documentation, sound configuration and signal-by-signal testing. ENP carries out this whole cycle, from IO list design to acceptance testing and documentation handover.