AMI data alongside the rest of your network — not in a separate silo.

The challenge

Smart-meter rollouts deliver impressive demos and stalled programmes. The meters arrive, the AMI vendor stands up a portal, and three years later that portal is still the only place the data lives. Cross-referencing meter usage with hydraulic data, billing exceptions, or quality alarms requires a CSV export and a spreadsheet.

The integration project keeps slipping because the vendor's API is bespoke, the IT team is stretched, and there's no internal platform to land the data into anyway.

What success looks like

How WaterTwin delivers it

• Standards-based meter ingestion — MQTT-native broker (EMQX), with first-class Sparkplug B support and OPC UA bridges for SCADA gateways. Your meter vendor's existing edge nodes connect with the same pattern as any IIoT device.
• Per-device credentialing — every meter gets its own MQTT username, TLS certificate, and ACL. No shared broker credentials, no cleartext.
• Multi-tenant access control — Super Admin sees everything; each region or service area has a Tenant Admin who manages their own users and assets without seeing other regions' data.
• Time-series history at meter resolution — every interval reading retained for billing reconciliation, leak inference, and consumption-pattern analysis.
• Alarms that combine meter and network signals — a billing-system exception combined with a DMA flow drop gives you a leak hypothesis you wouldn't see in either tool alone.
• REST API and SignalR for integrations back into your billing system, CRM, or BI platform.

A typical rollout pattern

1. Validate the meter vendor's MQTT or Sparkplug topology against WaterTwin's ingestion. Most modern AMI heads "just work" — we've not yet seen one that didn't bridge.
2. Configure the per-device provisioning flow so each new meter gets credentials automatically when commissioned.
3. Set up tenants matching your operational regions or service areas; assign their admins.
4. Wire the time-series store into your billing reconciliation process — usually the first place ROI shows up.
5. Layer in cross-signal alarms (leak inference, consumption anomalies, meter health) as confidence builds.

Where the value lands first

• Billing-system reconciliation — the gap between AMI usage and billed usage is the most-watched number; getting it into one place pays back the integration immediately.
• Customer-side leak detection — meter-level consumption spikes flag household leaks the customer hasn't noticed yet.
• Demand forecasting — high-resolution consumption time-series feed planning models that previously ran on monthly averages.
• Meter health — a meter that stops reporting is itself an alarm, not a hidden gap.