District heating network monitoring
Align plant, network and substation measurements to explain heat delivery, return temperatures, pumping demand and distribution losses.
- Measure
- Plant heat output, branch and substation heat, flow, supply and return temperatures, pressure context, pumping electricity and make-up water
- Calculate
- Delta-T, weather-normalised demand, pumping intensity, non-overlapping heat balances and an explicitly bounded distribution-loss estimate
- Good practice
- Keep meter identity, direction, units, multipliers, legal-metrology status, clock and data quality beside every value
- On site
- ZGW-20 Gateway, retains approved read-only points, local histories, checks and alarms in Edge
Define one heat-network balance before adding detail
Draw the plant outlets, network branches, storage, bypasses and delivery substations as a hierarchy. Each meter belongs to one declared boundary. Use the same interval, direction convention and clock basis throughout, and show unmetered branches and stored heat explicitly. Billing meters remain under the operator's approved metrology process; monitoring copies do not become settlement values.
| Boundary | Evidence to collect | Acceptance boundary |
|---|---|---|
| Heat plant | Heat output by source, fuel or electrical input, auxiliary demand, flow and supply and return temperatures | The plant total covers the declared sources and interval; storage charging, discharge and bypass flows are identified |
| Network | Branch heat and flow, temperatures, pump electricity, pressure context and make-up water | Branches are non-overlapping; missing branches and meter coverage are stated before a loss estimate is produced |
| Substations | Delivered heat, primary flow, supply and return temperatures, valve or pump state and meter quality | Operational telemetry is kept separate from billing, hydraulic control, protection and customer-side responsibilities |
Hardware for heat-network monitoring
Acquire documented heat-meter and controller points read only, and meter suitable electrical auxiliaries independently. Survey meter interfaces, controller roles, network topology, electrical boundaries, point counts and communications ownership before selecting hardware.
Combines approved BACnet/IP and Modbus points with EpiSensor measurements for local history, quality checks and alarms
1 per surveyed plant, network zone or communications boundary point count, network path and wireless coverage checked on site
Use only on a dedicated segment or where its master role is approved
Reads approved heat-meter, flow, temperature, pump and make-up-water registers from a documented Modbus RTU segment
1 per approved RS-485 segment up to 30 configured registers
Modbus RTU master over RS-485, 300 to 115,200 baud
Use only within the product's rated installation boundary
Measures suitable pump, plant-auxiliary or substation electrical boundaries independently
1 per declared three-phase electrical boundary 3 or 4 wire
- Choose the CT rating after surveying the declared low-voltage circuit
Class 0.5S to IEC 62053-22 with calibrated CTs, 0.1 A to 3 kA
Define the point list around the heat balance
Retain raw cumulative heat and volume values as well as instantaneous power, flow and temperatures. Every point needs a stable identity, unit, scale, direction, source timestamp, collection timestamp, quality state and declared parent boundary.
How district-heating measurements reach Edge
Approved heat meters and controllers keep their identities and authority. Edge aligns their read-only values with independent auxiliary electricity measurements without becoming a hydraulic or safety controller.
- Link
- Zigbee
- BACnet
- Edge
- Platforms
| Position | What it tells you | Reference | Sensor |
|---|---|---|---|
| Plant heat output | Cumulative heat and thermal power by source, primary flow, supply and return temperatures, storage state and bypass context | State the production boundary and account for storage charging, discharge and other heat paths before comparing output with delivery JRC district heating indicators | ZMB-31 (on this page) |
| Network and substation delivery | Cumulative heat, thermal power, primary flow, supply and return temperatures and delta-T for each non-overlapping branch or delivery point | EU rules place a meter at the heat exchanger or point of delivery for buildings supplied by district heating or cooling EU Energy Efficiency Directive | ZMB-31 (on this page) |
| Pumping and make-up water | Pump electrical demand, run or speed state, pressure context, make-up-water volume and approved alarms | Trend electricity and hydraulic context together; monitoring does not set pump pressure or prove network integrity JRC heating and cooling study | ZEM-65 (on this page) |
| Weather, time and data quality | Outdoor temperature, heating degree context, operating schedule, meter clock, last valid sample, gaps, resets and communications state | Normalise demand only with a declared weather source, base temperature, period and coverage rule JRC district heating indicators | ZGW-20 (on this page) |
Delta-T needs paired, aligned temperatures. Calculate supply minus return only from points on the same hydraulic boundary and time basis. A low delta-T is evidence for investigation, not a diagnosis of the valve, heat exchanger or customer system.
A loss estimate needs a closed balance. Compare plant output with non-overlapping delivered heat over the same complete interval. State storage changes, bypasses, known unmetered branches, meter uncertainty and missing data; do not silently assign the residual to pipe loss.
Meter identity survives every transformation. Keep serial or asset identity, location, flow direction, unit, multiplier, cumulative reset history, clock source, legal-metrology status and raw value beside each derived series.
District heating monitoring workflow
Begin with read-only acquisition and one reconciled network zone. Add branch and substation detail only where a named operational decision justifies it.
- Compare like-for-like intervals
- Use complete periods with a shared time basis. State outdoor conditions, connected load, operating schedule, plant mix, storage state and known outages beside every comparison.
- Track temperature and flow together
- Review supply, return, delta-T, flow and heat at the same boundary. Keep commands and proven states separate so an operator can distinguish demand, control response and stale telemetry.
- Expose gaps and residuals
- Show missing branches, stale values, resets and the unreconciled remainder. A last-known value must not appear current, and missing heat must not be replaced with zero.
- Keep approved controls authoritative
- Default acquisition to read only. Any setpoint, valve, pump or plant command requires a separate approved control design, permissions, hydraulic and safety limits, fallback behaviour and witnessed functional tests.
Commissioning checks
Commission identities, directions, clocks and boundaries before producing network comparisons or loss estimates.
-
Approve the network boundary map
Trace plant outlets, storage, bypasses, branches and delivery substations; assign every meter to one parent and record flow direction.
Pass when all included heat paths are named, child boundaries do not overlap and every omission is visible.
-
Verify meter identity and scaling
Compare each exported point with the meter or controller display and its approved schedule across zero, normal load and a known change.
Pass when identity, unit, multiplier, sign, cumulative value and quality state agree without undocumented conversion.
-
Prove clocks, intervals and gaps
Compare meter, controller, Gateway and report timestamps through an interval boundary; interrupt and restore one approved feed.
Pass when period assignment is reproducible, gaps remain gaps and stale values cannot appear current or zero.
-
Reconcile one complete period
Compare plant heat with non-overlapping branch and substation totals for the same interval, recording storage change, bypasses and unmetered paths.
Pass when the residual is quantified with coverage and uncertainty, and unexplained differences are logged for investigation rather than labelled as loss.
-
Witness a non-safety alarm
Create an approved test condition such as a stale meter, abnormal delta-T or unexpected pumping load, hold it through its delay, acknowledge it and record the response.
Pass when the correct operator receives the boundary, evidence and quality state, escalation and closure work, and no control command is issued.
Limits of heat-network monitoring
A connected operating record supports investigation and improvement. It does not itself establish billing, hydraulic safety, compliance or the physical cause of a loss.
- Operational copies of heat-meter data are not billing or settlement values. Legal metrology, sealing, verification, tariff and customer-dispute processes remain with the authorised operator.
- Monitoring does not replace hydraulic design, differential-pressure control, plant protection, pressure relief, expansion, water treatment, chemistry control or safety procedures.
- A low delta-T does not identify one fault. Confirm sensor placement and accuracy, flow, valve and heat-exchanger operation, control sequence and customer-side conditions.
- A heat-balance residual is not automatically distribution loss. Account for storage, bypasses, unmetered branches, meter uncertainty, clock misalignment, resets and missing data.
- Temperature trends do not provide thermographic surveys or leak detection. Locate suspected leaks with an appropriate field investigation and competent personnel.
Sources
- Directive (EU) 2023/1791 on energy efficiency (opens in a new tab) (opens in a new tab) European Parliament and Council
- Consumers in district heating and cooling (opens in a new tab) (opens in a new tab) European Commission Joint Research Centre
- Long term projections of large-scale heating and cooling in the EU (opens in a new tab) (opens in a new tab) European Commission Joint Research Centre
- Directive 2014/32/EU on measuring instruments (opens in a new tab) (opens in a new tab) European Parliament and Council
- Modbus Interface datasheet (opens in a new tab) EpiSensor. Specifications, ranges and ordering codes.
Related
Third-party devices for this application
More in the Device Directory: Energy meters (62), Current transformers (7)
Reconcile one network zone first
Send the network schematic, plant and substation meter schedule, controller models, point exports, communications architecture, operating schedules and required decisions. An engineer can define a read-only pilot and its commissioning evidence.