Why preventive maintenance matters
Preventive maintenance is the single most impactful change most operations can make to reduce unplanned downtime and control maintenance costs. The principle is simple: service assets at regular intervals before they fail, rather than waiting for something to break and scrambling to fix it. Yet many organisations still operate without a structured preventive maintenance programme, defaulting to reactive repairs that cost more, take longer and create unpredictable disruption.
Data from Australian industry benchmarks consistently shows that organisations with structured PM programmes achieve 25 to 40 per cent lower total maintenance costs than those relying primarily on reactive methods. The savings compound: fewer emergency callouts, lower overtime, reduced spare parts waste, longer asset life and, critically, higher asset availability. For field operations where every hour of downtime has a dollar value, whether in lost production, missed deliveries or idle crews, those savings are substantial.
This guide walks through a five-step process for building a PM programme from scratch. If you are starting from zero or rebuilding an existing programme that has fallen apart, this is the framework. Each step builds on the previous one, so work through them in order.
Step 1: Build your asset inventory
You cannot maintain what you have not documented. The first step is building a comprehensive asset register that captures every maintainable asset in your operation. This is not a quick task, but it is the foundation everything else rests on. Skip it, and your PM schedule will have gaps from day one.
What to capture for each asset
At minimum, your asset register should include the following for every maintainable item:
- Asset ID: A unique identifier (barcode, QR code or internal number) that never changes.
- Description: Make, model, serial number and a plain-language description.
- Location: Where the asset is physically located or assigned (site, building, production line, vehicle).
- Criticality rating: High, medium or low, based on the impact of its failure on safety, production and compliance.
- Commission date: When the asset entered service.
- Current meter reading: Hours, kilometres or cycles, depending on the asset type.
- Manufacturer service requirements: The OEM recommended intervals and tasks.
Practical tips for the inventory phase
Walk the floor. Do not rely on existing spreadsheets or purchase records alone. Physical verification catches assets that were never registered, assets that have been moved, and assets that have been decommissioned but never removed from the system. Use QR code or barcode labels to tag each asset during the walkthrough so you can scan them during future audits.
Prioritise breadth over depth in the first pass. Capture every asset, even if some records are incomplete. You can fill in serial numbers and commission dates later. What you cannot do is build a PM schedule for assets you do not know exist.
Step 2: Define maintenance tasks and intervals
With your asset inventory complete, the next step is defining what maintenance tasks each asset needs and how often. This is where the programme moves from a list of equipment to a schedule of work.
Start with manufacturer recommendations
Every piece of equipment comes with a service manual that specifies recommended intervals for oil changes, filter replacements, belt inspections, brake checks, calibrations and other routine tasks. These intervals are your starting baseline. They represent the minimum maintenance the manufacturer considers necessary to keep the asset reliable and the warranty valid.
Adjust for your operating conditions
Manufacturer intervals assume standard operating conditions. If your assets operate in dust, extreme heat, high humidity, constant vibration, or under heavy load, those intervals need to be shortened. A fleet vehicle rated for 15,000-kilometre oil changes might need 10,000 kilometres in outback conditions. A conveyor bearing rated for 5,000 hours might need inspection at 3,000 hours in a crusher application.
Use a tiered task structure
Group maintenance tasks into service levels to simplify scheduling. A three-tier structure works for most operations:
| Level | Frequency | Typical tasks |
|---|---|---|
| A (minor) | Monthly or every 250-500 hours | Oil and filter change, fluid top-ups, visual inspection, tyre/track check, safety device test |
| B (intermediate) | Quarterly or every 1,000-2,000 hours | Level A tasks plus brake inspection, belt replacement, coolant flush, battery test, calibration checks |
| C (major) | Annually or every 4,000-5,000 hours | Levels A and B plus transmission service, major component rebuild, full electrical system test, structural inspection |
Document each task with clear instructions, required parts, estimated duration and any safety precautions. This documentation becomes the basis for work orders and ensures consistency regardless of which technician performs the work.
Step 3: Set up scheduling and triggers
Defining tasks is only useful if there is a system to ensure they actually happen. This step is about establishing the scheduling mechanism that will generate work at the right time and escalate when things fall behind.
Choose your trigger types
Most PM programmes use a combination of trigger types. The most common are:
- Calendar-based: Service every 30 days, 90 days or 12 months. Simple and reliable for assets without usage meters.
- Usage-based: Service every 500 hours, 10,000 kilometres or 1,000 cycles. More accurate for assets with variable usage patterns.
- Whichever-comes-first: Service at 500 hours OR 90 days, whichever occurs first. This is the safest approach for most assets.
A CMMS with automated scheduling handles all three trigger types and fires whichever comes first. It also creates the work order automatically, assigns it to the right person and sends notifications when items are approaching or overdue. This automation is what separates PM programmes that sustain themselves from those that gradually fall apart.
Build in escalation rules
Define what happens when a scheduled service is not completed on time. A typical escalation chain might look like this:
- Due date: Work order assigned to technician with a target completion date.
- 3 days overdue: Automated reminder sent to technician.
- 7 days overdue: Notification escalated to supervisor.
- 14 days overdue: Alert sent to operations manager and asset flagged as high-risk.
Without escalation rules, overdue work orders accumulate silently until an asset fails and someone asks why the service was not done. By that point, the damage is done.
Integrate with inspections
Pre-start inspections and operator rounds are a natural complement to PM schedules. When a driver or operator flags a defect during a digital pre-start inspection, the system can automatically create a corrective work order linked to the asset. This catches developing issues between scheduled services and feeds real-time condition data into your maintenance planning.
Step 4: Staff and resource the programme
A well-designed PM schedule is worthless if you do not have the people, parts and time to execute it. This step covers the practical resourcing questions that determine whether your programme succeeds or stalls.
Calculate your labour requirement
Add up the estimated hours for all scheduled tasks across your asset portfolio. This gives you your total annual PM labour requirement. Divide by available technician hours (accounting for leave, training, reactive work and non-wrench time such as travel and paperwork) to determine whether your current team can handle the workload.
A common benchmark: technicians in field operations typically spend 55 to 65 per cent of their available hours on actual maintenance tasks. The remainder goes to travel, parts retrieval, paperwork and waiting. Factor this into your calculations, or you will overestimate capacity.
Stock critical spare parts
Review your task definitions and identify the parts consumed at each service level. Stock critical spares that have long lead times or are needed for your most important assets. Running out of a $30 filter and deferring a service because of it is an expensive false economy when the resulting breakdown costs thousands.
Tracking parts inventory alongside your PM schedule ensures that upcoming services have the materials they need. When the system generates a work order, it can automatically check stock levels and flag shortages before the technician arrives to find an empty shelf.
Protect PM time in the schedule
One of the most common reasons PM programmes fail is that planned work gets displaced by reactive work. A breakdown happens, the technician drops the scheduled service to deal with it, and the PM work gets deferred indefinitely. Over time, the backlog grows and more breakdowns occur because assets are being missed.
Protect PM time by dedicating specific days or shifts to planned work. Some operations run PM on weekends when production is lower. Others block out two days per week as PM-only time. The exact approach depends on your operation, but the principle is the same: treat planned maintenance as immovable and schedule reactive capacity separately.
Step 5: Track KPIs and refine
A PM programme is not a set-and-forget exercise. It requires ongoing measurement and refinement to stay effective. The right metrics tell you whether the programme is working, where it is falling short and where intervals need adjustment.
Essential PM programme KPIs
| KPI | Target | Why it matters |
|---|---|---|
| PM compliance rate | >90% | Percentage of scheduled PMs completed on time. Below 80% and breakdowns will increase. |
| Planned vs unplanned ratio | 80:20 | Measures the balance between preventive and reactive work. Indicates programme maturity. |
| MTBF | Trending upward | Mean time between failures. A rising MTBF confirms the PM programme is preventing breakdowns. |
| Maintenance cost per asset | Stable or declining | Total maintenance spend divided by asset count. Should stabilise as reactive costs decrease. |
| Asset availability | >90% | Percentage of assets available for use on any given day. The ultimate measure of programme impact. |
Monthly review cadence
Set a monthly review meeting to examine these KPIs, review overdue work orders, discuss recurring defects and adjust intervals where data supports a change. This review should involve both maintenance and operations stakeholders so that scheduling decisions consider production requirements.
Interval refinement
After six months of data, you will have enough history to refine your intervals. Assets where technicians consistently find no issues at service may be over-scheduled, and intervals can be extended. Assets that fail between services are under-scheduled, and intervals need shortening. This data-driven refinement is what transforms a generic PM schedule into one optimised for your specific operation.
Common mistakes to avoid
Building a PM programme is straightforward in theory but easy to derail in practice. These are the mistakes that most commonly cause programmes to stall or fail.
- Starting too ambitiously. Trying to put every asset on a PM schedule from day one overwhelms the team. Start with your top 20 per cent of critical assets and expand once the process is stable.
- Ignoring operating conditions. Copying manufacturer intervals without adjusting for dust, heat, load or usage patterns leads to either over-servicing or under-servicing.
- No escalation for overdue work. Without automated escalation, overdue services pile up silently until a failure forces attention.
- Letting reactive work displace PM. If every breakdown cancels a scheduled service, the programme will never reach critical mass. Protect PM time.
- Skipping the measurement step. Without KPIs you have no way to know if the programme is working or where to improve. Data turns maintenance from a gut-feel exercise into a managed discipline.
- Paper-based scheduling. Paper work orders get lost, handwritten entries are illegible, and there is no automated escalation or reporting. For any operation beyond 20 assets, a digital system is effectively required.
Tools and templates
The right tools accelerate implementation and sustain the programme long-term. Here is what to consider at each stage.
Maintenance management platform
A CMMS or maintenance management platform is the operational backbone of your PM programme. It manages the asset register, automates scheduling, generates and tracks work orders, and produces the KPI reports you need for ongoing refinement. MapTrack's maintenance module supports time-based, meter-based and condition-based triggers, handles work order assignment and escalation, and integrates with inspections so defect-driven work flows into the same system.
Inspection checklists
Digital preventive maintenance checklists standardise what technicians check at each service level. When the checklist is built into the work order, technicians follow a consistent process every time, and the completed checklist becomes part of the asset's service record.
Getting started
If you are currently running without a structured PM programme, the best time to start is now. Begin with Step 1, even if it takes a few weeks to complete the asset inventory. Each step you complete moves your operation closer to predictable, controlled maintenance costs and away from the reactive cycle that drains both budget and morale. Book a demo to see how MapTrack supports each step of the PM programme build, from asset register through to KPI dashboards.
