Key Takeaways

• Conformance testing verifies that a device correctly implements DLMS/COSEM.
• Compatibility testing validates interoperability across defined  use cases.
• Testing reduces integration risk in multi-vendor environments.
• DLMS/COSEM testing does not certify performance, durability or metrology accuracy.
• GCP provides a proven baseline that utilities can build on rather than recreate.

How do you validate compliance, ensure interoperability and decide between custom specifications and standardized solutions?

In the first installment, I mentioned the idiom “paper is cheaper than concrete,” meaning that the architect can change a drawing faster, easier and cheaper than the builder can knock down a wall or move the foundations. 

In this installment, we will explore “the sound of one hand clapping,” an expression I have borrowed from another seasoned standards professional. The relevance of this idiom is the concept of having a specification document, but no way of ensuring compliance with it. 

Assuming you have a well-thought-out specification, everything that comes after that in the process becomes progressively more expensive. Development costs, testing and certification platforms, acceptance testing, design tweaks, field trials, production and ultimately managing deployed systems for decades all depend on getting the foundation right.  

It is of course possible to design, build, commission, maintain, protect and lifecycle manage this development from the ground up, and some choose to do this. However, it is far more economical and safer to adopt an existing certification platform, developed and maintained by a consensus-based deliberative organization. The benefits of this approach come from the feedback, bug fixing and beta testing processes involving a wide variety of stakeholders. 

Furthermore, having the tool available to manufacturers’ development environment and fully accredited labs employing accredited experts will usually produce a better result than a testing platform developed in isolation. Without some form of certification platform, bug fixing loop and stakeholder involvement, any specification will be equivalent to the sound of one hand clapping. 

What is the difference between conformance and compatibility testing?
Conformance testing checks whether a device correctly implements the DLMS/COSEM standard, while Compatibility testing goes a step further, validating whether devices and systems can work together in defined use cases, with consistent functional behavior. 

This distinction is especially relevant following the DLMS User Association's launch of the AC Electricity Smart Meter GCP Compatibility Qualification Program. For utilities, vendors and system integrators, understanding what these tests do—and what they do not do—is essential to building smart metering systems that are easier to deploy, integrate and scale.

A simple way to think about the difference is a grand piano versus a musical composition.

Conformance testing checks whether the instrument is built and tuned correctly. Each key produces the expected note at the correct frequency, and the piano behaves according to the standard.

Compatibility testing asks a different question: can that instrument and its player follow the same score as others and produce the intended result? A perfectly tuned piano is important, but the score is what allows multiple players to perform the same piece in a recognizable way.

How does this apply to DLMS/COSEM?
In DLMS/COSEM terms, conformance proves that a device speaks the language correctly. Compatibility helps prove that different devices and systems can use that language together in defined scenarios.

At its core, conformance testing verifies that a device correctly implements the DLMS/COSEM standard as defined in the Blue and Green Books. It ensures adherence to the defined data exchange rules, including object models, Interface Class definitions  and service handling. This form of testing establishes that a device “speaks” DLMS/COSEM correctly and can be certified as standards conformant.

Compatibility testing, on the other hand, focuses on interoperability and interchangeability. It validates whether devices from different manufacturers can exchange information and operate together using defined use cases and agreed data models. This includes testing interactions between smart meters, head-end systems and other components commonly found in smart metering deployments.

Together, conformance and compatibility testing form the foundation of a robust, scalable and multi-vendor smart metering ecosystem.

What does DLMS/COSEM testing actually verify?
It’s important to understand the scope of DLMS/COSEM testing to set expectations correctly.

What is tested?

• Data exchange protocol compliance and functional behavior at the interface
• Correct implementation of DLMS/COSEM object models
• Handling of services such as GET, SET, ACTION and event notifications
• Interoperability across devices and systems at the use-case level
• Error handling and protocol robustness

What is not tested?

• Hardware performance or durability
• User interface functionality and display characteristics 
• Utility-specific operational policies or configuration
• Metrology performance and measurement accuracy
• Lower-layer communications: Correct implementation of the lower communication layers is assumed. Certification and testing of these layers are expected to be carried out separately by the relevant Alliance or certification body.

In essence, testing ensures that devices communicate correctly—but not that they meet every operational or environmental requirement that a user might require. However, the devices will meet the requirements of a specified and consistently implemented set of foundational use cases.

Who performs DLMS/COSEM testing?
A well-defined ecosystem supports DLMS/COSEM qualification and certification efforts.

• The DLMS User Association (DLMS UA) defines testing frameworks, certification rules and supplies bespoke testing software
• Accredited laboratories conduct formal conformance testing using DLMS UA official testing software tools
• Industry vendors and partners contribute to interoperability validation, specification validation and beta testing of the software tools

This collaborative approach helps ensure consistency, robust software validation, transparency and global recognition.

When should utilities involve accredited labs or experts?
Accredited laboratories provide controlled environments and standardized testing processes. They execute formal test cases and produce certification reports that are broadly recognized across the industry.

Accredited experts play a different but equally important role. They help organizations interpret standards, prepare for testing, provide training and guide implementation decisions. They can also assist utilities and vendors that need to extend GCP to support additional use cases or regional requirements in line with the DLMS/COSEM standards.

Engaging experienced support early can help organizations avoid unnecessary development effort, reduce risk and shorten deployment timelines.

Where can utilities get support with DLMS/COSEM and GCP?
Organizations beginning or expanding their DLMS/COSEM journey have several sources of support available:

• The DLMS User Association for certification guidance and qualification requirements
• Accredited test laboratories for formal testing services
• DLMS-accredited consultants and experts for technical support and training
• Technology providers with practical DLMS/COSEM deployment experience
• Itron's DLMS/COSEM and smart metering specialists

Having access to the right expertise can significantly simplify implementation. Utilities can focus on deployment and operational outcomes rather than spending time and resources creating their own companion specifications, testing frameworks and certification processes from the ground up.

Why does compatibility testing matter now?
Interoperability has become increasingly important as utilities modernize infrastructure and introduce more devices, systems and vendors into their networks.

For smaller utilities, GCP provides a proven and independently verified starting point. For larger utilities, it offers a common baseline that can reduce unnecessary complexity while still allowing room for additional functionality where needed. 

As the energy ecosystem expands beyond the traditional meter-to-cash domain into distributed energy resource management and customer-owned energy assets, some foundational use cases must remain consistent and well defined so that all Energy Smart Appliances can receive and deliver the right data to the right places in the system. If the baseline foundational use cases are reinvented by every region or even by every utility, there is little chance of any coherent ecosystem of energy assets operating correctly.

As part of the DLMS UA qualification process, support for mandatory GCP features is becoming a key requirement for certified electricity meters. This provides utilities with greater confidence that certified devices share a common interoperability foundation.

The question is no longer whether you can build your own specification from the ground up, but whether you can afford to. When a proven path already exists, the smartest move isn’t to forge a new one—it’s to follow it further and faster.

What comes next?
The next challenge is understanding what happens when a utility needs functionality beyond the baseline. How do you introduce regional requirements? When should you use extensions? How can additional functionality be added without recreating the complexity that standardization is intended to remove?

In the next installment, we'll explore extensions, regional annexes and additional functions, and how to introduce them in a way that preserves interoperability while meeting local requirements.

Meanwhile, to learn more about DLMS/COSEM and ACE SM GCP, read our white paper, DLMS/COSEM in Action, and watch our webinar, Future-Proofing AMI: Interoperability & Open Standards.