The average US water utility loses 16% of the water it distributes before it reaches a customer meter. That water was treated, pumped, and pressurized. It never generated revenue. It escaped through main breaks, joint failures, service line leaks, and unauthorized use — many of which ran for weeks or months before discovery.
Automated Meter Reading (AMR) solves a specific problem: it eliminates manual meter reads. A drive-by AMR system collects meter readings at walk-by or drive-by intervals instead of requiring a meter reader to access each meter location. That is genuinely valuable for billing efficiency and meter read accuracy.
But AMR does not solve the distribution monitoring problem. Between two AMR readings, the network is a black box. A main break detected on Tuesday was probably leaking since last Thursday. The pressure transient that indicates a valve failure happened at 2 AM Wednesday and was not visible until the next drive-by.
LoRaWAN-based IoT monitoring with IoT SimpleLink creates what AMR does not: continuous visibility into the distribution network between readings.
The Difference Between AMR and Continuous Monitoring
The distinction matters operationally:
AMR: Reads each meter periodically (daily, weekly, or monthly). Provides billing accuracy. Does not provide:
- Consumption anomalies between readings that suggest leaks on service lines
- Distribution pressure monitoring
- Flow balance across the network (water in vs. water accounted for at customer meters)
- Real-time main break detection
Continuous LoRaWAN monitoring: Meters and sensors report on 15-minute intervals (or faster on alarm conditions). Provides:
- Continuous consumption profiles — minute-by-minute patterns reveal customer leaks and unauthorized use
- Distribution pressure across the network in real time
- District Meter Area (DMA) flow balancing — the difference between water entering a zone and metered consumption in that zone is system loss
- Alarm-on-event: a meter reading outside of expected range fires an alert, not just logs a data point
A continuous monitoring system detects the anomaly within 24 hours: consumption that does not follow the customer’s pattern, running continuously through the night hours when normal use would be near zero.
What IoT SimpleLink Manages in a Water Utility Deployment
LoRaWAN-Connected Meters
Modern smart water meters include LoRaWAN radios as a standard or optional feature. Meters from manufacturers including Diehl Metering, Axioma, and others support LoRaWAN Class A transmission — reporting every 15 minutes with consumption data, tamper events, and meter diagnostic codes.
IoT SimpleLink manages the LoRaWAN network layer for the utility’s meter network:
- Gateway provisioning: Utility-owned LoRaWAN gateways are registered and managed centrally. For a municipal utility with several hundred meters concentrated in a service area, 2–4 gateways on elevated infrastructure (water towers, utility poles) typically provide full coverage.
- Meter device registration: Each meter’s EUI and authentication keys are provisioned. OTAA join procedure ensures authenticated, secured connections.
- Data forwarding: Meter uplinks forward to VX-Olympus, where the consumption data is stored and analyzed.
Pressure Monitoring
Pressure sensors at key points in the distribution network provide the operational picture that meters alone cannot:
- Pressure at pump station outlet — confirms pump output against setpoint
- Pressure at zone boundaries — detects pressure drops that indicate active main breaks or significant leaks
- Pressure at elevated storage — tank level monitoring tracks storage adequacy and identifies pump control failures
- Pressure at high-value customer connections — industrial and commercial accounts with specific pressure requirements
Pressure sensors connected via LoRaWAN report every 5–15 minutes during normal operations and on pressure deviation events. When a main break occurs, the pressure signature at surrounding sensors is detectable within minutes — not hours.
District Meter Area (DMA) Flow Balance
A DMA is a defined zone of the distribution network with metered inflows and all customer meters within the zone monitored. The water balance is:
Non-Revenue Water (NRW) = Water Into DMA − Authorized Metered Consumption
If water entering the DMA consistently exceeds what customers are billed for by more than the expected margin, there is unaccounted-for water loss in the zone. This is the primary technique for identifying leak-prone zones before locating individual leaks.
VX-Olympus DMA balance dashboards:
- Display real-time flow balance for each DMA
- Trend NRW percentage over time — rising NRW indicates developing leak activity
- Flag zones where NRW exceeds the target threshold — directing field crews to the priority zone
- Log DMA balance history for performance reporting and regulatory compliance
Night Flow Analysis
The most powerful technique in leak detection is night flow analysis: minimum flow during the hours when legitimate customer use is near zero (typically 2:00–4:00 AM). Any measurable flow in a DMA during this window — after subtracting the expected minimum night use — represents leakage.
IoT SimpleLink’s continuous 15-minute reporting enables automatic night flow analysis in VX-Olympus:
- Flag DMAs where minimum night flow exceeds the threshold
- Calculate the estimated daily volume wasted based on the night flow excess
- Trend minimum night flow over weeks to identify slowly developing leaks
This technique catches leaks that are too small to cause visible pressure changes but large enough to represent meaningful water loss.
Service Line and Customer Meter Monitoring
Individual customer meters on continuous monitoring provide three capabilities beyond billing:
Customer leak notification: A residential meter that shows constant flow during the 2–4 AM window — no occupant use expected — has a potential service line or in-home leak. Automatic notification to the customer prevents a high-bill dispute and builds goodwill with a proactive alert.
Tampering detection: Unusual meter readings, register anomalies, or tamper events from meters with tamper detection sensors flag potential unauthorized use or meter bypass.
High-consumption alerts: A commercial customer whose consumption spikes 300% above their 30-day baseline in a 4-hour window has either a process event or a pipe failure on their property. Early notification helps both the customer and the utility.
Network Design for Water Utility LoRaWAN
Water utility deployments have specific coverage requirements:
Underground meter pits: Below-grade meter installations attenuate signal. LoRaWAN at 915 MHz penetrates soil and concrete meter box lids, but with reduced signal strength. Verify RSSI readings from below-grade meters during pilot deployment — some installations may need SF11–SF12 to achieve reliable connectivity.
Dense urban deployments: Urban meter installations benefit from gateways mounted on utility poles or building rooftops at height. A gateway at 25–30 feet elevation in a dense urban area covers 500–1,000 meters reliably in most configurations.
Rural and suburban utilities: Open terrain provides excellent coverage. A single gateway at a water tower covers the entire surrounding distribution zone in most rural utility deployments.
IoT SimpleLink manages gateway placement and signal quality analysis — the RSSI distribution view shows which meters are connecting at which signal levels, identifying any locations requiring gateway repositioning or additional coverage.
Integration With Billing and SCADA
IoT SimpleLink’s data forwarding connects meter readings and distribution data to:
Utility billing systems: VX-Olympus sends consumption readings to billing system APIs or database connections at billing cycle intervals. Eliminates manual data transfer from the AMR system to billing.
SCADA/LIMS systems: Pressure and flow data from distribution sensors integrates with existing SCADA platforms if the utility has one — VX-Olympus serves as the IoT data aggregation layer feeding the SCADA historian.
Regulatory reporting: Water quality reporting and distribution performance metrics (NRW %, system pressure, meter read accuracy) generate from VX-Olympus data. Export-ready reports for state regulatory submissions.
The Outcome
LoRaWAN changes the economics of utility-wide continuous monitoring. A 5,000-meter utility network on LoRaWAN uses 8–12 gateways instead of 5,000 cellular data plans. The continuous data collection that was cost-prohibitive on cellular is routine on LoRaWAN.
Talk to our team about a water utility LoRaWAN deployment scoped to your service area and meter count.