Three things to take away
- Make mileage sources and update times explicit.
- Due, booked, in repair and available are different states.
- Review downtime reasons, work-order closure and task impact together.
The situation: the next assignment meets an open repair
The fleet plans transport by route while a separate spreadsheet tracks maintenance. A dispatcher assigns an online vehicle to the next shift, but the workshop still considers its repair unfinished. The missing connection is an agreed availability state.
Begin with one vehicle record linking mileage sources, maintenance plans and open work orders. Mark unreliable or missing mileage rather than silently replacing an operator-confirmed reading with an estimate.
- Maintenance dueMileage-based reminder
- Return bookingDispatch confirms replacement
- Work in progressBrake inspection
- Acceptance pendingRelease after acceptance
Planning: turn a reminder into a confirmed booking
Configure due conditions using manufacturer guidance and the fleet maintenance policy. Explain whether the trigger uses a date, distance or engine hours. A responsible operator confirms a workshop slot against the return plan; a reminder alone does not reserve capacity.
Dispatch sees booked, in-repair and awaiting-acceptance vehicles. Preserve any replacement assignment. A due reminder, a workshop booking and a vehicle withdrawn from service each require their own confirmation and meaning.
Four confirmations for maintenance coordination
| Operating step | Action | Evidence to review |
|---|---|---|
| Vehicle record | Confirm mileage, hours and maintenance rules | Source, update time and manual corrections |
| Booking | Align workshop capacity and return windows | Confirmed date, owner and replacement plan |
| Work order | Record work and actual downtime | Checks, evidence and parts-waiting reasons |
| Availability | Accept the work before releasing the vehicle | Approver, time and unfinished items |
Execution: connect the repair to return-to-service
The work order records the reported issue, inspection items, actions, supporting documents and actual start and end times. Qualified personnel handle safety-related issues through the established process; clearing a fault code is not evidence of repair.
Require an authorised acceptance step before restoring availability. Across shifts, dispatch needs to see vehicles still awaiting acceptance and any remaining work, rather than assuming that a closed invoice means the vehicle is ready.
Review: distinguish planned work from breakdown downtime
Separate scheduled maintenance, fault repair and parts waiting, then link downtime to affected tasks. Cost comparisons need consistent definitions of parts, labour, outside work and downtime; a single invoice does not describe whole-vehicle cost.
The pilot first tests mileage consistency, booking confirmation and acceptance. Any reduction in emergency replacement or interrupted journeys needs comparison across similar vehicles, routes and duty intensity. Device connectivity alone is not an operating result.
Questions, answered
Can every vehicle use the same service interval?
Do not assume so. The fleet team should confirm intervals against manufacturer requirements, vehicle type, duty and its maintenance policy.
Can this start without vehicle-bus data?
Yes. Confirmed manual mileage, bookings and work orders can support the process while reliable device integration is developed.
