A PM (Preventive Maintenance) action is a template for creating future work orders, based on certain conditions. One PM action can generate many work orders. There are two kinds of PM actions: Separate PM action and Route PM action.
Revision control give you the possibility and control on deciding having revisions of PM action or do all updates on the PM action itself without having revisions. This can be performed in two ways; either on the Site window or on the Separate/ Route PM Action window. If you enabled it on site, when new PM action is created using that site will automatically get the Revision Control enabled and vise versa. A PM action revision that is in active status can only be updated with restriction if revision control is enabled and major changes such as entering new jobs, changing criteria associated with maintenance plan, changing maintenance organization, etc, cannot be performed. When major changes are required, a new PM action revision has to be created. If revision control is disabled you can make any changes to the same PM action without having to create new PM action revisions.
The status of a PM action revision can be any one of the following:
The status of the PM action revision is changed by using the available right mouse button options. A new PM action revision can be created from a PM action which is in Active or Obsolete status if there is no PM action revision currently in the Preliminary status.
All PM actions and revisions are valid from the date of creation to the time period specified in IFS/Application Services by default. However, it is possible to limit (to cap) the effectiveness of individual PM action revisions by providing each PM action revision with a life span of its own. This feature is used when generating PM Plans. The life span of the individual PM action revision should be less than the time period specified in IFS/Application Services for the capping to take place. Note: To generate work orders, a PM action revision must be active and valid. The valid to date of new revision is copied from the latest revision of the PM action and not from the revision from where new revision is created.
It is also possible to connect calendars to PM action revisions. Calendars are defined in IFS/Application Services. When a calendar is connected to a PM action revision, the PM plan will be generated in accordance with the calendar. For more information please refer to the following online help document: PM Plan.
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 tools and facilities in order to be executed properly. The planning of this kind of task is often important, either because of the resource requirements, 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 the equipment or linear asset object, action to be taken, maintenance organization responsible for executing the work orders, operation requirements, external costs and expenses, material requirements and tool and facility requirements. Furthermore, you can organize these requirements with the help of jobs. You can also specify generation conditions and connect documents. Additionally, you can plan jobs and related operations on the PM plan of a PM action revision. For more information please refer to the following online help document: PM Plan.
A route consists of a number of Route PM actions. Usually, PM actions that put less demand on preparation and history are collected into a route. The advantage with the 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 in the route determines what objects should be lubricated, when, and by which maintenance organization.
On a route PM action you can enter information about equipment or linear asset object, action to be taken, maintenance organization responsible for executing the task, craft requirements, and material requirements. The material requirements can be organized with the help of jobs. You can also specify generation conditions and connect documents.
To determine whether a task should be a route PM action or a separate PM action, the answers to the following questions may provide some guidance;