Bus Shop MTTR: How to Measure and Reduce Repair Time
Two shops can post the same number of repairs a month and have completely different downtime — because one takes a day to turn a bus around and the other takes four. That gap is bus shop MTTR: mean time to repair, the metric that tells you not how often buses break, but how fast you get them back. And the honest truth most fleets discover when they finally measure it is that almost none of that time is spent turning a wrench.
ANALYTICS & REPORTING · MTTR
Bus Shop MTTR: How to Measure and Reduce Repair Time
MTTR is the clock on how fast your shop returns a bus to service. Measure it, break it into phases, and you'll find the bottleneck — almost never the actual wrench time.
4phases hide inside every repair time
Waitnot wrench, is where the time goes
÷total repair time by number of repairs
WHERE MTTR TIME GOES
Detect 12%Diagnose 20%Wait for parts 48%Repair 20%
What Bus Shop MTTR Really Measures
MTTR gets misread as "how long a tech spends fixing a bus." It's actually the total elapsed time from when a repair starts to when the bus is back in service — and that clock includes a lot of waiting.
WHAT PEOPLE THINK
Measurestime spent turning wrenches
Fixed bytechs working faster
Blamesthe shop's speed
Missesall the waiting in between
WHAT IT IS
Measurestotal start-to-service elapsed time
Fixed byremoving the waits
Revealsthe real bottleneck phase
Includesdetect, diagnose, parts, repair
This is why "make the techs faster" rarely moves MTTR. If half your repair time is a bus sitting idle waiting on a part, no amount of wrench speed touches it — you have to attack the wait.
MTTR is one half of the reliability picture — the recovery half — and pairs with MTBF, the metric for how often buses break. Together they tell the full bus fleet reliability story. This page zeroes in on driving MTTR down. Book a demo to see your MTTR by phase.
How to Calculate Bus Shop MTTR
The formula itself is simple — the value is in what it exposes. Add up the total time buses spent under repair over a period, divide by how many repairs you completed, and you have your mean.
Decide what "repair time" means and stick to it. Measuring only wrench hours gives a flattering number that hides the problem — measure elapsed downtime, the full time the bus was unavailable, or the metric won't help you.
A single MTTR number tells you there's a problem, not where it is. Break each repair into four phases and the bottleneck reveals itself — and it's rarely the phase you'd guess.
1
Detect
From when the defect is flagged to when a work order opens. Dead time before anyone acts — usually small, but pure waste when it isn't.
2
Diagnose
Waiting for a tech and a bay, then finding the fault. Queue time plus troubleshooting — a common hidden drag when the shop is backed up.
3
Wait for parts
The bus sits, diagnosed, while the part is sourced. For most fleets this is the single biggest slice of MTTR — and the most fixable.
4
Repair
The actual wrench time — the phase everyone focuses on, and usually the smallest. Making this faster barely moves the total.
The lesson repeats across fleets: attack phase 3, not phase 4. Stocking the right parts and speeding sourcing does far more for MTTR than pushing techs to wrench faster ever will.
Phase 1 — the flag-to-work-order gap — is its own quiet drain, and closing it is what a purpose-built bus CMMS is designed to eliminate. Once you can see all four phases side by side, the biggest one stops being a guess.
How to Reduce Bus Shop MTTR
Once you can see the phases, cutting MTTR is about attacking the biggest one first — then the next. Four moves target the waits that dominate most fleets' repair time.
1
Stock the Parts That Down Buses
Since parts-wait is usually the biggest phase, right-size your critical spares so a diagnosed bus isn't sitting days for a component. This is the highest-leverage move.
2
Kill the Detect Delay
Auto-create a work order the moment a defect is flagged, so nothing waits in a stack before the clock even starts productively ticking.
3
Prioritize the Bay by Impact
Sequence work so route-critical buses jump the queue, cutting the diagnose-phase wait for the units that matter most to service.
4
Track It and Keep Cutting
Watch MTTR and its phases over time. As you shrink the biggest slice, the next one becomes the target — MTTR reduction is a loop, not a one-time fix.
You can't cut what you don't time. The fleets that drop MTTR fastest are the ones measuring each phase — because that's what tells you whether to fix parts, the queue, or the handoff.
MTTR is only useful when it's measured accurately and split by phase. BusCMMS timestamps repairs as they move through the shop and turns that into an MTTR you can act on, not just report.
Automatic Phase Timestamps
Each repair is timed as it moves — detect, diagnose, parts, repair — so MTTR and its phases are captured without a stopwatch.
timed automatically
MTTR Calculation & Trend
Your MTTR computed for you and tracked over time, so you see whether the number is improving or slipping.
the trend, live
Phase Bottleneck Breakdown
See which phase eats the most time, so you attack the real bottleneck — usually parts-wait — instead of guessing.
find the slice
Slice by Bus, Tech & Type
Break MTTR down by unit, technician, and repair type, so you find where slow repairs concentrate.
pinpoint it
Parts Availability Link
Tie the parts-wait phase to inventory, so the components driving your MTTR up get stocked to bring it down.
attack the wait
Board-Ready KPI Reports
Export MTTR alongside your other KPIs, so shop performance is a chart you can show, not a claim you make.
show the gains
A generic tool logs the repair; a bus-built platform times its phases and shows you the bottleneck — BusCMMS is typically live in 2–4 weeks. Book a demo to see MTTR analytics on your shop.
A Shop Foreman's Take
Key Takeaways on Bus Shop MTTR
MTTR measures recovery speed — and the fix is almost never faster wrenching. Five things to act on.
MTTR — mean time to repair — is the average elapsed time it takes your shop to return a bus to service once a repair begins. It's a measure of recovery speed, distinct from MTBF (mean time between failures), which measures how often buses break in the first place. The most important thing to understand is that MTTR is elapsed time, not just wrench time. It runs from when the repair process starts to when the bus is back in service, and that clock includes all the waiting in between: the time before a work order opens, the queue for a technician and a bay, the wait for parts to arrive, and only then the actual repair. Most fleets that measure MTTR for the first time are surprised to find the hands-on repair is often the smallest slice, while waiting — especially waiting on parts — dominates. That's why MTTR is so useful: it captures the whole downtime experience of a repair, not just the labor, so it points you at the real reasons buses sit longer than they should.
How do you calculate bus shop MTTR?+
The formula is straightforward: total repair downtime divided by the number of repairs over the same period. If your buses spent a combined 120 hours under repair across 30 completed repairs in a month, your MTTR is 4 hours. The simplicity of the math is deceptive, though — the accuracy depends entirely on how you define "repair downtime." If you measure only the hours a technician was actively working, you'll get a flattering number that hides your real problem, because it excludes all the waiting that actually keeps buses off the road. The meaningful version measures elapsed downtime: the full time the bus was unavailable from the start of the repair process to its return to service. Pick that definition and apply it consistently. Beyond the single headline number, the real value comes from tracking MTTR as a trend over time and slicing it — by individual bus, by technician, by repair type — so you can see where slow repairs concentrate. A CMMS that timestamps repairs automatically removes the manual effort and the temptation to measure only the convenient part.
Why is my MTTR high even though my techs are fast?+
Because MTTR is dominated by waiting, not wrenching — so fast technicians can coexist with a high MTTR. Break any repair into four phases and it becomes clear. Detect is the gap from a defect being flagged to a work order opening. Diagnose is the queue for a tech and bay plus the troubleshooting itself. Wait-for-parts is the diagnosed bus sitting idle while the component is sourced. Repair is the actual hands-on work. For most fleets, wait-for-parts is the single largest slice, and the actual repair is one of the smallest. So if your techs are quick but buses still take days to turn around, the culprit is almost certainly one of the waiting phases — usually parts. This is exactly why "make the shop faster" so often fails to move the number: you're optimizing the smallest slice while the biggest one goes untouched. The fix is to measure each phase, find the dominant wait, and attack that — stock the parts, speed the handoff, prioritize the queue. Fast wrench time is worth having, but it's not where high MTTR comes from.
How do you reduce MTTR in a bus fleet?+
Attack the biggest phase first, and for most fleets that's the parts wait. Right-size your critical spares so a diagnosed bus isn't sitting for days waiting on a component you could have had on the shelf — this is typically the highest-leverage single move you can make on MTTR. Second, kill the detect delay by auto-creating a work order the moment a defect is flagged, so nothing sits in a stack before the repair process starts. Third, prioritize the bay by impact so route-critical buses jump the queue, cutting the diagnose-phase wait for the units that matter most to service. Fourth, and underpinning all of it, track MTTR and its phases continuously — as you shrink the biggest slice, the next one becomes your target, so MTTR reduction is a repeating loop rather than a one-time project. The essential enabler is measurement by phase: you cannot cut a wait you have never timed, and you cannot prove an improvement worked without a before-and-after. Fleets that break MTTR into phases and chase the dominant one consistently see the number fall — often dramatically — without their technicians working any harder.
How does BusCMMS help measure and reduce MTTR?+
BusCMMS makes MTTR a measured, actionable metric rather than a rough guess. Automatic phase timestamps time each repair as it moves through the shop — detect, diagnose, parts, repair — so MTTR and its component phases are captured without anyone running a stopwatch. MTTR calculation and trend computes the number for you and tracks it over time, so you see whether it's improving or slipping. The phase bottleneck breakdown shows which phase eats the most time, so you attack the real constraint — usually parts-wait — instead of guessing. You can slice MTTR by bus, technician, and repair type to find exactly where slow repairs concentrate. The parts-availability link ties the parts-wait phase to inventory, so the components driving your MTTR up are the ones that get stocked to bring it down. And board-ready KPI reports let you export MTTR alongside your other metrics, turning shop performance into a chart you can show leadership rather than a claim you have to defend verbally. Because it's purpose-built for bus fleets, the repair timing and the parts and inventory data live together, which is what makes phase-level MTTR analysis practical. Most fleets are live in two to four weeks.
