IEC 61850 Substation Automation: GOOSE, MMS, Sampled Values

IEC 61850 Substation Automation: GOOSE, MMS, Sampled Values

IEC 61850 has become the reference architecture for digital substations because it replaces hardwired, point-to-point integration with an object-oriented, interoperable communication model. For SCADA engineers, panel builders, and protection specialists, the practical challenge is not simply “supporting IEC 61850,” but designing networks, IEDs, engineering tools, and cybersecurity controls so that protection, control, and monitoring remain deterministic, testable, and maintainable. The three core communication services most often encountered are GOOSE for fast event exchange, MMS for client-server supervision and control, and Sampled Values for digitized measurement streams. Understanding their timing, bandwidth, redundancy, and compliance implications is essential for safe deployment in modern substations.

1. IEC 61850 architecture in the substation

IEC 61850 is more than a protocol; it is a layered information and communication model defined primarily in IEC 61850-7-1, 7-2, 7-3, 7-4, and 8-1. In practice, it standardizes:

• Data models for logical nodes, data objects, and data attributes.
• Communication services such as GOOSE, MMS, and Sampled Values.
• Engineering configuration via SCL files, especially ICD, CID, SCD, and SSD.
• Interoperability between protection relays, bay controllers, merging units, gateways, and SCADA front ends.

From a systems perspective, the architecture is typically divided into process level, bay level, and station level. The process level handles CT/VT interface and digitization, the bay level hosts protection and control IEDs, and the station level aggregates information for SCADA/HMI and remote dispatch. IEC 61850-6 defines the Substation Configuration Language (SCL), which is critical because engineering quality depends as much on configuration discipline as on network hardware selection.

For European projects, IEC 61850 is commonly used alongside IEC 60255 for protection relays, IEC 62443 for industrial cybersecurity, and IEC 60529 for enclosure ingress protection. If the substation is part of a machinery or process installation, the overall integration must still align with the EU Machinery Directive/Regulation context and the applicable CE conformity obligations, even though the substation automation system itself is usually governed by electrical and utility standards rather than machinery safety alone.

2. GOOSE: high-speed event distribution

Generic Object Oriented Substation Event, or GOOSE, is a publisher-subscriber service designed for very fast exchange of binary or structured status information over Ethernet. It is widely used for interlocking, trip, blocking, breaker failure, synchrocheck, and scheme logic between IEDs.

GOOSE is defined in IEC 61850-8-1 and uses Layer 2 Ethernet multicast, which means it does not rely on IP routing. This is a deliberate design choice for speed and determinism. The message is retransmitted multiple times with a decreasing repetition interval so that reception is highly reliable even on noisy networks. In practice, GOOSE is used for protection functions where end-to-end transfer times must be in the order of milliseconds.

Key design points:

• Use VLAN tagging and priority tagging per IEEE 802.1Q to prioritize protection traffic.
• Keep GOOSE domains localized to the substation network; do not route them across wide-area networks.
• Engineer redundancy carefully using PRP or HSR where required by availability targets.
• Test failover behavior, subscription mapping, and sequence number handling during FAT/SAT.

IEC 61850-5 provides communication requirements and performance classes. While actual performance depends on vendor implementation and network design, protection-related GOOSE applications are typically expected to meet stringent transfer times. For example, trip and interlocking applications often target sub-4 ms or similarly tight budgets depending on the utility’s protection philosophy and the specific function.

3. MMS: station-level supervision and control

Manufacturing Message Specification, or MMS, is the client-server service used for supervisory control, reporting, logging, file transfer, and configuration access. In IEC 61850, MMS is specified in IEC 61850-8-1 and is commonly used by SCADA masters, gateways, engineering workstations, and HMI systems.

MMS is the communication backbone for station-level visibility. Unlike GOOSE, it is not intended for ultra-fast protection tripping. Instead, it supports:

• Reading measured values and status points.
• Writing control commands such as open/close.
• Buffered and unbuffered reports.
• Event logs and disturbance file retrieval.
• Association management and data set access.

IEC 61850-7-2 defines the Abstract Communication Service Interface (ACSI), which MMS maps into concrete services. For SCADA integration, the practical engineering issues are connection limits, report buffering, time synchronization, access control, and how the gateway or master station handles model-driven data rather than flat point lists.

In a European compliance context, MMS-based remote access should be designed with IEC 62443 concepts such as zones and conduits, least privilege, secure remote maintenance, and strong authentication. With NIS2-driven critical infrastructure expectations, asset owners should also document logging, patching, incident handling, and supplier access controls. IEC 62351 is the key family for security of power system communications; it is especially relevant when assessing authentication, message integrity, and role-based access for IEC 61850 deployments.

4. Sampled Values: digitized CT/VT streams

Sampled Values, often abbreviated SV, carry digitized current and voltage measurements from merging units to protection and control IEDs. The standard is defined in IEC 61850-9-2 and further refined by IEC 61869-9 for digital interface requirements for instrument transformers. In modern systems, SV is fundamental to process bus architectures.

SV replaces conventional copper secondary wiring with Ethernet multicast streams. Instead of analog CT/VT loops, the merging unit samples the electrical waveform, converts it to digital values, and transmits the samples at a fixed rate. Protection relays subscribe to these streams and reconstruct the waveform for protection algorithms.

Engineering considerations include:

• Sampling rate and dataset size.
• Network bandwidth and latency.
• Time synchronization accuracy, typically via IEEE 1588 PTP or equivalent substation timing architecture.
• Interoperability between merging units and relays, especially around implementation agreements for 9-2LE profiles.

SV is bandwidth-intensive compared with GOOSE, and it is more sensitive to packet loss, jitter, and synchronization quality. For that reason, process bus design must be validated carefully, including switch performance, multicast filtering, redundancy scheme, and end-device buffering behavior.

5. Worked example: sizing a process bus for one feeder bay

Consider a feeder bay with one merging unit providing three-phase current and voltage samples to two protection IEDs. Assume the following:

• Sampling rate: 4,800 samples per second per phase group.
• Three-phase currents and voltages are packed into one SV frame.
• Each SV frame payload plus Ethernet overhead totals 256 bytes on the wire after VLAN tagging and protocol headers.
• Each merging unit transmits one stream to the network.
• Two protection relays subscribe to the same stream.

The raw bandwidth per stream is:

$$B = 256 \times 8 \times 4800$$

$$B = 9{,}830{,}400 \text{ bit/s} \approx 9.83 \text{ Mb/s}$$

If the stream is multicast, the network carries one copy per link segment, not one copy per subscriber, so the switching fabric sees approximately 9.83 Mb/s on each relevant egress port, plus overhead from other traffic. If there are 8 similar bays on the same station process bus, the aggregate SV load is:

$$B_{total} = 8 \times 9.83 \approx 78.6 \text{ Mb/s}$$

Now add GOOSE traffic. Suppose each bay generates 20 GOOSE events per second during normal operation, with an average frame size of 150 bytes and a retransmission burst factor of 4. The approximate average bandwidth is:

$$B_{GOOSE} = 20 \times 4 \times 150 \times 8$$

$$B_{GOOSE} = 96{,}000 \text{ bit/s} = 0.096 \text{ Mb/s per bay}$$

Across 8 bays:

$$0.096 \times 8 = 0.768 \text{ Mb/s}$$

So the process bus load is dominated by SV, not GOOSE. Even with conservative allowances for MMS, engineering access, and redundancy traffic, the total remains comfortably below 100 Mb/s. However, the design should still use 1 GbE infrastructure to preserve headroom, reduce queuing delay, and support future expansion. This is a practical example of why “it fits on paper” is not enough; deterministic behavior depends on low utilization, proper QoS, and clean multicast design.

6. Comparison matrix: GOOSE vs MMS vs Sampled Values

Service	Primary use	Communication model	Typical latency need	Network layer	Engineering risk
GOOSE	Trip, interlocking, blocking, status exchange	Publisher-subscriber multicast	Very low, milliseconds	Ethernet Layer 2	Misconfigured VLAN/priority, subscription mismatch, redundancy errors
MMS	SCADA control, reporting, logs, configuration	Client-server	Moderate, seconds acceptable	TCP/IP	Access control, point mapping, report overload, cybersecurity exposure
Sampled Values	Digitized CT/VT measurements	Publisher-subscriber multicast	Deterministic, cyclic	Ethernet Layer 2	Bandwidth, synchronization, packet loss, interoperability

7. Engineering and compliance considerations

IEC 61850 engineering quality depends on disciplined documentation and testing. IEC 61850-6 requires consistent SCL-based configuration management, while IEC 61850-10 addresses conformance testing. For protection and automation projects, the following clauses and standards are especially relevant:

• IEC 61850-5: communication requirements and performance classes.
• IEC 61850-6: SCL engineering and system configuration.
• IEC 61850-7-2 and 7-4: services and logical node models.
• IEC 61850-8-1: MMS and GOOSE mapping.
• IEC 61850-9-2: sampled values mapping.
• IEC 61869-9: digital interface for instrument transformers.
• IEC 62351 series: cybersecurity for power system communications.
• IEC 62443 series: industrial automation and control system security.
• IEEE 1588: precision time synchronization for process bus timing.

For European projects, compliance documentation should also address EMC, low-voltage equipment safety, panel wiring practices, and segregation of communication and power circuits. In panel design, the practical implications include shield termination, grounding strategy, switch power supply redundancy, and maintaining cable separation to reduce EMI-induced packet errors. If the system forms part of a safety-related machine or process interface, ISO 13849 or IEC 62061 may also be relevant, but they do not replace IEC 61850 engineering requirements.

Cybersecurity deserves special attention because IEC 61850 networks are increasingly connected to enterprise and remote access environments. Under IEC 62443, apply zone/conduit segmentation, role-based access, secure engineering workstations, controlled removable media, and logging of MMS sessions. Where applicable, align with the organization’s NIS2 obligations for incident response and supply-chain risk management.

8. Practical design rules for SCADA and substation engineers

• Use GOOSE only for fast peer-to-peer events, not for general telemetry.
• Use MMS for SCADA polling, reports, commands, and file transfer.
• Use SV only where the process bus architecture is justified by lifecycle cost, performance, and maintainability.
• Engineer time synchronization before commissioning protection logic.
• Validate multicast filtering and storm control on switches.
• Document all datasets, subscriptions, and control blocks in SCL.
• Perform end-to-end FAT with realistic traffic load, not just point-to-point bench tests.
• Test redundancy failover under live traffic, including PRP/HSR behavior if used.

Closing: common engineering mistakes and how to avoid them

The most common IEC 61850 mistakes are treating GOOSE like ordinary Ethernet traffic, overloading the process bus with unnecessary SV streams, underestimating time synchronization requirements, and assuming that vendor interoperability is automatic. Another recurring error is poor SCL governance: if datasets, control blocks, and logical node mappings are not controlled rigorously, the system becomes difficult to test and impossible to maintain. To avoid these failures, design with IEC 61850-5 performance targets in mind, configure and review SCL files systematically under IEC 61850-6, verify conformance under IEC 61850-10, and apply IEC 62351 and IEC 62443 cybersecurity controls from the start rather than as a retrofit. In short, a successful digital substation is not defined by how many Ethernet ports it has, but by how well its communication services are engineered, validated, secured, and documented.