Work Instructions - Process Control and a SOR (Set-up, Operate, and Reaction) Plan

[AAguado]

Well, I'm not sure :$ in which Room I should place this info: Marc, pls put it in the best fit place...

A few days ago, I was browsing at "Procedures" room and I was trying to find out any Work instruction example: nothing avaliable.
So, I'm attaching an example of my work instructions used by Operators in a Computer central agency.

Here's the explanation (DiviRep is the name of this product):
*Flux-D: workflow diagram, showing also: responsabilities, control process parameter and current specification (w/tolerances if apply).

*FMEA-D: FMEA starting from control process parameter (from Flux) to detect possible failures and consecuences.

*5w+1H_D: the well known methodology to deploy a reaction/prevention plan.

One of the main purpouses to writte down this very "long" wk instructions is for disminish Operators excessive dependence in Supervisors (FYI this area works 24/7), and to have a very formal documentation for trainning new Operators.

PS: Sorry for my English grammar horrors (English isn't my mother tongue...).

 

[E Wall]

Translation

After reviewing the documents provided, I find that I cannot offer an opinion because the documents are not in English. Please be patient, you may have to wait a few days for a response.

Can anyone else help out?

 

[AAguado]

Brief explanation

Ok.
I'm attaching a -very- brief explanation/translation of my previous post: I hope it'd be helpful .

Plz, let me know any comments or feedback.

 

[E Wall]

I like it

AAguado - This looks like a cross between a process control and a SOR (Set-up, Operate, and Reaction) plan. Very effective to communicate with first line employees for thier use and is a helpful auditing tool as well.

What I couldn't tell from the limited amount of translations is: Are there references included for any required records or reporting of information? If not you may consider including them along with references to higher level process documents if applicable.

Best Regards, Eileen

 

[AAguado]

Eileen,
Thx for your comments (I appreciate it ).

That was one of the main concerns of Top Managment here: is there an effective ending of work instructions? how do you know where it ends? is there any link with those currently mapped products (an output that might feed another product)?

Well, trackability it's how we distiguish if the "product" was effective performed . I mean, the output (a file, a report) will lead us to determine if we must segregate and rework or approve for next stage (note: most of the products, are sub-products or inputs for another process).

Thx again and I'll be carefully checkin' out your advice.