If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules, or it may not be included in your plan.


What is on it
Each row is a round — one instance of a plan coming due on one asset. A round is not yet a work order. It becomes one when it is raised: automatically, at the point the plan defines, or by hand from here when the plan has automatic generation turned off. A plan whose type raises an inspection raises an inspection instead of a work order. Overdue rounds have a red edge. Overdue preventive work is the number worth watching: it is the maintenance you decided to do and then did not.Rounds and their statuses
These are the default round statuses — your organisation may have changed them under statuses and transitions:List, Calendar and Activity creation summary
List and Calendar are two views of the same rounds: the work that has to be done. Activity creation summary answers the opposite question — what each schedule planned, including the rounds that will not be done because another round does their work.List
The list is sorted by due date, earliest first. Columns shown by default:
There are no buttons on the rows themselves. To act on a round — or on forty — tick it and use the bar at the foot of the screen, described under Acting on rounds.
Available from Columns: Triggered by (calendar, meter or condition), Meter at trigger, Days until due, Tolerance (days of slip allowed), Scheduled, Deferred to, Estimated minutes, Overdue, Notes, and who created and last updated the round.
Calendar


Activity creation summary
One row per schedule — a plan on one asset or one place, so a plan covering three pumps is three rows — showing three months of its calendar rounds at a time. The arrows move the window a month earlier or later.
A round skipped by activity merge — because a round of another plan does its work — keeps its place in the row in red, struck through, with ”→” and the number of the plan that does its work. Hovering over it says which plan, how often that plan runs and on which day: “Skipped: merged into plan (frequency) on day”. No work order is raised for it, and it is not on the list, the calendar or the capacity plan; the legend counts how many are in the window.
Meter-triggered rounds are not shown, because they have no frequency and never merge. Rounds appear once they are generated, as far ahead as the planning horizon; until then the summary says “No rounds in these months”.
Acting on rounds


Deferring needs Reschedule or defer a maintenance round. Skipping is the stronger decision, because it counts against compliance, and needs permission to edit maintenance plans.
Selecting every round matching the view, beyond the page on screen, runs the action in the background.
Tolerance
Most plans carry a tolerance — a number of days either side of the due date within which the round still counts as on time. A round done three days early on a plan with a week’s tolerance is on time; the same round two weeks late is not, and counts against PM compliance on the dashboards. Overdue rounds also appear in the Needs attention list and can be sent as notifications.Before you act
- Open the plan to change the schedule, the tasks or the tolerance.
- Open the asset to see everything else due on the same asset — doing two rounds in one visit is usually cheaper than two.
- Check the capacity plan before assuming a busy week can take what is due. This screen does not weigh technician hours, parts or shutdowns; it reports what is due.

