There are two ways in which maintenance orders are created; a maintenance order is generated when distributing a pending event or the maintenance order is created manually. With the manual creation of maintenance orders it is possible to plan a maintenance visit ahead of time. Planners of the visit can then create the maintenance order for the visit at any time prior to the actual visit occurring and can add and remove events (pending events and convenience tasks) from the maintenance order as the needs and requirements for the visit are established.
When distributing events you can create a package of events to be distributed to a maintenance order for execution at a workshop. You can only distribute events for the same top serial or a serial in its structure. The events on the maintenance order will be distributed with the same planned start and finish dates and with the same distribution type.
When the maintenance order is distributed with the Simplified Work Order distribution type, all events connected to the maintenance order will be handled within Fleet and Asset Management. When the Work Order distribution type is used, all events connected to the order will be created as work orders in IFS/Work Order Management and must be processed there. Task cards and subtasks included on the events will be created as work tasks, and connected resources, material, sign off requirements etc will be transferred to these work tasks. When the Execution Logic Structure distribution type is used, a work order structure will be created in IFS/Work Order Management based on the execution logic structure (ELS) for the maintenance order.
For information on how to process a work order in IFS/Work Order Management, refer the online help file Work Order. For information on work order distribution and handling in Fleet and Asset Management, refer the online help file Work Order - Fleet and Asset Management.
The following is a summary of the main actions that can be performed on a maintenance order:
The following table shows a description of each status on the maintenance order:
| Status | Description |
| New | The initial status used to represent an available maintenance slot. When a maintenance order is created manually it will automatically receive this status. In this status the maintenance order the minimum information required is the workshop ID and planned start and end dates. |
| Initial Scope Definition | The status used when defining the scope of the maintenance order, i.e., in terms of identifying the events to be included. |
| Under Preparation | The status in which task cards can be connected to the events and the execution logic structure is created. |
| Released | When the maintenance order with the Work Order or Execution Logic Structure distribution type is released, work orders will be generated per event and work tasks per task card and subtask. Data, such as, resources, material, and sign off requirements is transferred to the task. |
| Started | This status is used to indicate that work has started on the maintenance order. |
| Work Done | This status is used to indicate that all connected events are in either the Work Done or Finished status. When the maintenance order is in this status, sign off can be performed. |
| Finished | This status is used to indicate that the maintenance order has been signed off and is finished. |
| Cancelled | When a maintenance order is canceled, all connected events will be canceled as well. This status is used when the maintenance order is no longer applicable. |
The following table shows a description of each status on an event:
| Status | Description |
| New | The initial status used to represent an existing event that is not yet planned to be executed. |
| Planned in Scope | In this status the event has been planned on a maintenance order, but no work order has yet been created. |
| Incomplete | In this status the event has been planned on a maintenance order, but no task cards have been defined for the event. |
| Under Preparation | In this status task cards have been connected to events on the maintenance order. |
| Released | Depending on the distribution type selected, work orders will be created with connected work tasks, resources, material etc. when the event is released. |
| Started | This status is used to indicate that work has started on at least one of the connected task cards. |
| Work Done | This status is used to indicate that all task cards have reached the Work Done status or a higher status. Sign off can be performed on events in this status. Note: It is possible to reopen a maintenance event if, for instance, unplanned work is required and you need to add more task cards to the event. When reopened, the event is set to the Started status. |
| Finished | This status is used to indicate that the event has been signed off and is finished. When the event reaches this status, it will be transferred to the serial order history. |
| Cancelled | When an event is canceled, the status of the event will be changed to New and it will be disconnected from the current maintenance order. |
A maintenance order can be created weeks or even months ahead of time. The maintenance order can be created manually in an initial state to represent an available maintenance slot without any events yet being identified. In this initial state the maintenance order can be created with just the workshop and planned start and finish dates. As you continue with the planning of the order, you can add and remove events as the needs and requirements for the visit are established. When the scope is defined and ready for execution, the maintenance order can be released. At this time, a snapshot of the maintenance order can be taken to retain as a reference in terms of the initial request for the maintenance visit versus the final request.
You can assign additional events to the ongoing work scope. If events that do not have defined task cards exist, you must connect valid task cards to these events. For instance, if non routines have been discovered or condition measurements have been performed on an ongoing work scope, events may have been generated without any predefined task cards. For such events, task cards must be defined before you can proceed with the event.
When you are completing a maintenance order, you have the option of defining additional event information directly on the maintenance order. Furthermore, if sign off requirements have been defined on the maintenance order, sign off must be performed before completing the maintenance order.
When a maintenance order has being signed off and set to the Finished status, the maintenance order becomes historical and is transferred to the maintenance order history. The following information is retained on the historical maintenance order:
General information on the maintenance order, e.g., the distribution type used to distribute the order, the workshop at which the work is to be performed, the grouping ID used to generate execution logic structures, and if the maintenance order was canceled, the cause for canceling.
Information on the events that were executed or canceled on the maintenance order.
Information on any non routine work that was discovered during execution of the scheduled maintenance and reported on the work order or work task.
Information on any sign off requirements defined on the maintenance order.
Information on any snapshots taken of the maintenance order at various stages.
Journal entries generated when key actions were performed on the maintenance order.
The snapshots of a maintenance order will contain information of the maintenance scope throughout the planning stages up until execution. There are no restriction on when or how many snapshots can be taken. A snapshot can be taken, for instance, when releasing the maintenance order once the scope is defined and ready for execution. This snapshot can then be used as a reference in terms of the initial request for the maintenance visit as opposed to the final request.
The snapshot will contain all events included on the maintenance order as well as all task cards connected to each event.
The maintenance order journal is used to retain information on key changes to a maintenance order. The following changes on a maintenance order lead to the automatic creation of a journal entry:
Entries created for the above-mentioned changes are sorted into four valid journal categories: Info, Mx Event Removed, Changed Grouping ID and Task Card List Modified. Additional information on the journal entry is displayed in the journal text for each record. Journal entries will be generated when the following changes take place:
The content of the journal entries differs depending on the cause for their generation. They are as follows: