Amardeep, You will have to read up on the subject to get basic knowledge. If you have understanding issues on any particular point, I will try to help out. Regards, Biju
From India
From India
Ambika,
Some inputs for WI development.
1. The purpose of WI : A person who does not know the job should be able to read and understand the WI and perform the job. (Like we use windows help or instruction manual of a new gadget). So the language should be very simple.
2. The activities should be sequenced in the way it is to be performed. If there are a set of activities that are to be performed at the startup / shutdown, but not to be repeated these should be categorised separately in the same WI or made into a separate startup or shut down WI.
3. After the activity description add a separate column for the key point (pertaining to quality or operation) of that operation, if relevant.
4. Any safety instructions while performing the operation or PPE to be worn etc should be mentioned in the WI.
5. Illustrate the operations with a photograph, atleast where relevant. Suppose the activity is "release the emergency stop button by rotating clockwise", you can show a photo of emergency stop button in the panel so that even a new person can look for that in the panel and do the operation.
6. WIs are required in the language which the person performing the job understands. So if your operator understands a regional language only then the WI has to be in that particular regional language.
7. After developing the WI go to the concerned section and try to perform the operation by reading the WI. If not possible, observe a skilled operator and match his activities to the one written on the WI. This will help spot errors or fine tune the WI.
Regards,
Biju
From India
Some inputs for WI development.
1. The purpose of WI : A person who does not know the job should be able to read and understand the WI and perform the job. (Like we use windows help or instruction manual of a new gadget). So the language should be very simple.
2. The activities should be sequenced in the way it is to be performed. If there are a set of activities that are to be performed at the startup / shutdown, but not to be repeated these should be categorised separately in the same WI or made into a separate startup or shut down WI.
3. After the activity description add a separate column for the key point (pertaining to quality or operation) of that operation, if relevant.
4. Any safety instructions while performing the operation or PPE to be worn etc should be mentioned in the WI.
5. Illustrate the operations with a photograph, atleast where relevant. Suppose the activity is "release the emergency stop button by rotating clockwise", you can show a photo of emergency stop button in the panel so that even a new person can look for that in the panel and do the operation.
6. WIs are required in the language which the person performing the job understands. So if your operator understands a regional language only then the WI has to be in that particular regional language.
7. After developing the WI go to the concerned section and try to perform the operation by reading the WI. If not possible, observe a skilled operator and match his activities to the one written on the WI. This will help spot errors or fine tune the WI.
Regards,
Biju
From India
13Community Support and Knowledge-base on business, career and organisational prospects and issues - Register and Log In to CiteHR and post your query, download formats and be part of a fostered community of professionals.
Husys Introduction.pd f
Introduction to OD.doc
Introduction.zi p