Guide
HES and meter data management (MDM) explained for field teams
The head-end system (HES) talks to smart meters: it collects reads and events, sends commands and knows which meters are communicating. Meter data management (MDM) stores and validates that data and passes it to billing. Field teams matter to both, because a wrong serial or location recorded at installation stops a meter from ever working properly in either system.
Three systems, one meter
A smart meter on a wall in Lucknow or Pune is known to at least three systems:
- Billing, which knows the consumer, the account and the tariff.
- The head-end system (HES), which talks to the meter.
- Meter data management (MDM), which looks after the meter's data.
None of them was there when the meter was fitted. Everything they know about which meter went where comes from the field record. That's why it's worth a field supervisor understanding, roughly, what each system does.
What the HES does
The HES sits at the end of the communication network. Meters talk to it, usually over RF mesh or cellular networks, and it:
- Collects readings, load profiles and events from each meter
- Sends commands, such as connect, disconnect or a configuration change
- Knows which meters are communicating and which have gone quiet
That last point is where field teams meet the HES most often. A meter that stops communicating becomes an NCM (non-communicating meter), and an NCM usually needs a visit. See NCM resolution.
What the MDM does
The MDM receives the data the HES collects and makes it fit to bill. It:
- Stores reads for every meter over time
- Validates them, and estimates or flags gaps and odd values
- Passes clean consumption data to billing
The MDM also needs to know the meter's starting point: which meter replaced which, and with what readings.
How they differ, side by side
| HES | MDM | |
|---|---|---|
| Talks to | Meters, over the communication network | The HES on one side, billing on the other |
| Main job | Collect data, send commands | Store, validate and pass on data |
| Field teams notice it when | A meter won't commission or stops communicating | A first bill looks wrong |
Where the field record comes in
When a technician replaces a meter, five facts decide whether everything downstream works:
- The new meter's serial. If it doesn't match what the HES expects, the meter won't commission. A typo in one digit is enough.
- The premises. The meter has to be linked to the right consumer, or the right meter reads go to the wrong bill.
- The old meter's final reading. Billing closes the old meter on it.
- The new meter's initial reading. The MDM starts the new meter's history from it.
- The installation date. It separates old-meter consumption from new-meter consumption.
Scan serials instead of typing them, take photos that show the serial and readings, and get the record to the HES and MDM quickly. Most "meter not commissioning" calls trace back to one of these five.
Getting field data into the HES and MDM
On many rollouts, installation data reaches these systems as a spreadsheet uploaded in batches, days after the work. Errors are found late, when a crew has long moved on.
The better pattern is to send each installation once a supervisor has approved it, through the systems' API, and to read back whether the HES has the meter communicating. Approved data goes out, communication status comes back, and "installed" and "commissioned" become two separate, visible states.
Doing this in PIEBENCH
PIEBENCH is vendor-neutral on HES and MDM. When a supervisor approves an installation, PIEBENCH fires an event, and Connectorly delivers the record over REST, OAuth or a database connection, with each delivery tracked. The webhook sent on completion can read the HES's reply and flag the installation as communicating. HES lists of non-communicating meters can come back as work orders. See HES and MDM integration.
Built to integrate with your systems
HES, MDM, SAP IS-U, Oracle CC&B and billing systems, over REST, OAuth or a direct SQL connection. How integrations work
Questions buyers ask
What is the difference between HES and MDM?
The HES talks to the meters: it collects readings and events, sends commands such as disconnect, and knows which meters are communicating. The MDM stores and validates the data the HES collects, fills or flags gaps, and passes clean consumption data to billing.
What does a head-end system do in smart metering?
It is the software at the end of the communication network that meters report to. It collects reads, load profiles and events, sends commands such as connect and disconnect, and tracks which meters are communicating. Non-communicating meters it reports often become field visits.
Why does a new smart meter not commission?
Often because the field record does not match what the HES expects: a mistyped serial, the meter linked to the wrong premises, or the record not sent at all. Communication problems at the site are the other common cause. Scanning serials and sending approved records promptly removes most of the first kind.
What installation data should be sent to the HES and MDM?
The new meter serial, the old meter serial and final reading, the new meter's initial reading, the installation date and the premises or consumer it belongs to. Photos and GPS stay in the field system as evidence.
Do field teams need to understand the HES?
Not in technical depth. Supervisors should know what the HES needs from an installation record and what an NCM is, because those two things decide how many crews are sent back to premises they have already visited.
Free trial · no card
See it with your own crew
Start a free trial, or ask us for a walkthrough of your rollout.