R
Ryan Wilde
Re: Competent = Accredited?
[Devil's Advocate]
The reason we are accredited is proof with a single audit. I can write a manual, I can state that I am competent to test the presence of mercury in drinking water, but it isn't true. I can also state that I can produce 10 VDC with an uncertainty of 0.8 PPM, but without a qualified, competent assessor, you have no way to prove that, because if you, as my customer, could produce 10 VDC with an uncertainty of 0.8 PPM, you wouldn't need to pay me to make the measurement in the first place.
[/Devil's Advocate]
But if you are making measurements that your customer relies upon, measurements that they have no means to prove or disprove, again, how can they know?
Statements are fine, but they are not proof of competence, which is what an Accreditation is. The major difference between a Registration/Certification to a quality system and an Accreditation is proof of competence. Our assessors (two of them) spent three days at our location (eight employees), and all was actually reviewing our measurement process, not just documentation and paperwork, but the actual process. A statement is not proof, it is a leap of faith.
Now, I still don't think that everyone that makes measurements needs, or should, be accredited. Accreditation for wide-tolerance measurement is ludicrous. A statement of compliance shouldn't even be necessary. It's akin to putting makeup on a pig.
I agree with Ken, when the tolerances are tight, and the customer cannot prove nor disprove your measurements, then the only recourse for proof is third party assessment of competence, therefore Accreditation rears its ugly (time-consuming, expensive) head.
What I still feel is that something needs to be in between - something that is not full accreditation but is proof of competence. QS9000 manufacturers are not generally making measurement devices or standards, they are generally making P/N XXXXXX-XXX that goes into the 3.0L engine. The customer has no use for the data (a requirement of 17025) other than a warm fuzzy feeling. If the customer has proof of competence, the part should fit, and last as long as it was engineered to last. That is what everyone is shooting for, but the shift is from the old "handshake" sytem of trust to the "prove it" system. A statement of compliance is a written "I'm competent, trust me" system, which doesn't hold much water with corporations anymore.
Ryan
JRKH said:
I agree wholeheartedly. Where in a situation with critical tolerances I want my lab to be competent to make the measurments. But the origional question was not about competance or compliance, but accreditation.
[Devil's Advocate]
The reason we are accredited is proof with a single audit. I can write a manual, I can state that I am competent to test the presence of mercury in drinking water, but it isn't true. I can also state that I can produce 10 VDC with an uncertainty of 0.8 PPM, but without a qualified, competent assessor, you have no way to prove that, because if you, as my customer, could produce 10 VDC with an uncertainty of 0.8 PPM, you wouldn't need to pay me to make the measurement in the first place.
[/Devil's Advocate]
If we take the time and expense to set up a competent lab, and we have no complaints from customers re: measurements what is the point of getting certified?
But if you are making measurements that your customer relies upon, measurements that they have no means to prove or disprove, again, how can they know?
Before being forced to become certified to QS, we had a system in place based (somewhat loosely) on ISO-9000. In the preamble of the Quality Manual I stated that the system is ....."Designed to comply with the intent of ISO 9000....."
This both indicated a what we were shooting for and an out for anything we felt was superfluous. This system was just fine with our customers.
It strikes me that a similar statement in regards your internal lab should be sufficient.
Statements are fine, but they are not proof of competence, which is what an Accreditation is. The major difference between a Registration/Certification to a quality system and an Accreditation is proof of competence. Our assessors (two of them) spent three days at our location (eight employees), and all was actually reviewing our measurement process, not just documentation and paperwork, but the actual process. A statement is not proof, it is a leap of faith.
Now, I still don't think that everyone that makes measurements needs, or should, be accredited. Accreditation for wide-tolerance measurement is ludicrous. A statement of compliance shouldn't even be necessary. It's akin to putting makeup on a pig.
I agree with Ken, when the tolerances are tight, and the customer cannot prove nor disprove your measurements, then the only recourse for proof is third party assessment of competence, therefore Accreditation rears its ugly (time-consuming, expensive) head.
What I still feel is that something needs to be in between - something that is not full accreditation but is proof of competence. QS9000 manufacturers are not generally making measurement devices or standards, they are generally making P/N XXXXXX-XXX that goes into the 3.0L engine. The customer has no use for the data (a requirement of 17025) other than a warm fuzzy feeling. If the customer has proof of competence, the part should fit, and last as long as it was engineered to last. That is what everyone is shooting for, but the shift is from the old "handshake" sytem of trust to the "prove it" system. A statement of compliance is a written "I'm competent, trust me" system, which doesn't hold much water with corporations anymore.
Ryan