PM Scheduler

How this page works
  • A schedule generates a task on its own interval. Skipping one is recorded as a skip, not as a completion, because the compliance figures read from this.
  • Overdue is calculated from the last completion date, so completing a task late clears it and keeps the real date.
  • Assets come from the asset list. If a machine is missing here, add it there first.

Track all your equipment PM tasks in one place.

·
Computing PM compliance...Counting overdue, due-this-week, and on-track scope items.

Overdue

0
Past due date
-

Due soon (14d)

0
Next 14 days
-

On track

0
Compliance %
On-time delivery
-
What to do next
Computing recommendation...
Review the asset list →
How PM compliance is computed
  • Overdue: scope items where today > last completion + each task's own interval (Weekly=7, Monthly=30, Quarterly=90, Semi-annual=180, Annual=365 days).
  • Due soon (14d): scope items whose next due date falls within the next 14 days.
  • On track: everything else, including items with no completion history yet.
  • Compliance %: SMRP Metric 2.1.1, PM occurrences completed on schedule / occurrences due in the window (frequency-aware), via the canonical SMRP compliance calculation (same value Analytics shows). This is the Stair-2 gate metric, distinct both from the "on track now" snapshot count and from the "done on time" figure below it, which measures each PM against its own interval rather than against the schedule.

PM compliance feeds the Reliability dimension of your Maturity Stairway. Two consecutive weeks > 80% is the gate to Stair 2.

Loading assets...

Add Asset

Pick from Registered Assets

Loading assets...

or fill in manually

PM Tasks

Completion History