IEC 61850: substation automation beyond hardwired interlocks

IEC 61850 replaced copper with Ethernet in the high-voltage substation. Where legacy schemes wired every interlock, trip, and indication as physical contacts between relays, 61850 relays publish those same signals as high-speed Ethernet messages and describe the entire substation in a machine-readable configuration language. The standard dominates new transmission and distribution substations worldwide, and its ideas — sampled measurement streams, peer-to-peer event messaging, formal system configuration — are spreading into DER plants, microgrids, and large industrial power systems.

GOOSE, sampled values, and MMS

Three communication services do most of the work. GOOSE (Generic Object Oriented Substation Event) multicasts state changes — breaker positions, interlock conditions, trip commands — directly over Ethernet with transfer times under 4 ms and continuous retransmission so subscribers detect communication loss. GOOSE replaces hardwired interlocking wiring: engineering becomes subscribing signals in software instead of pulling cable.

Sampled values (9-2) stream digitized CT/VT measurements from merging units to relays and meters at 4,800 samples per second, so protection, metering, and power-quality functions share one measurement source with synchronized timestamps. MMS (client/server) carries the supervisory layer — SCADA reads, control commands, settings, and reports — over TCP/IP to station computers and control centers, often alongside DNP3 or IEC 60870-5-104 gateways toward legacy masters.

SCL: the substation as a file

The Substation Configuration Language (SCL, part 6) is arguably the standard's most durable contribution. Every capable device ships an ICD file describing its logical nodes and data; system tools combine these into an SCD file describing the whole substation — single-line topology, all devices, all datasets, all GOOSE subscriptions. The SCD is the as-engineered truth: testing, documentation, and future extensions all derive from it.

Treat the SCD as a controlled engineering document from day one. Version it, keep it synchronized with the running devices (a relay replaced without updating its CID export is a latent misoperation), and require vendors to deliver validated ICD files before FAT — malformed SCL is the most common integration delay in 61850 projects, and it is always discovered late unless explicitly tested early.

Migrating from legacy schemes

Brownfield migrations usually proceed bay by bay: new 61850 relays in refurbished bays, GOOSE interlocking within the new sections, and hardwired or gateway interfaces at the boundary to untouched bays. Keep three risks on the plan. First, network engineering is now protection engineering — GOOSE timing depends on VLANs, priority tagging, and redundancy (PRP/HSR), so the Ethernet design needs the same rigor as the relay settings; the network topology guide and TSN primer cover the underlying mechanisms. Second, time synchronization underpins sampled values and sequence-of-events analysis — engineer PTP properly (see the time synchronization guide). Third, cybersecurity arrives with the network: engineer zones and conduits for the substation LAN from the start, because a flat protection network reachable from the corporate WAN is an incident waiting for a date.