Reference · built on requestOperator by FibricProduction & maintenance

Cold Chain Excursion

Matches reefer and logger temperatures to lots in transit. Proposes a hold, quality review, or consignee notice on a limit breach.

Request accessPricing ↗

About

A trailer's zone drifted for an hour at a stop. Which lots were aboard? Cold Chain Excursion joins the temperature trace to the shipment and its lots. From Samsara it reads reefer readings per zone: return and supply air, set point, unit on or off, door open, and active alarm codes. From Geotab it reads status data keyed to a diagnostic. Shipment loggers from Monnit or SensorPush add pallet-level samples.

The shipment and its stops come from project44 or FourKites; the lots on it from the item fulfillment in NetSuite or the delivery in SAP S/4HANA. When a zone breaches the limit you set for those lots for longer than you allow, it proposes a hold, a quality review with the trace, or a notice to the consignee. A person sends each.

This is a reference listing. It documents what Fibric would read from Cold Chain Excursion and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Reefer readings from the Samsara Readings API with entityType asset: return and supply air per zone, set point, unit state, door open, ambient, alarm codes
  • StatusData and FaultData for trailers from a MyGeotab database, pulled incrementally with GetFeed
  • Temperature samples from shipment loggers through Monnit's REST API or Data Webhook, or the SensorPush Gateway Cloud API
  • Shipment tracking, stops, and ETAs from project44 unified shipment tracking or FourKites load tracking, by webhook
  • Lots on the shipment from the item fulfillment posted in NetSuite or the outbound delivery in SAP S/4HANA
  • The temperature limit and allowed duration per product, from the specification you supply

Proposed actions

  • Target capability: propose a hold on the lots aboard when a zone breaches its limit longer than you allow, as an ERP inventory status change
  • Target capability: propose a quality review with the trace attached: zone readings, set point, door events, and alarm codes across the stop
  • Target capability: propose a consignee notice naming the shipment, the lots, and the excursion window, sent by Microsoft Teams, Slack, or email once approved
  • Target capability: propose a carrier query when the unit reported off or a door stayed open at a stop, before any hold
  • Target capability: propose a shipment record with the temperature trace for the receiver's file

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • One zone at the stop

    Samsara shows one zone above set point with the door open for the whole stop. Cold Chain Excursion names the lots in that zone from the NetSuite fulfillment and proposes a hold on them.

    With Samsara, NetSuite

  • Query the carrier first

    Geotab status data shows the unit off while the shipment sat at a yard in project44. The operator proposes a carrier query in Slack before any lot is held.

    With Geotab, project44, Slack

  • Pallet logger, not the trailer

    A SensorPush logger rode with the pallet. Its samples, tied to the FourKites load, show the pallet stayed within limit while the zone drifted, so no hold is proposed.

    With SensorPush, FourKites

  • Tell the consignee before the dock

    Monnit logger samples on an SAP S/4HANA delivery show an excursion. The proposal is a Teams notice to the consignee with the trace, sent when the quality lead approves.

    With Monnit iMonnit, SAP S/4HANA Cloud, Microsoft Teams

Requirements

  • A telematics connector with reefer or trailer temperature data: Samsara or Geotab
  • A shipment tracking connector that links the trailer or load to a shipment: project44 or FourKites
  • An ERP connector that names the lots on each fulfillment or delivery: NetSuite or SAP S/4HANA
  • A limit and allowed duration per product, supplied by you or the shipper
Authentication
Cold Chain Excursion keeps no credentials. Reefer data arrives through your Samsara or Geotab connector, tracking through project44 or FourKites, lots through the ERP connector, and each notice goes out through the messaging connector under its scopes.

Limits

  • Matching a trailer to lots depends on the trailer or load id on the shipment. An untracked trailer yields a trace with no lots.
  • Reefer readings arrive only from trailers with a reefer-connected gateway. A logger in the load fills the gap for that pallet only.
  • It proposes. A hold or a notice goes out only after approval, and it never changes a set point.
  • Limits are yours. The operator does not decide what temperature is safe for a product.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Cold Chain Excursion ↗

Questions and answers

What does a person approve?
Every hold, review, notice, and carrier query. The proposal shows the shipment, the trailer or logger, the lots aboard, the trace across the breach, the limit applied, and the stop where it happened. Approve, change the lots, or dismiss. A dismissed breach is not proposed again.
What record is left?
A trace per shipment: readings, set points, door and unit events, and the stops. A receipt per proposal: the limit used, who approved, what was written to the ERP or sent, and how to release a hold.
What does it leave to people?
It never holds a lot, contacts a consignee or carrier, or changes a reefer set point. It never edits a shipment. If no lots can be matched, it proposes a review of the trace, not a hold.
Ask about Cold Chain Excursion

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy