As Applicable - Definition

[meserret]

Nowadays we are trying to make comments on ISO 9001:2000. Everything seems clear but, i dont understand; there are lots of "applicable"s in the standard. Does this mean that there is an absolute necessity or does it mean it is up to the company? Does it give a freedom to the user? Can you please help me? Thanks a lot...

------------------
Meserret

[Marc]

I suggest you take a quick read through Elsmar.com/obsolete/tuv.html

You will see the first part is a number of questions and there are accompanying answers. When the auditor comes questions such as these will be asked. You will have to answer.

Where ever you see "...where applicable..." it is no different than in the past. To some degree it is the same with how you deal with exclusions. If there is a stated requirement which you do not do you have to be ready to explain why it is not applicable to your business / company.

This is typical where there is a 'laundry list'. QS has a lot of laundry lists. Where ever you see "...where applicable..." or "...as applicable...", you have to look at the 'requirement' and ask yourself why you do not do it. Let's look at:
-------------------
7.5.1 Control of production and service provision
The organization shall plan and carry out production and service provision under controlled conditions. Controlled
conditions shall include, as applicable
a) the availability of information that describes the characteristics of the product,
b) the availability of work instructions, as necessary,
c) the use of suitable equipment,
d) the availability and use of monitoring and measuring devices,
e) the implementation of monitoring and measurement, and
f) the implementation of release, delivery and post-delivery activities.
--------------
Do you use and need work instructions? Maybe not - some companies are quite simple and train employees (lione item b). I have clients with no measuring devices (line item d) - they're a service industry.

It is up to you to be ready to explain why each line item and its contents are, or are not, applicable to your company.

Marc you say:

Do you use and need work instructions? Maybe not - some companies are quite simple and train employees (lione item b). I have clients with no measuring devices (line item d) - they're a service industry.

I was under the impression that all activities, (quality related) were to be documented. Did I miss something somewhere where WI are not needed if a person is trained to do a job ?

[Marc]

Yup - you can train many things. You only document what it makes sense to document. QS is a bit more anal than ISO about documentation required, though.

[Marc]

However, before you take that and run with it -- let's take a person who solders connections. You train them to solder - no need for a work instruction telling them to warm and adjust the pencil. Maybe you also teach (train) that person how to read certain markings on a circuit card and they they *may* not need an instruction for that.

You just have to look at your processes and ask yourself - what do I *really* need to document for people to do their jobs and what can I *train* them to do. And remember - what one company trains employees to do another company might have a work instruction. Many factors do come into play for consideration. Including turnover rate of personnel in that position, job requirements (High school grad? Prior experience within or outside of the company? Related college degree? Degree of complexity of the job? -- To name a few).

Many of my clients have appreciated how, with my help, they have significantly reduced their documentation in favour of training and/or common sense.

Thanks Marc,
Makes sense to me now. We were always lead here that if somebody did something, it had to be documented. I can see where WI may not be needed now and think we can reduce some of ours. Thanks again
Bryan

Suppose that we have a situation in which we decide not to write any WI and instead "train" the people. Then, one day:

- Somebody got sick
- The "trained" people leave the company
- Our trainer got another job
- It 's the 3rd shift and something happened
in the process that nobody remembers or
knows how to deal with
- A supervisor from other area is assigned to
the line and need to understand the
operation

I agree that maybe not "everything" should be documented but at least a one page WI with a diagram and the CTQ characteristics is a very helpful thing to have.

Gus Gutierrez

[Marc]

I don't see this as an issue -- Again, you have to look at each instance. Typically where, for example, you only have one person in a position you typically want to consider the need for work instruction(s).

On the other hand, you can take any 'What If....' scenario too far. What If... is a problem in this way when you document disaster plans. Do you plan for earthquakes if your plant is in Tennessee? What If.... 50 key employees are killed in a bus crash on the way to a golf outing? How will you recover and who will be able to do those jobs?

It's all about taking a common sense look at what you are documenting and why. A team evaluation /. discussion helps.