Purpose

For more information about the purposes and prerequisites, see Additional Functions for Multiple Counter Plans (Master Data) .

Process Flow

Starting a multiple counter plan

Scheduling can be started by the Start/Restart function or by a Start in Cycle. For Start in Cycle you can start with any cycle set of the plan and continue with the following cycle set (see also the start in the cycle for strategy plans).

For both functions, you can specify a start time – a time in the future is normally not possible. In addition, you can store a start time in the master data of the multiple counter plan. In this case, the multiple counter plan can also be started by the schedule monitoring (IP30). This only applies, however, if the start time is not in the future in relation to the system date.

The scheduling uses the start time to determine a start counter reading for performance-based cycles.

For time-based cycles, only the start date is relevant. The start time is not taken into account for time-based cycles.

If you have defined an offset for at least one cycle within a cycle set, then an offset scheduling is performed for calculating the first scheduled date using Start/Restart or Start in Cycle.

This offset scheduling is only performed for the scheduled date with the scheduling type Restart or Start in Cycle. Offsets in cycle sets other than the lowest can only be taken into consideration for a corresponding Start in Cycle. A schedule with the scheduling type “scheduled” is always calculated by the cycle itself.

Rescheduling

For more information, see Rescheduling .

Scheduled date calculation (algorithm) in the multiple counter plan

If multiple cycles are compiled into a cycle set, then the link type of the scheduling parameter governs which of the cycles determines the planned date. For an OR link, the earliest cycle determines the planned date, for an AND link, the latest cycle determines it.

For more information, see Scheduled Date Calculation in the Multiple Counter Plan .

Schedule preview in the multiple counter plan

With the scheduling period scheduling parameter, you can also generate a schedule preview for a multiple counter plan. In this process, a determined planned date is constantly checked against the end date of this preview (system date and call interval). The scheduled date is only actually displayed if the planned date is less than or equal to the end date of the preview.

If you have not specified a call interval, the scheduling will generate at least one scheduled date with the status Waiting.

Completion requirement in the multiple counter plan

With the completion requirement scheduling parameter, a maintenance call object is not generated for the next scheduled date for a multiple counter plan until the preceding scheduled date has the status Completed.

Generation of call objects

If a scheduled date is due, then the scheduling generates the maintenance call object(s) corresponding to the maintenance plan category. A decisive factor here is which cycle set is used as the basis for calculating the scheduled dates and which maintenance items are assigned to this cycle set. Therefore, only maintenance call objects that are assigned to the corresponding cycle set are generated for the maintenance items.

You can use the cycle set assignment to the maintenance item (with corresponding task list, if necessary) to differentiate between the planned maintenance tasks.

If a maintenance- or service order is generated as the maintenance call object and if the corresponding maintenance item is assigned to a task list, then this is copied completely into the order. There is no control at operation level as in the case of a strategy plan.

Individual adjustment of the scheduling

For more information, see Optimizing the Scheduling .