Manufacturing & OperationsGlossary

What Is MTTR (Mean Time To Repair)?

Also known as: mean time to repair, mean time to restore

Definition

MTTR (Mean Time To Repair) is the average time required to restore a failed asset to full operating condition, calculated as total repair time divided by the number of repairs. It measures maintainability rather than reliability.

MTTR (Mean Time To Repair) Explained

What the clock includes is the single most contested definition in maintenance metrics. Strict MTTR covers only hands-on repair time, from technician arrival to function restored. Mean time to restore service covers the full outage: detection, notification, technician travel, diagnosis, parts acquisition, repair, and verification. The second is what production actually loses, and it is often three to five times the first. Plants that report the narrow definition while production experiences the wide one generate persistent distrust of maintenance data.

MTBF and MTTR combine into inherent availability as MTBF divided by the sum of MTBF and MTTR. An asset with 400 hours MTBF and 6 hours MTTR has availability of 400/406, or 98.5 percent. That formula makes the trade-off explicit: an asset that fails often but is restored in minutes can outperform one that fails rarely but takes two days to fix, which is why designing for maintainability often beats chasing reliability alone.

MTTR reduction levers are usually logistical rather than technical. In most plants, diagnosis and parts wait dominate the outage clock while actual wrench time is a minority of it. The high-yield countermeasures are stocking critical spares locally, standardizing components across assets to shrink the spare-parts matrix, documenting fault trees and known failure signatures, providing machine-side access to manuals and drawings, and pre-positioning special tooling and lifting gear.

The metric also distorts easily. A single catastrophic rebuild can dominate the mean, so median repair time and a distribution view are usually more informative for planning. Splitting MTTR by failure mode is more actionable still, since the response to a chronic ten-minute sensor fault is completely different from the response to a twelve-hour spindle replacement even though both feed the same average.

Why It Matters

  • MTTR combined with MTBF yields availability, which sets the realistic capacity a scheduler should plan against.
  • Most MTTR is diagnosis and parts wait, not repair, so the largest reductions come from logistics and documentation rather than technician skill.
  • On a constraint, every hour of MTTR is an hour of plant throughput, giving spare-part stocking decisions a direct revenue justification.
  • Long MTTR forces larger inventory buffers throughout the plant, so improving it releases working capital as well as capacity.

In Practice

A maintenance department reports MTTR of 1.4 hours while production insists outages average most of a shift. Both are right. The 1.4 hours is wrench time. The full restore clock is 6.8 hours: 40 minutes before anyone reported the stop, 25 minutes for the technician to arrive, 3.2 hours waiting on a drive module shipped overnight, then 1.4 hours of repair and 45 minutes of requalification. Stocking the module on site cut the real outage by nearly half without changing a single repair procedure.

Frequently Asked Questions

Should MTTR include waiting for parts?

It depends which metric you are reporting, and you must state which. Mean time to repair conventionally counts only active repair time. Mean time to restore service counts the entire outage including detection, travel, diagnosis, and parts wait. Production capacity planning needs the restore-service number, because that is the duration the asset was actually unavailable.

How do MTTR and MTBF combine into availability?

Inherent availability equals MTBF divided by MTBF plus MTTR. With an MTBF of 300 hours and MTTR of 5 hours, availability is 300/305, about 98.4 percent. The formula shows that halving repair time improves availability as much as nearly doubling time between failures, which is often far cheaper to achieve.

Working with MTTR (Mean Time To Repair) in a live environment? Our engineers do this every day - and our AI agents automate most of it.