Powered By

Free XML Skins for Blogger

Powered by Blogger

Saturday, December 13, 2008

SAP to best handle Repeat Maintenance Jobs

Has anyone got a good idea or method how to use SAP to best handle repeat maintenance jobs?

Actually, we are in the process of trying to sort out repetative jobs from thousands of notifications from last few years, which is by itself an arduous task. After that maybe we can think of a way how to handle the process to reduce these jobs to make the system more efficient. Anyone done something like this before in your Company?

By analysing all of your equipment's and having a clear mapping about the frequencies from your task-lists, makes the process relatively simple. You can then group the same type of frequencies into one Maint. Plan for example.

We operate a sleek mechanism to ensure all orders are produced only on the week they're due, using IP30 - deadline monitoring (RISHTA20) as a scheduled job.

We customised the "Sort Code" used in the Maint.Plan, in a way that reflects the frequencies as mention above. So the scheduled jobs are then created in exact accordance with those sort codes (i.e. frequencies). The maint. planner only has to assign which "sort code" for new plans and the scheduled job is doing the rest.

You should think only of a Notification as a polite request for a further action, like to create a maint. order etc. For example in our company, we don't generate any notifications, as we see them as additional handling for no great benefit. We always create orders direct from the scheduled job. These orders then go to the maint. supervisor's "..workflow..", and they then distribute the orders at their discretion However, if your organisation is huge with many divisions, then perhaps it makes sense to use notification, but only you can decided.

I always tell our project team's... Always do what's necessary and not always what is possible...

No comments: