PM Optimization Case Study That Restored Control
A maintenance director had 1,800 preventive maintenance work orders open across six facilities. The dashboard suggested a busy, compliant program. The field reality was different: technicians were closing work orders without useful completion notes, critical assets had generic PM tasks, and emergency requests kept displacing scheduled work. This PM optimization case study shows why a high volume of closed PMs does not automatically mean a maintenance program is under control.
The example is a composite based on common operational conditions in multi-site maintenance environments. The details vary by industry, but the failure pattern is consistent: a CMMS becomes a ticketing archive when the work order process, asset data, and management routines do not support disciplined execution.
The PM Optimization Case Study: The Starting Point
The organization operated a distributed portfolio of manufacturing and warehouse facilities. Its CMMS had been in place for years, and every major asset category had some form of preventive maintenance schedule. Leadership believed the program was mature because monthly PM completion regularly appeared above 90%.
That number did not hold up under review. More than 30% of completed PMs had no labor time recorded. Nearly half used the same two-word completion note: “completed” or “checked.” Several high-priority assets had duplicate records, while other assets were missing serial numbers, locations, or parent-child relationships. Technicians could not reliably tell which work order applied to which physical unit.
The maintenance team was also managing a growing reactive workload. Emergency work represented 22% of total labor hours, and the weekly schedule was routinely abandoned by Wednesday. Planners were spending their time answering status questions, correcting work orders, and manually assigning technicians rather than preparing future work.
The core issue was not a lack of effort or a lack of software features. The operation had no consistent definition of a quality PM, no practical standard for documenting work, and no governance process to identify whether scheduled maintenance was reducing failure risk.
Why the Existing PM Program Produced Activity, Not Reliability
The first diagnostic step was separating compliance from effectiveness. A PM can be completed on time and still fail to protect an asset. If a task says “inspect unit” without defining the condition to inspect, the acceptable operating range, or the required response, each technician interprets it differently.
The team found that many PM templates had been copied from vendor manuals or legacy spreadsheets with little adaptation for the operating environment. Some included tasks that were too broad to execute efficiently. Others prescribed frequent inspections on low-risk equipment while critical failure modes received limited attention. The result was predictable: technicians rushed through low-value work, while chronic asset issues remained hidden in general notes and verbal handoffs.
Scheduling logic made the problem worse. PMs were generated in large monthly batches and assigned based on availability rather than asset criticality, route efficiency, or parts readiness. A technician might receive work orders across multiple buildings with no clear priority sequence. When urgent requests arrived, the planned work was deferred, often repeatedly.
Leadership reporting was equally weak. The maintenance manager could see completion rates and open work order counts, but not schedule compliance by criticality, PM exception reasons, repeat failures, wrench time, or the percentage of PMs producing corrective work. Without those measures, leadership had no way to distinguish an overloaded team from an undisciplined process.
Rebuilding the Program Around Execution
The optimization work began with a focused assessment rather than a full CMMS redesign. The goal was to establish control over the assets and workflows that created the most operational risk.
The team first ranked assets using a practical criticality model. Safety exposure, production impact, customer impact, repair cost, redundancy, and likelihood of failure were considered. This was not an academic scoring exercise. The maintenance manager, operations leaders, and experienced technicians worked through the equipment that could actually disrupt operations.
From there, the organization cleaned and standardized records for the highest-criticality assets. Duplicate records were merged, asset names were normalized, locations were verified, and parent-child structures were corrected where they affected troubleshooting or maintenance planning. The team did not attempt to perfect every record at once. That would have delayed improvement. It prioritized the data needed to schedule, execute, and analyze critical maintenance work accurately.
Standardizing PM Job Plans
Each critical PM template was reviewed against likely failure modes and the conditions technicians could realistically observe in the field. Vague language was removed. Tasks were rewritten with clear instructions, expected conditions, safety requirements, estimated labor, and response paths when an issue was found.
For example, “inspect belts” became a defined sequence: inspect for cracking, glazing, fraying, alignment, and tension; document observed condition; create a corrective work order when limits are exceeded. Where useful, the job plan included meter readings and required parts. The objective was not to turn technicians into data-entry clerks. It was to capture the minimum information required for accountable maintenance decisions.
The team also separated PM work from corrective work. A technician could identify and document a defect during a PM, but the repair was routed into a linked corrective work order with its own priority, estimate, parts requirement, and scheduling decision. This change gave management visibility into the defects PM work was uncovering and stopped large repairs from disappearing inside a closed inspection ticket.
Building a Weekly Scheduling Rhythm
The next change was operational: PM work stopped being released in a monthly flood. The planner created a rolling weekly schedule, protected time for high-criticality maintenance, and reviewed parts availability before work was assigned. Dispatch and operations were included in the review when asset downtime or site access required coordination.
The schedule was not treated as rigid. Emergencies happen, particularly in facilities with aging equipment or demanding production requirements. But every break from the schedule required a reason code: emergency response, operational deferral, missing parts, labor constraint, or access issue. Those reasons created a fact base for deciding whether the program needed more capacity, better planning, or stronger cross-functional coordination.
Supervisors began holding short daily reviews focused on execution barriers rather than blame. Which critical PMs were due? What work was blocked? What defects needed action? Which jobs required escalation? This routine reduced the reliance on informal conversations and gave technicians a clearer path for raising issues before they became failures.
What Changed After 90 Days
Within the first three months, the organization reduced its open PM backlog by 41% while improving the quality of completion documentation. The PM completion rate did not increase dramatically at first. It moved from 91% to 94%. That modest change mattered because the number now reflected work performed to a defined standard, not simply work orders closed before month-end.
Emergency labor fell from 22% to 15% of total maintenance hours. That was not solely the result of better PMs. The improvement also came from more reliable scheduling, faster follow-up on defects, and fewer technician hours lost searching for asset information or clarifying work scope.
Most importantly, leadership gained usable performance visibility. The weekly review tracked schedule compliance for critical assets, PM completion quality, overdue work by reason, corrective work generated from PMs, repeat failures, and emergency labor. These measures exposed where the process still needed attention. One site, for example, had strong completion rates but recurring motor failures. That pattern led to a targeted review of alignment procedures, spare motor specifications, and installation practices.
There were trade-offs. More detailed PMs initially required more planning time and slightly longer technician visits. A smaller number of low-value tasks were retired, which can feel uncomfortable to teams accustomed to measuring effort by task volume. The organization accepted those changes because its maintenance program was becoming more risk-based, defensible, and manageable.
The Operating Lesson for Maintenance Leaders
A PM program does not improve because a CMMS sends more reminders. It improves when the system reflects how work must be planned, executed, documented, reviewed, and corrected in the real operating environment.
Start by asking a direct question: if your most critical asset fails tomorrow, can your team prove that the right PM was performed, on schedule, to a clear standard, with defects routed to action? If the answer is uncertain, the priority is not adding more tasks. It is restoring control over the process that turns scheduled maintenance into reliable execution.
A focused PM health check can identify the few workflow, data, and reporting changes that will produce the fastest operational gains. The right starting point is the work your technicians perform every day, because that is where system adoption, uptime, and accountability either come together or break down.
