Originally posted by AJPaton:
Problem 1 - the computers don't move to the components being installed so people like a hard copy of what they're building, for occasional reference.
Problem 1 - the computers don't move to the components being installed so people like a hard copy of what they're building, for occasional reference.
This, company to company, may or may not work - in part because one has to take into consideration the turnover rate of the employees performing the work as well as complexity of the operator responsibilities (for example complexity of an assembly operation). You have to use some common sense here.
Let's say you have a low turn over rate (assemblers) and low complexity, consistent assembly - Your assemblers will probably not need much documentation to perform their job.
Let's say you have a high turn over rate (assemblers) and high complexity, but consistent, assembly - Your assemblers will probably need more documentation to perform their job than in the previous 'case'.
When I encounter this at client facilities the first question is: "...so you say you need a copy of the assembly drawing from time to time. Why is this? Specifically what information do you get off of the copy you keep at your station as a reference? Is this information which should be available all the time? Why do you only need the reference now and again?
From the answers to these questions I come up with my plan. Often they really don't ned the reference copy. But I have many clients where the assemblers keep a 'reference' copy. The key to acceptance during an audit is --> The assembler has to be ready to answer the above questions (such as what info do they use and how do they know if there has been an 'important' change) and the auditor's escort (or whoever in management is appropriate) should be ready to explain why this is a low risk situation.