Read the meter's own energy total, retain its identity and timestamps, and prove that recorded consumption agrees with the source meter. For district heating, define which circuit each meter measures before comparing buildings or estimating network losses.
Remote acquisition is not just a number-moving exercise. A plausible value can still be the wrong tariff, an old historical register, a volume total mistaken for energy, or a fresh timestamp attached to stale data. The monitoring record needs enough context to detect those failures.
Define the measurement boundary first
A heat network can have meters at the energy centre, network branches, building inlets, apartments or heat-interface units, and domestic-hot-water circuits. Draw the hydraulic boundary and name the circuit represented by every meter before comparing totals.
The difference between plant output and downstream totals is initially an unexplained balance residual. Storage changes, uncovered branches, unmatched time periods, missing readings and measurement uncertainty all contribute. A residual is not automatically distribution loss, and a return-temperature trend is an investigation signal rather than proof of a particular fault or saving.
Build a record contract
For each point, state exactly what it means and how continuity will be protected.
| Record | Preserve | Reject or investigate |
|---|---|---|
| Energy total | Meter identity, heating or cooling, tariff, unit, scale and current or historical selector | Wrong storage record or unexplained decrease |
| Volume total | Unit, scale and counter continuity | Treating cubic metres as thermal energy |
| Flow or power | Whether it is instantaneous or averaged, plus source time | Comparing unsynchronised measurements |
| Flow and return temperatures | Sensor positions, identity and units | Swapped sensors or the wrong circuit |
| Meter status | Raw code and model-specific meaning | Clearing a meter fault merely because communications recovered |
| Pulse count | Weight convention, raw count, baseline and known modulus | Reciprocal scaling, duplicates or an unexplained reset |
OMS record descriptors distinguish units, storage numbers, tariffs and functions. Preserve those distinctions instead of flattening every plausible value to a generic energy point. Exact records remain meter- and module-specific.
Keep the meter's calculation authoritative
Where the meter exposes cumulative heating or cooling energy, record that value. Its calculator combines the matched temperature pair, flow measurement and configured fluid model. A separate approximation can reveal a sign, unit or order-of-magnitude error; it does not recreate legal metrology.
For water in a suitable single-phase range, an illustrative sensible-heat check is:
thermal power (kW) ≈ density (kg/m³) × specific heat (kJ/kg·K)
× flow (m³/h) × temperature difference (K) ÷ 3,600
Fluid properties, installation, small temperature differences and timing alignment limit this check. Energy requires integration over elapsed time. One power reading does not establish interval energy.
Choose M-Bus, pulse or Modbus deliberately
Wired M-Bus can expose several identified registers and status values. Its commissioning guide covers electrical margins, addressing and record mapping. Modbus can expose a similarly rich model, but register address, type, byte order, scale, unit and access semantics must come from the exact meter map.
A pulse output commonly represents one configured quantity. An energy pulse carries a quantum of the meter's calculation; a volume pulse does not establish thermal energy. Record whether the convention is kWh per pulse or pulses per kWh. They are reciprocals, not interchangeable labels. Use the pulse scaling calculator before commissioning.
Preserve four different clocks
Do not describe every interval as the “reading interval”. Separate:
- the meter's physical measurement and register-update interval;
- the gateway's polling interval;
- the interface's reporting or transmission interval; and
- the storage or display aggregation interval.
Preserve meter time when it is available, acquisition time, time-zone or offset and the timestamp's provenance. A fifteen-minute report does not prove fifteen-minute measurement or billing suitability.
Make missing and discontinuous data visible
Missing is not zero. A useful quality model distinguishes fresh, stale, meter error, communications failure, duplicate, reset or replacement, and unresolved discontinuity. Good communication does not clear the meter's own fault.
If a counter has a documented modulus M and one wrap is independently confirmed, the delta is (M − previous) + current. A falling total can also mean replacement, reset, a different register or corrupt data, so never infer a wrap from arithmetic alone. Reject an interval where multiple wraps or identity continuity cannot be ruled out.
Three illustrative calculations show the distinction:
12,345.6 → 12,349.1 kWhin exactly 15 minutes is3.5 kWh, equivalent to14 kWaverage over that period, not an instantaneous power reading.0.1 kWh/pulse × 37 pulsesis3.7 kWh. Sparse pulses can create stepped short-interval rates even when physical flow is continuous.9,998 → 3with a known modulus of10,000and a confirmed single wrap is5increments. The same readings after a meter replacement must not use wrap arithmetic.
Reconcile against the source meter
Compare the same meter, register, unit, tariff, direction and bounded period. Record source and destination values at both endpoints where practical. Allow for display resolution, pulse quantisation and asynchronous update times; an exact decimal match at one wall-clock instant can be the wrong acceptance rule.
Agreement verifies the acquisition path. It does not calibrate the meter or establish that the installation and remote-reading chain are approved for billing. The EU Measuring Instruments Directive distinguishes complete heat meters and their subassemblies; applicable approvals and national rules still need separate confirmation.
Commission failure, recovery and replacement
Prove normal readings first, then disconnect or interrupt one approved test point. Verify that stale data is marked, healthy meters continue, duplicates are not added on retransmission, totals survive restart and the recovery does not fabricate missing interval detail from a later cumulative value.
When replacing a meter, create an explicit identity and baseline change. Do not let a new device silently inherit the prior counter. Retain the meter model and serial, circuit sketch, output module, raw example, record map, baseline, clock policy, quality rules, continuity handling, display reconciliation, owner and date.
Continue with the wired M-Bus application guide, the pulse acquisition guide, or open System Builder with the meter list and circuit boundaries.
Frequently asked questions
Which heat-meter value should an energy monitoring system record?
Record the meter's own cumulative heating or cooling energy register, together with meter identity, unit, scale, tariff or storage selector, timestamp provenance and status. Volume, flow, power and temperatures are useful supporting records but are not substitutes for the meter's calculated energy.
Can a remote heat-meter reading be used for billing?
A successful remote reading and agreement with the display do not establish billing approval, legal-metrology compliance or approval of the complete remote-reading chain. Confirm the exact meter approval, installation and applicable national requirements separately.
Does the difference between plant output and building totals equal district-heating network loss?
Not automatically. It is initially an unexplained balance residual. Timing, storage, uncovered branches, missing data, meter uncertainty and different measurement boundaries must be reconciled before attributing the difference to distribution loss.
Working out what this needs on your own site? Answer a few questions