Siebel Field Service Guide > Preventive Maintenance > About Triggers for Preventive Maintenance >

Prioritization of PM Plans for Date and Time Interval Triggers

You can select priority levels, ranging from 1-ASAP to 4-Low, for PM plans in the Priority field in the Preventive Maintenance List view of the Preventive Maintenance screen. The priority value determines whether actions are generated when multiple PM plans apply to the same asset. Actions can be overlapping.

If the Optional check box on the PM plan is not selected, then action generation is mandatory, and the actions are generated regardless of the PM plan priority. However, if the Optional check box is selected, then action generation for the plan depends on the priority. Prioritization of PM plans happens only in the same run, so if actions from a previous plan with lower priority are already generated, then the current plan does not override those actions, regardless of the PM plan priority. For more information about the Priority and Optional field, see Creating Preventive Maintenance Plans (End User).

Prioritization of PM plans affects only Date and Time Interval triggers. Set up other triggers so that they do not overlap between different PM plans. Usage, Threshold, and Event triggers from different PM plans that activate on the same day can generate overlapping actions without application of the prioritization logic.

PM prioritization can handle the following situations:

• Two or more PM plans have the same priority.

  The PM Engine evaluates PM plans with equal priority as if they have no priority with respect to each other. All the actions to generate from these plans are generated, and the engine does not evaluate the priority.

• There is a PM plan with a high priority and a PM plan with a low priority.

  The PM Engine processes the plan with the high priority first to generate the necessary actions. Next, the engine processes the plan with the low priority. The engine then checks whether the actions to generate are scheduled for the same day as the actions already generated by the plan with the high priority. If a high priority action already exists, then the low priority plan does not generate another action that overlaps the action.

• The PM plans have a check in the Optional check box.

  Plan actions to always generate do not have a check in the Optional check box 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 also affects the prioritization of other plans in the same run.

• The PM plans have no set priority.

  The PM engine evaluates PM plans with no priority as the plans with the lowest priority.