Asset and site context
Use a common organisation, site, asset, device, and sensor-channel model across current and future services.
The ciliot platform
Built for the operating work behind the dashboard.
ciliot provides the shared capabilities that connected-asset services need: tenant-aware identity and context, source-aware data, policy-driven conditions, accountable workflow, integrations, and reviewable operational evidence.
Connected assetsDevices, gateways, adapters, and source evidence.
Shared contextTenant, site, asset, policy, identity, and data quality.
Operational servicesConditions, alerts, incidents, response, and reporting.
Customer outcomesRole-relevant decisions with a reviewable record.
Designed to evolve
Start in cold chain without baking retail assumptions into every service.
The first module is Refrigeration & Cold-Chain Monitoring. The platform deliberately separates reusable connected-asset capabilities from the domain rules that make a service useful to a particular team.
Evidence-aware data
Keep immutable source evidence distinguishable from canonical, derived, and workflow records used by operational services.
Workflow and review
Make policies, conditions, people, notifications, decisions, and reports part of a coherent operational record.
A repeatable operating flow
Turn a connected signal into a clear, reversible decision path.
The platform is designed so an operational service can explain the condition it sees, its evidence and policy context, the people involved, and the outcome—not simply issue a notification.
- Ingest and retain source evidenceAdapters translate device inputs while preserving raw evidence for investigation.
- Apply service policy in contextDomain rules use the correct tenant, asset, site, regime, and data-quality context.
- Coordinate people and integrationsNotifications and APIs support human review without creating an ungoverned control path.
- Report with scope and lineageExports and dashboards carry the relevant context, limitations, and audit evidence.
Platform contracts
Shared by design, specific when it matters.
- Reusable identity, organization, site, asset, and entitlement contracts establish an operating boundary.
- Domain modules add their own policies, vocabulary, reports, and acceptance evidence without changing platform records.
- Replaceable adapters avoid a generic compatibility claim while allowing evaluated connectivity patterns to evolve.
People, systems, and controls
Give each participant the context they need, no more and no less.
A healthy IoT operating model has to serve local operations, specialist reviewers, customer IT, and platform support with explicit roles and a clear boundary between evidence and control.
Set up the tenant
Establish the organisation, sites, roles, entitlements, retention, and integration ownership.
Commission the estate
Associate gateways, devices, sensor channels, assets, calibration evidence, and operational contacts.
Operate the service
Use role-relevant queues, dashboards, reports, exports, and integrations to manage the daily work.
Review and improve
Use incident, support, usage, audit, and benefit evidence to govern the service and its future changes.
A deliberate trust boundary
Manage an operating service, not an opaque stream of device data.
Platform controls support tenant-aware authorization, encrypted transport and storage, immutable source evidence, and audited workflows. They are not a blanket guarantee or a substitute for each customer’s governance and compliance responsibilities.
Access in context
Plan organisation, tenant, role, entitlement, and support-access boundaries as explicit product controls.
Integration with contracts
Use defined interfaces, audit context, and evaluated support boundaries instead of unbounded connector promises.
Governed records
Retain the source, configuration, response, and report context needed to understand scope and lineage.
A platform conversation
See how your connected-asset operating model could fit together.
We start with the service and decision you need to support, then make the data, ownership, and integration boundaries explicit.