When a PM action has been created and generation conditions defined, you can continue to prepare the PM action with additional information. The preparation process varies slightly depending on whether the PM action is a Separate PM action or a Route PM action.
When you prepare a Separate PM action you can, in addition to the generation criteria, enter work instructions, material requirements, operations, external costs and expenses and tools and facility requirements. 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.
Craft requirements of a Separate PM action can be broken down into multiple operations. This is useful if you need to describe in what sequence certain steps should be done, and which craft and/or maintenance organization will be involved in the different operations. For each operation, you can also specify whether a maintenance team should be responsible for executing it. If so, you can only enter maintenance organizations and crafts connected the maintenance team. Furthermore, you can also include additional qualifications (i.e., competencies and licenses) that might be required for each operation (only applicable if IFS Human Resources is installed).
For work orders that have a series of operations, manual rescheduling can be cumbersome. To make the job a lot more easier and efficient, you can connect the operation lines to form a hierarchical structure, that is a Predecessor - Successor (i.e., Parent - Child) relationship. Including this structure in the PM actions makes the job even more simple. Consider the following example: A PM action has six operations connected as shown below.
Op No: <x> = Operation Number <x>
Thus, the predecessors for each operation number is as follows:
| Operation Number | Predecessor |
| Operation No: 1 | 2 |
| Operation No: 2 | None |
| Operation No: 3 | 2 |
| Operation No: 4 | 3,6 |
| Operation No: 5 | 2 |
| Operation No: 6 | 2 |
Note: You cannot delete operation lines that act as predecessors. For instance, in the above example, operation numbers 2, 3, and 6 cannot be deleted. You will have to remove the dependency in order to delete the operation lines. Furthermore, you cannot create relationships that loop. For example, operation no: 1 cannot be included as the predecessor of operation no: 2. To do so, you will have to remove the dependency and re-define it. Also you cannot include operation no: 4 as a predecessor to operation no: 2, since operation no: 2 is an indirect predecessor of operation no: 4.
As with all other information included in the PM action, the predecessor - successor relationships will also be copied to the work order when it is generated.
You can also connect permit types to the PM action which can be useful if certain safety regulations needs to be followed when performing the task.
Furthermore, you can create new, or connect existing documents to the PM action. You can also link your PM actions to structures, which is useful when a job involves several maintenance organizations, and you want to create a work order for each maintenance organization.
In IFS/Service Management, in addition to the information above, you can also enter a customer identity and service contract (if applicable).
The preparation of the PM action can be simplified by connecting a Separate Standard Job containing work description, operations, material requirements, tools and facilities and/or connected documents. The standard jobs are connected through jobs. The Separate PM action will inherit the information entered in the Separate Standard Job when connected. If need be you can add more information, or delete information.
When you prepare a Route PM action you can, in addition to the generation criteria, work description, material requirements and permit types. Furthermore, you can create new, or connect existing documents to the PM action.
The major difference between a Separate PM action and a Route PM action in terms of preparation is that on a Route PM action, the craft requirement cannot be broken down into multiple operations, and therefore only one craft can be assigned. Also, you cannot connect tools and facilities to a route PM action. A route PM action can therefore not be broken down into multiple operations. Also, A Route PM action cannot be linked into structures.
In IFS/ Service Management, in addition to the information above, you can also enter a customer ID and service contract (if applicable). Note: Route PM actions within the same route must use the same customer and contract.
The preparation of the PM action can be simplified by connecting a Route Standard Job containing work description, material requirements and/or connected documents. The standard jobs are connected through jobs. The Route PM action will inherit the information entered in the Route Standard Job when connected. If need be you can add more information, or delete information.