Preventive Maintenance Program Template & Prioritization Matrix
A practical, risk-based template to build a prioritized preventive maintenance (PM) schedule. Includes an asset register sample, criticality scoring, prioritization matrix, PM task definitions, frequency guidance, a simple calendar/dispatch template, and steps for integrating PMs into daily maintenance huddles and continuous improvement.
Purpose
This template helps you design a risk-based preventive maintenance program that protects critical assets without over-servicing less-critical equipment. Use the included scorecards, examples, and rules to prioritize work, set frequencies, and coordinate PMs with production and daily maintenance huddles.
How to use this template
- Populate the Asset Register with equipment, location, and basic details.
- Score each asset using the Criticality Scorecard (consequence & likelihood).
- Use the Prioritization Matrix to assign priority bands (A, B, C, D).
- Define PM tasks and assign suggested frequency buckets using the PM Task Definitions.
- Export the prioritized schedule to your calendar/CMMS and integrate PMs into daily maintenance huddles and the weekly dispatch plan.
Sample Asset Register (start here)
| Asset ID | Asset Name / Description | Location | Make / Model | Criticality Score | Priority Band | Primary PM Type |
|---|---|---|---|---|---|---|
| 1001 | Main conveyor (line 1) | Plant A - Line 1 | ConveyorCo X200 | 18 | A | Calendar + Condition |
| 1002 | Hydraulic press | Plant B - Shop | PressWorks P5 | 12 | B | Run-hours + Inspection |
Criticality Scorecard (example)
Score assets on two simple dimensions, then multiply to get a single criticality score.
- Consequence (1–6) — impact of failure on safety, production, quality, cost, or delivery. (1 = negligible, 6 = catastrophic)
- Likelihood (1–3) — current probability of failure based on age, condition, and history. (1 = unlikely, 3 = frequent)
Criticality Score = Consequence × Likelihood (range 1–18).
Priority bands (example)
- A (13–18): Highest priority — PMs required with short intervals; consider redundancy, spares, and condition monitoring.
- B (8–12): Important — regular PMs and condition checks; monitor trends.
- C (4–7): Routine — basic PMs, inspections timed to production windows.
- D (1–3): Low — minimal scheduled PM; use run-to-failure with periodic inspections.
Prioritization matrix (example)
A simple visual mapping of Consequence vs Likelihood helps allocate maintenance effort. Use the criticality score to assign the priority band above. Example decision rule: any asset with Consequence >=5 and Likelihood >=2 -> A band.
PM Task Definitions (templates)
- Inspection: Visual and functional check; record findings; escalate anomalies. (Checklist + photos)
- Lubrication: Apply specified lubricant to defined points; record quantity and condition.
- Parts replacement: Replace wear parts (belts, filters) per hours or calendar.
- Functional test: Run operational test and verify tolerances and safety interlocks.
- Condition measurement: Vibration, oil analysis, thermal scan, or other sensor reads.
Frequency guidance and simple optimization rules
Consider three frequency drivers and combine them pragmatically:
- Calendar-based (days/months) — use for corrosion, seals, and calendar-age wear.
- Usage-based (run-hours or cycles) — use for equipment where wear relates to use.
- Condition-based — use measurements or alarms to trigger service when indicators cross thresholds.
Optimization rules:
- Consolidate multiple tasks at common frequencies to reduce downtime (bundle tasks into one shutdown when safe).
- Shift non-critical tasks to planned production windows; avoid disrupting high-priority runs.
- Increase frequency for assets that show trending degradation; reduce when trend is stable and evidence supports it.
- Use a short pilot period when changing frequencies and monitor corrective work rates and failures for 3–6 months before locking changes.
Simple Calendar / Dispatch Template (weekly view)
| Day | Planned PMs | Priority | Assigned | Notes |
|---|---|---|---|---|
| Monday | Main conveyor — inspection & lubrication | A | Team 1 | Coordinate with Line 1 foreman |
| Wednesday | Hydraulic press — filter change | B | Team 2 | Schedule during off-peak |
Integrating PMs with Daily Maintenance Huddles
Use daily huddles to:
- Confirm today’s planned PMs and technician assignments.
- Raise any production constraints or change requests that could affect scheduling.
- Capture emerging condition findings and re-prioritize work in real time.
- Record PM completion and quick follow-ups (photos, spare needs).
Key performance indicators (suggested)
- PM compliance rate (% scheduled PMs completed on time)
- Preventive vs corrective maintenance ratio
- Overdue PM count
- Number of repeat failures after PM
When to escalate to a deeper analysis
If an asset shows repeated failures despite increasing PM effort, move to Reliability-Centered Maintenance (RCM) or a Root Cause Analysis. Avoid simply increasing frequency as the default remedy — find and address the failure mode.
Practical next steps
- Export this template to a spreadsheet or your CMMS and populate the asset register.
- Run the criticality score for each asset and assign priority bands.
- Schedule A-band PMs first; pilot frequency changes on a small set of assets and measure results.
- Use daily huddles to keep the schedule current and capture condition data that might convert PMs to condition-based triggers.
Files & artifacts to create from this template
- CSV/Excel asset register (fields: Asset ID, Name, Location, Consequence, Likelihood, Score, Priority, PM Type, Frequency, Last Done, Next Due)
- PM task checklists (one per PM task type — inspection, lubrication, replacement)
- Weekly dispatch board exported from CMMS or spreadsheet
Use this template as a living document — update scores and frequencies as you collect failure data and condition measurements.
Discussion
Comments and conversation will live here.