The water metering gap
Most water meters installed today report once a month — if at all. A technician walks a route, reads a dial, enters a number into a spreadsheet, and that number becomes the basis for a bill. Everything that happened to the water between that reading and the previous one is invisible: slow leaks running for weeks, burst pipes discovered only when a tenant calls, backflow events going undetected until damage is done.
Advanced Metering Infrastructure (AMI) exists to close that gap. It replaces the monthly snapshot with a continuous stream of hourly or sub-hourly data, transmitted wirelessly from each meter to a cloud platform where operators can act on it in real time.
The shift is not just about convenience. Non-revenue water — water that enters a distribution system but never reaches a paying customer — accounts for an estimated 20 to 30 percent of treated water in many municipal networks. Even in well-managed building portfolios, undetected leaks routinely add 10 to 15 percent to monthly consumption before anyone notices. AMI makes those losses visible and addressable.
How modern AMI works
A modern AMI deployment has three layers.
The meter and transmitter layer is where water is physically measured. Smart ultrasonic meters have no moving parts, which means higher accuracy over time and virtually no mechanical wear. An integrated or clip-on LoRaWAN transmitter sends meter readings, alarm flags, and network diagnostics wirelessly at configurable intervals — every 4 hours, every 8 hours, or in near-real-time depending on operator needs.
The network layer carries data from transmitter to cloud. LoRaWAN (Long Range Wide Area Network) is the most widely deployed technology for water metering: it operates on unlicensed radio frequencies, consumes microwatts of power per transmission, and can reach transmitters several kilometres from a single gateway. In areas where LoRaWAN coverage is unavailable or impractical, LTE-M cellular provides an alternative with comparable power efficiency and similar cloud integration paths.
The software layer is where data becomes actionable. A cloud platform like Laqua ingests every transmission, stores the time-series consumption record, and surfaces it through dashboards, alerts, and APIs. Operators see a control center map with every open alarm, consumption graphs for any meter across any time range, LoRaWAN network statistics, and a full alert history with resolution tracking.
What data advanced metering actually provides
The basic output of an AMI system is an indexed series of volume readings — typically the cumulative meter total at each transmission timestamp. From that raw sequence, the platform derives hourly and daily consumption intervals, trend comparisons against prior periods, and anomaly scores.
Beyond volume, modern transmitters report alarm flags that encode physical events at the meter:
- Dry alarm: the pipe appears empty, indicating either a supply cutoff or a meter removed from service
- Leakage: continuous low-level flow detected over an extended period, suggesting a slow drip or fixture left running
- Burst: sudden high-flow event above a configurable threshold, consistent with a pipe failure
- Backflow: reverse flow detected, which may indicate cross-contamination risk or a failed check valve
- Tamper: the meter casing or transmitter has been opened or disturbed
- Low temperature: ambient temperature has dropped to a level that risks pipe freezing
- Garbled register communications: the transmitter can no longer read the meter register cleanly, often indicating a hardware fault
Each alarm type has a different operational response. Backflow and burst events typically trigger immediate field dispatch. Leakage alerts can be scheduled for the next planned site visit. Low temperature warnings prompt preventive action before a freeze occurs. A platform that separates these alarm types, tracks their duration, and records how they were resolved makes that triage systematic rather than ad hoc.
LoRaWAN versus cellular: choosing the right network
The choice between LoRaWAN and LTE-M is mostly a question of existing infrastructure and site geography.
LoRaWAN suits operators who already own or can deploy gateways, who want to avoid recurring SIM card costs, and who are deploying in dense urban or campus environments where a small number of gateways can cover hundreds of meters. A single LoRaWAN gateway placed on a rooftop or utility pole can serve a radius of 2 to 5 kilometres in urban conditions and considerably more in open terrain. The unlicensed spectrum means no carrier dependency and no per-device connectivity fee beyond the platform subscription.
LTE-M suits operators in areas without LoRaWAN infrastructure, who want to rely on existing mobile network coverage, or who are deploying in isolated locations where installing a private gateway is impractical. The tradeoff is a per-SIM cost from the mobile carrier and a dependency on cellular network availability.
Both technologies deliver comparable battery performance for water metering use cases. Transmitters reporting every 4 to 8 hours typically achieve 15 to 20 years of battery life on a standard lithium cell — a critical consideration when deploying hundreds of meters that would otherwise require periodic battery replacement visits.
Occupant portals and the customer experience
AMI is often discussed in terms of operational efficiency for utilities and property managers. The occupant-facing dimension is equally important and frequently underestimated.
When residents have no visibility into their own water consumption, billing disputes are common. A tenant who receives an unexpectedly high bill has no way to verify it, correlate it with a specific event, or identify whether a dripping tap contributed significantly to the total. The result is a call to property management, a manual investigation, and often a credit issued simply to avoid the dispute — none of which required any fraud or error on either side.
A customer portal that shows daily and weekly consumption, compares usage against building averages, and flags anomalies in real time changes that dynamic. Residents can identify their own high-consumption days, correlate them with specific appliances or events, and contact support proactively rather than reactively. In pilot deployments, access to consumption data has been shown to reduce water usage by 5 to 15 percent without any other intervention — simply because people adjust behaviour when they can see the consequences.
The property manager perspective
For property managers overseeing multiple sites, AMI provides something manual meter reading never could: a unified view across an entire portfolio.
Without smart metering, monitoring water consumption across 20 buildings means 20 separate meter-reading schedules, 20 separate billing reconciliations, and 20 separate calls when something goes wrong. An AMI platform consolidates all of that into a single dashboard. The manager sees total consumption per site, active meter counts, open alarms categorised by type, and trend data for each property — from a single screen, without scheduling a visit.
Billing accuracy improves directly. Invoices generated from verified hourly data rather than estimated reads eliminate the correction cycles that consume management time and erode tenant trust. When a tenant disputes a charge, the manager can pull the hourly consumption graph for that unit for any period and resolve the conversation in minutes.
Planning an AMI deployment
Successful AMI deployments share a few common characteristics regardless of scale.
Pilot before you scale. Start with a small, representative sample — 10 to 50 meters covering the range of building types, pipe configurations, and use cases in your network. A pilot exposes integration issues, calibrates alert thresholds, and builds internal familiarity with the platform before you commit to full deployment.
Design network coverage deliberately. For LoRaWAN deployments, map your meter locations against planned gateway positions before installation. Tools like Pilot Things' coverage simulation can estimate signal reach from candidate gateway sites. LTE-M deployments benefit from a site survey confirming carrier signal strength in underground meter pits, which are common signal dead zones.
Define your alert response process. The value of real-time alerts depends entirely on having a defined response workflow. Before deployment, decide which alarm types trigger immediate field dispatch, which go into a scheduled queue, and who receives notifications for each category. Without this, a flood of alerts becomes noise rather than signal.
Communicate with occupants. If tenants will have access to a consumption portal, announce it before launch. Frame it as a tool for them, not a surveillance mechanism. Address privacy questions proactively. Occupants who understand the portal are significantly more likely to use it and to engage constructively with the data it provides.
What the data makes possible over time
Real-time metering data accumulates into an asset that goes well beyond operational alerts.
Year-over-year consumption comparisons reveal seasonal patterns, long-term efficiency trends, and the impact of infrastructure changes or tenant turnover. Anomaly detection algorithms that learn a building's normal consumption profile can flag deviations that would be invisible to a human reviewer looking at monthly totals. Integration with billing systems enables automatic invoice generation, consumption-based cost allocation across units, and variance reports that highlight outliers.
At the municipal scale, aggregate AMI data informs infrastructure planning decisions — where to prioritise pipe replacement, which districts have the highest non-revenue water losses, how demand patterns shift across different parts of the network.
The meters themselves generate that data passively. The only requirement is that the platform be there to receive it, store it, and surface it in forms that operators can act on.
Getting started with Laqua
Laqua is the Pilot Things all-in-one water metering platform — combining LoRaWAN and LTE-M connectivity, a real-time control center map, consumption dashboards, full alarm management, occupant portals, and property manager views in a single cloud application.
Deployments start with a pilot. The Pilot Things team works with you on network coverage planning, meter onboarding, and alert threshold configuration — then scales alongside your deployment as the fleet grows.
Contact the team to arrange a demo or discuss your specific deployment requirements.