The Hive · FLEET · Fleet Management
The violation was two stops away.It never happened.
0 hours-of-service checks a day. 0 of them read by a person.
Fleet software is a filing cabinet: hours here, inspections there, fault codes in a portal nobody opens. Fleet Management is the discipline that acts on them together — resequences a route before the hours run out, pulls a truck to the shop on the code that predicts the failure, and keeps a DVIR defect from becoming a roadside inspection.
Figure illustrative until per-tenant telemetry volume is confirmed.
Fleet software vs. Fleet Management
Same trucks. Same drivers.
Different CSA score in June.
One of them records the violation. The other made sure there wasn’t one.
Last night · autonomous
- 18:40Three remaining stops needed two hours five minutes against a driver’s one hour twenty. Resequenced to two stops, moved the third to the morning driver, and held every customer window.violation avoided
- 20:15Unit 318 threw an aftertreatment fault with forty-three hours to derate, against a 620-mile assignment. Pulled it, booked the 06:00 shop slot, and reassigned the load to unit 344.breakdown pre-empted
- 04:22A pre-trip DVIR reported a brake adjustment defect meeting an out-of-service threshold. Held the unit, opened the repair order, and moved the load to a compliant truck.inspection avoided
- 05:10Three units crossed their preventive interval against two open shop slots. Scheduled two, deferred the third inside interval tolerance, and rebalanced routes around the shop days.fleet kept whole
- 06:02A driver’s 34-hour restart would have ended mid-assignment. Re-planned the week so the restart completed before dispatch rather than during it.clock protected
The mandate
We don’t list features.
We publish the job.
Decides on its own
- Reads every driver’s hours against the route still ahead of them, not the route as planned
- Resequences stops before an hours-of-service violation becomes unavoidable
- Acts on engine fault codes by time-to-failure, not by the date of the next service
- Holds any unit whose DVIR defect meets an out-of-service threshold
- Schedules preventive maintenance against shop capacity and interval tolerance together
- Plans 34-hour restarts so they finish before dispatch, not during it
- Files IFTA mileage from the miles actually driven
Escalates to you
- Any resequence that breaks a committed delivery window
- Any deferral that would exceed interval tolerance
- Any driver trending toward a pattern rather than a single event
Never touches
- Load assignment, rate, and carrier selection — that’s TMS
- Raw ELD vendor feeds and their normalization — that’s the ELD Aggregator
- Any driver policy or interval tolerance you set on day one
Act 1 · operations
One fault code.
Four teams already moved.
- FLEETpulls unit 318 and books the shop
- TMSreassigns the 620-mile load to unit 344
- DOCKkeeps the origin appointment on the new tractor
- FINcodes the repair against the unit’s lifetime cost
Governed
Bold is easy.
Bold you can audit is rare.
- Run all three stops. Driver has 1h 20m and the last stop is 25 minutes out.
- Drive time to stop two is 55 minutes, not 25 — the 25 is stop three from stop two. The violation lands at stop two and the log is already electronic.
- Confirmed. Two stops fit inside the remaining clock with fourteen minutes of margin.
- Three-stop run rejected. Two stops completed legally. Third moved to the morning driver.
Both sides of that argument are in your log. Forever.
Your turn
Go ahead.
Break one.
Pick one. Nothing here reaches a person.
Running today.
At a company whose freight is real.
Fleet Management runs hours and maintenance in production at Watchmen Logistics, Elyon SCI’s Customer Zero and freight partner. Every decision on this page is the kind Watchmen’s fleet gets, every day. Running.
Your fleet software can log the violation.
Ask it why there wasn’t one.