Reference · built on requestOperator by FibricFleet, routes & field

Driver Hours

Compares each driver's remaining hours of service with the miles left on the plan and proposes a relay, swap, or reschedule first.

Request accessPricing ↗

About

Driver Hours is an operator job for the gap between what a plan asks of a driver and what the clock allows. It reads drive, shift, and cycle time remaining from the ELD platform, the miles and stops still on the plan, and the roster that says who else is on duty today.

When the miles left will not fit the hours left, it works out the earliest point at which that becomes true and proposes the cheapest fix first: a relay at a yard or named stop on the route, a swap to a driver with hours, or a reschedule of the last delivery. The dispatcher sees the shortfall in hours and miles, the options, and the cut-off time, then approves one. The dispatch is changed once and the clocks as read are kept with the decision.

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

  • Remaining time per driver: Samsara driveRemainingDurationMs, shiftRemainingDurationMs, and cycleRemainingDurationMs, with cycleTomorrowDurationMs for the next day
  • Motive available_time per driver with drive, shift, cycle, and break in seconds, plus seconds_tomorrow in the recap
  • Geotab DutyStatusAvailability with driving, duty, rest, cycle, and workday durations, and whether an adverse driving exemption is available
  • The plan still ahead: Samsara route stops and their scheduled times, Motive dispatches, or a Trimble Maps trip with ETAs per stop
  • Distance and time to each remaining stop from a Trimble Maps Mileage report, and the breaks a HoursOfService report inserts to stay compliant
  • Who is on duty and where, from Deputy rosters or When I Work shifts, so a relay or swap names a working driver
  • Vehicle position from the telematics platform, so the shortfall is measured from where the truck is, not where the plan said

Proposed actions

  • Target capability: propose a relay: the handover point on the route, the driver taking the load, and the hour both must be there by
  • Target capability: propose a driver swap in the dispatch: a Samsara route driverId change, or a Motive dispatch resent with the new driver
  • Target capability: propose a reschedule of the stops that cannot be reached, with the customer window they move to
  • Target capability: propose an open shift or extension in Deputy or When I Work for the relay driver, for the scheduler to publish
  • Target capability: propose the decision to the dispatcher in Slack or Microsoft Teams, with the hours and miles side by side

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

What you can build

  • Relay a Samsara route before drive time runs out

    driveRemainingDurationMs is compared with the drive time to each remaining stop. Where it falls short, the operator proposes a handover at the nearest yard on the route and a driverId change for the stops after it.

    With Samsara, Deputy

  • Swap a Motive dispatch to a driver on the roster

    available_time gives drive, shift, and cycle seconds. A dispatch that needs more is proposed for a swap to a driver When I Work shows on shift, and the dispatch is resent with that driver once approved.

    With Motive, When I Work

  • Check Geotab availability against a Trimble Maps trip

    DutyStatusAvailability gives duty and driving time left. A HoursOfService route report shows where the trip needs a break the driver cannot take. The operator proposes rescheduling the final stop.

    With Geotab, Trimble Maps

  • Offer the relay leg as an open shift

    Once the dispatcher picks a relay, the leg is proposed to Deputy as an open-shift offer to the drivers with hours, so the scheduler publishes it and the dispatch names whoever accepts.

    With Deputy, Microsoft Teams

Requirements

  • An ELD connector that returns remaining time per driver: Samsara, Motive, or Geotab
  • A plan with the stops and miles still ahead: Samsara routes, Motive dispatches, or Trimble Maps trips
  • A scheduling connector with today's roster, Deputy or When I Work, where relays and swaps should name an on-duty driver
  • A Samsara token with the Read ELD Compliance Settings (US) permission, where Samsara supplies the clocks
  • Slack or Microsoft Teams, where the dispatcher approves
Authentication
Clocks, plans, and rosters are read through the ELD, routing, and scheduling connectors you bind, each under its own token; the operator keeps no credential of its own.

Limits

  • Remaining hours are whatever the ELD reports. The operator applies no ruleset of its own and knows no exemption the ELD does not show
  • Miles left come from the routing platform's estimate; a detour or a long dwell shows up only once the vehicle position reveals it
  • A relay point must be a place the plan knows: a yard, a Trimble Maps Site, or a named stop. It does not invent one
  • It never edits a duty status log, sends a log suggestion, or extends a shift without the scheduler publishing it

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

Questions and answers

What does the dispatcher approve?
One of three proposals: a relay with its handover point and time, a swap naming the driver who takes over, or a reschedule of the stops that will not be reached. Each shows the hours left, the miles left, and the point where they cross.
What is kept afterwards?
The clocks as the ELD returned them, the stops and miles read, the roster consulted, the option chosen, the approver and time, and the dispatch change as the routing platform accepted it, with the original assignment kept for reversal.
Can it change a driver's logs or clocks?
No. Logs belong to the driver and the ELD. The operator reads remaining time, proposes a dispatch or shift change, and leaves the log alone.
Ask about Driver Hours

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