We've just been handed the task recommendations from an RCM Analysis. These have been loaded into an interim database (or Legacy System - I believe that's what they call it these days) to be ultimately uploaded into SAP.
The job at hand requires that we write detailed and sequenced procedures for the tasks loaded into the database. These would include tasks on Pumps, Fans, Compressors, Turbines, etc...
Would anyone know where I could find templates taht would assist in the creation of such?

Hi,

Do you mean the templetes use to prepare job instructure (SAP-PM called Task List) for equipment before upload to SAP? If yes! I guess you try to automate upload the data into SAP. So, you should to advise from your IT department or SAP service provider.

P.S. I have a templete for do that, too.

Hi Panuphan,

Really appreciate you taking the time to respond to this post. The IT Department has provided a format for uploading to SAP. I guess what I'm after is generic Maintenance Job Routines i.e. the actual job steps required for performing PMs and/or CMs on these items.

e.g.

1. Oil Change on a Gearbox
2. Bearing Change on Gas Turbine Generator
3. etc......

I will be building a team from the Supervisors and tradesmen out on site. I was hoping to have a few samples to hit the ground running

Regards

Gaspardck,

You may find it best to create your task list details/steps in a word document and have them attached to the tasklist as a PRT document. Rather than the SAP long text.
This will give you scope to include pictures diagrams table etc.
There are people out there who have created scripts that can take these RCM recommendations and turn them into a word format for tradesmen to easily follow.

Greg

quote:

Originally posted by gaspardck:

I will be building a team from the Supervisors and tradesmen out on site. I was hoping to have a few samples to hit the ground running

Regards

In our practical, I create task list for each equipment based on equipment problem e.g. How to repair pump seal was leaked, the task list shown the step and also resources such as spare part that need to be accomplish the job.

Our planner make only significant or often fails, why they do that becuase if save time to do the job plan.

I would like to ask you about Work Instruction in each equipment, did you have?

GIW,

I have provided a sample of what we've started doing. This is uploaded into the interim database.

Panuphan, you can have a look as well

Bearing_Replacement_for_Motors_(Sample).xls (22 Kb, 66 downloads)

gaspardck

Now, our practical begin to fit the work instruction to SAP (Task List)....we called "Work Package"

I think not different from you because the work instruction is not a special or the best thing in maintenance but it is importance.

I agree with you on its importance. There will be some rules applied for consistency which will be created once we get out on site. This will be done in conjunction with the Procedures Control Management System.

Right now I just need to help in getting generic work instructions for the different bits of Rotating Equipment and utilities

That's where I need the assistance

Gaspardck,

Just a word of warning. Your motor example has 21 steps; I hope your IT people are not intending then to create a task list with 21 operations on it. Doing it this way will only give your schedulers and tradepeople an administative nightmare with 21 operations that need to be scheduled and confirmed. The task list you you will end up with probably needs only 3 operations
1. Remove motor to workshop
2. Overhaul motor
3. Install motor

The long text of the oeprartion or the documents attached in PRTs will contain the detailed instructions on how to do the job. The purpose of the SAP operation is to ensure that all the resources needed to perform the task can be scheduled to be in the right place, at the right time and with the right tools and knowledge to be able to perform the scope of work covered by each operation.

David,

Your contribution hit the nail on the head. I'm very much with you.
I have been championing the need for keeping it simple. Unfortunately, we're in a position where the client has asked us to duplicate what was presented. This will be loaded into the interim database and edited later on. It may sound like a case of duplication, or not doing things right the first time.
Harsh reality!
We just need to produce a load of fat first which will be trimmed down to what's required for implementation.

Keep the contributions coming gentlemen

quote:

Originally posted by gaspardck:
We've just been handed the task recommendations from an RCM Analysis. These have been loaded into an interim database (or Legacy System - I believe that's what they call it these days) to be ultimately uploaded into SAP.
The job at hand requires that we write detailed and sequenced procedures for the tasks loaded into the database. These would include tasks on Pumps, Fans, Compressors, Turbines, etc...
Would anyone know where I could find templates taht would assist in the creation of such?

Keep a couple of things in mind when writing "work instructions" in your long text of a PM. I have writen almost 1000 Preventative Maintenance Plans in SAP so I am (almost)positive I am doing it right. First off is the header, It needs to be clear and concise and give some type of indication of the work center or operation if possible. My headers are as follows: "PM (E) Dicer Infeed conveyor motor". The PM is obvious, but it seperates them from regular or standing work orders. E stands for electrical and belongs to the **ELEC work center, and a basic description of the work. Also remember to use the same header information for your task list information and at the begining of your long text. Secondly it is a good idea to include some "Standard Instructions" in the long text, IE Basic safety rules in your facility, read and understand the PM before starting the work, report unsafe conditions to management...you get the just of it. this type of text should be on all of your PM's. Third you will have "Special Instructions". These are directly related to the task/work at hand, "1.0 Inspect Dicer infeed conyevor....", "2.0 Record amp reading" etc...And finally at the bottom of your long text you should write the Maintenance Plan number and "PM last updated on" Writing the PM # on the Work Order makes it easier to refer back to it. or else you have to pull up the work order # and look it up and then go back to it. Documenting the changes to the maintenance plan is always a good idea, especially when new equipment is added or deleted or plans are deactivated. Put the Date and a brief description of what was done. "3/5/08 - updated special instructions". If you would like a hard copy example you can request one from me directly at jfarrell@armstrong.com

Hi Jafnarf,

That's an excellent contribution. I would be extremely interested in seeing samples of your work.

I'm also interested in contributions on the following:

Procedure Development Policy or System

I am interested in the earlier comment about attaching detailed steps in word documents as PRT attachemnts. I can attach them to a task list, and see them listed on my work orders, but the PRT file does not print. How do I get the PRT file to print when the Maintenance Plan is called?

Hi gaspardck,

I would like to introduce myself as Krishna of Lapiz Technical Services from India.

We have reached you in the right time and we are happy to note that you are in the process of implementing a SAP system.

We can assist you to make your SAP implementation more easier quicker and effective.

Please consider our expertise as this is an excellent opportunity for you to save money, time and effort.

We would like to discuss in detail vide a teleconference about how our services could help you to make your SAP implementation a great success in shorter time and at lower cost.

Looking forward to the pleasure of hearing from you soon.

Krishna
Lapiz Technical Services
Email: lts@lapizdigital.com
Website: http://www.lapiztechnical.com

Hi Krishna,

Thank you for coming to my rescue

Unfortunately, I've already been saved by some of the scribes on the board who were gracious enough to share some of their infinite wisdom with me about the above topic which is really about Job Instructions rather than SAP implementation

Regards my friend