Value Stream Mapping for Fleet Maintenance: From Breakdown Report to Back-on-Road Without the Bay Bottleneck

A commercial vehicle is not generating value while it is waiting in a yard, sitting outside a repair bay or held up by an unanswered approval request. For fleet operators, every hour of downtime can affect delivery reliability, customer commitments, driver utilisation and operating cost.

Value Stream Mapping (VSM) provides a structured way to see the complete flow from breakdown report to back-on-road release. Rather than focusing only on technician wrench time, it examines the movement of the vehicle, parts, information, approvals and decisions across the entire maintenance process.

In the realm of commercial fleet maintenance, the fundamental purpose of VSM is to distinguish customer-value-adding repair activity from waiting, rework, unnecessary movement and avoidable administrative delay. The result is a fact-based improvement plan that identifies whether the repair bay is genuinely the bottleneck: or whether the constraint sits in parts, approvals, scheduling or information flow.

This guide presents a worked example for a truck and delivery-vehicle fleet using Lean Six Sigma principles.

1. Select the Right Fleet Maintenance Value Stream

Do not begin by mapping every maintenance activity at once. Preventive maintenance, accident repairs, roadside assistance and breakdown repairs may follow different paths and should usually be treated as separate value streams.

For this guide, the scope is:

From the moment a driver or telematics system reports a breakdown to the moment the vehicle is verified, released and available for dispatch.

The scope includes:

• Breakdown reporting and triage
• Towing or vehicle transport
• Yard check-in
• Bay allocation
• Diagnosis
• Approval
• Parts sourcing and staging
• Repair
• Verification and road test
• Work-order closeout and dispatch release

The customer is the internal or external fleet operator that requires a safe, reliable vehicle. Relevant CTQs: Critical to Quality requirements: may include:

• Total vehicle downtime
• Percentage of repairs completed within the service-level agreement
• First-pass repair success
• Repair cost
• Safety and compliance
• Availability for the next scheduled route

A practical VSM team should include dispatch, fleet management, technicians, parts personnel, service advisors and finance or approval representatives. The people who perform the work understand the actual process, including workarounds that may not appear in the fleet management system.

2. Build the Current-State Map at the Gemba

A current-state map should reflect what actually happens, not what the standard operating procedure says should happen. Walk several vehicles through the process and collect timestamps from system records, work orders and direct observation.

Capture both physical flow and information flow.

Physical flow

• Vehicle breaks down
• Driver reports the issue
• Dispatch arranges roadside assistance or towing
• Vehicle arrives at the depot
• Vehicle waits for a bay
• Technician diagnoses the fault
• Parts are sourced and staged
• Repair is completed
• Vehicle is tested
• Vehicle is released to dispatch

Information flow

• Breakdown report
• Triage decision
• Estimate and approval request
• Parts availability confirmation
• Technician assignment
• Repair status updates
• Completion notification
• Fleet availability update

For every process step, record:

• Processing time
• Waiting time
• Work in process
• Number of handoffs
• Rework or repeat repair
• Available capacity
• First-pass yield
• Primary cause of delay

A Time Observation Sheet is valuable because it separates actual work from waiting. A repair order may show eight hours between arrival and completion, yet direct observation may reveal only three hours of diagnosis, repair and testing. The remaining five hours may consist of queue time, approval delay or parts searching.

3. Worked Example: 240 Breakdown Repairs per Month

Consider a delivery fleet operating from one depot. The maintenance team reviews 30 recent breakdown repairs and identifies the following average current-state performance:

The average total lead time is approximately 44.5 hours, while value-adding or essential processing time totals 7.25 hours.

Process Cycle Efficiency is calculated as:

[
\text{PCE} = \frac{\text{Value-added time}}{\text{Total lead time}} \times 100
]

[
\text{PCE} = \frac{7.25}{44.5} \times 100 = 16.3%
]

This means the vehicle is actively being diagnosed, repaired or verified for only about 16.3% of its time in the stream.

Is the bay really the bottleneck?

The depot has three repair bays and 20 available maintenance hours per day after breaks, meetings and planned work. Average breakdown demand is 12 vehicles per day.

[
\text{Takt time} = \frac{20 \text{ available hours}}{12 \text{ breakdowns}} = 1.67 \text{ hours per vehicle}
]

The average repair cycle time is 3.0 hours per vehicle, significantly higher than the required takt time. The bay queue also holds an average of 9 vehicles, and bay utilisation is measured at 94%.

These indicators strongly suggest that repair capacity is a constraint. However, the map also shows that approval and parts delays are extending the queue. The correct response is not automatically to build another bay. First, the team should determine how much capacity can be recovered by improving the entire flow.

For further background on identifying bottlenecks through end-to-end mapping and takt time, see this Value Stream Mapping and bottleneck capacity guide.

4. Identify the Eight DOWNTIME Wastes

Mark the eight wastes directly on the current-state map.

• Defects: Incorrect diagnosis, incomplete breakdown descriptions or repeat repairs.
• Overproduction: Performing non-urgent work while breakdown vehicles remain queued.
• Waiting: Vehicles waiting for a bay, approval, parts, technicians or road-test capacity.
• Non-utilised talent: Technicians spending time searching for information instead of solving recurring causes.
• Transportation: Unnecessary towing, vehicle repositioning or movement between facilities.
• Inventory: Excessive work in process, unneeded parts or vehicles awaiting decisions.
• Motion: Walking to find tools, parts, paperwork or diagnostic equipment.
• Extra-processing: Duplicate data entry, repeated inspections and multiple approval steps.

In this example, the largest visible waste is waiting, but waiting is a symptom rather than a root cause. Its drivers include bay capacity, incomplete information, approval rules and parts availability.

The map should also show work in process at each queue. Nine vehicles waiting for bays, four waiting for approval and six waiting for parts provide more useful insight than a single average downtime measure.

5. Build the Future-State Map

A future-state map describes a practical operating condition, not an idealised long-term vision. It should show how vehicles, information and decisions will flow with fewer queues and clearer ownership.

For the worked example, the future state includes:

1. A standard digital breakdown form requiring fault category, vehicle location, symptoms and safety status.
2. A visual triage rule separating mobile repair, towing, fast-track work and planned repair.
3. A dedicated breakdown queue with clear FIFO rules and escalation criteria.
4. Pre-approved repair thresholds for routine, low-cost decisions.
5. A supermarket or Kanban system for high-frequency breakdown parts.
6. Standard work for diagnosis, tool preparation and common repair families.
7. Parts kitting before the vehicle enters the bay.
8. A daily capacity board showing available bays, technicians and priority vehicles.
9. Andon-style visual signalling when a vehicle exceeds its planned waiting time.
10. A single digital release transaction connecting maintenance status to dispatch availability.

The future-state design should also support Y = f(x) thinking. Vehicle downtime, the output Y, is influenced by inputs such as breakdown information quality, approval lead time, parts availability, technician capacity and repair-method consistency. Controlling these critical inputs improves the outcome more reliably than simply asking technicians to work faster.

Current state versus future state

These are project targets, not universal benchmarks. The team should validate them using its own fleet mix, operating hours, repair complexity and demand pattern.

6. Sequence Kaizen in the Right Order

Improvement should be sequenced so that each intervention supports the next.

1. Stabilise measurement

Define downtime, waiting time, repair time, first-pass yield and bay utilisation consistently. Check for measurement bias caused by missing timestamps or delayed system entries.

2. Improve breakdown information

Standardise the initial report so technicians receive usable information before the vehicle arrives. This reduces triage delay and prevents avoidable diagnostic repetition.

3. Establish visual flow control

Create clear status categories: awaiting tow, awaiting bay, diagnosing, awaiting approval, awaiting parts, repairing, testing and ready for dispatch.

4. Reduce approval delay

Formal approval checkpoints support governance, but unnecessary layers can create bottlenecks. Introduce thresholds that allow routine decisions to proceed without repeated escalation.

5. Improve parts availability

Use failure-mode data to set minimum stock levels for critical parts. Kit common repairs before the vehicle enters the bay.

6. Release bay capacity

Apply standard work, tool organisation and job preparation to reduce repair variation. Separate quick repairs from complex work where practical.

7. Pilot and verify

Use short Agile improvement cycles: test one change, measure the result, review frontline feedback and adjust before expanding. Compare averages, percentiles, queue size and first-pass yield: not only total downtime.

8. Control the gains

Use daily management, standard work and a KPI board. Where the data structure is appropriate, an X-bar and R chart can monitor repair-time averages and variation. For skewed downtime data, use medians, percentiles and box plots alongside the average.

Turn Fleet Downtime into a Structured Improvement Opportunity

Value Stream Mapping helps fleet leaders move beyond the assumption that every delay is caused by technician performance. It reveals the interaction between bays, parts, approvals, dispatch, information and customer demand.

Whether you are a fleet manager, operations leader, process analyst or maintenance supervisor, Lean Six Sigma training can help you apply VSM within the broader DMAIC framework. The Lean Six Sigma Practitioner’s Guide provides a useful foundation, while the CSSC-accredited Green Belt course develops the skills required to lead data-driven improvement projects.

Pursue Lean Six Sigma certification and learn to map the complete flow, confirm the true constraint and return more vehicles to the road with greater speed, reliability and control.

Kaizen. Kai-Care. Kai-Done. ( Lean Six Sigma)