Get Started with Smart District Heating
Begin with one operating area and one decision loop. A practical first scope is a heat source, a connected branch, several substations, their weather and operating history, and the work records used to explain abnormal conditions.
Prerequisites
| Requirement | Owner |
|---|---|
| Network and site boundary | Heating operations owner |
| Source-system access | SCADA, meter, weather, and integration owners |
| Asset and station identity | Asset or master-data owner |
| Data quality rules | Data engineer and operations reviewer |
| Forecast or simulation acceptance | Heating engineer |
| Action and rollback policy | Operations and control-system owners |
Choose the first workflow
| Starting goal | Recommended scope |
|---|---|
| Daily operating review | Station freshness, load outlook, open anomalies, active suggestions, and work-order state. |
| Network imbalance review | One branch with known topology, flow, pressure, temperature, valve state, and representative building response. |
| Cold-weather preparation | A reviewed baseline plus weather, load, supply-temperature, and building thermal-inertia inputs. |
| Equipment reliability | Pumps, heat exchangers, valves, and meters linked to Predictive Maintenance and work-order history. |
Implementation flow
Procedure
- Record the heat source, branch, stations, buildings, time window, and operating question.
- Map source tags to stable asset and station IDs through the project integration or DFS workflow.
- Confirm units, timezone, sampling interval, missing-value rules, and maintenance periods.
- Open the system overview, station summary, topology, and station history in read-only mode.
- Select one forecast, anomaly, or engineering scenario and define its acceptance evidence.
- Assign the reviewer who can accept, reject, or request more evidence.
- Keep proposed operating changes as recommendations until write integration, safety constraints, rollback, and manual override have passed project acceptance.
- Record the measured result and any work-order outcome.
Acceptance package
The first acceptance package should contain:
- network diagram and in-scope asset list;
- source-to-target mapping and data-quality summary;
- baseline operating period and known maintenance events;
- forecast or simulation input version;
- comparison criteria and reviewer decision;
- action record, rollback instruction, and measured outcome when execution is in scope.
Failure handling
| Problem | Response |
|---|---|
| Station names differ across systems | Resolve aliases in the identity mapping before combining records. |
| Key signals are stale or missing | Keep the workflow read-only, mark the gap, and use a reviewed alternate source. |
| Network topology is incomplete | Limit the study to a verified branch and record excluded nodes. |
| Forecast or simulation cannot be accepted | Preserve the run and residuals, then update data, parameters, or acceptance criteria. |
| An action lacks rollback or manual override | Keep it as a recommendation and route it to the control-system owner. |