Maintenance Notifications (PM-WOC-MN)
You use this application component in maintenance processing in the event of a malfunction or exceptional situation to:
Maintenance notifications document maintenance tasks completely, and make them available for analysis in the long term. You can use them for preliminary planning and execution of tasks.
Maintenance processing for unplanned tasks can be divided into the following three major areas:
The main element in this area is the maintenance notification. It is used to describe the condition of a technical object or to report a malfunction at a technical object and request that the damage be repaired.
The main element in this area is the maintenance order. It is used to plan in detail the execution of maintenance tasks, trace the progress of the work performed, and to settle the costs for the maintenance tasks.
The main element in this area is the maintenance history. It is used to store the most important maintenance data on a long-term basis. You can call up this data at any time for evaluation purposes.
You can use this instrument to process all the tasks that are executed within Plant Maintenance, and operations that do not belong directly to Plant Maintenance, such as investment, modifications, conversions, and so on.
When you enter a notification for a maintenance object, the system automatically copies all the relevant object data (for example, installation location cost center).
You can use maintenance notifications as the basis for creating maintenance orders, in order to:
When planning concrete tasks in a maintenance order, you can make reference to several maintenance notifications. If one or more notifications already exist for a maintenance order, you can also enter the technical data for the assigned object retrospectively for these notifications.
During processing or upon completion of a maintenance order, you can also create maintenance notifications as completion confirmations in the form of activity reports.
Follow-up tasks can result from maintenance notifications, such as printing a certain paper, triggering an R/3 function, or initiating a workflow.
When a maintenance notification is technically completed, its data is entered in the maintenance history.