Page History

In order to assign work to technicians and manage the team's workload, you want the PM cases for the specific occurrences to be generated. At the same time, you don't want to generate cases for the PM occurrences that are too far in the future, as they may likely change and will only clutter the views in the system.

This configuration setting allows you to control how far in advance the PM cases will be generated.

For example, if the PM group is defined as weekly, and this setting is set to 2 (i.e. "Schedule work 2 intervals in advance"), then each time the IMMS InfraLink PM generator runs, it will make sure the PM cases are generated for the next two weeks.

This setting defines the recurrence pattern:

• The "Once" option is used to define work, which needs to occur only one time, such as initial commissioning work or a one-time / ad-hoc inspection;
• The "Daily" option is used to define work, which must occur every day or on specific days every so often;
• The "Weekly" option is used to define work, which must occur every week or every several weeks (e.g. every 2 weeks);
• The "Monthly" option is used to define work, which will be due every month or during specific months; and, finally,
• The "Annually" option is used to define work, which will be due every year or every several years.

After the schedule type is selected, IMMS InfraLink will allow you to specify the frequency and to further refine when the PM completion will be due. Specifically,

• If the schedule is defined as weekly, you will be able to specify by which day of the week the work will have to be completed.
• If the schedule is defined as monthly, you will be able to specify completion by a certain date (e.g. 25th of each month) or by a certain day of a certain week (e.g. second Thursday of a month);
• If the schedule is defined as annual, you will be able to specify completion by a certain date (e.g. 25th of June) or by a certain day of a certain month (e.g. last Friday of September);

This section contains a few additional parameters that define how the work is scheduled and when it will be expected to be performed.

• Scheduling Window <N> days. The scheduling window defines how far ahead of the due date the work can be performed. For example, if a PM schedule requires work to be completed by Friday of each week, it may not make sense to complete the work on Friday one week, on Monday the next week, and on Friday the following week, as the interval between the second and third occurrences of the PM will be almost two weeks. The scheduling window allows the PM planner to prevent such situations by specifying a short scheduling window. For example, if the scheduling window is set to 1 day, the work will have to be performed on the due date; If the scheduling window is set to 2 days, the work can be performed on the due date or the day prior, and so on.
• Start Date. The start date defines when the schedule defined by the PM group becomes applicable.
  For instance, if the PM group defines work to be completed by Thursday of each week, and the start date is specified as November 1, 2015, the first occurrence of the PM generated by the IMMS InfraLink PM generator would be due on November 5, 2015 (which is the first Thursday following the specified start date).
• End Date. In addition to the start date, you can put an end date on the PM schedule. You can do that by either specifying the number of occurrences to be performed or by setting a specific end date. The PM generator will not generate additional cases for PM occurrences when the specified number of occurrences is reached or when the calculated due date for the next occurrence falls beyond the specified end date.