|
|
• If a Condition-Based PM Plan template has more than one product associated with it, and those products have different technical attributes, then technical attributes are no longer available to be added as condition lines. This is because attributes are specific to the technical attribute template assigned to a product. If multiple products use different technical attribute templates, it could result in duplicate attributes or too many confusing attributes.
• The Expression Display Value is aligned with the Expression Internal Value. The Expression Display Value is updated when the Expression Internal Value is updated based on dynamic adjustments or conditions or time-frequency changes.
|

|
Field
|
Description
|
||
|---|---|---|---|
|
Default Purpose of Visit
|
In the Purpose of Visit, assign one of the following:
• Work Plan: In the Work Plan tab, select the Work Plan to automatically generate service tasks, recommended parts, and tools for the associated PM Work Orders. The list of Work Plans is displayed based on the Products, Product Line, and Product Family added in the Applicable Products tab. For more information, see Work Plan.
• Task Template: In the Task Template tab, select the Task Template to assign specific tasks to the owner of the PM Work Orders. For more information, see Task Templates.
When a work order is created from the PM Plan’s condition, the purpose of visit record provides vital tasks or parts information needed for the PM Work Order.
|
||
|
Use current value of IB attribute
|
Select this checkbox to ensure that PM Plans created using this template acknowledge the current attribute values of the covered installed product(s).
|
||
|
Add Rule
|
Click the Add Rule button to launch a modal for creating a condition rule on the PM Plan Template. In this condition rule, you can define the attribute and value for generating PM Work Orders from a Condition-based PM Plan. . For more information, see Adding Rules.
|
||
|
Advanced Expression
|
If you have multiple condition rules configured, you can define an advanced condition based on the execution sequence of these rules. This allows you to control how rules interact using logical operators.
For example, (1 OR 2) AND 3 indicates:
• Rule 1 or Rule 2 must be met.
• In addition, Rule 3 must also be met for the condition to apply.
|
||
|
Work Order Completion is Based On
|
Indicates the selected Work Order date or date/time field on the PM Work Order that will be considered the completion date. This is used for Dynamic Adjustment.
|

|
|
Attributes vary based on the condition type selected in the Criteria tab. If the PM Plan Template has a condition type of Usage/Frequency, the attribute options include Technical Attributes, IB Attributes, and Date Attributes. If the PM Plan Template has a condition type of Criteria/Comparison, the attribute options include only Technical Attributes and IB Attributes.
|
|
Field
|
Description
|
|---|---|
|
Operator
|
When the Template’s condition type is Usage/Frequency ,
If the value chosen in the 'Attribute' cell is a field on the Installed Base object or a technical attribute, you can choose Every or Every decrement as an operator. If one of the Date attributes is chosen, you can choose the operator as Every. Every indicates a progressive or incremental counter. Every decrement indicates a decreasing counter. This is a mandatory field.
When the Template’s condition type is Criteria/Comparison,
You can enter equals, greater than, or less than in the operator field.
|
|
Value
|
Enter the frequency or count of a specific aspect of the product. This field works in cooperation with the attribute and operator to determine the milestone parameters of your condition.
For example, if you want to perform preventive maintenance for a printer every six months or every 10,000 printouts, whichever comes faster, in this case, create two rules rows and select 6 and 10,000 as frequency.
|
|
Start
|
Enter a date or a number based on the attribute you chose. If you select the Use the current value of the IB attribute option, the current value of the IB is considered Start At a value of the IB attribute. This influences the schedules that get generated.
This is considered the starting point for calculation of the condition’s milestone. The Work Order generated for this condition is based on this starting value.
|
|
Stop
|
Enter the date or a number at which the system stops creating the PM work orders. For example, if you want to configure the rule to stop creating the PM work orders at 40,000 counts, enter 40,000. If a date-based attribute is chosen, enter the date.
|
|
Threshold %
|
Indicate a percentage of the condition’s frequency value. It will be used by the PM Engine to generate a Work Order in advance of the condition’s milestone, based on the corresponding percentage value. If left blank, 100% is assumed. This field is only available for Technical and IB Attributes.
|
|
Adjustment Section
|
Configure Dynamic Adjustment to reschedule the future PM visit based on the early or delayed PM completion of the current PM Work Order.
|
|
Adjustment Type
|
The Adjustment type determines how dynamic adjustment is applied. If the type is Actual, the next condition milestone is adjusted by calculating the difference in the attribute value from the expected Work Order completion and its actual completion. If the type is Fixed, the next condition milestone is adjusted by a fixed value indicated in the Adjustment Value fields.
|
|
Adjustment Range
|
The minimum and maximum horizon that Dynamic Adjustment will consider when applying adjustments to PM Schedules generated from this condition rule. If a PM Work Order is completed at a value less than the minimum, no dynamic adjustment will occur. If a PM Work Order is completed at a value greater than the maximum, the maximum value of adjustment will occur.
|
|
|
The Threshold % field is valid only for numbers.
|