ciliot

Request a pilot conversation

Start with a real operating question.

A ciliot pilot is an opportunity to test the service in representative conditions: the sites, assets, signals, people, evidence needs, and decision points that matter to your team.

  • Representative operating settingBring the site types, refrigerated assets, and conditions you need to evaluate.
  • Named response pathInclude the teams who acknowledge, investigate, escalate, and review a condition.
  • Evidence and measureSet the scenario, source data, baseline or hypothesis, and acceptance evidence before drawing a conclusion.

Tell us where to start

Share only the contact details and high-level operating context needed to begin a conversation.

Please do not include sensitive personal, customer, access, or security information.

This deployed static preview has no connected form endpoint and does not retain submitted values. An approved, consent-aware route is required before public release. See the privacy approach.

Pilot approach

Use a real-world pilot to test the operating model, not to create a generic case study.

We structure the discussion around a representative scenario and evidence plan so that all parties understand the scope, assumptions, and limits of the result.

  1. Frame the question

    Identify the condition, decision, people, desired evidence, and likely constraints that matter most in day-to-day operations.

  2. Choose representative scope

    Include enough sites, assets, signals, connectivity conditions, and operating patterns to test normal and difficult cases.

  3. Exercise the response

    Plan actual drills such as a high excursion, missing telemetry, gateway outage, power loss, calibration expiry, or notification failure.

  4. Review the result

    Assess acceptance evidence, data limitations, response quality, and a documented benefit baseline or hypothesis before any external claim.

What a productive first discussion covers

Make the boundary, responsibility, and evidence expectations explicit early.

We do not need production credentials or sensitive customer records to have an initial conversation. A high-level view of the operating environment is enough to decide whether a pilot is worth shaping.

Sites, assets, and signals

Which operating locations, asset classes, sensor types, gateways, and supporting signals should be representative?

People and response

Who owns acknowledgement, escalation, investigation, corrective actions, review, IT/security, and implementation?

Evidence and outcome

What evidence is needed, what should be tested, and which approved data source and method can support a measure?