00 — Overview

Work & Supply network member (Step 7 of the asset-condition programme). The demo data is fictional; the Work templates are Work's own cumulative service tiers.

What Scheduled Maintenance is

A plan says what is required for a maintenance group (and optionally an SMCS code), how often (its triggers) and which Work template to use. An item is the live state of a plan on one unit: when it was last done, when it is next due, whether work has been raised. There is no plan type: the Work template carries the work type (service, inspection, statutory ...) and the tasks, and a sample is just a task in the template.

The models

• MaintenancePlan — code, name, maintenance group (it covers the child groups; no group means no units), an optional SMCS code (the plan applies only to units that have that SMCS fitted), the Work template, lead_days (raise the work this many days before it is due), tolerance_days (grace past the due point before overdue) and fixed_cycle.
• PlanTrigger — several per plan, "250 h or 3 months, first reached": meter (which meter, the interval), calendar (days), fixed_date (day and month) or life (follows Lifecycle's forecast for the SMCS on the unit).
• PlanInclusion — a larger service covers a lesser one (1000 h covers 500 h and 250 h).
• ScheduleItem (schedule.item, SI-…) — the unit, the plan (empty for a one-off from a condition finding, a life forecast or by hand), last done, next due (the earliest across the triggers), status, forecast confidence, the per-trigger detail, the Work order, the item it was incorporated into, and any deferral.

The demo data (3 Oct 2026)

The plans: 250 h (or 90 days), 500 h and 1000 h services, an annual inspection each 15 March (a placeholder Work template) and a transmission change-out for SMCS 3030, all for the "793F haul trucks" group.