Smart District Heating brings network visibility, operational analytics, engineering simulation, and reviewed dispatch workflows into one operating context. Teams can connect heat sources, pipelines, substations, buildings, weather, alarms, work orders, and operating records to understand current conditions and prepare the next action.
The product API uses /api/v1/heatops/* and the AI Engine uses /ai/heatops/*. Customer-facing pages use Smart District Heating; heatops appears only in technical identifiers.
Documentation map
Operating model
Capability areas
| Area | Customer workflow |
|---|
| Network operations | Review heat sources, pipelines, station state, spatial load, suspected leaks, pressure, flow, temperature, and data freshness. |
| Forecasting | Compare load and supply-temperature outlooks with weather, operating history, model version, and confidence context. |
| Anomaly and diagnosis | Triage station and network anomalies, review contributing signals, attach root-cause notes, and record false alarms. |
| Hydraulic and thermal analysis | Use a calibrated network graph to compare flow distribution, pressure loss, pipe heat loss, heat delivery, and building thermal response. |
| Severe-weather planning | Compare baseline, cold-weather, preheating, balancing, and equipment-availability scenarios before an operating meeting. |
| Dispatch governance | Route proposed setpoints and valve changes through project constraints, responsible-owner review, audit, rollback, and manual-override procedures. |
| Maintenance loop | Connect findings to Inspector or CMMS work orders and use the completed outcome as model and operating evidence. |
Capability maturity
| Delivery level | Scope |
|---|
| Product workflow | Station and topology views, history, forecasts, anomaly queues, diagnosis context, suggestions, operating logs, reporting, and work-order linkage. |
| Project-configured engineering workflow | Parameter calibration, four-layer network twin studies, hydraulic and thermal scenario comparison, residual review, and severe-weather analysis using approved project data. |
| Controlled automation | Dispatch execution is enabled only when the project has approved write integration, constraints, audit, rollback, and manual override. |
Prerequisites
- Stable IDs for heat sources, pipelines, substations, zones, buildings, sensors, meters, and work records.
- Timestamped supply and return temperatures, pressure, flow, heat, valve, pump, and weather data where available.
- Reviewed unit mappings, sensor quality rules, and source-system ownership.
- A named operations owner and engineering reviewer.
- A project decision on recommendation-only, approved write, and emergency response modes.
| Input | Purpose |
|---|
| Network and asset register | Defines heat sources, pipelines, branches, substations, equipment, zones, and buildings. |
| Operational time series | Provides temperature, pressure, flow, heat, valve, pump, indoor-condition, and meter context. |
| Weather and forecast data | Supports load review, cold-weather scenarios, and update timing. |
| Work and inspection records | Explains outages, maintenance, abnormal readings, field findings, and closure outcomes. |
| Model and parameter package | Versions topology, calibration inputs, solver profile, assumptions, and acceptance criteria. |
Expected output
A completed workflow produces a traceable review package containing source freshness, network scope, forecast or simulation version, assumptions, residuals, recommended action, reviewer decision, execution record, and measured outcome.
Validation checklist
- Network identity matches the source systems and field naming.
- Forecasts and simulations show their data window, model or parameter version, and limitations.
- Recommendations link to the readings and scenarios that support them.
- Operating actions have an owner, approved constraint set, rollback path, and audit record.
- Work-order or operation-log outcomes are returned to the review record.
Failure handling
| Problem | Response |
|---|
| Source identity is unresolved | Keep affected records separated and complete the asset and tag mapping. |
| Data freshness is below the review requirement | Mark the result conditional and repair or replace the affected source. |
| Forecast or simulation evidence is outside acceptance | Preserve the result, review inputs and parameters, and rerun after correction. |
| An action lacks approval or recovery controls | Keep it as a recommendation and assign it to the responsible operations owner. |