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, tool/equipment resources, material 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 type of generation criteria, or combine several generation criteria. If revision control is enabled the criteria can only be modified if the PM action is in preliminary status. If any modification is required on a PM action in active status, a new PM action revision has to be created. If revision control is disabled the criteria can be modified in any status of the PM action.
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 condition 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.
A preventive maintenance action is used for defining a maintenance task for an equipment or a linear asset object, which can require work list lines, material, personnel resources, and/or tool/equipment resources 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 PM action can for example be a 'Monthly inspection', 'Yearly shutdown', etc.
On a PM action you can enter information about equipment or linear asset object, action to be taken, maintenance organization responsible for executing the work orders, work list lines, material requirements, resource requirements for personnel and tool/equipment, external costs and expenses and connect documents. You can also enter jobs to connect work task templates. In addition, jobs are also used to organize materials, work list lines, personnel and tool/equipment and any planning lines.
The PM actions generate work orders, which can be standalone work orders that are separately prepared and scheduled together with other work orders, both preventive and non-preventive maintenance tasks (corrective maintenance) created from fault reports and service requests.
If a PM action is a task that should usually be performed together with other tasks on the same work order, the functionality for group and merge can be used. The group and merge functionality makes it possible to get several PM actions generated into same work order.
Usually PM actions that put less demands on preparation and history are interesting to collect into same work order, or if there are several PM actions that have very much in common. The advantage of grouping and merging PM actions is that they will be combined into same work order, ensuring that execution and reporting can be done as efficiently as possible. A grouped and/or merged work order can for example be a "lubrication" work order, where the PM actions within the work order determines what objects should be lubricated, when, and by which maintenance organization.
After you have created a PM Group ID, you need to enter this group on the PM actions wanted. They need to be prepared separately one by one with information about equipment or linear asset object, action to be taken, maintenance organization responsible for executing the task, material requirements and resource requirements for personnel and tool/equipment. You can also connect documents. This information will be automatically copied over to the work order generated from the grouped PM action.
Work orders are generated when the calendar generation is executed, when an event is reported and/or when the condition generation is executed, and the system sees that there are due PM actions. When there are no other PM actions to group or merge with for a PM action, there will still be a work order generated for this PM action only.
When reporting a merged work order with connected work task steps to a work task, each work task step only need to be reported as done or not done. When reporting time you only need to report how long it took to complete the whole work task, hence simplifying the reporting in process.