Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62051 Standard: Glossary of Terms for Electricity Metering Data Exchange
IEC 62051-1 serves as the official vocabulary reference for the entire IEC 62056 (DLMS/COSEM) suite, which governs data exchange in smart electricity metering systems. Without a standardized glossary, the cross-vendor interoperability that modern smart grids depend on would be impossible. This article unpacks the critical terms every metering engineer must know.
Tip: IEC 62051 is not meant to be read cover-to-cover. Use it as a reference when implementing DLMS/COSEM communication stacks or when writing meter specification documents.
The Core Vocabulary: Understanding the Building Blocks
The IEC 62056 suite uses an object-oriented data model known as COSEM (Companion Specification for Energy Metering). IEC 62051 defines the terminology for this model with precision, ensuring that a “register” in one implementation is structurally identical to a “register” in another. Here are the most important definitions:
| Term | Definition | Example / Role |
|---|---|---|
| Interface Class (IC) | An abstract template defining a set of attributes and methods for a specific type of functionality | Register IC, Clock IC, ProfileGeneric IC |
| Attribute | A property of an Interface Class object that carries a specific value | value, unit, scaler, status |
| Method | An operation that can be performed on an Interface Class object | reset(), capture(), setParameter() |
| OBIS Code | A unique numerical identifier (A-B-C-D-E-F) for data items | 1.8.0 = total active energy delivered |
| Logical Device | An abstraction within a physical meter that appears as a distinct entity | Multiple logical devices can share one physical meter |
| Association | A secure logical connection between Client and Server | Authentication and encryption context |
| Data Model | The collection of all IC objects and their relationships in a device | The complete object hierarchy |
Why it matters: The precision of IEC 62051 definitions means that a meter from Manufacturer A and a head-end system from Vendor B can communicate without ambiguity — the meaning of every data field is globally agreed upon.
OBIS Codes and the Value Group System
OBIS (Object Identification System) codes are perhaps the single most important concept defined in the IEC 62051 glossary. Every data point in a smart meter is identified by a six-value code (A-B-C-D-E-F), where each value group has a specific meaning:
| Group | Name | Meaning | Example (1.8.0.0.0.255) |
|---|---|---|---|
| A | Media / Energy Type | Electricity, gas, water, heat | 1 = Electricity |
| B | Channel | Measurement channel number | 8 = Total (all phases) |
| C | Physical Quantity | What is being measured | 0 = Active energy |
| D | Measurement Type | Direction, tariff, etc. | 0 = Delivered |
| E | Tariff / Rate | Tariff number | 0 = All tariffs |
| F | Storage / History | Historical period or profile buffer | 255 = Default |
Implementation Note: OBIS codes are hierarchical. A meter engineer configuring a new measurement point must correctly assign all six value groups to ensure the data appears in the correct register. Misconfigured OBIS codes are one of the most common integration issues in AMI deployments.
Engineering Design Insights
Understanding IEC 62051 terminology is not an academic exercise — it directly impacts system architecture decisions:
Logical Device Modeling
Modern smart meters often host multiple logical devices. For example, one logical device may handle revenue metering while a second handles grid monitoring functions. IEC 62051’s precise definition of logical devices enables this separation of concerns, each with independent access control and association settings.
Interface Class Inheritance
The glossary defines the concept of Interface Class inheritance. A “ProfileGeneric” IC inherits from the base “Profile” IC, which in turn inherits from “BaseClass”. This object-oriented approach means that once you understand one IC, you can predict the behavior of related ICs, reducing implementation effort.
Security Association Management
IEC 62051 defines the association mechanism as a secure context between client and server. This is not a simple TCP connection; it involves application-layer authentication (Low, High, or High with HLS) and encryption (AES-128-GCM in modern implementations). The glossary provides the vocabulary to specify these security levels unambiguously.
Design Pattern: When architecting a metering data collection system, use the IEC 62051 logical device model to separate critical (billing) data from non-critical (monitoring) data. This allows you to apply different security policies and polling intervals without redesigning the data model.
FAQs
Q: Is IEC 62051 only for electricity metering?
A: While primarily developed for electricity metering, the glossary and the DLMS/COSEM suite have been extended to cover gas, water, and heat metering. OBIS codes for these media types are defined in the A-group (A=2 for gas, A=3 for water, A=4 for heat).
Q: How does IEC 62051 relate to IEC 62056-62?
A: IEC 62051 provides the vocabulary, while IEC 62056-62 defines the actual Interface Classes and OBIS code assignments. Think of 62051 as the dictionary and 62056-62 as the encyclopedia that uses those words to build complete data models.
Q: What is the difference between a Register and a ProfileGeneric?
A: A Register stores a single current value (e.g., instantaneous voltage). A ProfileGeneric stores a time-stamped log of entries (e.g., 15-minute load profile). Both are Interface Classes, but ProfileGeneric adds buffer management and capture mechanisms that Register does not have.
Q: Are there certifications for IEC 62051 compliance?
A: The DLMS User Association offers certification programs that verify correct implementation of the COSEM object model and terminology defined by IEC 62051. Products that pass receive the “DLMS Certified” mark, which is increasingly required by utility tenders worldwide.
