A Logical Node (LN) is a standardized, object-oriented abstraction defined by IEC 61850 that encapsulates a single, well-defined substation automation function, such as a circuit breaker (XCBR), distance protection (PDIS), or current measurement (TCTR). Each LN groups related Data Objects (DO)—like position, mode, and health—into a self-contained module, enabling interoperability between multi-vendor Intelligent Electronic Devices (IEDs) by providing a common semantic interface regardless of the underlying hardware implementation.
Glossary
Logical Node (LN)

What is a Logical Node (LN)?
A Logical Node (LN) is the smallest functional building block in the IEC 61850 data model, representing a specific protection, control, or measurement function within an Intelligent Electronic Device (IED).
LNs are instantiated within a Logical Device (LD) on a physical IED and communicate via abstract services mapped to protocols like MMS, GOOSE, or Sampled Values. The IEC 61850 standard defines over 90 logical node classes grouped by function—protection (P), control (C), metering (M), and system services (S)—allowing engineers to design Substation Automation Systems (SAS) by composing these functional blocks rather than hard-coding proprietary logic, dramatically simplifying configuration, testing, and lifecycle management.
Core Characteristics of Logical Nodes
Logical Nodes are the atomic functional elements within the IEC 61850 object model, each encapsulating a specific protection, control, or measurement capability with standardized data objects and services.
Standardized Functional Encapsulation
Each LN represents a well-defined, self-contained function within a physical IED. The standard pre-defines the data objects and behavior for common utility functions, ensuring interoperability between devices from different manufacturers.
- XCBR: Circuit breaker control and monitoring
- PDIS: Distance protection element
- MMXU: Measurement unit for currents and voltages
- PTRC: Protection trip conditioning logic
Hierarchical Naming Convention
Every LN instance is uniquely identified by a structured reference path that reflects its physical location in the substation hierarchy. This path concatenates the IED name, access point, and logical device.
- Format:
IEDNameLDName/LNClassNameInstanceID - Example:
Q1SB1PDIS1refers to instance 1 of distance protection in bay Q1 - Enables precise addressing for GOOSE publisher-subscriber bindings and SCADA data mapping
Mandatory vs. Optional Data Objects
The IEC 61850-7-4 standard defines a strict schema of mandatory (M) and optional (O) data objects within each LN class. This guarantees a baseline of functionality while allowing manufacturers to differentiate.
- Mandatory:
Mod(Mode),Beh(Behavior),Health(Health),NamPlt(Name Plate) are common to all LNs - Optional: Advanced diagnostic or control points specific to a vendor's implementation
- Ensures that critical operational data is always present and uniformly accessible
Common Logical Node Class
All LNs inherit from a common logical node class (LLN0), which provides fundamental attributes for self-supervision and mode control. This inheritance enforces a consistent management interface across every function in the substation.
- Mode (Mod): Controls operational state—
On,Off,Test,Test/Blocked - Behavior (Beh): Reports the actual current functional state
- Health (Health): Reflects internal self-diagnostic status (
Ok,Warning,Alarm) - Name Plate (NamPlt): Provides vendor, version, and configuration metadata
Service Interfaces for Data Access
LNs expose their data through standardized Abstract Communication Service Interfaces (ACSI) , which are mapped to specific protocols like MMS. These services define how clients read, write, report, and log data.
- GetDataValues/SetDataValues: Immediate read/write of data object attributes
- Reporting: Buffered and unbuffered change-driven event reporting
- Logging: Time-stamped historical data storage for disturbance analysis
- GOOSE Control: Direct multicast publishing of status changes for peer-to-peer tripping
Logical Device Containment
LNs are grouped into Logical Devices (LDs) within a physical IED. An LD typically represents a coherent protection or control domain, such as a bay controller or a measurement unit, and always contains an LLN0 for management and an LPHD for physical device information.
LLN0: Manages the LD's datasets, reports, and GOOSE control blocksLPHD: Maps to the physical hardware, providing nameplate and health data- Allows a single IED to host multiple independent functional domains, such as separate bays
Frequently Asked Questions
Clear answers to the most common questions about IEC 61850 Logical Nodes, the fundamental building blocks of substation automation data models.
A Logical Node (LN) is the smallest functional building block in the IEC 61850 data model, representing a specific, well-defined protection, control, measurement, or monitoring function within a substation automation system. Each LN is a named grouping of Data Objects and their associated attributes that together model a real-world power system function, such as a circuit breaker (XCBR), a distance protection element (PDIS), or a current transformer measurement (TCTR). The standard defines over 90 standardized LN classes grouped by function—protection (P), control (C), metering (M), generic (G), and more—ensuring semantic interoperability between Intelligent Electronic Devices (IEDs) from different manufacturers without requiring custom signal mapping.
Common Logical Node Groups and Examples
Standardized logical node groups defined by IEC 61850-7-4, each representing a category of substation functions with representative instances.
| LN Group Prefix | Functional Category | Example LN | LN Class Description | Typical Host IED |
|---|---|---|---|---|
A | Automatic Control | ATCC | Automatic tap changer control for transformer voltage regulation | Voltage Regulator Relay |
C | Supervisory Control | CSWI | Switch controller handling Select Before Operate (SBO) sequences for circuit breakers and disconnectors | Bay Control Unit |
G | Generic Function References | GGIO | Generic process I/O mapping binary status and analog setpoints not modeled by dedicated LNs | RTU or Gateway |
I | Interfacing and Archiving | IHMI | Human-machine interface for local operator display and alarm annunciation | Station HMI |
L | System Logical Nodes | LLN0 | Logical node zero representing the access point and common data set for a physical IED | All IEDs |
M | Metering and Measurement | MMXU | Three-phase measurement unit calculating RMS voltage, current, power, and frequency | Protection IED or Meter |
P | Protection Functions | PDIS | Distance protection with multi-zone quadrilateral or mho characteristics for transmission line fault detection | Distance Protection Relay |
R | Protection Related Functions | RSYN | Synchrocheck function verifying voltage, phase angle, and frequency differences before breaker closing | Bay Control or Protection IED |
S | Sensors and Monitoring | SIML | Insulation medium supervision monitoring SF6 gas density, pressure, and temperature in GIS equipment | Condition Monitoring IED |
T | Instrument Transformers | TCTR | Current transformer representing the physical CT ratio, accuracy class, and secondary circuit | Merging Unit |
X | Switchgear | XCBR | Circuit breaker with position indication, operation counter, and trip coil supervision | Circuit Breaker IED or Bay Control Unit |
Y | Power Transformers | YPTR | Power transformer monitoring winding hot-spot temperature, aging rate, and cooling system status | Transformer Monitoring IED |
Z | Other Power System Equipment | ZBAT | Battery system monitoring state of charge, terminal voltage, and charge/discharge current limits | Battery Management System |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Logical Nodes are the atomic functional elements within the IEC 61850 object model. Explore the core components that interact with and host these standardized building blocks.
Common Data Classes (CDC)
Standardized templates that define the structure and semantics of data objects contained within a Logical Node. Each CDC specifies a set of mandatory and optional attributes with defined functional constraints (e.g., ST for status, MX for measurements).
- SPS (Single Point Status): Used for binary states like circuit breaker position.
- MV (Measured Value): Carries analog measurements with deadbanding and range attributes.
- ACT (Protection Activation): Models the output of protection functions, including general, phase-specific, and neutral signals.
Logical Device (LD)
A container that groups Logical Nodes and provides a communication access point for an Intelligent Electronic Device (IED). An IED typically hosts one or more Logical Devices, each representing a distinct functional subsystem.
- Contains exactly one LLN0 (Logical Node Zero) for managing common device-level data.
- Contains exactly one LPHD (Physical Device Information) for hardware health and nameplate data.
- Enables modular organization of protection, control, and measurement functions within a single physical device.
Logical Node Groups
IEC 61850-7-4 organizes Logical Nodes into functional groups based on their application domain. Each group is identified by a leading character in the LN class name.
- L Group (System LNs): Physical device information (LPHD) and logical node zero (LLN0).
- P Group (Protection): Distance protection (PDIS), overcurrent (PTOC), differential (PDIF).
- R Group (Protection Related): Auto-recloser (RREC), synchrocheck (RSYN).
- X Group (Switchgear): Circuit breaker (XCBR), disconnector (XSWI).
- T Group (Instrument Transformers): Current transformer (TCTR), voltage transformer (TVTR).
Data Object Naming Hierarchy
The full path to a data attribute follows a strict hierarchical concatenation that uniquely identifies every signal in a substation automation system.
Structure: IEDNameLDName/LNName.DataObjectName.DataAttributeName
Example: T1CTRL/XCBR1.Pos.stVal
T1CTRL: The IED controlling Transformer 1.XCBR1: The circuit breaker Logical Node instance.Pos: The data object for switch position (type DPC).stVal: The status value attribute (e.g.,0for off,1for on).
GOOSE Message Subscription
Logical Nodes produce data that is published via Generic Object Oriented Substation Event (GOOSE) messages. Receiving IEDs subscribe to these messages by mapping incoming data to input references in their own LN instances.
- A PDIS (distance protection) LN may subscribe to the Pos.stVal output of an XCBR LN to implement breaker failure logic.
- Subscription is configured in the Substation Configuration Language (SCL) file using
ExtRefelements. - GOOSE allows peer-to-peer communication between LNs across different physical IEDs on the station bus.
LN Instance ID
Each Logical Node instance within a system must have a unique reference composed of a standardized class name, an instance number, and an optional prefix.
- Class: The four-character standardized function name (e.g., XCBR, MMXU).
- Instance Number: A numeric suffix distinguishing multiple instances of the same class (e.g.,
XCBR1,XCBR2). - Prefix: An optional user-defined string added for further functional grouping (e.g.,
Q0XCBR1for a specific bay). - The combination ensures unambiguous identification across the entire substation project.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us