MTTR and MTBF are the two numbers every maintenance manager reports — and the two most maintenance managers calculate wrong. The errors are not arithmetic. They are definitional: counting planned maintenance as a failure, including parts-shipping wait time in repair time, disagreeing on what even constitutes a "failure," and the single most common mistake — reporting Mean Down Time (MDT) while calling it MTTR, which makes a team's numbers look structurally worse than peers who measure correctly. These are not academic distinctions. Unplanned downtime cost industrial operations an average of $532,000 per hour in 2024, and the decisions that reduce it — which assets to replace, which to monitor, where to invest preventive maintenance budget — all flow from MTTR and MTBF being measured consistently. MTBF (Mean Time Between Failures) tells you how reliable an asset is: how long it runs before breaking. MTTR (Mean Time To Repair) tells you how maintainable it is: how fast your team restores it. Together they produce availability — the number that actually determines whether your fleet meets its commitments. This guide gives maintenance managers the correct calculation methodology for both metrics, the worked examples that show the math, the common errors that corrupt the numbers, and the benchmarks by fleet and equipment type that tell you whether your performance is good or just average. HVI's inspection & maintenance software calculates both metrics automatically from every closed work order — no spreadsheets, no manual math, no two-week lag.
Stop Calculating Reliability Metrics by Hand
HVI computes MTTR, MTBF, and availability automatically from every work order closed — per asset, per site, updated in real time. No spreadsheets. No definitional errors. No lag.
MTTR vs MTBF: The Core Distinction
The two metrics answer two different questions. Confusing them — or optimizing one while ignoring the other — is how maintenance teams end up firefighting instead of preventing.
MTBF
Mean Time Between Failures
"How reliable is it?"
Average operating time between one failure and the next. Measures reliability. Higher is better. A rising MTBF means your assets are breaking less often.
GOAL: Increase it
+
together =
Availability
MTTR
Mean Time To Repair
"How fast do we fix it?"
Average active repair time from failure detection to restoration. Measures maintainability. Lower is better. A falling MTTR means your team resolves failures faster.
GOAL: Decrease it
The Formulas — Exactly as They Should Be Calculated
Three formulas, one relationship. Get the inputs right and the numbers are trustworthy. Get them wrong and every decision built on them is wrong too.
There is also Failure Rate (λ) = 1 ÷ MTBF, used in reliability engineering. For most fleet maintenance decisions, MTBF, MTTR, and Availability are the working trio.
Start free with HVI and get all three computed automatically.
Worked Example: A Fleet Vehicle Over One Quarter
Numbers make it concrete. Here is the full calculation for a single asset over a 13-week quarter — the same methodology applies whether you are measuring one truck or a 500-vehicle fleet.
THE DATA
Scheduled operation (Q1)2,160 hrs
Total downtime (repairs)18 hrs
Number of failures3
Repair times2.5 + 4.0 + 3.5 hrs
STEP 1 — MTBF
Operating time = 2,160 − 18 = 2,142 hrs
MTBF = 2,142 ÷ 3 = 714 hours
The vehicle runs about 714 hours (roughly 30 days) between failures.
STEP 2 — MTTR
Total repair = 2.5 + 4.0 + 3.5 = 10.0 hrs
MTTR = 10.0 ÷ 3 = 3.33 hours
When it fails, active repair takes about 3.3 hours on average.
STEP 3 — AVAILABILITY
714 ÷ (714 + 3.33) = 99.5%
The vehicle is available 99.5% of the time it is needed.
The 5 Math Errors That Corrupt Your Numbers
Every one of these makes your metrics look different from reality — usually worse, sometimes dangerously better. They are the reason two fleets with identical actual performance report wildly different MTTR and MTBF.
1
Reporting MDT as MTTR
The biggest error. Mean Down Time includes parts-shipping, wait-for-technician, and shift delays. MTTR is active repair time only. A failure with 1.5 hrs repair but 14 hrs waiting for overnight parts is 1.5 hrs MTTR, not 15.5 hrs. Reporting MDT as MTTR makes your team look slow versus peers who measure correctly.
2
Counting Planned PM as Failures
Scheduled preventive maintenance is not a failure. Including PM events in the failure count deflates MTBF artificially — making reliable assets look unreliable and triggering unnecessary replacement decisions.
3
Including Downtime in Operating Time
MTBF operating time is the time the asset was actually running. Forgetting to subtract repair and PM downtime inflates MTBF — making assets look more reliable than they are and masking a deteriorating trend.
4
Inconsistent "Failure" Definition
Does a 12-minute operator-cleared stoppage count? Pick one policy (e.g. "failures are stoppages requiring maintenance intervention") and apply it every time. Inconsistency makes period-over-period trends meaningless.
5
Mixing Asset Classes
Averaging MTBF across a dump truck and a pickup produces a number that describes neither. Calculate per asset class, per site — then roll up. A fleet-wide average hides the assets actually dragging down performance.
Errors 1–5 all stem from manual calculation. HVI applies one consistent definition to every closed work order automatically — active repair time, true operating hours, failures vs PM correctly separated, per asset class.
Book a demo to see the methodology enforced.
MTTR vs MDT: The Distinction That Trips Everyone
This deserves its own section because it is error #1 and the most consequential. The difference between MTTR and MDT is the difference between measuring your team and measuring your whole supply chain.
Failure Event
Active Repair (MTTR)
Wait Time
Total Down (MDT)
Weekend off-shift failure
1.5 hrs
6 hrs (team arrival)
7.5 hrs
Failure needing overnight parts
8 hrs
14 hrs (parts shipping)
22 hrs
In-stock parts, on-shift
3 hrs
0 hrs
3 hrs
Why it matters: MTTR measures your maintenance team's efficiency. MDT measures your entire support chain — parts inventory, scheduling, shift coverage. Both are useful, but reporting MDT as MTTR penalizes your technicians for supply-chain delays they do not control. Track them separately.
Benchmarks by Fleet & Equipment Type
"Is 714 hours MTBF good?" depends entirely on the asset. Here are working benchmark ranges by equipment type. Use them to know whether your numbers are strong, average, or a problem.
Equipment Type
Typical MTBF
Typical MTTR
Target Availability
Heavy-duty truck (Class 8)
500–900 hrs
3–6 hrs
95%+
Light-duty fleet vehicle
800–1,500 hrs
2–4 hrs
97%+
Wheel loader / heavy equipment
400–700 hrs
4–8 hrs
93%+
Forklift (warehouse)
600–1,200 hrs
2–5 hrs
96%+
Trailer / towed asset
1,500–3,000 hrs
2–4 hrs
98%+
Industrial pump / rotating
700–1,000 hrs
3–5 hrs
99%+
Benchmarks are starting points, not targets. The real signal is your own trend: a declining MTBF on any asset is an early warning that condition is deteriorating — act before the breakdown.
Start free with HVI and track trends per asset automatically.
What the Numbers Tell You to Do
MTTR and MTBF are not report-card numbers to file away. Each combination of high/low points to a specific action. Here is the decision matrix.
High MTBF + Low MTTR
Best case
Assets are reliable and fix fast. Maintain the program, document what works, and apply it to weaker asset classes.
High MTBF + High MTTR
Slow repairs
Assets rarely break, but when they do, repairs drag. Focus on parts inventory, technician training, and diagnostic speed.
Low MTBF + Low MTTR
Firefighting
Team fixes fast but assets keep breaking. You are excelling at reaction, not prevention. Invest in preventive maintenance and root-cause analysis.
Low MTBF + High MTTR
Critical
Assets break often and take long to fix. Availability is collapsing. Requires immediate structured improvement — likely asset replacement plus program overhaul.
Measure Consistently, Then Act on the Trend
MTTR and MTBF are only as useful as they are consistent. The formulas are simple — MTBF is operating time divided by failures, MTTR is active repair time divided by failures, and availability is MTBF over MTBF plus MTTR. The difficulty is never the arithmetic; it is the definitional discipline: counting only true failures, measuring active repair time rather than total downtime, excluding planned maintenance, applying one failure definition every period, and calculating per asset class rather than blending everything into a meaningless fleet average. Get those right and the numbers tell you exactly where to act — whether you are in the firefighting quadrant that needs preventive investment, the slow-repair quadrant that needs better parts and training, or the critical quadrant that needs asset replacement. Get them wrong and you make expensive decisions on corrupted data. The benchmarks in this guide tell you whether your numbers are strong for your equipment type, but the more important signal is always your own trend line — a declining MTBF on any asset is an early warning to act before the breakdown. HVI's inspection & maintenance software removes the manual-calculation error entirely: it computes MTTR, MTBF, and availability automatically from every closed work order, applies one consistent definition across the fleet, separates failures from planned maintenance correctly, and surfaces the per-asset trends that tell you what to do next — all updated in real time instead of two weeks out of date in a spreadsheet. Start free today or book a 30-minute demo to see your reliability dashboard live on your fleet.
Get MTTR, MTBF & Availability Calculated Automatically
Real-time metrics from every closed work order. One consistent definition fleet-wide. Per-asset trend tracking. Failures separated from PM. No spreadsheets, no lag. Trusted by 25,000+ users worldwide.
Frequently Asked Questions
Q: What is the difference between MTTR and MTBF?
MTBF (Mean Time Between Failures) measures reliability — how long an asset runs before it fails, calculated as total operating time divided by number of failures. MTTR (Mean Time To Repair) measures maintainability — how fast your team restores a failed asset, calculated as total repair time divided by number of failures. MTBF answers "how often does it break," MTTR answers "how fast do we fix it." Together they produce availability.
Q: How do I calculate availability from MTTR and MTBF?
Availability = MTBF ÷ (MTBF + MTTR), expressed as a percentage. For example, a vehicle with 714-hour MTBF and 3.33-hour MTTR has availability of 714 ÷ (714 + 3.33) = 99.5%. Availability is the number that matters most for fleet commitments — it tells you what percentage of needed time the asset is actually ready to work.
Start free with HVI.
Q: What is the most common MTTR calculation error?
Reporting Mean Down Time (MDT) while calling it MTTR. MTTR is active repair time only — from failure detection to restoration. MDT includes wait time: parts shipping, technician arrival, shift delays. A failure with 8 hours of repair but 14 hours waiting for overnight parts is 8 hours MTTR and 22 hours MDT. Reporting the 22 as MTTR makes your team look slow versus peers who measure correctly. Track both, but never confuse them.
Book a demo.
Q: Should planned maintenance count as a failure in MTBF?
No. Scheduled preventive maintenance is not a failure and must be excluded from the failure count. Including PM events deflates MTBF artificially — making reliable assets look unreliable and potentially triggering unnecessary replacement decisions. Only count unplanned stops that require maintenance intervention to restore function. Also exclude PM downtime from operating time when calculating MTBF.
Q: What is a good MTBF for a heavy-duty truck?
Working benchmark for a Class 8 heavy-duty truck is 500–900 hours MTBF with 3–6 hours MTTR, targeting 95%+ availability. Light-duty fleet vehicles run higher (800–1,500 hr MTBF), heavy equipment like wheel loaders lower (400–700 hr). But benchmarks are starting points — the more important signal is your own trend. A declining MTBF on any asset is an early warning to act before the breakdown.
Start free today.
Q: How does HVI calculate these metrics?
HVI computes MTTR, MTBF, and availability automatically from every work order closed — per asset, per site, updated in real time. It applies one consistent failure definition across the fleet, correctly separates failures from planned maintenance, measures active repair time rather than total downtime, and surfaces per-asset trends. This eliminates the manual-calculation errors that corrupt spreadsheet-based metrics and removes the typical two-week reporting lag.
Book a demo to see the reliability dashboard.
.png)
