Mean Time to Repair
Key Takeaways
- MTTR covers only hands-on repair time: from when work begins to when the repair is mechanically complete. It excludes detection, parts waiting, travel, and testing time.
- Formula: MTTR = Total repair time / Number of repairs. Example: 25 hours across 5 repairs = 5-hour MTTR.
- MTTR is frequently confused with Mean Time to Recovery, which covers the full incident lifecycle. Using the terms interchangeably produces incompatible data when benchmarking.
- Spare parts availability is consistently the largest single contributor to repair delays, making on-site stocking of critical components the highest-leverage MTTR improvement.
- CMMS platforms that surface asset history, work instructions, and parts availability at the work site directly reduce diagnosis time and repair errors.
- MTTR and MTBF together determine asset availability: Availability = MTBF / (MTBF + MTTR).
What Is Mean Time to Repair?
Mean Time to Repair is the maintenance metric that measures how long the physical repair of a failed asset takes, on average. The clock starts when a technician begins active work on the failure and stops when the repair is mechanically complete and the asset is ready for post-repair testing and handback. It is a measure of repair efficiency rather than total downtime impact.
The distinction between repair time and recovery time is important for accurate benchmarking and improvement targeting. A maintenance team might achieve a 3-hour repair time on average while the total average downtime per failure event is 8 hours, because 5 of those hours are spent on detection, waiting for parts, and post-repair testing. Tracking only one figure while calling it by the other name obscures where the real time is being lost and leads to improvement efforts aimed at the wrong phase.
MTTR is one of the two levers available for improving asset availability. The other is MTBF: making assets fail less often. Reducing MTTR improves availability by shortening the period of downtime when failures do occur, even without changing how frequently they happen.
MTTR Formula and Calculation
The formula is:
MTTR = Total repair time / Number of repairs
Worked example: A maintenance team completed 5 repairs on a production line during the month. The actual hands-on repair times for each event were 4 hours, 6 hours, 3 hours, 7 hours, and 5 hours. Total repair time: 25 hours.
MTTR = 25 / 5 = 5 hours
For MTTR to be a meaningful metric, the start and stop timestamps must be defined consistently. The most common approaches are:
- Start: When the technician physically begins work on the asset (wrench-on time), not when they receive the work order or arrive at the location
- Stop: When the repair is mechanically complete, before testing and sign-off
Teams that define MTTR inconsistently across shifts or teams produce data that cannot be trended meaningfully. Standardizing the definition in the CMMS work order template is the simplest way to enforce consistency.
MTTR and Its Relationship to Other Maintenance Metrics
| Metric | What It Measures | Included in MTTR? |
|---|---|---|
| MTTD | Time from fault onset to detection | No |
| MTTA | Time from alert to acknowledgment | No |
| MTTR (Repair) | Hands-on repair duration | Yes (this is MTTR) |
| Mean Time to Recovery | Full incident lifecycle | Yes (MTTR is one phase within recovery) |
| MTBF | Average uptime between failures | No (complementary metric) |
What Drives High MTTR
Parts Availability
Waiting for spare parts is consistently the largest single contributor to repair delays in maintenance operations. When a critical component must be ordered after failure, the entire repair is gated on procurement and delivery. MTTR data that shows long average repair times for specific asset categories often reveals a parts stocking problem rather than a technician skill problem. Stocking critical spares on-site, informed by failure frequency and MTTF data, is the highest-leverage MTTR improvement in most facilities.
Diagnosis Difficulty
Complex or ambiguous failure modes extend the time a technician spends identifying the root cause before beginning the repair. Technicians who have not encountered a specific failure type before take longer to diagnose it than those who have. Access to the asset's maintenance history, previous failure modes, and documented repair procedures reduces diagnosis time significantly, especially for less experienced team members.
Physical Access and Isolation Requirements
Some assets are located in confined spaces, at height, or require complex lockout/tagout and permit-to-work procedures before work can begin. These requirements are often fixed by installation design, but poorly organized isolation procedures, unclear permit processes, or insufficient safety equipment can add unnecessary time to the pre-repair phase that is captured in MTTR.
Failure Severity
Not all repairs are equal in scope. A bearing replacement on a small motor takes a fraction of the time required to diagnose and repair an internal gearbox failure. MTTR averages that do not segment by failure type or severity can hide significant variation: a few major repairs with very long durations can inflate the average while masking excellent performance on routine repairs.
How to Reduce Mean Time to Repair
Optimize Spare Parts Stocking
Review MTTR data by failure type to identify which repairs are most commonly delayed by parts availability. For the highest-frequency and highest-consequence failures, establish minimum on-site stocking levels informed by failure rates. Link spare parts reorder points to CMMS-tracked consumption data so stock is replenished automatically rather than requiring manual review after each use. Good inventory management directly reduces repair waiting time.
Build Structured Work Instructions
For the most common failure types, create step-by-step repair procedures in the CMMS and attach them to work order templates. Structured instructions reduce diagnosis time, reduce the probability of repair errors that require rework, and make the knowledge of experienced technicians available to less experienced team members. Work instructions that include torque specifications, part numbers, and safety requirements are particularly effective.
Cross-Train Technicians on High-Frequency Failures
When repair capability is concentrated in one or two individuals, MTTR is vulnerable to shift coverage gaps. Cross-training ensures that the knowledge required for common repairs is distributed across the team, reducing wait time for the right technician to become available and improving overnight and weekend response capability.
Use Mobile CMMS at the Point of Repair
A CMMS accessible from a mobile device at the asset location gives technicians immediate access to maintenance history, previous failure modes, work instructions, and parts availability without leaving the work site. This eliminates round trips to an office computer or maintenance room during the repair process, reducing both diagnosis time and repair delays.
Conduct Post-Repair Reviews on Long-Duration Events
Repairs that significantly exceed the average MTTR for their type contain information about what went wrong in the repair process. Structured post-repair reviews for these events identify recurring bottlenecks: parts that were not stocked, isolation procedures that were unclear, documentation that was missing, or failure modes that were unfamiliar to the responding technician. Addressing these root causes prevents the same delays from recurring.
MTTR and Asset Availability
The relationship between MTTR and availability is direct and quantifiable:
Availability = MTBF / (MTBF + MTTR)
For an asset with MTBF of 500 hours and MTTR of 5 hours, availability is 500 / (500 + 5) = 99.0%.
Reducing MTTR from 5 hours to 2 hours raises availability to 500 / (500 + 2) = 99.6%. That 0.6 percentage point improvement represents approximately 52 fewer hours of downtime per year on a continuously operating asset, with no change to the asset's underlying reliability or failure frequency.
The Bottom Line
MTTR is one of the two levers available for improving asset availability. Reducing how long repairs take delivers measurable availability gains without requiring any change to how often assets fail. For most maintenance operations, that makes it a high-return target because the improvements are operational rather than capital-intensive.
The highest-leverage MTTR reduction consistently comes from parts availability. When critical spares are stocked on-site based on failure frequency data, the largest single contributor to repair delays is eliminated before a failure even occurs. Structured work instructions in the CMMS and cross-trained technicians address the next tier of delays. Together, these three measures convert long, unpredictable repair events into shorter, more consistent ones.
Track MTTR by failure type and asset category rather than as a single facility-wide average. That segmentation reveals whether long repair times reflect a parts stocking problem, a skill gap, or a physical access constraint. Each root cause requires a different response, and the data will tell you which problem to solve first.
Reduce Repair Time with Better Asset Visibility
Tractian's CMMS gives technicians instant access to asset history, work instructions, and parts availability at the point of repair, cutting diagnosis time and eliminating avoidable delays.
See How It WorksFrequently Asked Questions
What is Mean Time to Repair?
Mean Time to Repair (MTTR) is the average time required to perform the physical repair work on a failed asset. It is measured from when a technician begins the hands-on fix to when the repair is mechanically complete, isolating repair labor time from waiting time, detection time, and post-repair testing.
How is Mean Time to Repair calculated?
MTTR equals total repair time divided by the number of repairs in the measurement period. For example, 25 hours of total hands-on repair time across 5 repair events gives an MTTR of 5 hours. Accurate calculation requires consistent timestamps for when physical repair work begins and ends, applied uniformly across all technicians and shifts.
What is the difference between Mean Time to Repair and Mean Time to Recovery?
Mean Time to Repair covers only hands-on repair work: from when the technician begins the fix to when it is mechanically complete. Mean Time to Recovery covers the full incident lifecycle: detection, diagnosis, repair, testing, and return to service. Recovery time is always equal to or longer than repair time. Using the terms interchangeably produces incompatible data when comparing performance across teams or against benchmarks.
What is the biggest driver of high MTTR?
Parts availability is consistently the largest single driver of repair delays. When a required component is not stocked on-site, the entire repair waits on procurement and delivery. Reviewing MTTR data by failure type to identify which repairs are most commonly delayed by parts availability, then establishing on-site stocking levels for those components, typically delivers the fastest MTTR improvement.
How does MTTR affect asset availability?
Availability = MTBF / (MTBF + MTTR). Reducing MTTR directly increases availability without requiring any change to how frequently the asset fails. For an asset with a 500-hour MTBF, reducing MTTR from 5 to 2 hours increases availability from 99.0% to 99.6%, representing approximately 52 additional operating hours per year on a continuously running asset.
How does a CMMS help reduce MTTR?
A CMMS reduces MTTR primarily by giving technicians immediate access to asset history, previous failure modes, work instructions, and parts availability at the point of repair. This eliminates time spent searching for documentation, reduces diagnosis time through historical fault pattern recognition, and prevents trips back to an office or storeroom during the repair. Work order templates with structured repair procedures further reduce variability and rework.
Related terms
Maintenance Cycle: Definition
A maintenance cycle is the complete sequence of activities performed on an asset from one maintenance event to the next, sustaining asset reliability.
Maintenance Dashboard: Definition
A maintenance dashboard is a real-time visual display of key maintenance KPIs, work order status, and asset health data used to manage and improve maintenance operations.
Maintenance Documentation: Definition
Maintenance documentation is the complete set of records, procedures, and reports that capture maintenance activities, asset history, and compliance data in an industrial facility.
Maintenance Demand: Definition
Maintenance demand is the total volume of maintenance work required by assets at a given time, encompassing planned, unplanned, and condition-triggered work orders.
Maintenance Downtime: Definition
Maintenance downtime is the period when equipment is taken offline for maintenance activities, impacting OEE availability and production output.