Key takeaways
Short answer: Run-to-failure and condition-based maintenance sit at opposite ends of the maintenance-strategy spectrum. Run-to-failure (RTF) deliberately operates an asset until it breaks, then fixes it — which is a sensible, economic choice for low-consequence assets where preventing failures would cost more than the failures. Condition-based maintenance (CBM) continuously monitors an asset's real health and intervenes only when measured indicators cross a threshold — the right choice for critical assets where failure is expensive. RTF accepts failure; CBM catches it just in time. For the strategy method that chooses between them, see reliability-centered maintenance.
Run-to-failure (RTF) is the deliberate strategy of operating an asset until it fails, with no preventive intervention, and then repairing or replacing it. Crucially, as a strategy this is a conscious, economic choice — not the same as reactive maintenance by neglect. RTF is the right call when preventing an asset's failures would cost more than simply letting them happen: cheap, redundant, easily-replaced, low-consequence assets whose failure causes little disruption. For such assets, spending on inspections, monitoring, or scheduled replacement is wasted effort, because the failure itself is trivial and easily absorbed. RTF holds no maintenance cost until the asset fails, and for genuinely low-consequence equipment that is the most economic outcome. The discipline is to apply RTF deliberately, to the assets where the analysis shows failure is cheaper to accept than to prevent — not as a default to important equipment.
Condition-based maintenance (CBM) is, in a sense, the opposite philosophy: continuously or periodically monitor an asset's actual health — vibration, temperature, oil condition, motor current, acoustics — and intervene only when those measured indicators show that intervention is genuinely due. Rather than letting the asset fail (RTF) or servicing it on a blind schedule (preventive), CBM acts on real evidence of developing degradation, catching a failure just before it happens. CBM minimizes both unnecessary maintenance (you act only when the condition warrants) and unplanned failures (you catch degradation early). Its cost is the monitoring infrastructure — sensors, data, analysis — and the discipline to act on what the data shows. CBM is the right choice for critical, expensive, or instrumented assets where failure is costly enough that the monitoring investment pays for itself many times over in avoided breakdowns.
The clean distinction is what you do about failure: RTF accepts it (let the asset fail, then fix), CBM catches it (monitor and intervene just before failure). They sit at opposite ends of the maintenance-strategy spectrum — RTF the most hands-off, CBM among the most sophisticated. The choice between them is driven entirely by consequence and cost. For a low-consequence asset, accepting failure (RTF) is cheapest, because catching it with CBM would cost more in monitoring than the failure costs. For a high-consequence asset, catching failure (CBM) is cheapest, because the monitoring cost is small next to the breakdown it prevents. They are not competing approaches to the same asset but appropriate strategies for different assets — which is exactly why a method like RCM exists to decide, asset by asset, which strategy each one warrants.
A plant has two pumps. The first is a small, cheap, redundant backup pump — if it fails, the backup takes over and no one notices, and the pump is replaced from stock in an hour. For this pump, run-to-failure is the right strategy: monitoring it or servicing it on a schedule would cost more than its trivial, easily-absorbed failures, so the plant deliberately runs it to failure and replaces it when it dies. The second is a large, expensive, critical pump whose failure stops the whole line and takes days to repair. For this pump, condition-based maintenance is the right strategy: vibration and temperature sensors monitor its health, and when the data shows a developing bearing problem, the plant intervenes just in time — a planned repair instead of a catastrophic failure. Same type of asset, opposite strategies, each chosen by the consequence of failure.
The decision is a consequence-and-cost analysis done per asset. Choose run-to-failure when the asset is low-consequence — cheap, redundant, quickly replaced, with failures that cause little disruption — so that the cost of any preventive or condition-based effort would exceed the cost of just letting it fail. Choose condition-based maintenance when the asset is critical, expensive to fail, or dangerous, and is instrumentable, so that the monitoring investment is justified by the costly failures it prevents. Between these extremes sit scheduled preventive maintenance (for predictable-wear assets) and predictive maintenance (CBM plus forecasting). No single strategy is right for a whole plant; the goal is to match each asset to the strategy its consequence and cost warrant — which is the entire purpose of reliability-centered maintenance. Run-to-failure and CBM are the two ends of the range that analysis chooses between.
Both strategies, applied correctly, protect the availability factor of OEE by allocating maintenance effort where it matters. Condition-based maintenance directly raises availability on critical assets by catching failures just before they cause unplanned downtime — the biggest availability loss — converting them into planned interventions and lifting reliability. Run-to-failure protects OEE indirectly: by deliberately not spending effort on low-consequence assets, it frees maintenance resources to concentrate on the critical ones that actually drive availability. The combination — CBM where failure hurts, RTF where it does not — is exactly how a maintenance program maximizes the availability it buys per unit of effort, the logic behind condition-based and reliability-centered maintenance.
Fabrico provides the data to decide where each strategy fits and to confirm it is working. Its downtime and failure data reveals which assets actually cause the most lost OEE — telling you which warrant condition-based monitoring and which are low-consequence enough to run to failure — grounding the strategy choice in real impact rather than assumption. For CBM assets, connecting that monitoring to live OEE confirms whether catching failures early is actually lifting availability. Book a demo to match maintenance strategy to real consequence.
Run-to-failure deliberately operates an asset until it fails, then repairs or replaces it — a valid economic choice for low-consequence assets. Condition-based maintenance monitors real asset health and intervenes only when indicators show intervention is due. RTF accepts failure; CBM catches it just in time.
Not quite. Run-to-failure as a strategy is a deliberate, economic choice for low-consequence assets where preventing failures would cost more than the failures. Reactive maintenance by neglect is running critical equipment to failure for lack of any strategy — that is the costly mistake RTF is not.
For genuinely low-consequence assets — cheap, redundant, quickly replaced, with failures that cause little disruption — where the cost of monitoring or preventive effort would exceed the cost of simply letting the asset fail and fixing it.
For critical, expensive, or dangerous assets that can be instrumented, where failure is costly enough that the monitoring investment pays for itself by catching degradation early and converting breakdowns into planned interventions.
Condition-based maintenance directly raises availability on critical assets by catching failures before unplanned downtime. Run-to-failure protects OEE indirectly by freeing maintenance effort from low-consequence assets to focus on the critical ones that drive availability.
Connexion
Blog
