Review Smart District Heating Dispatch Safety and Evidence
Use this workflow to move a forecast, anomaly finding, or simulation result into an accountable operating decision. The same review path applies whether the outcome is an inspection, a work order, a manual adjustment, or a project-approved control-system action.
Prerequisites
- Named operations approver and execution owner.
- Project-approved constraints for each controllable parameter.
- Readback, audit, rollback, and manual-override procedures.
- Stable links to station, equipment, scenario, and work records.
- A method for recording the measured outcome.
Decision flow
Review a recommendation
- Confirm the source evidence, network scope, time window, and recommendation version.
- Review requested supply temperature, pressure, flow, valve, ramp, schedule, and affected-zone values that apply to the project.
- Run the project constraint check and inspect warnings, blocked values, and any adjusted values.
- Compare the recommendation with current equipment state, active work, manual overrides, and weather updates.
- Record approval, rejection, requested change, execution owner, and expiration time.
- Execute through the approved operating path.
- Verify command readback, station and zone response, alarms, comfort evidence, and rollback conditions.
- Link the outcome to the operation log, work order, forecast, anomaly, or scenario record.
Minimum evidence record
| Field | Purpose |
|---|---|
| Source record | Links the decision to a forecast, anomaly, simulation, or operator finding. |
| Input and model version | Reproduces the recommendation context. |
| Constraint result | Shows passed, warned, blocked, or adjusted parameters. |
| Approver and executor | Establishes accountability. |
| Action and readback | Records what was requested and what the control system reported. |
| Rollback and override | Shows the available safe recovery path. |
| Measured outcome | Captures temperature, pressure, flow, heat, comfort, alarm, and work result as applicable. |
Execution modes
| Mode | Use |
|---|---|
| Recommendation only | Default for early deployment, uncertain data, or incomplete control integration. |
| Approved manual action | An operator applies the accepted recommendation through existing procedures. |
| Controlled write integration | A project-specific integration writes after approval and returns command and state evidence. |
| Emergency response | Existing control and manual procedures take priority when triggers or safety conditions require them. |
Validation checklist
- The recommendation still matches the current weather, equipment, and station state.
- The project constraint set and approver are recorded with the decision.
- The requested action, returned state, and any adjusted value are visible in the audit record.
- Rollback and manual override have been confirmed before execution.
- The measured outcome is linked to the originating evidence and work record.
Failure handling
| Problem | Response |
|---|---|
| Constraint configuration is missing | Keep the result as a recommendation and involve the control-system owner. |
| Command readback differs from the request | Stop dependent actions, preserve evidence, and follow the rollback procedure. |
| Weather or station state changes before execution | Expire the recommendation and recompute or rereview it. |
| Outcome cannot be measured | Keep the action open and create an inspection or data-repair task. |
| Recommendation causes an adverse trend | Follow the recovery playbook and retain the complete timeline for engineering review. |