Menu
Run-to-Failure vs Preventive Maintenance: When Doing Nothing Is the Right Strategy

Run-to-Failure vs Preventive Maintenance: When Doing Nothing Is the Right Strategy

Run-to-failure deliberately runs an asset until it breaks. On the right asset that is smart, not lazy. On the wrong one it is a catastrophe waiting to happen.
Run-to-Failure vs Preventive Maintenance: When Doing Nothing Is the Right Strategy
Run-to-Failure vs Preventive Maintenance: When Doing Nothing Is the Right Strategy

Key takeaways

  • Run-to-failure deliberately operates an asset until it fails, then repairs or replaces it.
  • On low-criticality, cheap, redundant assets, run-to-failure is the rational choice.
  • On critical assets, run-to-failure invites catastrophic, expensive, unsafe failures.
  • It is a deliberate strategy chosen by criticality — not an absence of strategy.

Short answer: Run-to-failure means deliberately running an asset until it breaks, then fixing it — no preventive work. On a cheap, non-critical, easily-replaced asset, that is the economically correct choice. On a critical asset whose failure stops the line or creates a hazard, it is reckless. The skill is choosing run-to-failure deliberately by criticality, not by neglect. See also condition based vs time based maintenance.

When run-to-failure is right

  • Low criticality — failure does not stop production.
  • Cheap and fast to replace.
  • Redundant or non-safety-related.

When it is dangerous

  • Critical assets that stop the line.
  • Safety- or environment-related equipment.
  • Long-lead or expensive to replace.

Why it is a real strategy

Preventive work on a trivial asset wastes labour better spent on critical equipment. Choosing run-to-failure for the trivial frees resources for what matters — that is reliability-centred thinking, not laziness.

Deciding by criticality

An asset criticality assessment sorts equipment by failure consequence. The low end gets run-to-failure; the high end gets preventive or condition-based care. The matrix makes the call explicit.

How OEE relates

Run-to-failure on a non-constraint costs little OEE. The same strategy on the bottleneck would be disastrous — which is exactly why criticality, not habit, must drive the choice.

See how Fabrico captures this automatically on your lines — explore OEE for manufacturing or book a demo.

Related reading

Frequently asked questions

Is run-to-failure just neglect?

No — chosen deliberately by criticality, it is rational.

Which assets suit it?

Cheap, non-critical, redundant, fast to replace.

How do I decide?

Use an asset criticality assessment.

Can the bottleneck be run-to-failure?

No — its failure costs the whole plant.

Das Neueste aus unserem Blog

Definieren Sie Ihren Zuverlässigkeitsfahrplan
Überzeugen Sie sich selbst!
Definieren Sie Ihren Zuverlässigkeitsfahrplan
Indem Sie auf die Schaltfläche „Akzeptieren“ klicken, erklären Sie sich mit der Nutzung einverstanden.Cookies beim Zugriff auf diese Website und bei der Nutzung unserer Dienste. Erfahren Sie mehrWeitere Informationen zur Verwendung und Verwaltung von Cookies finden Sie in unserem Datenschutzrichtlinie und Cookie-Erklärung