MTTR (Mean Time To Repair) is the average time required to repair a failed asset and restore it to full operational status.
What is MTTR?
MTTR measures the average duration from the moment a failure is detected to the moment the asset is returned to service. It covers every step of the repair process: diagnosis, parts procurement, physical repair, and post-repair testing. Maintenance teams use MTTR as a primary KPI to evaluate repair efficiency, plan staffing levels, and benchmark performance across facilities and equipment classes.
Unlike MTBF (Mean Time Between Failures), which tracks how long equipment runs before breaking down, MTTR focuses exclusively on the repair window. A low MTTR indicates that a team can respond and resolve failures quickly, minimising production losses. A high MTTR signals bottlenecks in spare parts supply, technician availability, or diagnostic capability that extend each downtime event.
MTTR is most commonly applied in manufacturing, IT infrastructure, and energy sectors where unplanned downtime carries significant financial consequences. In 2026, as predictive maintenance tools become more widespread, reducing MTTR remains a fundamental objective because even accurately predicted failures still require efficient repair to limit their operational and financial impact.
Key Characteristics of MTTR
Understanding what MTTR represents requires recognising the attributes that distinguish it from other maintenance metrics.
- Measures the full repair cycle — from initial failure detection through diagnosis, parts sourcing, physical repair, and post-repair verification testing until the asset is fully operational again.
- Expressed in hours or minutes — industry benchmarks vary significantly by sector; a wind turbine may measure MTTR in days while a CNC machine targets minutes.
- Directly correlated with downtime cost — every additional hour of MTTR equals lost production revenue, overtime labour, and potential penalty clauses in service-level agreements.
- Calculated as total repair time divided by number of repairs — the formula is straightforward, but consistent data collection across the repair workflow is essential for accuracy.
- Sensitive to supply chain efficiency, technician skill, and diagnostic tooling — improvements in any of these areas can produce measurable MTTR reductions without capital investment in new equipment.
MTTR Formula
The calculation for Mean Time To Repair is straightforward:
MTTR = Total Repair Time / Number of Repairs
For example, if a packaging line motor fails three times in a month and the repair times are 5.4 hours, 3.2 hours, and 4.1 hours, the calculation is: MTTR = (5.4 + 3.2 + 4.1) / 3 = 4.23 hours. This means that on average, each repair on that motor took approximately 4 hours and 14 minutes from detection to operational restoration.
Accurate MTTR tracking depends on consistent timestamping at each stage of the repair process. Many computerised maintenance management systems (CMMS) automate this by logging when a work order is opened, when parts are issued, and when the asset is returned to service. Without standardised data entry, MTTR values can be misleadingly low if the clock starts late or misleadingly high if it includes unrelated administrative delays.
MTTR Examples and Use Cases
How MTTR plays out depends heavily on the operating environment and the nature of the asset. The following examples illustrate the range of scenarios where MTTR is a critical metric.
Manufacturing Production Line
A conveyor drive motor fails at 08:15 on a food packaging line. The maintenance technician is dispatched, diagnoses a bearing failure by 08:35, retrieves a replacement bearing from the on-site spares store by 08:50, completes the repair by 10:20, and runs a 20-minute verification test. Total repair time: 2 hours 25 minutes. If similar failures occur twice more that quarter with repair times of 2.4h and 1.8h, the quarterly MTTR for that failure mode is (2.42 + 2.4 + 1.8) / 3 = 2.21 hours. The maintenance manager uses this figure to justify adding a second spare motor to reduce future repair time below 1.5 hours.
IT Infrastructure and Server Operations
A rack server in a co-located data centre experiences a hard drive failure. An on-site spare is available, the drive is hot-swapped in 10 minutes, RAID rebuilds in 35 minutes, and verification testing takes 5 minutes. MTTR for this single event is 50 minutes. Over a year, the infrastructure team tracks MTTR across all server repairs to identify whether specific hardware models or rack locations correlate with longer repair durations. This data drives procurement decisions and staffing for after-hours support coverage.
Offshore Wind Energy
A turbine gearbox fails 15 kilometres offshore. Remote diagnosis takes 2 hours. A crew and replacement parts must be mobilised via marine vessel, adding 18 hours of logistics time. The physical repair takes 6 hours and post-repair testing takes 1 hour. Total MTTR: 27 hours. In this scenario, parts procurement and logistics account for roughly 67 percent of the total repair time. The operator uses this MTTR breakdown to justify investing in condition-monitoring sensors that provide earlier failure warning, allowing parts and crew to be pre-positioned and reducing the logistics component of MTTR from 18 hours to approximately 4 hours.
Strategies to Reduce MTTR
Reducing MTTR is a priority for any organisation where downtime is costly. The most effective strategies address the specific phases of the repair process that contribute the most delay.
Stock critical spare parts locally
Maintaining an optimised spare parts inventory at the point of use eliminates the procurement delay that often dominates MTTR, particularly in remote or offshore environments. Bills of materials and min-max stock levels for high-criticality components ensure parts are available when needed.
Improve diagnostic speed with condition monitoring
Vibration analysis, thermal imaging, and oil analysis can pinpoint the failure mode before a technician arrives on site. This collapses the diagnosis phase and ensures the right parts and tools are brought to the job on the first visit, avoiding repeat trips.
Standardise repair procedures
Documented, step-by-step repair work instructions reduce variability between technicians and eliminate time spent deciding on the correct approach. Standardisation also makes it easier to train new team members to meet the same MTTR targets.
Use predictive maintenance to pre-position resources
When sensors indicate a component is approaching failure, maintenance teams can schedule the repair during a planned window, confirm parts availability, and assign a technician before the failure occurs. This converts what would be a high-MTTR reactive repair into a low-MTTR planned one.
Related Terms
MTBF (Mean Time Between Failures) measures the average operating time between failures; it is the reliability counterpart to MTTR in the failure-repair cycle.
MTTF (Mean Time To Failure) is similar to MTBF but applies to non-repairable assets that are replaced rather than repaired after failure.
OEE (Overall Equipment Effectiveness) is a composite metric that includes availability, which is directly impacted by MTTR, alongside performance and quality.
Downtime is the total period an asset is non-operational; MTTR represents the repair portion of that downtime.
Predictive Maintenance uses condition-based monitoring to forecast failures, enabling teams to pre-position parts and reduce MTTR before the failure even occurs.
Preventive Maintenance is scheduled, time- or usage-based maintenance aimed at reducing the frequency of unplanned failures, thereby lowering the number of high-MTTR reactive repairs.
Frequently Asked Questions
MTTR (Mean Time To Repair) is the average time it takes to fix a failed asset and return it to service. It includes diagnosis, parts sourcing, the repair itself, and post-repair testing, giving maintenance teams a clear measure of how efficiently they resolve failures.
MTTR equals total repair time divided by the number of repairs in a given period. For example, if three repairs took 4 hours, 6 hours, and 5 hours respectively, MTTR = (4 + 6 + 5) / 3 = 5 hours. Accurate timestamps at each repair stage are essential for reliable calculations.
MTTR measures how long repairs take on average, while MTBF (Mean Time Between Failures) measures how long equipment operates before failing. Together, they describe the full failure-repair cycle: MTBF tells you how often failures occur, and MTTR tells you how quickly you recover from them.
There is no universal good MTTR because benchmarks vary by industry and asset type. A CNC machine might target under 2 hours, while an offshore wind turbine may consider 24 hours acceptable. The most effective approach is to track your own baseline and aim for continuous reduction over time.
Common strategies include stocking critical spare parts locally, improving diagnostic speed with condition monitoring, standardising repair procedures, and using predictive maintenance to pre-position resources before failures occur. Targeting the longest phase of your repair process yields the fastest MTTR improvement.
Yes. MTTR covers the entire repair window from failure detection to operational restoration, including time spent waiting for spare parts, technician availability, or equipment access. This is precisely why parts procurement delays often represent the biggest opportunity for MTTR reduction.