Scheduling Parameters in Maintenance Plan

[sriram_007]

Objective :

The Main Objective of this Blog post is to explain how the Scheduling parameters are Functioning on the calculation of the Plan date in Preventive Maintenance - Single Cycle Plan

 

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 :

The basis of month always 30 days ; Only the factory calendar dates are get counted.  i.e  Cycle one month , factory calendar Saturday/Sunday/Public holiday free , start of cycle 01.08.2023 results in plan date of 13.09.2023 . Selecting the Indian (IN) 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 incase 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 a 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.