- 1. Introduction
- 2. What Is the IEC 61850 Data Model?
- 3. Intelligent Electronic Device (IED)
- 4. Logical Devices (LD)
- 5. Logical Nodes (LN)
- 6. Measurement Logical Nodes
- 7. Switching and Circuit Breaker Logical Nodes
- 8. Data Objects (DO)
- 9. Data Attributes (DA)
- 10. Common Data Classes (CDC)
- 11. Functional Constraints (FC)
- 12. IEC 61850 Object Reference Structure
- 13. IEC 61850 Data Model and MMS Communication
- 14. Data Model and GOOSE Communication
- 15. Data Model and SCL Files
- 16. Practical Example: Mapping MiCOM Feeder Protection Data
- 17. Common Data Model Errors
- 18. Practical Testing of IEC 61850 Data
- 19. Engineering Recommendations
- 20. Conclusion
- 21. Practical IEC 61850 and MiCOM Training by Elec-Engg
1. Introduction
Understanding the IEC 61850 data model is essential when configuring, testing and integrating MiCOM protection relays into modern substation automation systems.
IEC 61850 does not simply transfer electrical measurements and protection signals as unstructured data points. It organizes information into a standardized object-oriented structure consisting of logical devices, logical nodes, data objects and data attributes.
This structure allows different systems, such as MiCOM protection relays, Siemens SICAM PAS, SCADA servers and engineering tools, to exchange information using a common communication model.
For protection and commissioning engineers, understanding this structure is particularly important when:
- Configuring IEC 61850 communication in MiCOM relays
- Identifying protection indications
- Mapping measurements into SCADA
- Configuring MMS datasets and reports
- Engineering GOOSE communication
- Reviewing ICD and SCD files
- Troubleshooting missing or incorrect data points
- Testing IEC 61850 communication with Wireshark and IED simulation tools
This article explains the IEC 61850 data model from a practical engineering perspective, with examples relevant to MiCOM protection relays.
Important: The logical nodes and data references shown are standard examples. Their availability and exact implementation must be verified against the specific MiCOM model, order code, firmware and IEC 61850 documentation.
2. What Is the IEC 61850 Data Model?
The IEC 61850 data model defines how information inside an Intelligent Electronic Device (IED) is organized and identified.
For example, a MiCOM feeder protection relay may contain information about:
- Phase currents
- Voltages
- Frequency
- Overcurrent protection
- Earth fault protection
- Circuit breaker position
- Protection trip commands
- Device alarms
- Communication status
IEC 61850 organizes these functions into logical nodes and data objects.
The main hierarchy is:
Substation
|
+-- IED
|
+-- Logical Device
|
+-- Logical Node
|
+-- Data Object
|
+-- Data Attribute
Each level has a specific role.
| Element | Description |
|---|---|
| Substation | Overall electrical installation |
| IED | Intelligent electronic device |
| Logical Device | Logical grouping of related functions |
| Logical Node | Standardized functional element |
| Data Object | Information associated with a function |
| Data Attribute | Individual value or property |
This structure allows an IEC 61850 client to identify and access information without relying exclusively on manufacturer-specific point names.
3. Intelligent Electronic Device (IED)
An IED is a device that performs protection, control, monitoring or automation functions.
Examples include:
- MiCOM feeder protection relays
- MiCOM distance protection relays
- MiCOM transformer protection relays
- Siemens SIPROTEC relays
- ABB protection and control IEDs
- SEL protection relays
- Bay control units
- Merging units
In an IEC 61850 system, an IED is represented through its logical structure and communication access points.
For example:
IED Name: MiCOM_FEEDER_01
Access Point: Ethernet1
Server
|
+-- Logical Device
|
+-- Logical Node
+-- Logical Node
+-- Logical Node
An IED name identifies the device within the SCL engineering project.
It is important to distinguish the IED name from its IP address. The IED name is part of the IEC 61850 configuration, while the IP address identifies its network interface.
4. Logical Devices (LD)
A Logical Device is a logical grouping of functions within an IED.
A physical MiCOM relay may contain one or more logical devices depending on its implementation.
For example, a simplified relay structure might be:
MiCOM_FEEDER_01
|
+-- ProtectionLD
| |
| +-- PTOC
| +-- PIOC
| +-- PTRC
|
+-- MeasurementLD
| |
| +-- MMXU
|
+-- ControlLD
|
+-- XCBR
+-- CSWI
This is an illustrative organization, not a guaranteed MiCOM implementation.
Logical devices help organize related functions and provide a structured way to access the IED’s data.
4.1 Logical Device Naming
Logical devices are identified using names defined in the IED configuration.
For example:
PROTMEASCTRL
These are illustrative names only.
The actual logical device names must be obtained from the device data model or SCL description.
5. Logical Nodes (LN)
A Logical Node represents a standardized function within an IED.
Logical nodes are one of the most important concepts in IEC 61850.
Instead of defining every manufacturer’s protection function using completely different names, IEC 61850 provides standardized logical-node classes for common functions.
For example:
| Logical Node | Description |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIS | Distance protection |
| PDIF | Differential protection |
| MMXU | Measurement functions |
| XCBR | Circuit breaker |
| XSWI | Switch or disconnector |
| CSWI | Switching control |
| PTRC | Protection trip conditioning |
| RREC | Automatic reclosing |
| GGIO | Generic input/output |
| LPHD | Physical device information |
| LLN0 | Logical device common information |
These standardized names make IEC 61850 data models easier to understand across different manufacturers.
5.1 Protection Logical Nodes
Protection logical nodes represent protection functions.
Common examples include:
PTOC – Time Overcurrent Protection
Used to represent time-delayed overcurrent protection functions.
PIOC – Instantaneous Overcurrent Protection
Used to represent instantaneous overcurrent protection functions.
PDIS – Distance Protection
Used to represent distance protection functions.
PDIF – Differential Protection
Used to represent differential protection functions.
PTRC – Protection Trip Conditioning
Used to represent protection trip conditioning and related information.
RREC – Automatic Reclosing
Used to represent automatic reclosing functions.
The presence of a logical node does not automatically mean that all its optional data objects are implemented in a particular MiCOM relay.
6. Measurement Logical Nodes
Electrical measurements are commonly represented using measurement-related logical nodes.
The most familiar example is MMXU.
6.1 MMXU – Measurement
MMXU represents three-phase electrical measurements and related quantities.
Depending on the implementation, it may provide:
- Phase currents
- Phase-to-phase voltages
- Phase-to-neutral voltages
- Active power
- Reactive power
- Apparent power
- Power factor
- Frequency
A simplified representation is:
MMXU
|
+-- Current
|
+-- Voltage
|
+-- Active Power
|
+-- Reactive Power
|
+-- Frequency
For a MiCOM feeder relay, the engineer may use MMXU information to transfer phase current and voltage measurements to SICAM PAS or another SCADA system.
6.2 Measurement Quality
Measurement values should be evaluated together with their quality information.
IEC 61850 uses the q attribute to indicate the quality of a data value.
For example, a measurement may have an invalid or questionable quality state even when a numerical value is available.
SCADA systems should handle quality information correctly rather than displaying every received value as valid.
7. Switching and Circuit Breaker Logical Nodes
Switching information is particularly important in protection and control systems.
Common switching-related logical nodes include:
| Logical Node | Function |
|---|---|
| XCBR | Circuit breaker |
| XSWI | Switch or disconnector |
| CSWI | Switching control |
| CILO | Interlocking |
| CPOW | Point-on-wave switching, where implemented |
7.1 XCBR – Circuit Breaker
XCBR represents circuit breaker information.
Typical information may include:
- Breaker position
- Breaker operating information
- Breaker health or related status
- Supported control-related information
A simplified example:
XCBR
|
+-- Position
|
+-- Operating Information
|
+-- Status Information
The exact data objects and attributes depend on the IED implementation.
7.2 CSWI – Switching Control
CSWI represents switching control functionality.
It is associated with control operations such as:
- Circuit breaker opening
- Circuit breaker closing
- Switch operation
The actual control capability depends on the relay configuration, control model and application logic.
7.3 XSWI – Switch or Disconnector
XSWI represents switchgear information for switching devices other than circuit breakers, depending on the equipment and implementation.
For example, a substation disconnector may be represented through XSWI.
8. Data Objects (DO)
A Logical Node contains one or more Data Objects.
A Data Object represents a particular item of information within the logical node.
For example, an MMXU logical node may contain data objects for current, voltage, power and frequency.
A protection logical node may contain data objects representing protection operation and settings.
A circuit breaker logical node may contain data objects representing position and related information.
A simplified structure is:
Logical Node: MMXU
|
+-- A
|
+-- PhV
|
+-- W
|
+-- Hz
These are common IEC 61850 data-object names, but the exact availability and content must be checked against the device model.
8.1 Data Object Examples
| Logical Node | Data Object example | Meaning |
|---|---|---|
| MMXU | A | Current |
| MMXU | PhV | Phase voltage |
| MMXU | W | Active power |
| MMXU | Hz | Frequency |
| XCBR | Pos | Position |
| PTOC | Str | Start information |
| PTOC | Op | Operation information |
The names above illustrate common IEC 61850 concepts. The complete reference must include the logical device and actual logical-node instance.
9. Data Attributes (DA)
A Data Object contains Data Attributes.
These attributes represent individual values, status information, configuration information or other properties.
For example, a switching position data object may contain:
stVal– Status valueq– Qualityt– Timestamp
A measurement data object may contain:
mag– Magnitudeq– Qualityt– Timestamp
The exact attributes depend on the data object and its Common Data Class.
9.1 Example: Circuit Breaker Position
A simplified circuit breaker position representation is:
XCBR
|
+-- Pos
|
+-- stVal
+-- q
+-- t
Here:
stValrepresents the position state.qrepresents quality.trepresents the associated timestamp.
The actual position encoding and status interpretation must be handled according to the IEC 61850 data type and device implementation.
9.2 Example: Current Measurement
A simplified current measurement representation is:
MMXU
|
+-- A
|
+-- phsA
| |
| +-- mag
|
+-- phsB
| |
| +-- mag
|
+-- phsC
|
+-- mag
This illustrates how phase current information may be organized.
Actual references and available phases depend on the relay implementation.
10. Common Data Classes (CDC)
IEC 61850 uses Common Data Classes to define the structure and meaning of data objects.
A CDC specifies the attributes and data types associated with a particular category of information.
Examples include:
| CDC | Typical use |
|---|---|
| SPS | Single-point status |
| DPS | Double-point status |
| INS | Integer status |
| ENS | Enumerated status |
| MV | Measured value |
| CMV | Complex measured value |
| WYE | Three-phase measurements |
| DEL | Delta-connected measurements |
| SPS/ACT-related structures | Status and operation information, depending on the data model |
| SPC | Controllable single-point |
| DPC | Controllable double-point |
| INC | Controllable integer |
The exact CDC used depends on the data object defined in the IEC 61850 model.
Understanding CDCs is useful when mapping relay data into SCADA databases because it helps engineers identify the nature and structure of each data object.
11. Functional Constraints (FC)
Functional Constraints identify the purpose or use of a data attribute.
They help distinguish measurements, status values, control information and configuration parameters.
Common functional constraints include:
| FC | Meaning | Typical application |
|---|---|---|
| ST | Status | Breaker position |
| MX | Measurement | Current and voltage |
| CO | Control | Switching command |
| SP | Setpoint | Setpoint value |
| CF | Configuration | Configurable parameters |
| DC | Description | Descriptive information |
| RP | Unbuffered reporting | Report configuration |
| BR | Buffered reporting | Buffered report configuration |
| SG | Setting group | Setting group information |
| SE | Setting group edit | Setting group editing |
| SV | Substitution | Substituted values |
| BL | Blocking | Blocking information |
| OR | Operational restriction | Operational restriction information |
Not every FC applies to every logical node or data object.
11.1 Why Functional Constraints Matter
Consider a circuit breaker position and a circuit breaker control command.
Although both relate to the same physical circuit breaker, they represent different information.
- Position is status information.
- Control is an operation request.
Using the wrong functional constraint can result in incorrect data access or control configuration.
12. IEC 61850 Object Reference Structure
An IEC 61850 data reference identifies a specific item in the IED data model.
A typical structure is:
IEDName
LogicalDevice
LogicalNode
DataObject
DataAttribute
For example, an illustrative reference may look like:
MiCOM_FEEDER_01/PROT1.PTOC1.Op.general
This is a conceptual example, not a guaranteed MiCOM reference.
The components represent:
MiCOM_FEEDER_01– IED namePROT1– Logical devicePTOC1– Logical node instanceOp– Operation data objectgeneral– Data attribute
The exact reference must be taken from the relay’s actual IEC 61850 data model.
12.1 Why Exact References Are Important
A SCADA system cannot reliably access a data point if the configured reference does not match the server’s actual data model.
For example, using the wrong logical device name, logical-node instance or data attribute may cause:
- Failed data access
- Missing measurements
- Reports not received
- Incorrect point mapping
- Failed control operations
Always verify references against the actual device description and online data model.
13. IEC 61850 Data Model and MMS Communication
MMS is used to access IEC 61850 server data and services.
A typical architecture is:
SICAM PAS
MMS Client
|
|
Ethernet
|
|
MiCOM Relay
MMS Server
|
|
IEC 61850 Model
The client may perform supported services such as:
- Association establishment
- Server and logical-device discovery
- Logical-node discovery
- Data-object access
- Data reads
- Reporting
- Supported control operations
The actual services available depend on the relay implementation.
13.1 MMS Data Access
When an MMS client requests a measurement, it uses the corresponding IEC 61850 data reference.
For example, a client may access a current measurement represented through MMXU.
The server returns the requested value together with associated information where supported.
The engineer should verify:
- Correct object reference
- Correct functional constraint
- Data type
- Quality
- Timestamp
- Engineering unit
- Scaling
14. Data Model and GOOSE Communication
GOOSE uses IEC 61850 data objects as the basis for publishing selected information.
However, GOOSE communication does not simply transmit arbitrary MMS read requests.
A publisher is configured with a dataset and GOOSE control block.
The selected dataset members are transmitted through Ethernet multicast messages.
A simplified architecture:
MiCOM Relay A
Publisher
|
GOOSE Dataset
|
GOOSE Control
|
Ethernet Multicast
|
MiCOM Relay B
Subscriber
|
External Reference
|
Protection or Control Logic
14.1 Dataset Members
A GOOSE dataset may contain selected status information, such as:
- Protection operation
- Breaker status
- Interlocking status
- Blocking signals
The publisher and subscriber must be configured consistently.
14.2 External References
In SCL engineering, ExtRef elements are commonly used to describe external references, including the relationship between received GOOSE information and subscriber data.
Correct external-reference mapping is important for ensuring that the subscriber uses the intended published information.
15. Data Model and SCL Files
The IEC 61850 data model is described through SCL configuration files.
Common file types include:
| File | Purpose |
|---|---|
| ICD | IED capability description |
| CID | Configured IED description |
| IID | Instantiated IED description |
| SCD | Substation configuration description |
| SSD | System specification description |
An SCL file may contain information about:
- IEDs
- Access points
- Servers
- Logical devices
- Logical nodes
- Data objects
- Datasets
- Report control blocks
- GOOSE control blocks
- Communication parameters
- External references
15.1 Example of SCL Data Model Structure
A simplified conceptual structure is:
<SCL>
<IED name="MiCOM_FEEDER_01">
<AccessPoint name="AP1">
<Server>
<LDevice inst="PROT1">
<LN0 lnClass="LLN0" inst="">
<DataSet name="Measurements">
<!-- Dataset members -->
</DataSet>
</LN0>
<LN lnClass="MMXU" inst="1"/>
<LN lnClass="PTOC" inst="1"/>
<LN lnClass="XCBR" inst="1"/>
</LDevice>
</Server>
</AccessPoint>
</IED>
</SCL>
This is an illustrative XML structure, not an actual configuration file for a specific MiCOM relay. A valid SCL file requires the appropriate schema elements, attributes, data types and references.
16. Practical Example: Mapping MiCOM Feeder Protection Data
Consider a feeder protected by a MiCOM relay.
The SCADA system needs the following information:
- Phase currents
- Frequency
- Circuit breaker position
- Overcurrent start
- Overcurrent trip
- Earth fault trip
- Relay alarm
A practical mapping table may be prepared as follows:
| SCADA information | IEC 61850 logical node | Data object example |
|---|---|---|
| Phase current | MMXU | A |
| Frequency | MMXU | Hz |
| Breaker position | XCBR | Pos |
| Overcurrent start | PTOC | Str |
| Overcurrent operation | PTOC | Op |
| Earth fault operation | Applicable protection LN | Implementation-dependent |
| Relay alarm | Device status or alarm LN | Implementation-dependent |
This is a functional mapping guide. The exact logical nodes, data objects and attributes must be checked in the selected MiCOM relay.
16.1 Engineering Procedure
- Identify the MiCOM relay model and firmware.
- Obtain its IEC 61850 documentation.
- Review the available logical devices.
- Identify the required logical nodes.
- Locate the required data objects.
- Confirm functional constraints.
- Verify the data types and CDCs.
- Prepare the SCADA point list.
- Configure MMS reporting.
- Test the actual values and status indications.
17. Common Data Model Errors
Incorrect interpretation of the IEC 61850 data model can create problems during commissioning.
| Error | Consequence | Solution |
|---|---|---|
| Wrong logical device | Data access fails | Verify the actual LD name |
| Wrong LN instance | Incorrect or unavailable point | Check the configured LN instance |
| Wrong data object | Missing or incorrect information | Check the device data model |
| Wrong attribute | Invalid data reference | Verify the complete reference |
| Incorrect FC | Access or configuration problem | Confirm functional constraint |
| Incorrect CDC interpretation | Wrong SCADA data type | Check the common data class |
| Assuming all standard LNs exist | Missing data points | Verify the relay implementation |
| Ignoring quality | Invalid data displayed as valid | Map and process quality correctly |
| Ignoring timestamps | Incorrect event sequence | Preserve timestamp information |
18. Practical Testing of IEC 61850 Data
Data model verification should be part of the commissioning process.
18.1 Online Data Model Verification
Use the supported engineering or IEC 61850 client tools to:
- Establish communication.
- Discover logical devices.
- Discover logical nodes.
- Identify available data objects.
- Read supported attributes.
- Verify measurements.
- Check quality and timestamps.
18.2 Measurement Testing
Compare the values received through IEC 61850 with:
- Relay front-panel measurements
- Test equipment measurements
- Expected secondary values
- SCADA display values
Check engineering units and scaling.
18.3 Protection Indication Testing
Using approved test procedures:
- Apply the appropriate test condition.
- Verify protection start.
- Verify protection operation.
- Check the corresponding IEC 61850 data.
- Confirm SICAM PAS or SCADA indication.
- Verify event timestamps and quality.
18.4 Control Testing
For supported control objects:
- Verify the object reference.
- Confirm the control model.
- Check local/remote selection.
- Verify interlocking.
- Test the command under approved conditions.
- Confirm actual equipment feedback.
19. Engineering Recommendations
For effective IEC 61850 data-model engineering in MiCOM relays:
- Start with the actual device documentation, not assumed logical-node lists.
- Verify the complete logical device and logical-node structure.
- Understand the difference between data objects and data attributes.
- Learn the main CDCs and functional constraints.
- Verify quality and timestamp handling.
- Use exact data references in SCADA databases.
- Review the ICD and SCD files carefully.
- Distinguish MMS data access from GOOSE publishing and subscription.
- Test every important indication against the physical relay behaviour.
- Maintain a complete data-point list for commissioning and future maintenance.
20. Conclusion
The IEC 61850 data model is the foundation of communication and interoperability in modern substation automation systems.
For MiCOM protection relays, understanding logical devices, logical nodes, data objects, data attributes, CDCs and functional constraints is essential for successful configuration and SCADA integration.
This knowledge helps engineers identify the correct data references, configure MMS reporting, engineer GOOSE applications and troubleshoot communication problems.
The most important practical lesson is that standard IEC 61850 names provide a common framework, but the actual implementation must always be verified against the selected MiCOM relay’s documentation and configuration.
21. Practical IEC 61850 and MiCOM Training by Elec-Engg
Elec-Engg provides practical training in protection relays, IEC 61850 engineering and substation automation.
Relevant training subjects include:
- MiCOM protection relay engineering
- IEC 61850 data models
- Logical nodes and data objects
- Functional constraints and CDCs
- MMS communication and reporting
- GOOSE configuration and testing
- ICD, CID and SCD files
- SICAM PAS integration
- Wireshark protocol analysis
- Protection relay testing and commissioning
Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.
Practical courses by Dr Saeed Roostaee / Elec-Engg.
Website: https://elec-engg.com/
