DLMS Smart Meter, OBIS and HES Integration: AMI Project Buyer Technical Verification Checklist

"Supporting DLMS/COSEM" can serve as a starting point for evaluating smart meter products, but this statement alone does not prove that the product has end-to-end interoperability capabilities.

In advanced metering infrastructure (AMI) projects, DLMS smart meters need to correctly exchange data and commands required for the project with gateways, data concentrators, or front-end acquisition systems (HES). Establishing physical or network connections is just one step in the system integration process.

Smart meters and upper level systems also need to be consistent in the following aspects:

. COSEM objects and interface classes;

. OBIS identifier;

. citation method;

Supported services and Conformity Blocks;

Communication configuration file;

Identity authentication and security settings;

Client access permissions;

Data type, unit, and multiplier;

Definition of events and load curves;

. HES side object mapping.

COSEM defines how measurement data and equipment functions are represented in object form, while OBIS provides standardized identification for corresponding data items and object instances. The DLMS application layer provides the client server services required for establishing associations, accessing object properties, and calling object methods.

Therefore, for AMI project buyers, the key issue should not only be:

Does this smart meter support DLMS/COSEM?

And further confirmation should be made:

Does the specific smart meter configuration provide the necessary objects, security settings, and communication configurations for the project, and can it operate correctly in conjunction with the data concentrator and HES used in the project?

What does interoperability mean in AMI projects?

Interoperability refers to the ability of different devices and systems to exchange the information required for a project, and to interpret and use this information correctly.

A typical AMI data link may include:

DLMS intelligent smart meter

→ Communication Network

Gateway or data concentrator

Pre Acquisition System (HES)

MDM/billing/utility platform

4、 Smart meter, data concentrator, and HES communication link

In some projects, HES directly communicates with smart meters; In other projects, communication is accomplished through data concentrators.

A typical link may be:

DLMS Smart Meter

→ PLC/RF/cellular communication/other communication networks

→ Data Concentrator

→ HES

DLMS/COSEM can run on multiple communication configuration files. The required communication configuration and testing scope should be confirmed based on the selected product, communication technology, data concentrator design, and project requirements.

There may be significant differences in the functionality of data concentrators across different projects. The buyer should confirm whether the data concentrator undertakes the following functions:

Operating as a DLMS client for smart meters;

Transparent forwarding of communication messages;

Store and summarize smart meter data;

Scheduling local reading tasks;

Support storage and forwarding mechanism;

Expose or forward processed data to HES;

Perform protocol conversion or data conversion;

Manage local communication retries and fault recovery.

The project team should also verify:

Address structure;

Session establishment and timeout mechanism;

The number of smart meters that each data concentrator can access;

Reading plan;

Communication retry mechanism;

Offline data storage capability;

Recovery mechanism after network interruption;

Remote configuration responsibilities;

Responsibilities for firmware management.

A smart meter running normally in laboratory direct connection testing does not mean that it can still maintain the same communication and integration performance in actual communication networks and data concentrator architectures.