Siebel Field Service Guide > Preventive Maintenance > Preventive Maintenance Triggers >
Prioritization of PM Plans for Date and Time Interval Triggers
Priority levels can be selected for PM plans, ranging from 1-ASAP to 4-Low. This is done using the Priority field on the Preventive Maintenance screen > Preventive Maintenance List view. The priority value is used to determine whether actions (which can be overlapping) need to be generated when more than one PM plan applies to the same asset.
If the Optional flag on the PM plan is not selected, this means that action generation is mandatory and the actions are generated regardless of its priority. However, if the Optional flag is selected, action generation for this plan is dependent on the priority. Prioritization of PM plans only happens in the same run, which means that if actions from a previous plan with lower priority were already created, then the current plan does not override those actions, regardless of its priority.
Prioritization of PM plans only affects Date and Time Interval triggers. Other triggers should be set up so that they do not overlap between different PM plans. This means that Usage, Threshold, and Event triggers from different plans that trigger on the same day, can create overlapping actions without the prioritization logic being applied.
The logic of PM prioritization can handle one or a combination of the following scenarios:
- Scenario 1. Two or more PM plans have the same priority.
- Scenario 2. There are two PM plans.one with a high priority and one with a low priority
- Scenario 3. The PM plans have the optional flag set to FALSE.
- Scenario 4. The PM plans have no set priority.
In Scenario 1, PM plans with equal priority behave as if they have no priority with respect to each other. This means that all the actions that need to be generated from these plans are created and that the priority is not considered to be a factor.
In scenario 2, the PM Engine processes the plan with the higher priority first to generate the necessary actions. Next, the engine processes the plan with the lower priority. It then checks if the actions to be created are scheduled for the same day as those already generated by the plan with the higher priority. If a higher priority action already exists, then the lower priority plan does not create another action that overlaps the old one.
In scenario 3, plan actions that must always be created will have the optional flag set to FALSE for the corresponding PM plan. In this case, the PM Engine ignores the priority and the plan executes normally. The priority of mandatory PM plans will also affect the prioritization of other plans in the same run.
Finally, in scenario 4, PM plans with no priority are considered as plans with the lowest priority.
See Plans View for more information on the Priority and Optional fields.