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

Time Interval Triggers

Time Interval triggers in a PM plan for an asset determine the dates on which the PM engine schedules PM actions for that asset. Other factors that determine these dates include:

• Installation date of the asset
• Period of time for which you run the PM engine

Time Interval triggers include the following fields:

• Interval. A time interval in days.
• Valid Start. A number that indicates the first day in the asset life to which the corresponding interval applies.
• Valid End. A number that indicates the day in the asset life to which the corresponding interval no longer applies.

Example of Using Time Interval Triggers

This topic gives one example of how the PM engine schedules PM action dates. You may use this feature differently, depending on your business model. For an asset purchased on June 8, the PM plan for the asset includes the Time Interval triggers listed in the following table:

Time Interval trigger number 1 indicates that for the first day of the asset life, a time interval of 1 day applies. Time Interval trigger number 2 indicates that for the second through the sixth day of the asset life, a time interval of 3 days applies. Time Interval trigger number 3 indicates that for the seventh and subsequent days of the asset life, a time interval of 5 days applies.

If you run the PM engine from June 8 to June 30, the PM engine uses the asset installation date to calculate the PM action dates, because no PM actions currently exist. The PM engine schedules the following PM action dates: June 9, 11, 14, 23, 28:

• For the first day of the asset life (June 9), Time Interval trigger number 1 applies. The engine adds 1 day to the June 8 installation date to obtain the June 9 scheduled date.
• For the second through sixth days of the asset life (June 10 - June 14), Time Interval trigger number 2 applies. The engine adds 3 days to the June 8 installation date to obtain the June 11 scheduled date, and adds 6 days to the June 8 installation date to obtain the June 14 scheduled date.
• For the seventh and subsequent days of the asset life (June 15 - June 30), Time Interval trigger number 3 applies. The engine adds 10 days to the June 8 installation date to obtain the June 18 scheduled date. (The engine adds 10 days, and not 5 days, to obtain a date that is on or after the seventh day of the asset life.)
• The engine adds 15 days to the June 8 installation date to obtain the June 23 scheduled date, and adds 20 days to the June 8 installation date to obtain the June 28 scheduled date.

If you complete the June 28 scheduled action two days early on June 26, and if you run the PM engine for the period of time from June 8 to July 15, the PM engine uses this last completion date to calculate the PM action dates. The PM engine schedules the following PM action dates: July 1, 6, 11:

• For the seventh and subsequent days of the asset life, Time Interval trigger number 3 applies. The engine adds 5 days to the June 26 completion date to obtain the July 1 scheduled date.
• The engine adds 10 days to the June 26 completion date to obtain the July 6 scheduled date, and adds 15 days to the June 26 completion date to obtain July 11 scheduled date.

If you do not complete the July 11 scheduled action, and if you run the PM engine for the period of time from June 8 to July 31, the PM engine uses this last scheduled date to calculate the PM action dates, because the last scheduled action has no completion date. The PM engine schedules the following PM action dates: July 16, 21, 26:

• For the seventh and subsequent days of the asset life, Time Interval trigger number 3 applies. The engine adds 5 days to the July 11 scheduled date to obtain the July 16 scheduled date.
• The engine adds 10 days to the July 11 scheduled date to obtain the July 21 scheduled date and adds 15 days to the June 11 scheduled date to obtain the July 26 scheduled date.

Although the interval could be less than 1 day, higher-level logic currently prevents triggers from firing more than once a day.

The asset installation date determines the age of the asset. An asset with no installation date has an age of 0 days.

NOTE:  Do not change the installation date of an asset, because the existing PM actions will not be consistent with your revised installation date.

Though you cannot change the dates of scheduled PM actions for an asset, you can restart PM action scheduling to go into effect on the current date or a future date. To restart PM action scheduling for an asset, use one of the following methods:

• In the Date Completed field of the latest PM action for the asset, enter the restart date.
• The PM engine uses the existing Time Interval triggers in the asset's PM plan and this restart date to schedule PM actions.
• Delete the asset from the PM plan, and create a new PM plan for the asset with new Time Interval triggers.
• The PM engine uses the revised Time Interval triggers and the asset installation date to schedule PM actions.
• If the PM plan contains only the asset for which you want to restart PM action scheduling, set an end day corresponding to today for any Time Interval triggers that are in effect on the restart date, delete any Time Interval triggers that are in effect after the restart date, and create new Time Interval triggers to replace them.

  The PM engine uses the revised Time Interval triggers and the date of the last completed PM action for the asset to schedule PM actions. If no completed PM actions exist, the engine uses the date of the last scheduled PM action for the asset instead of the date of the last completed action. If no scheduled PM actions exist for the asset, the PM engine uses the asset installation date instead of the date of the last scheduled PM action.