Maintenance Compliance Rate

Goal of the analysis:

Measure how reliably preventive and planned maintenance is executed as scheduled and on time, and use insights to reduce unplanned downtime, raise availability, and optimize maintenance spend. Maintenance Compliance Rate covers on‑time completion of preventive maintenance (PM) tasks, weekly schedule adherence, and the balance of planned vs reactive work. Executives use it to stabilize throughput without capex, cut breakdowns and overtime, size planner/scheduler and spares programs, synchronize maintenance with production windows, and ensure that PM effort is value‑adding (RCM‑aligned) rather than administrative.

Data required:

• Work management (CMMS/EAM):
  • Work orders: type (PM/condition-based/corrective/emergency), priority, asset, scheduled start/finish, planned labor hours, actual start/finish, actual labor hours, status codes (completed, deferred, cancelled), deferral reasons/approvals.
  • PM master data: frequencies/intervals, tolerance windows (e.g., ±10%), task lists, crafts/trades, estimated durations.
  • Backlog and age by asset/craft; planner/scheduler assignments.
• Asset and criticality context:
  • Asset hierarchy (site/line/work center/asset), criticality ranking (A/B/C), failure history, MTBF/MTTR, constraint assets.
• Production and downtime (MES/SCADA/OEE):
  • Planned production schedule, maintenance windows, changeovers; downtime logs by cause to link compliance to unplanned downtime.
• Labor and resource availability (LMS/HR):
  • Technician rosters, skills/certifications, overtime, wrench time studies, contractor usage.
• Spares and materials (Storeroom/ERP):
  • Parts availability, kit completeness, lead times, reservations against PMs, stockouts.
• Policies and normalization:
  • Definition of “on‑time” (within window), schedule lock period (freeze), emergency work definitions, holiday/shift calendars, time zone alignment.

Detailed step-by-step instruction on how to conduct the analysis:

1. Define metrics and scope.
   • PM Compliance (%) = PM work orders completed within the defined tolerance window ÷ PM work orders due in the period × 100.
   • Weekly Schedule Compliance (%) = Work orders completed from the frozen weekly schedule ÷ Work orders scheduled × 100.
   • Overdue PMs = count and age (days) of PMs past due; Deferral Rate (%) = PMs deferred with approval ÷ PMs due.
   • Planned Work Ratio (%) = Planned (PM + planned corrective) labor hours ÷ Total maintenance labor hours.
   • Emergency Work % = Emergency labor hours ÷ Total; Wrench Time (%) = Direct tool time ÷ Paid maintenance hours (optional overlay).
2. Extract and prepare data.
   • Pull 12–13 weeks of CMMS work orders and PM masters; include planned vs actual dates/times, hours, status, and reasons.
   • Bring in asset criticality, production windows, and downtime logs to link compliance with availability outcomes.
   • Normalize time zones, ensure status codes are consistent; remove cancelled PMs that were legitimately superseded by higher-level work.
3. Cleanse and classify.
   • Deduplicate split/child work orders; map reissued PMs to the original due date; standardize deferral reasons (access, parts, production, weather).
   • Exclude PMs intentionally moved within policy (frozen window rules) from “misses,” or report separately.
4. Compute compliance metrics.
   • Calculate PM Compliance, Schedule Compliance, Overdue PM count/age, Deferral Rate, Planned Work %, Emergency % by site, asset family, criticality, craft, and planner.
   • Build backlog aging buckets (0–7, 8–14, 15–30, 31+ days) for PMs and planned corrective work.
5. Link to reliability and production outcomes.
   • Correlate compliance vs Unplanned Downtime Hours/Availability at asset/line level; compare MTBF trend on assets with high vs low compliance.
   • Quantify capacity impact: hours of unplanned downtime attributable to missed/overdue PMs; translate to lost units and $ contribution margin.
6. Segment and localize.
   • Slice by criticality (A/B/C), constraint assets, shifts/crews, trades, planners, and by cause of deferral (parts unavailable, access denied, labor shortage).
   • Identify nodes with chronic deferrals or overdue PMs on high‑criticality assets.
7. Trend and control.
   • Plot weekly PM Compliance, Schedule Compliance, and Emergency % for 12–16 weeks; add control limits; annotate shutdowns, peaks, planner changes.
   • Track backlog age trends and “break‑in” work (added after freeze) vs adherence to the frozen weekly schedule.
8. Scenario and what‑if.
   • Model effect of: spares kitting (−parts‑caused deferrals), planner/scheduler staffing, freeze discipline (reduce break‑ins), condition‑based triggers (optimize PM load), and coordinated windows with production.
   • Estimate expected lift in PM Compliance and the resulting reduction in unplanned downtime and overtime.
9. Integrity checks.
   • Audit a sample of “completed on time” PMs for actual execution vs administrative closure; confirm tolerance windows applied correctly.
   • Ensure emergency work is not misclassified to inflate Planned Work %; reconcile labor hours to payroll and CMMS totals.

Format of the output of analysis:

• Executive scorecard: PM Compliance %, Weekly Schedule Compliance %, Overdue PMs (count/age), Deferral Rate %, Planned Work %, Emergency %, Wrench Time %, trend vs target, and link to Unplanned Downtime/Availability.
• Heatmaps: compliance by site × asset family/criticality, by planner/scheduler, and by craft/shift.
• Backlog aging dashboard: PM and planned corrective backlog by age buckets and criticality.
• Cause bridge: deferrals/misses by reason (parts, access/production, labor, data) and their contribution to lost hours and downtime.
• Correlation panel: scatter of PM Compliance vs Unplanned Downtime Hours/MTBF by asset; outlier list for RCAs.
• Calendar/Gantt: frozen weekly schedule vs actual completions and break‑ins.

How to interpret results:

• PM Compliance ≥90% with low Emergency % (≤10%): Healthy planning and reliability; sustain and shift focus to optimizing PM content (RCM) and cost.
• Low compliance with high Emergency % and rising unplanned downtime: Reactive culture; address planning/scheduling discipline, spares kitting, and access coordination first.
• High compliance but no improvement in downtime/MTBF: PM program may be misdirected; review task effectiveness (RCM/PM optimization) and move to condition‑based where appropriate.
• Overdue PMs concentrated on critical assets/constraint: Elevated risk of breakdowns and throughput impact; immediate action and prioritized scheduling needed.
• Many deferrals due to “parts unavailable”: Storeroom planning and PM kitting gap; improve BOMs, reservations, and min/max settings.
• Schedule Compliance low with many “break‑ins”: Weak freeze discipline or poor coordination with operations; implement a weekly scheduling meeting and governance.

Steps a company can take to improve on this measure:

• Planning and scheduling discipline:
  • Establish a frozen weekly maintenance schedule (e.g., freeze 70–80% of available hours) with joint Ops–Maintenance review; limit break‑ins to approved emergencies.
  • Right‑size planner/scheduler capacity (1 planner per 15–20 technicians); standardize job plans with estimated hours and task lists.
• Spares and kitting:
  • Build PM kits; reserve parts at plan time; maintain accurate BOMs and critical spares min/max; monitor kit completeness as a gate to schedule release.
• Optimize PM content (RCM/CBM):
  • RCM review of top assets to eliminate low‑value PMs and add predictive checks; introduce condition‑based triggers (vibration, temp) to reduce unnecessary work and improve effectiveness.
• Operations alignment:
  • Coordinate PMs with changeovers/low‑demand windows; define access SLAs; include maintenance windows in the production schedule.
• Execution and workforce enablement:
  • Deploy mobile CMMS for real‑time completion and time capture; improve wrench time through kitting, staging, and permit readiness; train on job plans and lockout/tagout.
• Governance and data quality:
  • Weekly KPI huddles on PM Compliance, Schedule Compliance, and Emergency % with root‑cause actions; audit “paper closes”; standardize reason codes for deferrals/misses.
• Example scenarios:
  • If PM Compliance is 72% with 35% of misses due to parts, implement PM kitting and BOM cleanup for top 50 assets; target ≥88% compliance and −30% emergency hours in 8 weeks.
  • If Schedule Compliance is 65% with many break‑ins, enforce a 1‑week freeze and a joint scheduling meeting; expected +15–20 pts in schedule compliance and −20% overtime.
  • If compliance ≥90% but downtime unchanged, run an RCM review and add vibration monitoring on the top 10% critical assets; aim for MTBF +20% and emergency work <8%.

Benchmark comparisons:

General benchmarks (directional):

• PM Compliance: Typical 80–90% weekly; world‑class ≥90–95% (within tolerance windows).
• Weekly Schedule Compliance: 80–90% in disciplined programs; break‑ins ≤10–15% of weekly hours.
• Planned Work Ratio: 70–85% planned vs 15–30% reactive/emergency; Emergency Work ≤10% of total hours.
• Wrench Time: 45–55% typical; best‑in‑class 55–65% with strong kitting/staging.

Constructing internal benchmarks:

• Track 12–16 weeks of PM Compliance and Schedule Compliance by site/asset family/planner; publish quartiles and set guardrails (e.g., PM Compliance <85% or Emergency % >15% triggers action).
• Set criticality‑based targets (e.g., A‑assets ≥95% PM Compliance; B ≥90%; C ≥85%) and prioritize backlog on A‑assets.
• Pair compliance KPIs with Unplanned Downtime Hours/MTBF and Availability to confirm that higher compliance yields reliability gains; adjust PM content if not.
• Rebaseline after CMMS cleanup, RCM reviews, or staffing/model changes; codify high‑performing sites’ planning cadence and kitting standards.