Review Smart District Heating Forecasts and Anomalies

Use a single review queue to connect weather and load outlooks with station anomalies, network context, maintenance history, and operator decisions.

Prerequisites

• Fresh station history and approved weather input.
• Stable station, pipeline, equipment, and zone IDs.
• Forecast model version and confidence or error context.
• An anomaly owner and a work-order or operating-log path.

Review flow

Review forecasts

1. Confirm the forecast horizon, weather issue time, history window, and station coverage.
2. Compare the selected forecast with recent actual load and supply-temperature behavior.
3. Review the model version, prediction interval, data gaps, and cold-weather indicator.
4. Check whether outages, holidays, manual control, or topology changes alter the comparison.
5. Record the forecast as accepted, conditional, or rejected for the operating meeting.

Triage anomalies

Evidence	Review action
Supply-temperature deviation	Compare target, measured value, weather, operating mode, and sensor quality.
Efficiency drop	Review primary and secondary temperatures, flow, exchanger condition, pump state, and recent maintenance.
Pressure difference	Check adjacent nodes, pump and valve state, leaks, sensor calibration, and topology.
Flow imbalance	Compare branches and substations under the same operating period and load context.
Valve and temperature relationship	Review command, feedback, delay, actuator condition, and downstream response.
Rapid temperature loss	Check pipe condition, flow, outdoor conditions, meter quality, and work history.

Record the decision

For each accepted finding, store the station or branch, time window, source readings, forecast or anomaly version, contributing signals, reviewer, decision, follow-up, and closure outcome. Mark false alarms and data-quality failures separately so they can improve thresholds and models.

Validation checklist

• The forecast and anomaly use the intended tenant, network, and time window.
• Source timestamps and quality flags are visible.
• Model version and uncertainty are part of the review.
• Diagnosis notes distinguish evidence from operator interpretation.
• Follow-up is linked to an operation log, inspection, or work order.

Failure handling

Problem	Response
Forecast input is incomplete	Keep the result conditional and obtain an approved alternate weather or load source.
Many stations change at once	Review shared weather, source, pressure, topology, and integration events before station-level causes.
Contributing signals conflict	Mark the finding for engineering review and preserve every source timestamp.
Repeated false alarms occur	Review source quality, operating-mode segmentation, thresholds, and model evidence.
No follow-up owner exists	Keep the item open and route it to the operations owner before drafting an action.

Related docs

• Prepare Data and Network Topology
• Predictive Maintenance Operations
• Advisory-to-Work-Order Closed Loop