Meter Data Management

What Is Advanced Metering Infrastructure (AMI)?

Advanced metering infrastructure (AMI) reads meters automatically over a two-way network. See its four parts, how it works, AMI vs AMR, and AMI for water.
What Is Advanced Metering Infrastructure (AMI)?

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.

Key Takeaways
  • AMI is four parts: smart meters, a two-way network, head-end software and an MDMS.
  • In 2022, 119.3 million of 165 million US meters were advanced meters (FERC).
  • AMI sends 15-minute to hourly reads daily; AMR still needs a drive-by each cycle.
  • Hourly AMI water reads reveal continuous flow, an early sign of a leak.
  • Most utilities need an MDMS to validate AMI reads before billing.

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.

The Four Parts of an AMI System

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.

PartWhat it isWhat it does
Smart meter and endpointThe meter, plus a radio or cellular module (the endpoint)Records interval usage, events and alarms; sends them over the network
Communication networkRF mesh, cellular, fixed-base radio or power-line carrierCarries reads from meters to the utility, and commands back to meters
Head-end systemSoftware supplied with the meter networkTalks to meters, collects raw reads, sends commands, monitors the network
Meter data management system (MDMS)Software that sits between the head-end and billingValidates, estimates and stores reads; hands billing-ready data to billing and CIS

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.

What AMI Data Includes

AMI produces more than a monthly total. The data types a utility receives depend on the meter, but most AMI systems deliver:

  • Interval reads. Consumption for each 15-minute, 30-minute or hourly period.
  • Register reads. The cumulative meter reading, usually once a day, used as the billing anchor.
  • Event and alarm data. Tamper flags, leak alerts, reverse flow, power outage and restoration messages.
  • Meter health data. Battery level, signal strength, firmware version and communication status.
  • Command responses. Confirmation that a remote read, connect, disconnect or valve command was carried out.

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.

How AMI Works, Step by Step

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.

  1. Record usage at the meter. The smart meter records consumption in fixed intervals and logs any events, such as a leak alarm or tamper flag.
  2. Transmit over the network. The endpoint sends stored intervals over the communication network, usually several times a day.
  3. Collect at the head-end. The head-end system receives the raw reads, confirms which meters reported, and retries meters that did not.
  4. Pass reads to the MDMS. The head-end exports reads to the meter data management system by file or API on a schedule.
  5. Validate and estimate. The MDMS checks each read against validation rules, estimates missing intervals, and holds suspect reads for review.
  6. Calculate billing quantities. The MDMS totals intervals into the values the rate needs, such as total usage or usage by time-of-use period.
  7. Send to billing and CIS. Billing calculates the charge, and customer service sees the same usage data when a customer calls.

AMI vs AMR vs Manual Reading

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.

Manual readingAMR (drive-by or walk-by)AMI (fixed network)
How reads are collectedTechnician reads the dialVehicle or handheld receives a radio signal near the meterMeter sends data over a fixed network
Read frequencyMonthly or lessMonthly, on the route scheduleDaily or more, with 15-minute to hourly intervals
CommunicationNoneOne-way, meter to collectorTwo-way, meter to utility and back
Site visit neededEvery readEvery read cycle, from the streetOnly for repairs and installs
Remote commandsNoNoYes, such as on-demand reads or remote disconnect
Leak and event alertsFound at next readLimited flags at next readNear real time

Many utilities run all three at once during a rollout. The billing process has to accept reads from each method without separate workarounds.

AMI Network Types

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.

Network typeHow it worksTypical fit
RF meshMeters relay data through each other to a collectorDense service areas with many meters close together
Fixed-base (point-to-multipoint) radioMeters send directly to tower-mounted collectorsMixed urban and rural areas; common for water
CellularEach endpoint uses a public cellular networkScattered meters where building a network costs too much
Low-power wide-area (such as LoRaWAN)Battery endpoints send small packets over long rangeWater and gas meters without line power
Power-line carrierData travels over the electric distribution linesRural electric systems

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.

What AMI Changes for Billing and Customer Service

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 for Water, Electric and Gas Utilities

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.

Water AMIElectric AMIGas AMI
Endpoint powerBattery, often rated for many yearsLine powerBattery
Typical intervalHourly15 minutesHourly or daily
Main operational useLeak detection, continuous-flow alerts, backflow and tamper flagsOutage detection, voltage data, remote connect and disconnectUsage monitoring, tamper flags, remote shutoff where supported
Rate supportTiered and seasonal ratesTime-of-use and demand ratesSeasonal and tiered rates

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.

Benefits of AMI for Utilities

The benefits of AMI depend on whether the data reaches billing and customer service in usable form. When it does, utilities typically see:

  • Fewer field trips. No monthly route, fewer re-reads and fewer estimated bills from missed meters.
  • Earlier leak and tamper alerts. Continuous-flow and tamper flags arrive within hours, not at the next read.
  • Fewer high-bill disputes. Customer service can show hourly usage when a customer calls about a bill.
  • Support for new rate designs. Interval data makes time-of-use, demand and conservation rates possible.
  • Off-cycle reads on demand. A move-in or move-out read can be taken remotely on the day it is needed.
  • Better loss tracking. Water utilities can compare metered totals with production data by zone.

Common AMI Challenges

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.

  • Data volume. A 25,000-meter utility on hourly reads receives about 600,000 interval reads a day.
  • Communication gaps. Some meters fail to report every day, so the MDMS has to estimate and later replace those intervals.
  • Mixed fleets. Rollouts take years, so billing must accept AMI, AMR and manual reads in the same cycle.
  • Billing system limits. Older billing systems were built for one read per month and cannot use interval data.
  • Vendor lock-in. A head-end and MDMS bundled by one meter vendor can make a later meter change expensive.

Questions to Answer Before an AMI Project

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.

AMI and SMART360

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.

Frequently Asked Questions

What is advanced metering infrastructure in simple terms?

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.

What is the difference between AMI and a smart meter?

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.

What is the difference between AMI and AMR?

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.

What are the benefits of AMI water meters?

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.

Does a utility need an MDMS for AMI?

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.

How long does an AMI deployment take?

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.

Read More On This Topic