Example: Using Time Interval Triggers
This topic gives an example of how the PM Engine schedules PM action dates. The following table lists the Time Interval triggers that the PM plan includes for an asset that you purchase on June 8.
| Time Interval Trigger Number | Interval | Valid Start | Valid End |
|---|---|---|---|
1 |
1 |
0 |
2 |
2 |
3 |
2 |
7 |
3 |
5 |
7 |
(no value) |
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, then the PM Engine uses the asset installation date to calculate the PM action dates, because no PM actions currently exist. The PM Engine schedules PM action dates of June 9, 11, 14, 18, 23, 28 as follows:
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 2 days early on June 26, and if you run the PM Engine for the period of time from June 8 to July 15, then the PM Engine uses this last completion date to calculate the PM action dates. The PM Engine schedules July 1, 6, 11 PM action dates as follows:
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, then 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 July 16, 21, 26 PM action dates as follows:
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 July 11 scheduled date to obtain the July 26 scheduled date.
Although the interval can be less than 1 day, higher-level processing logic currently prevents triggers from occurring more than once a day.