Condition-Based PM Plan Templates
Condition-based PM Plan Templates 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 updated Technical Attributes. Condition-Based PM Plan Templates can also support time conditions, such as PM visits every six months or once per year
You can use the Installed Base's
Technical Attributes to monitor the characteristics of important components and use the changing values to inform condition-based PM plans on when to issue preventive maintenance work orders. Technical Attributes also allow an org to automatically execute preventive maintenance visits based on product usage.
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.
Condition-Based PM Process
The ServiceMax
Preventive Maintenance Process supports both Time-Based and Condition-Based PM plans, where each individual process can only be configured to support one type at a time. When the PM Process Type is set as Condition-Based, the
Number of Work Orders setting, which determines how many work orders are created based on the coverages of a PM Plan is always One Per In stalled Product. 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.
• 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.
Condition Types
In the Condition-Based PM Plans, you can define conditions based on the following:
• Usage or Frequency Based: Executes maintenance plans based on pre-defined usage metrics (For example, miles, hours, or cycles) or time interval (For example, every month).
• Criteria or Comparison: Executes maintenance plans based on real-time conditions, using comparison logic supported by an operator.
You can configure the required conditions in
Condition-Based PM Plan Templates.
Use Cases
• Servicing a printer every 10000 prints is an example of usage-based condition 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. This is an example of criteria-based condition PM Plan.
Related Topics