Purpose

For more information on the purposes and prequisites, 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.

However, 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.

Schedules with scheduling type Restart or Start in Cycle

For performance-based cycles, the start time is used to read a measurement document valid for the counter and the value recorded there is copied into the scheduling as the start counter reading.In this process, the measurement document read is either recorded directly for the start time or is set before the start time (a virtual counter reading for the start time is not simulated).

On the start counter reading, the cycle lengths (or the offset lengths) are added up and used to determine the planned counter reading for this cycle.The annual performance recorded for the counters and the most up-to-date counter reading are used to calculate the corresponding planned date.The most up-to-date counter reading can deviate from the start counter reading.

The start time remains decisive for the first scheduled date.If, after a start has been performed, a new measurement document is created between the old measurement document and the start time, then the new document is read for a schedule update and the new document’s value is used as the start value in the scheduling.This can lead to a corresponding movement or postponement of the planned date.

For time-based cycles, only the start date is relevant.The start time is not taken into account for time-based cycles.On the start date, the cycle lengths (or the offset lengths) are added up and used to determine the planned date for this cycle.

Schedules with scheduling type scheduled

For these scheduled dates, the dates of the respective preceding scheduled dates are relevant.If the preceding date has the status Waiting or Skipped, then the planned date of this scheduled date is used as the reference time (date and 00:00:00 hours) for the follow-on date.However, if the preceding date has the status Completed, then the completion date and time are set as the reference time.

Moreover, for performance-based cycles, whether the reference time is in the past or the future in relation to the current system time is decisive.A reference time in the past means that the measurement document relevant to this point in time is read later.The measurement reading of the document is used as the basis for adding the cycle lengths.

The measurement document is read after each time the schedule is updated.Here also if a document has been created in the meantime, this can lead to scheduled dates being postponed.

If the reference time lies in the future with regard to the current system time, then a performance-based cycle is simulated for this reference point of the basis value for the addition.The annual performance maintained using the counters and the most up-to-date measurement document are taken into account for this.

For time-based cycles, only the date of the reference time is relevant.The cycle lengths are added to this date to determine the next planned date.

Special Features

If a preceding date has the status Completed, then for all performance-based cycles the measurement document relevant at the time of completion – even if the timepoint is in the future – is read and the value of the document is used as the base value for the further scheduling.As no measurement document can be recorded in the future, this can lead to unwanted postponements.Therefore, make sure that the completion date is close to the current date and that the next measurement document is created soon.

If a performance-based cycle is a cycle set of the leading (and thus the “planned-date determining”) cycle and if the counter of the cycle is used again to calculate the next scheduled date (for example, in the next cycle set), then the planned counter reading of the preceding scheduled date is set directly as the reference value for calculating the next scheduled date.This means that a leading, performance-based cycle transfers the information directly and is not subject to any simulation of the reference value.

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 .