Reference · built on requestOperator by FibricFleet, routes & field

Reefer Excursion

Reads reefer temperature and setpoint from trailer telematics against each load's required range and proposes a stop, inspection, or hold.

Request accessPricing ↗

About

A reefer can run all night at the wrong setpoint. Reefer Excursion reads, per zone, the setpoint, return air, and ambient temperatures, the run mode, alarms, and door state from Samsara's trailer stats, or the setpoint_deg_c, return_deg_c, discharge_deg_c, mode, and door_status from Motive's reefer activity report and its sensor samples. It reads each load's required range from the shipment's contents in project44, or from the load record you keep, and matches trailer to load.

A reading outside the range, a setpoint that does not match the load, or a door open beyond the time you allow becomes a proposal: a message telling the driver to stop and check, an inspection issue on the trailer, or a hold on the load. Dispatch approves.

This is a reference listing. It documents what Fibric would read from Reefer 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

  • Samsara trailer stats through GET /fleet/trailers/stats: reeferSetPointTemperatureMilliCZone1, reeferReturnAirTemperatureMilliCZone1, reeferAmbientAirTemperatureMilliC, reeferRunMode, reeferAlarms, and reeferDoorStateZone1
  • Motive reefer activity reports through GET /v1/reefer_activity_reports with setpoint_deg_c, return_deg_c, discharge_deg_c, mode, and door_status per zone
  • Motive reefer sensor samples through GET /v1/reefers/samples with temperature_deg_c, humidity_pct, and zone_location, and the company thresholds min_temp_deg_c and max_temp_deg_c
  • Temperature setpoints and product categories in a shipment's contents, and reefer condition for full truckload, from project44 tracking
  • Which trailer is on which load, from the trailerNumber in FourKites truck assignment or the load record you keep
  • The driver's reply to a stop-and-check message through Twilio's inbound message webhook

Proposed actions

  • Target capability: propose a Twilio message to the driver through the Messages resource asking for a stop and a setpoint check, with the reading quoted
  • Target capability: propose an issue on the trailer through POST /issues in Fleetio with asset_id, summary, reported_at, and the readings in the description
  • Target capability: propose a hold on the load as a Slack message to dispatch through chat.postMessage, with the trace, for a person to place
  • Target capability: propose attaching the temperature trace as a PDF to the load stop through the FourKites Document Upload API, keyed by loadNumber

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

What you can build

  • Stop the driver when the setpoint is wrong for the load

    Compare reeferSetPointTemperatureMilliCZone1 with the range from project44 contents at load assignment; when they disagree, propose the driver message and a Fleetio issue in one approval.

    With Samsara, project44, Twilio

  • Watch return air as well as the setpoint

    Read return_deg_c and door_status from Motive per zone; a door open past your limit with return air drifting proposes a driver message before the product is out of range.

    With Motive, Twilio

  • Put the trace on the load

    When an excursion is confirmed, propose the PDF trace through the FourKites Document Upload API on the delivery stop, so the receiver and the claim have the same record.

    With FourKites

  • Hold the load where dispatch works

    Post the proposed hold to the dispatch Slack channel with trailer, load, readings, and time out of range; dispatch approves and places the hold in the TMS.

    With Slack, Fleetio

Requirements

  • Reefer telematics with per-zone readings: Samsara trailer gateways or Motive asset gateways on the trailers
  • The required temperature range per load: from project44 shipment contents or a load table you maintain
  • A trailer-to-load link: FourKites truck assignment, or the trailer number on your load record
  • The excursion rules you want: tolerance around setpoint, minutes out of range, and door-open time
Authentication
A Samsara API token with Read Trailer Statistics, or a Motive API key; a project44 client ID and secret; FourKites API keys per subscribed bundle; a Fleetio API key with Account-Token; a Twilio Account SID and auth token; a Slack app with chat:write.

Limits

  • Samsara's trailer stats endpoint returns up to 3 types per request, so a full zone read is several calls; polling is paced
  • Neither Samsara nor Motive documents a setpoint write on this path; the job cannot change the reefer, it can only tell the driver
  • A trailer with no gateway, or a reefer not wired to it, yields no readings and is listed as unmonitored
  • FourKites document uploads take at most 2 MB and are asynchronous; the trace is trimmed to the excursion window

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 Reefer Excursion ↗

Questions and answers

What does dispatch approve?
Per excursion: the trailer and load, the readings with their times, the range they broke, and the proposal: driver message text, a Fleetio issue, a hold notice, or the trace upload. Each line is approved or rejected separately; a rejected line records why.
What is on file after an excursion?
The trailer, load, and zone; the setpoint, return air, ambient, mode, alarm, and door readings across the window; the range source; the proposals, decisions, approvers, and times; the driver's reply if any; and the Fleetio issue or FourKites document id.
Can it change the reefer setpoint or stop the truck?
No. It has no control path to the reefer or the vehicle. It reads, proposes, and after approval sends one message, opens one issue, or uploads one document. Physical action is the driver's, on a person's instruction.
Ask about Reefer 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