Focusing on performance based maint plans expecting the assigned counter to be the ONLY factor in determining whether to issue a call.

We are currently getting orders even though the measure point has not reached the required metric. The plan seems to be doing a call based on the pre-calculated schedule of IP10.
Our plans are set up with Call Horizon 100%; Early Shift 100%; Late Shift 100%....we do not utilize TOLERANCE. My question is how to prevent the call from being made upon reaching one of these estimated dates, with total reliance on the measure point to determine the call.

Thanks in advance.

Maybe you did not update the counter readings ontime in the work orders.

From your description, I think we have the same "heartburn"...From my understanding it has been an issue for sometime with all SAP configurations. The basic issue is that the Annual Estimate is used by SAP to calculate the expected Activity per day... then SAP uses this calculated valve to establish the Call Dates for the Maintenance Plan... and then it relies solely on the Call Dates to determine when the order is generated.

Currently there are only a few methods that can be used to abate this situation:
1. Every so often (monthly or whatever schedule you determine) you can manually enter a new Annual Estimate (based on the readings you are taking) and then reschedule the plan either manually or let the batch job take care of it...if that is how you are set up..(IP10 manually 1 by 1 or IP30 manually or batch)... this will give you a somewhat more realistic situation... but it is time consuming and you will still have some issues depending on the interval between pm's. (from our experience, this is the only option without development or interfaces..)
2. Development... there is a user exit that can be used with some development efforts to automate the steps listed in method 1. The program uses the data collected in the measuring documents to update the annual estimate... the rescheduling of the maintnenace plans is automated in this manner... still may have some issues with intervals for some of your plans, but like method 1... it could help improve the situation by some margin.
3. Interface... you can interface a 3rd party solution that actually handles meter readings in the manner in which they should be handled... that is the pm is triggered solely on the trigger points that you establish.

If you find any other ways to handle this situation... I would LOVE to know about them!

I would suggest not running automatic scheduling of these plans. Manually run the deadline monitoring program just after you have entered the counter readings. Ensure the interval for call objects is zero days so that SAP does no future predictions.
Using this method there should be no need to update annual estimates as they are not used in the schedule calculation.

in the maintenance plan, do you tick the option where the order must be completed before it calls the next planned maintenance order?

hans

Try this on a test plan.

Lower the value of your annual estimate to about 500. Reschedule the plan. The plan/call date should reflect some time in 2032.

The plan will never be called unless the counter exceeds the frequench on the plan.