Meter Data Management

MDMS vs Head-End System: What Each Does in an AMI Network

A head-end system talks to smart meters; an MDMS validates their reads for billing. See what each does, who owns which task, and how the two connect.
MDMS vs Head-End System: What Each Does in an AMI Network

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
  • The head-end talks to meters: it collects raw reads, sends commands and runs the network.
  • The MDMS validates reads, estimates gaps and sends billing-ready data to billing.
  • Utilities with two meter vendors usually run two head-ends feeding one MDMS.
  • Only one system should set the estimate billing uses: the MDMS.
  • A head-end bundled with its MDMS can tie future meter purchases to one vendor.

A head-end system is the software that communicates with a utility's smart meters: it collects raw reads, sends commands and monitors the meter network. A meter data management system (MDMS) takes those raw reads, validates them, fills gaps and sends billing-ready data to billing and customer service. The head-end belongs to the meter network; the MDMS belongs to the utility's business systems.

Utilities planning AMI often hear both terms in the same vendor meeting, and some vendors bundle the two, which makes the line between them harder to see. The split matters because it decides who fixes a bad read, what happens when you add a second meter vendor, and whether your bills depend on one supplier's network software. This guide explains what each system does, where the boundary sits, how the two connect, and what to ask before you buy either one. It is written for operations leads, IT managers and billing managers at utilities serving 3,000 to 100,000 accounts. For the MDMS side of an AMI project, the SMART360 meter data management module connects to the head-end and validates every read before billing.

MDMS vs Head-End System at a Glance

Both systems sit inside advanced metering infrastructure, described in full in the guide to advanced metering infrastructure. They handle the same reads at different stages.

Head-end system (HES)Meter data management system (MDMS)
Main jobCommunicate with meters and the networkTurn raw reads into billing-ready data
Usually supplied byThe meter or network vendorA software vendor, or the billing platform
Talks toMeters, endpoints, collectorsHead-ends, manual and AMR read files, billing, CIS
Data it holdsRaw reads, events, meter and network statusValidated, estimated and edited reads, with history
Main usersMetering and network techniciansBilling, meter data analysts, customer service
Number per utilityOne per meter network or vendorUsually one, fed by every head-end
If it failsReads stop arrivingBad reads reach bills, or bills are delayed

The split exists because the two systems answer to different parts of the utility. The head-end is built around the meter network: radio protocols, endpoint batteries, collectors and firmware. It changes when the utility changes meter vendors or network technology. The MDMS is built around customers and money: accounts, rates, billing cycles and audit history. It changes when the utility changes rates, adds services or replaces its billing system. Keeping the two separate lets each one change without forcing a project in the other.

What a Head-End System Does

AMI head-end software is supplied with the meter network, and each meter vendor's head-end speaks its own protocol. The AMI software evaluation guide covers how to assess the network side. A head-end typically handles:

  • Meter communication. Scheduling when meters report and retrying meters that miss a window.
  • Raw read collection. Receiving interval and register reads exactly as the meter sent them.
  • Commands to meters. On-demand reads, remote connect and disconnect, valve shutoff where supported, and configuration changes.
  • Firmware and configuration. Pushing updates and settings to meters and endpoints over the air.
  • Network health. Tracking signal strength, battery levels, collectors and meters that have stopped reporting.
  • Event and alarm forwarding. Passing tamper, leak, reverse-flow and outage messages to the systems that act on them.

The head-end does not decide whether a read is correct for billing. It confirms the read arrived; it does not test it against the account's history or the rate. Head-ends also tend to keep only recent data, often a few months, because their storage is sized for network operations rather than for multi-year billing history. The people who use it day to day are metering technicians and network staff, not billing staff.

What an MDMS Does

The MDMS starts where the head-end stops. Its job is to make sure every account has an accurate usage figure for the billing cycle. Its core function is VEE, explained in the guide to VEE in meter data management. An MDMS typically handles:

  • Validation. Checking each read against rules such as high usage, zero read, register decrease and days in period.
  • Estimation. Calculating a value for missing or failed reads, and replacing it when the real read arrives.
  • Editing and audit trail. Recording every manual correction with the original value, user and reason.
  • Multi-source input. Accepting reads from several head-ends plus manual and AMR routes in one format.
  • Billing quantities. Totaling intervals into the values each rate needs, such as usage by time-of-use period.
  • Meter and account sync. Keeping meter-to-account links current through move-ins, move-outs and meter swaps.
  • Long-term storage. Keeping interval history for bill disputes, rate studies and audits.

Who Owns Which Task

Some tasks clearly belong to one system. Others fall in between, and that is where most integration problems start. Agreeing on ownership before go-live avoids duplicate work.

TaskHead-endMDMSNotes
Collect reads from metersOwns
Retry meters that missed a readOwns
Remote connect, disconnect or valve shutoffExecutesRequests, via billing or CISThe business decision comes from billing or customer service
Check a read against usage historyOwns
Estimate a missing read for billingOwnsSome head-ends fill short gaps; the MDMS should decide what billing uses
Store interval history for billingOwnsHead-ends often keep only recent data
Leak and tamper alertsDetectsRoutes to work orders and customer service
Meter swap recordsRecords new meter on networkLinks new meter to account and closes old reads

How a Read Moves from Head-End to MDMS

At most utilities the handoff runs on a fixed schedule, several times a day:

  1. Meter reports to the head-end. The endpoint sends stored intervals and any events over the network.
  2. Head-end confirms receipt. The head-end logs which meters reported and queues retries for those that did not.
  3. Head-end exports reads. Reads and events are sent to the MDMS by API or scheduled file, in the format the integration defines.
  4. MDMS matches meters to accounts. Each meter ID is matched to its active service point; unmatched reads go to a separate queue.
  5. MDMS validates and estimates. Reads are checked against validation rules; gaps are estimated and labeled.
  6. MDMS holds exceptions for review. Suspect reads wait in a review queue with the account history attached.
  7. MDMS releases data to billing. Billing-ready quantities move to the billing engine before the bill run.

Timing matters at each step. If the head-end exports once a night, a read taken in the morning reaches the MDMS the next day. That is fine for monthly billing but too slow for a same-day move-out read or a leak alert. Many utilities run a nightly bulk export for billing and a separate event feed for alarms, so urgent messages do not wait for the next file.

How the Two Systems Connect

The head-end to MDMS link is the integration that decides how quickly and reliably reads reach billing. The AMI and MDM integration guide covers the full chain to billing. Four connection methods are common.

Connection methodHow it worksStrengthWatch for
Pre-built connectorThe MDMS vendor maintains an integration for a named head-endFastest to set up; vendor keeps it currentConfirm the exact head-end name and version
REST APIThe MDMS pulls reads from, or receives reads pushed by, the head-end APINear real time; flexibleNeeds development and monitoring
Scheduled file transferThe head-end exports CSV or XML files on a scheduleSimple; works with older head-endsDelays and failed files can go unnoticed
Industry standard messagesMessages defined by IEC 61968-9 or MultiSpeakCommon vocabulary across vendorsEach vendor supports a different subset

One Head-End, Several Head-Ends, or Bundled

How many head-ends a utility runs shapes the MDMS decision. The guide to meter data management systems explains the MDMS layer in more depth.

SetupWhat it looks likeMain risk
One head-end, separate MDMSOne meter vendor; MDMS from another supplierLow; adding a second vendor later is simple
Several head-ends, one MDMSTwo or more meter vendors, often during a rollout or after an acquisitionLow, if the MDMS has connectors for each
Head-end with bundled MDMSThe meter vendor supplies bothChanging meter vendors can mean replacing the MDMS too
No MDMSThe head-end exports reads straight to billingBilling receives reads no one has validated

Utilities mid-rollout often run a second head-end, or keep manual and AMR routes for meters not yet converted. An MDMS that accepts every source keeps one bill run for the whole service area.

What Changes When You Add a Second Meter Vendor

Adding a second meter vendor is the moment when the split between head-end and MDMS matters most. It happens more often than most utilities plan for: a vendor discontinues a meter model, a better price comes up in the next bid, or the utility acquires a neighboring system that uses different meters.

With a separate MDMS, the work is limited to the new network. The new vendor's head-end is installed, the MDMS adds a connector for it, and reads from both head-ends land in the same validation rules and the same bill run. Billing, rates and customer service do not change.

Without a separate MDMS, or with an MDMS bundled into the first vendor's head-end, the second vendor's reads have nowhere common to go. The utility either builds a second path into billing, with its own validation and its own exceptions, or replaces the bundled MDMS. Either option turns a meter purchase into a software project.

Signs the Boundary Is in the Wrong Place

These problems usually mean a task is sitting in the wrong system, or in neither:

  • Billing staff log into the head-end to check reads before the bill run.
  • Estimated reads differ between the head-end and the bill, and no one can say which is correct.
  • A meter swap creates two partial bills because the head-end and billing were updated separately.
  • Leak alerts stay in the head-end and never become a work order or a customer notice.
  • Adding a meter vendor is quoted as a billing project, because the billing system was built around one head-end's file format.

How to Evaluate the MDMS and Head-End Split

Most utilities choose meters and the head-end first, then the MDMS. Four questions test whether the two will work together.

Does the MDMS have a pre-built connector for your head-end, by name?

"Supports AMI" is not the same as a maintained connector for your head-end and version. Ask for the list.

Which system decides the estimate billing uses?

There should be one answer. If both systems estimate, the MDMS should own the final billing value and keep the head-end's raw data for reference.

Can the MDMS accept manual and AMR reads alongside AMI?

A rollout takes years. Unconverted meters still need to be validated and billed in the same cycle.

What happens to your MDMS if you change meter vendors?

If the answer involves replacing it, the head-end and MDMS are bundled, and your next meter purchase is tied to one supplier.

Where SMART360 Fits

SMART360 is the MDMS layer, not a head-end. It connects to the head-end through pre-built connectors for Neptune, Itron, Kamstrup and Sensus, and validates every read before it reaches billing, whether it came from AMI, a manual route or a photo read in the field app. SMART360 Next checks every read against six validation rules, with thresholds set by zone, meter type, customer class and season. Flagged reads go to an exception queue, and missing reads are estimated and trued up on the next real read.

Because meter data, billing and customer information run on one platform, there is no separate MDMS-to-billing integration to maintain, and a "Can we bill?" check confirms every service is ready before each run. 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 head-end would connect, see SMART360 meter data management in action.

Frequently Asked Questions

What is a head-end system in AMI?

A head-end system is the software that communicates with smart meters over the AMI network. It schedules and collects meter reads, sends commands such as remote disconnect, pushes firmware updates and monitors network health. It is usually supplied by the meter or network vendor.

What is the difference between an MDMS and a head-end system?

The head-end collects raw reads from meters and manages the network. The MDMS validates those reads, estimates gaps, stores history and sends billing-ready data to billing and customer service. The head-end answers "did the read arrive?"; the MDMS answers "is the read right for the bill?"

Can a utility use a head-end system without an MDMS?

It can, by sending head-end exports straight to billing, but the reads are not validated against account history first. Most billing systems were built for one read a month and cannot store or check interval data, so errors reach bills.

Does each meter vendor need its own head-end?

Usually yes. Each meter vendor's network uses its own head-end software. A utility with two meter vendors typically runs two head-ends feeding one MDMS.

Is AMI head-end software the same as AMI software?

Not always. AMI head-end software refers to the network communication layer. "AMI software" is sometimes used for the whole stack, including the MDMS and analytics. When comparing vendors, ask which layers each product covers.

Read More On This Topic