What Is Meter Data Management? A Guide for Multi-Site Property Portfolios

If you manage a portfolio of 50, 100, or 300 buildings across Europe, you already have a meter data management problem. You just do not call it that.
“Smart meter data management market size has grown rapidly in recent years. It will grow from 2.08 billion dollars in 2024 to 2.49 billion dollars in 2025 at a compound annual growth rate of 19.8%.” (RESEARCH AND MARKETS, 2025)”
Meter data management started in the utility sector. There, meter data management refers to the software used to collect and validate readings from millions of smart meters for billing and operational control.
That definition is now too narrow.
Today, real estate portfolios face a similar meter data management challenge. Multi-site property owners also manage large volumes of meter data. They also need accurate, traceable records. And under frameworks such as CSRD, they must be able to prove every kilowatt-hour with confidence.
That is where a modern meter data management system becomes critical.
Traditional utility-focused content is written for grid operators, not for commercial real estate teams. The core challenge may look similar, but the context is different. Property owners need a meter data management system that supports portfolio-wide visibility, audit-ready reporting, and enterprise-scale data quality.
This guide explains what meter data management is, how a meter data management system works, and why the traditional utility view falls short for multi-site real estate. You will also learn what a portfolio-grade MDM system should include, how it supports CSRD, GRESB, and BACS compliance, and what to look for when choosing a platform.
What is meter data management?
Meter data management is the structured process of collecting, validating, storing, and distributing data from utility meters across a portfolio. It covers electricity, gas, water, and thermal energy. The goal is a single, trusted record of consumption that every downstream system can rely on.
The discipline started inside electric utilities. As smart meters replaced manual reads, utility companies needed a way to handle the enormous volume of interval data flowing in from advanced metering infrastructure.
A meter data management system, or MDMS, became the centralised single source of truth for meter data, sitting between the field hardware and the billing engine. The meter data management software market is forecast to grow by double digits annually through the decade, according to MarketResearchFuture.
Property owners inherited the same problem from a different angle. A logistics portfolio with 300 warehouses generates meter readings from hundreds of devices across different countries and formats. Without a common data management layer, that information stays fragmented. Enterprise meter data needs the same rigour finance teams apply to the general ledger.
How does a meter data management system actually work?

A meter data management system performs four jobs in sequence: collection, validation, storage, and distribution. Each stage has to work for the platform to be trusted by auditors, investors, and finance teams.
Data collection from any meter, any age, any protocol
Data collection starts at the meter. A meter data management system has to handle electricity, gas, water, and heat meters of every generation. That includes smart meters with native cellular connectivity and legacy devices that only speak M-Bus, Modbus, or pulse output. In a portfolio, meter types are never uniform. Replacing every device is neither practical nor necessary. A modern MDM system connects to what is already installed and reads it in real time or near real time.
Compared with automatic meter reading, full meter data management goes beyond scheduled reads. It lets you monitor minute-level interval data, which is the only way to spot anomalies, after-hours waste, and equipment faults.
Validation, estimation, and editing (VEE)
The next step is data validation. A raw meter read is not yet trusted data. A meter data management system applies a validation, estimation, and editing process, widely known as VEE, to every reading.
Validation checks each read against rules that flag missing intervals, zero values, negative consumption, spikes, static values, or usage outside expected bounds. Estimation fills short gaps using historical profiles or neighbouring devices. Editing logs any manual correction with a full audit trail. Modern meter data management software uses machine learning to refine estimation rules over time, so gaps close tighter each month without manual input.
VEE is the foundation of energy data management quality. Without it, every downstream report is suspect.
Storage in a time-series database with hierarchical models
Once validated, the data has to be stored in a way that supports both long-term reports and real time data analysis. That means a time-series database, organised in a hierarchy: country, site, building, meter. This structure lets you aggregate consumption up the portfolio or drill down to a specific device in minutes.
This is where utility time series data earns its keep. Invoices give you a monthly total. Time-series storage gives you a minute-by-minute record you can audit, benchmark, and act on.
Integration with ESG, billing, and reporting systems
A meter data management system is only useful if the data reaches the tools that need it. That means API-first integration. The platform should push clean, validated readings to ESG reporting tools, tenant rebilling workflows, building automation controls, and your data lake.
An MDM system that cannot integrate cleanly forces manual exports. Manual exports break the audit trail. Broken audit trails fail CSRD assurance. A platform that supports every downstream consumer through a single data contract removes that risk.
Why the utility-grid view of MDM does not fit commercial real estate
Most meter data management software was built for utility companies, not for property owners.
An electric utility uses a meter data management system for one main goal: billing at scale. That is why utility MDM platforms focus on meter-to-cash processes, demand forecasting, outage detection, and grid analytics.
A real estate portfolio works differently.
Property owners need meter data management software for portfolio visibility, audit-ready reporting, and asset-level decisions across multiple sites. That is also why many utility MDM features, especially customer engagement tools, add little value in commercial real estate.
A property portfolio looks different. A few thousand assets, spread across countries, owned by a single enterprise, consuming electricity, gas, water, and heat in parallel. The question is never "can we bill this customer?". It is "can we prove every kilowatt-hour to our CSRD auditor, our GRESB assessor, and our investors?"
The integration targets are different too. A utility MDM feeds a billing engine. A portfolio MDM feeds ESG platforms, internal data lakes, and executive dashboards. The ESG data integration gap that property owners face does not exist in the same form on the utility side.
Fragmented utility data management for real estate is still the norm. Energy reports arrive in different formats from different countries. Auditors refuse to accept invoice-based submissions because an invoice shows a monthly total with no traceability back to individual meters or timestamps. A utility-grade MDM does not solve that, because it was never designed for it.
What a portfolio-grade meter data management system looks like

A portfolio-native meter data management system is built around five principles.
Hardware-agnostic across every meter type
It reads any meter, regardless of age or manufacturer. A logistics operator with 50 buildings will usually have three generations of hardware running in parallel. The MDM system must cover all of it without a rip-and-replace programme. This is what makes an energy data management system portfolio-proof.
A country-to-site-to-building-to-meter hierarchy
The data model matches the structure of the business. You should be able to ask "what is our total electricity consumption in Poland this quarter?" and drill down to a specific warehouse, a specific building, a specific meter, in one click. That is only possible if the hierarchy is designed in from the start.
Audit-ready traceability from sensor to dashboard
Every data point carries a provenance record: which device produced it, when, under what firmware, with what validation status. Auditors can follow the trail from an ESG disclosure figure back to the individual meter read that produced it. This is non-negotiable under CSRD.
Real time data instead of monthly cycles
A utility-grade MDM often runs on bi-monthly or monthly batch cycles. That is fine for accurate billing. It is useless for spotting a gas leak at 3 AM or a lighting circuit that never switches off at night. A portfolio MDM runs on minute-level real time data by default. The €180,000 leak nanoGrid caught at a client site within 24 hours was only possible because the platform runs continuously, not on monthly cycles.
API-first integration with every downstream system
The platform exposes clean REST APIs so ESG tools, BMS software, rebilling systems, and internal analytics all pull from the same validated source. One data contract, many consumers. No exports, no spreadsheets, no reconciliation.
WDP built its portfolio reporting around exactly this model. Across 300+ logistics buildings in six countries, nanoGrid delivers more than 98% data coverage against an industry average closer to 70%, with every reading traceable back to a certified on-site installation.
How meter data management powers CSRD, GRESB, and BACS compliance
Three regulatory frameworks now depend on the quality of your meter data. A portfolio without a proper MDM system will struggle with all three.
CSRD requires an audit trail from meter to report
CSRD demands limited assurance from an independent auditor. Every figure in your sustainability report must be traceable. According to Watershed's CSRD audit guidance, organisations need detailed logs of every data upload, transformation, and estimation method used. Invoices alone do not qualify. An MDM system that records validation status, device provenance, and every editing action is what makes your disclosure defensible. Goodman, Belfius, and other nanoGrid clients now build disclosures on this basis, not on invoice totals.
GRESB scoring rewards coverage, accuracy, and granularity
A stronger GRESB score depends on how much of your portfolio is actually measured, not estimated. An MDM solution that reads every site continuously gives you the coverage GRESB assessors now expect. See our GRESB guide for the scoring detail. Accurate meter data is the single biggest lever most portfolios still have.
BACS compliance under the revised EPBD takes effect in 2026
From January 2026, non-residential buildings with heating, cooling, or ventilation systems above 290 kW must install a class C building automation and control system under the revised Energy Performance of Buildings Directive. From 2030, the threshold drops to 70 kW. BACS compliance requires continuous energy monitoring, fault detection, and optimisation, all of which depend on clean meter data feeding into your BACS layer. That directly supports service reliability and the efficiency targets baked into the regulation. An MDM system is the data infrastructure that makes BACS compliance real rather than paper.
What to look for when evaluating a meter data management platform
Before signing, test the platform against eight questions.
First, does it read every meter type you have today, and every meter you might install in the next five years? Hardware-agnostic coverage is not optional for a portfolio that spans countries and decades.
Second, how transparent is the VEE process? You should be able to see every validation rule, every estimation method, and every manual edit. Opaque data analysis is a CSRD audit risk.
Third, is the data model hierarchical in a way that matches how your business is actually structured? Country, entity, site, building, meter. Anything less and reports become a reconciliation exercise.
Fourth, does the platform deliver real time data, or is it a monthly batch system in real-time clothing? Ask for the refresh interval at meter level, not just at dashboard level.
Fifth, what integrations ship natively? ESG platforms, BMS, billing engines, data lakes. If each connection needs a custom development project, costs will multiply and maintenance will eat your team.
Sixth, who owns the data and the audit trail? You should, not the vendor. Check the contract, not the marketing.
Seventh, is the delivery model hardware-as-a-service, software-only, or on premises? A HaaS model shifts deployment risk to the vendor and keeps the hardware layer maintained at no extra capex. On premises deployments still have a place for specific enterprise security policies, but most portfolios now run cloud based for scale and cost reasons.
Eighth, what security controls protect the data in transit and at rest? Role-based access, encrypted transport, and network segmentation should be standard, with clear audit logs of every user action. Strong data security is what makes the platform safe to expose to enterprise ESG tools, external auditors, and tenant-facing billing services.
Belfius runs its 28% gas-reduction programme across 100+ offices on MDM solutions built to this standard, with efficiency tracked at site level every day and utility systems monitored across the portfolio.
Turning meter data into portfolio-grade infrastructure
Meter data management is not just utility-grid software anymore. For multi-site property owners, it is the foundation every ESG claim, every investor report, and every compliance filing stands on. Fragmented data fails audits. Invoice-based reporting fails CSRD. A portfolio-native meter data management system fixes both, and pays for itself through the waste, leaks, and anomalies it catches along the way.
WDP, Belfius, and Goodman built their energy data intelligence on this foundation. nanoGrid is the infrastructure layer that made it possible, across hundreds of buildings, millions of data points, and every major ESG framework. Ready to see what audit-ready meter data looks like for your portfolio? Book a demo and we will show you.
Frequently Asked Questions about Meter Data Management
What is the difference between a meter data management system and an energy management system?
A meter data management system and an energy management system sit at different layers of the stack. A meter data management system handles the raw data: capture, VEE, storage, distribution. An energy management system sits on top and applies analytics, benchmarking, and optimisation to that data.
You cannot run a useful EMS without a reliable MDM underneath. Many energy management software platforms assume clean data will arrive from somewhere else. In a multi-site portfolio, that somewhere else does not exist by default. The MDM layer is what makes the data reliable enough for the EMS to produce credible recommendations, whether that means cost control, asset monitoring, or tenant rebilling.
Can you use meter data management software if you do not own the meters?
Yes. Most property owners do not own the meters installed by their utility companies. A modern meter data management system reads the meters you already have, whether you own them or not, and builds your own validated record on top.
This is the difference between relying on utility-company reports and owning your data. You cannot control what the supplier sends you. You can control what flows through your own MDM system. For portfolio reporting, investor transparency, and tenant rebilling, ownership of the validated data stream is what counts, not ownership of the hardware.
How long does it take to roll out a portfolio-scale meter data management system?
Rollout time depends on portfolio size and hardware variety, not on the software itself. A single-site pilot can be live in a few weeks. A pan-European portfolio of several hundred buildings typically rolls out over six to eighteen months, site by site, with the platform operational from day one.
