Reference · built on requestOperator by FibricWorkforce & scheduling

Driver Fatigue

Reads ELD hours-of-service status and planned routes and proposes a reassignment before a driver runs out of drive or duty hours.

Request accessPricing ↗

About

Driver Fatigue is an operator job for the hours a driver has left. It reads each driver's hours-of-service clocks from your ELD platform: time until the next required break, drive time remaining, on-duty time remaining in the shift, and cycle time remaining. It reads the route or dispatch planned for that driver and the driving and stop time it will take.

Where the plan needs more than the clocks allow, it proposes a reassignment: the stops to move, the driver with hours to take them, and the time by which the change must be made. The dispatcher approves in Slack or Microsoft Teams, the dispatch is updated once, and the clocks as read at the time are kept with the decision.

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

  • Hours-of-service clocks: Samsara HOS clocks with driveRemainingDurationMs, shiftRemainingDurationMs, cycleRemainingDurationMs, and timeUntilBreakDurationMs
  • Available time per driver: Motive available_time with drive, shift, cycle, and break in seconds; Geotab DutyStatusAvailability with driving, duty, rest, and cycle
  • Current duty status: Samsara currentDutyStatus with hosStatusType, Motive hours_of_service, Geotab DutyStatusLog records
  • Violations already logged: Motive hos_violations and its hos_violation_upserted webhook
  • Planned routes and dispatches: Samsara routes with stops, Motive dispatches, Onfleet tasks and route plans, DispatchTrack planner routes with driving_period per stop
  • Route time under hours-of-service rules: Trimble Maps HoursOfService route reports with estimated arrival times and the stops inserted for compliance
  • Driver shifts as scheduled: Deputy rosters or When I Work shifts, where drivers are scheduled there

Proposed actions

  • Target capability: propose a reassignment of named stops from a driver short of hours to a driver with hours, with the clocks that justify it
  • Target capability: propose the dispatch change: a Samsara route update, a Motive dispatch resent with the new driver, or an Onfleet task reassignment
  • Target capability: propose a message to the dispatcher in Slack or Microsoft Teams with the driver, the shortfall, and the change to approve
  • Target capability: propose a daily list of drivers whose planned routes exceed their clocks, ordered by when the shortfall begins

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

What you can build

  • Reassign Samsara route stops before drive time runs out

    HOS clocks per driver are compared with the route's stops and drive time. Where driveRemainingDurationMs falls short, the operator proposes moving the last stops to a driver with hours, for the dispatcher to approve in Slack.

    With Samsara, Slack

  • Resend a Motive dispatch to another driver

    available_time gives drive, shift, and cycle seconds per driver. A dispatch that needs more than the driver has is proposed for reassignment; once approved, the whole dispatch body is resent with the new driver.

    With Motive, Microsoft Teams

  • Check Onfleet route plans against Geotab availability

    DutyStatusAvailability gives driving and duty time left per driver. Route plans whose task durations exceed it are proposed for task reassignment to a worker with time.

    With Geotab, Onfleet

  • Plan with Trimble Maps HoursOfService reports

    A route report under hours-of-service rules shows estimated arrivals and any stops inserted for compliance. Where the arrivals miss delivery windows, the operator proposes a split across two drivers.

    With Trimble Maps, Samsara

Requirements

  • An ELD connector with hours-of-service clocks or availability: Samsara, Motive, or Geotab
  • A routing or dispatch connector with the driver's planned stops: Samsara routes, Motive dispatches, Onfleet, DispatchTrack, or Trimble Maps trips
  • A Samsara token with the Read ELD Compliance Settings (US) permission, where Samsara is the source
  • Slack or Microsoft Teams for the dispatcher's approval
Authentication
Clocks and routes are read, and dispatch changes proposed, through the connectors you bind, under the access you granted each; the operator owns no credential.

Limits

  • It reads the clocks the ELD computes and computes no hours-of-service of its own. A ruleset or exemption is whatever the ELD applies
  • Samsara returns an empty duty status when the driver app is disconnected; the operator reports that driver as unknown, not available
  • Route time comes from the routing system's estimate. Traffic and dwell beyond the estimate are not foreseen
  • It proposes reassignments; it never changes a driver's duty status, edits a log, or sends a log suggestion

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 Driver Fatigue ↗

Questions and answers

What does the dispatcher approve?
A reassignment: the driver short of hours, the clocks as read and when, the stops to move, the driver proposed to take them, and the deadline for the change. The dispatcher approves, picks another driver, or declines. The dispatch is unchanged until then.
What does it keep after a decision?
The clocks and route read, the shortfall computed, the proposal, the approval with name and time, the dispatch change as the routing system accepted it, and how to reverse it.
Does it ever change a driver's log or status?
No. Logs and duty status belong to the driver and the ELD. The operator reads them, proposes a dispatch change, and stops there.
Ask about Driver Fatigue

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