Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD IEC TS 61850 — Power Utility Automation Data Model Mapping Technical Specification Series (Exchange of CDC-Based Models with IEC 60870-5-101/104 and COSEM to IEC 61850 Translation)
Communication Networks and Systems for Power Utility Automation — Part 80-1 and Part 80-4 (2016 Editions)
🔌 PD IEC TS 61850 is the BSI-adopted IEC/TS 61850 series for communication networks and systems for power utility automation. This batch contains two mapping/translation guidelines from the 80-x sub-series: Part 80-1, which specifies how to exchange information from a CDC (Common Data Class) based data model using IEC 60870-5-101 or IEC 60870-5-104, and Part 80-4, which provides the translation from the COSEM object model (the IEC 62056 electricity metering data exchange suite) to the IEC 61850 data model. Both are handled by BSI Technical Committee PEL/57 (Power systems management and associated information exchange); Part 80-1 supersedes the withdrawn DD CLC/TS 61850-80-1:2010. Together they are the key interoperability bridge between substation automation (IEC 61850), telecontrol communications (IEC 60870), and metering systems (COSEM/DLMS).
💡 A power system runs several communication “languages” at once: IEC 61850 inside substations, IEC 60870-5-101/104 on dispatch telecontrol links, and COSEM/DLMS in smart meters. The mapping and translation guides in this series are the bridge that lets these systems “speak the same data semantics”.
1. Series Composition and Scope 📌
| Standard | Title | IEC Edition | Core Content |
|---|---|---|---|
| PD IEC/TS 61850-80-1:2016 | Communication networks and systems for power utility automation — Part 80-1: Guideline to exchanging information from a CDC-based data model using IEC 60870-5-101 or IEC 60870-5-104 | IEC TS 61850-80-1 (Ed.2.0, 2016-07) | Mapping architecture, gateway use cases, logical device/node mapping to 60870 |
| PD IEC/TS 61850-80-4:2016 | Communication networks and systems for power utility automation — Part 80-4: Translation from the COSEM object model (IEC 62056) to the IEC 61850 data model | IEC TS 61850-80-4 (Ed.1.0, 2016-03) | Data modelling hierarchy, translation tables, data-type mapping |
⚠️ Both documents are guidance/translation technical specifications, not new protocols: they establish consistent data-semantics mappings between existing protocol stacks for reference and implementation in gateways, IEDs, and metering integration.
2. Part 80-1: Exchanging CDC-Based Data Models with IEC 60870-5-101/104 🔄
IEC 61850 organises information with an object-oriented CDC (Common Data Class) data model, while IEC 60870-5-101 (serial/modem) and IEC 60870-5-104 (TCP/IP-based) are the mainstream telecontrol protocols. Part 80-1 provides a systematic way to connect the two worlds:
- Mapping architecture: defines the overall mapping framework from IEC 61850 object models to 60870 application service data units (ASDUs).
- Conceptual architectures and use cases: gives three typical deployment use cases for a gateway device, plus an (optional) architecture for an IED directly connected to a wide area network (WAN).
- Mapping of a device-oriented information model: specifies rules for device object references, logical device class, and logical node class mapping to 60870-5-101/104 addresses and information object addresses.
- Data types and control: handles process data (status, measurement, control, setpoints) and lossless transport of quality bits, timestamps, and attributes.
With uniform mapping tables and use-case templates, integrators can repeatedly design gateways that deliver substation-side IEC 61850 data to the dispatch master station over 60870 links.
3. Part 80-4: Translation from the COSEM Object Model to IEC 61850 📊
IEC 62056 (DLMS/COSEM) is the de facto standard for electricity metering data exchange; its COSEM object model describes metering data objects inside meters. Part 80-4 addresses semantic translation between the “metering world” and the “automation world”:
- Data modelling hierarchy: systematically compares the IEC 62056 data model and application layer with IEC 61850 principles, identifying corresponding levels.
- Translation principles: defines general principles for translating IEC 62056 COSEM objects into IEC 61850 logical nodes.
- Data type template mapping: gives correspondences between IEC 61850 DataTypeTemplates and IEC 62056 Common Data Types.
- Translation tables: provides object-by-object translation tables for categories such as metering and measurement, covering energy, power, demand, and events.
✅ The value of translation is bi-directional consistency: whether a metering value is described on the COSEM side or the IEC 61850 side, it should have identical semantics, units, and timestamps, enabling substation automation systems to directly trust smart-meter data and reducing duplicate acquisition and inconsistent bases.
4. Summary of Key Technical Points 🔧
| Topic | Key Content | Document |
|---|---|---|
| Mapping architecture | Mapping framework from 61850 objects to 60870 ASDUs | 80-1 |
| Gateway use cases | Three gateway deployments and IED direct WAN architecture | 80-1 |
| Node mapping | Logical device/node class to 60870 address rules | 80-1 |
| Modelling hierarchy | Correspondence of IEC 62056 and IEC 61850 data models | 80-4 |
| Object translation | Translation principles from COSEM objects to logical nodes | 80-4 |
| Translation tables | Object-by-object translation for metering/measurement and data types | 80-4 |
5. Engineering Practice 🛠️
- 🔍 Substation-dispatch gateway design: design gateways per Part 80-1 to map station-side 61850 data to 101/104 for the dispatch master station.
- 🔧 Smart-meter data integration: use Part 80-4 translation tables to bring COSEM metering data into substation automation systems, unifying telemetry and metering.
- 📊 Engineering verification: compile point lists from the standard mapping tables and check address, quality, and timestamp consistency for every point on both sides.
- 📋 System upgrade: when introducing IEC 61850 over existing 60870 links, use the mapping guides to evaluate compatibility and plan a transition strategy.
6. Frequently Asked Questions ❓
❓ Q: What is the difference between IEC 61850 and IEC 60870-5-101/104?
A: IEC 61850 is an object-oriented substation automation communication standard with a rich model and real-time mechanisms like GOOSE/SV; IEC 60870-5-101/104 are address-information-object telecontrol protocols with high transport efficiency and strong WAN suitability. They often coexist in one grid and are bridged by gateways.
A: IEC 61850 is an object-oriented substation automation communication standard with a rich model and real-time mechanisms like GOOSE/SV; IEC 60870-5-101/104 are address-information-object telecontrol protocols with high transport efficiency and strong WAN suitability. They often coexist in one grid and are bridged by gateways.
❓ Q: What is a CDC?
A: CDC (Common Data Class) is the fundamental information-model building block in IEC 61850, describing the structure and attributes (quality, timestamp, unit) of measurement values, statuses, and controllable objects. Part 80-1 maps based on the CDC data model.
A: CDC (Common Data Class) is the fundamental information-model building block in IEC 61850, describing the structure and attributes (quality, timestamp, unit) of measurement values, statuses, and controllable objects. Part 80-1 maps based on the CDC data model.
❓ Q: What is the relationship between COSEM and DLMS?
A: DLMS is the protocol specification for metering communication; COSEM (Companion Specification for Energy Metering) defines the object model and data semantics. Together they form DLMS/COSEM, which constitutes the IEC 62056 series. Part 80-4 translates its COSEM object model to the IEC 61850 data model.
A: DLMS is the protocol specification for metering communication; COSEM (Companion Specification for Energy Metering) defines the object model and data semantics. Together they form DLMS/COSEM, which constitutes the IEC 62056 series. Part 80-4 translates its COSEM object model to the IEC 61850 data model.
🔍 Q: Where do mapping errors most often occur?
A: Quality-bit and timestamp semantics, unit conversion, information-object address allocation, and refresh/deadband handling on both sides are the most error-prone. Checking every point against the standard mapping tables and performing joint commissioning is the key to correctness.
A: Quality-bit and timestamp semantics, unit conversion, information-object address allocation, and refresh/deadband handling on both sides are the most error-prone. Checking every point against the standard mapping tables and performing joint commissioning is the key to correctness.