Preventive maintenance is the systematic practice of servicing assets before they fail. It is the foundation of every reliability program and the single practice with the largest cost-reduction effect on maintenance operations. The DOE Federal Energy Management Program reports that a disciplined preventive program reduces unplanned breakdowns by 70 to 75 percent and extends asset life by 20 to 40 percent compared with reactive-only operations.
A CMMS runs preventive work systematically across the full asset base, without the compliance drift that spreadsheet-driven programs suffer. PM schedules generate work orders automatically, technicians execute them with documented procedures, and the CMMS tracks compliance so program health is visible at all times.
Asset-Specific PM Plans
Every asset has a PM plan appropriate to its type, criticality, and usage pattern. A CMMS holds a library of templates and adapts them per asset.
A good PM plan includes:
- Tasks: the specific inspections, lubrications, adjustments, or replacements the PM comprises
- Frequency: calendar-based (every 30, 90, 180, or 365 days), meter-based (every 500 hours, every 10,000 miles), or condition-based (triggered by vibration, temperature, or other sensor thresholds)
- Required parts: the consumables that accompany each PM execution
- Estimated duration: for scheduling and capacity planning
- Required skills: for technician assignment
- Procedure: step-by-step instructions accessible in the field
A CMMS that holds PM templates as shared resources lets an organization apply the same discipline across hundreds or thousands of similar assets. One change to a template propagates to every asset of that type, which is how a small reliability team can maintain program integrity across a large asset base.
Automated Scheduling
The CMMS generates PM work orders automatically on their trigger (calendar, meter, or condition). Technicians see the work on their mobile devices without planners having to chase schedules.
The scheduling logic handles three cases:
Fixed-interval PMs: a 30-day HVAC filter inspection generates a work order every 30 days regardless of runtime. Simple to implement, appropriate for regulatory and safety PMs that must happen on calendar.
Meter-based PMs: a “500-hour bearing lubrication” generates a work order when the asset’s runtime meter crosses the threshold. Requires meter readings (manual, IoT, or integrated from control systems). Produces tighter alignment between maintenance and actual use.
Condition-based PMs: a “replace filter when differential pressure exceeds 2.0 inches” generates a work order when sensor data crosses the threshold. Most efficient when instrumentation is available and the condition signal is reliable.
Most operations run a mix of all three, with calendar-based PMs on regulatory and simple tasks, meter-based PMs on duty-cycle-sensitive equipment, and condition-based PMs on the most critical assets. A CMMS that handles all three without forcing operators to use only one is the only design that scales.
Completion Tracking
Schedule compliance (the percentage of PMs completed on time) is the single most predictive metric for program health. A CMMS produces it automatically; leadership sees the trend.
Programs that sustain 90 percent or higher PM compliance produce the breakdown-reduction and life-extension benchmarks cited above. Programs that drift below 70 percent do not, and the relationship is consistent enough across industries that compliance rate is often the first metric executive reviews look at.
A CMMS dashboard that shows PM compliance by team, by site, and by asset class supports targeted corrective action: a team or site with falling compliance usually has a specific workable cause (staff change, equipment downtime, priority conflict) that can be addressed if it is visible early.
Continuous Tuning
PM intervals that are too aggressive waste labor. Intervals that are too relaxed let failures through. A CMMS tracks failure data against PM cadence and supports the ongoing tuning that reliability engineering does.
The tuning discipline:
- Review failure data quarterly against the PM schedule
- For assets with failures between PMs: tighten interval, change procedure, or add condition monitoring
- For assets with no failures and good condition at PM time: consider loosening interval
- Document the change and track the outcome over the next two to four PM cycles
This iterative refinement is what separates mature programs from new ones. A CMMS that retains the full history (PM actions, failures, condition readings, parts consumption) makes the analysis tractable. Without that history, the tuning has to rely on general industry guidance, which is always less accurate than data from the specific operation.
The 70-80 Percent Rule
Well-run programs typically run 70 to 80 percent of maintenance hours on planned work (preventive, planned corrective, improvement projects), with less than 25 percent truly reactive.
Most organizations start well below this ratio. First-year gains usually come from converting obvious reactive work to preventive: a pump that has failed three times in six months is a candidate for a tighter PM schedule, not a fourth reactive repair. Second-year gains come from condition monitoring and root-cause work that converts less-obvious reactive patterns into preventive ones. By year three, mature programs typically stabilize in the 70 to 80 percent planned range.
The economic effect is substantial. Planned work is 3 to 5 times cheaper per labor hour than reactive work (no overtime, no emergency parts expediting, no collateral damage, better first-time fix rates). Moving 20 percentage points of maintenance hours from reactive to planned typically reduces total maintenance cost by 15 to 25 percent.
Industry-Specific Considerations
Retail Assets
Retail asset PM covers HVAC, refrigeration, lighting, POS, and building systems across store networks. A CMMS applies consistent PM across all stores and surfaces the outliers where tuning would improve cost or reliability. Store-format differences (urban compact versus suburban big-box) drive legitimate differences in PM cadence; a CMMS that handles variant templates per format supports this without losing the benefit of network-wide standardization.
Food and Beverage Assets
Food and beverage assets carry production-critical PM alongside sanitation requirements. A CMMS coordinates both, scheduling maintenance PM into CIP windows and tracking sanitation-cycle compliance for FDA and USDA records. The two programs share data in a CMMS (the same asset record, the same personnel, the same compliance documentation) instead of running as parallel systems.
Construction Assets
Construction assets move between projects and experience variable operating intensity. A CMMS tracks hours and cycles per asset, scheduling PM against actual use rather than calendar alone. Asset-location tracking across projects is itself a value driver: without it, PM can lapse because the asset is assumed to be at a different site.
Hospitality Assets
Hospitality asset PM has to work around guest occupancy. A CMMS integrated with PMS occupancy data schedules PM into unoccupied rooms and during low-occupancy periods, which is the only way to maintain guest-facing assets without generating complaints.
Healthcare Assets
Healthcare asset PM combines equipment reliability with regulatory compliance (Joint Commission, CMS, state health departments). A CMMS tracks both dimensions against the same record, which is the only scalable path to survey-ready PM documentation across hundreds of regulated assets.
Frequently Asked Questions
How do we know PM frequency is right?
Compare failure rate with and without PM. If failures happen despite PM, the interval may need shortening or the procedure may need changes. If failures are rare and equipment condition is good at PM time, the interval may be too aggressive and can be loosened.
What percentage of maintenance should be preventive?
Well-run programs run 70 to 80 percent of hours on planned preventive and proactive work, with less than 25 percent truly reactive. Most organizations start lower and improve gradually over 18 to 36 months of disciplined program work.
How does a CMMS handle PM for very old equipment?
Through asset-specific templates based on age, usage, and observed condition. Older equipment often needs more frequent PM; a CMMS supports the customization without forcing a team to rebuild standard templates from scratch.
Can PM actually over-service equipment?
Yes. Excessive intervention on stable assets can introduce defects (contamination, incorrect reassembly, damage during disassembly) that would not have occurred with less-frequent service. The tuning discipline above avoids this by letting failure data and condition data inform interval decisions rather than applying uniform aggressive cadence across the asset base.
Ready to apply this to your operation? Book a Task360 demo.
