Smart Metering for AMI & Utility Applications

Remote meter reading focuses on collecting meter data through a defined communication path, while AMR/AMI adds broader field communication, device management and structured data collection. Prepaid metering adds a customer credit, token or vending workflow. A project may combine these routes, but the metering hardware, communication network, data-collection platform and prepaid-service responsibilities should be defined separately before hardware is selected.

No. Meter hardware does not automatically include HES, MDMS, vending, payment, SIM provisioning, cloud hosting or customer-account services. These are separate technical and commercial scopes unless they are explicitly included in the project agreement. The ownership and responsibility for each system layer should be confirmed during project definition.

A remote reading or AMI project should define the meter interface, field network, site topology, device count, gateway or data-concentrator architecture, communication protocol, register map or message structure, data interval and destination platform. For larger AMI deployments, also define HES/MDMS ownership, security requirements, pilot scale, exception handling and rollout acceptance criteria.

Utility and prepaid metering requirements are market- and project-specific. The exact meter model, configuration, certification or compliance documents, communication requirements, prepaid workflow, software integration and local utility specifications should be verified against the destination market before final selection. Website content alone should not be treated as confirmation of local utility acceptance.