cancel
Showing results for 
Search instead for 
Did you mean: 

Preventive maintenance with a single cycle plan

Former Member
0 Kudos

Hello gurus,

I am just getting into PM. Here's my example :

Cycle is 7 days

Shift factor late : 25%

Tolerance : 10%

Shift factor early : 25%

Tolerance : 10%

Cycle modification factor : 1

Call horizon : 70%

Scheduling period : 28 days

Scheduling indicator : time selected

1st PM order created was 26.09.2008 ( manual call) for a starting fate 26.09.2008

2nd PM order is created on 01.10.2008 for a starting date 04.10.2008

Then first and 2nd orders have been completed 06.10.2008

3rd PM order is created on 10.10.2008 for a starting date 11.10.2008

4th PM order is created on 17.10.2008 for a starting date 18.10.2008

Can someone explain to me :

-for the 2nd PM order : why starting date is 04.10.2008? why creation date is 01.10.2008?

-for the 3rd PM order : why starting date is 11.10.2008? why creation date is 10.10.2008?

I can not figure out how the dates are determined ...

Thanks for your help !

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hello to all,

You did not answer me about "if the first order is delayed by 4 days" :

- what does it mean in SAP concretely?

Thanks again for the help !

P.

MTerence
Active Contributor
0 Kudos

Hi

If the first order is delayed by 4 days....exa : it has to completed on 1st, but the order is completed on 4th.

if u have given shift late factor as 100% and cycle length is 8 days, then it wil caluclte the next cal date as 12th of the month.

If u have given the shift factor as 50%, then it will cal on 8th of the month...

- Pithan

Former Member
0 Kudos

Hello Amit,

Regarding my example : i found out why the creation date was 4.10.08 and not 3.10.2008. The thing is i did not have a factory calendar in my maintenance plan , but in my work center , i had a specific calendar = 7 day week calendar which 3.10.2008 was a public holiday !

I still have to understand why 3rd and 4th order have a creation date of 10 and 17 of October.

About your simpler example (better idea) :

-let's say we are 7 Nov : a first order is created with 10th Nov as starting date : OK. We should see the 2nd order with 'Scheduled hold' status with 'Call date' = 17th Nov and 'Starting date' = 20th Nov,...and the 3rd , and the 4th because of scheduling period (40 days)

-"if the first order is delayed by 4 days" : does it mean "if first order has been completed 14th Nov", then 2nd order will have a 'Starting date' = 21st Nov

-when will be the best day to schedule jobs for deadline monitoring (program RISTRA20) ? and how often?

Thanks again for the help

amit_saxena7
Active Participant
0 Kudos

Hi,

The best day to schedule jobs for deadline monitoring and how often, totally depends on the requirements of your client. But scheduling once every ten days would be enough to keep your plan up to date.

And i would suggest you to keep the Shift Factors as 100% to avoid any confusion. So that if one call object gets delayed then the next ones will also get delayed by the same period of time. But obviously that also depends on the client requirement and the type of Technical Object.

Thanks,

Amit.

MTerence
Active Contributor
0 Kudos

Hi

Exactly, but the cal date will depends on call horizon you are giving...

If u give as 100% it will calculate according to your plan with 7 days diff...

- Pithan

former_member654170
Contributor
0 Kudos

Hi Pierre,

r u scheduling Maintenance Plan with deadlinemonitoring.

I guess u hv rescheduled the Maintenance Plan with IP30 with call Interval 1 day

narendra

Former Member
0 Kudos

Hello,

I understand that 2nd PM order has been created 01.10.2008 because of call horizon 70% and 7 day cyle => 7 days x 0.7 = 4.9 days => 26.09.2008 + 4.9 days = 01.10.2008

But why starting date is 04.10.2008 ? : I expected to be 03.10.2008 because 26.09.2008 + 7 days = 03.10.2008. Unless we have to take the 8th day (because 7day cycle), so it's 03.10.2008...

I see that for 3rd and 4th order , there has been 7 days (as 7 day cycle) as start date but what about creation dates : why is it 10.10.2008 and 17.10.2008 for 3rd and 4th order?

What to do to see an effect of shift factor and tolerance ?

Thanks again,

Pierre

amit_saxena7
Active Participant
0 Kudos

Hi,

You dont have to anything to see an effect of shift factor and tolerance other than entering the required values in specific fields, rest the system will take care of.

To understand how the dates are decided lets take a sompler example-

Cycle : 10 days

Shift factor late : 25%

Tolerance : 10%

Shift factor early : 25%

Tolerance : 10%

Cycle modification factor : 1

Call horizon : 70%

Scheduling period : 40 days

Scheduling indicator : time selected

Now suppose we start the plan on 1st of Nov.

Then the creation date will be 7th and start date will be 10th.

But if due to any reason the order is preponed or delayed for less than 1 day (9th or 11th), which is within tolerance of 10%, there will not be any effect on the future dates of Orders.

But somehow if the order is order is preponed or delayed for more than 1 day (before 9th or after 11th), then depending on the delay the effect will be reflected on the dates of subsequent orders.

For ex. if the first order is delayed by 4 days then the next order will be delayed by 1 day (since the Shift factor is 25%).

Thanks,

Amit.

amit_saxena7
Active Participant
0 Kudos

Hi,

Please go through the following definitions and check this [link|http://help.sap.com/saphelp_46c/helpdata/en/b0/df293581dc1f79e10000009b38f889/frameset.htm]. Go to Preventive Maintenance>Maintenance Planning>Scheduling>Scheduling Parameters>Scheduling Indicators.

Shift Factor: The shift factor only applies once the maintenance plan has already been scheduled, and when the difference between the planned date and actual date lies outside the tolerance range.

Tolerence: There are two tolerance ranges for the scheduling parameters in the Maintenance Planning component.

1. + Tolerance

For a late completion confirmation, this tolerance defines the time span in which a positive deviation between the actual and planned date does not influence any subsequent scheduling.

2. - Tolerance

For an early completion confirmation, this tolerance defines the time span in which a negative deviation between the actual and planned date does not influence any subsequent scheduling.

Call Horizon: The call horizon specifies as a percentage when a maintenance call object (for example, a maintenance order) should be created for a calculated maintenance date, that is, the time interval between the confirmation date or start date and the next planned date of a maintenance plan until the maintenance order is created.

Thanks,

Amit.

Edited by: Amit Saxena on Nov 3, 2008 5:13 PM

MTerence
Active Contributor
0 Kudos

HI Pierre

According to your plan, u have given the cycle date as 7 days....

so when the starting date is 4.10.2008, the next will be 11.10.2008...

It depends on the cycle length...

secondly.... u have given cal horison as 70%

It means, it will cal up the order, once it reaches 70% of the time before the starting date....

you can clearly check.. that the starting date as a difference of 7 days...

Check it out...

If this is useful.. points...

- Pithan