Skip to main content
Maintenance Plan actions are available to admins. Select the assets the plan will maintain, then define the schedule and work order details.

​
Create a plan

  1. Open Maintenance Plans.
  2. Select New Maintenance Plan.
  3. Enter the Plan name.
  4. Add between 1 and 100 Assets.
  5. Configure Recurrence: Daily with selected weekdays, Weekly, Monthly by date, Monthly by weekday, or Yearly.
  6. Set the First work order due date and Plan timezone.
  7. Set when work starts before its due date, in hours, days, or weeks. Monthly by date also supports a specific start day before the due day. Choose how far ahead to create orders with Scheduling horizon, up to one year.
  8. Use Add work order details to enter the regular work. Saving these details returns you to the plan draft.
  9. Optionally add longer-frequency work orders and choose the starting position in the cycle.
  10. Select Create Plan.
Create validates the form directly. Missing or invalid fields are highlighted and brought into view. A separate preview or written reason is not required. New work details become a shared Work Order Template when you save the plan. Leaving without saving the plan discards a new template draft. You can also select an existing library template. The plan stays linked to that template. Editing it from the plan or the library updates the same record, and every linked plan uses its latest details for work orders generated after the edit. No reattachment is needed. Work orders already generated keep their existing contents, even when their due dates are in the future. Archiving the template stops dependent future work.

​
Edit future intent

  1. Open the plan and select Edit.
  2. Change the plan definition.
  3. Select Save Plan.
Saving writes a new version and supersedes the current future Planned rows. Existing generated work orders and history keep their original snapshots. This boundary lets you adjust the future cadence without rewriting completed or in-flight records. Use Duplicate to open a populated creation form. Change the name, assets, or schedule before creating the new plan. The original plan stays unchanged, and both plans retain links to the same templates. Editing a shared template affects future generation for both plans. Renaming a plan updates its name in the source link on existing work orders when those views reload. The work orders retain their own original details and historical creation attribution. For a specific monthly start day, work starts on that day in the plan timezone. If the actual due date comes before or on that day, including a short month or an earlier first due date, work starts one day before it is due.

​
Longer-frequency work

A plan supports one regular work definition and up to nine longer-frequency definitions. Each longer-frequency definition runs every 2–100 occurrences; each frequency must be different. On a matching date, it replaces the regular work. If two frequencies coincide, the larger frequency wins. For example, regular A with B every 2 occurrences and C every 4 gives A, B, A, C, then repeats. Starting at position 4 begins with C, A, B, A. The starting position changes which work is due first without changing the first due date.

​
Pause, resume, and archive

Every lifecycle action requires a Reason.
  • Pause stops future generation and keeps existing generated work and history.
  • Resume reactivates the plan at the next future occurrence after the current time and its last planned due date. It does not replay the gap.
  • Archive removes the plan from the active catalog and preserves its stored history.
Disabling Maintenance Plans, or disabling Procedures for a plan whose linked template includes one, closes the generation boundary for affected plans. Existing generated work and stored plan history remain preserved. Re-enabling resumes eligible plans from the next future occurrence.

​
Backfill missed work

Backfill is the explicit path for creating selected historical occurrences after a pause, module boundary, or operational gap.
  1. Open an Active or Paused plan and select Backfill missed work.
  2. Choose From and To dates. Canary interprets them in the Plan timezone.
  3. Select Preview backfill.
  4. Review the asset, nominal date, resolved time, and plan version for each candidate.
  5. Select only the occurrences you intend to create.
  6. Enter a Reason.
  7. Select Create selected work.
The lookback can reach up to 90 days. The window must fit within the plan’s current horizon, and one confirmation can add at most 500 occurrences. Canary excludes occurrences that already have a live record and requires a new preview if the plan or candidate set changes before confirmation. Backfill is unavailable for archived plans. The app currently has no Restore control. Backfilled work uses the selected historical plan version for its schedule and template selection, and the linked template’s current details when the work order is generated.

​
Skip one planned occurrence

In Occurrence history, choose an occurrence that is still Planned and select Skip. Add a Reason and confirm Skip Occurrence. The occurrence remains in history as Skipped and never produces a work order.

​
Review history and health

The plan detail shows Next due, Current version, Generation health, Last run, and its assets. Use:
  • Occurrence history for the state and generated work order of each asset occurrence.
  • Version history for the definition snapshot behind each period of future intent.