Preventive plans

A preventive plan connects a machine with its maintenance intervals, last completion and next due date. The Technician submits the plan with supporting evidence, and the Maintenance Reviewer decides whether the exact revision is ready to guide the next cycle. The Maintenance Manager can then distinguish reviewed plans from work still awaiting a decision.

The due-plan scan creates Requested preventive work orders for reviewed plans whose next due date has arrived. It uses the plan and due cycle to recognize a repeated run, helping the planner avoid duplicate requests for the same scheduled maintenance. The resulting work order still follows the normal planning and permit process before execution.

• Plan evidence. Record the asset, day and hour intervals, completion context and next due date. Attach the reasoning in the plan evidence so the reviewer can assess why that schedule fits the equipment and the intended maintenance task.
• Review decision. Pending Review, Reviewed, Changes Requested and Rejected make the decision state visible. The Maintenance Reviewer considers the submitted revision. Later corrections use a successor linked to the earlier plan, preserving the evidence behind the original decision.
• Due request. The daily scan selects reviewed plans due at or before its run time. It assigns an active Technician, with an active Maintenance Manager as the fallback. The planner checks that assignment and due date before scheduling the generated request.

Choose the evidence needed to justify an interval and decide who reviews it. Confirm the next due date for each pilot asset rather than assuming that an imported interval also establishes its current maintenance position. Agree how the Maintenance Manager checks the first generated request and how the reviewer handles a changed maintenance requirement.

The daily scan runs at 03:35 UTC. Rehearse what that means for the local operating day and for work due around the scan time. Agree how day and hour intervals inform planning; any connection to operating-hour readings needs its own setup. Check the active staff list because the scan selects the first active Technician by name before applying its manager fallback.

A Technician submits a monthly inspection plan for cooling pump CP-14 with its last completion, next due date and supporting evidence. The Maintenance Reviewer accepts the exact revision and the plan becomes Reviewed. When its due date arrives, the scan creates a Requested preventive work order for the pump.

Run the same due cycle again and check that the Maintenance Manager still sees the original request without an extra copy. Then change the proposed interval through a successor submission and inspect the link to the earlier plan. The reviewer should be able to explain both decisions from the retained evidence. After the resulting maintenance closes, compare the service next due date with the plan before accepting the next cycle’s schedule.

• Due Preventive Plans — Reviewed plans whose next due date has arrived, ready for maintenance planning.
• Plan Review Inbox — Submitted schedules and supporting evidence waiting for the review decision.

Rehearse the preventive cycle, then use request planning to prepare the generated job.