I'm in the process of setting up an APQP style system in a company that is not an automotive supplier. My previous job as a QE for a tier 1 automotive supplier, the APQP system was accepted without question. The resistance I am running into is that the un converted think it is just another layer of paper. Does any one have any tips that will help point out the advantages of having a robust APQP system? Thanks.


Jim Thomson
SLC, Utah

The automotive APQP system is a proven failure. Do advance planning, do preventive failure analysis, do real process control, but my advice is to leave the AIAG stuff to the B3 as they hurtle down the tubes.

I'm in the process of setting up an APQP style system in a company that is not an automotive supplier. My previous job as a QE for a tier 1 automotive supplier, the APQP system was accepted without question. The resistance I am running into is that the un converted think it is just another layer of paper. Does any one have any tips that will help point out the advantages of having a robust APQP system? Thanks.


Jim Thomson
SLC, Utah

Look at it from a cost/benefit view. Part of APQP is good preventative quality, and part is bureaucratic red tape. Pick what would benefit your company the most.

Do you have field reliability issues with new product? Use DFMEA. Do you have out-of-the-box quality issues? Look at PFMEA. Supplier launch problems? Look at PPAP (streamlined version).

If you slowly introduce the basic elements, and the company sees the benefit, or the relationship to current problems, they will accept it easier.

I'm in the process of setting up an APQP style system in a company that is not an automotive supplier. My previous job as a QE for a tier 1 automotive supplier, the APQP system was accepted without question. The resistance I am running into is that the un converted think it is just another layer of paper. Does any one have any tips that will help point out the advantages of having a robust APQP system? Thanks.

Why do you want to introduce this? What is wrong the existing system?


The automotive APQP system is a proven failure. Do advance planning, do preventive failure analysis, do real process control, but my advice is to leave the AIAG stuff to the B3 as they hurtle down the tubes.
:mg: blasphemy:agree1:
Jim Thomson: Do you agree from your experience? or is your experience that APQP is too little too late and too shallow, you cannot get DFMEA to do your PFMEA and the only training that is given is how to use the customers reporting tool.

APQP is a model for project management but use what is needed otherwise you will introduce another layer of paper

Thank you for the responses. As for the company I work for now, they are transitioning from a "craft shop" to a high volume production shop. There is a lot of tribal knowledge that I would like to capture and standardize. I agree that adding another layer of paper will be useless but on the one product I have worked on, just working through the PFMEA and control plan has proved useful in highlighting areas that need improvement. I think that once I convince people that the system is useful, more people will jump on board. Also, our director of quality is out of Delphi and wants this implemented across all product lines. When the big guy speaks, people listen. Thanks again.

Jim Thomson
SLC, Utah

If you want to implement this system you may want to start with certain tools and develop from there. I have seen this mostly work in the R&D group and evolve up from there. FMEAs are very useful at documenting problems, ideas and control plans to prevent failures. I would work on this first. But, I must agree that adding this system as a whole - if the customer doesn't require it, may be cost prohibitive. Good luck

I'm in the process of setting up an APQP style system in a company that is not an automotive supplier. My previous job as a QE for a tier 1 automotive supplier, the APQP system was accepted without question. The resistance I am running into is that the un converted think it is just another layer of paper. Does any one have any tips that will help point out the advantages of having a robust APQP system? Thanks.Jim ThomsonSLC, Utah

Hi Jim

My ideas to help sell it would be

1) Don't call it APQP, too much baggage with that word, call in new product development, project managment, but avoid the Q word. As soon as people hear the Q word, they think "not my problem - Quality can take care of that"

2) I support the others, take only the stuff that makes sense to you and do it well. Do the rest later, if ever

3) Finally I always have a list of past failure$ that I can link to APqP. I sell with that. "Hey, that field failure cost us big $, perhaps if we had done validation testing we could have prevented that...if we had a system...like APqP."

It sometimes takes years...before they can hear what you are saying