Discussion in 'APQP and PPAP' started by Celeste, Aug 11, 2015.
What is the difference between APQP and contract review? They seem to overlap quite a bit.
As far as I could see, APQP is creating the processes needed to make a particular product, more than likely for the automotive industry. Contract review is geared more towards what the customer wants and requires, customer specifications, purchase orders, etc.
Contract review should be done during APQP to ensure that the customer's expectations and specifications are part of the planning process. Part of APQP is to review those specs and requirements, in addition to production planning, design considerations, etc. APQP encompasses anything that plays any kind of role in producing a part for a customer.
Hope this helps!
That is what I think as well. From your experience, are all the chapters (phases) of APQP done prior to the RFQ or just phase 1 and 2.
Mostly, what we do as a part of the RFQ process is a feasibility analysis and making sure we have all the relevant information to make an effective analysis. The remaining phases we do after we are awarded the part(s). A lot of what is done during the RFQ process depends on your customer's requirements.
I would like to think this is how most companies operate, and in fact, many companies will recognize their core business processes and have generic quality plans as baseline starters for customer specific plans. That way when the RFQ and feasibility are completed, it could be matched up to a generic baseline process and expanded on from there as needed. APQP could be as simple as the customer wants you to preform a core process to your business with the expected outcomes predetermined. Standard service vs. Customer Specific service. Don't re-create the wheel every time if you do not have to.
Normally, after finishing contract review and approved by management, we start the APQP
From my experience contract review would be carried out first - once you have established what the customer requires and feasibility of this, the APQP process would then take over throughout the product lifecycle from development through to production.
You can then tie in the design reviews or stage gates to the contract reviews and feedback to the customer - i found this part to be particularly important when changes are required and ensuring approval from all parties was established before moving onto the next element
Contract review is more of a process step where as APQP is for want of a better explanation, a framework
Separate names with a comma.