Metering Operations on One Platform
One operations view of meter data and the health of every meter and gateway, for a utility that had relied on manual readings and scattered reports.
Project Overview
Part of a partner-led smart metering program for a utility operator. KoderTroop built the platform behind the meters: it ingests meter data from the field, monitors meter and gateway connectivity, and gives operations teams a single dashboard. The architecture applies equally to enterprises running devices across a service area and to meter and gateway manufacturers that need the cloud side built.
The Business Problem
Meter data reached operations from many sources, communication faults were difficult to isolate, and the view of the field depended on manual readings and reports kept in different places.
What We Built
We designed and built the device-to-cloud path: telemetry ingestion, secure communications, operator dashboards, alerting and reporting. Ingestion was kept separate from processing so the utility can add field hardware or change its processes without rebuilding the platform.
The Outcome
Operations teams see meter activity and device health in one place. Investigation, reporting and any later automation now draw on the same data rather than on separate extracts.
Project Details
Inside the Platform
The main screens, walked through one capability at a time.
| Topic | Rate | State |
|---|---|---|
| ami/fdr-03/hourly | 71 | Live |
| ami/fdr-07/hourly | 64 | Live |
| ami/fdr-09/hourly | 88 | Live |
| ami/fdr-11/hourly | 59 | Live |
| ami/fdr-12/hourly | 18 | Short |
| ami/gw/+/status | 480 | Live |
| ami/events/power | 6 | Quiet |
| ami/dlq/rejected | 3 | Review |
| Permission | Grid operator | Field technician | Management |
|---|---|---|---|
| View meter readings | Own sectors | ||
| View device health | Own sectors | ||
| Acknowledge alerts | Own sectors | — | |
| Close alerts | — | — | |
| Add field visit notes | Own sectors | — | |
| Run reports | — | ||
| Schedule reports | — | — | |
| Manage users and roles | — | — |
| When | Change | By |
|---|---|---|
| Today 08:12 | S. Kulkarni added as field technician, Sectors 3–4 | R. Iyer |
| Yesterday 17:40 | Field technician: Close alerts removed | R. Iyer |
| Yesterday 11:05 | M. Joshi moved from grid operator to management | P. Desai |
| 12 Nov 15:22 | A. Rao assigned to Sector 6 | R. Iyer |
| 11 Nov 09:48 | Management: Schedule reports granted | P. Desai |
| Meter | Feeder | Gateway | Last read | Note |
|---|---|---|---|---|
| MTR-12904 | Feeder 12 | GW-12 | Yesterday 21:00 | Gateway offline |
| MTR-12931 | Feeder 12 | GW-12 | Yesterday 21:00 | Gateway offline |
| MTR-07215 | Feeder 7 | GW-07 | Yesterday 14:00 | Weak signal |
| MTR-03388 | Feeder 3 | GW-03 | 2 days ago | Field check booked |
A decoupled MQTT broker layer takes in hourly meter payloads separately from processing.
Technologies & Delivery Models
Tech Stack
The tools we rely on for this layer of the system.
Related Case Studies
Related Work
Insights
- Running Kubernetes at the Edge for Utility GridsAn architecture for running Kubernetes at the edge on low-power utility nodes, using k3s, local autonomy and periodic sync.
- Unified Data Engineering with Microsoft Fabric: Joining OT Telemetry and Enterprise BIHow to bring high-volume IoT and OT telemetry together with ERP data in Microsoft Fabric OneLake, using Delta Parquet storage, Direct Lake reporting and Azure AI models.
- Securing AMI Networks as Smart Meter Fleets GrowHow to secure AMI gateways and smart meters that attackers can physically reach, open and probe.
Services
Industries
Planning a Comparable System?
Tell us about the device, the sites and the systems it has to connect to. A senior specialist will work through the architecture with you.