Reference · built on requestOperator by FibricFleet, routes & field

Route Deviation

Flags vehicles that leave the planned corridor or stop where no stop was planned, and proposes a driver check-in or a route note.

Request accessPricing ↗

About

Route Deviation is an operator job that compares where a vehicle is with where its plan says it should be. It reads positions and geofence events from your telematics platform and the planned stops from your route source, then draws a corridor of the width you set around the planned path. A vehicle outside that corridor, or one stopped longer than your threshold at a place that is not a planned stop, becomes a case.

For each case it proposes one of two things to the dispatcher on duty: a check-in message to the driver, sent through the driver app or by SMS, or a note on the route recording where the vehicle went and why, once the driver answers. The dispatcher approves, edits, or dismisses each one. Nothing reaches the driver until they do.

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

  • Vehicle positions: the Samsara vehicle stats feed gps type, Geotab LogRecord and DeviceStatusInfo through GetFeed, Motive vehicle_location_updated webhooks and GET /v3/vehicle_locations
  • Planned stops: Samsara routes with scheduledArrivalTime per stop and the route events stream (stopEnRoute, stopArrived, stopSkipped), Geotab Route entities and their routePlanItemCollection of zones
  • Geofence events: Samsara GeofenceEntry and GeofenceExit subscriptions, Geotab ExceptionEvent records from ZoneStop rules, Motive v1/geofences/events with the vehicle and the driver at start and end
  • Vendor deviation alerts: Samsara alert configurations with the Out of Route and Outside Geofence trigger types, and Trimble Maps Trip Management Out of Route notifications
  • Route4Me Activity Feed entries typed destination-out-sequence, geofence-entered, geofence-left, driver-arrived-early, and driver-arrived-late, plus device GPS history per route
  • Long stops: Verizon Connect Reveal Long Stop and Geofence alert webhook messages, Geotab Trip stopDuration and stopPoint, and dwell against the threshold you set
  • Driver replies to a check-in, read back from Samsara GET /v1/fleet/messages and Motive v1/messages

Proposed actions

  • Target capability: propose a check-in to the driver through Samsara POST /v1/fleet/messages, Motive POST v1/messages, Webfleet sendTextMessageExtern, or a Twilio SMS
  • Target capability: propose a route note through Route4Me /actions/addRouteNotes.php with the device position, or a notes change on a Samsara route through PATCH /fleet/routes/{id}
  • Target capability: propose a dispatcher card in Slack or Microsoft Teams with the planned stop, position, distance off corridor, and approve and dismiss buttons
  • Target capability: propose recording a recurring unplanned location as a Samsara address or a Geotab Zone, so the next visit there is a planned stop

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

What you can build

  • Check in when a Samsara vehicle leaves the corridor

    The stats feed gps type is set against the route's stops and their scheduledArrivalTime. When the vehicle sits outside the corridor you set, the operator proposes a message through POST /v1/fleet/messages, and the reply comes back through GET /v1/fleet/messages.

    With Samsara, Slack

  • Note a Geotab zone stop that was not on the plan

    ExceptionEvent records from ZoneStop rules name the device, driver, zone, and duration. If the zone is not in the Route's routePlanItemCollection, the operator proposes adding it to the Route's comment through Set, for approval in Microsoft Teams.

    With Geotab, Microsoft Teams

  • Act on a Trimble Maps Out of Route notification

    Trip Management raises Out of Route notifications for trips marked InProgress. The operator pairs each with the vehicle's last position and proposes an SMS check-in through Twilio, with the dispatcher's approval first.

    With Trimble Maps, Twilio

  • Turn Route4Me out-of-sequence activity into a route note

    Activity Feed entries typed destination-out-sequence and geofence-left are matched to the route's address list. The operator proposes a note through /actions/addRouteNotes.php with the device latitude and longitude, once the driver has answered.

    With Route4Me, Slack

Requirements

  • A telematics connector that reports positions or geofence events: Samsara, Geotab, Motive, Webfleet, or Verizon Connect Reveal
  • A route source the vehicle's plan lives in: Samsara routes, Geotab Route entities, Route4Me routes, or a Trimble Maps trip marked InProgress
  • A corridor width and a dwell threshold, set per fleet or per route in the operator's configuration
  • Slack or Microsoft Teams for the dispatcher's approval, and a driver channel: the telematics app's messaging or Twilio
Authentication
No credential is stored by the operator. Positions, plans, and messages pass through the connectors you bind, each under the access its own token or session carries.

Limits

  • Detection lags position cadence. Verizon Connect Reveal documents polling a vehicle's location at most every 3 to 5 minutes; Webfleet's standard is one a minute
  • A vehicle with no route in the bound route source is not judged. Without a plan there is no corridor
  • The corridor is a geometric test against the planned path. Road closures and detours are not read unless you bind a signal that carries them
  • It does not resequence stops or reroute the vehicle. A check-in or a note is the proposal; the plan changes only by a person's hand

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 Deviation ↗

Questions and answers

What does the dispatcher approve?
A card per case: the vehicle, the planned stop, where it is instead, how far off the corridor, and how long it has been there. The proposal is a check-in message or a route note. The dispatcher approves it as written, edits the text, or dismisses it with a reason.
What record is left?
Per case: the positions and events read, the corridor applied, the proposal, who approved it and when, the message as sent and the driver's reply, or the note as written. A dismissed case is kept with its reason.
Does it ever message a driver on its own?
No. A check-in leaves only after a dispatcher approves it, and it is sent once. The operator does not reroute vehicles, change stop order, or alter geofences. Recording a recurring location as an address or zone is also a proposal.
Ask about Route Deviation

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