Reference · built on requestOperator by FibricFleet, routes & field

Route Resequence

Re-orders the remaining stops on an active route after a delay, closure, or missed window and proposes the new sequence to dispatch.

Request accessPricing ↗

About

Route Resequence is an operator job for a route that has already left the yard. It reads the stops still ahead of a driver, the time window on each, and where the vehicle is now. It reads what has changed since the plan was cut: a stop reached late, a closure or incident on the road ahead, a weather warning over the next county.

When the remaining order no longer fits its windows, it drafts a new order for the stops left and shows the dispatcher what moves, what is late whatever the order, and why. The dispatcher approves, edits, or declines. Only then is the route updated in the routing system, once. The plan as it stood, the events that prompted the change, and the accepted order are kept together.

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

  • Stops still ahead on a Samsara route, each with a state of scheduled, en route, arrived, departed, or skipped, and its scheduledArrivalTime
  • Arrivals and departures as they happen, through Samsara RouteStopArrival and RouteStopDeparture events and the route audit-logs feed
  • Route4Me route addresses with sequence numbers, time windows, and visited or departed flags, plus late-arrival entries in the activity feed
  • Onfleet taskDelayed and predictedTaskDelay triggers, each fired once a delay passes the threshold in seconds you set
  • Trimble Maps trip notifications for ETA changes and Out of Route events on trips marked InProgress
  • Active incidents, closures, and construction on major highways from the 511 traffic events feed for the route's region
  • Active watches, warnings, and advisories from the National Weather Service by zone or point along the remaining stops

Proposed actions

  • Target capability: propose a new order for the remaining stops, with each stop's window, its new arrival estimate, and the stops that stay late
  • Target capability: propose the Samsara route update through PATCH /fleet/routes/{id}, sent with the entire stops array as Samsara requires
  • Target capability: propose a Trimble Maps trip change through PUT /trip/modify, with ETAs recalculated for every stop that follows
  • Target capability: propose moving a stop that cannot be reached today to another route, or a Route4Me optimization run over the stops left
  • Target capability: propose the change to the dispatcher in Slack or Microsoft Teams, with the closure or warning that prompted it

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

What you can build

  • Re-sequence a Samsara route after a late arrival

    RouteStopArrival shows a stop reached past its window. The operator drafts a new order for the stops still scheduled and, once the dispatcher approves in Slack, sends PATCH /fleet/routes/{id} with the full stops array.

    With Samsara, Slack

  • Route around a 511 closure on a Trimble Maps trip

    A closure on the highway ahead arrives from the 511 traffic events feed. The operator proposes a modified trip through PUT /trip/modify with the affected stops moved later and the ETAs recalculated.

    With Transit & Traffic, Trimble Maps

  • Hold Onfleet stops under a weather warning

    A National Weather Service warning covers the final stops. When predictedTaskDelay fires, the operator proposes moving those stops to the end of the route plan or to tomorrow, for the dispatcher to approve.

    With Weather & Severe Alerts, Onfleet

  • Move a Route4Me destination that cannot be reached

    An address flagged late in the activity feed, with its window already passed, is proposed for a move to another route through move_route_destination.php, with the remaining sequence re-optimized.

    With Route4Me, Microsoft Teams

Requirements

  • A routing connector holding the active route and its stops: Samsara routes, Route4Me, Onfleet route plans, or Trimble Maps trips
  • Vehicle position from the same platform or a telematics connector, so the new order starts from where the truck is
  • A 511 traffic events token or a National Weather Service User-Agent, where road or weather events should trigger a re-sequence
  • Slack or Microsoft Teams as the place the dispatcher approves
Authentication
Routes, positions, and public road and weather feeds are read through the connectors and signals you bind; the operator holds no credential of its own.

Limits

  • It re-orders stops already on the route. It does not add stops, change a customer's window, or promise a new one
  • A Samsara route update replaces the whole stops array; a stop edited by hand at the same moment is overwritten by the approved order
  • 511 coverage is by program and region; the SF Bay feed covers nine counties and allows 60 requests per 3600 seconds per token
  • Weather and road events say what is happening, not how long it lasts. The estimate uses the routing system's travel times

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 Route Resequence ↗

Questions and answers

What does the dispatcher approve?
A new order for the stops still ahead: each stop's window, the estimated arrival under the new order, the stops that will be late whatever the order, and the event that prompted the change. The dispatcher can accept it, edit it, or decline. Nothing changes in the routing system until then.
What record does it leave?
The route as it stood, the stop states and vehicle position it read, the road or weather event with its time, the order proposed, who approved it and when, and the update as the routing system accepted it, with the previous order kept so the change can be reversed.
Does it ever change a route on its own?
No. Every re-sequence is a proposal. Without an approval the route keeps the order the planner gave it, and the operator only records that a change was suggested.
Ask about Route Resequence

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