Scheduling Parameters:
Here we maintain the Scheduling Parameters for the single cycle plan directly in the maintenance plan as
shown as below.
There are 3 types of scheduling Indicator
1. Time
2. Time- key date
3. Time-factory calendars
Based On Time Scheduling Indicator:
According to the Time scheduling indicator, the calculation is based on every 30 days all the calendar
days should get counted for example if I give 01.08.2023 it will calculate after 30days. i.e 31.08.2023 is
the plan date.
Based on Time-Key Date:
According to the Time-key date indicator, the calculation is based on effective days of the month i.e If I
give 01.08.2023 as start date, the plan date occurs on 01.09.2023
Based on the Factory Calendar:
Call Horizon:
The Call Horizon determines when a maintenance call object, for example, a Maintenance
Order should be generated for a Maintenance Call.
A percentage that determines how much time must pass after the start or completion confirmation date of
a maintenance plan before the system creates a maintenance call object, for example, a maintenance order
or a service entry sheet, for a calculated maintenance date (planned date).
If no current completion confirmation date is available, the last planned date is used as a starting date for
calculating the call date for the maintenance call objects.
For example
If the duration of the cycle is 150 days and the call horizon is 0 %, 80%, or 100%, the system creates the
order after the following number of days:
0% - Immediate call
80% - Call after 100 days (= 80% of 150 days)
100% - Call after 150 days, on the planned date
For 0% of call horizon :
The Schedule will appear like this:
For 90% of call horizon:
By the same way if the call horizon is 90%
For 100% of call horizon:
By the same way if the call horizon is 100%
Completion requirement:
If you set this indicator, the system only generates the next Call object once the preceding call
object has been confirmed. If in case you're planning to release the second schedule, the
completion requirement check box is in marked stage, the interface will not allow you to release
the schedule due to the incompletion of first schedule.
Shift Factor:
Shift factor specifically for your maintenance plan by specifying the shift percentage to be taken
into account when calculating the next due date. For example the planned date for your
maintenance order was 01.09.23, but it was confirmed 15 days too late on 16.09.23. The next
planned date may now be on a different date since this is dependent on the shift factors entered:
If the shift factor is 0% the next planned date will be 01.10.2023
If the shift factor is 100% the next planned date will be 16.10.2023
If the shift factor is 50% the next planned date will be 08.10.2023
Tolerance
In the maintenance plan there are two different kinds of Tolerance's
Positive Tolerance
Negative Tolerance
Positive Tolerance:
For a late completion, this tolerance defines the time span in which a
positive deviation between the actual and planned date does not influence
any subsequent scheduling.
Negative Tolerance:
For an early completion, this tolerance defines the time span in which a
negative deviation between the actual and planned date does not influence
any subsequent scheduling
For example, if you have created a maintenance plan for 30 days and you
have defined a tolerance of 10% in the case of early completion. This
produces the tolerances of 3 days. If the completion is made no more than 3
days before the planned date, the system does not consider this deviation
when calculating the next planned date.
.
Q: What is the relationship (if any) between shift factors and tolerances? Are they used in
conjunction with each other or separately?
A: Shift factors and tolerances can be used in conjunction with each other or they can be used separately.
The screen shots illustrate how this is accomplished.
Tolerance defines late or early completion time period and the impact it has on the plan schedule: (+)
tolerance is set for late completions and (-) tolerance is set for early completions.
The shift factor is the percentage of shift that a plan can move if not completed on time. For example, if a
maintenance plan is due Sept. 1, but the work is not confirmed until Sept. 5, the shift factor will determine
the next plan due date. A100% shift on a monthly plan will move the due date to the exact day in the next
month that the work was confirmed in September (in this case, Oct. 5). A 0% shift will not allow the plan
to move the due date. The order was completed Sept. 5, but the due date is on the first of every month,
therefore, the next due date will be Oct. 1.
To use the shift factor and tolerance together, the principals are still the same. However, you are now
taking the percentage of the shift factor into account with the completion from the tolerance. The images
above illustrate how the plan change date changes with a 100% shift factor and doesn’t change with a 0%
shift factor.
Q: How do shift factors and tolerances handle multiple cycles on a maintenance plan?
A: Tolerances and shift factors react the same in single-cycle and strategy plans. Settings should be set at
the strategy level, and then they will carry over to each individual maintenance plan when it is created. To
avoid this situation, you may also want to maintain hierarchies in the maintenance strategy against each
pack, if you haven’t already done so.
