Mean Time to Repair (MTTR)

Table of Contents

Mean Time to Repair (MTTR) is a maintenance metric that measures the average time required to restore a failed asset to operational condition, from the moment the failure is detected to the moment the asset returns to service. MTTR captures the full repair cycle — detection, diagnosis, parts procurement, repair execution, and return to service — making it a comprehensive indicator of maintenance response effectiveness rather than just a measure of hands-on repair time.

MTTR is primarily a measure of unplanned corrective maintenance. A low MTTR indicates that the maintenance organization detects failures quickly, diagnoses root cause efficiently, has the right parts available, and executes repairs effectively. A high MTTR indicates friction somewhere in that chain — delayed detection, slow diagnosis, parts unavailability, or insufficient technician skill or capacity for the failure type.

MTTR is most meaningful when tracked alongside Mean Time Between Failures (MTBF). MTBF measures how often assets fail; MTTR measures how long it takes to recover when they do. Together they define the availability profile of an asset — and the total cost of its failure pattern.

Why MTTR Matters

Every hour an asset is down for unplanned repair has a cost: lost production, idle labor, potential safety exposure, and customer impact. MTTR quantifies the duration of that cost exposure per failure event. For a production-critical asset with high downtime cost, reducing MTTR from 10 hours to 5 hours on 20 annual failures eliminates 100 hours of unplanned downtime per year — a number with direct financial translation.

MTTR also reveals where maintenance program investment delivers the highest return. If MTTR is high because technicians spend two hours locating parts before starting a repair, the investment case is for better spare parts management and stocking strategy. If MTTR is high because diagnosis takes three hours on a complex failure, the investment case is for better documentation, troubleshooting guides, and technician training. MTTR disaggregated by failure phase — detection time, diagnosis time, repair time, return-to-service time — points directly to the constraint.

For asset replacement decisions, sustained high MTTR on aging equipment is a concrete financial argument. When repairs take longer because components are harder to source, technicians are less familiar with aging designs, and failures are more complex, MTTR data quantifies the operational cost of continued operation versus replacement.

How MTTR Is Calculated

The MTTR Formula

MTTR is calculated as:

MTTR = Total Unplanned Maintenance Hours / Total Number of Repair Events

For a defined period, sum the total hours consumed by unplanned corrective maintenance events and divide by the number of those events. The result is the average repair duration per failure.

Example: A pump experiences 8 unplanned failures over 12 months. Total maintenance hours across those 8 events sum to 48 hours. MTTR = 48 / 8 = 6 hours per failure.

MTTR can be calculated at multiple levels: facility-wide, by asset class, by individual asset, or by component type. Component-level MTTR — the average time to replace a specific bearing type, for instance — is more actionable for improvement planning than facility-wide averages that obscure which assets and failure types are driving the number.

MTTR vs. MTTF vs. MTBF

These three metrics are frequently referenced together and are often confused:

  • MTTR (Mean Time to Repair): Average time to restore a failed asset to service. Measures recovery speed.
  • MTBF (Mean Time Between Failures): Average operating time between failure events for repairable assets. Measures reliability. See: Mean Time Between Failures (MTBF).
  • MTTF (Mean Time to Failure): Average operating time before failure for non-repairable assets or components. Used for replacement planning rather than repair planning. See: Mean Time to Failure (MTTF).

Asset availability is directly calculated from MTBF and MTTR: Availability = MTBF / (MTBF + MTTR). An asset with an MTBF of 500 hours and an MTTR of 10 hours has an availability of 98 percent. Reducing MTTR improves availability even when MTBF remains constant.

MTTR Benchmarks

A commonly cited MTTR benchmark for industrial equipment is 5 hours or less. This benchmark is a starting reference point, not a universal standard — the appropriate MTTR target varies significantly by asset type, failure complexity, and operational context. A 5-hour MTTR on a simple pump replacement is poor performance. A 5-hour MTTR on a complex gearbox failure requiring precision alignment is strong performance.

The more useful benchmark is internal trend: is MTTR on a specific asset class improving over time? And is MTTR on Tier 1 critical assets lower than on Tier 2 and Tier 3 assets — reflecting the prioritization that criticality should produce?

MTTR by Industry

Manufacturing: MTTR on production-critical assets in manufacturing translates directly to throughput loss. A bottleneck machine with a 12-hour average MTTR and 15 annual failures loses 180 hours of production capacity per year to repair time alone. Manufacturing maintenance programs track MTTR by asset and by failure type to identify where spare parts stocking, technician training, or better troubleshooting documentation would reduce repair duration most significantly.

Mining: MTTR in mining is complicated by logistics — a haul truck breakdown in a remote pit location adds travel time, parts transport time, and sometimes shift-change delays to the repair duration before hands-on work begins. Mining maintenance programs track total MTTR inclusive of logistics time to capture the full downtime cost, then analyze which portion is reducible through field parts stocking, mobile maintenance deployment, or improved failure detection that allows planned repairs at the workshop rather than reactive field repairs.

Oil and Gas: MTTR in oil and gas is heavily influenced by permit-to-work and isolation requirements. A repair that takes 2 hours of hands-on time may consume 8 total hours when isolation, permit issuance, work execution, deisolation, and return-to-service testing are included. Tracking MTTR inclusive of all these phases reveals whether improvement opportunities lie in the maintenance execution itself or in the surrounding safety management processes.

Crane and Rigging: Crane MTTR carries both operational and contractual consequences in construction and marine loading operations where crane availability is committed to project schedules. A crane out of service longer than expected disrupts lift schedules, delays dependent trades, and in some contracts triggers liquidated damages. MTTR tracking on crane components — hoist systems, slewing drives, hydraulic systems — identifies which failure types carry the greatest schedule risk and where spare parts stocking or service agreement coverage reduces exposure.

Common MTTR Measurement and Improvement Failures

Measuring repair time only, not total downtime: MTTR that captures only hands-on repair time excludes detection delay, parts wait time, and return-to-service testing — often the largest contributors to total downtime duration. Tracking total time from failure detection to asset return to service produces a more accurate picture of actual downtime cost and reveals where the real improvement opportunities lie.

No parts availability analysis: Studies consistently show that maintenance technicians spend 20 to 25 percent of their time searching for parts and materials. When MTTR is high, parts unavailability is frequently the primary cause — not slow repair execution. MTTR analysis should include parts wait time as a tracked component so that stocking strategy improvements can be justified with downtime cost data.

Tracking facility MTTR only: A single facility-wide MTTR average obscures which assets, failure types, and technician teams are driving the number. MTTR tracked at the asset class and individual asset level identifies specific improvement targets. MTTR tracked by failure type identifies which repairs consistently take longest and where documentation or training investment would reduce diagnosis and execution time.

No connection to asset criticality: A Tier 3 non-critical asset with a 20-hour MTTR warrants less improvement investment than a Tier 1 critical asset with a 6-hour MTTR. When MTTR improvement initiatives are prioritized by asset criticality, the operational impact of the improvement is maximized. MTTR data without criticality context produces improvement efforts that may not address the failures with the highest downtime cost.

MTTR tracked but not acted on: Tracking MTTR without investigating the causes of high values produces a metric without improvement. When MTTR on a specific asset consistently exceeds target, a structured analysis of the repair cycle — detection time, diagnosis time, parts time, repair time — identifies the specific constraint and the intervention that would address it.

MTTR vs. Related Metrics

  • MTTR (Mean Time to Repair): Average time to restore a failed asset to service. Measures recovery speed and maintenance response effectiveness.
  • MTBF (Mean Time Between Failures): Average operating time between failure events. Measures asset reliability. Improving MTBF reduces failure frequency; improving MTTR reduces failure duration. See: MTBF.
  • Asset Availability: The percentage of time an asset is available for operation. Calculated from MTBF and MTTR. Both metrics drive availability — MTTR improvement has the most impact when MTBF is already high. See: Asset Availability.
  • Mean Downtime (MDT): Total downtime per failure event including all delays. MDT is broader than MTTR — it includes administrative delays, waiting time, and logistical delays that are not strictly repair time. See: Mean Downtime (MDT).
  • Wrench Time: The percentage of a technician’s available time spent performing actual maintenance work. Low wrench time extends MTTR by increasing non-productive time within the repair cycle. See: Wrench Time.

Frequently Asked Questions

What does MTTR measure?

MTTR measures the average time required to restore a failed asset to operational condition across multiple failure events. It captures the full repair cycle from failure detection through return to service, including diagnosis time, parts procurement time, hands-on repair time, and return-to-service testing. MTTR is a measure of maintenance response effectiveness — how quickly and efficiently the maintenance organization recovers from unplanned failures. A low MTTR indicates effective detection, diagnosis, parts availability, and repair execution. A high MTTR indicates a constraint somewhere in that chain.

What is a good MTTR?

A commonly cited benchmark is 5 hours or less for industrial equipment, but the appropriate target varies significantly by asset type and failure complexity. The more useful target is improvement over time on specific assets and failure types, combined with a lower MTTR on Tier 1 critical assets than on lower-criticality equipment. A 5-hour MTTR on a critical compressor may represent strong performance. An 8-hour MTTR on a simple pump replacement may represent poor parts availability or inefficient diagnosis — regardless of how it compares to a generic benchmark.

How do you reduce MTTR?

Reducing MTTR requires identifying which phase of the repair cycle is the primary constraint. If detection is slow, invest in condition monitoring and operator reporting systems that identify failures earlier. If diagnosis takes too long, invest in troubleshooting documentation, failure mode libraries, and technician training for the most common complex failures. If parts wait time is the constraint, improve spare parts stocking strategy based on failure frequency and downtime cost for critical components. If repair execution is slow, review work planning quality, tool availability, and whether the right skill sets are assigned to the right failure types.

How does a CMMS support MTTR tracking?

A CMMS tracks MTTR by recording failure detection time, work order creation time, work order completion time, and asset return-to-service time on every corrective work order. This data enables MTTR calculation at any level — facility, asset class, individual asset, or component — without manual data aggregation. The CMMS also enables MTTR analysis by failure type, by technician team, and against asset criticality tiers, turning a single average into a diagnostic tool that identifies specific improvement targets.

Track and Reduce MTTR With Redlist

Redlist records failure detection time, repair duration, and return-to-service time on every corrective work order — giving maintenance teams the data to identify what is driving repair time and where to invest for the greatest downtime reduction.

Explore the Redlist CMMS  |  Request a Demo

4.7 Star Rating
Rated 5 out of 5

Redlist Lubrication Management  Software Live Demo

The Redlist Lubrication Management Software demonstration environment is not a personal free trial. You do not have to enter your payment information to access the free trial, and you are not required to subscribe at the end of the trial to continue usage.

It is a prepopulated live environment which means:

  1. The data is wiped and reset every night.
  2. Any changes you make in the environment will not be saved to the following day.
  3. Do not add any personal or proprietary information to the demo, as other users may see the data you input.
  4. Do not add any personal or proprietary information to the demo, as other users may see the data you input.

This demo is intended for desktop computer use. It is not optimized for Mobile or Tablet. The use of the DIY demo to build your own competing software is expressly prohibited.