Skip to main content
This page follows what happens after a maintenance plan is activated: how its triggers become rounds, how rounds become work orders or inspection rounds, and how each is judged on time or late.

Plans, rounds and work

Step by step

1

The plan is activated

Activating publishes version 1 of the plan and builds its schedule straight away. A plan with nothing in scope or no trigger cannot be activated — the builder’s Preview step says what is missing.
2

Rounds are placed on the schedule

For calendar triggers, rounds are created for every asset in scope across your organisation’s planning horizon — 90 days unless your administrator has changed Planning horizon (days) under organisation settings. The schedule is topped up automatically as time moves on, and a planner can top it up at once with Generate now on Maintenance Due. Each round falls due at midnight on its site’s own clock — a round at a site in India is due at 00:00 India time, not at midnight wherever the server is — and its end dates, exceptions and blackout days are read on the site’s calendar too.A calendar trigger counts either from one date for the whole plan or from a date each asset carries, such as its installation date — see Counted from each asset’s date. A plan over an asset category or type that covers Existing assets only or New assets only places rounds only for the assets on that side of the day it was first activated.Meter and condition triggers do not predict dates. Their rounds are raised the moment the reading or condition says so — see below. A trigger once, on a date the asset carries follows each asset’s own date instead — see Asset-date triggers.
3

The round comes into its lead time

A plan’s lead time is how many days before the due date its work should appear. When a round enters that window:
  • if the plan has Raise the work order automatically switched on, its work order is raised by itself (or, for an inspection plan, its inspection round is raised);
  • if it is switched off, the round waits on Maintenance Due for a planner to raise it by hand — the choice for plans gated on readiness or capacity.
A plan with no lead time raises its work on the due date itself.
4

The work is done

The work order is worked and closed like any other, or the inspection round is answered and submitted. Submitting an inspection round completes the round that asked for it.
5

The next round follows

A fixed-calendar trigger keeps its dates whatever happens. A trigger set to count from completion places the next round one interval after the last one was finished, so a late round moves the ones after it.

What a work order takes from its plan

When a round’s work order is raised, it copies from the plan as it stands at that moment: The job also names the plan that raised it — its number, its name and how often it runs — on the Planned work card of the work order, so whoever holds the job can tell a quarterly overhaul from a monthly check without leaving it. Editing the plan later changes rounds not yet raised. Work orders already raised keep what they were raised with, because a job somebody is part-way through should not change under them. Where the plan names an inspection template but its type is an ordinary work order type, each round raises the work order and an inspection round beside it. The work order is still what somebody is scheduled and held to a due date for.

Counted from each asset’s date

A calendar trigger set to count from an asset date field gives every asset in scope its own schedule. The first round is the asset’s date plus the plan’s Start schedule after (days), and every round after it is a whole number of intervals from that first one. Forty chillers installed across a year are then serviced monthly from each one’s own installation, rather than all on the plan’s one date. An asset whose date is empty is given no rounds, rather than a schedule counted from a guess. The builder’s Preview step says how many such assets there are and lists them, and an asset is scheduled as soon as its date is filled in. When the date changes, that asset’s rounds not yet raised as work orders are taken off and its schedule is counted again from the new date. Such a trigger never counts from completion.

Meter triggers

A meter trigger names a meter type — running hours, cycles, kilometres — rather than one meter, so every asset in scope that carries a meter of that type is watched separately. When a new reading on an asset passes the last value that asset fired at plus the interval, a round is raised for that asset. A reading that jumps more than one interval raises one round, not several: 1,600 hours against a 500-hour interval raises one round and the next falls due at 2,000. Readings are recorded on the asset’s meters, including from the field app.

Condition triggers

A condition trigger is a rule about the asset — a meter’s latest reading above a limit, a health score below a threshold, a field with a particular value. It is checked against the asset as it stands, and only on the rising edge: a round is raised when the condition becomes true, and not again until that round is finished. Readings re-check conditions immediately; everything else is checked on a regular pass.

Asset-date triggers

A trigger once, on a date the asset carries names one of the asset’s dates — a calibration due date, a warranty expiry, or a date custom field your organisation added. Every asset in scope falls due on its own value of that date, so one plan can calibrate fifty instruments that each fall due on a different day. The round is scheduled for the asset’s date, raised the plan’s lead time ahead of it, and due on that date plus the plan’s tolerance. An asset added with its date already behind it gets its round at once, dated when it really was due. A completed round does not come back until somebody records the asset’s next date, so moving the date on is what schedules the next one. There is at most one open round per trigger and asset. The date is checked whenever it is written — the asset saved, a date custom field answered, an asset added to the plan, the plan activated or its triggers saved — and once an hour for dates that time alone has brought inside the lead time.

When triggers combine

A plan with more than one trigger combines them with its trigger rule:

Lead time, tolerance and compliance

The builder’s Preview step shows both for the plan’s first round, for example 3 days · on time until Oct 22, 2026.

Rounds merged into a longer one

A plant often runs weekly, monthly, quarterly, half-yearly and yearly schedules on the same equipment, and the visit the yearly service makes also does that month’s monthly round and the weekly one before it. Activity merge is a switch on each site, in its Planned maintenance section, that says so once for the whole site. It is off by default. With it on, a weekly, monthly, quarterly or half-yearly round is skipped when a less frequent schedule for the same asset (or the same place), location and work order type already visits it. A weekly round looks seven days ahead; the others look at the same calendar month. The skipped round is still recorded, as Skipped, naming the round that does its work. It raises no work order, and it is not on the Maintenance Due list, its calendar or the capacity plan. A merged round still covers the one below it, so a yearly can cover a monthly that in turn covers a weekly. If the covering round is later cancelled, the rounds it covered are put back. Only calendar triggers merge. To see which rounds were merged and into what, open Activity creation summary on Maintenance Due.

Round statuses

Rounds have their own state model. The defaults are below, and your administrator can rename or extend them under statuses. Skipping, deferring and raising early are done from Maintenance Due, which also offers a calendar view of what is coming.

Versions

Every round records the version of the plan it was raised under. If a plan is edited after it was last published, new rounds follow the edits straight away but still carry the old version number — the plan’s screen warns about this, and Publish version N puts the change on the record. See Publishing a new version.

Maintenance Due

Where rounds are raised, deferred and skipped.

Inspections

What an inspection round is and how it is graded.