Couldn't reach MaintainX
MaintainX API 429: {"error":"Rate limit exceeded"}
PM completion
Last 30 days · 30 days
Tracks every work order MaintainX flags as a PM — either via its native fields (
Click the pencil icon on any row to open the override editor — corrections you save flow straight into these numbers without touching MaintainX. Manage the full override set from the Settings tab.
type=PREVENTIVE, recurrence rule, procedure attached) or by name convention (“Week 1 Tunnel PM - 101”-style titles). A PM counts as on time when completedAt ≤ dueDate and late when it's completed after the due date. Open PMs whose due date has already passed are surfaced as overdue so you can go clear them. On-time % is weighted across every completed PM in the range.Click the pencil icon on any row to open the override editor — corrections you save flow straight into these numbers without touching MaintainX. Manage the full override set from the Settings tab.
Overall on-time
—
0 of 0 completed PMs on time
PMs completed
0
in the selected range
On time: 0 · Late: 0
Open + overdue
0
open PMs past due right now
Longest overdue: —
Open PMs
0
PMs not yet completed
On the clock: 0 · Overdue: 0
PM completion by site
One row per
NNN Site Openasset in MaintainX — the same site list used by the Site downtime page. Sites appear in numeric order (101, 102, 103, …) and are shown even when no PM activity touched them in this range. Locations outside the site list are appended below the divider, worst on-time % first. Any row you've overridden in the Settings tab flows through here automatically.No sites were resolved and no PMs were touched in this range.
Open + overdue
PMs past due right now
Snapshot of every open PM whose due date has passed. Longest overdue first — schedule these before anything else recurring. Click the pencil icon to correct a PM whose numbers look wrong.
No PMs are currently overdue — clean board.
Data pulled live from MaintainX · refreshed Sep 15, 2026, 6:28 AM · Non-PM completion time →