Infor EAM PM Compliance and Maintenance Backlog Weeks Calculator
This calculator turns counts and hours you can pull from Infor EAM or HxGN EAM into the maintenance KPIs managers ask for: PM compliance, total backlog in crew weeks, ready backlog weeks and the PM share of completed work. Move the technician slider or the sweep chart to see how crew size changes the backlog.
Your numbers
R5EVENTS with EVT_PPM not null and EVT_TARGET in the period.
EVT_COMPLETED on or before EVT_TARGET plus the grace window.
Informational: apply it when you count on-time PMs.
Sum of R5ACTIVITIES.ACT_EST on open work orders.
Share of paid hours spent on hands-on work.
Your results
Targets shown are common maintenance management rules of thumb, not Infor or Hexagon formulas. PM share counts work orders, not hours.
Backlog weeks vs number of technicians
Sweeps Technicians from 4 to 30, holding your other inputs fixed.
Get your EAM maintenance KPIs reviewed
Send us an export of PM and corrective work orders and we will return compliance, backlog weeks and a list of stale work orders inflating your backlog.
Optional. The tool and every export work without this. No spam.
Where each input comes from in EAM
PM work orders due are rows in R5EVENTS where EVT_PPM is not null and EVT_TARGET falls in the period. On time means EVT_COMPLETED is on or before EVT_TARGET plus your grace window; the SQL generator on this site returns that classification per work order. Corrective work orders completed are R5EVENTS rows of your corrective job types closed in the period, filtered on the system status EVT_RSTATUS. Backlog hours are the sum of R5ACTIVITIES.ACT_EST on work orders that are still open. The share of ready backlog depends on how your site marks planned work, often a user status such as ready to schedule mapped in R5UCODES.
- Count work orders, not activities, for the compliance inputs.
- Exclude cancelled PMs from both due and completed.
The formulas and their basis
PM compliance = PM work orders completed on time / PM work orders due x 100. Weekly capacity = technicians x paid hours per week x wrench time. Total backlog weeks = open estimated hours / weekly capacity. Ready backlog weeks = total backlog weeks x share that is planned and ready. PM share = completed PM / (completed PM + completed corrective) x 100. These follow the metric definitions used in maintenance and reliability practice, such as the SMRP best practice metrics for PM compliance and backlog; the targets (PM compliance of 90 percent or more, ready backlog of 2 to 4 weeks) are widely used rules of thumb, not EAM settings or vendor formulas. Some sites calculate backlog with total paid hours instead of wrench time hours; state which one you use.
Worked example
With the defaults, 340 of 400 PMs were on time, so PM compliance is 85 percent, 5 points under a 90 percent target. Twelve technicians at 40 paid hours and 55 percent wrench time give 264 hands-on hours per week, so 3,200 estimated backlog hours equal about 12.1 weeks of total backlog. If 60 percent of that is planned and ready, ready backlog is about 7.3 weeks, above the 2 to 4 week band. Before hiring, check that the backlog is real: old work orders that were done but never closed, duplicate requests and inflated estimates all push the number up. PMs are 370 of 1,270 completed work orders, about 29 percent.
Common mistakes
Counting PMs completed in the period instead of PMs due in the period mixes two populations and can show compliance above 100 percent. Using ACT_EST when many work orders have no estimate understates backlog, so check how many open work orders have zero estimated hours first. Including archived or cancelled work orders distorts both counts. Finally, a 100 percent PM compliance with rising breakdowns usually means PMs are being closed without the work, so review a sample of completed PM work orders and their booked hours in R5BOOKEDHOURS.
Frequently Asked Questions
What is a good PM compliance percentage?
Many maintenance organizations aim for 90 percent or more of PMs completed within their window, often a grace period of around 10 percent of the PM interval or a fixed number of days. Define the window first, because the same data can show 70 or 95 percent depending on it.
How many weeks of backlog should a maintenance team have?
A common rule of thumb is 2 to 4 weeks of ready backlog, meaning planned work with parts and permits available. Less than that and crews run short of planned work; much more and work is waiting too long. Total backlog including unplanned requests is usually higher.
Does Infor EAM calculate PM compliance itself?
EAM stores what you need, target and completion dates on PM work orders, and you can build KPIs and reports on it, but the definition of on time and the grace window are yours. This calculator makes the formula explicit so it matches whichever report you build.
What wrench time should I use?
Use a measured value from a work sampling study if you have one. Without one, many sites assume something between 35 and 60 percent. Keep the same assumption over time so the backlog trend stays comparable.
If you want these KPIs refreshed from EAM automatically and explained in plain English to supervisors, we can add a private AI layer on your own servers.
Related Tools
Infor EAM Work Order Backlog and PM Schedule SQL Generator
Read-only SQL for Infor EAM and HxGN EAM: backlog by department, oldest open work orders, estimated vs booked hours, PM schedule for the year and PM on-time results.
Maintenance & ReliabilityInfor EAM / HxGN EAM Work Management Table Reference (R5 Tables)
The R5 tables behind work orders, equipment, PM schedules, labor, stores and cases in Infor EAM 11.x and HxGN EAM 12, with key columns and common joins.
Maintenance & ReliabilityInfor EAM 11.x to HxGN EAM 12 Upgrade Checklist
A 40-item checklist for on-premises Infor EAM 11.x customers upgrading to HxGN EAM 12, from customisation inventory to integration retests and cutover.
More Maintenance & Reliability tools
See all- MTBF and MTTR Worksheet
- TPM Autonomous Maintenance CIL Standard Template
- TPM Autonomous Maintenance Standard Template
- TPM Pillars and Autonomous Maintenance 7 Steps Reference
- Preventive Maintenance Schedule Template
- Maintenance Work Order Template
- Inherent vs Operational Availability Calculator (MTBF, MTTR)
- Spare Parts Criticality Scoring Worksheet
- Maintenance Backlog Calculator (Weeks of Work and Crew Size)
Keep exploring
Free tools
- SAP PM Maintenance Backlog Weeks CalculatorTurn the open work hours from your SAP PM order list into backlog in weeks, net burn rate and weeks to clear. Includes a crew-size sweep.
- Infor EAM Work Order Backlog and PM Schedule SQL GeneratorRead-only SQL for Infor EAM and HxGN EAM: backlog by department, oldest open work orders, estimated vs booked hours, PM schedule for the year and PM on-time results.
- Maintenance Backlog Calculator (Weeks of Work and Crew Size)Turn backlog hours into weeks of work, estimate the time to clear it and find the crew size that holds it stable.
ERP fixes and how-tos
- How to add a private AI layer to Infor EAM on-premReference architecture to add AI to Infor EAM on-prem: read-only data path, retrieval, permissions, local GPUs, write-back control and rollout.
- SAP PM Reports: Key Plant Maintenance Tcodes and What They AnswerWhich SAP plant maintenance report answers which question: notifications IW28/IW29, orders IW38/IW39, equipment IH08, plans IP24 and operations IW49N.
Runs with your ERP
- Prometheus Planning & Scheduling with SAP Plant MaintenanceHow Prometheus Planning and Scheduling works with SAP Plant Maintenance work orders on S/4HANA and ECC: data flows, setup, pitfalls and a private AI layer.
- HxGN EAM and Infor M3 via Infor IONHow HxGN EAM (formerly Infor EAM) connects to Infor ERPs such as M3 through Infor ION: purchasing, inventory and payables sync, setup, pitfalls and AI uses.
- Oracle Fusion Cloud Maintenance with Fusion ERP and SCMHow Oracle Fusion Cloud Maintenance handles work orders, preventive maintenance and warranty on Fusion SCM: data flows, setup, pitfalls and private AI ideas.
AI on your ERP
- AI for SAP Plant Maintenance: Notifications, Work Orders, and Predictive SignalsAI grounded on SAP PM data that triages notifications, drafts work orders, standardizes failure codes, and flags predictive maintenance signals, on-prem.
- AI for HxGN EAM, Formerly Infor EAM: Ask Your Asset Records Questions Without Exporting ThemAdd private AI to Hexagon HxGN EAM, formerly Infor EAM: question equipment, work orders and stores through web services, on-prem or sovereign cloud.