Skip to main content
A Maintenance Plan is the scheduling definition for recurring preventive work. It combines regular work details, optional longer-frequency work, between 1 and 100 Assets, a timezone-aware recurrence, and a planning horizon. For every asset and occurrence inside the horizon, Canary creates a separate preventive work order. The work order starts as Open, uses the occurrence as its Due Date, and carries the template’s title, description, priority, assignment, location, picture, and procedure snapshot when configured.

​
Plan relationships

Only admins can create, edit, duplicate, pause, resume, archive, backfill, or skip Maintenance Plan work.

​
Calendar recurrence

The First work order due date is interpreted in the Plan timezone. Canary stores the IANA timezone with the plan so the cadence follows local calendar time through daylight-saving changes. A missing spring-forward time shifts forward by the daylight-saving gap; a repeated fall-back time uses the earlier instant.

​
Planning horizon

The Planning horizon controls how far ahead Canary materializes occurrences and generates work orders. It must be positive and no longer than one year: up to 366 days, 52 weeks, 12 months, or 1 year. A wider horizon creates more future work earlier. A shorter horizon keeps the active work queue closer to execution. Canary continues rolling the horizon forward while an eligible plan is Active.

​
Occurrence and plan states

An occurrence can be Planned, Generated, Skipped, or Superseded. The Occurrence history preserves these outcomes and links generated entries to their work orders. A visible plan is either Active or Paused:
  • Active plans can reconcile their horizon and generate work.
  • Paused plans keep generated work and history while future generation waits.
  • Resuming starts from the next future occurrence. Canary uses Backfill missed work for deliberate historical creation.
  • Archiving removes the plan from the active catalog and keeps its definitions, versions, occurrences, and generated-work provenance in storage.

​
Versioned history

Each saved definition becomes a plan version with captured work details, procedures, assets, recurrence, cycle position, work start offset, timezone, and horizon. Editing a plan supersedes affected future Planned rows. Template edits update the shared template without changing the plan’s schedule or requiring reattachment. At generation, each occurrence captures the template version and contents actually used. Generated work orders and earlier history retain those captured facts. Use Version history to understand definition changes and Occurrence history to follow planned, generated, skipped, and superseded work. Next: Create and manage a Maintenance Plan.