Task lists and preventive plans

Preventive maintenance relies on two objects: the task list (what to do) and the plan (when to do it). The CMMS then generates the work orders at the right time.

Task lists

Maintenance > Task lists describes a standard intervention: an ordered list of steps (check, measurement, replacement), each of which can be a checkpoint with an expected value and unit (for example "oil pressure: 4.5 bar"), the estimated duration, the discipline (mechanical, electrical, instrumentation...), the planned parts with their quantities and the useful documents. A task list is reusable by as many plans and work orders as needed; when a work order is created, its steps and parts are copied, so they can be adapted without changing the task list.

Preventive plans

Maintenance > Maintenance plans links an equipment, a task list and a frequency:

• time-based: every n days, weeks or months from the last execution (or from a start date), with a tolerance;
• meter-based: every n units (hours, cycles...) on one of the equipment's meters, with a lead threshold to issue the work order before the exact due value;
• mixed: whichever of the two comes first triggers.

The plan also carries the priority and the lead time (number of days before the due date to create the work order), the intended team or technician, and a permit-required flag. The Next due and Overdue columns of the list highlight lagging plans; an inactive plan is kept but no longer generates anything.

Work order generation

The scheduled job gmao-preventive-generation (every night at 2 a.m. by default) creates the work orders of the plans whose due date falls within the lead window, without duplicates: at most one open preventive work order exists per plan. The Generate button of the list forces immediate generation for the site. Each generated work order carries the Preventive type, the copied task list and the planned due date.

Planning

Work > Planning shows work orders on a weekly or monthly calendar, per team or per technician. Drag and drop moves a work order; the colour reflects priority and status. Use it to level the workload and to prepare shutdowns.

The AI agent and plans

When the AI agent (see its chapter) notices that an equipment suffers repeated failures between two preventive interventions, or on the contrary that a plan has never revealed any anomaly, it proposes an interval adjustment with a quantified justification (MTBF, MTTR, number of failures). Nothing is changed without your validation in AI agent.