Why MDM Pricing Conversations Feel Opaque
When utility managers consider adding an MDM (Meter Data Management) system the pricing equation may not always be straightforward. That’s because MDM sits between two systems utilities already budgeted for separately: the AMI network that collects meter data, and the CIS that bills against that data.
A variety of questions may arise. What’s included in an MDM quote? What integrations are included? Will a new interface be needed? How is support cost structured? Is baseline-data migration part of implementation or a separate charge? The up-front price looks good, but what happens down the road?
What Drives MDM Pricing
Most MDM pricing comes down to a handful of variables, and understanding each of them helps utilities make a better decision.
Meter count and growth trajectory. The number of active endpoints is a basic pricing driver, but where is that count is headed? Utility managers need to ask how pricing scales as endpoints are added, not just what the current count costs. Is future pricing tiered based on total meters, or simply a flat additional cost per endpoint?
VEE Capability. Validation, Estimation, and Editing (VEE) is a process that catches bad reads, fills data gaps, and allows staff to assess flagged intervals before they reach billing: it is a core MDM function. The level of VEE sophistication and flexibility matters. It’s important to fully understand how it works.
AMI integration. AMI providers may offer some MDM capability as part of their headend. However, what happens if a utility decides to change AMI vendors, or already has more than one type of AMI meter installed? For more on that question see MDM Software for Electric Cooperatives: Why One Size Does Not Fit All The ability to support more than one brand of AMI meter can be a critical factor.
CIS integration. The MDM interface to the Customer Information System (CIS), where customer records reside and billing is done, is another crucial factor. An MDM system must always provide clean data that can be used with confidence for billing. Whether the connection between the MDM and CIS is a true integration, or a more rudimentary interface will make a big difference. It affects both the upfront integration cost and the ongoing support burden.
Common MDM Pricing Structures
MDM vendors generally use a combination of the following pricing components.
The license or subscription fee. This is usually the most predictable recurring cost. It’s the baseline monthly or annual cost for the right to use the product. Other one-time costs related to installation will usually apply as well.
Per meter or per endpoint. Straightforward to forecast when the utility can predict with some confidence what meter counts will look like in the future.
Tiered or flat platform pricing. A set per-meter fee based on how many total meters are installed. Example: the per-meter price may be $X between 20,000 meters and 25,000 meters but go up when the count hits 20,001 meters.
Per read or per transaction. A per-transaction model that looks reasonable today can grow quickly if interval data volume rises.
Data Storage. How much MDM data a utility is required to or chooses to store will be a long-term cost that must be taken into consideration.
Staff training. Especially relevant for smaller utility and cooperative teams where one or two people share MDM administrator duties alongside other duties. On a related note, if the user interface is intuitive and easy to use, less training will be required.
Questions to Ask When Comparing MDM Quotes
Whether the process involves a formal Request for Proposal (RFP) or a more direct vendor conversation, a few questions consistently key to a clear understanding of what the system will cost.
- Is pricing based on current meter count, projected meter count, or read volume, and how does the number change as the deployment grows?
- What is included in the implementation estimate, and what triggers additional charges?
- How is pricing affected if the utility adds a second AMI vendor or switches vendors in the future?
- What does the support tier structure look like, and what response times come with each tier?
- What is the cost of data migration and who validates the data before go-live?
- How often does the vendor revisit pricing, and is any portion of the fee tied to factors outside the utility’s control, such as a third-party data hosting cost?
For a broader framework on working through these questions, How to Evaluate MDM Software: A Decision-Maker’s Framework for Utilities and Cooperatives covers the full evaluation process beyond pricing alone.
¹ CentralView is Central Service Association (CSA) Trademark.
The information presented in this article is intended for general educational purposes. Utility software environments vary significantly. We recommend consulting with a qualified technology advisor to evaluate solutions appropriate to your organization’s specific operational requirements.