Smart-meter RFQs: separate DLMS/COSEM, cellular uplink and local access

Begin with the information the operator needs

List the measurements, registers, event records and reading intervals required by the project. Separate monitoring from any remote disconnect or tariff function. Include the electrical installation type and the exact meter configuration the qualified metering team needs to review. A catalogue described as “smart” may offer only some of those functions, and optional communication modules can change both the configuration and the documents supplied.

Treat the protocol profile as a compatibility requirement

DLMS/COSEM describes metering data and communication arrangements; OBIS identifiers help name the relevant data objects. The DLMS User Association publishes architecture and protocol documentation for this system. A broad protocol label still leaves implementation choices to confirm. Ask the head-end team for the required profile, objects and access method, and obtain the proposed meter’s corresponding documentation. Give the integration test a real reading list rather than accepting a successful connection alone.

Choose the wide-area link for the deployment

A cellular module needs suitable bands, operator service, SIM provisioning and the agreed network arrangement. Other meter systems may use a different field network and a shared concentrator. Keep the topology visible in the proposal. The customer’s telecom and compliance teams should confirm destination requirements for the exact communication module and ordered version. A radio option sold under one family name does not establish suitability in every country.

Describe local access by the field task

An optical port, Bluetooth or Wi-Fi can support a local commissioning or service workflow. Ask what the technician must read or change, which tool is used and which authorization is required. Local access does not automatically form the wide-area meter network, nor does it make the meter readable by the head-end. List local tools, supported software versions and handover responsibilities with the equipment.

Agree account and credential handling early

Identify who provisions devices, manages access and replaces credentials when ownership or service arrangements change. Exchange sensitive configuration through the agreed secure channel. Use test credentials for compatibility trials and document how production setup differs. Also establish what happens after a meter replacement: device identity, site association and historical records should remain understandable to the operator.

• Name the head-end owner and required meter profile.
• Keep local service permissions separate from remote access.
• Record meter and communication-module versions in the test.

Turn the RFQ into a sample test

Ask the supplier to identify the proposed model and options against each requirement. Verify the applicable model documents rather than accepting only a generic company certificate or catalogue. Test the agreed readings, units, timestamps, security setup and recovery on the intended head-end. Include any control function only under its own approved scope. Send the reading list, head-end details, deployment country and local-service workflow so the selection can focus on compatibility.

Common questions