vanputten said:
Are people talking about the standard, conformity assessment to the standard, or implemenation of the standard? Keep in mind these are 3 different things.
Language is never precise. The Koala bear eats, shoots, and leaves. The Koala bear eats shoots, and leaves. The Koala bear eats shoots and leaves.
The most sold peice of literature ever has millions of people worldwide trying to interpret it. The Bible.
So is it the standard you are complaining about? Conformity assessment to the standard? Or organizations' understanding and implementation of the standard?
By the way, the TC blah, blah, blah is always looking for help. It is a volunteer group. Please join and be part of the solution.
I agree with you. I'd like to see more people volunteer and get involved.
Within the context of this thread (which I resurrected because it is a recurring theme), I see the current issues to parallel the old issues with the addition of the subjectiveness of the 2000 standard brought (the change from "Show me proof you doing this" to "Tell me about how you're doing this"). But I don't see the standard as the major issue. I see it as I always have - The problems are in the iterpretations.
You mentioned the Bible and I do believe it is a good way to illustrate the issue of interpretations of written 'words'. In college I took a number of religious courses including 'comparative religions' in which we traced the path of religious scriptures from a number of religions going back to the 'original' texts (scrolls, etc.). Tie that in with the evolution of languages over time and you have an interesting stew out of which have come the interpreted texts we have today (in the case of christians it's the King James bible). And even that book is so widely interpreted that there are hundreds of 'sects' each of which interprets the same words differently. That said, ISO 9001 is a relatively recent document so one would hope that verbiage and interpretation would be less of an issue.
While I did not, and do not, think the change in the standard was wise, especially with respect to the interpretative issues, we have what we have in so far as the content of the standard goes. I think juliedrys, in her post a few years back, said the issue is interpretations.
I have long held the belief that interpretations play a big part. This is a real 'oldie', but go to
This Old Page and scroll down to where it says "What Part Do I Play?
EDIT: Well, now I'm not a happy camper - I had about three more paragraphs typed in and somehow I screwed up and deleted the entire second half... Wow - THAT threw me! Bummer...
OK - I brought up that old page because for a long time during implementations I perceived myself as as much of a 'lawyer' interpreting the standard as anything else. Auditor interpretation has long been an issue. I remember in about 1995 a company I worked with did their procedures in flow charts and the auditor had to be convinced that they were 'procedures'. Flow charts were not in the auditor's paradigm of what a procedure was. Now days, flow charts are part of the norm.
Well, I had several more paragraphs - this thread got me to thinking - but after loosing a bunch of what I wrote, and since it's getting late having some other things to do, I'll end here. To summarize, I think it's less of an issue of the words in the document than it is the auditor's 'qualifications' / interpretations.
Yet, I've never really complained with the consideration that trying to write a 'standard' that can be applied to any company (not to mention any TYPE of company) is nearly impossible. This is the reason for TS 16949 and AS9100. There has to be text more specific to their industry to lessen the interpretative aspect of compliance.