What MTTR and MTBF actually measure
Mean time to repair (MTTR) describes the average time required to restore an asset after a failure. Mean time between failures (MTBF) describes the average operating time between functional failures for a repairable asset. Together they help separate two different problems: how often failures occur and how long recovery takes.
MTBF is only useful with consistent failure definitions
If one shift records every brief interruption and another records only maintenance-confirmed failures, MTBF comparisons will be misleading. Define which events count, use consistent asset boundaries, and distinguish equipment failure from process, material, operator, and planned downtime.
Break MTTR into waiting and wrench time
MTTR is not just hands-on repair time. A useful breakdown includes diagnosis, waiting for access, waiting for parts, waiting for information or approval, hands-on work, testing, and return-to-rate time. This reveals whether the best improvement is a job plan, spare-parts change, training, troubleshooting standard, or equipment redesign.
Use the measures together
- Low MTBF and high MTTR usually indicate a high-priority reliability problem.
- Low MTBF and low MTTR may indicate frequent nuisance failures or an opportunity for redesign.
- High MTBF and high MTTR may indicate low-frequency but high-consequence exposure that deserves preparedness work.
- Improving the metric by changing coding behavior is not a reliability improvement.
Build a small review rhythm
Review the top assets and failure modes weekly or monthly. Ask what changed, what the team learned, and what action has an owner and due date. Connect the metrics to production impact and the backlog so the review leads to decisions rather than a dashboard report.
For the broader context, read 5 Strategies to Reduce Unplanned Downtime in Manufacturing and request the GTEK downtime reduction white paper.