Key takeaways
Short answer: MTBF and MTTR are the two core maintenance metrics, and they measure opposite things. MTBF — Mean Time Between Failures — is how long an asset runs between failures, a measure of reliability: bigger is better. MTTR — Mean Time To Repair — is how long it takes to restore the asset once it fails, a measure of repairability: smaller is better. Together they determine availability. Confusing them, or improving one while ignoring the other, leaves uptime on the table. For the properties beneath them, see reliability vs maintainability.
MTBF — Mean Time Between Failures — is the average operating time a repairable asset runs between one failure and the next. You calculate it as total operating time divided by the number of failures over a period: a machine that ran 4,000 hours and failed five times has an MTBF of 800 hours. MTBF is the headline measure of reliability — how seldom the asset fails. A higher MTBF means longer, more consistent runs between breakdowns; a falling MTBF is an early warning that something is degrading. Crucially, MTBF says nothing about how bad each failure is to recover from — an asset can have a long MTBF and still cripple production if every rare failure takes days to fix. That recovery side is a separate metric.
MTTR — Mean Time To Repair — is the average time it takes to restore a failed asset to working order, calculated as total repair time divided by the number of failures. It is the headline measure of maintainability — how quickly you recover. MTTR captures everything from the moment the asset goes down to the moment it is running again: diagnosis, getting the part, the actual repair, testing, restart. A low MTTR means fast recovery; a high MTTR means each failure hurts for a long time. MTTR depends heavily on things you can design and organise — access to the failed part, spares availability, clear procedures, technician skill — and it says nothing about how often the asset fails. It is purely about the cost, in time, of each failure.
The reason both matter is that availability depends on the two together. The standard relationship is availability is roughly MTBF divided by (MTBF + MTTR): reliability in the numerator, reliability plus repairability in the denominator. This means you can reach a given availability by different routes — a very reliable asset that is slow to fix, or a less reliable one that is fixed fast. It also means improving just one metric has limited effect if the other is poor: a huge MTBF is undermined by a huge MTTR, and a tiny MTTR cannot fully rescue an asset that keeps failing. Reading the two together is what tells you whether an availability problem is a failure-frequency problem (MTBF) or a recovery-speed problem (MTTR).
An asset runs 950 hours, fails, and takes 50 hours to repair, in a repeating pattern. MTBF is 950 hours; MTTR is 50 hours; availability is 950 divided by (950 + 50) = 95%. Now suppose you cannot easily reduce failures, but you can attack the repair: better spares, clearer diagnostics, and access improvements cut MTTR from 50 hours to 10. Availability rises to 950 divided by (950 + 10), about 99%. Alternatively, leave MTTR at 50 but double MTBF to 1,900 through reliability work: availability becomes 1,900 divided by (1,900 + 50), about 97.4%. Same starting point, two different levers, two different gains — and the right one depends on which metric is actually dragging your availability down.
The two metrics call for completely different action. To raise MTBF (fewer failures): root-cause recurring breakdowns, tighten preventive and condition-based maintenance, fix lubrication and alignment, address operating stresses, and use FMEA to target the highest-risk failure modes. To lower MTTR (faster recovery): stock the right spares, improve access to failure-prone components, write clear diagnostics and repair procedures, train technicians, and pre-stage tools and kits. MTBF work attacks how often you are in the hole; MTTR work attacks how long you stay there. The discipline is to read the two before spending — chasing reliability when your problem is slow repairs, or the reverse, wastes effort on the lever that is not actually broken.
MTBF and MTTR sit directly beneath the availability factor of OEE. Low MTBF shows up as frequent downtime events; high MTTR shows up as long ones — and decomposing availability loss into how-often versus how-long is exactly how you decide which to fix, the same split behind availability vs reliability and reliability vs maintainability. There is also a performance knock-on: an asset with a low MTBF, even if quickly repaired, never settles into its rated speed, so poor reliability can dent the performance factor too. Tracking both metrics turns a sagging availability number into a specific, addressable cause.
Fabrico computes MTBF and MTTR from the downtime data it already captures — how often each asset fails and how long each repair takes — and shows them next to live OEE. Seeing the two side by side is what tells you whether an availability problem is a frequency problem (raise MTBF) or a recovery problem (cut MTTR), so you invest in the right lever. It then confirms in the trend whether your fix actually moved availability. Book a demo to see your reliability and repair metrics from real events.
MTBF (Mean Time Between Failures) is the average operating time between failures — a measure of reliability. MTTR (Mean Time To Repair) is the average time to restore the asset after a failure — a measure of repairability. MTBF is how often you fail; MTTR is how long you are down each time.
Availability is approximately MTBF divided by (MTBF + MTTR), so it depends on both. A high MTBF with a high MTTR still loses availability, and a low MTTR cannot fully rescue an asset that keeps failing. The two together determine uptime.
MTBF is total operating time divided by the number of failures. MTTR is total repair time divided by the number of failures. For example, 950 operating hours with one failure taking 50 hours gives MTBF 950 and MTTR 50, for 95% availability.
Neither universally — it depends on which is costing you availability. If the asset fails often, focus on MTBF (reliability). If each repair takes a long time, focus on MTTR (faster, better repairs). Read both before deciding where to invest.
Both drive the availability factor of OEE: low MTBF causes frequent stops, high MTTR causes long ones. Low MTBF can also dent the performance factor, since a frequently-failing asset never settles into its rated speed.
Вход
Блог
