IEC 61850 vs IEC 60870: Why Your Protocol Choice is Killing Your Commissioning Timeline

GridHacker Team •
Hero image for IEC 61850 vs IEC 60870: Why Your Protocol Choice is Killing Your Commissioning Timeline

The Problem Nobody Talks About

We have all been there. You are standing in a substation, three days behind schedule, staring at a laptop screen while a relay refuses to talk to the SCADA gateway. The vendor swears the point list is correct, the network switch is configured for VLAN tagging, and yet, the data remains stubbornly offline.

The industry loves to sell the “seamless integration” of modern protocols, but the reality for those of us on the ground is a persistent, low-level war between legacy serial-based paradigms and the object-oriented, Ethernet-centric world of IEC 61850. If you are still treating IEC 61850 like it’s just a faster version of IEC 60870-5-104, you are not just missing the point—you are setting yourself up for a failure that will manifest as a catastrophic delay during site acceptance testing.

Technical Deep-Dive

To understand the friction, we have to look at the architectural intent. IEC 60870-5-104 (the Ethernet-wrapped version of the -101 serial protocol) is fundamentally a telecontrol protocol. It is designed to move data from a point A to a point B. It is static, address-based, and relies on a rigid, pre-defined point list. You define an address, you map it to a register, and if the register changes, the RTU sends an update. It is simple, predictable, and remarkably easy to troubleshoot because you can trace the packets and see exactly what is happening on the wire.

IEC 61850, conversely, is an object-oriented modeling standard. It does not just send data; it describes the substation. Through the Substation Configuration Language (SCL), it defines the semantics of the equipment. A circuit breaker is not just a binary status bit; it is a logical node (XCBR) containing position status, control interfaces, and health monitoring.

The primary difference lies in the abstraction layer. IEC 60870 operates at the data link and application layers with minimal metadata. IEC 61850 operates on an abstract communication service interface (ACSI), which maps to different stacks depending on the task. For high-speed protection, we use GOOSE (Generic Object Oriented Substation Event) over the Ethernet layer directly, bypassing the TCP/IP stack to keep latency within the sub-millisecond requirements for protection tripping. For SCADA, we use MMS (Manufacturing Message Specification). If you are confused by the iec-61850-vs-iec-104 distinction, remember that one is a message-passing protocol, and the other is a complete information model.

Implementation Guide

When moving from a legacy 60870 environment to a 61850-based architecture, stop thinking in terms of “mapping points.” Start thinking in terms of “modeling functions.”

  1. The SCL Workflow: You must start with the System Specification Description (SSD). If you don’t have a clear SCL file, you don’t have a project. The configuration process starts at the design phase, not the commissioning phase.
  2. VLAN and Traffic Management: Because IEC 61850 relies heavily on multicast traffic (GOOSE and Sampled Values), your network infrastructure is now a protection component. You cannot simply plug these devices into a generic unmanaged switch. You must implement IGMP snooping and properly segment your traffic to ensure that a broadcast storm from a non-critical device doesn’t trip your primary protection relays.
  3. MMS Client Configuration: When configuring your SCADA gateway to poll an IED (Intelligent Electronic Device), you are not just polling registers. You are browsing the object model. Ensure your gateway software is fully compliant with the edition of IEC 61850 the relay is running. Mixing Edition 1 and Edition 2 devices in the same Substation Configuration Language file is a recipe for silent data mapping failures.

Failure Modes and How to Avoid Them

I once worked on a site where a project manager insisted on using a “simplified” configuration tool to map IEC 61850 signals to an older SCADA system. The tool essentially stripped the semantic metadata from the IEC 61850 objects to force them into a legacy register-based structure.

Everything worked fine during the initial loop checks. However, during a bus fault, the GOOSE messaging traffic spiked, and the network switch—which had not been configured with proper priority queuing (Quality of Service)—prioritized the SCADA polling traffic over the GOOSE protection messages. The result? A relay failed to trip because its GOOSE message was queued behind a low-priority SCADA heartbeat packet.

The lesson here is simple: never treat substation networking as “IT stuff.” If your SCADA polling interval is too aggressive, you will choke the very devices that are supposed to keep the grid stable. Always calculate the bandwidth requirements of your GOOSE traffic and ensure your switches support IEEE 802.1p/Q for VLAN tagging and priority queuing.

When NOT to Use This Approach

Do not force IEC 61850 into a retrofit project where the existing IEDs and communication infrastructure are strictly serial. If you are dealing with a legacy RTU that does not support MMS, attempting to bridge IEC 61850 to 60870-5-104 using a protocol converter often results in a “least common denominator” scenario. You lose the object-oriented benefits of 61850 while introducing a new, complex point of failure in the gateway.

If your scope is limited to simple telemetry—monitoring a few analog values and status points—IEC 60870-5-104 is still the more robust, easier-to-maintain choice. It is battle-tested, requires significantly less engineering overhead to configure, and is far less sensitive to network misconfigurations. Use 61850 when you need distributed intelligence, high-speed interlocking, or peer-to-peer communication between IEDs. If you don’t need those features, you are just buying yourself a more expensive, more complicated headache.

Conclusion

The transition from IEC 60870 to IEC 61850 is not a migration; it is a paradigm shift from telecontrol to substation automation. It requires a fundamental change in how you approach commissioning, network design, and troubleshooting. If you approach 61850 with the mindset of a 60870 engineer—focusing only on the data points and ignoring the model—you will inevitably fail when the network gets congested or the configuration files drift. Respect the complexity of the standard, invest in proper network hardware, and always, always verify the SCL file before you touch the physical cabling.

*This article is intended for informational purposes only for experienced electrical engineers and equipment procurement professionals. All specific technical parameters, protocol compliance thresholds, and performance specifications mentioned must be independently verified against the applicable standard revision, equipment datasheet, and site-specific engineering studies before any design, procurement, or operational decision is made. GridHacker and its authors accept no liability for misapplication of the content herein.*

Hero image: An electric vehicle charging station with a black plug connected to a car.. Generated via GridHacker Engine.

Related Articles