Condition-Based PM Plan Templates
Condition-based PM Plans allow you to set up a PM Plan that creates Work Orders based on single or multiple conditions such as the number of miles driven and/or transactions completed, with conditions coming from manual entries or IoT signals. This is an addition to Time-Based PM Plans, such as every six months or every year.
You can use the Installed Base's
Technical Attributes to monitor the characteristics of some important components and use the values to create condition-based PM plans to implement preventive maintenance. It also allows you to execute preventive maintenance based on product usage.
Use Cases
• Servicing a printer every 10000 prints is an example of a condition-based PM Plan.
• You can even use a combination of conditions such as usage-based and time-based conditions. One such scenario can be a vehicle that needs to be serviced every 6 months for 2 years or every 2000 miles till 6000 miles.
• Monitoring pressure readings on equipment with water systems to identify when and where a leak is likely to occur. In this scenario, you can define a condition such as if water pressure is higher than 80 PSI, then create a maintenance service request.
Additional Information for Condition-Based PM Plans
You can also create the Condition-Based PM Plan from Installed Product, Service Maintenance Contract, Account, and Location. You can create the PM Plan by clicking the OOTB Create PM Plan SFM. The Condition-Based PM Plan is launched with fields such as PM Plan Name, PM Plan Template, Work Order Purpose (Task Template), Start Date, End Date, Activity Date, and Description. The fields available on the plan depend on the object from where you create the plan. You can also use the SFM Mappings to map the fields between the following objects:
• PM Plan Template to PM Plan
• Source record (Service Contract/ Account / Location / Installed Product) to PM plan
You need to use the group settings available in Module: Preventive Maintenance; Sub-Module: Manage PM Plan, to map the fields. For more information about the settings, see
Settings.
The
PM Process screen supports Condition-Based PM plans. When the PM Process Type is set as Condition-Based, the Number of Work Orders is always One Per Product. Additionally, such a process can have one schedule. After the condition-based PM Plan and PM Process are set up, the scheduler picks up the PM Process and eligible condition-based PM Plans, and checks whether PM Work Orders are due for creation. This is done by evaluating the condition and comparing it with the actual attribute value on the related Installed Product and/or time intervals. If the conditions match, a PM Work Order is created and linked to the PM Plan. On such a PM Work Order, the Preferred Start Date is updated as described below in various conditions:
• If the Work Order is created after matching the attribute on the Installed Product, the Preferred Start Date is set as the creation date of the work order.
• If the Work Order is created after matching the date attribute in the condition, the Preferred Start Date is set as the actual date value on the matching schedule record.
• If the Work Order is created after matching the date attribute in the condition, the Preferred Start Date is set as the actual date value on the matching schedule record.
• When the Work Order was created after matching both counter and date, the Preferred Start Date is set as the actual date value on the matching schedule record.