True compliance is your reported PM compliance after removing completions that did not represent real, verified work.
Your dashboard says 92%. Is that real work, or is it auto-completes, zero-labor closes, and a generous grace window padding the number? Enter your reported compliance and three discount factors to see what the number looks like with the inflation stripped out.
Probably not, if you have never audited it. Most Maximo environments have some combination of auto-completed PMs that nobody actually performed, PMs closed with zero labor hours reported, and PMs counted as on time under a window broader than the one documented in the governance standard. Each of these inflates the reported number without inflating the actual work done. This estimator discounts those suspect completions to show what your compliance would look like if every counted PM represented real, verified work.
Easily, and usually without anyone setting out to cheat. The three most common methods are auto-completion workflows that close PMs without human intervention, supervisors closing work orders with no labor hours to clear the backlog before a reporting cycle, and using a broad compliance window that counts late work as on time. None of these require malicious intent. Auto-completion may be a legacy configuration nobody revisited. Zero-labor closes may be technicians who did the work but did not enter hours. The result is the same: the dashboard reports effort that did not happen.
A PM work order that moved to COMP status in Maximo with zero actual labor hours recorded. This can mean the technician did the work but forgot to enter time, or it can mean someone closed the work order without doing the work. In Maximo, check LABTRANS for actuals or the ACTLABHRS field on the work order. In a healthy program, PMs with zero labor should be well under 5%. If yours is double digits, the compliance number is meaningfully inflated.
Maximo can be configured with escalation workflows or scheduled automation that changes work order status automatically after a set period. This was sometimes set up years ago to prevent old PMs from cluttering the backlog indefinitely. The problem is that the compliance query counts these as completed work. If 10% of your PMs are auto-completing, your reported compliance is 10 percentage points higher than the real number. Check your escalation configurations and cron task schedules.
This estimator shows you the gap between reported and real compliance. The Maximo KPI Guide to PM Compliance covers how to find and fix each inflation source in Maximo: the queries that identify auto-completes and zero-labor closes, the configuration changes that prevent them, and the governance standard that defines what counts as a real completion.