Meter data management systems for large utility companies

If your goal is automating meter-to-cash for a utility with millions of smart meters, my top choice would be Oracle Utilities Meter Data Management (MDM)—with Itron IEE MDM and Landis+Gyr MDMS as the strongest alternatives.

The important caveat: the “best” MDM depends heavily on your existing CIS/billing platform, AMI vendors, and whether you want MDM to remain a specialized data layer or become part of a broader utility platform.

My shortlist

Oracle's current product documentation specifically covers high-volume interval/scalar data, automated VEE, bill-determinant calculation, service orders and CIS integration. Oracle also says its customers have more than 64 million meters in production.www.oracle.com

Itron's case is particularly compelling if you're looking for a purpose-built MDM specialist: IEE is deployed on more than 50 million meters, supports electric/gas/water and C&I/IoT data, and is designed for large IOUs.na.itron.com

Landis+Gyr is arguably the strongest competitor on raw deployed scale: it reported in 2024 that its MDMS was processing data from 87 million meters. Its platform supports VEE, exception management, billing extracts, virtual/net metering and standards-based integration.www.landisgyr.com+1

Siemens' current offering is Gridscale X MDM, formerly EnergyIP MDM. Siemens says it is used by more than 200 utilities and is designed for near-real-time processing across electric, gas and water.www.siemens.com

Why I'd pick Oracle for meter-to-cash

For your specific objective—automating the entire meter-to-cash chain, rather than simply storing interval reads—Oracle has the most compelling overall architecture.

A modern flow should look roughly like:

AMI/HES → MDM → VEE → usage calculation → billing determinants → CIS/billing → settlement/customer channels

Oracle explicitly supports this chain. Its MDM performs VEE and usage calculations, calculates/publishes bill determinants, integrates with CIS, and its broader meter platform adds service-order management and smart-device management.www.oracle.com

That's important because the biggest MDM projects don't usually fail because the database can't ingest meter reads. They fail because exceptions, meter events, estimation, device changes, service orders and billing integration remain manual.

Oracle also offers SaaS/cloud deployment, which is attractive if you're trying to reduce the operational burden of running an enormous MDM database.www.oracle.com

Where Itron could beat Oracle

I'd seriously consider Itron IEE if:

• You already have a large Itron AMI footprint.
• Your primary concern is extremely mature meter-data processing.
• You want a relatively vendor-neutral MDM layer but expect Itron to remain a strategic AMI supplier.
• You have complicated settlement/interval-data requirements.

Itron has a particularly credible scale story: its own documentation says IEE has been tested for interval-data collection and processing at 10M+ meters and has more than 50M meters in production.na.itron.com

Where Landis+Gyr could beat both

I'd put Landis+Gyr at the top of the evaluation if your AMI estate is predominantly Landis+Gyr/Gridstream.

Its MDMS is built around high-volume AMI data, VEE and billing preparation, but also has operational capabilities such as outage analytics and theft detection. Its MDUS product provides a direct bridge between smart-metering infrastructure and SAP for Utilities.www.siemens.com+1

That's particularly interesting if your back office is SAP, because the integration architecture can materially affect the economics of the MDM project.

One important point: don't select purely on “meters supported”

The vendors all have credible million-/tens-of-millions-meter scale. The more revealing RFP metrics are:

1. Reads/hour at your projected peak, not theoretical meter count.
2. VEE processing latency for your full meter population.
3. Percentage of reads automatically resolved without human intervention.
4. Billing determinant generation time.
5. Number of concurrent billing cycles.
6. Time to replay/reprocess a day's data after an outage or bad configuration.
7. AMI/HES interoperability.
8. CIS/billing integration.
9. Support for distributed energy resources, net metering and bidirectional meters.
10. Cloud operating cost at your actual interval-read volume.
11. Data retention/archiving costs.
12. Migration strategy from your current MDM.
13. Ability to run AMI 2.0 / near-real-time data without turning the MDM into an operational bottleneck.

Gartner's 2024 Market Guide specifically describes metered consumption data as central to meter-to-cash and highlights the shift toward granular, near-real-time data.www.gartner.com

My recommendation

If I were designing the procurement:

Shortlist: Oracle, Itron, Landis+Gyr, Siemens.

Default winner: Oracle Utilities MDM, particularly if you also want Oracle's broader utility platform and cloud services.

Exception: If you already have a dominant Itron or Landis+Gyr AMI environment, I would not automatically choose Oracle. The integration, operational familiarity and existing meter/network ecosystem can outweigh feature differences.

And I'd make the vendors prove their systems using your actual meter population and a representative 24-hour/30-day AMI dataset, including bad reads, missing intervals, meter exchanges, remote disconnects, net metering and billing-cycle peaks. That benchmark will tell you considerably more than a feature matrix.

If you tell me (1) approximate meter count, (2) electric/gas/water, (3) your AMI vendor, and (4) CIS/billing platform (Oracle, SAP, Salesforce, custom, etc.), I can build a vendor-by-vendor architecture and 100-point scoring matrix and identify which MDM I'd buy for your specific environment.