When defining PM schedules with the Define PM Schedules task, you need to specify the execution interval. The system provides several options for controlling the ways in which the schedule is generated:
Based on current conditions, available resources, or other factors, you may wish to change the frequency for executing a task. For example, you may choose to define a basic schedule, with an alternate, less frequent schedule that you can execute when resources are low. Similarly, you may wish to have multiple schedules that are based on the season.
For example, suppose you require three different schedules for checking your heating system: for winter, you check it every 10 days; for summer, you check it every 90 days, and for fall and spring you check it every 30 days. To set this up, you would complete Frequency 1 Interval with 10, Frequency 2 Interval with 90, and Frequency 3 Interval with 30. At different times during the year, you tell the system which Frequency Interval to use to schedule work by setting the Current Frequency field; for example, when generating the schedule for the winter months, you would set Current Frequency to 1.
Fixed scheduling sets the execution of a PM procedure according to the scheduled first execution date, instead of the actual completion date of the last PM work order. Floating scheduling, on the other hand, schedules a PM procedure’s execution date according to the actual completion date of the last PM work order.
For example, suppose you set a PM procedure to be executed on the first day of each month. However, because of a holiday, work scheduled for January 1, 2009 is not executed until January 5, 2009. With fixed scheduling, the next due date for the PM procedure is February 1, 2009—one month from its scheduled execution date. With floating scheduling, the next due date is February 5, 2009—one month from the actual completion date.
See Also