The fourteen hours
between two
readings.
A platform built for this client: wireless temperature sensors installed across the site's cooler and freezer equipment, paired with our cloud monitoring platform. The problem it solved was not the accuracy of the manual temperature log. It was everything that happened between entries.
A blind spot
every retail
operator has.
The client is a retail grocery chain operating in Ontario. Before this project, temperature readings for the site's cooler and freezer units were taken by hand, by staff, for compliance purposes. The readings themselves were fine.
What the process could not do was see overnight, or catch a unit drifting between checks. Overcooling that quietly costs money every night; an intermittent failure that recovers before the morning round; a door seal degrading over weeks. None of it appears in a log of discrete readings. It surfaces as a compliance gap or a spoiled-product loss, which is to say after it has already cost something.
This is not one operator's problem. Any retail or cold-chain operator running manual temperature logging carries the same gap, and most of them have never seen what is in it.
Sensors, a floor
plan, and a
threshold.
Wireless temperature sensors across the coolers, freezers and display cases, each mapped to its position on the site's own floor plan so a reading has a location rather than a device ID. Data lands continuously on the platform, with thresholds set per zone and alarms routed to a person rather than into a log.
The hardware carries a fifteen-year battery, which matters more than it sounds. The usual failure mode of a sensor programme is not the sensors — it is that eighteen months in, a third of them are flat, the data has holes in it, and nobody trusts the dashboard any more.
What the operator
reports since
deployment.
They are the operator's own post-deployment reporting. They are not IPMVP-verified savings: there is no stated measurement boundary, no fitted baseline and no confidence interval behind them, so they indicate a direction rather than underwrite a business case.
We are stating that plainly because the rest of this site holds a different standard. Where we publish measured savings on audit and optimization work, the method and the uncertainty are published with them — see why we adjust the baseline, not the results. A monitoring deployment establishes the instrumentation that would make a properly verified measurement possible; on this site that verification has not been run.
The change that is not in dispute is the operational one. Compliance temperature records are now generated continuously rather than collected by hand, the overnight window is no longer blind, and an equipment problem reaches somebody while it is still a problem rather than after it has become a loss.
What the site
looks like now.
Every deployed sensor is mapped onto the store's floor plan, and live device data is surfaced through the platform's Insights view. Both are shown below as they appear for this deployment.
Hardware is unobtrusive and battery-powered, so installation needed no cabling, no electrical work and no interruption to trading.
Not a product.
A platform built
for one site.
The sensors are off the shelf. What was built here is everything above them — the floor plan, the thresholds, the alarm routing and the record an inspector accepts. Where a client needs something that does not exist, that is what we build.
Nearby work.
Food manufacturing plant
A continuously operating process facility optimized around production, with savings verified after implementation.
Solar on a cold store
Two cold storage facilities, 360,521 ft² of roof and about six megawatts modelled across two utilisation cases.
The rest of the platform
Q-Peak, Q-Energy and the custom platforms we build — what each does and why it exists.
Thirty minutes, with the engineer who would run the work.
No cost and no obligation. Bring twelve months of utility bills if you have them — that alone is usually enough to say whether a building has a capital problem or a controls problem.