Fleet Vehicle Downtime Cause Attribution Rate

Fleet vehicle downtime cause attribution rate asks how many unavailable periods have a verified primary cause, so the first step is to separate planned work, since scheduled maintenance downtime differs from an unexpected failure. A downtime episode should have an owner even while its cause is unsettled, because the dispatcher can confirm when the truck stopped taking assignments and maintenance can later establish the failed component without inventing a diagnosis at dispatch.

Classify a vehicle that breaks down away from its depot using the same start rule as a local fault, since towing and transit to a repair shop are real unavailable time even if the maintenance ticket opens later. Choose a primary-cause rule before comparing depots.

If it means the initiating incident, a battery fault remains primary despite a long supplier wait, while if it means the longest delay, parts availability may be primary instead. Keep the chronological intervals in the record rather than changing the headline category every time the vehicle moves, since diagnosis, active repair, parts waiting, external transport and return inspection each describe a different use of unavailable hours, and when multiple repairs happen in one visit, split time only where records support it.

Fix the episode boundaries carefully, since if a contractor invoice arrives after the truck is released, the invoice date is not the downtime end, so compare repair release, safety sign-off and dispatch availability to establish the defensible boundary, and compare work-order notes with dispatch status where timestamps disagree, because the garage may mark a job finished before the safety reviewer clears the vehicle. A warranty claim that delays authorisation belongs in the elapsed downtime even if the repair cost is later reimbursed, and a rented replacement is not evidence the original vehicle was ready, so keep rental expense or cover capacity alongside the asset record.

An accident with body damage may also expose an overdue inspection, so code the collision as the incident and preserve the inspection as a distinct reason the vehicle could not return on the expected date. Check the assignment calendar when calculating lost service, because a bus not scheduled during the repair still has asset downtime but may have caused no missed passenger journey, so report the two outcomes separately.

Set a review cut-off for open episodes, since an asset still undergoing diagnosis belongs in the denominator with an unknown or provisional code according to the stated rule, not outside the calculation altogether. Count episodes and unavailable hours side by side, because a large number of short tire incidents can matter for call-out capacity while one long engine repair dominates asset-hours lost.

When a cause is corrected after investigation, retain the first code and reviewer decision, so a later verified finding can change the current report while the audit trail explains earlier published numbers. Keep a recurrence link when the same failure appears after a recent repair, because it may be a distinct downtime episode but the investigation should see the earlier work and tested fix.

Test the coding guide on two ambiguous cases from different depots, and if reviewers choose different primary causes for the same timeline, clarify examples before using the rate to compare locations. Report how many cases lack enough evidence to classify.

A high attribution score can still conceal weak diagnosis if the difficult episodes were excluded or treated as a generic other category. Use the rate to plan maintenance, parts and spares, not to assign blame to a team.