Key Takeaways:

• Interoperability is the hard part. The standard is only the starting point; the real work is aligning vendor implementations and proving they work together.
• Custom specs can create hidden costs. Bespoke requirements may look simple upfront but can require expensive testing, fixes and compliance tools later.
• Generic Companion Profiles (GCP), developed by the DLMS User Association, helps reduce unnecessary variation in endpoint design. Its value is giving utilities a common, verifiable baseline so they don’t have to redesign core requirements for every deployment.
• Certification helps, but has limits. The DLMS UA Qualification Program supports integration confidence, but does not certify performance, reliability or vendor quality.
• Regional flexibility is the next tension. Customization may be needed, but too much could undermine the benefits of standardization.

What if the most valuable innovations weren’t the ones that added complexity—but the ones that quietly removed it? 

Take the invention of USB-C, for example. With a single open standard, users no longer need multiple chargers or cables. Devices automatically negotiate power, data and functionality, enabling faster charging, safer delivery and seamless interoperability. By reducing proprietary connectors, the standard itself fades into the background and becomes part of the furniture, while users take for granted the simplicity.

That’s the value of standards: less complexity, greater interoperability and faster deployment and integration. 

As utilities manage increasingly complex, multi-vendor AMI environments, standards like DLMS/COSEM and the ACE SM Generic Companion Profile (GCP) are designed to make that interoperability possible. But getting there takes more than just adopting a specification. 

We spoke with Tony Field, DLMS US Chairman of the Board, about what it takes to make interoperability work—and why it’s becoming more important for today’s utilities.

Q: Interoperability is described as a key benefit of standards. What makes it so challenging to achieve?
Tony: Interoperability is defined as the ability for devices and systems from different vendors to simply work together. In reality, it requires much more than just agreeing on a specification.

A standard is the instruction manual. It defines how a device should behave in a consistent, repeatable and unambiguous way. But getting from that definition to real-world interoperability involves resolving inconsistencies, avoiding misinterpretation and ensuring implementations align across vendors. Once that’s done, you need to prove it by developing test and certification platforms to verify implementations.

Q: How do DLMS/COSEM and the ACE SM Generic Companion Profile (GCP) help address that?
Tony: DLMS/COSEM provides the foundation for how data is structured and exchanged. The GCP builds on that by defining common use cases, data models, formats and default values. 

The intent is to avoid repeatedly redesigning baseline requirements and use cases for different regions or deployments. Without that shared baseline, utilities often end up creating bespoke specifications, which introduces cost, complexity and unpredictability without any additional value.

With the ACE SM GCP as a base, you still have flexibility where needed, but you’re starting from a consistent, globally aligned approach that is both hardened and independently verifiable.

Q: What do organizations tend to get wrong about implementing standards like this?
Tony: The level of effort required to move from a specification to a fully interoperable standard is often underestimated. A former colleague and standards professional, for whom I had great respect, used to say, “Paper is cheaper than concrete.” Although flippant, this pretty much sums up the situation.

Defining the standard is only the first step. After that, you have to address inconsistencies, correct errors and stabilize the specification. Then you need a testing platform to validate compliance and behaviour. Many organizations that choose to write their own specification from scratch, or rely on consultants to do so, ultimately have to find alternative ways to verify compliance with bespoke software tools. They also face pain of working through small inconsistencies and errors on their own—this is the “concrete,” and it is expensive!

Q: How does the DLMS UA Qualification Program help reduce integration risk in multi-vendor environments?
Tony: The DLMS UA Qualification Program provides independent verification that a device meets the core data exchange and functional requirements. It confirms compliance with DLMS/COSEM core specifications and shows that devices support a well-defined set of interoperable use cases at the data level, enabling integration in multi-vendor and multi-meter environments–a requirement for many utilities. There has been significant industry investment over many years to build and maintain the testing, certification and compliance infrastructure behind it.

While multi-vendor systems have been around for years and offer a level of normalization of devices into a set of use cases, each device still requires the development and testing of a specific “driver.” Using an off-the-shelf, certifiable standard like the ACE SM GCP enables devices to be connected to systems much more quickly and cost-effectively. 

It’s also important to be clear about its scope. It does not certify product performance, reliability or environmental durability, and it’s not an endorsement of a specific device or manufacturer.

Q: How does interoperability help simplify complexity for utilities?
Tony: Without a common standard and qualification framework, utilities often need to develop their own specifications and testing tools. That can require external consultants, specialized skills and significant time and expense.

Using a common interoperability baseline simplifies meter design and integration while still supporting the majority of meter-to-cash use cases. This allows utilities to avoid rebuilding that capability themselves and focus more on deploying and using the system.

Q: How does DLMS/COSEM support next-generation AMI deployments?
Tony: As utilities move toward more advanced AMI systems, speed of deployment and integration becomes increasingly important.
Standardized interfaces help utilities work more predictably across applications and use cases, rather than spending time and money validating different meter customizations. That can help redirect resources toward broader customer and digital transformation initiatives.

Q: What role does standardization play as grid systems become more complex?
Tony: The diversity of technologies, vendors and specifications in smart metering has created fragmented systems and increased complexity. Multiple communication technologies with different data formats further add to the challenge of cost efficiency and data exchange.

Standardization helps utilities address current challenges while positioning them for the future of smart metering and grid evolution. By adopting GCP-compliant meters and interoperable solutions based on a global platform, utilities can benefit from standardization and a more efficient AMI network. Success in this evolving landscape depends on a combination of device certification, effective vendor engagement and secure, resilient data practices.

Stay tuned for part two of this blog series where we’ll take a deeper dive into regional extensions, the pros and cons of that approach and the power of good layer separation. 

To learn more about DLMS/COSEM and ACE SM GCP, read our whitepaper, DLMS/COSEM in Action and watch our recent webinar, Future-Proofing AMI: Interoperability & Open Standards.