Reference · built on requestOperator by FibricFleet, routes & field

Yard Moves

Builds a trailer move list from yard positions, dock appointments, and door status and proposes it to the yard lead for approval.

Request accessPricing ↗

About

Yard Moves is an operator job for the yard jockey's next hour. It reads where each trailer sits, from the trailer's own gateway or the position the yard system last recorded, which appointments are due at which door, and which doors have a trailer at them now.

From those it builds an ordered list of moves: the trailer, the spot it is in, the door or spot it goes to, and the time by which it must be there. Moves for trailers whose door is still occupied wait behind the move that clears it. The yard lead sees the list, reorders or removes lines, and approves. The list is then sent to the jockey once, and each move is checked off as the trailer's position confirms it.

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

  • Trailer positions from Samsara: assets of type trailer through GET /assets and their position through the asset location-and-speed stream
  • GPS and reefer door state per trailer from the Samsara trailer stats feed, so a loaded reefer is not left off power
  • Appointments per site by date through project44 GET /services/appointments/v1/appointments, with the yardShipment's carrier and trailer
  • Door and arrival milestones on an appointment: ARRIVED, CHECKED_IN, and START, with scheduled and actual times
  • Yard activity from FourKites Dynamic Yard and Appointment Manager, which FourKites lists as platform services with their own callbacks
  • Yard entry and exit of tractors and trailers through Samsara geofence alerts

Proposed actions

  • Target capability: propose an ordered move list: trailer, from spot, to door or spot, deadline, and the appointment each move serves
  • Target capability: propose the list to the yard lead in Slack or Microsoft Teams, where lines can be reordered or struck before approval
  • Target capability: propose the appointment milestone update through PUT /services/appointments/v1/appointment/{appointmentId}/milestones once a trailer reaches its door
  • Target capability: propose a spot or door change on an appointment where the door assigned is still occupied
  • Target capability: propose a jockey task per move through Onfleet Create task or your dispatch connector, marked done when the trailer's position confirms it

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

What you can build

  • Build the morning move list from Samsara trailer positions

    Trailers are located through the location-and-speed stream and matched to today's project44 appointments by trailer number. The operator proposes the moves in door-time order for the yard lead in Slack.

    With Samsara, project44, Slack

  • Mark the door milestone when the trailer arrives

    When a trailer's position lands at its assigned door, the operator proposes the ARRIVED milestone with actualDateTime on the appointment, so the appointment system matches the yard.

    With project44, Samsara

  • Sequence moves behind an occupied door

    A trailer due at a door still holding another is queued behind the move that clears it. The order and the reason are shown to the yard lead in Microsoft Teams.

    With FourKites, Microsoft Teams

  • Hand each move to the jockey as an Onfleet task

    Approved lines become tasks with the trailer, spot, and door in the notes and completeBefore set to the appointment time; a task is completed when the trailer's position confirms the move.

    With Onfleet, Samsara

Requirements

  • Trailer positions from a gateway or the yard system: Samsara trailers, or the last recorded spot in project44 or FourKites
  • An appointment system with door assignments and milestones through an API: project44 YMS Appointments or FourKites Appointment Manager
  • A named spot map for the yard, so a position becomes a spot the jockey recognises
  • A Samsara token with Read Assets and Read Trailer Statistics scopes, where Samsara supplies trailer positions
  • Slack or Microsoft Teams for the yard lead's approval
Authentication
Trailer positions, appointments, and door milestones are read and proposed through the connectors you bind; the operator holds no yard credential of its own.

Limits

  • A trailer with no gateway is placed where the yard system last recorded it; an unrecorded move leaves that spot stale until someone corrects it
  • It orders moves by appointment time and door availability. It does not know a jockey's speed or headcount unless the roster says
  • The milestone events documented by project44 are ARRIVED, CHECKED_IN, and START; other door states must be read from the yard system's own records
  • Reefer state is read from the Samsara trailer feed where a reefer gateway exists; it does not otherwise know whether a trailer is powered

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 Yard Moves ↗

Questions and answers

What does the yard lead approve?
The move list for the period: each line names the trailer, where it is, where it goes, when it must be there, and the appointment it serves. The lead reorders, removes, or adds lines, then approves. Nothing reaches the jockey until then.
What record is left?
The positions and appointments read with their times, the list proposed, the lead's edits and approval, the tasks sent, and each move's confirmation from the trailer's position, so a missed move is visible the same hour.
Does it drive anything or move trailers itself?
No. It writes a list. A jockey moves the trailer, a person approves the list, and the appointment system records milestones only after the operator proposes them.
Ask about Yard Moves

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