# Infor EAM PM Compliance and Maintenance Backlog Weeks Calculator

> Source: https://netray.co/tools/infor-eam-pm-compliance-and-backlog-weeks-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Turn work order counts and estimated hours from Infor EAM into PM compliance, backlog weeks and ready backlog weeks, and see how crew size changes the backlog.

## Category

maintenance

## Erp

Infor EAM

## Audience

- Maintenance manager
- Reliability engineer
- Maintenance planner

## Tool

**Kind:** calculator

**Inputs:**

#### PM work orders due in period

**Key:** pm_due

**Type:** number

**Default:** 400

**Min:** 0

**Step:** 10

**Unit:** WOs

**Help:** R5EVENTS with EVT_PPM not null and EVT_TARGET in the period.

#### PM work orders completed on time

**Key:** pm_on_time

**Type:** number

**Default:** 340

**Min:** 0

**Step:** 10

**Unit:** WOs

**Help:** EVT_COMPLETED on or before EVT_TARGET plus the grace window.

#### PM work orders completed (on time or late)

**Key:** pm_completed

**Type:** number

**Default:** 370

**Min:** 0

**Step:** 10

**Unit:** WOs

#### Grace window used for on time

**Key:** grace

**Type:** number

**Default:** 7

**Min:** 0

**Step:** 1

**Unit:** days

**Help:** Informational: apply it when you count on-time PMs.

#### Corrective work orders completed in period

**Key:** cm_done

**Type:** number

**Default:** 900

**Min:** 0

**Step:** 10

**Unit:** WOs

#### Open backlog estimated hours

**Key:** backlog_hours

**Type:** number

**Default:** 3200

**Min:** 0

**Step:** 100

**Unit:** hours

**Help:** Sum of R5ACTIVITIES.ACT_EST on open work orders.

#### Technicians

**Key:** techs

**Type:** slider

**Default:** 12

**Min:** 1

**Max:** 60

**Step:** 1

**Unit:** people

#### Paid hours per technician per week

**Key:** hours_week

**Type:** number

**Default:** 40

**Min:** 1

**Step:** 1

**Unit:** hours

#### Wrench time

**Key:** wrench

**Type:** slider

**Default:** 55

**Min:** 10

**Max:** 90

**Step:** 1

**Unit:** %

**Help:** Share of paid hours spent on hands-on work.

#### Share of backlog that is planned and ready

**Key:** ready_pct

**Type:** slider

**Default:** 60

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

**Outputs:**

#### PM compliance

**Key:** pm_compliance

**Expr:** pm_on_time / pm_due * 100

**Format:** percent

**Primary:** true

**Description:** PM work orders done within the window divided by PM work orders due.

#### Gap to a 90% PM compliance target

**Key:** compliance_gap

**Expr:** max(0, 90 - pm_compliance)

**Format:** percent

#### Hands-on crew capacity per week

**Key:** capacity

**Expr:** techs * hours_week * wrench / 100

**Format:** hours

#### Total backlog

**Key:** backlog_weeks

**Expr:** backlog_hours / capacity

**Format:** weeks

**Primary:** true

**Description:** Estimated hours of open work divided by weekly hands-on capacity.

#### Ready backlog

**Key:** ready_weeks

**Expr:** backlog_weeks * ready_pct / 100

**Format:** weeks

**Description:** Rule of thumb: 2 to 4 weeks of ready work.

#### Ready backlog vs 2-4 week band (-1 low, 0 in band, 1 high)

**Key:** ready_band

**Expr:** if(lt(ready_weeks, 2), -1, if(gt(ready_weeks, 4), 1, 0))

**Format:** integer

#### PM share of completed work orders

**Key:** pm_share

**Expr:** pm_completed / (pm_completed + cm_done) * 100

**Format:** percent

**Chart:**

#### Backlog weeks vs number of technicians

**Type:** line

**X:** techs

**From:** 4

**To:** 30

**Steps:** 14

**Series:**

- backlog_weeks
- ready_weeks

**Disclaimer:** Targets shown are common maintenance management rules of thumb, not Infor or Hexagon formulas. PM share counts work orders, not hours.

## Content

**Intro:** 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.

**Sections:**

#### Where each input comes from in EAM

**Body:** 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.

**Bullets:**

- Count work orders, not activities, for the compliance inputs.
- Exclude cancelled PMs from both due and completed.

#### The formulas and their basis

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### What is a good PM compliance percentage?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

pm compliance calculator, maintenance backlog weeks calculator, infor eam facility maintenance, infor eam yearly pm schedule report, infor eam facility performance, infor eam facility management best practices, ready backlog weeks, wrench time backlog

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json