Blog / Reliability
Reliability · Guide

MTTR Reduction Plan: A 12-Week Template to Use

OL By OEE Lab Editorial |Updated 2 November 2026 |5 min read
Short answer

An MTTR reduction plan has four parts: measure where restore time goes, rank failures by hours lost, apply one fix per failure mode, then check the gain in availability and OEE. Waiting, diagnosis and parts are the first places to look, and your data decides. The 12-week plan below is a template to adapt.

The plan on one page

1
Weeks 1-2: measure
Time every repair by phase: notice, call, wait, diagnose, parts, repair, test, restart.
2
Weeks 3-4: rank
List failure modes by hours lost, which is count x mean restore time.
3
Weeks 5-8: fix
Apply one fix for each of the top three failure modes, with one named owner each.
4
Weeks 9-10: escalate
Agree who gets called, and after how many minutes.
5
Weeks 11-12: check and hold
Compare with the baseline, then write the fix into standard work.
One line or one machine group at a time. Add the next line only after the check in week 12.

Use one definition from day one.

Run the clock from the failure until the machine works again, in line with the IEC term mean time to restoration. Some plants stop it at the first good product instead, so write your choice down.

Hands-on time alone would hide most of what this plan goes after. The calculation itself is on how to calculate MTTR.

Weeks 1-2: measure the phases

Put a one-line sheet at the machine, or read stop times from a signal. Ask the technician to note the arrival time, the time the fault was found, and the time the part arrived.

Do not chase accuracy to the second. You need to know whether diagnosis takes 5 minutes or 50.

The result is the baseline. If you have no target yet, what is a good MTTR shows how to derive one from these same phases.

Weeks 3-4: rank failures by hours, not by count

Example: a palletizing cell over one quarter with 1,000 planned hours. It logged 33 failures, three modes in all.

Failure modeFailuresMean restoreHours lostWhere the time goes
Drive trips1840 min12.0Waiting for someone to reset
Gripper sensor1265 min13.0Diagnosis, then finding a sensor
Gearbox3480 min24.0Part not in stock
Total3389 min49.0
Hypothetical cell. MTTR = 49 h / 33 = 1.48 h, or 89 minutes.

By count, the drive trips look like the priority. By hours, the rare gearbox takes half the total, and each mode needs a different fix.

A downtime Pareto chart by hours makes this ranking visible. Keep the count beside it, since each failure also interrupts flow.

Weeks 5-8: match each fix to the phase that hurts

PhaseTypical fixTest that it worked
NoticeStop signal, stack light, andonMinutes from stop to first call
Call and waitOn-call rule, and rights for operators to do safe resetsMinutes from call to arrival
DiagnoseFault cards at the machine, repair history, fault code listsMinutes from arrival to fault found
PartsCommon spares near the line, exchange units for slow repairsMinutes from fault found to part in hand
RepairTool kit per failure mode, written stepsHands-on minutes
RestartShort checklist, first-off checkScrap in the first minutes after restart
Pick the row your data points to. Do not start all six at once.

In the example, each failure mode gets one fix:

  • Gearbox: a spare or exchange unit on the shelf cuts 480 minutes to 240. See spare parts management.
  • Gripper sensor: a fault card and a spare sensor at the cell cut 65 minutes to 35.
  • Drive trips: a code list and a trained, safe operator reset cut 40 minutes to 25. Manufacturers' codes are in the troubleshooting directory.
Gearbox, before24 h
Gearbox, after12 h
Gripper sensor, before13 h
Gripper sensor, after7 h
Drive trips, before12 h
Drive trips, after7.5 h
Same 33 failures in the quarter. The bars show hours lost before and after, scaled to the largest bar.

The total falls from 49 to 26.5 hours with the same number of failures. MTTR falls from 89 to 48 minutes, since 26.5 / 33 = 0.80 hours.

Spares carry a cost, so test each stocking choice before buying. The spare parts inventory calculator weighs the carrying cost against a stockout.

Weeks 9-10: set the clock for escalation

Long stops are often long because nobody decided when to call for help. Write down who is called after how many minutes, by name or role, for each shift.

A clock also protects the operator, who no longer has to judge when to ask. See the ladder in how to reduce unplanned downtime, and the routine in first response to a line stop.

Weeks 11-12: check the gain in OEE

Example: 49 hours lost in 1,000 planned hours is availability of 95.1% from failures. At 26.5 hours lost, availability is 97.4%.

At 86% performance and 97% quality, OEE moves from 79.3% to 81.2%, or 1.9 points. That is the number to show the plant, and the downtime cost calculator turns those hours into money.

Then write each fix into standard work, or the gain will fade. Fault cards go out of date, and spares drift out of stock unless someone owns them.

Guard metrics: how a plan like this goes wrong

  • MTBF falls. Quick resets can leave the cause in place. Track MTBF and repeat failures within a day of the repair.
  • Restart scrap rises. A rushed restart moves the loss from availability to quality.
  • The numbers improve on paper. Reclassifying long repairs as planned work lowers MTTR and saves nothing, so check against total hours lost.
  • Safety steps get skipped. Lockout and safe reset rules stay as they are, and they are never where you look for minutes.

Short stops under your threshold do not belong in this plan. They are a different problem, covered in how to reduce micro-stops.

See it live in Fabrico

This plan starts by knowing what happened during each stop. Where cameras are fitted, Fabrico can stream video of a stop on request next to its machine data, and operators tag the cause at the line. See how Fabrico uses cameras for OEE.

What people ask next

What is the fastest way to reduce MTTR?

Find the phase with the most waiting and fix that first. It is often response, diagnosis or parts, though your own timing decides. Start with first response to a line stop.

How do you measure MTTR reduction?

Compare the same failure modes before and after, using the same clock. Also track total hours lost, because MTTR alone can improve when only the failure mix changes. The MTBF and MTTR calculator helps with the sums.

How long does an MTTR reduction plan take?

This template runs for 12 weeks on one line, which is enough for a few fixes and a first check. Rare failures need longer before you can judge them, since a mode that happens three times a quarter gives little data.

Should I focus on MTTR or MTBF first?

Measure both and compare the hours each could win. Response fixes often come sooner, because they work on every failure, but prevention removes the loss for good. See how to improve MTBF.

Who should own the MTTR plan?

One person per failure mode, with production and technicians both at the table. Response time depends on both groups. Review it in the daily production meeting.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

← More OEE Lab guides · First response to a line stop →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES