Maintenance Plan Call Dates called earlier than Call Horizon

[lmoc]

Hi,

May I ask for help in explaining why the Call Date for the first Call Object line was called when there is a Call Horizon of 45 DAYS? The details of the Maintenance Plan are as follows:

Maintenance Plan created and scheduled : 29.01.2024

Cycle Unit : 1000 HR

Call Horizon : 45 DAYS

Start Counter Reading : 75830 (counter reading when Maintenance Plan was created)

First Planned Date : 28.05.2024

First Call Date : 17.03.2024

Scheduling indicator : 3 - Performance Based

What is the basis of the Call Date? Shouldn't it be based on the Call Horizon? Thank you

[memem · Accepted solution]

Greetings,

as per documentation:

So according to your maintenance plan a call object should be created 45 days before the cycle 1000 hours is reached. The estimated date when cycle is reached is calculated based on counter annual estimate and regular measurement documents input.

You can also try clicking on the call algorithm button in IP10. System should show how it calculated call number data.

Best regards, Matjaž.

[lmoc · Accepted solution]

Thank you Matjaz. I have checked the algorithm button and I have the data below

[lmoc · Accepted solution]

Annual Estimate = 2367.52 Activity per day = 6.49 Start Counter Reading = 75830 Next Counter Reading = 76830 The first object was called at 17.03.2024 which is not 45 days from the Planned Date of 28.05.2024. My question is why was the Maintenance Order called at 17.03.2024? Thank you.

[memem · Accepted solution]

@lmoc Can you post a screenshot of IP10 transaction for your maintenance plan. Can you also post a screenshot of measuring documnets for your counter?

[lmoc · Accepted solution]

@memem I have attached the screenshots of IP10 and the Measuring Documents in the original question. May I ask if you may check if you can see it? Thank you

[memem · Accepted solution]

Greetings, how often do you schedule the maintenance plan - do you run IP30 daily? It is possible that the cycle is reached before 45 days. Perhaps also think why do you use call horizon - would it be okay if the maintenance call object would be created when the cycle reaches 1000?

[lmoc · Accepted solution]

Yes, IP30 is run daily via background job. We are using call horizon for MRP consideration. Thank you.

[lmoc · Accepted solution]

UPDATE: After reading several articles, it seems the Call Dates were called earlier because of the 30 DAYS entered as parameter in IP30. Since the Call Dates fell to the Interval entered in IP30, the call objects were created. Kindly confirm if this analysis is correct. Thank you.

[memem · Accepted solution]

Greetings, well that certainly sounds about right!

[lmoc · Accepted solution]

Thank you! You're time is greatly appreciated