
For US Utilities serving 3,000-100,000 meters and for operations team, billing team and utility managers. For Heads of Billing who own collections accuracy and revenue leakage.
Advanced metering infrastructure (AMI) is the combination of smart meters, a two-way communication network, head-end software and a meter data management system that lets a utility collect usage data automatically, usually every 15 minutes to every hour. AMI replaces monthly manual or drive-by reads with reads that arrive daily or more often without a site visit. In 2022, 119.3 million of the 165 million meters in the United States were advanced meters, a 72.3% share (FERC).
AMI is often described as "smart meters," but the meter is only one of four parts. The network, the head-end and the meter data management system matter as much, because they decide whether the data that leaves the meter becomes an accurate bill. This guide explains what AMI is, how its parts fit together, how it differs from AMR, how it works for water, electric and gas utilities, and the questions to answer before a rollout. It is written for utility directors, operations leads and billing managers at utilities serving 3,000 to 100,000 accounts. If you are planning how AMI data will reach your bills, the SMART360 meter data management module shows how reads from AMI and manual routes are validated in one place.
FERC, using the EIA definition, describes advanced meters as meters that record usage at least hourly and send it to the utility at least daily. That data needs four connected parts to become useful.
The head-end belongs to the meter network. The MDMS belongs to the utility's business systems. A utility with meters from two vendors usually runs two head-ends but one MDMS. The guide to meter data management systems covers the MDMS layer in depth.
AMI produces more than a monthly total. The data types a utility receives depend on the meter, but most AMI systems deliver:
Each data type has a different use. Interval reads support time-of-use rates and leak detection. Register reads support billing. Event data supports field work and outage response.
From the meter to the bill, AMI data follows the same path at most utilities. The split between head-end and MDMS responsibilities is explained in MDMS vs head-end system.
AMI is often confused with automated meter reading (AMR). Both use radio, but they work differently. The AMR to AMI upgrade guide covers the transition path step by step.
Many utilities run all three at once during a rollout. The billing process has to accept reads from each method without separate workarounds.
The network is the part of AMI that varies most between deployments. The choice depends on terrain, meter density and whether meters have line power.
The network choice is usually made together with the meter vendor, because each vendor's endpoints are built for specific network types. That choice also fixes the head-end, since each network runs its own head-end software. Utilities with hilly terrain or scattered rural meters often end up with two network types in one service area, for example fixed-base radio in town and cellular endpoints for remote accounts. The billing side does not need to know which network a read came from, as long as the meter data management system accepts reads from every source in one format.
AMI changes daily work in the billing office as much as in the field. With monthly reads, billing staff review a handful of exceptions per route. With AMI, the system receives thousands of reads per meter each month, and staff review only the reads that fail validation. Move-in and move-out reads no longer need a truck; the read for the exact day is already on file. Customer service changes too. When a customer calls about a high bill, the representative can show hourly usage and point to the day the usage changed, which often settles the call before it becomes a formal dispute.
AMI started in electric metering, but water and gas utilities now deploy it widely. The main difference is power: electric meters run on line power, while water and gas endpoints run on batteries, which limits how often they transmit.
For water utilities, the benefit of AMI water meters is often leak detection. An hourly read that never drops to zero shows continuous flow at the premise, which usually means a leak. The utility can alert the customer days or weeks before a high bill.
The benefits of AMI depend on whether the data reaches billing and customer service in usable form. When it does, utilities typically see:
AMI also adds work that a monthly route never had. Planning for these problems early avoids most of the cost. Many of them sit in the connection between AMI and billing, covered in the AMI and MDM integration guide.
An AMI project is a meter, network and software decision at once. The AMI software evaluation guide covers vendor criteria in detail. Four questions shape the plan before any vendor meeting.
Which system will validate AMI reads before they reach a bill?
If the answer is "the billing system," check whether it can handle interval data at all. Most utilities need an MDMS between the head-end and billing.
Can the software accept reads from more than one meter vendor?
A rollout often mixes vendors over its life. Software tied to one head-end makes the next meter purchase harder.
How will reads from meters not yet converted be handled?
Manual and AMR reads will run alongside AMI for years. They need the same validation and the same bill run.
Who on staff will work the exceptions?
AMI cuts field work but adds data review. Plan who owns held reads, leak alerts and communication failures each day.
SMART360 is the system that turns AMI reads into accurate bills. It is not a meter network or head-end: it connects to head-ends through pre-built connectors for Neptune, Itron, Kamstrup and Sensus, and validates every read, whether AMI, manual or photo, before it reaches billing. SMART360 Next checks every read against six validation rules, and thresholds can be set by zone, meter type, customer class and season. Missing reads are estimated and trued up on the next real read.
Because billing, customer information and meter data sit in one platform, customer service sees the same usage data that billing used. Island Water Authority runs its meter-to-bill process on SMART360 and has reached 99% billing accuracy with a 38% faster meter-to-bill cycle. To see how your AMI reads would flow into billing, see SMART360 meter data management in action.
Advanced metering infrastructure is a system that reads utility meters automatically and sends the data to the utility over a network, usually several times a day. It includes the smart meters, the network, the head-end software that talks to the meters, and the meter data management system that prepares the data for billing.
A smart meter is one part of AMI. AMI is the full system: the meters, the communication network, the head-end software and the meter data management system. A smart meter without the rest of AMI cannot deliver data to billing.
AMR uses one-way radio and still needs a vehicle or handheld to pass near the meter each cycle. AMI uses a fixed two-way network, so reads arrive daily or more often without a site visit, and the utility can send commands back to the meter.
AMI water meters send hourly reads that show continuous flow, which points to leaks at the premise. Utilities can alert customers early, take move-in and move-out reads remotely, and answer high-bill calls with hourly usage instead of one monthly total.
Most do. AMI produces thousands of interval reads per meter each month, and most billing systems cannot validate or store that volume. An MDMS validates the reads, estimates gaps and sends billing-ready quantities to billing.
Meter installation usually runs over several years, depending on meter count and budget. The software side, connecting the head-end to an MDMS and billing, can be completed well before the last meter is installed, so billing is ready for the first AMI reads.