Metering Data Standards in Europe: DLMS/COSEM, CIM, and Beyond

Why Standards Matter for Metering

Europe's smart meter rollout involves hundreds of millions of devices from dozens of manufacturers, deployed across markets with different regulatory requirements. Without interoperability standards, every meter-to-head-end and head-end-to-utility integration becomes a custom project. Standards reduce this complexity, but the European metering standards landscape is itself complex.

DLMS/COSEM: The Device-Level Standard

DLMS/COSEM (Device Language Message Specification / Companion Specification for Energy Metering) is the dominant standard for smart meter communication in Europe. Published as IEC 62056, it defines how meters expose their data and how head-end systems request it.

Architecture

DLMS/COSEM uses an object-oriented data model:

Interface classes define types of data objects a meter can contain. Examples include Register (a measured value), Profile Generic (a table of time-stamped values), and Association (security context).

OBIS codes (Object Identification System) identify specific data items. OBIS code 1.0.1.8.0.255 is active energy import total (your electricity bill's main reading). The hierarchical code structure identifies the value group, medium, channel, measurement, tariff, and billing period.

Application associations establish security contexts between client (head-end) and server (meter). Different associations can provide different access levels: public for basic readings, management for configuration, firmware for updates.

Communication Profiles

DLMS works over various transport layers:

• HDLC over direct serial connections (RS-485, optical port)
• TCP/IP wrapper for Ethernet and cellular connections
• S-FSK PLC (IEC 61334-5-1) for power line communication in the PRIME and G3-PLC variants
• GPRS/NB-IoT for wireless WAN communication

Security

DLMS/COSEM security has evolved significantly:

• Suite 0 (no encryption) is obsolete but still found in older meters
• Suite 1 uses AES-GCM-128 for authenticated encryption
• Suite 2 adds elliptic curve key agreement for forward secrecy

Key management is critical. Each meter has unique encryption keys that must be securely provisioned during manufacturing, stored safely by the utility, and rotated according to security policy. Lost keys mean inaccessible meters.

IEC 61968-9: The System Integration Standard

Where DLMS/COSEM handles meter-to-head-end communication, IEC 61968-9 standardizes data exchange between metering systems and utility enterprise applications (billing, network management, customer portals).

Message Types

IEC 61968-9 defines standardized messages for:

• MeterReadings containing interval data, register reads, and events from meters
• MeterServiceRequests for remote connect/disconnect, configuration changes
• MeterEvents for tamper alerts, power quality events, firmware updates
• EndDeviceControls for sending commands to meters through the head-end

Implementation Approaches

Web services (SOAP/XML) following the IEC 61968-100 implementation profile. Structured but verbose.

REST/JSON implementations are increasingly common despite not being formally standardized in IEC 61968. Lighter weight and more developer-friendly.

Message bus integration using the CIM message header with message broker middleware (ESB). Suitable for large utilities with complex integration landscapes.

National Implementations

European countries have layered national requirements on top of international standards:

Netherlands (DSMR/SMR5)

The Dutch Smart Meter Requirements (DSMR, now SMR5) define a specific DLMS/COSEM profile for residential meters. Key features:

• P1 port providing real-time consumption data to home energy management devices
• Standardized telegram format allowing any third-party device to read meter data
• Centralized meter data management through regional network operators

Germany (BSI Smart Meter Gateway)

Germany took a unique approach with the Smart Meter Gateway (SMGW):

• A separate security device sits between the meter and the WAN
• BSI (Federal Office for Information Security) certifies gateway hardware and firmware
• Communication uses TLS with PKI-based authentication
• The gateway enforces German data protection requirements at the hardware level

This architecture prioritizes security and privacy but adds cost and complexity.

Spain (PRIME PLC)

Spain's rollout is based on PRIME (PoweRline Intelligent Metering Evolution) power line communication:

• DLMS/COSEM application layer over PRIME PLC physical and data link layers
• Concentrators at distribution transformers aggregate meter data
• High penetration rate (nearly complete residential rollout)

Italy (Chain 2 / Open Meter)

Italy, having completed the first European smart meter rollout (Enel's Telegestore), is deploying second-generation meters (Open Meter) with:

• Enhanced DLMS/COSEM profiles
• Support for 15-minute interval data (first generation was limited)
• PLC communication with multi-vendor interoperability

Integration Challenges

Multi-Vendor Environments

Even with DLMS/COSEM, different meter manufacturers implement the standard differently:

• Optional features are supported or not
• Object lists vary (which OBIS codes are available)
• Communication parameters differ
• Firmware update mechanisms are manufacturer-specific

Head-end systems need meter type-specific drivers even within the DLMS framework. Plan for this heterogeneity.

Data Volume Management

A utility with five million smart meters generating quarter-hourly interval data produces 480 million readings per day. System integration at this scale requires:

• Batch processing for routine data flows
• Compression and efficient serialization (XML is verbose; consider binary alternatives for high-volume interfaces)
• Selective data routing (billing systems need validated register reads; analytics platforms need raw interval data)

Data Quality Across System Boundaries

Data quality problems often surface at integration points. Common issues:

• Time synchronization errors between meters and head-end systems
• Missing data from communication failures (gaps in interval data series)
• Unit and scaling discrepancies between meter output and target system expectations
• Timezone handling especially during daylight saving transitions

Implement validation at every system boundary. Catch discrepancies early rather than discovering them in customer bills.

Looking Ahead

The European Commission's Electricity Market Design reform and the Interoperability Framework for energy services are pushing toward:

• Greater standardization of customer data access formats
• Pan-European energy data spaces
• API-based access to metering data for authorized third parties

Software teams building metering integrations should design for increasing openness and interoperability, even if today's implementations are still largely national.

Summary: European metering data standards provide a framework for interoperability, but the reality involves national variations, multi-vendor complexity, and massive data volumes. Build integration layers that handle this diversity while maintaining data quality across system boundaries.