Preventive maintenance — the complete operations guide
Preventive maintenance is the practice of performing planned, scheduled service on physical assets before failure occurs — replacing reactive firefighting with a predictable, budgeted, data-driven maintenance programme that extends asset life, reduces downtime, and eliminates emergency repair costs.
Used by manufacturing, healthcare, facilities, and fleet operations teams · No credit card required
What is preventive maintenance?
Preventive maintenance (PM) is the scheduled, proactive servicing of physical assets at defined intervals — designed to prevent failure before it occurs, rather than responding to failures after they happen. It replaces the unpredictable, costly cycle of breakdown and emergency repair with planned, budgeted, controlled maintenance work.
Every piece of equipment deteriorates over time and through use. Bearings wear, lubricants degrade, filters accumulate, belts stretch, seals dry out. A preventive maintenance programme identifies these deterioration patterns and schedules servicing — lubrication, part replacement, calibration, inspection — at the point where intervention is cost-effective, before deterioration progresses to failure.
In practice, PM is implemented through a CMMS (Computerized Maintenance Management System) that stores PM rules for each asset, automatically generates PM work orders when intervals become due, assigns them to technicians, and records the service outcome — creating a continuous, auditable maintenance programme that runs without manual coordination.
What a PM programme solves
- Unplanned downtime from equipment failures that should have been preventable
- Emergency repair costs 3–5× higher than equivalent planned service
- Missed manufacturer-specified service intervals voiding warranty coverage
- No record of whether maintenance was performed — or when it was last done
- Maintenance schedules living in one person's head — lost when they leave
- Compliance failures when regulators ask for maintenance evidence
- Premature asset retirement due to neglect rather than economic end-of-life
Glossary
- PM Rule
- A configured instruction that defines a service type, interval, and technician assignment for an asset — the engine of automatic PM work order generation.
- PM Interval
- The frequency at which a PM task is performed — measured in time (days, months) or usage (hours, cycles, km).
- PM Compliance Rate
- Percentage of PM work orders completed within their scheduled window. Target: above 95%.
- MTBF
- Mean Time Between Failures — the primary metric validating PM programme effectiveness. Higher MTBF means fewer failures.
- PM:CM Ratio
- Ratio of preventive to corrective work orders. Higher ratios indicate a more proactive maintenance culture.
- Condition-based PM
- PM triggered by a monitored asset parameter (vibration, temperature, pressure) crossing a threshold — rather than elapsed time.
- OEM Specifications
- Original Equipment Manufacturer service requirements — the authoritative source for minimum PM intervals and procedures.
Four types of preventive maintenance schedules
The correct PM schedule type depends on how the asset deteriorates — over time, through use, or in response to measurable condition parameters. Most organizations use a combination of types across their asset fleet.
Time-based PM
Triggered by elapsed calendar timeService is performed every N days, weeks, months, or years — regardless of how much the asset was used in that period. Time-based PM is appropriate for assets where deterioration is primarily time-dependent: lubricant oxidation and breakdown, filter clogging from airborne particulates, seal drying and cracking, battery capacity degradation, and corrosion. It is the easiest PM type to implement — no usage tracking infrastructure required.
Examples
- HVAC filter replacement — every 90 days
- Generator oil change — every 6 months
- Fire extinguisher inspection — annually
- UPS battery replacement — every 3 years
Best for: Assets in continuous or standby operation where time drives deterioration
Usage-based PM
Triggered by a usage counter milestoneService is performed every N operating hours, production cycles, kilometres, or other usage unit. Usage-based PM is appropriate for assets where deterioration is proportional to operational load rather than elapsed time: machine bearings, cutting tools, conveyor components, vehicle drivetrains, and hydraulic systems. Requires a mechanism to track usage — either manual logging or an automated meter reading.
Examples
- CNC spindle bearing inspection — every 500 hours
- Vehicle oil change — every 10,000 km
- Press die inspection — every 50,000 cycles
- Hydraulic filter replacement — every 2,000 operating hours
Best for: High-duty-cycle equipment where usage determines wear, not time sitting
Condition-based PM
Triggered when a monitored parameter crosses a thresholdService is performed when sensor data or inspection findings indicate the asset is approaching a deterioration threshold — not on a fixed schedule. Condition-based PM is the most operationally efficient: assets in excellent condition are not serviced unnecessarily, while assets deteriorating faster than expected are serviced earlier. It requires monitoring infrastructure (vibration sensors, thermography, oil analysis, pressure monitoring) and is economically justified for high-criticality assets.
Examples
- Bearing replacement when vibration amplitude exceeds 8 mm/s
- Oil change when viscosity index falls below specification
- Transformer service when dissolved gas analysis shows anomalous readings
- Pump maintenance when differential pressure exceeds 15 psi threshold
Best for: High-criticality assets where monitoring infrastructure cost is justified
Calendar-based PM
Triggered on specific calendar datesService is tied to specific dates in the calendar year — seasonal shutdowns, regulatory inspection windows, manufacturer-mandated annual overhauls, or insurance-required certification dates. Calendar-based PM is often non-negotiable: regulatory inspections must occur before a specific date, seasonal maintenance must be completed before extreme weather periods, and certain certifications expire on fixed annual dates regardless of usage.
Examples
- Boiler annual inspection — before winter heating season
- Chiller seasonal commissioning — April 1 before summer cooling demand
- Annual elevator certification inspection — before licence renewal date
- Emergency lighting full-duration test — September annually
Best for: Regulatory compliance requirements and seasonal operational cycles
Practical guidance: Most organizations should start with time-based and usage-based PM for all assets — these require no sensor infrastructure and capture the majority of preventable failure scenarios. Reserve condition-based monitoring for the 10–20% of assets that are either safety-critical or where unplanned failure cost significantly exceeds the monitoring infrastructure investment.
How preventive maintenance works — the full programme cycle
A well-implemented PM programme is a continuous cycle — not a one-time setup. From PM rule configuration through work order execution to interval reset and compliance monitoring, each stage feeds the next.
PM Rule Configuration
For each asset requiring PM, one or more PM rules are created in the CMMS. Each rule specifies: service type (lubrication, filter change, calibration, inspection), interval type and duration, lead notification time (days before due to alert the team), assigned technician, work order priority, and checklist. A single asset may have multiple PM rules covering different service types at different intervals — for example, a CNC machine might have a monthly lubrication rule, a 500-hour spindle inspection rule, and an annual coolant system flush.
Outputs
Interval Monitoring
The system monitors each PM rule's next due date against the current date on a daily basis. For time-based rules, the comparison is straightforward: current date ≥ next due date. For usage-based rules, the comparison requires a current usage reading from the asset record. When a rule's interval becomes due — or within the configured lead notification window — the system prepares to generate a work order. No human needs to check schedules, remember due dates, or manually trigger the process.
Outputs
Automatic Work Order Generation
When the due date arrives, the system creates a PM work order automatically. The work order is pre-populated with the service description, asset details, assigned technician (from the PM rule), priority level, and checklist. An in-app notification is sent to the Engineering Head or Owner: 'PM work order generated for [Asset Name] — [Service Type] due.' The work order appears in the technician's queue ready for execution. No manager needs to manually create it — the programme runs itself.
Outputs
Technician Notification & Scheduling
The assigned technician receives an in-app notification identifying the asset, the service required, the priority level, and the SLA deadline. The technician reviews the work order, consults the checklist, and schedules the service for an appropriate time — coordinating with operations to minimize disruption. For planned PM services requiring downtime, the technician and production manager agree on a maintenance window in advance. This is the critical operational advantage of PM over corrective maintenance: the downtime is planned, not imposed.
Outputs
PM Execution & Checklist Completion
The technician executes the service, working through the checklist item by item. Inspection findings are recorded: condition ratings, measurements, observations. Service tasks are logged: fluids changed, filters replaced, components lubricated, adjustments made. Parts consumed are listed with quantities and costs. Time spent is logged. Before and after photographs document the service state. Any findings that require follow-up — abnormal wear, emerging faults, components approaching end-of-life — are noted in work order notes and can trigger a linked corrective work order.
Outputs
Manager Review & Approval
The technician submits the completed PM work order for manager review. The manager verifies the checklist completion, reviews findings, validates costs, and inspects the after photographs. If findings require follow-up maintenance, a corrective work order is raised at this stage. Once satisfied, the manager approves and closes the PM work order. Closure locks the cost record and triggers the downstream automations.
Outputs
Interval Reset & History Update
Work order closure triggers four automatic system actions. (1) A maintenance record is created on the asset — permanently recording the service date, technician, checklist findings, and cost. (2) The PM rule's last-serviced timestamp updates to the closure date. (3) The next PM due date recalculates based on the interval — the cycle begins again. (4) The PM work order cost is added to the asset's accumulated maintenance total and total cost of ownership. No manual schedule management is required. The programme perpetuates itself.
Outputs
Compliance Monitoring & Interval Optimization
The PM programme generates compliance and performance data that improves over time. PM compliance rate (work orders completed on time ÷ total generated) reveals execution discipline gaps. MTBF trends reveal whether PM intervals are preventing failures effectively. Findings patterns reveal whether intervals need tightening (advanced wear found consistently) or can be extended (assets found consistently in excellent condition). This feedback loop — from execution data to interval configuration — is what transforms a static PM schedule into an optimizing maintenance programme.
Outputs
How preventive maintenance operates across industries
PM applies differently depending on the operational environment, asset type, and regulatory context. Here is how mature PM programmes operate in four industries.
Operational outcomes
- 14 machines × 3 PM rules = 42 maintenance schedules — all automated, zero manual management
- Oil analysis finding detected early-stage bearing wear — corrective repair scheduled during planned window
- Zero unplanned hydraulic failures on machines with compliant PM history
Operational outcomes
- 100% PM compliance across 850 medical devices — zero manually managed schedules
- Calibration records with technician attribution ready for instant regulatory export
- HTMS accreditation audit completed in 1 day vs 3-week manual preparation
Operational outcomes
- 312 assets × multi-schedule PM = 140+ work orders per month, all auto-generated
- Pre-summer commissioning completed across all 8 buildings before peak demand
- PM finding documentation resolved contractor liability dispute
Operational outcomes
- 38 vehicles × multiple PM rules — all compliance tracked automatically via odometer logging
- PM compliance rate 94.7% — with data-driven root cause for the 5.3% gap
- No roadworthiness failures related to missed manufacturer service intervals
Key components of a preventive maintenance system
A PM system is built from interconnected components. Understanding these explains how a well-configured CMMS turns PM rules into a self-running maintenance programme.
PM Rule
The foundational entity. Each PM rule defines a service for a specific asset: service name, interval type (time/usage), interval duration, lead notification time, assigned technician, work order priority, and checklist. A single asset can have multiple PM rules covering different service types at different intervals. PM rules are the only configuration required to run the entire PM programme — everything else is automatic.
Generates: PM Work Orders, Notifications
Interval Scheduler
The engine that monitors PM rule due dates. For time-based rules, it compares the last service date plus interval against today. For usage-based rules, it compares the last service usage reading plus interval against the current asset usage value. The scheduler runs daily and generates work orders for every rule that has crossed its threshold. It is the mechanism that eliminates manual schedule management.
Runs: Daily. Checks: every PM rule for every asset
PM Work Order
Auto-generated from PM rules, PM work orders follow the same eight-status lifecycle as corrective work orders (Open → Assigned → In Progress → On Hold → Awaiting Approval → Completed → Closed). They inherit the PM rule's assigned technician, priority, and checklist. On closure, they create a maintenance record, reset the PM interval, and update TCO — the same downstream automations as corrective work orders. The work order is the execution unit of the PM programme.
On Close: maintenance record, interval reset, TCO update
PM Checklist
A structured sequence of tasks and inspection items attached to a PM rule. The checklist ensures every technician follows the same procedure regardless of experience level, and creates a documented record of exactly what was checked and what was found. Items can be inspection steps (check belt condition), measurement records (record bearing temperature), service tasks (replace filter), or function tests (verify alarm activation). Checklists are completed on the work order and preserved in the maintenance record.
Attached to: PM Rule. Completed on: PM Work Order
Maintenance History
Every completed PM work order becomes a permanent maintenance record on the asset. The history shows every PM service performed: date, service type, technician, checklist findings, and cost. This accumulated history is the primary data source for MTBF calculation, interval optimization, and compliance evidence. Regulators, insurers, and auditors all draw on PM maintenance history as evidence that assets have been properly maintained.
Created by: Work order closure. Used for: MTBF, compliance, interval tuning
Asset Criticality Classification
Each asset is assigned a criticality level — Critical, High, Medium, Low — based on the operational and safety consequences of failure. Criticality modifies PM behaviour: Critical assets may receive shorter intervals, faster escalation on missed PM, tighter SLA windows for associated work orders, and higher manager visibility. Criticality classification is the mechanism that ensures the PM programme allocates the most attention to the assets where the cost of failure is highest.
Modifies: PM interval tightness, escalation speed, SLA windows
Lead Notification & Overdue Escalation
Two notification events govern PM execution. Lead notifications fire N days before a PM is due — giving the maintenance team time to prepare parts, schedule downtime windows, and coordinate with operations. Overdue escalation fires when a PM work order is not started within a threshold period after generation — notifying the Engineering Head or Owner that a scheduled PM is being neglected. These notifications close the loop between automatic generation and actual execution.
Lead: configurable days before due. Escalation: on overdue trigger
PM Cost Tracking & TCO Integration
Every PM work order carries a cost log — labour time, materials consumed, and external service fees. On closure, the total PM cost is transferred to the asset's accumulated maintenance total. Over time, PM costs are separated from corrective costs in the asset's TCO breakdown — enabling PM programme cost analysis: what does it cost per asset per year to maintain proactively, and how does that compare to the assets with high corrective maintenance frequency?
Feeds: Asset TCO, PM programme cost analysis
Preventive maintenance automation and system intelligence
The operational value of a PM system comes from what it does automatically — not from what managers remember to do manually. These are the automation behaviours that transform a PM schedule into a self-running maintenance programme.
Automatic work order generation
PM work orders generate automatically when intervals become due — no human trigger required. The scheduler runs daily, checking every PM rule across every asset. When a rule crosses its threshold, a work order is created, assigned, and the team is notified. PM scheduling stops being a management dependency.
Lead-time advance notification
Before a PM due date arrives, a configurable lead notification fires — typically 7–14 days before. This gives technicians time to pre-order parts, schedule asset downtime windows with operations, and ensure the relevant technician is not on leave. Lead notifications prevent the 'PM generated but not actionable' scenario.
Overdue PM escalation
When a PM work order passes a configurable overdue threshold without being started, an escalation notification fires to the Engineering Head or Manager. This surfaces neglected PM before it becomes a compliance gap. Critical assets can be configured to escalate faster — ensuring life-safety PM is never silently overdue.
Interval auto-reset on close
Closing a PM work order automatically updates the PM rule's last-serviced timestamp and recalculates the next due date. The next PM work order will generate exactly on schedule without any manual configuration change. The maintenance cycle perpetuates itself indefinitely.
Linked CM work order from PM findings
When a technician records an abnormal finding during PM execution — worn component, emerging fault, calibration out of range — a linked corrective maintenance work order can be raised directly from the PM work order. The parent-child link preserves the relationship between the PM finding and the subsequent corrective repair.
TCO auto-accumulation
Every closed PM work order adds its cost to the asset's accumulated maintenance total. PM costs are tracked separately from corrective costs in the TCO breakdown — enabling cost comparisons between proactive and reactive maintenance spend per asset over time.
Maintenance record auto-creation
Closing a PM work order automatically creates a permanent maintenance record on the asset — capturing service date, technician, checklist findings, and cost. The PM history grows continuously without any manual data entry. Compliance evidence accumulates automatically.
PM compliance rate tracking
The system tracks PM compliance rate continuously — the ratio of work orders completed on time vs generated. Low compliance rates surface in the dashboard and can be filtered by asset category, facility, or technician — making the root cause of non-compliance visible and actionable.
Immutable PM audit trail
Every PM work order action — status transitions, technician notes, cost entries, photo uploads, checklist completions — is recorded in the immutable audit event log. The PM audit trail is always complete, always timestamped, and cannot be modified. Regulators and auditors receive the definitive record of every PM event.
Preventive maintenance best practices
The difference between a PM programme that works and one that exists on paper is operational discipline — in how rules are configured, checklists are designed, compliance is enforced, and intervals are optimized.
Programme design
Start with manufacturer OEM specifications as your baseline
Every asset's PM programme should be grounded in manufacturer-specified service requirements. OEM specifications represent the minimum intervals validated for average operating conditions. Using shorter intervals is always safe; using longer intervals without operational justification risks warranty violation and premature failure.
Create PM rules for every asset with a service schedule — not just critical ones
Operations teams often configure PM rules only for high-criticality assets and manage lower-priority assets informally. This creates systematic non-compliance for the 'low-priority' assets — many of which are more expensive to replace or repair than the high-priority ones if maintained poorly over time.
Use asset criticality to tighten intervals for safety-critical assets
Standard PM intervals are designed for average operational conditions and average consequences of failure. For assets where failure creates safety risk, regulatory violation, or disproportionate production impact, apply a criticality multiplier — shortening the interval by 20–30% to create an additional safety margin.
Checklist design
Make checklists specific enough for any technician to execute consistently
'Check belt condition' is not a checklist item — 'Inspect drive belt for cracking, glazing, or excessive wear — acceptable if no surface cracking visible and belt deflection within 5mm under 10N load' is. Specific acceptance criteria are what make checklists produce consistent outcomes regardless of who performs the PM.
Include measurement recording items — not just pass/fail inspection items
Measurements recorded at each PM visit — bearing temperatures, vibration amplitudes, fluid levels, pressure readings, clearances — create a condition trending dataset. A bearing temperature that was 42°C at the last PM and is now 56°C is a leading indicator of failure, invisible in a pass/fail checklist but obvious in a measurement trend.
Always include post-service functional verification
The last checklist item on every PM should be a functional test: run the equipment for a defined period, verify no abnormal noise, confirm operating parameters are within specification. PM that ends before functional verification has not confirmed that the service achieved its goal — the next failure may have occurred during the PM itself.
Execution discipline
Never skip a PM and log it as complete
Logging a PM as complete when it was not performed — to hit a compliance metric or avoid a notification — destroys the integrity of the PM history. The maintenance record created by a 'false close' is evidence of a service that did not happen. When the asset subsequently fails and the history is reviewed, the fraudulent record is both operationally useless and a liability.
Log all materials consumed on PM work orders
PM cost data is only useful if it captures actual material consumption, not just labour time. Technicians who skip materials logging produce systematically understated PM cost data — making TCO analysis unreliable and misrepresenting the true cost of the PM programme.
Raise a CM work order immediately for findings that exceed the PM scope
A PM visit that finds a failing component beyond the scope of the scheduled service should not attempt to fix it informally. A linked corrective work order should be raised from the PM work order — assigning the remediation to the appropriate resource, with its own SLA deadline, cost log, and audit trail.
Interval optimization
Review PM findings data quarterly to identify interval misalignment
If PM checklists consistently show assets in perfect condition with no findings, the interval may be too short — you are spending PM costs without finding any deterioration to address. If checklists consistently show advanced deterioration, the interval is too long — the PM is arriving after significant degradation has already occurred.
Track MTBF per asset category to validate PM effectiveness
The single most reliable indicator of PM programme effectiveness is whether MTBF is improving over time. If assets are failing at the same frequency before and after implementing a PM programme, the programme design needs review — either intervals are too long, checklists are missing the deterioration mechanism, or execution compliance is too low.
Do not extend intervals without operational data justification
Extending PM intervals to reduce maintenance cost is a legitimate optimization — but only when supported by consistent findings data showing the asset is healthy at the current interval. Extending intervals to save budget without data justification is deferred maintenance, not optimization.
Preventive maintenance metrics and KPIs
A PM programme that is not measured is not managed. These KPIs provide the operational and financial evidence that validates PM investment and guides programme improvement.
PM Compliance Rate
PercentagePM work orders completed within their scheduled window as a percentage of total PM work orders generated. The primary governance metric for a PM programme. Low compliance means the programme exists on paper but not in practice — asset intervals are effectively longer than configured.
Target: ≥ 95%
Mean Time Between Failures (MTBF)
Days / HoursAverage operating time between corrective maintenance events on an asset or asset category. The primary effectiveness metric for a PM programme — a well-run PM programme should increase MTBF over time. Declining MTBF despite PM compliance indicates an interval or checklist problem.
Target: year-on-year improvement
PM-to-CM Ratio
RatioNumber of preventive work orders vs corrective work orders in a period. Indicates maintenance culture maturity. A ratio below 1:3 (one PM for every three CMs) signals predominantly reactive operations. World-class operations target above 2:1 (twice as many planned PM events as reactive repairs).
Target: ≥ 1:1 (proactive parity)
PM Overdue Rate
PercentagePercentage of PM work orders that are overdue — generated but not completed within their window. Segmented by asset category, facility, and technician. PM overdue rate reveals execution capacity gaps and priority conflicts that compliance rate alone may obscure.
Target: < 5% at any given time
Average PM Cost Per Asset
Currency / PeriodAnnual PM spend per asset, segmented by category and facility. Enables benchmarking across similar assets and facilities. Assets with PM costs significantly above category average may have over-specified intervals; assets with costs below average may be under-maintained.
Benchmark: compare within category
Asset Availability Rate
PercentagePercentage of scheduled operating time the asset is available for use. PM downtime is planned and controllable; corrective downtime is not. High availability rate reflects a programme that is controlling downtime through planning rather than experiencing it through failure.
Target varies by asset criticality
First-Time Fix Rate on CM Following PM
PercentageWhen a PM finding generates a corrective work order, the percentage of those CMs resolved in the first attempt. Low rate indicates that PM findings are not generating sufficiently specific corrective work orders — the fault is found but not properly diagnosed, leading to repeat repair attempts.
Target: ≥ 85%
PM Cost vs CM Cost Ratio
RatioAnnual PM spend vs annual corrective maintenance spend for an asset or category. The financial case for PM is strongest when CM costs significantly exceed PM costs for the same asset. This ratio quantifies the ROI of the PM programme and drives capital allocation decisions.
Target: PM cost < CM cost prevented
Findings Rate
PercentagePercentage of PM work orders that record at least one abnormal finding or corrective follow-up recommendation. Too high (above 30%) may indicate intervals are too long; too low (below 5%) may indicate intervals are too short or checklists are not specific enough to detect real deterioration.
Target: 8–20% for time-based PM
PM programme maturity benchmark
Reactive (Level 1)
PM:CM ratio < 1:4 · No formal PM rules · Maintenance schedules in people's heads · No compliance tracking
Structured (Level 2)
PM:CM ratio ~1:2 · PM rules configured · Compliance 70–85% · MTBF tracked but improving slowly
Optimized (Level 3)
PM:CM ratio ≥ 2:1 · Compliance > 95% · MTBF improving year-on-year · Intervals data-driven
Reactive vs preventive vs predictive maintenance
The three maintenance strategies represent different positions on the proactivity–cost spectrum. Most organizations should operate with a preventive foundation and selectively layer predictive on high-criticality assets.
| Dimension | Reactive Maintenance | Preventive Maintenance | Predictive Maintenance |
|---|---|---|---|
| When service occurs | After failure — unplanned | On schedule — before failure | When condition monitoring indicates threshold approach |
| Downtime type | Unplanned — maximum disruption | Planned — scheduled maintenance window | Minimal — service only when needed |
| Maintenance cost | High — emergency rates, expedited parts | Moderate — planned service with standard parts | Lowest for parts, but high monitoring infrastructure cost |
| Infrastructure required | None | CMMS with PM rule configuration | Sensors, IoT infrastructure, data analytics platform |
| Asset useful life | Shortened — failures cause secondary damage | Extended — deterioration caught before failure | Maximized — service precisely when needed |
| Risk of unnecessary service | None — only serviced when broken | Some — healthy assets serviced on schedule | Minimal — condition-triggered service only |
| Compliance evidence | No evidence — failures are not scheduled | Full evidence — every PM creates a dated service record | Condition monitoring data — complex to present for audit |
| Implementation complexity | Lowest — no configuration required | Low — PM rules in a CMMS, no hardware | High — sensor installation, calibration, analytics setup |
| Best suited for | Non-critical, easily replaced, low downtime cost | Most assets — optimal cost-benefit across all criticality levels | High-criticality assets with significant sensor ROI potential |
Practical recommendation for most organizations: Build a complete preventive maintenance foundation first — configure PM rules for every asset using manufacturer-specified intervals, run the programme for 12 months, and measure MTBF and PM compliance. Once the preventive foundation is mature and compliance is above 90%, evaluate condition monitoring investment for the 10–20% of assets where unplanned failure cost is highest. Predictive maintenance on a reactive maintenance foundation produces analytics data with no action infrastructure to respond to it.
Frequently asked questions
Detailed answers to the questions maintenance managers, operations directors, and facilities teams ask most frequently about preventive maintenance.
What is preventive maintenance?
Preventive maintenance (PM) is the practice of performing planned, scheduled maintenance on physical assets before failure occurs — with the goal of preventing breakdowns, extending asset useful life, and reducing unplanned downtime. Unlike corrective maintenance, which responds to failures after they happen, preventive maintenance is proactive: tasks are performed at defined intervals (time, usage, or condition-based) regardless of whether the asset shows signs of failure. A well-designed PM programme replaces unpredictable reactive maintenance with predictable, budgeted, planned maintenance work.
What is the difference between preventive and corrective maintenance?
Preventive maintenance (PM) is planned and proactive — performed on a schedule before failure occurs. Corrective maintenance (CM) is reactive — performed after a failure has been detected or reported. The operational distinction is significant: PM work orders are predictable, scheduled, and budgeted in advance; CM work orders are unplanned, disruptive, and typically more expensive. Studies consistently show that emergency corrective repairs cost 3–5 times more than equivalent planned preventive service, because they involve emergency labour rates, expedited parts procurement, and indirect costs of operational downtime. The goal of a PM programme is to reduce CM frequency by catching deterioration before it becomes failure.
What are the main types of preventive maintenance schedules?
There are four primary PM schedule types. Time-based PM is triggered by elapsed calendar time — every 30 days, 6 months, or annually — regardless of asset usage. It is the simplest to implement and appropriate for assets with time-dependent deterioration (e.g., lubricant breakdown, filter accumulation, seal degradation). Usage-based PM is triggered by a usage counter — every 500 operating hours, every 10,000 km, every 1,000 production cycles. It is appropriate for assets where wear is proportional to usage rather than time. Condition-based PM is triggered when a monitored parameter crosses a threshold — vibration amplitude, temperature, oil viscosity, or pressure differential. It requires sensor infrastructure but produces the most efficient service intervals. Calendar-based PM is fixed to specific calendar dates — quarterly, semi-annual, annual — often driven by manufacturer specifications or regulatory requirements.
How does preventive maintenance software generate work orders automatically?
In a PM software system like UniAsset, PM rules are configured for each asset. Each rule defines the service type, interval (time or usage), lead time for notification, assigned technician, and work order priority. A background scheduler runs daily and compares each PM rule's next due date against the current date. When a rule's interval has elapsed, the scheduler automatically creates a PM work order — linked to the rule, the asset, and the pre-configured technician — and sends an in-app notification to the Engineering Head. No manual trigger is required. The technician executes the work and closes the work order, which automatically resets the PM rule's interval and calculates the next due date.
How often should preventive maintenance be performed?
PM intervals should be based on manufacturer recommendations first, then adjusted based on operational data. Manufacturer service manuals specify minimum service intervals designed for average operating conditions. In high-duty-cycle environments — heavy industrial use, continuous operation, harsh conditions — intervals should be shortened. Operational data from a running CMMS provides the most reliable interval optimization: if an asset consistently shows no degradation at 90-day intervals but early-stage degradation at 120-day intervals, 90 days is the correct interval. The key principle is that PM intervals exist to prevent failure — if maintenance is consistently finding the asset in perfect condition, the interval may be too short; if maintenance is consistently finding advanced wear, the interval is too long.
What is PM compliance rate and why does it matter?
PM compliance rate is the percentage of scheduled preventive maintenance work orders that are completed within their designated service window. It is calculated as: (PM work orders completed on time ÷ total PM work orders generated) × 100. Target is above 95%. PM compliance matters because an asset whose PM is consistently performed late is receiving service at longer-than-designed intervals — meaning deterioration may progress past the designed detection point before maintenance occurs. Low PM compliance (below 80%) is the most common preventable cause of premature asset failure in organizations that have a PM programme but execute it inconsistently.
What is the difference between preventive and predictive maintenance?
Preventive maintenance is interval-based — service is performed at fixed schedules regardless of actual asset condition. Predictive maintenance is condition-based — service is performed only when monitoring data indicates the asset is actually approaching a failure threshold. Predictive maintenance is more efficient (no unnecessary service on healthy assets) but requires condition monitoring infrastructure — vibration sensors, thermography, oil analysis, or IoT telemetry. For most organizations, a pragmatic approach is a hybrid: time-based and usage-based PM as the foundation (reliable, inexpensive, no sensor infrastructure needed), with condition monitoring layered on for high-criticality assets where the cost of monitoring is justified by the cost of unplanned failure.
What should a preventive maintenance checklist include?
A well-designed PM checklist should include: (1) Safety steps — lockout/tagout procedures, PPE requirements, isolation verification before work begins; (2) Inspection items — specific components to visually inspect, with acceptance criteria (e.g., 'inspect drive belt — acceptable if no cracking or glazing visible'); (3) Measurement tasks — readings to record (pressure, temperature, vibration amplitude, clearances) with pass/fail tolerances; (4) Service tasks — fluid changes, filter replacements, lubrication points with specified quantities and grades; (5) Functional tests — post-service operational verification (e.g., 'run unit for 5 minutes and confirm no abnormal noise'); (6) Findings documentation — space for the technician to note any observations that require follow-up. Checklists should be specific enough that two different technicians performing the same PM would take the same actions.
How does preventive maintenance reduce equipment downtime?
Preventive maintenance reduces downtime through three mechanisms. First, it prevents failures: by replacing wear parts and servicing critical components before they deteriorate to failure state, PM eliminates the unplanned downtime events that corrective failures cause. Second, it allows downtime to be planned: when a PM service requires taking an asset offline, that downtime can be scheduled for a low-impact period (shift changeovers, weekends, planned shutdowns) rather than occurring unexpectedly mid-production. Third, it improves failure detection: PM checklists include condition assessments — if a technician notes abnormal wear during a PM visit, a targeted corrective repair can be scheduled during the next maintenance window before the asset fails completely. The combination of failure prevention, planned downtime windows, and early fault detection is what drives the 30–50% downtime reduction typically observed when organizations transition from reactive to preventive maintenance programmes.
How do PM schedules integrate with asset lifecycle management?
PM schedules are the active maintenance phase of the asset lifecycle. In an integrated asset lifecycle management system, PM rules are configured on individual assets at the time of registration — with intervals derived from manufacturer specifications and operational requirements. Every PM work order that closes creates a permanent maintenance record on the asset and adds its cost to the asset's total cost of ownership. The PM completion history is visible in the asset's service timeline, providing the maintenance frequency data needed for MTBF analysis, interval optimization, and repair-versus-replace decisions. PM compliance rate per asset also feeds into the asset condition profile — assets with consistently missed PM are flagged as higher risk for unplanned failure.
What industries depend most heavily on preventive maintenance?
All industries that operate physical assets benefit from PM, but the operational stakes are highest in manufacturing (production line downtime translates directly to lost revenue — a single unplanned stoppage can cost more than an entire year of PM service for the failed machine), healthcare (medical device failures can directly harm patients — regulatory requirements mandate PM compliance for most medical equipment), facilities management (HVAC, elevator, fire suppression, and life safety systems require PM compliance to meet regulatory and insurance requirements), and fleet operations (vehicle PM schedules determine roadworthiness compliance, insurance validity, and driver safety). In regulated industries like aviation, nuclear, and food processing, PM records are legally required evidence of compliance — making PM documentation as important as the maintenance itself.
How do you build a preventive maintenance programme from scratch?
Building a PM programme involves six steps. (1) Asset inventory: create a complete register of all physical assets requiring PM, including serial numbers, installation dates, and manufacturer details. (2) Gather manufacturer PM requirements: extract service schedules from equipment manuals — these define the minimum PM intervals you are obligated to follow to maintain warranty validity and manufacturer recommendations. (3) Prioritize by criticality: classify assets by operational criticality — Critical, High, Medium, Low — and design tighter PM intervals and faster escalation for Critical assets. (4) Design PM rules: for each asset, create PM rules covering all required service types, configuring interval, assigned technician, checklist, and notification lead time. (5) Enter into a CMMS: configure all PM rules in a maintenance management system so work orders generate automatically. (6) Monitor compliance: track PM compliance rate monthly and adjust intervals based on findings data — tightening intervals where technicians are finding early-stage deterioration, extending intervals where assets are consistently found in perfect condition.
What is the cost impact of a good preventive maintenance programme?
Organizations with mature preventive maintenance programmes consistently report: 25–35% reduction in unplanned downtime (fewer corrective emergencies); 10–30% reduction in overall maintenance cost (PM services are cheaper than emergency repairs); 15–25% increase in asset useful life (properly maintained assets reach their designed end-of-life rather than failing prematurely); and 5–15% reduction in energy consumption (well-maintained equipment operates more efficiently). The most financially significant impact is on high-criticality production assets: the cost of a single unplanned failure event — including emergency repair premium, production loss, and restart costs — can exceed the total annual PM budget for that asset category. The ROI case for preventive maintenance is strongest where corrective failures carry the highest indirect cost.
Get started
Build your preventive maintenance programme in UniAsset — free.
Configure PM rules, automate work order generation, track compliance, and build a complete asset maintenance history — in one system of record.
Used by manufacturing, healthcare, facilities, and fleet operations teams. No credit card required.