However, you can't enter a larger counter reading than that of the last measurement document, since maintenance planning should be structured based on current data documented in the system using measurement documents.
Scheduling Parameters – Performance-Based
Call horizon
Scheduling period
Initial counter reading
Completion requirement
Shift factors
Tolerances for shift factors
Cycle modification factor
Principle of Performance-Based Scheduling
For example, see the table Counter Reading and Cycle Value:
Counter Reading and Cycle Value
By adding the cycle value to the current counter reading, beginning from the cycle start, the first planned date is set after 200 days.
| Estimated annual performance: | 36,500 liters |
| Internal calculation of daily performance: | 36,500 : 365 days = 100 liters per day |
| Planned date for a cycle of 20,000 liters: | 20,000 : 100 = 200 days |
Scheduling Functions Planned Date
A planned date is calculated based on the estimated annual performance, depending on the cycle.
Scheduling Functions with Measurement Document
Call Horizon
Call Horizon: Percentage and Duration
Annual throughput: 36,500 liters
Results in a daily throughput quantity of 100 liters
Selected cycle: 20,000 liters
Results in a calculated cycle duration of 200 days
Cycle start is a counter reading of 0 liters on 03/15
Results in a planned date on 10/01
Call horizon should be 90%
The call horizon at 90% means that the order isn't created on 10/01 but on 9/11 (therefore, after 180 days).
Caution
The above example is a calculation of planned dates that doesn't take account of measurement documents. If measurement documents are created, the planned dates are recalculated based on these measurement documents.
Hint
If no value is specified for the call horizon when scheduling the maintenance plan, the system assumes that the call horizon is 0%. As a result, a call is made immediately (that is, an order is generated) when the maintenance plan is started, independent of the counter reading. If the cycle duration should be kept, it's advisable to set a call horizon of 100%.
Scheduled Calls
If you're working with a call horizon of 90%, for example, the calculated planned date also appears in the list of scheduled calls.
However, the call (when the order is generated) occurs earlier.
For example, see the table Scheduled Calls.
Scheduled Calls
| Cycle start: | 03/15 |
| Estimated annual performance: | 36,500 liters |
| Calculated daily performance: | 100 liters |
| Resulting planned date: | 10/01 |
Call horizon: 90%
Call date: after 180 days, therefore 09/10
This means that an order is generated on 10/09, if no measurement documents were entered before then.