Connected Home Programme Assurance: The Missing Layer Between Connectivity and Enterprise Systems

Utilities are moving from supplying energy to coordinating how it is used inside the home. Heat pumps first among the assets, then batteries, solar inverters, EV chargers, smart meters, smart thermostats and time of use tariffs, are becoming parts of one customer programme rather than a collection of separate devices.

That creates a new operating problem. Connectivity platforms can retrieve device data and send control instructions. Enterprise systems can manage customers, billing, service cases, programme eligibility and reporting. Neither layer was built to prove that a connected home programme is working as intended across thousands or millions of homes.

The missing layer is connected home programme assurance: the governed record between connectivity and enterprise systems, keeping consent, asset context, decision logic, intervention history, exceptions and measured outcomes attached to the same home over time. Without it a utility can know that a home is connected and that a customer is enrolled, and still be unable to explain what decisions were made, why they were made, what evidence supported them, and whether the promised customer or system outcome was delivered.

What connectivity gives you

Connectivity solves access. It establishes whether a device can be reached, what telemetry is available and what commands can be issued, which is foundational for any smart tariff, flexibility, retrofit or low carbon heating programme.

Access is not assurance. A connected heat pump can report flow temperature, operating state, energy use and fault codes, and each of those still leaves the operative questions open: was it commissioned to its design, does it suit this household, does its operation line up with the customer's tariff, did the service visit change anything. A connected battery can respond to dispatch, and the dispatch record alone still leaves open whether customer settings were respected, comfort held, consent preserved, and the outcome later claimed in a flexibility report actually delivered.

Connectivity creates the signal. Programme assurance is what makes the signal usable for accountable operations.

What enterprise systems hold

Enterprise systems hold the commercial and customer record: who the customer is, which products they have, what tariff they are on, what communications have gone out, which service cases are open and which programme they have joined.

That record is essential, and it is a different thing from a technical evidence trail. Enterprise systems are rarely designed to keep a live account of the home's energy assets, preserve device level context, version the rules a decision was made under, or compare predicted with observed performance after an intervention. When connected home data is pushed straight into them, the detail tends to flatten into notes, flags, events and summary fields.

What is left is a gap between operational reality and enterprise memory. The programme carries on; the reasoning behind it becomes hard to reconstruct.

What programme assurance does

Programme assurance maintains the evidence chain that neither side can hold on its own. For every participating home it should answer five operational questions:

What is installed, connected, consented, and reliable enough to use?
What baseline was used to judge performance or eligibility?
What decision was made, under which rule, using which evidence?
What action followed, and was it automated, approved, overridden, or escalated?
What changed afterwards, and can the outcome be verified?

A dashboard can show that a device is offline, that a tariff event occurred, or that an exception queue is growing, and that is a different job. Programme assurance records the chain from input to decision to action to outcome, so that programme teams, customer operations, technical assurance and compliance teams can inspect the same governed record from their own viewpoints.

Behind those five questions sits one requirement: each home carries a maintained account of what it is and what it holds, its fabric, its heating system, its controllable assets, its tariff context, its consent state, so that raw telemetry can be interpreted rather than merely collected, and each answer stays attached to the evidence that produced it. Enterprise systems then receive clean, governed summaries with links back to that evidence, rather than becoming the place where technical context is compressed beyond recovery.

Why utilities need this layer now

Connected home programmes are getting harder to run because they combine several forms of risk in the same household.

Technical risk covers device availability, telemetry quality, integration changes, control latency and inconsistent asset metadata. Customer risk covers comfort, bill impact, consent, vulnerable customer handling, complaints and opt out behaviour. Commercial risk covers benefit claims, partner performance, subsidy evidence, flexibility revenues and installation quality. Compliance risk covers the explainability of automated decisions, customer communications, auditability and data minimisation.

Each is manageable when handled separately. A single control action may depend on device data, tariff logic, weather, occupancy assumptions, customer consent, grid signals and programme rules all at once, and when the evidence chain breaks the utility is left with fragments: a command log in one place, a customer note in another, a reporting metric somewhere else.

Programme assurance keeps those fragments connected.

Design principles

A handful of design choices decide whether the record is still usable when someone comes back to it a year later.

Consent should be treated as an operational dependency rather than a static checkbox. When the scope of consent changes, the system should know which decisions and actions remain permitted.

Asset context should be versioned. A home with a newly installed heat pump, a changed tariff, an added battery or an updated control setting is not the operating case it was last month.

Decision logic should be traceable. Whether the action came from a rule, a forecast or a human operator, the record should show the evidence used and the reason for the decision.

Exceptions should be first class workflow objects. Missing telemetry, inconsistent device state, repeated opt outs, failed dispatch and customer complaints all need an owner, a service level and closure evidence, and where a home is not delivering its promise, the record should carry the cause the evidence supports rather than a suspicion aimed at whoever touched it last.

Outcomes should be measured against the promise that was made. A flexibility event, retrofit programme, tariff optimisation or low carbon heating deployment deserves to be judged on the customer and programme outcomes it was meant to deliver, rather than on whether a control signal was sent.

And the record itself should be independent of every party whose performance it evidences. A programme's benefit claims are only as strong as the reader's confidence that nobody who profits from the claim could bend the evidence beneath it. That is an argument for the record being kept outside the delivery chain, with its method fixed and governed, so the same reading re-run gives the same answer.

What this changes day to day

With programme assurance in place, a utility can scale connected home activity without losing the evidence needed to manage it.

A customer operations team can see why a home was contacted, what the system observed and what options were on the table before a recommendation was made. A technical team can tell poor telemetry apart from poor equipment performance. A programme manager can see whether failures cluster by device type, housing archetype, tariff design or data quality issue. A compliance team can inspect automated decisions without reconstructing them from disconnected logs.

Partner management improves as well. Connected home programmes usually involve installers, device manufacturers, aggregators, local delivery partners and public bodies. A shared record of what happened and what was evidenced lets all of them work from the same facts, without forcing every party into the same enterprise system, and it protects the good work as reliably as it explains the shortfalls.

A practical starting point

Utilities do not need to replace their connectivity or enterprise systems to add programme assurance. The practical starting point is coverage: for each participating home, the record already begins with what is publicly known about the building, and grows as the programme adds to it. The minimum a governed record holds for a participating home:

enrolled customer and active consent state
installed assets and confidence in asset metadata
connectivity status and telemetry freshness
applicable programme rules and the version in force
baseline used for eligibility or performance comparison
decisions made and actions taken
exceptions, overrides, and service handovers
measured outcomes and confidence level

Once that record exists, the organisation can decide which teams need which view of it. Customer operations may want concise explanations, technical assurance the telemetry and the working detail behind it, programme leadership portfolio level risk and outcome reporting, compliance the decision lineage and an audit export. The underlying record stays the same.

The strategic point

Connected home scale will not be won by connectivity alone. It will be won by the organisations that can run connected homes as accountable programmes: technically reliable, safe for customers, commercially measurable and auditable.

The assurance layer is what makes that possible. It sits between device connectivity and enterprise systems, holding the programme's evidence together as work passes between them. For a utility, that is the difference between owning connected assets and running connected home operations it can stand behind.

This brief is published by Aeterno. HeatAssure keeps the record it describes: one maintained, evidence-linked record per home, from design through operation, kept and governed outside the delivery chain. The worked argument is at programme assurance.

HeatAssure: the record each home is held to
Housing & Place: expected versus observed programme operation, kept on one record, and why assurance comes before broader optimisation