Prepare Smart District Heating Data and Network Topology
The operating model depends on consistent network identity and time-series context. Build the source mapping before comparing stations, estimating state, calibrating a simulation, or preparing a dispatch recommendation.
Prerequisites
- Access to approved SCADA, meter, weather, asset, inspection, and work-order sources.
- An owner for asset identity and source-tag mapping.
- A reviewed network diagram or pipeline register.
- Agreed timezone, units, sampling interval, and quality flags.
Data model
Required mappings
| Object | Minimum fields | Useful additions |
|---|---|---|
| Heat source | Stable ID, name, status, source system | Capacity, supply and return boundaries, meter IDs |
| Pipeline or branch | Stable ID, upstream, downstream, length | Diameter, roughness, insulation, resistance, heat-loss parameter |
| Substation | Stable ID, network node, status | Pump, exchanger, valve, meter, served building or zone |
| Building or zone | Stable ID, serving station | Floor area, envelope or load coefficient, thermal capacity, comfort range |
| Signal | Tag ID, asset binding, unit, timestamp | quality flag, calibration date, expected range |
| Work record | Work-order ID, asset or station binding, status | symptom, cause, action, attachment, measured outcome |
Prepare the data
- Export or connect the approved asset, pipeline, station, and tag registers.
- Resolve aliases across SCADA, GIS, ERP, CMMS, and inspection systems.
- Bind signals to the correct source, branch, station, equipment, or zone.
- Normalize temperature, pressure, flow, heat, valve, pump, and weather units.
- Mark sensor outages, maintenance periods, manual overrides, and topology changes.
- Review station and network freshness before enabling forecasts or analysis.
- Create a versioned topology and data-readiness record for the study period.
Quality checks
| Check | Review question |
|---|---|
| Identity | Do all source tags resolve to one intended operating object? |
| Topology | Are upstream, downstream, branch, and serving relationships complete for the selected scope? |
| Time | Are timezone, clock drift, sampling interval, and aggregation rules consistent? |
| Units | Are pressure reference, flow basis, temperature, heat, and energy units explicit? |
| Physics | Do supply and return relationships, flow direction, and plausible ranges pass engineering review? |
| Work context | Are outages and abnormal values explained by work orders, inspections, or operating logs? |
Validation checklist
- Every source tag resolves to the intended operating object or remains explicitly unresolved.
- The selected network scope has complete upstream, downstream, and serving relationships.
- Units, timezone, sampling, and aggregation rules are recorded with the input version.
- Sensor outages, maintenance periods, overrides, and topology changes are visible.
- The operations and data owners have accepted the readiness record.
Expected output
The workflow produces a versioned network model, source mapping, signal-quality summary, excluded-data list, and named data owner. Forecast and simulation runs should reference this package rather than silently reading changing inputs.
Failure handling
| Problem | Response |
|---|---|
| A source tag maps to several assets | Stop the join and resolve the identity with the asset owner. |
| Flow direction changes or is unknown | Mark the affected branch and select a model that supports the reviewed operating state. |
| Pipe parameters are unavailable | Start with engineering priors, record confidence, and calibrate against measured station history. |
| Building response data is incomplete | Use a reviewed zone aggregate and state the excluded buildings. |
| Data changes after a study begins | Create a new input version and retain the prior run for comparison. |