This Use Case describes the process for triggering preventive maintenance (PM) work based on the utilization of an asset. A maintenance management system can schedule PM work based on when the asset usage, which is obtained from a process historian, passes a designated threshold. Only the usage readings are described by this use case, and not the threshold, as they form the basis of the work trigger.

Background

While there has sometimes been confusion between automated triggering of Preventive Maintenance (PM) and the evolving trend to use more Condition-Based Maintenance (CBM), PM, along with Corrective Maintenance (CM) continue to be part of the “Maintenance Mix”, with the appropriate use of each to be dictated by a maintenance strategy properly linked to ERM. Parts of this linkage are normally established through an engineering practice known as Reliability Centered Maintenance (RCM), but comprehensive linkage to the ERM process has not been routine to the degree that will be increasingly required.

PM procedures are normally setup to be performed based on the passage of time, some sort of meter-based utilization record (such as miles driven) or a combination of the two. PM procedures must often be performed as part of a manufacturer’s warranty requirements or to meet external regulator agency requirements. While PM is expected to slowly decline in favor of CBM, it is still critical for systems that rely on it and it is often too easy to miss a PM that is required by utilization. PM, CBM and CM are often interrelated when a PM procedure is setup to trigger an inspection route work order which may subsequently result in either a CM or CBM activity. Proper integration with the controls and/or plant data historian environment enables the usage information to be captured for automatic PM triggering. The EAM system must be able to compare the newly proposed PM event to any pre-existing events to avoid generating multiple work orders for the same requested activity, but the individual request must enable a linkage with an audit trail from each requesting system (Agent).

Scenarios