Maintenance strategies are usually presented as a ladder you climb, with reactive at the bottom and something clever at the top. That framing is misleading and expensive. Every real site runs several strategies at once, deliberately, and the skill is deciding which assets get which. A plan that puts everything on a calendar interval wastes as much as one that waits for things to break.
Reactive and breakdown maintenance are choices, not failures
Reactive maintenance and breakdown maintenance mean fixing it when it stops, and for a large share of assets that is the correct economic answer. A cheap, redundant, quickly replaced component with no safety consequence does not deserve a schedule. The failure is not running to failure; it is running to failure by accident, on an asset whose stoppage costs a shift. Deciding explicitly which assets are allowed to fail is the first honest step in any maintenance strategy.
Routine, scheduled and proactive: the same idea at different depths
Routine maintenance and scheduled maintenance describe work fixed to an interval, inspect, clean, lubricate, replace on time regardless of condition. Proactive maintenance goes one step further and asks why the failure happens at all, addressing causes rather than symptoms. In practice most sites need the interval-based layer first, because it is cheap and repeatable, and reach for cause-hunting only on the assets that keep coming back despite it.
Condition based and smart maintenance, and what they need
Condition based maintenance acts on a measured signal rather than a date, which is more efficient and needs something to measure with. Smart maintenance usually means the same idea with the readings collected automatically. The honest caveat is that both require instrumentation or manual readings taken consistently, and a site that cannot keep a checklist filled in reliably will not sustain a condition-based programme. Start where the data already exists.
A maintenance strategy example that is actually usable
Take the asset list, and for each entry answer two questions: what does it cost when this stops, and does it fail with time, with use, or at random. Assets that are expensive to lose and fail predictably get intervals. Expensive and unpredictable gets condition monitoring where you can measure something. Cheap and quickly replaced runs to failure on purpose. That sorting takes an afternoon and does more for a plan than any software decision.
Questions people ask about maintenance strategy
Is reactive maintenance always bad?
No. For cheap, redundant, quickly replaced assets with no safety consequence, running to failure is the correct economic answer. The problem is doing it by accident on something whose stoppage costs a shift.
What is the difference between routine and scheduled maintenance?
In practice very little; both mean work fixed to an interval regardless of condition. Routine tends to describe the light recurring tasks, scheduled the planned replacements, but sites use them interchangeably.
When is condition based maintenance worth it?
When the asset is expensive to lose, fails unpredictably, and you can actually measure something that changes before failure. Without a reliable measurement it becomes calendar maintenance with extra steps.