- Introduction
- 1. What Is the IEC 61850 Data Model?
- 2. Understanding Logical Devices in MiCOM Relays
- 3. What Are IEC 61850 Logical Nodes?
- 4. IEC 61850 Logical Node Groups
- 5. Protection Logical Nodes in MiCOM Relays
- 6. Measurement Logical Nodes in MiCOM Relays
- 7. Circuit Breaker Logical Nodes
- 8. GGIO – Generic Input and Output
- 9. Data Objects and Data Attributes
- 10. Common IEC 61850 Data Classes
- 11. Functional Constraints in IEC 61850
- 12. IEC 61850 Data Quality and Timestamp
- 13. IEC 61850 Logical Nodes and MMS Communication
- 14. IEC 61850 Logical Nodes and GOOSE Communication
- 15. Practical Example: Mapping MiCOM Feeder Protection Information to IEC 61850
- 16. How to Identify Available Logical Nodes in a MiCOM Relay
- 17. Common Mistakes When Working with IEC 61850 Logical Nodes
- 18. Conclusion
- IEC 61850 and MiCOM Relay Training by Elec-Engg
Introduction
One of the most important concepts in IEC 61850 is its standardized object-oriented data model. Unlike conventional communication protocols, where information is often represented through register addresses or proprietary signal numbers, IEC 61850 organizes substation information using logical devices, logical nodes, data objects and data attributes.
This standardized structure allows protection relays from different manufacturers to exchange information using a common data model.
In Schneider Electric MiCOM protection relays, IEC 61850 logical nodes represent protection functions, measurements, circuit breaker information, monitoring signals and other device-related information.
For example, a MiCOM feeder protection relay may use logical nodes such as PTOC for time overcurrent protection, PIOC for instantaneous overcurrent protection, MMXU for measurements and XCBR for circuit breaker information.
Understanding these logical nodes is essential when configuring MMS communication, GOOSE messaging, SCADA integration and IEC 61850 engineering projects.
This article explains the IEC 61850 data model and its practical application in MiCOM protection relays.
1. What Is the IEC 61850 Data Model?
IEC 61850 defines a standardized structure for representing information inside Intelligent Electronic Devices (IEDs).
The data model follows a hierarchical structure:
- Physical IED.
- Logical Devices (LD).
- Logical Nodes (LN).
- Data Objects (DO).
- Data Attributes (DA).
Each level has a specific purpose.
IED: The complete intelligent electronic device, such as a MiCOM P143 feeder protection relay.
Logical Device: A functional grouping of related logical nodes inside the IED.
Logical Node: Represents an individual protection, measurement, control or monitoring function.
Data Object: Represents a specific item of information associated with a logical node.
Data Attribute: Defines the actual value, status, quality or other property of the data object.
This structure makes IEC 61850 data accessible through standardized references.
2. Understanding Logical Devices in MiCOM Relays
A Logical Device (LD) is a grouping of logical nodes within an IED.
For example, a MiCOM protection relay may contain logical devices associated with:
- Protection functions.
- Measurements.
- Control functions.
- Circuit breaker monitoring.
- Device supervision.
The exact logical device names and organization depend on the relay implementation.
A logical device contains one or more logical nodes.
For example:
A conceptual example of a MiCOM relay data model could be:
MiCOM_P143
|
+---- PROT
| |
| +---- PTOC1
| +---- PIOC1
| +---- PTRC1
|
+---- MEAS
| |
| +---- MMXU1
|
+---- CTRL
|
+---- XCBR1
+---- CSWI1
This is an illustrative structure, not a guaranteed data model for every P143 firmware version.
3. What Are IEC 61850 Logical Nodes?
Logical nodes are the fundamental building blocks of the IEC 61850 data model.
Each logical node represents a standardized function within an IED.
Logical node names generally consist of four letters.
Examples include:
| Logical node | Function |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIF | Differential protection |
| PDIS | Distance protection |
| MMXU | Measurement functions |
| XCBR | Circuit breaker |
| XSWI | Circuit switch |
| PTRC | Protection trip conditioning |
| RREC | Autoreclosing |
| GGIO | Generic input/output |
| LPHD | Physical device information |
| LLN0 | Logical device common information |
Logical nodes are classified into different functional groups according to IEC 61850.
4. IEC 61850 Logical Node Groups
IEC 61850 organizes logical nodes into functional groups.
The following groups are particularly relevant to protection and substation automation.
| Prefix | Functional group | Application |
|---|---|---|
| A | Automatic control | Automatic functions |
| C | Control | Switching and control |
| D | Distributed energy resources | DER functions |
| G | Generic functions | General-purpose functions |
| I | Interfacing and archiving | External interfaces |
| L | System logical nodes | Device and logical device information |
| M | Metering and measurement | Electrical measurements |
| P | Protection | Protection functions |
| R | Protection-related functions | Related protection functions |
| S | Supervisory control | Supervision |
| T | Instrument transformers | CT and VT functions |
| X | Switchgear | Breakers and switches |
| Y | Power transformers | Transformer functions |
| Z | Further power system equipment | Other equipment |
For MiCOM protection engineers, the P, M, X, C and G groups are especially important.
5. Protection Logical Nodes in MiCOM Relays
Protection logical nodes represent individual protection functions.
They are particularly important when integrating MiCOM relays with SCADA systems and other IEC 61850 IEDs.
5.1 PTOC – Time Overcurrent Protection
PTOC represents time overcurrent protection.
It is relevant to MiCOM feeder protection relays such as the P141 and P143.
Typical information associated with this function includes:
- Protection pickup.
- Protection operation.
- Protection start indication.
- Protection stage information.
- Protection mode and status.
A conceptual logical node reference could be:
PROT/PTOC1
5.2 PIOC – Instantaneous Overcurrent Protection
PIOC represents instantaneous overcurrent protection.
It is used to model high-set or instantaneous overcurrent functions.
This logical node is useful when communicating instantaneous protection operation information to an external system.
5.3 PDIF – Differential Protection
PDIF represents differential protection functions.
It is particularly relevant to transformer and line differential protection applications.
MiCOM P643 and P546 applications may involve differential protection functionality.
The exact logical node implementation depends on the relay’s IEC 61850 model.
5.4 PDIS – Distance Protection
PDIS represents distance protection.
It is important in transmission line protection applications involving MiCOM distance relays such as the P44x family.
It can represent distance protection-related information, including protection operation and associated status information.
5.5 PTRC – Protection Trip Conditioning
PTRC represents protection trip conditioning.
It is associated with protection trip information and trip-related processing.
It is especially important when understanding the relationship between protection functions and circuit breaker trip commands.
5.6 RREC – Autoreclosing
RREC represents autoreclosing functionality.
It is relevant to feeder and transmission line protection schemes where automatic reclosing is implemented.
6. Measurement Logical Nodes in MiCOM Relays
Measurement information is essential for SCADA monitoring and power system operation.
The MMXU logical node represents measurement functions.
Typical measurement quantities include:
- Phase currents.
- Phase voltages.
- Line-to-line voltages.
- Active power.
- Reactive power.
- Apparent power.
- Frequency.
- Power factor.
For example, a conceptual IEC 61850 reference for phase A current is:
MEAS/MMXU1.A.phsA.cVal.mag.f
The path represents:
- MEAS: Logical device.
- MMXU1: Measurement logical node.
- A: Current data object.
- phsA: Phase A.
- cVal: Complex measured value.
- mag: Magnitude.
- f: Floating-point value.
The exact reference must be verified against the MiCOM relay’s actual data model.
7. Circuit Breaker Logical Nodes
Circuit breaker monitoring and control are fundamental functions in substation automation.
IEC 61850 defines several logical nodes for switchgear applications.
7.1 XCBR – Circuit Breaker
XCBR represents circuit breaker information.
It can include information about:
- Breaker position.
- Breaker operating status.
- Switching-related information.
- Breaker-related measurements and supervision, where implemented.
A common data object associated with breaker position is:
XCBR1.Pos
7.2 XSWI – Circuit Switch
XSWI represents a circuit switch, such as a disconnector or earthing switch.
It can be used to communicate switch position and associated information.
7.3 CSWI – Switch Controller
CSWI represents switch control functionality.
It is associated with the control of switching equipment.
In a MiCOM-based substation, the relevant switching and control functions may be integrated with protection relays or bay control equipment, depending on the architecture.
8. GGIO – Generic Input and Output
GGIO stands for Generic Process I/O.
It is especially important when representing application-specific binary and analog signals that do not have a dedicated standardized logical node.
For example, GGIO may represent:
- External binary input.
- Programmable logic output.
- General alarm.
- Communication status.
- Auxiliary indication.
- Application-specific control signal.
GGIO is particularly useful in multi-vendor substation automation projects.
However, engineers must distinguish between an internal MiCOM signal and the standardized IEC 61850 representation exposed by the relay.
9. Data Objects and Data Attributes
A logical node contains one or more data objects.
Each data object contains data attributes.
For example, the XCBR logical node may contain a position data object called Pos.
The Pos data object contains several attributes.
Common examples include:
| Attribute | Meaning |
|---|---|
| stVal | Status value |
| q | Quality |
| t | Timestamp |
| ctlModel | Control model |
| oper | Operate information |
For example:
XCBR1.Pos.stVal
This reference identifies the status value associated with the breaker position.
The status value may indicate the breaker state according to the standardized enumeration.
Typical double-point position states include:
- Intermediate-state or transient condition.
- Open.
- Closed.
- Bad-state or invalid indication.
The exact encoding and interpretation should follow the applicable IEC 61850 data object definition.
10. Common IEC 61850 Data Classes
IEC 61850 uses standardized Common Data Classes (CDCs) to define the structure and behavior of data objects.
Some important CDCs include:
| CDC | Description |
|---|---|
| SPS | Single Point Status |
| DPS | Double Point Status |
| INS | Integer Status |
| ENS | Enumerated Status |
| MV | Measured Value |
| CMV | Complex Measured Value |
| WYE | Three-phase measured values |
| DEL | Three-phase delta-connected quantities |
| ACD | Directional protection activation information |
| ACT | Protection activation information |
| SPC | Single Point Control |
| DPC | Double Point Control |
| INC | Integer Control |
| ENC | Enumerated Control |
| APC | Analog Process Control |
For example:
- SPS can represent a single binary status.
- DPS can represent circuit breaker position.
- MV can represent a measured value.
- ACT can represent protection activation information.
The CDC defines the standardized structure of the associated data object.
11. Functional Constraints in IEC 61850
Functional Constraints (FCs) identify the purpose of data attributes.
They help distinguish between status information, configuration data, measurements and control information.
Some important functional constraints include:
| FC | Meaning | Application |
|---|---|---|
| ST | Status | Equipment and protection status |
| MX | Measurands | Current, voltage and power |
| CO | Control | Control operations |
| SP | Setpoint | Setpoint information |
| CF | Configuration | Configuration parameters |
| DC | Description | Descriptive information |
| EX | Extended definition | Additional definitions |
| RP | Unbuffered reporting | Report control |
| BR | Buffered reporting | Buffered report control |
| SG | Setting group | Setting group information |
| SE | Setting group editable | Setting group editing |
| SV | Substitution | Substituted values |
| BL | Blocking | Blocking information |
| OR | Operational restriction | Operational restrictions |
For example:
MMXU1.A.phsA.cVal.mag.f
The magnitude attribute is associated with the MX functional constraint.
Understanding functional constraints is useful when browsing IEC 61850 data models and configuring external clients.
12. IEC 61850 Data Quality and Timestamp
IEC 61850 does not communicate only the value of a signal. It can also provide information about the quality and time associated with that value.
Two important data attributes are:
- q: Quality.
- t: Timestamp.
12.1 Quality – q
Quality information indicates the validity and reliability of a data value.
It can include:
- Validity.
- Source.
- Test status.
- Operator blocking.
- Detail quality information.
For example, a measurement may be marked invalid if the associated source is unavailable or the data is unreliable.
12.2 Timestamp – t
The timestamp indicates when the value or event was associated with a particular time.
Time information is important for:
- Event sequence analysis.
- Fault investigation.
- Disturbance analysis.
- Protection operation records.
- SCADA event monitoring.
Accurate time synchronization is particularly important when multiple MiCOM relays exchange event information.
13. IEC 61850 Logical Nodes and MMS Communication
MMS provides access to the IEC 61850 data model.
For example, a SCADA client can read a measurement from a MiCOM relay using its logical node reference.
A conceptual communication path is:
SCADA Client
|
| MMS Read Request
v
MiCOM IEC 61850 Server
|
v
Logical Device
|
v
MMXU1
|
v
Current Measurement
|
v
MMS Read Response
The same data model can be used to configure reporting.
For example, a dataset containing breaker position and protection operation signals can be associated with a Report Control Block.
14. IEC 61850 Logical Nodes and GOOSE Communication
Logical nodes and data objects are also fundamental to GOOSE communication.
GOOSE datasets contain selected data attributes from the publisher’s IEC 61850 data model.
For example, a feeder relay may publish:
- Protection trip status.
- Breaker position.
- Protection start status.
Another MiCOM relay can subscribe to the corresponding GOOSE dataset and use the received information in its programmable logic.
This relationship between logical nodes, datasets and GOOSE communication is essential for practical IEC 61850 engineering.
15. Practical Example: Mapping MiCOM Feeder Protection Information to IEC 61850
Consider a MiCOM P143 feeder protection relay.
The objective is to integrate the relay with a station-level SCADA system.
The following information is required:
| Required information | Possible logical node |
|---|---|
| Overcurrent protection | PTOC |
| Instantaneous overcurrent | PIOC |
| Phase current measurements | MMXU |
| Circuit breaker status | XCBR |
| Protection trip conditioning | PTRC |
| Generic auxiliary signals | GGIO |
| Device health | LPHD |
The engineering process is:
- Identify the required information.
- Check the MiCOM IEC 61850 data model.
- Identify the corresponding logical nodes.
- Identify the required data objects.
- Determine the required data attributes.
- Verify functional constraints.
- Configure the appropriate MMS datasets and reports.
- Configure GOOSE datasets where required.
- Test the information exchange with the SCADA client.
- Document the final signal mapping.
This approach ensures that the station-level system receives the correct information from the MiCOM relay.
16. How to Identify Available Logical Nodes in a MiCOM Relay
The available logical nodes depend on the specific relay model and firmware.
Engineers can identify the supported data model through:
1. IEC 61850 technical documentation
Consult the relay’s communication manual and IEC 61850 implementation documentation.
2. MICS document
The Model Implementation Conformance Statement identifies the supported IEC 61850 model and services.
3. ICD file
The IED Capability Description file provides information about the capabilities and data model of the IED.
4. IEC 61850 configuration software
Use the appropriate MiCOM engineering and configuration tools to inspect the available data objects and communication configuration.
5. IEC 61850 client tools
An IEC 61850 client can browse the server data model and inspect the available information, subject to the relay’s access configuration.
Never assume that all standardized logical nodes are implemented in every MiCOM protection relay.
17. Common Mistakes When Working with IEC 61850 Logical Nodes
Some common engineering mistakes include:
- Assuming all relays use identical logical device names.
- Selecting a logical node without checking its actual implementation.
- Confusing data objects with data attributes.
- Ignoring functional constraints.
- Incorrectly interpreting status values.
- Ignoring data quality information.
- Using incorrect signal references in datasets.
- Assuming an internal relay signal is automatically exposed through IEC 61850.
- Using an incompatible SCL configuration.
- Ignoring firmware-dependent data model differences.
Correct understanding of the IEC 61850 data model is essential for reliable communication engineering.
18. Conclusion
IEC 61850 logical nodes and data objects provide the standardized information structure used by MiCOM protection relays for communication with external substation automation systems.
Understanding logical devices, logical nodes, data objects, data attributes, Common Data Classes and Functional Constraints enables engineers to configure MMS reporting, GOOSE messaging and SCADA integration correctly.
For protection and commissioning engineers, the ability to identify and interpret the IEC 61850 data model is one of the most important skills required for modern digital substation engineering.
Practical experience with MiCOM relay data models, SCL files and IEC 61850 diagnostic tools helps engineers move from theoretical knowledge to successful project implementation.
IEC 61850 and MiCOM Relay Training by Elec-Engg
Elec-Engg provides practical training in power system protection, MiCOM protection relays and IEC 61850 substation automation.
Our training covers:
- MiCOM relay engineering and configuration.
- IEC 61850 logical nodes and data models.
- MMS communication and reporting.
- GOOSE publisher and subscriber configuration.
- Data objects, datasets and functional constraints.
- SCL file engineering.
- MiCOM relay integration with SICAM PAS.
- IEC 61850 testing and troubleshooting.
Training is available through online courses, structured self-paced programs, face-to-face sessions and customized in-house training.
Website: https://elec-engg.com/
