Conditions with a policy
Configure appropriate regimes, limits, delays, and applicability rather than treating every temperature change as the same event.
Refrigeration & cold-chain monitoring
Connect the alert to the operating reality.
ciliot helps teams monitor refrigeration conditions, work through excursions, and retain the evidence needed to understand what happened. It is designed to support accountable human decisions, not autonomous refrigeration control.
1. SenseReceive temperature and supporting device signals with their source context.
2. UnderstandEvaluate readings against the right regime, calibration state, and operating context.
3. RespondRoute a visible exception to a named team with acknowledgement and escalation.
4. ReviewRetain the condition, action, and limitations as a reviewable operating record.
A traceable operational workflow
Move beyond a temperature graph without losing the source detail.
A reading is only one part of an excursion review. The service brings configured temperature regimes, asset context, supporting signals, ownership, and response records into the same operational thread.
Signals in operating context
Review temperature alongside relevant door, power, defrost, gateway, connectivity, or late-data information when it is available.
Response with a responsible person
Make the acknowledgement, escalation route, corrective action, and review status clear to the people coordinating the response.
Evidence that can be investigated
Keep the details a reviewer needs within reach.
A good incident record is more than a status. ciliot is designed to hold the evidence scope needed for a team to investigate whether a condition was real, what context applied, and how the response progressed.
- Source and timingDistinguish device event time, receipt time, late data, and source evidence.
- Calibration and configurationKeep applicable sensor calibration status and policy context visible to the reviewer.
- Action and reviewRecord who acted, what was done, and which evidence limitations remain.
Illustrative incident record
Chilled display 14 · Attention required
- Configured condition identifies an excursion candidate against the relevant temperature regime.
- Asset, sensor channel, site, and source timing are retained for the reviewer.
- Responsible contact is notified and the acknowledgement time is visible.
- Notes and final review make the evidence scope clear rather than declaring automatic compliance.
One service, shared teams
Give each role a useful view of the same operating story.
The same condition can affect local store operations, quality, engineering, supply chain, and leadership. The service supports role-relevant views without losing the shared context.
Store and site teams
See what needs attention now, who owns it, and the next operational step.
Quality and food safety
Review the configured regime, evidence completeness, calibration state, and action history.
Facilities and engineering
Use correlated signals and trends to investigate equipment, power, door, or connectivity patterns.
Important boundary: ciliot can complement controllers and sensors, but it does not claim to autonomously control refrigeration equipment or establish regulatory compliance.
Questions teams ask
Start with the operational question, not a generic promise.
We use a pilot to test a representative operating scenario, evidence need, and measurable hypothesis with your team.
Does ciliot replace the refrigeration controller?
No. The initial service is a monitoring and evidence workflow. Any controller write is separately safety-engineered, authorised, and audited.
Can a green dashboard prove compliance?
No. In-range readings are evidence within a defined scope. A reviewer must still consider calibration, evidence completeness, policy, local requirements, and known gaps.
Can we use our existing devices and gateways?
The platform is designed for replaceable adapters and reusable contracts. A pilot validates the exact device, connectivity, support, and commissioning boundary before adoption.
What should a pilot measure?
Agree a representative site population, an operational scenario, response drill, baseline, data sources, calculation method, and named approvers before making any benefit claim.
A grounded first step
Bring a real cold-chain question to a pilot conversation.
We will focus on your operating conditions, people, evidence needs, and a measurable hypothesis—not a pre-packaged savings claim.