Home » When Your Utility Outgrows Its Meter Data Management Capability

CentralViews

When Your Utility Outgrows Its Meter Data Management Capability

Utility billing analyst reviewing interval data in meter data validation software

When a municipal utility installs advanced metering infrastructure (AMI), the meter vendor often includes basic, embedded meter data management (MDM) functionality. For the first few years, it works well enough. Reads come in, bills go out and the billing team learns which reports they need.

Then things change. The city adds water meters from a different manufacturer. The council approves a time-of-use (TOU) rate. Engineering asks for transformer loading data. An auditor asks how a disputed read was corrected. One request at a time, the embedded MDM that came with the meters falls short.

This article covers signs that your utility has outgrown its current embedded MDM and what to do next.

Why Embedded MDMs Hit a Ceiling

Throughout this article, embedded MDM means the basic meter data management functionality that comes bundled with a meter vendor’s system. A standalone MDM is a separate platform that sits between your head-end systems and your billing system and is not tied to a single meter vendor.

A meter vendor’s embedded MDM is built to support that vendor’s meters. Its main job is to collect reads from the vendor’s head-end system (the software that communicates with the meters) and pass them to billing. That focus works well when a utility has one meter type, one service and simple rates.

However, limitations appear when the utility needs more. Full meter data management, which is what a standalone MDM provides, also includes validation, estimation and editing (VEE), a complete audit trail, multi-service support, and integration with billing, outage and engineering systems. Our article What Utilities Lose With a Bundled AMI Data Interface explains those gaps in detail. The point here is that as requirements change and grow, embedded MDM capabilities stay the same.

That growth is widespread. According to the U.S. Energy Information Administration (EIA), U.S. electric utilities had more than 147 million AMI meters in service in 2025. That is about 87 percent of all electric meters and more than double the count in 2016. As AMI becomes standard, utilities are asking more of the data it produces.

Seven Signs Your Utility Has Outgrown Its Embedded MDM

No single symptom means it is time for a change. When several show up together, your embedded MDM is likely holding your utility back.

The billing team checks reads by hand. If staff export reads to spreadsheets to hunt for spikes, zeros and missing intervals before every billing cycle, the system is not validating data on its own.

Adding a second meter vendor or a new service. Many municipal utilities run electric, water and sometimes gas meters from different manufacturers. An embedded MDM tied to one vendor can’t manage them all.

Interval data volumes keep climbing. Moving from daily reads to hourly or 15-minute intervals can strain current capabilities.

New rates are on the table. TOU, demand and prepaid rates depend on accurate interval data. If you can’t validate intervals reliably, those rates are hard to bill with confidence.

Corrections leave no trail. When a read is estimated or edited, you should be able to see the original value, why it was flagged, the method used and who approved the change. If only the final number is available, disputes and audits get harder.

Other departments want the data. Engineering wants transformer loading and voltage information. Customer service wants usage history for high bill inquiries. Operations wants to spot leaks or tampering, but the data they need isn’t available.

Switching meter vendors feels impossible. If replacing your meters means replacing your meter data system and retraining billing staff, your embedded MDM is outmoded.

Validation Is Often a Key Deficiency

Lack of validation tends to cause the most day-to-day pain. Meter data validation software applies rules to every read before it reaches billing. It compares each read with the account’s own history, with similar accounts and with expected ranges, then flags anything outside the rules. Missing reads are estimated using an approved method. Staff can review and edit exceptions, and every change is recorded.

Without strong validation, errors are caught after bills go out, often by the customer. The result is high bill complaints, rebills, and staff time required for resolution. Our article Validation, Estimation and Editing – the Heart of Accurate Billing explains how a well-designed validation process works and the common gaps to watch for.

For municipal utilities, validation also supports public accountability. A city utility may need to explain a disputed bill to a council member, answer an open records request or support a rate decision with clean data. Validated, auditable reads make each of those easier.

Adding a Service

Consider a city utility that installed electric AMI several years ago and has used the meter vendor’s embedded MDM from the start. The arrangement works until the city approves a water meter replacement program using a different manufacturer.

Now the utility has two options:

  • Run two separate embedded MDMs, each with its own screens, rules and reports, and have the billing team reconcile them every cycle.
  • Move to a single standalone MDM that accepts data from both systems and applies analogous validation rules to each service.

The first path costs less up front but adds work every month. The second takes more planning, but it gives the utility one place to validate, correct and report on all data. It also makes the next meter decision easier, because a standalone MDM no longer depends on which vendor wins the bid.

What Changes When You Move to a Standalone MDM

A standalone MDM sits between the AMI head-end systems and the customer information system (CIS) that handles billing. It does not replace the meters or the head-end software. Instead, it becomes your utility’s single source of validated meter data.

Utilities that make this move typically see changes in these areas:

  • Validation rules are set by service and rate class, so electric, water and gas reads are each checked appropriately.
  • Exceptions are handled in one queue instead of in spreadsheets and email.
  • Every estimate and edit is recorded, which simplifies disputes and audits.
  • Billing receives cleaner data, which means fewer rebills and high bill calls.
  • Other departments can use the same validated data for engineering, outage and customer service work.
  • Future meter vendor changes affect only the head-end connection, not the entire meter-to-cash process.

Planning the Transition

Moving from an embedded MDM to a standalone MDM is manageable when you plan carefully. These steps help:

  • Inventory your meters and services. List every meter type, vendor, head-end system and read interval you support today and expect to support in the next five years.
  • Document your current workarounds. Note every manual check, spreadsheet and report your staff use to fill gaps. These become the requirements for the new system.
  • Decide how much history to bring forward. Validation and estimation work best with historical data, so choose which reads, and how many years, to migrate.
  • Run in parallel before cutover. Compare results from the old and new systems for a billing cycle or two. This builds confidence and catches rule settings that need adjustment.
  • Train beyond billing. Customer service, engineering and operations staff should know what the new data can do for them.

For a full set of evaluation criteria, see How to Evaluate MDM Software: A Decision-Maker’s Framework for Utilities and Cooperatives.

Where CentralView MDM Fits

CentralView[1] MDM is a standalone meter data management platform built by Central Service Association (CSA). It supports electric, water and gas metering from one platform, works with major AMI providers and can be deployed alongside your existing billing system. Utilities that also use CentralView CIS get a tightly integrated meter-to-cash process.

If your current embedded MDM is starting to feel small, our team can help you assess where your utility stands and what a transition would involve.

Talk to a CSA MDM Specialist

The information in this article is for general educational purposes. Utility software environments vary significantly. We recommend consulting a qualified technology advisor to evaluate solutions for your organization’s specific operational requirements.

[1]CentralView is a trademark of Central Service Association (CSA).