HClimate Dashboard

A high point count is not the same as visibility

An instrumented portfolio produces telemetry continuously — temperature, humidity and device state, sampled per point across every building on the estate. What an energy or facilities manager is actually measured on is narrower than that stream: comfort complaints and hot/cold calls, energy intensity per m², and how long a fault runs before anyone notices it. None of those are answered by a raw point stream.

Point count is the easy part to sell and the hard part to use.

why instrumentation stalls

In practice the workflow degrades to CSV export and a pivot table, and detection becomes reactive — the tenant calls before the dashboard says anything. That is the failure mode worth designing against: plant running out of schedule for days, a drifting setpoint, or a dropped sensor quietly biasing an average nobody re-checks.

Underneath sat a commercial constraint. A platform that stalls when someone filters it is a platform that stops being opened, and adoption is what the whole investment rests on: unused analytics cannot justify the sensor capex at renewal. Speed here is not a nicety — it is the difference between a monitoring contract that renews and one that is written off.

Estate-level triage, device-level proof

Our mission was to build the layer that makes the instrumentation pay for itself — a tool with scientific credibility and consumer-grade responsiveness, structured the way an estate is actually managed: triage at portfolio level, then drill to the device that explains the reading. It had to stay fast at full estate scale rather than at demo scale, because the moment it hesitates is the moment a facilities manager goes back to the spreadsheet.

Two views that mirror how an estate is actually walked

The app resolves to two views because that is the shape of the job. A Buildings overview answers "which sites are behaving"; an All-devices breakdown answers "which unit is causing it" — triage, then evidence, with no dead ends between them.

The decision that mattered was refusing to let estate size show through to the user. However many buildings and devices sit behind a view, the interface responds at the same speed — so an estate can be onboarded without the tool degrading, and a facilities manager never learns to expect a wait. Interrogating the portfolio stays a reflex rather than a chore, which is the only condition under which anyone checks it daily rather than after a complaint.

Built with