For a temperature-sensitive shipment, the record is the product. A cold-chain monitor has to log that goods stayed in range for the whole journey, survive weeks on a small battery with no charging, and produce evidence that a customer, an auditor or an insurer will accept — often with no connectivity for most of the trip.
A cold-chain monitor travels with a shipment of food, pharmaceuticals or biologicals and records whether it stayed within its temperature window. If it did not, that has to be known and provable; if it did, the record is what releases the goods. The device's output is evidence, and evidence has to be trustworthy.
The constraints are field constraints. The journey can be weeks with no way to charge, so the battery has to last on a duty cycle that still captures excursions. Connectivity is intermittent or absent across borders and in transit, so the log must be complete on the device and reconcilable later. And the record has to resist tampering to be worth anything to an auditor.
So it is built as a logger first and a radio second: reliable in-range and excursion capture, multi-week energy budget, and a tamper-evident record that uploads when it can and stands alone when it cannot.
Stated before any of them had an answer.
The device exists to produce evidence; a log that could be altered or has gaps is worthless to a customer, auditor or insurer.
Journeys run for weeks with no charging, yet the monitor must sample often enough to catch a short excursion, which is a tight energy trade.
Across borders and in transit there may be no signal for most of the trip; the complete record has to live on the device and reconcile later.
A temperature breach can be short; too coarse a sampling interval misses it, too fine drains the battery, so the duty cycle is a real design decision.
A shipment that arrives is not the deliverable; the trustworthy record that it stayed cold is. The device is a logger that survives weeks and proves it did not miss anything.
The scope of the work, rather than a capability list.
Rarely the subsystem that sounds difficult.
Integrity and tamper-evidence are the point; a log that a party can dispute or that has silent gaps fails the one job the device has.
Catching a brief excursion wants frequent sampling; lasting weeks wants rare sampling; resolving that tension is the core energy trade.
Designing the device to stand alone for the whole journey, and only opportunistically upload, is harder than assuming a connected sensor.
Evidence is only as good as the sensor's accuracy over time and temperature; calibration has to hold across the journey, not just at dispatch.
A complete, tamper-evident temperature record a customer or auditor accepts.
Multi-week life on one battery, with a duty cycle that still catches short excursions.
A full record on the device regardless of connectivity, reconciled when a link appears.
A sampling strategy proven to catch brief breaches within the energy budget.
Customer projects are presented at property, capability, outcome and integration level. Customer names, internal architecture, confidential deliverables and commercial terms are not disclosed. Where a detail would identify a customer it is omitted rather than approximated. More is available under a non-disclosure agreement, within the limits the customer has agreed.
Every item links to its own page.
Because the device exists to produce trustworthy evidence. Measuring temperature is routine; producing a complete, tamper-evident log that a customer, auditor or insurer will accept — with no silent gaps and integrity that survives a dispute — is the real requirement. A monitor that records accurately but whose log can be altered or is missing the moment an excursion happened has failed at its actual job.
Through an energy budget built around the duty cycle. Sampling frequently enough to catch a short temperature excursion costs energy, and the journey may run for weeks with no way to recharge, so the sampling strategy is a deliberate trade validated by measurement rather than a default. Deep sleep between samples and efficient logging are what make multi-week life on a small battery achievable.
The device is designed to stand alone. The complete record lives on the monitor throughout the journey, so an absence of signal across borders or in transit loses nothing; when a link does appear, the device uploads opportunistically and reconciles. The evidence never depends on being connected at the moment an excursion occurs, which is essential because that is exactly when a signal is least likely to be present.
Written for engineers. Share it with one.
Tell us the specification, the constraint and the deadline. Programmes that cross silicon, radio, embedded and AI are where Faststream is strongest.