Why your maintenance strategy matters
Maintenance is not a single activity. It is a decision about how and when you intervene to keep assets running. Get that decision wrong, and you either spend too much on unnecessary servicing or too little, until something breaks at the worst possible time.
The strategy you choose shapes your costs, your downtime profile, your spare parts inventory and the daily workload of your maintenance team. A fleet of haul trucks at a mine site demands a different approach to a bank of office air conditioners. Applying the same strategy to both wastes resources on one and underserves the other.
This guide walks through five maintenance strategies, from the simplest (reactive) to the most sophisticated (reliability-centred). Each has a place. The goal is not to pick one and apply it everywhere, but to match the right strategy to the right asset based on criticality, cost and consequence of failure.
Reactive maintenance: when it works, when it hurts
Reactive maintenance, also called run-to-failure or corrective maintenance, means you do not touch the asset until it breaks. There is no scheduled servicing, no inspections, no monitoring. When it stops working, you fix it or replace it.
This sounds negligent, but for certain assets it is the most rational approach. If the asset is cheap to replace, has no safety implications, does not affect production when it fails, and does not degrade gradually (it either works or it does not), then the cost of preventive servicing may exceed the cost of occasional replacement. Light bulbs, disposable filters, basic hand tools and non-critical office equipment all fall into this category.
The problems start when reactive maintenance is applied to assets where it should not be. A critical pump that feeds an entire processing circuit, a crane on a construction site, a refrigerated transport unit carrying perishable goods: these are assets where unplanned failure carries serious consequences. Lost production, safety incidents, contract penalties, spoiled inventory.
The hidden cost of over-reliance on reactive maintenance is chaos. When breakdowns are unplanned, technicians are pulled from scheduled work. Parts need to be sourced urgently, often at premium cost. Overtime hours spike. And the planned work that got deferred creates a backlog that triggers more breakdowns, feeding a cycle that consumes the entire team's capacity.
Use reactive maintenance deliberately, for assets you have consciously decided to run to failure, not as a default because you have not got around to setting up anything better.
Preventive maintenance: scheduled peace of mind
Preventive maintenance (PM) is scheduled servicing at fixed intervals. Change the oil every 250 hours. Inspect the belts every month. Replace the bearings every 12 months. The schedule is based on time, usage or manufacturer recommendations, and it happens regardless of the asset's current condition.
This is the workhorse of most maintenance programmes, and for good reason. PM is straightforward to plan, easy to resource and does not require sensors or advanced analytics. You know what needs doing, when it needs doing, and you can schedule the parts and labour in advance. That predictability is valuable.
The trade-off is over-servicing. A bearing that could run for 18 months gets replaced at 12 because the schedule says so. Oil gets changed at 250 hours even though analysis would show it is still in specification at 350. Over-servicing is not catastrophic, but it adds up: unnecessary parts consumption, unnecessary labour hours and unnecessary downtime for servicing.
Despite that, preventive maintenance is the right strategy for the majority of assets in most organisations. It dramatically reduces unplanned breakdowns, extends asset life, and provides a structured framework for managing a large fleet. Automated PM scheduling through a CMMS takes the manual effort out of tracking intervals and generating work orders, which means the schedule actually gets followed rather than forgotten.
Start here if you are moving away from reactive maintenance. A solid preventive programme covers 70 to 80 per cent of what most operations need.
Predictive maintenance: data-driven timing
Predictive maintenance (PdM) uses data to forecast when an asset will fail, then schedules intervention just before that point. Instead of servicing at fixed intervals, you service when the data tells you the asset needs it.
The data comes from various sources: vibration sensors on rotating equipment, oil analysis for engines and gearboxes, thermography for electrical systems, ultrasonic testing for structural components. Each technique measures a specific indicator of degradation. When the indicator crosses a threshold, a work order is triggered.
The advantage over preventive maintenance is precision. You are not replacing a component that still has useful life, and you are not waiting until it fails catastrophically. You are intervening at the optimal point, which minimises both downtime and parts consumption. Studies consistently show that predictive maintenance reduces maintenance costs by 25 to 30 per cent compared to preventive-only programmes, and cuts unplanned downtime by 30 to 50 per cent.
The barrier is investment. Sensors, data infrastructure, analytical software and people with the skills to interpret the data all cost money. For a $2,000 pump, the cost of condition monitoring may exceed the cost of simply replacing it on a schedule. For a $500,000 haul truck engine, the economics shift dramatically in favour of prediction.
Predictive maintenance is most valuable for high-cost, high-criticality assets where unplanned failure is expensive and where the failure modes are detectable through monitoring. It complements preventive maintenance; it does not replace it entirely.
Condition-based maintenance: monitor and respond
Condition-based maintenance (CBM) is closely related to predictive maintenance, but the distinction matters. Where predictive maintenance forecasts future failure, condition-based maintenance responds to current condition. When a measured parameter (temperature, vibration, pressure, fluid level) moves outside its normal range, maintenance is triggered.
Think of it as a traffic light system. Green means the asset is operating within normal parameters, no action needed. Amber means a parameter has shifted and should be investigated at the next opportunity. Red means intervention is required now.
CBM does not require the forecasting algorithms that predictive maintenance uses. It requires monitoring (sensors, inspections or regular testing) and defined thresholds for action. This makes it more accessible for organisations that are not ready for full predictive analytics but want to move beyond calendar-based preventive schedules.
Practical examples include monitoring hydraulic fluid contamination levels in excavators, tracking bearing temperatures on conveyor systems, checking belt tension on crushers, or performing regular oil sampling on generator sets. When the condition data says the asset needs attention, you act. When it does not, you leave it alone.
The operational benefit is similar to predictive maintenance: you avoid unnecessary servicing and catch developing problems before they cause unplanned stoppages. MapTrack's maintenance module supports condition-based triggers alongside time-based and meter-based schedules, so teams can blend strategies within a single system.
Reliability-centred maintenance: the decision framework
Reliability-centred maintenance (RCM) is not a maintenance technique. It is a structured framework for deciding which technique to apply to each asset. Originally developed for commercial aviation in the 1970s, RCM analyses every asset and its failure modes to determine the most cost-effective maintenance strategy.
The process asks a series of questions for each failure mode: what is the function of this component? How can it fail? What happens when it fails? What is the consequence (safety, environmental, operational, economic)? Is the failure detectable before it occurs? What maintenance task can prevent or mitigate the failure?
The output is a tailored maintenance programme where every task has a documented justification. Some assets get preventive schedules. Some get condition monitoring. Some get a redesign to eliminate the failure mode entirely. And some, where the consequence of failure is negligible, are deliberately run to failure.
RCM is resource-intensive to implement. A full analysis of a complex plant can take months and requires cross-functional input from maintenance, operations and engineering. For large mining operations, processing plants and fleet-heavy logistics businesses, the investment pays off. For a small construction business with 50 assets, it is likely overkill.
Even if you do not conduct a formal RCM study, the underlying principle is worth adopting: match the maintenance strategy to the asset, based on criticality and failure consequences. Not everything needs the same level of attention.
Which strategy should you use?
The honest answer is: a combination. No operation of any complexity runs a single strategy across every asset. The table below provides a quick reference for matching strategy to context.
Reactive suits non-critical, low-cost assets where failure has no safety, production or compliance impact. Run them until they break, then fix or replace.
Preventive suits the majority of assets where scheduled servicing reduces breakdown risk at a reasonable cost. This is the foundation most teams should build on first.
Predictive suits high-value, high-criticality assets where the cost of unplanned failure justifies the investment in sensors and analytics.
Condition-based suits assets where failure is detectable through inspection or monitoring, but the forecasting infrastructure of predictive maintenance is not yet in place.
Reliability-centred suits complex operations with large, diverse asset fleets where a formal decision framework delivers measurable improvements in reliability and cost.
For most teams reading this, the practical starting point is to strengthen your preventive maintenance programme and introduce condition monitoring for your most critical assets. A platform like MapTrack lets you manage time-based, meter-based and condition-based schedules in one place, so you can blend strategies without juggling multiple systems.
If you want a deeper dive into implementing these strategies, the full maintenance strategy guide covers each approach in more detail with worked examples. And if you are ready to put structure around your maintenance workflows, book a demo to see how MapTrack handles scheduling, work orders and asset health tracking for field teams.
