This was an e-mail I received:
What was QS-9000 REALLY supposed to achieve?
The original intent of QS-9000 was to reduce or eliminate multiple supplier audits by the 'Big 3' and to set a 'standard' set of basic requirements including aspects such as design and development via the AIAG's APQP process. This process included additional aspects such as requirements for FMEAs and control plans, as well as several other improvement elements such as an effective nonconformance and corrective action system. The issue of interpretations came heavily into play as did the number of suppliers which did not have anyone in-house who understood many of the requirements. Many companies did not even have someone who really understood the basics of control plan development, FMEAs and such. This said, many companies had never even done SPC and again had no one internally who really understood SPC.
This was combined with many QS-9000 auditors who did not understand the workings of things like control plans themselves, not to mention interactions of the systems as a whole. I should mention here that many customers often had SQAs which, sad to say, did not understand any more than the auditors and their suppliers. I met one QS auditor who was a college prof who 'dropped out'. He had no manufacturing or other business experience. The audit went OK but he was obviously not an appropriate auditor - his understanding of many aspects was lacking including the intracies and applicability of FMEAs and control plans, tying in SPC and such. in some cases, such as where the company had little internal understanding, it was a lot like the old 'blind leading the blind'.
Another reality was the auto makers are really product oriented. Even with QS-9000, customer audits at many companies did not subside as predicated. I was working with Motorola when Ford sent a team in for several days. While QS-9000 was nice to have, Ford really wanted product audits and Q1. In conversations there at the time, it was evident that the number of customer audits did not decline. Admittedly this is anecdotal, but I believe it was real.
What occurred was a serious learning curve for a lot of companies as well as the recognition that while the idea of a common set of automotive quality standards was and is a good idea, not every company expected the same things. The confusion was severe as evidenced by the flurry of interpretations and explanations of the document.
Another failure mode was that QS-9000 was developed mainly with high volume precision manufacturers in mind. This did not stand up as QS-9000 meant different things to manufacturers of different products. For example, transmission parts will have many critical dimensions and tight tolerances while a rubber grommet is quite a bit less. On the other hand, 50 grommets may go in each car in a number of models while for the dashboard manufacturer there was only one per car and may only be used on one platform.
Unfortunately, the document was too specific to be easily understood and applicable to all manufacturers.
What were the Good points about QS-9000?
QS-9000 did provide a good base for a quality system which went into enough technically that if implemented, including (for many, many companies this was problematic) having trained personnel, could not help but to have a positive effect on a company. In the 1980's I became involved in quality assurance in a military manufacturing environment. Most of the QS-9000 requirements were addressed because of the nature of the product - high reliability military electronics for aerospace and marine environments. From this experience I recognized that elements of QS-9000 were good, basic requirements for reliable products. From FMEAs to control plans, none of this was new.
What was new was applying these in a typical company. It was expensive ($500 hammers and toilet seats come to mind). However, again I think it is important to recognize the 'good' aspects of QS-9000.
Why ISO/TS 16949?
About 1998 I was privy in a meeting where what is now TS 16949 was being formulated. There were a number of issues including those addressed above, but in addition the 'Big Three' were recognizing they each had different things they wanted. QS-9000 started out as a 'mutual consortium' of 3 companies. By 1998, as often happens to mutual partnerships in projects between companies, the 'Big Three' wanted to offload the responsibility for the document and end this 'special' relationship.
In addition, there was a lot of pressure from mega companies like Motorola for significant changes. To some extent they extended their influence into the document content and such just as lobbyists do in politics. And remember - Some mega companies even refused to consider QS-9000 registration - Intel is an (admittedly rare) example of this.
Another aspect was that Europe watched as QS-9000 developed and spread. I generally see the following stated as the overall reasoning:
What about the 'Process Approach'?
I won't expound on this much because I see it as silly from the view point of a biologist, which I am by training. Everything is a system so to me it's a 'no brainer'. A company has a billing system of one sort or another which HAS to interact with other parts of the company to function. And if billing does not function, the company cannot exist no differently than a body can live without critical organs.
Summary
In the long run, I'm not so sure it's an issue of QS-9000 failing. I didn't like QS-9000 personally as I felt it was extremely poorly written. But - taking into account the evolution of manufacturing capability and technology in general, it served a purpose, abit an expensive one for many companies. I see ISO 9000 in the same way with the exception that I think the 2000 revision was a poor one where the intent of ISO 9000 changed and in fact absorbed some qs-9000 requirements.
OK, folks. Now it's YOUR turn. Did QS-9000 fail in its objectives? If you believe it did, please take a minute and explain why you think it did or didn't.
If you have any 'official' explaination(s) about Why Qs-9000 was written, Why it failed and/or Why TS 16949, let us know about it/them!
The following is as I understand the events and reasoning. I have nothing 'official'. Bear in mind the following are my opinions and that QS-9000 was written about 10 years ago:> I am putting together a presentation for a client and wanted to provide
> some justification for what QS-9000 was supposed to achieve and hence show
> the reasons for the changes in TS 16949. All I can get from the standard is
> that it was supposed to reduce variation in the supply chain. When I was on
> the TS 16949 working group I heard stories about QS-9000 not fulfilling its
> dream - talk about firms not making the linkages between FMEA, SPC and
> process variation but I have nothing official that I can use. I have looked
> at your site but cannot locate anything relevant. Can you help?
What was QS-9000 REALLY supposed to achieve?
- Reduced customer audits of suppliers - Savings to the supplier by a reduction of audits and savings to the Big 3 by allowing them to reduce SQA personnel (and shifting the cost to the supplier - 3rd party audits paid for by the supplier, of course).
- Bring a common set of certain systems standards to their customers. The word 'harmonzie' is often used.
- Ensure suppliers are following requirements both internal and external.
- Officially: To reduce variation in the supply chain.
The original intent of QS-9000 was to reduce or eliminate multiple supplier audits by the 'Big 3' and to set a 'standard' set of basic requirements including aspects such as design and development via the AIAG's APQP process. This process included additional aspects such as requirements for FMEAs and control plans, as well as several other improvement elements such as an effective nonconformance and corrective action system. The issue of interpretations came heavily into play as did the number of suppliers which did not have anyone in-house who understood many of the requirements. Many companies did not even have someone who really understood the basics of control plan development, FMEAs and such. This said, many companies had never even done SPC and again had no one internally who really understood SPC.
This was combined with many QS-9000 auditors who did not understand the workings of things like control plans themselves, not to mention interactions of the systems as a whole. I should mention here that many customers often had SQAs which, sad to say, did not understand any more than the auditors and their suppliers. I met one QS auditor who was a college prof who 'dropped out'. He had no manufacturing or other business experience. The audit went OK but he was obviously not an appropriate auditor - his understanding of many aspects was lacking including the intracies and applicability of FMEAs and control plans, tying in SPC and such. in some cases, such as where the company had little internal understanding, it was a lot like the old 'blind leading the blind'.
Another reality was the auto makers are really product oriented. Even with QS-9000, customer audits at many companies did not subside as predicated. I was working with Motorola when Ford sent a team in for several days. While QS-9000 was nice to have, Ford really wanted product audits and Q1. In conversations there at the time, it was evident that the number of customer audits did not decline. Admittedly this is anecdotal, but I believe it was real.
What occurred was a serious learning curve for a lot of companies as well as the recognition that while the idea of a common set of automotive quality standards was and is a good idea, not every company expected the same things. The confusion was severe as evidenced by the flurry of interpretations and explanations of the document.
Another failure mode was that QS-9000 was developed mainly with high volume precision manufacturers in mind. This did not stand up as QS-9000 meant different things to manufacturers of different products. For example, transmission parts will have many critical dimensions and tight tolerances while a rubber grommet is quite a bit less. On the other hand, 50 grommets may go in each car in a number of models while for the dashboard manufacturer there was only one per car and may only be used on one platform.
Unfortunately, the document was too specific to be easily understood and applicable to all manufacturers.
What were the Good points about QS-9000?
QS-9000 did provide a good base for a quality system which went into enough technically that if implemented, including (for many, many companies this was problematic) having trained personnel, could not help but to have a positive effect on a company. In the 1980's I became involved in quality assurance in a military manufacturing environment. Most of the QS-9000 requirements were addressed because of the nature of the product - high reliability military electronics for aerospace and marine environments. From this experience I recognized that elements of QS-9000 were good, basic requirements for reliable products. From FMEAs to control plans, none of this was new.
What was new was applying these in a typical company. It was expensive ($500 hammers and toilet seats come to mind). However, again I think it is important to recognize the 'good' aspects of QS-9000.
Why ISO/TS 16949?
About 1998 I was privy in a meeting where what is now TS 16949 was being formulated. There were a number of issues including those addressed above, but in addition the 'Big Three' were recognizing they each had different things they wanted. QS-9000 started out as a 'mutual consortium' of 3 companies. By 1998, as often happens to mutual partnerships in projects between companies, the 'Big Three' wanted to offload the responsibility for the document and end this 'special' relationship.
In addition, there was a lot of pressure from mega companies like Motorola for significant changes. To some extent they extended their influence into the document content and such just as lobbyists do in politics. And remember - Some mega companies even refused to consider QS-9000 registration - Intel is an (admittedly rare) example of this.
Another aspect was that Europe watched as QS-9000 developed and spread. I generally see the following stated as the overall reasoning:
I do not deny this is a large part of the TS movement. However, remember that the Japanese and most Pacific Rim auto manufacturers have not embraced TS 16949 any more than they did QS-9000."16949 harmonizes QS 9000 with European standards for automotive supplier quality systems (VDA, ANFIA and CCFA/FIEV). ISO/TS 16949 has ISO 9001:1994 at its core and also incorporates some of the anticipated changes in ISO 9001:2000. These include increased focus on product realization and resource management.
What about the 'Process Approach'?
I won't expound on this much because I see it as silly from the view point of a biologist, which I am by training. Everything is a system so to me it's a 'no brainer'. A company has a billing system of one sort or another which HAS to interact with other parts of the company to function. And if billing does not function, the company cannot exist no differently than a body can live without critical organs.
Summary
In the long run, I'm not so sure it's an issue of QS-9000 failing. I didn't like QS-9000 personally as I felt it was extremely poorly written. But - taking into account the evolution of manufacturing capability and technology in general, it served a purpose, abit an expensive one for many companies. I see ISO 9000 in the same way with the exception that I think the 2000 revision was a poor one where the intent of ISO 9000 changed and in fact absorbed some qs-9000 requirements.
OK, folks. Now it's YOUR turn. Did QS-9000 fail in its objectives? If you believe it did, please take a minute and explain why you think it did or didn't.
If you have any 'official' explaination(s) about Why Qs-9000 was written, Why it failed and/or Why TS 16949, let us know about it/them!