The maintenance technician receives all the orders that need to be executed and have the status ready for execution. In this phase, all preliminary and main operations are executed.
After the operations have been performed, the operations’ status must be changed to finally confirmed. To get insights into the execution status of the maintenance orders and operations, the supervisor can filter for completed orders and can change the status of the order to main work completed.
Maintenance Processing
| Order | Notification |
|---|---|
| Used to plan maintenance tasks, and plan or track the costs incurred. Planning functions do not have to be executed; orders can also be created as immediate orders without any planning. | Used to convey maintenance requirements, the documentation for technical findings, and the documentation for activities performed. |
Orders and notifications can be used independently of one another. However, they are usually combined to utilize the advantages of both instruments.
A maintenance order can also be created directly, without a notification. The findings for the malfunction description can be entered later, when the order is concluded, by a subsequent report. The disadvantage is that data regarding the origin of the malfunction can be lost.
A maintenance order is structured as follows:
| MainteMaintenance Order Part | Description |
|---|---|
| Order Header |
|
| Object List |
|
| Operation | Describes the tasks that must be performed, who performs those, and what guidelines they follow |
| Material List |
|
| Production resources and tools |
|
| Settlement rule |
|
| Costs (estimated/planned/actual) |
|
Operations List
The operations contained within an operation list can be outlined in different detail levels, depending on the type of maintenance order and scope of the work planned. An operation can consist of various sub-operations, that is, a task can be split up into various sub-tasks, which then can be assigned to different work centers. Sub-operations can be defined for the same operation number, for example, operation 0010 0010, operation 0010 0020.
Sub-operations have limited functionality in comparison to (main) operations: Material assignment and booking of actual costs is not possible.
Execution Stages
Order operations can be classified according to their significance within the operation tale of the operation data area and in the operation details. Besides, within the stage column, (sub-)operations can be classified as preliminary (PRE), main (MAIN) and subsequent (POST) work steps.
Object List
The object list is an integral part of the maintenance order that is used to collect and group:
- Notifications for the same technical objects
- Notifications for different technical objects
- Technical objects without notifications
Hence, the object list consists of several objects to be processed.
If notifications are assigned to the order, the first one in the object list appears in the notification field in the order header (=header notification). Both the header notification, and the others in the object list, can be separated from the order. The object list does not control the order. Adjustment of work to be performed, update of history, or cost distribution are not performed for the objects in the object list.
Notifications can be assigned to either an existing or a new order. If the notification has a task list assigned, its operations can be copied to the operation list of the order. As a prerequisite, the integration of a notification with an order must be set.
The following fields are available for the operations list:
- Functional Location
- Equipment
- Notification
- Date scheduled for notification (if the notification was generated from a maintenance plan)
The notifications assigned to an order are copied to the object list of the order.
In the settings of an order type, you can define how the object list entries influence the operation list of an order, for example, the creation of a maintenance order combining various notifications, which are each linked to a different task list.
The following assignment options are available:
- Order operations to object list entries are set to inactive (default)
- Order operations only for notifications, created via maintenance plans
- Order operations for all notifications
- Order operations to all object list entries
Both notifications and operations can be deleted. If a notification is deleted from the object list of an order, all corresponding operations that came with the task list of the notification are deleted from the operation list of the order. Also, if the operations linked to a notification are deleted from the operation list of the order, the corresponding notification is also deleted from the object list.
When an order is created based on a notification, the long text of the notification can be copied as the long text of the order (only possible during order creation).
Controlling
Cost calculation is an integrated function of maintenance orders and is carried out based on the planned and consumed resources. A distinction is made between orders which:
- Accumulate costs on the order header
- Accumulate costs on the order operation
Costs in the maintenance order can be displayed in two different views:
- By value category (cost category)
- By cost element (detailed cost analysis)
By default costs are calculated at header level. The operation account assignment (OAA) solution allows you to calculate costs of maintenance orders at operation level. Header totals are summed, as required. No costs are stored on the OAA order object database.
Postings at Header Level versus Postings at Operation Level
Costs are settled by default at header level. The OAA solution allows you to post the costs of maintenance orders at the operation level. An order must have either a header-based or an operation-based costing. You cannot have mixed-mode costing.
Header-costed orders create their settlement rule based on the account data of the reference object in the order header.
Orders with operation account assignment use the same logic, that is, based on the reference object in the order header but create a settlement rule for each operation.
If a technical object is assigned to the operation, the settlement rule for the operation will be created based on the data of this object.