Run-to-Failure Maintenance: When It Makes Sense

Run-to-failure (RTF) maintenance is a strategy in which an asset is deliberately operated until it breaks down, with no scheduled intervention beforehand, because the cost and effort of preventing the failure exceed the cost of simply fixing it when it happens. When RTF is chosen on purpose for the right equipment, it is a rational, money-saving decision. When it happens by accident because no one planned maintenance at all, it is just uncontrolled breakdown that quietly drains capacity and budget. The difference between those two situations is the whole story.

Planned run-to-failure vs unplanned breakdown

These two things look identical on the shop floor: a machine stops, someone repairs it, production resumes. But they are opposites in intent.

• Planned RTF is a documented decision. You have analyzed the asset, confirmed that failure is cheap, safe, and non-disruptive, and stocked the spare part in advance. When it fails, you replace it in minutes.
• Unplanned reactive maintenance is the absence of a decision. Nobody assessed the asset, no spare is on the shelf, and the failure cascades into scrap, missed orders, and overtime. This is a leading cause of unplanned downtime in factories.

The practical test: if you can describe why you are letting an asset run to failure and you have the spare ready, it is planned RTF. If you cannot, it is a gap in your maintenance program, not a strategy.

When run-to-failure is the rational choice

RTF makes economic sense for a specific class of assets. Good candidates usually share several of these traits:

• Low criticality: failure does not stop the line or endanger anyone.
• Redundancy: a backup unit or parallel path keeps production running when one fails.
• Cheap and fast to replace: think light bulbs, small pumps, sensors, hand tools, standard belts, and inexpensive motors.
• Unpredictable, random failure: parts with a flat failure curve where preventive replacement would not actually reduce breakdowns.
• Low repair cost relative to prevention: the labor and downtime of preventing failure cost more than the failure itself.

For this equipment, spending money on inspections, condition-based maintenance, or preventive schedules is waste. You would be paying to prevent a failure that costs almost nothing. A proactive maintenance strategy is the right default for critical machines, but forcing it onto trivial assets burns technician hours you cannot get back.

When run-to-failure is dangerous

RTF becomes reckless the moment failure carries consequences beyond a quick swap. Do not run these to failure:

• Assets whose failure creates a safety or environmental hazard (pressure vessels, brakes, guarding, anything that can hurt a person).
• Bottleneck or single-point-of-failure machines where one breakdown halts the entire line.
• Equipment with long lead-time spare parts, where a failure means days or weeks of waiting.
• Assets where failure causes collateral damage, such as a cheap bearing that seizes and destroys an expensive shaft.
• Machines central to product quality, where degradation quietly raises your scrap rate before the outright failure.

This is why criticality analysis comes first. You rank each asset by the consequence and likelihood of failure, then assign RTF only to the low-consequence tail. Tools like FMEA and Pareto analysis help you separate the vital few assets that need protection from the trivial many that can safely fail.

A simple cost comparison example

Consider a small $200 conveyor motor with a redundant backup, so a failure never stops the line. Compare two strategies over one year.

Preventive replacement (swap every 6 months whether it needs it or not):

• 2 replacements per year at $200 each = $400 in parts.
• 2 hours of technician time per swap at $60/hour = $240 in labor.
• Total preventive cost = $640 per year, and you often discard motors with life still in them.

Run-to-failure (replace only when it fails):

• This motor actually fails about once every 18 months, so roughly 0.67 failures per year.
• Parts: 0.67 x $200 = $134.
• Labor: 0.67 x 2 hours x $60 = $80.
• No production loss, because the backup covers the gap.
• Total RTF cost = $214 per year.

RTF saves about $426 per year on this one motor, or roughly 66 percent. The math flips entirely if there is no backup: add even 4 hours of lost production at a $500/hour contribution margin and each failure now costs $2,000, making prevention the clear winner. The decision is always driven by the true cost of the failure, not the cost of the part.

The metrics that tell you if RTF is working

Even a deliberate RTF asset needs monitoring, because failure patterns change over time. Track these reliability metrics: MTBF and MTTR (mean time between failures and mean time to repair) for repairable assets, and MTTF for consumables you replace rather than fix. If MTBF starts falling or a "cheap" failure begins driving downtime, that asset has outgrown RTF and belongs on a preventive or condition-based plan. A rising failure rate is your signal to re-run the criticality analysis.

Where run-to-failure fits in a full maintenance program

RTF is not the opposite of a mature maintenance program. It is one tool inside it. A well-run plant runs a mix: preventive schedules for predictable wear, condition-based monitoring for critical rotating equipment, and RTF for the low-value tail. Within a total productive maintenance approach, deliberately assigning RTF frees technician time for the assets that actually move your OEE numbers. The goal is to spend maintenance effort where it changes the outcome and to stop spending it where it does not.

How Fabrico supports run-to-failure decisions

To decide RTF intelligently you need accurate failure and downtime data, and that is exactly what Fabrico provides. Fabrico is a real-time OEE and production-monitoring platform with a built-in CMMS, so every stoppage, work order, and spare-part movement is captured automatically. Its OEE product shows you which assets actually drive downtime, and the CMMS product tracks failure frequency, repair time, and spare-part usage per asset so your criticality analysis rests on real numbers instead of guesses. Because Fabrico offers camera and computer-vision monitoring, it can even capture stops on older machines that have no PLC, exactly the cheap, unmonitored assets RTF decisions often involve. Fabrico is EU-built with EU data residency. It does not perform predictive maintenance, automatic reordering, or digital-twin simulation. Instead it is the accurate data foundation that lets you decide, per asset, whether run-to-failure is a smart choice or a hidden liability.

Frequently Asked Questions

Is run-to-failure the same as having no maintenance strategy?

No. Deliberate RTF is a documented decision to let a specific low-criticality asset fail because prevention costs more than the failure, with a spare part ready in advance. Having no strategy means failures happen by accident on assets nobody assessed, which leads to unplanned downtime, scrap, and emergency repairs. Same repair, opposite level of control.

Which assets are good candidates for run-to-failure?

Assets that are cheap, fast to replace, non-critical, redundant, and whose failure is safe and causes no collateral damage. Light bulbs, small redundant pumps, standard belts, and inexpensive sensors are classic examples. Any asset whose failure risks safety, halts the line, has long-lead spares, or damages other equipment should never be run to failure.

How does run-to-failure relate to preventive and predictive maintenance?

They serve different asset classes within one program. Preventive maintenance schedules work on assets with predictable wear, condition-based and predictive approaches (predictive is an industry concept for forecasting failures from sensor data) target critical rotating equipment, and RTF covers the low-value tail where prevention would be wasteful. A mature plant uses all of them, matched to each asset's criticality.

Ready to base your run-to-failure decisions on real failure and downtime data instead of guesswork? Book a Fabrico demo to see how real-time OEE monitoring and a built-in CMMS reveal exactly which assets you can safely run to failure and which ones you cannot.