SAP EAM usage based preventive maintenance scenario solely based on counter readings

[former_member564417]

Greetings,

we would like to establish usage based preventive maintenance for PRTs. I am having some trouble understanding why SAP triggers maintenance orders with no measurement documents.

The example is as follows:

I have a single cycle maintenance plan that should generate a maintenance order every 1 PC

This maintenance call should be created on the same day as it is planned and the system should calculate dates for one year in advance

There are two measurement documents created for this counter. One for initializing the counter and one for the first reading

The total counter reading is 1 which in our business scenario means that no pieces have been produced with this PRT and no maintenance is necessary but while scheduling my maintenance plan in IP10 an order gets generated for every day.

I do understand that an order gets generated every day because my cycle is 1 PC and annual estimate is 365 PC but in reality it means that maintenance orders for a usage based preventive maintenance are being created without any actual usage - measurement documents.

The business scenario is a s follows:

• there are many PRT which can be used for a period of time and then put into storage where they are kept for up to 10 years
• at any time they can be brought out of storage for production and then put back
• PRTs are serialized

My question is as follows:

Is it possible to generate maintenance calls for a usage based preventive maintenance scenario solely based on counter readings.

Thank you for your help.

Best regards,

Matjaž.

[former_member564417 · Accepted solution]

Greetings,

The idea where the annual estimate on the counter is as low as possible seems to do the trick. The annual estimate needs to be sufficiently lower than the cycle .

If our cycle is 500 PC then the annual estimate is lets say 50. By doing this we almost certainly prevent the system to schedule a maintenance call item without sufficient total counter reading.

Best regards,

Matjaž.

[peter_atkin]

Matjaz Moser

Instead of using a maintenance plan to create order, you could investigate user exit IMRC0001 which is triggered on measurement document creation.

You could enter code in this user-exit to create the orders.

PeteA

[former_member564417]

Dear Peter,

that would be an option but doing this prevents us from using standard maintenance plans functionalities such as:

• task list assignment
• scheduling periods
• etc

Best regards,

Matjaž.

[former_member564417]

Dear Peter,

I guess the user exit is intended for the exact case that we would like to solve. I have red the documentation for it and at one point it says:

The system can schedule maintenance plans automatically. Scheduling is started each time a measurement document is saved. It makes sense to use this customer exit if you have a large number of maintenance plans, but only a few measurement and counter readings.

If I understand this correctly this user exit would schedule a maintenance plan once a measurement document is created but it doesn't solve the initial problem since a maintenance order would be created without taking the cycle into account - an order would be created without the counter reaching the threshold value.

Best regards,

Matjaž.

[peter_atkin]

I've never used this user-exit in conjunction with a maintenance plan...

But I suppose you could create a maintenance plan and never schedule it. Then use the user-exit to create a manual call on the maintenance plan.

PeteA

[former_member564417]

Dear Peter,

in that scenario, the user exit should check the cycle of maintenance plan as well as the total counter reading before creating a manual call. That is quite a deviation from standard functionality but it might be worth investigating further.

I will try another scenario in which annual estimate on counter master data is 1 and see how scheduling behaves with respect to measurement documents.

Best regards,

Matjaž.