IEC 61850 Series Structure, Explained by Part
IEC 61850 is often described as a protocol, but it is really a layered series that separates an abstract data model from the concrete communications that carry it. Engineers integrating substation or DER equipment need to know which part defines the model, which defines the configuration language, and which maps the model onto MMS, GOOSE, or Sampled Values. This page maps that structure so the part numbers on an IED datasheet stop being noise. It assumes you already know what IEC 61850 broadly is.
IEC 61850 series structure in one line: The IEC 61850 series separates concerns by part: the 7-x parts define the abstract data model and services, including logical nodes and the abstract communication service interface, the 6 part defines the SCL configuration language, and the 8-x and 9-x parts map the abstract model onto real protocols, MMS and GOOSE in 8-1 and Sampled Values in 9-2. The abstraction is the point: one model, several transport mappings.
The Core Idea: Abstract Model, Concrete Mappings
The defining architectural choice in IEC 61850 is the split between an abstract information model and the specific communication mappings that carry it. The model, defined in the 7-x parts, describes data in terms of logical nodes and standardized data objects that mean the same thing regardless of vendor. The mappings, defined in the 8-x and 9-x parts, then bind that abstract model onto real network protocols. The site's overview of IEC 61850 for substation automation introduces this framework.
This separation is why 61850 is more than a protocol. You model an intelligent electronic device's data once, in vendor-neutral terms, and the same model is exposed over client-server MMS for SCADA reporting, over GOOSE for fast peer-to-peer protection signaling, and over Sampled Values for digitized measurements. Understanding the series means understanding which layer each part sits in.
Which Part Does What
The table below maps the parts most integrators encounter.
| Part | Layer | Defines |
|---|---|---|
| 61850-5 | Requirements | Communication requirements for functions |
| 61850-6 | Configuration | SCL, the substation configuration language |
| 61850-7-1 to 7-4 | Model | Data model, ACSI, common data classes, logical nodes |
| 61850-8-1 | Mapping | Mapping to MMS and GOOSE |
| 61850-9-2 | Mapping | Mapping to Sampled Values |
| 61850-90-x | Technical reports | Extensions such as wide-area and DER use |
The 7-x cluster is the heart of the model. 7-2 defines the abstract communication service interface, 7-3 the common data classes, and 7-4 the compatible logical node classes that the site covers under logical nodes and data model naming. Part 6 is the SCL configuration language that lets tools exchange a substation's full configuration in a standard file.
The mapping parts are where the abstract model meets the wire. Part 8-1 carries both client-server MMS and the fast GOOSE message, while part 9-2 carries Sampled Values for digitized instrument-transformer data. The same logical node modeled in the 7-x parts is what all three transports ultimately expose.
Reading a Datasheet Against the Structure
When an IED datasheet lists IEC 61850 support, the structure tells you what to check. Support for the model and MMS gives you SCADA-style reporting. Support for GOOSE, from part 8-1, gives you fast protection signaling between devices, which depends on the GOOSE retransmission and heartbeat timing the site covers separately. Support for Sampled Values, from 9-2, is what a process-bus architecture with merging units needs.
Reading the datasheet against the series therefore means asking which parts a device implements, because a device can model its data to the 7-x parts and expose it over MMS without supporting GOOSE or Sampled Values at all. Interoperability lives in the SCL files of part 6, which is why engineering tools exchange configuration as SCL rather than proprietary formats.
For the operations side, once these IEDs are feeding data upstream, a monitoring platform such as Merobix can trend the resulting measurements and status across sites. The 61850 structure governs how the substation devices talk to each other; the monitoring layer consumes the reported values so operators see them alongside the rest of the plant.
Frequently Asked Questions
Is IEC 61850 a protocol or a series of standards?
It is a multi-part series, not a single protocol. Its defining feature is the separation of an abstract data model, defined in the 7-x parts, from the concrete communication mappings that carry it, defined in the 8-x and 9-x parts. The same modeled data can be exposed over client-server MMS, over GOOSE for fast peer-to-peer signaling, and over Sampled Values for digitized measurements, which is why it is more accurately called a framework than a protocol.
Which IEC 61850 part defines GOOSE and Sampled Values?
Part 8-1 defines the mapping to MMS and to GOOSE, so GOOSE peer-to-peer messaging is specified there. Part 9-2 defines the mapping to Sampled Values, used to carry digitized instrument-transformer measurements over the process bus. Both are mappings of the same abstract data model defined in the 7-x parts, which is why a single logical node can be exposed over MMS, GOOSE, or Sampled Values depending on which mapping a device implements.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.