What Is IEC 61850?

Back to Blog

The Data Model, MMS, GOOSE, and Sampled Values

The most powerful idea in IEC 61850 is its standardized data model. Real substation functions - a circuit breaker, a protection relay, a measurement - are represented by predefined logical nodes with consistent naming, so a breaker looks the same regardless of vendor. System Configuration Language (SCL) files describe the whole substation in a portable, machine-readable form, which dramatically simplifies engineering and interoperability.

On the wire, IEC 61850 uses several services. MMS (Manufacturing Message Specification) over TCP/IP provides client/server communication for SCADA reads, controls, and reporting. GOOSE (Generic Object Oriented Substation Event) is a fast, publish/subscribe multicast service on the local Ethernet used for protection and interlocking, where trip signals must reach other devices in milliseconds. Sampled Values (SV) stream digitized current and voltage from merging units, replacing hard-wired analog signals in fully digital substations.

IEC 61850 Beyond the Substation

While born for substations, IEC 61850's model has expanded to hydro plants, wind and solar farms, and distributed energy resources, and it appears wherever oil and gas facilities own significant electrical infrastructure - large compressor drives, power generation, and switchgear at processing plants. SCADA and energy-management systems act as MMS clients reading the standardized data model from intelligent electronic devices (IEDs).

Integrating IEC 61850 into a broader monitoring platform is typically done at the MMS client level or through a gateway that maps the 61850 model to another protocol. GOOSE and Sampled Values stay on the local substation network for latency reasons, while curated measurements and status are forwarded upward. An operator can consolidate substation and process data by gatewaying IEC 61850 values to a routable protocol that a cloud SCADA ingests, giving one historian and dashboard across electrical and process assets.

How to Read an IEC 61850 Object Reference

Every value in a 61850 device is addressed by a path with a fixed grammar: LogicalDevice/LogicalNode.DataObject.DataAttribute, plus a functional constraint that selects the attribute's role. Take the symbolic reference Feeder1/Q1XCBR1.Pos.stVal. Feeder1 is the logical device, a container the vendor uses to group functions. Q1XCBR1 is an instance of the XCBR class - the standardized logical node for a circuit breaker - with a prefix and instance number that let one relay host several breakers. Pos is the data object for switch position, and stVal is the attribute carrying the actual open or closed state, sitting next to q (quality) and t (timestamp).

Once you can parse that one reference, you can parse any conforming device from any manufacturer, which is the practical payoff of the standardized model. The same grammar covers measurements (a power value lives under an MMXU logical node), controls (Pos also exposes the structures used by select-before-operate commands), and settings. A useful habit when a value looks wrong: read the q attribute beside it before suspecting the wiring, because the device may already be telling you the measurement is invalid, substituted, or produced in test mode.

SCL File Types and the Engineering Workflow

SCL is one XML schema wearing several hats, distinguished by file extension, and knowing which file does what saves real confusion on a project:

File	Role
ICD	Device capabilities, as exported by the vendor tool
SSD	System specification: single line diagram and required functions
SCD	The fully engineered substation - all IEDs, datasets, and communications
CID	The configuration one specific device is told to run
SED	Exchange file between separately engineered projects

The intended flow runs bottom-up and top-down at once: vendor tools export ICDs describing what each device can do, a system configurator combines them with the SSD into the SCD, and each vendor tool then imports the SCD to generate the CID actually downloaded to its device. In practice the friction points are tool-to-tool import quirks and mixed-edition fleets, so treat the SCD as the master engineering artifact, keep it under version control, and update it whenever a device configuration changes - reconstructing a lost SCD from scattered device files is slow, unpleasant work.

Station Bus, Process Bus, and Redundant Networks

A digital substation usually has two network tiers. The station bus carries MMS client/server traffic and GOOSE between protection relays, bay controllers, and the gateway. The process bus carries Sampled Values and trip GOOSE between merging units, breaker IEDs, and protection relays. Sampled Values only make sense if every publisher shares a common clock, so precision time distribution - IEEE 1588 PTP profiles for power systems - becomes part of the network design, along with VLANs and priority tagging to keep time-critical traffic segregated from bulk traffic.

Because protection depends on the LAN, redundancy is engineered in rather than bolted on. IEC 62439-3 defines the two schemes used in substations: PRP, where every frame is duplicated across two fully independent LANs and the receiver discards the second copy, and HSR, where duplicates circulate both directions around a ring. Both deliver frames through a single network failure without a switchover pause, which spanning-tree style recovery cannot promise. Which one fits a given substation is a topology and cost decision made per project.

Commissioning and Testing Notes

The standard builds test facilities into the model rather than leaving you to lift wires. Devices expose mode and behaviour controls so a relay can be placed in a test state where its outputs are flagged as such, and GOOSE and Sampled Values frames carry test and simulation flags that subscribers evaluate. Used properly, this lets you inject and observe without disconnecting live trip circuits - but any testing on in-service protection is planned with the responsible protection engineer and follows site procedures, without exception.

The subscription side deserves equal attention. A GOOSE subscriber checks the configuration revision of what it receives, so an innocent-looking change to a publisher's dataset can silently invalidate every subscriber until they are re-engineered. After any SCD change, verify subscription health from each device's diagnostics before declaring the work done. For the SCADA direction, resist polling the entire model: decide which points operations actually needs, then build focused datasets and report control blocks around them, which keeps bandwidth, databases, and alarm lists sane.

Frequently Asked Questions

Sources & Further Reading

Primary references from the standards bodies and regulators that define this topic:

• IEC Webstore (International Electrotechnical Commission standards) - IEC
• IEEE Standards Association - IEEE