Maintenance & Reliability worked example

MTTR with total repair hours of 48 hr: a worked example

This worked example runs the mttr numbers for a tougher week than the baseline: total repair hours of 48 hr instead of the typical 96 hr. Measure mean time to repair by dividing repair labor hours by the number of completed repairs.

The inputs for this scenario

  • Total repair hours: 48 hr (the input this scenario stresses; the baseline uses 96)
  • Number of repairs: 12 repairs (held at the documented default)
  • Normalization factor: 1 x (held at the documented default)

Working through the calculation

  • The calculation starts from the formula this tool documents: MTTR = total repair hours รท number of repairs.
  • MTTR works out to 4 hr / repair at these inputs, and this is the headline figure for the scenario.
  • Base Repair Time works out to 4 hr / repair at these inputs.
  • Normalization Factor works out to 1 x at these inputs.
  • Repair Count works out to 12 value at these inputs.

How this compares with the baseline

  • Against the tool's baseline example, where total repair hours sits at 96 hr and the headline result is 8 hr / repair, this scenario comes in 50% below the baseline at 4 hr / repair.
  • Use it in monthly maintenance reviews, RCA follow-ups, and CMMS reporting to gauge how quickly your team restores assets and to benchmark maintainability across lines or sites. A result at this level usually justifies acting on the stressed input before touching anything else, because every other figure in the table is downstream of it.

Results at a glance

  • MTTR: 4 hr / repair (headline result)
  • Base Repair Time: 4 hr / repair
  • Normalization Factor: 1 x
  • Repair Count: 12 value

Run it with your numbers

  • To rerun this with your own numbers, open the live MTTR calculator, set total repair hours to your actual value, and adjust the remaining inputs to match your operation.

Last reviewed 2026-05-12.