Water and Utility IoT: Smart Metering and Leak Detection

What's inside

The full contents of Water and Utility IoT: Smart Metering and Leak Detection, slide by slide. Read it here, or use the viewer above for the designed version.

1. 02

   Why This Matters Now

   • Aging distribution infrastructure faces rising repair costs and unplanned outages
   • Non-revenue water remains a persistent drag on utility revenue in many systems, industry-reported range typically cited as double-digit percentages of treated supply
   • Regulatory bodies and rate cases increasingly expect demonstrable conservation and loss-reduction programs
   • IoT sensing, connectivity, and analytics have matured enough for grid-wide deployment, not just pilots
   • Utilities that instrument early gain a multi-year head start on data-driven asset planning
2. 03

   Smart Meter Technology: The Building Block

   • Advanced Metering Infrastructure (AMI) meters transmit interval consumption data automatically, replacing manual reads
   • Automated Meter Reading (AMR) is a lower-cost intermediate step: drive-by or walk-by collection without full two-way network
   • Ultrasonic and electromagnetic meters offer better low-flow accuracy than legacy mechanical meters, reducing under-registration
   • Battery life, typically rated in years by manufacturers, and enclosure durability are key selection criteria for buried or pit-set installs
   • Meter selection should be paired with a data architecture decision — not treated as a standalone hardware purchase
3. 04

   Rollout Models: Phased vs. Full-Scale

   • AMR-to-AMI staged migration lets utilities reuse existing meter bodies and upgrade endpoints incrementally
   • Greenfield full AMI rollout suits utilities replacing meters at or near end of life across the service territory
   • District-by-district phasing supports budget cycles and lets field teams build installation expertise progressively
   • Representative example, not a verified case study: a mid-size utility sequences rollout by pressure zone, aligning meter change-out with planned main replacement work
   • Vendor and communication protocol choice at this stage constrains options for a decade or more — evaluate for interoperability, not just initial cost
4. 05

   Real-Time Consumption Data and Demand Management

   • Interval data (hourly or sub-hourly) reveals consumption patterns invisible in monthly or quarterly billing reads
   • Time-of-use visibility supports peak demand shaping and more accurate capacity planning for treatment and pumping
   • Consumption anomalies — continuous flow, zero reads, reverse flow — surface automatically instead of at the next manual read cycle
   • Aggregated demand forecasts improve drought and supply-constraint planning at the system level
   • Data volume grows quickly with interval frequency; storage and analytics capacity should scale with meter count, not lag behind it
5. 06

   Non-Revenue Water: The Core Economic Case

   • Non-revenue water combines real losses (leaks, main breaks) and apparent losses (meter inaccuracy, unauthorized use, billing error)
   • Industry-reported ranges vary widely by network age and geography; each utility should establish its own audited baseline rather than adopt a generic figure
   • Smart metering primarily addresses apparent losses by improving measurement accuracy and detecting tampering or bypass
   • District metered areas (DMAs) paired with smart meters isolate real losses to specific zones for targeted repair
   • Reducing non-revenue water is typically the single largest quantifiable financial driver for an IoT metering business case
6. 07

   Leak Detection: From Reactive to Predictive

   • Acoustic sensors mounted on mains and valves detect the distinct sound signature of pressurized leaks
   • Continuous minimum night flow analysis at the DMA level flags new leaks within days rather than at the next customer complaint
   • Satellite and aerial leak survey technologies complement ground sensors for large or hard-to-access transmission mains
   • Machine learning models can prioritize leak alerts by estimated volume and criticality, focusing crews on highest-impact repairs first
   • Detection speed matters commercially: shorter time-to-detection directly reduces both water loss volume and third-party damage risk
7. 08

   Pressure and Flow Monitoring Across the Network

   • Distributed pressure sensors at critical nodes replace sparse, manually-read gauges with continuous coverage
   • Pressure transients (surges, water hammer) are a leading contributor to pipe fatigue and can now be captured in real time
   • Flow monitoring at DMA boundaries enables water balance calculations that isolate loss zones without full-network excavation
   • Pressure management — actively reducing excess pressure where safe — is a proven lever for extending pipe life and cutting background leakage
   • Integrating pressure and flow data with SCADA gives operations a single operational picture instead of siloed systems
8. 09

   Predictive Maintenance for Pumps and Valves

   • Vibration, temperature, and current sensors on pump stations detect bearing wear and cavitation before failure
   • Valve position and cycle-count monitoring identifies actuators approaching end of service life
   • Predictive scheduling shifts maintenance from fixed calendar intervals to condition-based triggers, reducing both unnecessary service and surprise failures
   • Illustrative scenario: a pump station flags rising vibration trend weeks ahead of a bearing failure, allowing maintenance to be scheduled during a planned low-demand window
   • Asset criticality scoring helps prioritize which pumps and valves receive sensor investment first
9. 10

   Customer Engagement Through Usage Insight

   • Web and mobile portals give customers near-real-time visibility into their own consumption, supporting conservation behavior
   • Automated high-usage alerts help customers catch in-home leaks (running toilets, irrigation faults) before bills spike
   • Granular data supports more transparent billing dispute resolution, reducing call center volume tied to estimated reads
   • Usage insight can be tiered by customer segment — residential conservation messaging differs from commercial demand management
   • Customer trust in metering accuracy tends to improve when usage data is made visible and explainable, not just billed
10. 11

    Integration with Billing and Asset Management Systems

    • AMI data should flow directly into the Customer Information System (CIS) to eliminate manual read entry and reduce billing error
    • Meter data management (MDM) platforms act as the integration layer, validating and normalizing data before it reaches downstream systems
    • Linking sensor alerts to a GIS-based asset registry and work order system closes the loop from detection to dispatched repair
    • Integration architecture should be planned before vendor selection — retrofitting integrations after deployment is materially more costly
    • Data ownership and export rights should be specified contractually so the utility is not locked into a single vendor's analytics layer
11. 12

    Connectivity Choices for Dispersed Infrastructure

    • Low-Power Wide-Area Network (LPWAN) options — including licensed cellular (LTE-M, NB-IoT) and unlicensed (LoRaWAN) — trade off range, battery life, and infrastructure cost
    • Mesh radio networks suit dense urban service areas; point-to-multipoint or cellular suits rural, widely spread service territories
    • Coverage gaps (basements, remote rural mains) often require a mixed-technology approach rather than a single network standard
    • Network ownership model matters: utility-owned infrastructure gives control but requires capital and maintenance; carrier-based connectivity shifts that burden for a recurring fee
    • Connectivity choice should be validated with a coverage survey in representative terrain before committing to full rollout
12. 13

    Regulatory and Conservation Drivers

    • Water scarcity pressures in many regions are pushing regulators toward mandated loss-reduction targets and reporting
    • Rate case proceedings increasingly reward utilities that can demonstrate measurable conservation and loss-reduction outcomes
    • Water loss auditing methodologies (such as those published by industry bodies like AWWA) are becoming a baseline expectation, not a differentiator
    • Cybersecurity and data privacy requirements for connected infrastructure are tightening and should be built into vendor evaluation criteria
    • Early alignment with regulators on reporting metrics avoids rework when compliance requirements formalize
13. 14

    Phased Grid-Wide Deployment Roadmap

    • Phase 1 (Months 1-6): Baseline audit, pilot DMA selection, connectivity survey, vendor evaluation
    • Phase 2 (Months 6-18): Pilot deployment in one or two DMAs, validate data pipeline and leak detection workflow end-to-end
    • Phase 3 (Months 18-36): Scaled rollout by district, prioritizing highest non-revenue water and highest-risk pressure zones first
    • Phase 4 (Ongoing): Full network coverage, predictive maintenance program maturation, continuous improvement of analytics models
    • Each phase should carry a defined go/no-go checkpoint tied to measured outcomes, not calendar dates alone
14. 15

    Next Steps and the Ask

    • Commission a water loss audit and connectivity survey to establish a utility-specific baseline before vendor selection
    • Approve a bounded pilot (one to two DMAs) with clear success metrics: detection time, apparent loss reduction, data integration completeness
    • Form a cross-functional steering group spanning operations, IT, billing, and regulatory affairs to own integration decisions
    • Set a decision checkpoint at pilot completion to authorize phased, grid-wide investment based on measured pilot results
    • Request: budget and executive sponsorship to launch the Phase 1 baseline audit and pilot within this fiscal cycle