Facilities with structured preventive maintenance programmes achieve 50% greater efficiency and experience 71% fewer unplanned downtime incidents compared to operations running reactively. Yet most FM teams still spend 60–80% of their maintenance budget reacting to failures — not because they lack knowledge, but because they lack a system. Sign in to OxMaint to build your preventive maintenance programme from asset inventory to automated scheduling — or book a demo to see a structured PM framework configured for your facility.
Strategy Guide · Maintenance Excellence 2026
Preventive Maintenance Best Practices: A Complete Framework for Facility Managers
From asset criticality ranking and FMEA-driven scheduling to CMMS automation and continuous improvement — the systematic PM framework that converts reactive fire-fighting into planned, measurable reliability.
71%
Fewer downtime incidents with structured PM vs. reactive-only programmes
4.8×
Higher cost of emergency repairs vs. the same repair as a planned PM event
85%
PM completion rate — the best-in-class benchmark for high-performing FM teams
12–18%
Annual maintenance cost savings from FMEA-driven PM vs. run-to-failure
Where Are You Today?
The PM Maturity Ladder — 5 Levels of Maintenance Excellence
Every FM team sits somewhere on this ladder. Knowing your current level identifies the single highest-value next step. Sign in to OxMaint to move up the ladder with automated scheduling, digital work orders, and CMMS-tracked PM completion rates.
Level 5
Predictive & Optimised
Condition-based triggers replace calendar intervals. IoT sensor integration, FMEA-driven task libraries, and continuous interval optimisation using MTBF data. PM completion >90%. Reactive ratio below 10%.
Excellence
Level 4
CMMS-Automated PM
All PM tasks scheduled and tracked in CMMS. Work orders auto-generate before due dates. Mobile checklists with photo documentation. KPIs tracked: completion rate, MTTR, cost per asset. Reactive ratio 20–35%.
Advanced
Level 3
Structured Preventive
Formal PM schedule exists and is followed consistently. Asset criticality ranking drives task priority. OEM and regulatory intervals documented. Still mostly calendar-based. Reactive ratio 35–50%.
Developing
Level 2
Informal PM Attempts
Some PM tasks exist on paper or spreadsheets. Execution depends on individual memory and initiative. No formal tracking. High missed intervals. Reactive ratio 50–70%.
Early
Level 1
Reactive / Run-to-Failure
Maintenance occurs only when something breaks. No asset inventory, no PM schedule, no tracking. Emergency repairs dominate. High cost, low predictability, frequent safety incidents. Reactive ratio >70%.
Reactive
The Framework
5-Step PM Framework: From Asset Inventory to Continuous Improvement
This is the structured sequence that transforms a reactive operation into a reliable, data-driven programme. Each step builds on the previous — skipping asset inventory makes scheduling guesswork; skipping CMMS automation makes continuous improvement impossible. Book a demo to see this framework implemented in OxMaint for your facility.
01
Build the Asset Inventory and Criticality Ranking
Register every maintainable asset with equipment name, model, location, installation date, and OEM manual reference. Assign each asset a criticality classification — Critical, Important, or Standard — based on its impact on operations, safety, and regulatory compliance if it fails. The 20% of assets classified as Critical typically drive 80% of PM planning attention and resource allocation. Without this inventory, PM scheduling is guesswork.
Output: Complete asset register with criticality scores, ready for PM task assignment
02
Apply FMEA — Define What Can Fail and Why
For each Critical asset, conduct Failure Mode and Effects Analysis: identify every failure mode, its operational and safety effect, and a Risk Priority Number (RPN = Severity × Occurrence × Detection). High-RPN failure modes drive specific PM task definitions — not generic "inspect pump" instructions but actionable tasks: "check seal condition, verify coupling alignment, measure bearing temperature." FMEA converts maintenance from calendar assumption to risk-evidence prevention. Nearly 60% of maintenance leaders using CMMS tools say FMEA is critical for a robust PM programme. Sign in to link FMEA findings to PM task templates in OxMaint.
Output: FMEA-linked PM task library per Critical asset with justified intervals
03
Select the Right Scheduling Methodology Per Asset
Calendar-based PM suits assets with predictable wear patterns and compliance-mandated intervals. Usage-based PM (runtime hours, cycles) suits motors, pumps, and vehicles. Condition-based PM (sensor threshold triggers) suits assets where degradation is detectable before failure. Aligning methodology to failure pattern prevents over-maintaining low-risk equipment while under-maintaining condition-sensitive assets simultaneously — the defining characteristic of calendar-only PM programmes. Book a demo to see per-asset scheduling methodology configuration in OxMaint.
Output: Per-asset scheduling methodology and initial PM intervals set by failure evidence
04
Automate in CMMS — Eliminate Manual Coordination
Configure all PM tasks, intervals, and assignments in the CMMS so work orders generate automatically before due dates. Technicians receive mobile notifications with full task checklists, asset history, and parts requirements. Completion data flows back into the asset record at close. The programme moves from "relies on someone remembering to book the contractor" to "work orders generate, escalate, and close automatically." Best-in-class target: PM completion rate above 85%. Below 70% signals scheduling overload or resource gaps. Sign in to activate automated PM scheduling in OxMaint.
Output: Automated PM work order engine with mobile checklists and completion tracking
05
Measure, Analyse, and Optimise Continuously
Review PM programme performance quarterly using CMMS data: completion rate, reactive ratio, MTBF per asset class, MTTR, and cost per work order. Identify assets with recurring failures despite PM — intervals too long or incorrect tasks. Identify assets with zero defects across multiple cycles — candidates for interval extension. Delete legacy PM tasks that cannot be linked to a documented failure mode. Eliminating unjustifiable tasks reduces maintenance cost and technician workload without increasing risk. Book a demo to see PM analytics and interval optimisation in OxMaint.
Output: Quarterly PM optimisation cycle with data-driven interval adjustments
Scheduling Methodologies
Which PM Scheduling Approach Fits Which Asset?
Calendar-Based
Trigger: Fixed time interval
Best for assets with predictable degradation rates unrelated to usage — building envelope inspections, fire suppression tests, compliance-driven checks with regulatory interval requirements.
Simple to schedule and plan resources
Satisfies regulatory interval requirements
May over-maintain low-utilisation assets
Usage-Based
Trigger: Runtime hours / cycles / mileage
Best for assets whose wear is proportional to use — motors, pumps, compressors, vehicles, and any equipment where OEM PM intervals are expressed in operating hours rather than calendar time.
Aligns maintenance to actual wear accumulation
Prevents under-maintenance of high-utilisation assets
Requires runtime hour tracking in CMMS
Condition-Based
Trigger: Sensor threshold or inspection finding
Best for assets where degradation is detectable before failure — bearing vibration, motor current trending, oil analysis, refrigerant subcooling drift. Work order triggered by data, not calendar.
Maintenance only when genuinely needed
Catches P-F interval before failure occurs
Requires sensor infrastructure or monitoring
Predictive
Trigger: AI / ML anomaly detection
Best for high-criticality assets with continuous sensor coverage — chillers, critical power systems, production equipment where unexpected failure has severe consequence. Extends P-F detection upstream.
Earliest possible failure detection
Highest asset availability for critical equipment
Requires data infrastructure and ML calibration
Risk-Driven Maintenance
How FMEA Drives PM Task Definitions
FMEA converts maintenance from calendar assumption to risk-evidence prevention. The RPN score determines which failure modes get PM tasks and how frequent those tasks must be. Sign in to OxMaint to link FMEA findings directly to PM work order templates per asset.
S
Severity
How bad is the failure's effect on operations, safety, or compliance? (1–10)
×
O
Occurrence
How often does this failure mode occur? Based on work order history. (1–10)
×
D
Detection
How easily is it detected before it causes harm? Lower = easier to detect. (1–10)
=
RPN
Risk Priority
High RPN → frequent PM + condition monitoring. Low RPN → run-to-failure may be acceptable.
If a PM task cannot be linked to a specific failure mode in your FMEA, consider removing it. Many facilities carry "legacy PMs" added years ago for equipment that no longer exists or one-time failures. Eliminating unjustifiable tasks reduces maintenance cost and technician workload without increasing risk.
Measuring Success
The 5 KPIs That Define a High-Performing PM Programme
PM Completion Rate
Target: >85%
Percentage of scheduled PMs completed on time. Below 70% signals resource gaps compounding into emergency costs. Track monthly per asset class.
Reactive-to-Planned Ratio
Target: <20% reactive
Proportion of total work orders that are unplanned. Above 40% reactive indicates PM is not preventing failures effectively. Most facilities reach target within 12 months of CMMS adoption.
MTBF
Target: Increasing trend
Mean Time Between Failures per asset class. Increasing MTBF confirms PM is preventing failures. Declining MTBF despite PM indicates wrong intervals or incorrect task definitions.
MTTR
Target: Decreasing trend
Mean Time to Repair — average time from failure to return to service. Decreasing MTTR reflects better technician preparation and parts availability driven by CMMS asset history.
Cost per Work Order
Target: PM < Reactive cost
Planned PM costs 4.8× less than the same repair as an emergency. Tracking this ratio builds the business case for PM investment and defends FM budget against reactive cost accusations.
Ready to Move Your Facility Up the PM Maturity Ladder?
OxMaint provides the asset registry, FMEA-linked PM templates, automated work order scheduling, mobile checklists, and KPI dashboards that make every step of this framework executable from day one. Free trial, no implementation fees.
Common Questions
Facility Managers Ask These About Building a PM Programme
What is the difference between preventive and predictive maintenance?
Preventive maintenance (PM) operates on a pre-defined schedule — calendar intervals, runtime hours, or usage cycles — regardless of current equipment condition. Predictive maintenance (PdM) uses real-time condition data from sensors, vibration analysis, thermography, or oil analysis to schedule maintenance only when degradation indicators suggest failure is approaching. PM is the foundation; PdM extends the P-F interval detection for critical assets. Most facilities implement PM first, then layer PdM on top for highest-criticality equipment. Sign in to configure both PM schedules and condition-based triggers in OxMaint.
How do I know if my PM intervals are set correctly?
Correctly set PM intervals produce a specific CMMS data pattern: inspections regularly find minor wear and early degradation but rarely severe failures. If your PM visits consistently find nothing wrong, the interval is likely too short — you are over-maintaining. If assets are failing between PM visits, the interval is too long. Start with OEM recommendations, then use CMMS work order history to adjust based on actual failure patterns after 12–18 months of data. Book a demo to see interval optimisation analytics in OxMaint.
How long does it take to build a PM programme from scratch?
A functional first-pass PM programme — asset inventory, criticality ranking, initial PM tasks and intervals, and CMMS configuration — typically takes 4–8 weeks for a single-site facility with 200–500 assets. The first 12 months of execution accumulates the data needed for meaningful interval optimisation. A mature, data-optimised programme typically requires 18–24 months of CMMS data history. Starting is the highest-value action — every month of reactive-only operation delays the data accumulation needed to optimise. Sign in to start building your PM programme in OxMaint today.
What PM completion rate should I target and what does below-target mean?
Best-in-class facilities target above 85%. Below 70% typically signals one of three problems: the schedule is overloaded relative to available technician hours; technicians are being pulled to reactive emergencies; or the CMMS is generating PMs technicians do not believe are necessary. Each cause has a different solution. The common thread: track completion rate in your CMMS and review the gap cause monthly rather than accepting low completion as normal. Book a demo to see PM completion rate tracking per asset class in OxMaint.
