All resources
Whitepaper · 18 Nov 2026 · 16 min read · smoc.cloud team

Standardised meter models: why DLMS GCP matters for the metering business

DLMS/COSEM compliance does not guarantee consistency. How the Generic Companion Profile standardises meter models, and why that lowers cost and lock-in.

Executive summary

DLMS/COSEM gave the metering industry a common language. But a common language is not the same as a common vocabulary. Two meters can both be fully DLMS/COSEM compliant and still expose different objects, different profiles and different event codes for the same thing.

The DLMS User Association's Generic Companion Profile (GCP) addresses this by defining a standardised set of objects, functions and behaviours that meters should implement in the same way. This paper explains what standardised meter models are, why they matter for running the metering business, and how to adopt them.

Figure 1. Meters from different manufacturers exposing the same standardised object model to one head-end and operations layer.
Figure 1. Meters from different manufacturers exposing the same standardised object model to one head-end and operations layer.

1. The problem: compliant, but not consistent

DLMS/COSEM (IEC 62056) defines how meter data is modelled and exchanged, using interface classes and OBIS codes. It deliberately leaves room for choice. In practice that means:

  • Different object lists: vendors choose which objects, profiles and attributes to implement
  • Different event codes: the same tamper or power failure can be reported in different ways
  • Different configurations: load profiles, capture periods and registers vary between models
  • Custom integration per model: each new meter type needs its own mapping in the head-end, MDMS and operations tools
Integration effort per new meter model
Object mappingEvent mappingTestingOperations setup0 days8 days16days24days32days
  • Vendor-specific model
  • Standardised model (GCP)
Figure 2. Illustrative. Most integration effort goes into mapping differences that a standardised model removes.

2. What a standardised meter model provides

A companion profile such as GCP builds on DLMS/COSEM and specifies:

  1. A defined object model: which objects, attributes and OBIS codes a meter exposes
  2. Common use cases: billing reads, load profiles, events, disconnect control, firmware update and clock management, all behaving the same way
  3. Consistent security: agreed security suites and key handling
  4. Conformance testing: so a utility can verify a meter before it reaches the field
Figure 3. The layered model: physical meter, standardised object model, and the business applications built on it.
Figure 3. The layered model: physical meter, standardised object model, and the business applications built on it.

3. Why it matters for the metering business

Lower integration cost

Integrate once against the standard model rather than once per meter model. New vendors and new models become a configuration step, not a project.

Figure 4. From a tangle of custom adapters to one standard connection layer.
Figure 4. From a tangle of custom adapters to one standard connection layer.

Real vendor choice

When meters behave the same way, switching suppliers or running several in parallel is far less risky. Procurement can compete on price and quality rather than integration lock-in.

Better operations

Operations teams see the same events, the same profiles and the same KPIs for every meter. Triage rules, dashboards and reports work across the whole estate.

Cleaner data for billing and analytics

Consistent registers and profiles mean fewer reconciliation errors, fewer estimated bills and analytics that can be trusted across vendors.

Cumulative integration cost as the estate adds meter models
1234680k250k500k750k1000k
  • Vendor-specific (£k)
  • Standardised (£k)
Figure 5. Illustrative. A standard model costs slightly more up front, then each additional meter model is far cheaper to add.

4. How to adopt standardised meter models

  1. Specify it in tenders: require conformance to the companion profile and evidence of testing
  2. Test before rollout: run conformance and interoperability checks on samples of every model
  3. Map legacy meters: use a vendor-neutral information model in your operations layer so older meters appear in the same shape
  4. Align upstream: map the standard model to IEC CIM for MDMS, billing and network systems
  5. Measure: track integration time, exception rates and read quality per model

5. Common pitfalls

  • Assuming compliance means consistency: ask for the profile, not just the protocol
  • Ignoring the installed base: most estates will run legacy and standard meters together for years
  • Stopping at the meter: the value comes when operations, billing and analytics all use the same model

Conclusion

Standardised meter models turn DLMS/COSEM from a shared protocol into a shared way of working. For utilities, that means lower integration cost, real vendor choice and operations that work the same across the whole estate. Read how DLMS/COSEM and IEC CIM fit together, explore our information model, or request a demo.

Figures marked illustrative are indicative examples and not results from a specific customer.

How smoc.cloud helps

Two meters can both be DLMS/COSEM compliant and still behave differently. smoc.cloud maps every device to a standardised model based on the Generic Companion Profile, so differences that cause failures become visible and manageable.

  1. Spot it

    Find non-conforming models

    smoc.cloud profiles each meter type in the estate against the GCP baseline and highlights models, firmware versions and OBIS objects that deviate from it.

  2. Find the root cause

    Link deviations to failures

    Read failures, rejected commands and data gaps are grouped by model and firmware, so you can see when a problem is caused by a non-standard profile rather than by the network or the site.

  3. Fix it

    Normalise and plan out the outliers

    One information model across vendors means integrations and processes run the same way for every meter, and the evidence supports firmware fixes or procurement rules that stop lock-in returning.

What this means for you

Write companion profile conformance into your next meter tender. It is the cheapest way to keep future vendor choice open.

DNOs: how smoc.cloud helps
The Metering Operations Brief

One email a month with new articles, whitepapers and field notes on running smart metering estates. Unsubscribe at any time.

Join the conversation on LinkedIn

Open on LinkedIn
Nov 18, 2026

Customers never see your head-end. They see their bill. A commissioning that stalls. A meter that quietly stops reading. A register that drifts. None of it reaches the customer straight away. Weeks later it arrives as an estimated bill and a call to the contact centre. Our new whitepaper follows five moments that shape the customer experience, from installation to support, and shows where operations decide whether each one goes right. Which stage generates most of your metering complaints? #CustomerExperience #SmartMetering #Utilities

Nov 17, 2026

If you're a utility lead, your IT and compliance teams will ask about security before you ever get to features. They should. Metering platforms touch critical infrastructure and customer data. A good demo answers the hard questions early: how the platform is secured, how it handles compliance, how it fits protocols you already run. What's the first question your IT team asks about a new platform? #UtilityOperations #SmartMetering #CyberSecurity

Nov 14, 2026

How to walk into a budget meeting with metering ROI that survives questions. Start with your estate size. Under 100k meters runs differently from 100k to 1M, and both differ from over 1M. The math changes at each tier. Then map your operations to the cost lines: reads, exceptions, field visits, compliance effort. Then put numbers on each one. Provable beats impressive every time. #UtilityOperations #SmartMetering #EnergySector

next_step

See your estate in smoc.cloud.

A demo walks through your utility types, your vendors and your compliance obligations — not a generic slide deck.