What is MTTR in maintenance?

MTTR is Mean Time To Repair, the average time to restore an asset after a failure, calculated as Total Repair Hours divided by Number of Repairs. With 28 hours across 8 repairs, MTTR is 3.5 hours. It spans failure detection through verified restoration, including response, diagnosis, parts retrieval, and repair, so it reflects true production impact rather than just wrench time.

How do I calculate MTTR for the quarter?

Add up all corrective repair time in the period and divide by the number of completed repairs. Eight failures totaling 28 repair hours gives MTTR = 28 / 8 = 3.5 hours. Use CMMS timestamps from failure detection to restoration, include parts wait and diagnosis time, and exclude planned maintenance jobs so the metric reflects only unplanned corrective recovery.

What is a good MTTR target?

It depends on asset criticality and access to spares, so benchmark against your own trend and similar equipment. For many production assets, several hours is typical; critical bottlenecks often target under one hour. More important than the absolute number is the breakdown. If 3.5 hours includes 2 hours of parts retrieval, the fix is stocking spares, not working faster.

Why is my MTTR higher than the actual repair time?

Because MTTR includes more than the physical repair. It starts at failure detection and covers response time, diagnosis, parts retrieval, the repair, and verification. If the wrench time is 1 hour but MTTR is 3.5 hours, the other 2.5 hours is response, waiting on parts, and testing. That gap is your improvement target, usually parts availability or diagnosis speed.

Should MTTR be in hours or minutes?

Use whichever gives readable numbers for your assets, but keep the unit consistent. Most maintenance teams report hours, like 3.5 hours per repair. For fast-recovery lines where repairs take a few minutes, minutes are clearer. Whatever you choose, make sure Total Repair Hours and Number of Repairs use the same period and the same start point, failure detection, across every asset compared.

MTTR vs MTBF, how do they work together?

MTBF measures how often an asset fails; MTTR measures how long it takes to recover. Together they set availability: Availability = MTBF / (MTBF + MTTR). With MTBF of 600 hours and MTTR of 3.5 hours, availability is 600 / 603.5, about 99.4%. Improve MTBF to fail less often and MTTR to recover faster; both raise uptime, but through different actions.

Maintenance and Reliability

MTTR Formula

Mean Time to Repair (MTTR) is the average time needed to restore an asset to operating condition after a failure. Use it to evaluate maintainability, size technician coverage, and find repair steps that slow recovery.

Formula

MTTR = Total Repair Hours / Number of Repairs

Variables

Total Repair Hours: Sum of all time spent repairing failures in the period, from failure detection to restoration
Number of Repairs: Count of completed corrective repairs in the same period

Understanding the MTTR Formula

MTTR measures maintainability: once an asset fails, how long does it take to get it running again. It divides Total Repair Hours by Number of Repairs, so 28 repair hours over 8 failures gives 3.5 hours per repair. Unlike MTBF, which is about how often you fail, MTTR is about how fast you recover. Long MTTR points to slow diagnosis, poor parts availability, or missing documentation, all of which are fixable without touching the equipment itself.

Start the clock at failure detection, not technician arrival, and stop it at verified restoration. Total Repair Hours should include response time, diagnosis, parts retrieval, the physical repair, and verification. Pull these from CMMS work-order timestamps. In the example, 8 completed corrective repairs consumed 28 hours total. Exclude planned maintenance jobs; MTTR is about corrective recovery. If parts wait time is logged separately, add it in, because it often dominates the total.

A 3.5 hour MTTR is only meaningful against your recovery target and its breakdown. Decompose it: if 2 of the 3.5 hours is parts retrieval, stock those spares locally rather than chasing faster wrenching. Trend MTTR alongside MTBF; combined, they set availability. Rising MTTR with steady MTBF means recovery is degrading, often from staffing gaps or eroded tribal knowledge. Target the longest repair steps first, since the mean is usually pulled up by a few slow jobs.

Worked Example

A production asset had 8 failures in the quarter. Total repair time was 28 hours.

MTTR = 28 / 8 = 3.5 hours per repair

Result: 3.5 hours average repair time

Common Mistake

Starting the clock at technician arrival instead of failure detection. MTTR should include response time, diagnosis, parts retrieval, repair, and verification. Excluding response and parts wait time makes MTTR look lower than the real production impact.

Frequently Asked Questions

What is MTTR in maintenance?: MTTR is Mean Time To Repair, the average time to restore an asset after a failure, calculated as Total Repair Hours divided by Number of Repairs. With 28 hours across 8 repairs, MTTR is 3.5 hours. It spans failure detection through verified restoration, including response, diagnosis, parts retrieval, and repair, so it reflects true production impact rather than just wrench time.
How do I calculate MTTR for the quarter?: Add up all corrective repair time in the period and divide by the number of completed repairs. Eight failures totaling 28 repair hours gives MTTR = 28 / 8 = 3.5 hours. Use CMMS timestamps from failure detection to restoration, include parts wait and diagnosis time, and exclude planned maintenance jobs so the metric reflects only unplanned corrective recovery.
What is a good MTTR target?: It depends on asset criticality and access to spares, so benchmark against your own trend and similar equipment. For many production assets, several hours is typical; critical bottlenecks often target under one hour. More important than the absolute number is the breakdown. If 3.5 hours includes 2 hours of parts retrieval, the fix is stocking spares, not working faster.
Why is my MTTR higher than the actual repair time?: Because MTTR includes more than the physical repair. It starts at failure detection and covers response time, diagnosis, parts retrieval, the repair, and verification. If the wrench time is 1 hour but MTTR is 3.5 hours, the other 2.5 hours is response, waiting on parts, and testing. That gap is your improvement target, usually parts availability or diagnosis speed.
Should MTTR be in hours or minutes?: Use whichever gives readable numbers for your assets, but keep the unit consistent. Most maintenance teams report hours, like 3.5 hours per repair. For fast-recovery lines where repairs take a few minutes, minutes are clearer. Whatever you choose, make sure Total Repair Hours and Number of Repairs use the same period and the same start point, failure detection, across every asset compared.
MTTR vs MTBF, how do they work together?: MTBF measures how often an asset fails; MTTR measures how long it takes to recover. Together they set availability: Availability = MTBF / (MTBF + MTTR). With MTBF of 600 hours and MTTR of 3.5 hours, availability is 600 / 603.5, about 99.4%. Improve MTBF to fail less often and MTTR to recover faster; both raise uptime, but through different actions.