Smart Utilities
Phoenix Smart Water Technology: From Metering to Leak Analytics
Published by IOT Phoenix Research & Editorial Team

- Step 1: Metering
- Step 2: Communications
- Step 3: Data Platforms
- Step 4: Leak Analytics
- Step 5: Irrigation and Landscape
- Step 6: Buildings and Cooling Systems
- Evaluating a Smart Water Program
- Example: A Multifamily Owner Cuts Overnight Flow
- Risks and Trade-offs
- What Comes Next
- Water Quality and Pressure: The Other Sensors
- Pressure Management and Pumping
- The Human Side of Smart Water
- Questions to Ask a Vendor
- Sources
Water technology in the Valley has moved from reading meters once a month to listening to pipes, analyzing patterns, and alerting people before a leak turns into a flood or a bill nobody expected. This article follows the technology chain from the meter at the curb to the analytics that interpret its data, and explains what each step does, what it costs, and where claims should be tested. It is written for facility managers, property owners, utility staff, and curious residents. The aim is practical: how to tell whether a smart water program will actually save water and money in a desert city.
Step 1: Metering
Everything begins with measurement. Traditional meters are read by a person or a drive-by radio at long intervals. Advanced metering infrastructure, or AMI, adds communications so that meters report readings several times a day. Newer meters use ultrasonic or electromagnetic measurement with no moving parts, which keeps accuracy high at low flows, where mechanical meters tend to under-read. The City of Chandler has said its system is expected to go live in 2027, using gateway collectors on poles and offering customers a portal with daily use and leak alerts. It is one example of how a Valley city is building the metering layer. Our guide to smart water meters covers what residents can expect.
| Meter Approach | How It Reads | Strengths | Limits |
|---|---|---|---|
| Manual read | Technician visits | Low technology cost | Monthly data only, labor heavy |
| Automatic meter reading | Drive-by or walk-by radio | Faster collection | Still infrequent data |
| AMI | Fixed network or cellular | Frequent data, leak alerts, billing accuracy | Higher cost, network to maintain |
| Submeters | Private meters inside a property | Tenant billing, irrigation and cooling tracking | Owner must manage the data |
Step 2: Communications
Meter data must travel. Options include fixed radio networks owned by the utility, cellular modems, and low-power wide-area networks. Utilities weigh coverage, battery life (often 15 to 20 years for a meter), cost, and security. A key question for any program is who owns the data path and what happens when a vendor changes or a network is retired. Choose open formats and contracts that guarantee data access.
Step 3: Data Platforms
A meter data management system validates readings, fills gaps, and feeds billing. Analytics layers sit on top and turn raw readings into insight. The useful outputs are simple: a continuous-flow alert, a usage change flag, a district water balance, and a ranked list of leaks by volume. Dashboards should be built for the person who must act, whether that is a utility crew, a property manager, or a homeowner.
Step 4: Leak Analytics
Leaks are the biggest reason to adopt smart water technology, and they come in several kinds.
- Customer-side leaks. Running toilets, broken irrigation lines, and slab leaks. Continuous flow overnight is the telltale sign. The City of Phoenix's May 2026 expansion of a toilet leak detection program at a city-operated housing community uses in-building sensors for exactly this problem.
- Service line leaks. Leaks between the main and the meter, which AMI data and acoustic tools can help locate.
- Main leaks. Larger leaks on utility pipes, found with pressure transients, acoustic sensors, satellite or aerial surveys, and district balance.
- Apparent losses. Meter under-reading, billing errors, and unauthorized use, found by comparing data.
Algorithms look at the shape of consumption over time. A household that never stops using water for 24 hours likely has a leak. A district whose night flow is rising has a growing loss. A mix of statistical rules and machine learning is common, and the best vendors can explain why an alert fired. The City of Phoenix did not publish measured savings for its program, which illustrates a general point: ask for results in gallons and dollars, not just alerts generated.
Step 5: Irrigation and Landscape
In Phoenix, outdoor use is large, so irrigation is a major target. Smart controllers adjust watering using weather and soil moisture, flow sensors detect broken heads and stuck valves, and submeters verify what landscapes actually consume. See smart irrigation sensors and drought restrictions and IoT irrigation for Phoenix parks.
Step 6: Buildings and Cooling Systems
Cooling towers, boilers, pools, and fixtures all use water. Commercial properties can submeter these systems, set alerts for abnormal makeup water, and track water use per square foot. Data centers, as covered in our piece on how Phoenix data centers monitor cooling, power, and water, show how closely water can be tracked when stakes are high.
Evaluating a Smart Water Program
- Define the baseline. Measure current losses or use before installing anything.
- Set a savings target in gallons. Convert to dollars using your actual rates.
- Check accuracy. Test meters and sensors against a reference.
- Plan for response. Alerts that no one acts on save nothing.
- Count total cost. Include network, software fees, installation, and staff time.
- Verify results. Compare use and losses after the program with the baseline.
Example: A Multifamily Owner Cuts Overnight Flow
Imagine a 300-unit apartment complex in the West Valley that pays a large water and sewer bill. The manager installs a submeter at the main service with a data logger and adds leak sensors to a sample of units. The overnight flow report shows the property never drops below a steady baseline, suggesting continuous leaks. Walkthroughs find running toilets in a dozen units and a broken irrigation valve near a parking lot. Repairs cut overnight flow substantially, and a monthly report keeps the issue from returning. The savings pay for the sensors in under a year in this scenario. It is hypothetical, but it matches the pattern the technology is designed for.
Risks and Trade-offs
- Accuracy claims. Check independent test data, not only brochures.
- Battery and network life. Replacement cycles add cost and labor.
- Privacy. Detailed usage data can reveal household habits. Policies must be clear.
- Customer communication. Alerts must be understandable and actionable, and customers need help when leaks are on their side of the meter.
- Equity. Programs should help renters and lower-income households, not only owners who can afford sensors.
What Comes Next
Expect more utilities to roll out AMI, more cities to combine meter data with network sensors, and more private owners to install submeters and leak sensors as conservation pressures grow. The best programs will be the ones that publish what they save. For the infrastructure view, read why connected water infrastructure matters for metro Phoenix, and see IoT leak detection for Phoenix homes and businesses or browse our smart water coverage.
Water Quality and Pressure: The Other Sensors
Smart water technology is not only about meters. Utilities and large buildings also use pressure sensors to find surges that break pipes, online chlorine and turbidity sensors to confirm water quality, and temperature sensors to watch for stagnation in plumbing. In hot weather, water sitting in building pipes can warm and lose disinfectant, so facilities that serve vulnerable people sometimes monitor water temperature and flow at the ends of long pipe runs. Low-use buildings, such as a school in summer, are especially at risk. A flushing program triggered by sensor data can protect water quality while using less water than a fixed schedule.
Pressure Management and Pumping
Lowering pressure at the right times reduces the leak rate in aging mains and cuts the chance of breaks. Utilities use pressure reducing valves and variable speed pumps controlled by sensor data to keep pressure within a safe band. In a city with long pumping lifts and large elevation changes, this also saves energy. The trade-off is that pressure must stay high enough for firefighting and service, so changes need careful modeling and monitoring.
The Human Side of Smart Water
Technology only saves water when someone acts. Utilities need crews to chase alerts, customer service teams to explain them, and outreach programs to help households fix leaks. Renters need landlords who respond, and landlords need clear alerts and simple repair steps. Programs that combine sensors with practical help, such as free repair kits or plumber referrals, tend to produce better outcomes than programs that only send notifications. Plan for these costs from the start, because a smart water project that ignores response capacity can produce more alerts than the organization can handle.
Questions to Ask a Vendor
- What accuracy do your meters or sensors achieve at low flows?
- How long do batteries last in Phoenix heat, and how are they replaced?
- Who owns the data, and can I export it in open formats?
- How do alerts work, and can I tune thresholds?
- What happens if the network or vendor changes?
- Can you show measured savings from a similar desert deployment?
When comparing programs, favor those that report outcomes on a regular schedule, such as gallons saved, leaks fixed, and average time from alert to repair, since these show whether the technology is working in practice.
As a practical next step, pick one site, one corridor, or one district, set a baseline this month, and review results with the people who will do the work. Small, measured pilots build the evidence and the confidence needed for larger investments, and they surface problems while they are still inexpensive to fix.
Sources
- City of Chandler: Advanced Metering Infrastructure
- City of Phoenix: Smart leak detection program expands
