METER IT
Heat Network Metering

This section shows how accurate metering and transparent billing form the foundation of compliance - and the importance of data.

Grace's experience isn't unique. Across the sector, recurring issues include:

Developers installing meters but no data loggers.
Data collected but locked in unusable formats.
Bulk meters missing from registers.
Probes installed incorrectly, leading to wrong reads.
Billing agents sending estimates rather than real consumption.

Many PMs inherit networks that look fine on the surface but are missing vital data collection, putting them immediately at risk of non-compliance.

Why Metering Matters

Metering is the foundation of compliance and trust.

✓ Legal requirement: Every heat network must be notified to the OPSS (only until January 2026 when Authorisation commences), and have meters installed where viable.

✓ Fairness: Residents expect to pay only for what they use - not for their neighbour’s hot showers.

✓ Performance: Without data, you can’t see whether the system is running efficiently or wasting money.

✓ Billing: Bills must be based on actual consumption wherever possible. If supply meters are installed, monthly billing to ACTUAL DATA is suggested as the “reasonable practice”.

Key Takeaway

“You can’t manage what you can’t measure — and you can’t defend a bill you can’t explain.” (ADE Guidance)

Pain Points & Common Failures

Metering & The Flow of Data

This is the journey of data on a typical mBus metering system. When any of these steps fail - a logger offline, a missing router, no open access to data - PMs lose visibility and residents lose trust.

Please note that this is just an example, there are many other metering systems available.

The heat meter records consumption in kWh.
A data logger captures the readings.
A router pushes that data to a server.
The data collector turns it into usable reports.
A billing agent issues bills and supports residents.

mBus: effective communication protocol for transporting metering data locally. Can be wired or wireless (wired is more reliable)

Data logger: central piece of equipment used to record metering data

Network router: allows for the metering data to be sent via internet to an external location

Data collector: ideally this is a piece of software used to sort the metering data, getting it into the right format before it can be ingested into the billing software. If software is not available, this can be done manually.

d-Analysed:

From Data to Decisions

by Daniel Davies

Collecting data is only the start. The real power comes from what you do with it.

Test tariffs against actual consumption.
Spot anomalies before they turn into disputes.
Track efficiency losses and plan maintenance.
Build a compliance file ready for Ofgem audits.

Metering and data collection isn’t a back-office admin job - it’s the backbone of compliance and good resident relationships.

Checklist: Why Your Metering Setup Might Not be Delivering Data

Property managers often find themselves firefighting billing issues because the data pipeline breaks down. Common causes include:

Meters not installed correctly – poor commissioning or skipped feasibility studies.
Hardware failures – faulty meters, broken HIUs, or failed communication devices.
Lack of remote monitoring – no automated alerts when meters stop reporting.
System integration issues – data not flowing properly between metering, billing, and reporting platforms.
Poor record keeping – missing or inaccurate meter registers at handover.
Neglected maintenance – no programme to check meters remain functional and accurate.
Data validation gaps – anomalies slip through because no one is checking consumption trends against benchmarks.

In 7 out of 10 audits, the problem wasn’t the meter itself but missing or broken links in this data chain. The data you collect today will be the evidence that protects you tomorrow.”

Case Study: When Meters Exist but Data Doesn’t Flow

Background

A mid-rise development had meters fitted in every flat. On paper, it looked compliant. But no routers, no loggers, and no integration with billing meant the data wasn’t leaving the meters.

Consequences

Bills were estimated → resident complaints soared.
Service charges became unpredictable.
No data meant no efficiency checks, no benchmarking, no compliance evidence.

Fix & Lessons Learned

Retrofitted LoRaWAN loggers and data collectors.
Established automated alerts for connectivity failures.
Restored bills based on real use, cutting disputes and giving the PM confidence.

“I’ve seen countless networks with shiny new meters that don’t actually deliver usable data. It’s one of the biggest blind spots for PMs - and the first thing Ofgem will expose.

Daniel Davies - d-Analysed

d-Analysed

Data is the lifeblood of heat networks. Without it, you can’t bill fairly, monitor efficiency, or prove compliance.

Dive into our recent d-Analysed articles for more insights.

Read the Article

Read the Article

Read the Article

Read the Article

A PM's Checklist: What to Ask For

Has your heat network been notified to OPSS? [INSERT LINK]
Is there a register of every meter (with serial numbers and addresses)?
Is there remote access to readings?
Are residents billed on actual consumption?
Do residents get at least two bills a year?
Can you explain the tariff clearly to a resident?