Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC TS 61970-2:2004: Energy Management System Application Program Interface โ Glossary
💡 Key Insight: IEC TS 61970-2:2004 is the terminological foundation of the entire IEC 61970 series — the Common Information Model (CIM) for energy management systems. While often overlooked by engineers eager to dive into the CIM class model (Part 301) or the component interface specifications (Parts 401–500), this glossary is the critical enabler of semantic interoperability. Without the precise definitions established in Part 2, the same term could mean different things in different utility systems, defeating the purpose of a common information model.
1. Purpose and Role Within the 61970 Series
IEC 61970 is a multi-part standard for the Energy Management System Application Program Interface (EMS-API). The standard aims to enable the integration of EMS applications from different vendors, the exchange of power system models between utility systems, and the long-term archiving of power system data. Part 2 provides the glossary of terms used across all other parts of the 61970 series — approximately 250 defined terms covering power system equipment, measurements, control systems, topology, scheduling, and market operations.
The glossary addresses a fundamental problem in the electric power industry: different regions, utility companies, and equipment manufacturers use the same term to mean different things. For example, “breaker” in one system might refer to the physical switching device; in another, it refers to the logical protection zone; in a third, it refers to the maintenance scheduling entity. IEC 61970-2 resolves these ambiguities by establishing a single, precise definition for each term as used within the CIM context, along with notes clarifying how the CIM definition relates to common industry usage.
⚠> Semantic Ambiguity Example: The term “generator” is defined in IEC 61970-2 as “an asynchronous machine that converts mechanical energy into electrical energy, normally part of a generating unit.” This seems straightforward, but note the distinction: the standard carefully distinguishes between GeneratingUnit (the business entity that schedules and dispatches power), Generator (the physical synchronous machine), and GeneratingSet (the combined prime mover + generator assembly). Many existing EMS implementations use “generator” for all three concepts interchangeably, causing data exchange errors when models are shared between systems.
2. Key Terminology Categories
The glossary organizes terms into several categories that reflect the major functional domains of the EMS-API:
2.1 Equipment and Apparatus
This category covers physical power system equipment: Conductor, Transformer, Switch, Breaker, Disconnector, BusbarSection, Line, Cable, Reactor, Capacitor, and PowerTransformer. Each definition specifies not just the physical characteristics but also the electrical behavior and the topological role within the CIM network model. For instance, “Breaker” is defined as “a mechanical switching device, capable of making, carrying, and breaking currents under normal circuit conditions and also making, carrying for a specified time, and breaking currents under specified abnormal circuit conditions such as those of short circuit.” This definition draws from IEC 60050 (International Electrotechnical Vocabulary) but adds the CIM-specific context of how a breaker is represented in the network topology model.
2.2 Measurements and Telemetry
Critical terms for SCADA and data acquisition include AnalogValue, AnalogLimit, DiscreteValue, AccumulatorValue, MeasurementValue, MeasurementValueQuality, and MeasurementValueSource. The glossary distinguishes between a measurement (the conceptual observation of a physical quantity) and a value (the specific numeric reading at a point in time). This distinction is fundamental to the CIM time-series data model and is frequently misunderstood by system integrators who treat measurements and values interchangeably, leading to difficulties in historical data management and state estimation.
2.3 Topology and Connectivity
Network topology terms form the core of the CIM connectivity model: ConnectivityNode, Terminal, TopologicalNode, TopologicalIsland, Bus, and Substation. The glossary defines the critical distinction between a ConnectivityNode (a point in the network where terminals of conducting equipment are connected — a logical connection point) and a TopologicalNode (a set of connectivity nodes that are electrically connected through closed switches — the result of topology processing). This distinction is essential for state estimation and power flow applications.
| Term | Category | Brief Definition | Typical Misinterpretation |
|---|---|---|---|
| ConnectivityNode | Topology | Logical point where terminals connect | Confused with physical busbar |
| TopologicalNode | Topology | Set of connected nodes under closed switches | Confused with ConnectivityNode |
| GeneratingUnit | Generation | Business entity for scheduling power | Confused with physical generator |
| ControlArea | Operations | Portion of the network under balancing authority | Confused with substation or region |
| BaseVoltage | Equipment | Reference voltage level for a network segment | Assumed equal to operating voltage |
| Rating | Equipment | Maximum allowable capacity under specified conditions | Confused with nameplate value |
3. The Glossary as a Standardization Tool
Beyond its role within the 61970 series, the IEC 61970-2 glossary serves as a standardization reference for the broader power system industry. The terms defined in Part 2 are reused by IEC 61968 (distribution management), IEC 62325 (energy market communications), and IEC 61850 (substation automation). When these standards reference CIM terms, they inherit the precise definitions from 61970-2, ensuring semantic consistency across the entire IEC power system management standards framework.
The glossary also plays a critical role in regulatory compliance. Many transmission system operators are required by regulators to submit network models and operational data in CIM format. The glossary ensures that the submitted data uses consistent terminology — a “ControlArea” in a day-ahead schedule has exactly the same meaning as a “ControlArea” in a real-time SCADA snapshot. Without the glossary, the same regulatory submission could be interpreted differently by the submitting utility and the receiving regulator, leading to compliance disputes.
✅ Engineering Best Practice: When deploying any CIM-based integration project, use the IEC 61970-2 glossary as the basis for a project-specific data dictionary. Map every term used in the project’s existing systems to the corresponding CIM term, and document any gaps where the CIM definition does not precisely match the local usage. This mapping exercise typically identifies 15–25% of data exchange requirements that would otherwise be misinterpreted. The mapping should be maintained as a living document updated whenever new interfaces are added or existing systems are upgraded.
4. Limitations and Subsequent Editions
IEC TS 61970-2:2004, while comprehensive for its time, does not include terms for more recent power system developments: distributed energy resources (DER), electric vehicle charging infrastructure, battery energy storage systems, microgrids, and advanced market mechanisms (e.g., FERC Order 841 participation models). These terms have been added in subsequent editions and amendments to the 61970 series, primarily through updates to the CIM model (IEC 61970-301) that have extended the glossary informally. Users should verify that their projects reference the most current CIM edition for terminology covering modern grid assets.
The Technical Specification status (TS rather than IS) reflects that the glossary, like the rest of the 61970 series, undergoes continuous evolution. The CIM User Group (CIMug) maintains a change request process for proposing new terms or modifications to existing definitions. Since 2004, over 200 terms have been added through this process, many of which have been incorporated into the standard’s amendments.
🚨 Interoperability Risk: A recurrent issue in CIM-based integration projects is that project teams use terms like “Substation,” “Bus,” and “Rating” with their intuitive meanings rather than the precise IEC 61970-2 definitions. In one documented case, a model exchange between two ISO/RTO systems in North America required 6 weeks of manual reconciliation because one system defined “Substation” as a voltage-level grouping (two distinct voltages = two substations) while the other defined it as a geographic grouping (same fence line = one substation, regardless of voltage). Following the IEC 61970-2 definition would have avoided this entirely: a Substation is defined by its geographic containment, not by voltage level.
5. Frequently Asked Questions
Q1: Is the IEC 61970-2 glossary legally binding for CIM implementation?
The glossary itself is not legally binding, but regulatory requirements for CIM-based model exchange (such as those mandated by FERC in the US, ENTSO-E in Europe, and AEMO in Australia) effectively make the definitions compulsory for regulatory compliance. Using non-CIM terms or CIM terms with non-standard definitions in regulatory submissions typically results in rejection of the data exchange.
Q2: How does IEC 61970-2 relate to the IEC 60050 International Electrotechnical Vocabulary?
IEC 61970-2 draws heavily from IEC 60050 (IEV) for equipment-related definitions but extends them with CIM-specific context. For example, the IEV defines “transformer” in purely physical terms; IEC 61970-2 adds attributes like “ratedVoltage,” “ratedPower,” and vector group connections that are essential for EMS applications. Where conflicts exist between IEV definitions and CIM definitions, the CIM definition takes precedence within the EMS-API context.
Q3: Does the standard include definitions for market and economic terms?
Partially. The 61970 series glossary includes basic market terms (ControlArea, ReserveRequirement, LoadForecast) but defers detailed market terminology to IEC 62325 (Market Communications). The boundary between the two series is that 61970 covers physical system management (what exists in the grid) while 62325 covers commercial transactions (who buys and sells what).
Q4: How should a project handle terms that are not defined in IEC 61970-2?
Undefined terms should be proposed to the CIM User Group through the formal change request process. Pending adoption, project teams should define local extensions using the CIM naming conventions and document them clearly as extensions. The use of private (non-CIM) namespaces should be minimized and clearly identified in all CIM XML exchanges to prevent interoperability issues.
