
Key takeaways
Short answer: MTTF measures average time to failure for a non-repairable asset (a bearing, a fuse). MTBF measures average time between failures for a repairable asset (a pump, a CNC machine). MTTR measures average time to repair. They are easy to confuse but answer different questions and apply to different asset types. Using the wrong one produces wrong reliability conclusions. See also MTTR vs MTBF.
Mean Time To Failure applies to assets that are NOT repaired — they fail and get replaced.
MTTF = Total operating time / Number of failures (and replacements)
Classic examples: light bulbs, fuses, bearings, single-use components. You do not repair a fuse; you replace it. MTTF answers "how long does this kind of component last on average?"
Mean Time Between Failures applies to repairable assets — equipment that fails, gets fixed, and continues operating.
MTBF = Total operating time / Number of failures
Examples: motors, pumps, conveyors, machines. MTBF answers "how often does this equipment fail between repairs?"
Mean Time To Repair is the time from failure detected to back-in-service.
MTTR = Total repair time / Number of failures
It is a maintainability metric — how well your maintenance system responds when failures occur.
Using MTTF for equipment that is actually repaired. If a motor is rebuilt every 10,000 hours of operation, that motor is repairable. MTBF (with the repair time excluded from operating time) is the right metric. Calling it MTTF treats the rebuild as a replacement and produces misleading reliability numbers.
The cleaner test: do you keep records of repairs by serial number? If yes, it is MTBF. If you just count replacement events with no repair, it is MTTF.
Most CMMS dashboards report MTBF and MTTR per asset. MTTF appears in deeper component analysis or in vendor datasheets.
The classical Availability formula uses MTBF and MTTR:
Availability = MTBF / (MTBF + MTTR)
MTTF does not appear in this equation because it applies to non-repairable assets — and a non-repairable asset that fails is replaced, not waiting on MTTR.
1. Using MTTF on equipment. Overestimates the failure rate because rebuild events are treated as replacements.
2. Using MTBF on components. Confusing — the component does not get rebuilt, so MTBF and MTTF would mean the same thing, but the formula nuance matters in reliability engineering.
3. Including planned maintenance time in MTTR. MTTR is about reactive repair, not PMs. Mixing them inflates MTTR.
4. Using vendor MTBF as your MTBF. Vendor numbers are based on rated conditions. Your duty cycle, environment, and maintenance program produce a different number.
A modern CMMS calculates MTBF per asset and MTTR per asset from work order history. For component-level tracking (where MTTF applies) it depends on whether the CMMS tracks replacements at the BOM-line level. Most do; many do so loosely.
Fabrico's CMMS calculates MTBF and MTTR per asset with trend lines, supports component-level replacement tracking for MTTF analysis where the inventory data supports it, and ties downtime events from OEE directly to MTTR — keeping the reliability math clean.
See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.
Industrially, bearings are usually treated as non-repairable (replaced). Some specialty applications rebuild bearings; those would treat them as repairable.
MTBF and MTTR. They together determine Availability, which is a factor in OEE.
For replaceable components within fleet assets, yes. For the assets themselves (vehicles, machines), MTBF is the right metric.
Less common variant — Mean Time To Between Failures. Effectively the same as MTBF in most usage.
Root cause work, PM recalibration, condition-based monitoring, design changes. See the MTTR vs MTBF article for the detailed contrast on improvement paths.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!