PM processing involves developing a PM Plan, where the purpose is to ensure that the object is properly cared for so that costly breakdowns and interruptions to the production can be avoided and the need for corrective maintenance is minimized.
The PM Plan consists of Preventive Maintenance actions (PM actions). On each PM action you can define;
What type of action needs to be taken for what object.
What is required to perform the task in terms of competency, personnel resources, material, tools and facilities and instructions.
When, or under what circumstances, should the task be performed.
In order for the PM actions to generate work orders on a regular basis (calendar based generation), or based on the condition of the object (condition based generation), or because of a certain type of event that has occurred (event based generation), you need to enter one or several generation criteria on the PM action. You can define one generation criteria, or combine several generation criteria. The criteria can be modified if the PM action is in preliminary status or revision control is disabled. If revision control is enabled and modification is required on a PM action which is in active status, a new PM action revision has to be created.
PM processing also involves running generation routines so that work orders can be created from the PM actions when due. To generate work orders for due PM actions, the Calendar generation, Event generation and Criteria generation procedures need to be executed on a regular basis (The decision is entirely up to you). Work orders are only generated for active and valid PM action revisions. For information about active and valid PM action revisions, please refer to the following online help document: PM Action.
All information needed for the work order will be copied from the PM action to the work order as the work order is generated. The work orders are prepared, scheduled, executed and reported in (together with all other, non preventive maintenance work). The information cumulated on the work order can then be used to further optimize the PM action and hence the PM Plan.
The PM actions in the PM Plan can be either route PM actions or separate PM action.
A Separate Preventive Maintenance Action is used for defining a maintenance task for an equipment or a linear asset object, which require material, operations, and/or tools and facilities in order to be executed properly. The planning of this kind of task is often important, either because of the availability of the resources, or because of timing issues, i.e., the PM action must be performed at a certain time in order not to obstruct the production. A Separate PM action can for example be a 'Monthly inspection', 'Yearly shutdown', etc.
On a separate PM action you can enter information about equipment or linear asset object, action to be taken, maintenance organization responsible for executing the work orders, operations, material requirements, external costs and expenses, tool and facility requirements and connect documents. You can also enter jobs to connect standard jobs. In addition, jobs are also used to organize materials, operations, tools and facilities and any planning lines.
The separate PM actions generate separate work orders, which can be prepared and scheduled together with non preventive maintenance tasks (corrective maintenance) created from fault reports and service requests.
A Route PM action is a task that should usually be performed together with other tasks on the same route. A route consists of a number of Route PM actions. Usually, PM actions that put less demands on preparation and history are collected into a route. The advantage of a route is that the PM tasks on a route are combined into one route work order, ensuring that execution can be done as efficiently as possible. Also, reporting in a route work order is fast and easy. A route can for example be a Lubrication route, where the Route PM actions within the route determines what objects should be lubricated, when, and by which maintenance organization.
After you have created a route id, you need to create Route PM actions and prepare them separately one by one and enter information about equipment or linear asset object, action to be taken, maintenance organization responsible for executing the task, and material requirements. You can also connect documents. This information will be automatically copied over to the route work orders generated from the route's PM actions.
Route work orders are generated when the Calendar generation is executed, when an Event is reported and/or when the Criteria generation is executed, and the system sees that there are due PM actions. Since a route can contain route PM actions for several maintenance organizations and suppliers, one route work order is generated per route id, maintenance organization and contractor.
When reporting the route you only need to report the 'stops' that have not been completed. When reporting time you only need to report how long it took to complete the whole route work orders, hence simplifying the reporting in process.