Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62361: Power Systems Interoperability — CIM to IEC 61850 Harmonization
The smart grid vision promises seamless data exchange between utility control centers, substations, field devices, and market participants. Yet the reality is that two fundamentally different information models govern these domains: the Common Information Model (CIM), used in energy management and distribution management systems (IEC 61970/61968), and the IEC 61850 data model, used in substation and DER automation. These models evolved independently, with different terminology, different abstraction levels, and different design philosophies.
IEC 62361, titled “Power systems management and associated information exchange – Interoperability in the long term,” is the critical bridge that resolves the semantic mismatch between CIM and IEC 61850. Without this standard, end-to-end interoperability between the control center and the field remains an expensive, bespoke integration exercise for every deployment.
📋 The Interoperability Problem
To appreciate what IEC 62361 accomplishes, one must first understand the root of the interoperability problem. Consider a simple example: a circuit breaker in a substation.
| Aspect | CIM (IEC 61970/61968) | IEC 61850 | IEC 62361 Resolution |
|---|---|---|---|
| Modeling philosophy | Object-oriented, network-oriented | Function-oriented, device-oriented | Bidirectional mapping rules |
| Object naming | “Breaker” (class: Breaker) | “XCBR” (logical node for circuit breaker) | XCBR ↔ Breaker equivalence mapping |
| Attributes | ratedVoltage, ratedCurrent, position | Loc (position), BlkOpn (block open), BlkCls (block close) | Semantic equivalence table |
| Communication | Web services, SOAP, RESTful APIs | MMS (ISO 9506), GOOSE, SV (Ethernet) | Gateway profile definitions |
| Data exchange scope | Network model, topology, state estimation | Real-time I/O, protection, control | Boundary definition and overlap resolution |
💡 Engineering Insight: The fundamental challenge is that CIM models the power network (buses, branches, transformers as electrical nodes) while IEC 61850 models the automation functions (protection, control, monitoring as logical nodes). A transformer in CIM is a conducting equipment with impedance parameters; in IEC 61850 it is represented by logical nodes YPTR (power transformer), YLTC (tap changer), and YPSH (phase shift). IEC 62361 provides the mapping between these two worldviews, enabling a control center to request a specific tap position change through the CIM interface and have that request executed by the IEC 61850-based substation automation system.
🏗️ Standard Structure — The Harmonization Toolkit
IEC 62361 is organized into multiple parts, each addressing a specific aspect of the CIM-61850 harmonization challenge:
| Part | Title | Key Contribution |
|---|---|---|
| 62361-1 | Reference Model | Framework for organizing and coordinating TC 57 standards; defines the architectural principles for harmonization |
| 62361-2 | Glossary | Unified terminology across CIM, 61850, and IEC 62325 (energy market) domains—a common language |
| 62361-100 | CIM Profiles to 61850 Data Models | Technical mapping rules: how to represent CIM objects as IEC 61850 logical nodes for real-time data exchange |
| 62361-102 | CIM to 61850 Harmonization | Aligns core semantics and design principles; defines the overlapping scope and resolves naming conflicts |
62361-100: The Core Mapping Specification
Part 100 is the most technically detailed section. It specifies how CIM profiles (defined using UML and XSD) are transformed into IEC 61850 logical nodes and data objects. The mapping operates at three levels:
- Class-to-LN mapping: Each relevant CIM class maps to one or more IEC 61850 logical nodes
- Attribute-to-DO mapping: Each CIM attribute maps to an IEC 61850 data object or data attribute
- Association mapping: CIM associations (relationships between classes) map to IEC 61850 data flows and GOOSE publications
✅ Implementation Milestone: The most common use case for IEC 62361-100 is the integration of a DER management system (DERMS) with a distribution management system (DMS). The DERMS uses IEC 61850-7-420 logical nodes (e.g., DERA, DERB, DRCC) to communicate with the field devices, while the DMS uses CIM (IEC 61968-4) for network model management. IEC 62361-100 defines how the DER capabilities reported through 61850 are mapped to CIM attributes for network analysis functions like volt-VAR optimization and state estimation.
🔧 The Semantic Bridge — Key Mapping Examples
IEC 62361-102 provides detailed mapping tables for the most important overlapping concepts. Here are representative examples of the mapping rules defined in the standard:
| CIM Entity | IEC 61850 Entity | Mapping Rule | Data Direction |
|---|---|---|---|
| Breaker.position | XCBR. Pos (DPC status) | Direct attribute mapping: CIM position enum → XCBR position status | Bidirectional |
| TapChanger.stepPosition | YLTC. TapPos (integer) | After scaling factor (CIM uses per-unit, 61850 uses absolute tap position) | Control center → Substation |
| Measurement.measValue | MMXU. A.phsA.cVal.mag (analog) | Measurement value with unit conversion (CIM uses SI, 61850 uses primary/secondary) | Substation → Control center |
| AnalogLimitSet.LimitValue | LIMG. Alm (alarm group) / LIMG. Lmt (limit) | Limit value mapping with threshold type identification | Bidirectional |
| SynchronousMachine.p | MMXU. TotW (total active power) | Active power measurement from generator | Substation → Control center |
⚠️ Practical Implementation Challenge: The most difficult aspect of the CIM-61850 mapping is handling the unit and scaling differences. CIM typically expresses values in SI units (W, V, A) while IEC 61850 allows both SI and primary/secondary units depending on the logical node configuration. Additionally, CIM uses per-unit values for some parameters (e.g., tap changer position), whereas IEC 61850 uses integer tap positions. The IEC 62361 mapping tables include scaling factor definitions, but implementing these correctly requires careful configuration of both systems. Many integration projects fail during commissioning because of a misconfigured scaling factor that goes undetected until the operator sees a wildly inaccurate reading.
📊 Relationship with the IEC 62357 Reference Architecture
IEC 62361 does not exist in isolation—it is one of the key standards within the IEC 62357 “Seamless Integration Reference Architecture” umbrella. The relationship between the two standards is straightforward: IEC 62357 provides the “big picture” of how all TC 57 standards fit together, while IEC 62361 provides the specific mapping details for the CIM-61850 interface.
In the IEC 62357 architecture, the CIM-61850 harmonization spans the boundary between the Information layer (where CIM provides the semantic model for enterprise-level data exchange) and the Communication layer (where IEC 61850 provides the protocol for real-time device-level communication). Without IEC 62361, there is a “semantic gap” between these layers that must be filled with custom application logic. With IEC 62361, the mapping is standardized, allowing off-the-shelf integration platforms to handle the translation.
🚨 Critical Planning Advice: When planning a DMS-ADMS integration project, do not assume that IEC 62361 compliance alone guarantees interoperability. The standard defines the mapping rules, but each utility deploys its own CIM profiles (IEC 61968-3 to 61968-9) and its own IEC 61850 device configurations. The project must include a semantic validation phase where the actual CIM profiles and 61850 IED capabilities documents (ICD files) are checked against the IEC 62361 mapping tables. Budget at least 4–6 weeks for this validation—it will save months of commissioning delays.
❓ Frequently Asked Questions
Q1: Does IEC 62361 require both CIM and IEC 61850 to be implemented in the same system?
No. IEC 62361 is primarily relevant for systems that sit at the boundary between the control center domain (CIM) and the substation/field domain (IEC 61850). A standalone EMS that only communicates with other EMS systems using CIM does not need IEC 62361. Similarly, a standalone substation that only communicates with its own IEDs using IEC 61850 does not need it. The standard becomes essential when you build the interface between these two domains.
Q2: How does IEC 62361 handle version differences between CIM and IEC 61850 editions?
The standard defines mapping rules at the semantic level, not the version level. However, IEC 62361-100 includes conformance statements that specify which versions of CIM (IEC 61970-301 edition and IEC 61968-11 edition) and which editions of IEC 61850 (primarily Edition 2.1) are supported. When either standard is updated, the TC 57 working group responsible for IEC 62361 produces a technical corrigendum or amendment to update the mapping tables.
Q3: Can IEC 62361 be used for real-time control applications?
Partially. The information model mapping defined in IEC 62361 is suitable for control applications with response time requirements of 100 ms or slower (typical SCADA and EMS functions). For time-critical control (GOOSE messages with 3 ms delivery requirements as per IEC 61850-5), the mapping does not introduce latency but the CIM side of the interface may not be designed for such speed. In practice, time-critical control signals are handled within the IEC 61850 domain, while the CIM interface handles the “one step up” coordination.
Q4: What tools support IEC 62361 compliance testing?
Several tools support CIM-61850 interoperability validation. The UCA International Users Group provides the IEC 61850 certification test program that includes CIM harmonization tests. Commercial tools like SISCO’s CIM-61850 Mapper and OMICRON’s StationScout include mapping validation features. The open-source CIMHub project also provides mapping utilities. However, there is no single “IEC 62361 compliance tester”—verification typically requires a combination of CIM validation tools, IEC 61850 conformance test tools, and manual review of the mapping configuration.
