Know an install workedbefore the callback.
Predicted against observed performance across the base you answer for. The installs that need attention surface first, and the evidence keeps itself.
A module of HeatAssure™, from Aeterno. Also in the platform: Design Studio · HEM Access
Proof that installed systems perform as promised, boilers included, across the heating fleet you answer for. Verified from meter and connected data against the home’s governed record.
Commissioning is where quality, margin and trust leak.
If predicted and observed performance are not checked early, the cost arrives later: callbacks, warranty spend and partner friction.
A quality decision in hours, not an investigation in months.
Predicted against observed
Start from the design assumptions and expected operating envelope, then compare them with how the installed system actually behaves.
Exceptions surface first
The installations that need review rise to the top, with confidence on whether the issue is design, installation, configuration or operating context.
Evidence packs keep themselves
What was expected, what was observed, what the team concluded and what happened next stay on the record, without a manual write-up.
Learning feeds the base
Verified outcomes improve future commissioning expectations and installer support across your base.
The teams that carry the quality question.
Technical and QA teams
See which installations performed as designed, which need attention, and which installer or cohort patterns are emerging.
Service operations
Less unnecessary dispatch, and better prepared arrivals when an intervention is needed. Predicted against observed, with the likely next action.
Product and warranty leaders
Installation issues separated from genuine product issues, with a usable record of what happened in the field.
One cohort, six to eight weeks.
A first deployment runs on one installer cohort, region or slice of the base you answer for. It proves where quality is drifting, how quickly issues surface, and what evidence the current process is missing.
- 01
Start with a defined slice, or one installer cohort.
- 02
Use the commissioning records, design assumptions and observed data you already have.
- 03
Get an exception-led view, a quality baseline and evidence packs for review.
- 04
Use the result to decide where the record extends next across the base.
- One record, two admissibilities: compliance-admissible at design time and checked against operation, with governed provenance across the boundary.
The public evidence this module is built on, worked through: the commissioning quality proof.
Asked before a first deployment.
Start with commissioning quality.
If quality, callbacks or warranty risk are already visible, this is the cleanest place to begin.