Skip to content
Cold chain & telemetry

Cold chain & telemetry

Agent: the telemetry agent (telemetry in ExecuteLoop), with the TEMPERATURE_EXCURSION and CHAIN_OF_CUSTODY_AUDIT evidence documents.

What it does

It reads sensor and telematics data, works out whether a load really left its stated band and for how long, and drafts the quarantine, probe or reroute for a quality manager to approve. Its jobs:

  • Temperature excursions. Measures time out of the stated band, gaps in the log, and the load’s exposure when the records state its value.
  • Sensor or product. Tells a stuck or silent sensor apart from a real change in temperature.
  • Site thresholds. Flags speeding, perishable dwell at the dock and weighbridge differences against the thresholds your site states.
  • Fleet and yard safety. Ranks events with a safety impact first, such as a hazardous-goods segregation problem or a driver in distress.
  • Custody gaps. Finds intervals longer than the stated check-in cadence, door events with no task, and loads with no events at all.

What it reads

Temperature and humidity readings, reefer logs, GPS, speed, fuel and engine data, weighbridge events, custody events, dispatch states and the thresholds your records state. Telemetry arrives through the connections described in Telemetry. It can run read-only queries against the connection a run was started with.

What it produces

  • Excursion and custody evidence documents, each figure cited. See Evidence documents.
  • Action cards with a priority and one proposed step, such as “hold the load and probe the core before release”. They wait on Actionable Twins under the cold chain play, and each reefer with readings out of band is pinned on its Map view.
  • On Options, the what-if options for a cold-chain decision, each scored on the share of temperature readings past a limit their own row states. See Action cards & money.
  • Safety notices for a supervisor, ranked by urgency.

Human oversight

  • A quality manager or supervisor approves every quarantine, reroute and release.
  • The agent never adjusts a reefer controller, locks or unlocks a crane, stops a conveyor or reroutes a vehicle itself. It can propose a step or raise a cue as a request; a person acts.

Model

The deployment’s general reasoning tier.

The excursion and custody documents are fixed arithmetic over cited readings. No model computes their figures.

Where it runs and data handling

On the deployment’s own model plane: Runink’s shared machines on a Trial, your own cloud on Cloud and your own servers on On-premises. No outside AI service is called on any plan. See Facts shared by every card.

Guardrails

  • No stated band, no breach. FACE never assumes a threshold the source didn’t provide, and never borrows an industry norm.
  • A missing reading is “not measured”, never zero. A gap in the log is reported as a gap.
  • Refuses to alter, suppress or fabricate sensor, GPS, speed, fuel or driver records.
  • Refuses to bypass hazardous-goods segregation rules or crane safety locks.
  • Refuses to run equipment control commands without a person’s authorisation.
  • Stays on monitoring, cold chain, fleet telematics and yard safety.

How to read its results

  • A surface or air reading isn’t the product’s core temperature. The card says to probe the core; it doesn’t certify the product.
  • Exposure is stated only when the records give the load value with a currency. Otherwise it is absent as “not measured”.
  • Any projection of when a load will leave its band is labelled as modelled, not measured.
  • An unrecorded handoff is not a break in custody. Custody findings are statements about the record, never about the goods or the people.