Preventive Maintenance Approaches
There are three ways to schedule preventive maintenance in EZYiD. A fixed maintenance schedule is generally linked to the manufacturer’s recommended service schedule; the frequency is fixed (e.g. Half Yearly, Quarterly), but the system still allows the maintenance to actually be completed on a customer’s preferred date rather than forcing an exact due date. A rolling maintenance schedule instead recalculates the next due date from the last completed maintenance date, so the interval “rolls forward” each time a service is completed. Separately, task-based scheduling lets you set up a one-off or recurring task tied to a calendar frequency (via “+Quick Schedule” on an asset, or “New Schedule Task” in Task Management) independent of the formal maintenance policy. For any of these approaches, the start date for the first scheduled maintenance is calculated from either the asset’s Date of Manufacture or its Date of First Use, and a Preferred Date field lets the customer nominate when they’d like the work actually carried out.Setting Maintenance Frequency on the Product Data Sheet
Opening a product’s edit page and going to the Policies tab shows an Inspection Policy and a Maintenance Policy section. The Maintenance Policy Frequency field (e.g. No Inspection, Half Yearly) sets the default preventive schedule that will be inherited by every asset created from or linked to that product. A single Checklist can be attached here (e.g. “6 Monthly Service Checklist”), but a checklist schedule (a rotating sequence of checklists) cannot be attached at the product level — only a single, static checklist.Setting Maintenance Frequency on an Asset
The same Maintenance Policy Frequency field is also available directly on the Asset (both on the Create Asset page and on an existing asset’s Policies tab). This is where a checklist schedule must be assigned, since checklist schedules can only be attached at the asset level, typically during onboarding. The Checklist Name dropdown lists both single checklists and checklist-schedule entries (shown with a “Sched-” prefix, e.g. “(Sched-Service Schedule) 6 Month”). The asset’s Policies tab also displays whether the schedule currently starts from Date of Manufacture or Date of First Use, along with Last Maintenance Date and the calculated Next Maintenance Date.Building a Checklist Schedule
Checklist schedules are configured under Settings > Checklist Schedules (an admin-level settings page, not the Templates > Checklist builder, which only creates single checklists). Each checklist schedule has a Name, a Type (e.g. Maintenance), a Status (Active/Inactive), and optional Site and Category scoping. The core of the schedule is an ordered, numbered list of checklists — for example, the “Service Schedule” example contains #1 “6 Monthly Service Checklist” followed by #2 “Annual Service Checklist”. Checklists can be added to the sequence via a dropdown/Add control and removed with an “X”. When a maintenance is completed, the system automatically advances to the next checklist in this sequence for the following service, rotating back to the start once the sequence is exhausted — this is what enables the quarterly/half-yearly/yearly rotation pattern.Completing a Maintenance Event
Preventive maintenance is carried out from the asset’s row-level “more options” (⋮) menu by selecting Maintenance. This opens a Maintenance Audit for the asset’s currently assigned checklist, organized into sections (for example Engine Bay, Mechanical, Safety), each containing individual Yes/No questions with optional “Log Defects” and “Annotations” links per question. After all sections are stepped through, a Maintenance Result panel shows the outcome (Passed/Failed based on responses), lets you set the asset’s status, add an observation note, and click “Mark As Completed.” This leads to an Update Asset Information panel, which requires a Pass/Fail declaration (a legally-equivalent-to-signature confirmation), and captures the Service Engineer name, Service Company name, and Service Date. The Next Maintenance Date is shown read-only (recalculated automatically), and the Next Service Checklist field shows the next checklist in the rotation, pre-selected by the system. A Useful Life Extension section lets you extend the asset’s current expiry date by a number of years/months if the service warrants it. Submitting this form finalizes the maintenance record, advances the checklist rotation, and updates the asset’s Last/Next Maintenance dates.Corrective Maintenance
Corrective maintenance centers on the Defects module (Operations > Defects). A defect can be logged standalone via “Log New Defect +” on the Defects dashboard, or in-context during an inspection/maintenance audit via the “Log Defects” link under a specific checklist question, which automatically links the defect to that asset and question. Each defect requires a Title/Summary and a Severity Level — Observation (address when convenient), Minor (schedule for repair), Major (urgent attention needed), or Critical (immediate action required) — and can optionally include a Description, Lockout Tag details (scanned Tag ID, Reported By, GPS location), photo attachments, and links to related defects via the Linked Defects tab. Defects sit in an Open status until resolved. Rather than being closed manually, open defects on an asset are automatically cleared when a scheduled Maintenance action is run to completion with a Pass outcome — so a passed maintenance service acts as the corrective close-out step for that asset’s outstanding defects.NoteCorrective action features are still evolving. This section reflects the current defect-logging and auto-clear-on-pass behavior only, and will need updating as new corrective maintenance features (such as dedicated repair tasks or manual resolution workflows) are added.