What is IEC 61850?

IEC 61850 is an IEC (International Electrotechnical Commission) standard published in 2003 and revised in 2013 that defines a complete communication architecture for electrical substation automation — from the fast protection messaging that trips a breaker in under 4 milliseconds, to the SCADA data access that lets an operator read current transformer measurements, to the XML configuration files that describe what capabilities each device has. It was designed to replace the dozens of proprietary protocols (SEL, GE, ABB, Siemens each had their own) that utilities were forced to implement separately for each vendor's protection and automation equipment.

The standard is significant for two reasons beyond its technical content. First, it is the first power-sector communication standard to be built around an object model rather than a register map — IEDs are described in terms of what they do (protect a transformer, measure current on a feeder) rather than what address their data lives at. Second, it has been widely adopted globally: virtually every major IED vendor — SEL, GE, ABB, Siemens, Schneider, Mitsubishi, Hitachi — now ships IEC 61850-compliant devices, and NERC CIP, IEEE, and grid operators worldwide reference or require it for new substation designs.

IEC 61850 is becoming the grid communication standard for the energy transition. As renewable energy generation (wind, solar, battery storage) connects to the grid at an accelerating pace, the number of grid edge assets that need to communicate with utility control systems is growing rapidly. IEC 61850 is the protocol being specified for smart inverters, wind turbine controllers, battery management systems, and grid-tied storage — not just traditional substations. Engineers working in the renewables and smart grid space will encounter IEC 61850 increasingly, even if they have never worked in a traditional substation environment.

Where IEC 61850 is used

🏭

Electrical Substations

The original and primary application — transmission and distribution substations communicating protection relays, bay controllers, merging units, and RTUs on a substation Ethernet LAN and to the utility SCADA over WAN.

🌬️

Wind Farms

IEC 61850 is increasingly specified for wind turbine controllers and farm-level communication with grid operators. IEC 61400-25 (wind power) is built on IEC 61850's data model.

🔋

Battery Energy Storage (BESS)

Grid-scale battery systems use IEC 61850 for communication with grid operators and energy management systems. Increasingly required in interconnection agreements for storage assets.

☀️

Solar Generation

Smart inverter communication standards increasingly reference IEC 61850's object model. Utility-scale solar installations use it for protection and SCADA connectivity alongside DNP3.

⚡

Distribution Automation

Feeder automation, self-healing grid schemes, and automated fault isolation and restoration (FLISR) in distribution networks use IEC 61850 GOOSE messaging between field devices for fast, coordinated switching.

🏗️

Industrial Substations

Large industrial facilities (refineries, smelters, data centers, large campuses) with significant electrical infrastructure increasingly specify IEC 61850 for their internal substation automation alongside traditional OT connectivity.

The IEC 61850 communication services

IEC 61850 is not a single protocol — it is a family of communication services, each optimized for a different aspect of substation operation. Understanding the four main services clarifies how the standard works and why it requires a different approach than simpler protocols like Modbus or DNP3.

GOOSE

GOOSE — Generic Object Oriented Substation Event

Ultra-fast protection and interlocking — Ethernet multicast, sub-4ms end-to-end

Transport: Ethernet Layer 2 multicast (no IP, no TCP)

Latency: <4ms (Class P1), <3ms (Class P2)

Port: No port — EtherType 0x88B8

GOOSE is the fastest IEC 61850 service — the one used for protection trips, interlocking signals, and real-time status exchange between IEDs within a substation. It operates directly at Ethernet Layer 2, bypassing TCP/IP entirely to achieve sub-4ms end-to-end latency. A protection relay detecting an overcurrent condition publishes a GOOSE message that every subscribed IED on the Ethernet LAN receives simultaneously — a transformer differential relay can trip a breaker, signal a lockout relay, and notify a bay controller in under 4 milliseconds.

GOOSE uses a retransmission mechanism for reliability: the message is initially sent at fast intervals (≈2ms) then backs off to slower intervals as long as the state remains unchanged. Any subscriber that misses the first transmission will receive the next one. When the state changes again, the fast retransmission cycle resumes. This eliminates the need for a TCP acknowledgment layer while still providing high confidence that the message was delivered.

GOOSE is purely intra-substation. It requires a single Ethernet LAN with no routers between publisher and subscriber (Layer 2 multicast does not cross routers). It is not used for SCADA communication to an operations center — that is handled by MMS over IP.

MMS

MMS — Manufacturing Message Specification

SCADA data access, reporting, and control — TCP/IP, routable over WAN

Transport: TCP/IP (ISO-on-TCP, RFC 1006)

Port: TCP 102

Use: SCADA reads/writes, reports, logs, time sync

MMS (ISO 9506) is the IEC 61850 service for SCADA communication — reading measurements, writing setpoints, receiving reports, and retrieving logs from IEDs. It runs over TCP/IP and is therefore routable, making it the mechanism used by utility control centers to communicate with substations over WAN links, and by third-party OPC servers like TOP Server to read IED data.

IEC 61850 maps its data model onto MMS using the concept of buffered and unbuffered reports. An IED can be configured to send reports to a SCADA client when data values change, when integrity intervals expire, or when events occur. Buffered report control blocks (BRCBs) store reports during communication interruptions and deliver them when the connection is restored — similar in concept to DNP3's event buffering, but defined within the standard's object model. Unbuffered report control blocks (URCBs) discard reports during disconnections and resume with current values on reconnection.

For OPC connectivity, an OPC server with an IEC 61850 MMS client driver reads logical node data from IEDs using MMS object addressing and exposes it as named OPC tags. TOP Server's IEC 61850 driver uses this mechanism.

Sampled Values (SV)

Sampled Values — IEC 61850-9-2

High-frequency current and voltage waveform data from merging units

Transport: Ethernet Layer 2 multicast

Rate: 80 or 256 samples per power cycle (4000 or 12,800 samples/sec at 50Hz)

Source: Merging units (interface between instrument transformers and IEDs)

Sampled Values is the IEC 61850 service for transmitting digitized current and voltage waveform samples from merging units to protection relays and measurement devices. A merging unit connects to current and voltage transformers, digitizes the instantaneous waveform at 80 or 256 samples per power cycle, and publishes the sample stream as a continuous Ethernet multicast. Protection relays subscribe to this stream and perform their protection calculations on the digitized waveform data rather than on analog inputs from the transformers directly.

Sampled Values is relevant to engineers working on digital substation designs, where the traditional analog CT/VT wiring to each protection relay is replaced by a single fiber or Ethernet run from the merging unit to the IED bay. It is less commonly encountered in conventional substation retrofits, where analog CT/VT connections remain in place. Not all OPC servers handle Sampled Values — it is a specialized real-time streaming service rather than a data access protocol.

SCL

SCL — Substation Configuration Language

XML-based device and system configuration — the "GSD file" of IEC 61850

Format: XML

File types: ICD, SSD, SCD, CID

Purpose: Describe IED capabilities and configure the complete substation

SCL is the configuration language that makes IEC 61850 self-describing. Every IED publishes an ICD file (IED Capability Description) that describes in XML all of the logical nodes, data objects, and services the device supports. A system engineer uses a configuration tool to compose the ICD files from all devices into a complete SCD file (Substation Configuration Description) that defines the complete substation automation system — which IEDs publish which GOOSE messages, which SCADA client subscribes to which reports, and how the logical nodes in each IED map to the physical substation equipment.

For OPC server configuration, SCL/ICD files are the starting point. TOP Server's IEC 61850 driver can import an IED's ICD file to automatically discover all available logical nodes and data objects, rather than requiring manual address entry. This significantly reduces configuration time for substations with many IEDs.

IEC 61850-90-2 / R2

IEC 61850 over WAN (Teleprotection & R2)

Extending IEC 61850 communication beyond the substation LAN

Scope: Technical report for WAN communication

Relevance: Control center to substation, ICCP bridging

The core IEC 61850 standard was designed for substation-internal communication. IEC 61850-90-2 is a technical report that addresses how IEC 61850 communication extends to the control center over WAN. MMS over TCP/IP already handles this for SCADA data access. The 90-2 report covers additional considerations including firewalls, routing, latency management, and the interface between IEC 61850 substations and legacy ICCP (Inter-Control Center Communications Protocol) used for energy trading and grid coordination.

For engineers integrating IEC 61850 substations into a broader SCADA or EMS infrastructure, the MMS-over-TCP/IP path — with an OPC server acting as the MMS client — remains the primary integration point and does not require understanding 90-2 in detail for most deployment scenarios.

The IEC 61850 data model: logical nodes

IEC 61850's most important innovation over DNP3 and Modbus is its self-describing data model. Rather than addressing data by register number or point number, IEC 61850 organizes every piece of data in an IED into a hierarchy of Logical Devices → Logical Nodes → Data Objects → Data Attributes.

Logical nodes are standardized functional blocks defined by the standard. Each logical node has a two-to-four letter prefix that identifies its function. This standardization means that a protection relay from SEL and a protection relay from ABB both use the same logical node names for the same functions — a SCADA engineer does not need to learn two different vendor-specific data structures to understand what data they represent.

Logical Node	Function name	What it represents
XCBR	Circuit Breaker	Breaker position (open/closed), trip/close commands, operating count, spring charge status
XSWI	Switch / Disconnector	Isolator and earthing switch position, operation commands
MMXU	Measurement	Voltage, current, power, power factor, frequency — the standard metering measurements for a circuit
PDIF	Differential Protection	Differential protection function — operate signal, restrain signal, fault quantities
PTOC	Time Overcurrent Protection	Overcurrent protection operate and pickup signals, settings, fault current
PDIS	Distance Protection	Distance protection zones, reach settings, operate signals
PSCH	Protection Scheme Communication	Communication-assisted protection — permissive overreaching, blocking, direct transfer trip
RBRF	Breaker Failure Protection	Breaker failure detection and initiation signals
GAPC	Generic Automatic Process Control	Generic purpose — used for schemes not covered by specific LN classes
LPHD	Physical Device Information	Power supply status, health, nameplate information for the physical IED
LLN0	Logical Node Zero	Logical device-level information — mode, health, GOOSE and report settings

A full IED address in IEC 61850 looks like: IED_SEL351/Bay1PROT/PTOC1.Op.general — reading from right to left: the general attribute of the Op (Operate) data object within logical node PTOC1 (first time overcurrent protection instance) in logical device Bay1PROT on IED IED_SEL351. Anyone who knows IEC 61850's logical node definitions immediately understands what this value represents, regardless of who manufactured the IED.

IEC 61850 vs. DNP3

IEC 61850 and DNP3 are the two dominant protocols for utility substation communication, and they are often found in the same substation — DNP3 for legacy devices and wide-area SCADA communication, IEC 61850 for modern IEDs and intra-substation protection. Understanding the distinction helps engineers allocate each protocol to its appropriate role.

Feature	IEC 61850	DNP3
Primary design goal	Substation automation interoperability — one standard for all vendors	SCADA master-to-RTU communication over WAN links
Data model	Rich semantic model — logical nodes with standardized function names	Typed object model — binary, analog, counter groups with class/variation
Fast protection messaging	Yes — GOOSE, sub-4ms, Layer 2	No — polling latency too high for protection
WAN/routable communication	Yes — MMS over TCP/IP	Yes — DNP3/TCP
Event buffering	Yes — Buffered Report Control Blocks (BRCB)	Yes — event class model with device buffer
Self-describing (no external tag list)	Yes — ICD/SCL files describe all data	No — requires separate point list configuration
North American installed base	Growing — new substations; greenfield renewable energy	Dominant — existing utility infrastructure
Typical OPC server access	MMS client driver — TOP Server IEC 61850	DNP3 master driver — TOP Server DNP3

Software Toolbox products for IEC 61850

IEC 61850 MMS client

TOP Server — IEC 61850 driver

TOP Server's IEC 61850 driver acts as an MMS client, connecting to IEDs in substations and renewable energy sites over TCP port 102 using the IEC 61850 MMS service. It reads logical node data objects and attributes by their IEC 61850 address, supports import of SCL/ICD files for automatic data discovery, and exposes all IED data to OPC DA and OPC UA clients. Buffered and unbuffered report control blocks can be configured to receive data-change events from IEDs rather than polling. The driver supports the common logical node classes — XCBR, MMXU, PTOC, PDIF — for typical utility and substation applications, alongside Siemens SIPROTEC, SEL, GE, ABB, and other major IED families that implement the standard.

OPC output to SCADA/Historian

TOP Server — OPC DA / OPC UA server

Once TOP Server's IEC 61850 driver has established MMS connections to IEDs, all logical node data is available to any OPC DA or OPC UA client — utility SCADA systems, process historians, energy management systems, and analytics platforms. Multiple OPC clients can subscribe to the same IED data simultaneously without creating additional MMS sessions to each device. This is the standard architecture for integrating IEC 61850 substations and renewable energy sites into broader utility or industrial SCADA infrastructure.

Edge + IIoT for grid assets

N3uron + TOP Server

For renewable energy sites and grid-connected assets building modern IIoT architectures — feeding operational data to cloud SCADA, energy trading platforms, or AI-driven optimization systems — N3uron subscribes to TOP Server's OPC UA output, contextualizes IED logical node data into ISA-95-structured topic paths, and publishes to an MQTT broker or cloud historian via Sparkplug B. This bridges IEC 61850 substation data from a technology designed for proprietary utility SCADA systems into modern cloud and AI-ready data platforms, without changing the underlying IED configuration or protection scheme.

Frequently asked questions

Does IEC 61850 replace DNP3 in substations?+−

Not immediately, and not universally. The practical picture in most North American utilities is a coexistence: legacy RTUs, older IEDs, and wide-area SCADA communication continue to use DNP3 because the installed base is enormous and replacing working infrastructure is expensive. New IED procurement from the major relay manufacturers (SEL, GE, ABB, Siemens, Schneider) typically includes IEC 61850 capability alongside DNP3 on the same hardware — the customer configures which protocol to use for which communication path.

In new substation builds and renewable energy interconnections, IEC 61850 is increasingly specified as the primary or sole intra-substation protocol, with DNP3 or ICCP used for the WAN link to the control center. Substations designed after approximately 2015 in most jurisdictions are likely to have IEC 61850 for IED-to-IED communication even if the SCADA WAN still uses DNP3. In Europe and internationally, IEC 61850 adoption in new substations is nearly universal; in North America, adoption is strong and growing.

Can GOOSE messages be read by an OPC server?+−

GOOSE operates at Ethernet Layer 2 — it does not use TCP/IP and therefore cannot be received by a standard network application. GOOSE is intended for IED-to-IED communication within the substation LAN for protection and interlocking functions, not for SCADA data collection.

The correct mechanism for reading IED data into an OPC server is MMS over TCP/IP. Many of the same data objects that IEDs publish via GOOSE (breaker position, protection operate signals) are also accessible via MMS on the same IED. TOP Server's IEC 61850 driver reads these via MMS. If your application genuinely requires reading the GOOSE message stream itself (for protection testing, event analysis, or engineering tools), specialized IEC 61850 analysis software or hardware GOOSE capture tools are used — this is outside the scope of an OPC server integration.

What is an IED and how is it different from a PLC?+−

An Intelligent Electronic Device (IED) is a microprocessor-based protection or control device installed in electrical substations — protection relays, bay controllers, automatic transfer switches, voltage regulators, power quality monitors. IEDs are purpose-built for electrical power system applications: they perform protection functions (overcurrent, differential, distance protection), manage circuit breaker operations, and measure power system quantities like voltage, current, power, and frequency.

A PLC is a general-purpose programmable controller designed for industrial process automation — it can be programmed to do virtually anything, but it is not inherently designed for power system protection. IEDs have specialized analog input hardware for current and voltage transformers, are type-tested for specific protection functions against IEC standards (IEC 60255 series), and operate at the sub-millisecond speeds required for power system protection. The communication protocols are also different: PLCs use Modbus, EtherNet/IP, or S7; IEDs use DNP3 and IEC 61850.

What is NERC CIP and how does it relate to IEC 61850?+−

NERC CIP (North American Electric Reliability Corporation Critical Infrastructure Protection) is a set of mandatory cybersecurity standards that apply to bulk electric system (BES) assets in North America — including transmission substations, generation facilities, and control centers. NERC CIP standards impose requirements for electronic security perimeters, access control, configuration management, and incident reporting on the systems that communicate with and control these assets.

IEC 61850 systems that communicate with NERC CIP-applicable assets must be deployed and managed in compliance with the relevant CIP standards. This typically means placing IEC 61850 MMS traffic (TCP port 102) within the electronic security perimeter, controlling access to IED management interfaces, and logging all access and configuration changes. The IEC 61850 standard itself does not define security — IEC 62351 is the companion security standard that addresses encryption, authentication, and access control for IEC 61850 communication, and NERC CIP requirements increasingly drive its adoption in practice.

How do I get data from an IEC 61850 IED into a historian or SCADA system?+−

The standard integration path is: IED (MMS server) → OPC server with IEC 61850 MMS client driver → SCADA / historian (OPC client). TOP Server connects to the IED using the IEC 61850 MMS protocol on TCP port 102, reads logical node data objects at configured polling rates or via report subscriptions, and exposes the data through its OPC DA and OPC UA server interface. Your SCADA or historian connects to TOP Server as an OPC client and subscribes to the IED data like any other OPC data source.

For initial configuration, import the IED's ICD file into TOP Server to automatically discover all available logical nodes and their data objects, rather than manually entering addresses. The ICD file is typically available from the IED vendor as part of the device documentation or engineering tool export.

What is IEC 61968/61970 (CIM) and how does it relate to IEC 61850?+−

IEC 61968 and IEC 61970 define the Common Information Model (CIM) — the data model used for utility enterprise systems: energy management systems (EMS), distribution management systems (DMS), energy trading platforms, and asset management systems. CIM models the entire power system topology — how lines, transformers, generators, and loads connect and relate to each other — at a higher level of abstraction than IEC 61850's device-level data model.

IEC 61850 and CIM operate at different levels: IEC 61850 describes what a specific IED measures and controls (this protection relay, that circuit breaker). CIM describes what role that equipment plays in the larger power system topology (this line segment feeds that load zone). Mapping between IEC 61850's device model and CIM's topology model is an active area of standards work (IEC 61850-7-410 and related documents), and is relevant when integrating IEC 61850 substations into utility enterprise systems. For the practical OPC/SCADA integration question, CIM is background context rather than a direct requirement.

Integrating IEC 61850 substations or renewable energy sites into SCADA?

Software Toolbox has been connecting utility infrastructure — DNP3 RTUs, IEC 61850 IEDs, and everything in between — to OPC and modern data platforms for decades. TOP Server's IEC 61850 driver covers MMS client connectivity with SCL/ICD file import for every major IED vendor.

Talk to an engineer

What is IEC 61850?

What is IEC 61850?

Where IEC 61850 is used

The IEC 61850 communication services

The IEC 61850 data model: logical nodes

IEC 61850 vs. DNP3

Software Toolbox products for IEC 61850

Frequently asked questions

Integrating IEC 61850 substations or renewable energy sites into SCADA?

Ready to connect IEC 61850 IEDs to your SCADA?

Related Resources