Maintenance History (PM-WOC-MH) 
Purpose
When managing technical systems, you not only want to document and support the planning of maintenance processing, you also want long-term verification documents in the form of a maintenance history.
Implementation Considerations
A long-term maintenance history (PM history) is important for the following reasons:
For safety reasons, it must be possible to prove that the preventive maintenance and inspections requested in the past were actually performed.
The history of a technical object contains important information for investing in replacements. In addition to costs, information on breakdown behavior and damage frequency can have a considerable influence on decisions regarding new investments.
A detailed history is highly beneficial for maintenance planning. Analyzing completed orders enables comparisons to be made between plants, technical systems, equipment or assemblies in order that conclusions may be drawn on how to create an optimum PM strategy. For the short-term planning of individual orders, you can refer to a similar historical order and thus considerably simplify and speed up the planning process for the current order.
Features
A good maintenance history must facilitate a differentiated analysis that is object-specific, function-related or task-oriented, and thereby provide answers to the following questions:
Structure of the Maintenance History
The maintenance history is structured largely automatically by the PM system. The data which will later make up the maintenance history is derived by maintaining the master data, entering and processing maintenance notifications, scheduling maintenance plans or executing orders.
The maintenance history comprises the following sections:
The Usage History)
The Notification History)
The Order History)

These three sections form the basis for a differentiated analysis. Object and function-related questions are answered from the usage history, and task-oriented questions are answered from the notification and order histories.