VDA 2 Production Process and Product Approval (PPA)

VDA 2 Production Process and Product Approval (PPA)

1. What Is VDA 2 Production Process and Product Approval (PPA)?

VDA 2 Production Process and Product Approval (PPA) is an operational quality framework for demonstrating that a product and its production process meet agreed requirements before series delivery. It connects two questions: “Does the product conform?” and “Can the production process consistently manufacture it as required?” It is a release procedure, not simply a sample inspection.

VDA stands for Verband der Automobilindustrie, the German Association of the Automotive Industry. 2 identifies the publication volume. PPA means Production Process and Product Approval, encompassing both manufacturing readiness and product conformity.

For automotive component suppliers, the executive value is a disciplined decision about launch readiness: which evidence supports release, which gaps require intervention, and which production configurations the evidence actually covers.

2. Origin and Background

Origin: VDA, whose first Volume 2 appeared in 1975. It established common guidance for assessing supplier quality capability, inspecting initial samples, and evaluating incoming series parts. Successive editions developed this into a more explicit approval procedure for new and modified deliveries. The framework originated in automotive supply relationships rather than being adapted from a general management model.

The latest published edition is the seventh revised edition, September 2026. The sixth edition, April 2020, emphasized customer–supplier agreement and removed standard submission levels. The seventh strengthens risk-based selection of necessary deliverables, permits referencing existing evidence, and streamlines documentation. Teams should establish which edition and customer-specific requirements govern their engagement rather than automatically applying an old checklist—or assuming publication alone changes their contract.

3. How VDA 2 Production Process and Product Approval (PPA) Works

PPA connects requirements, verification, internal assessment, and customer evaluation. Its logic is straightforward: establish what must be demonstrated, generate credible evidence, evaluate gaps, and document the release decision. Scope, content, and timing should be agreed with the customer before execution.

Production process: Can manufacturing repeat the result?

Process approval addresses reproducibility, production quality, and agreed capacity under series conditions. Evidence should represent the intended production location, equipment, tooling, personnel, process flow, and supporting logistics—not an exceptional engineering build assembled through undocumented adjustments.

Product: Does the delivered configuration conform?

Product evidence demonstrates conformity to applicable specifications. Depending on the component, this may involve dimensions, materials, function, reliability, cleanliness, electrical characteristics, or software requirements. A battery enclosure and an electronic control unit require different verification plans; neither should inherit an irrelevant generic evidence package.

Approval: Does the evidence justify release?

The organization evaluates its evidence and performs its internal release activities; the customer evaluates the agreed submission and records its decision. Reduced submission does not mean reduced responsibility for generating and retaining necessary evidence. Supplier quality-system certification is also distinct from product-specific approval.

For management purposes, define the approval object as a specific part revision and manufacturing configuration. Split tooling, cavities, sites, or variants where differences could affect conformity. Treat sub-supplier evidence and outsourced operations as dependencies, not administrative attachments.

4. When to Use VDA 2 Production Process and Product Approval (PPA)

Use PPA for new parts and for product or production changes that require approval under the applicable customer rules. Relevant situations can include material substitutions, production transfers, tooling changes, and changes in sub-tier supply. Notification requirements and approval triggers can differ by customer; a change notification does not establish permission to implement the change.

It is especially powerful when launch pressure could otherwise obscure unresolved manufacturing risks. It helps structure decisions such as whether to release a second production line, postpone a tooling transfer, or require further validation before changing a material source.

PPA is not a tool for selecting vehicle markets, setting prices, or evaluating mobility-service business models. For low-volume components, agree a defensible verification approach rather than forcing statistically weak capability conclusions from insufficient observations.

Plan cross-functional involvement from engineering, manufacturing, quality, purchasing, logistics, and relevant software specialists. Useful inputs include controlled specifications, validation results, measurement evidence, capacity studies, and supply-chain approval status. Build the calendar around tooling availability, laboratory lead times, corrective work, and customer review—not around how quickly a presentation can be assembled.

5. How to Apply VDA 2 Production Process and Product Approval (PPA): Step-by-Step

  1. Clarify the decision and governing requirements.

    Specify whether the decision concerns a new launch, engineering change, additional source, or production transfer. Identify the applicable edition, customer requirements, intended delivery date, approval authority, and affected sites. Separate internal readiness milestones from customer authorization.

  2. Gather controlled inputs.

    Collect the current drawing or specification, approved changes, process flow, validation plan, inspection methods, production data, and sub-supplier status. Reconcile revision discrepancies before testing. For electronic products, include the relevant hardware and software configuration and agreed quality requirements.

  3. Define the approval objects.

    Map part numbers and revisions to production sites, lines, tools, cavities, and variants. Identify where evidence can reasonably be shared and where separate verification is needed. Do not assume that a common commercial part number establishes manufacturing equivalence.

  4. Construct the evidence plan.

    Create a requirements-to-evidence matrix showing each requirement, verification method, acceptance criterion, configuration, owner, due date, and submission arrangement. Link controlled source documents. This management artifact should make missing evidence visible without becoming a substitute for the required PPA documentation.

  5. Execute representative verification.

    Run the agreed production validation under series conditions and preserve the connection between samples, configurations, and results. Establish measurement suitability before interpreting conformity or capability. Assess quality and capacity separately: sufficient output does not demonstrate acceptable quality.

  6. Translate findings into decisions.

    Classify gaps by their effect on conformity and release readiness. Assign corrective actions, resources, and verification dates. Distinguish internal assessment from the customer’s decision, and follow the applicable formal arrangements for deviations rather than creating an informal “conditional approval” category.

  7. Test assumptions and sensitivities.

    Challenge whether the evidence remains persuasive across expected shifts, material lots, tool wear, variant mix, and production demand. Use these questions to strengthen verification—not to relax agreed acceptance criteria. Record which assumptions would trigger renewed assessment.

  8. Align stakeholders and maintain the baseline.

    Review unresolved items jointly with accountable functions and the customer interface. Resolve disagreements about scope before submission. After release, maintain configuration history, evidence traceability, and change-control responsibilities so later modifications do not silently invalidate the approved baseline.

Where several plants and sub-suppliers have open evidence items, program management support can establish one closure plan, dependency log, and escalation cadence. Coordination supports the responsible technical teams; it does not confer approval authority.

6. Example: VDA 2 Production Process and Product Approval (PPA) in Action

Fictional example: Northbridge Thermal Systems supplies battery cooling plates to a passenger vehicle OEM. It plans to transfer production to a second plant while maintaining the existing product design. Management wants uninterrupted supply, but the new welding fixtures and leak-test equipment differ from those at the approved site.

The team selects PPA to structure the release decision. It agrees the verification scope with the customer and defines each plate variant, welding fixture, and production location as an evidence boundary. Inputs include dimensional results, weld verification, leak-test validation, process performance, capacity evidence, and purchased-material approval status.

Trial parts meet dimensional requirements, but the team discovers inconsistent leak-test results between stations. The dimensional report alone therefore cannot justify release. Further investigation identifies fixture sealing variation that compromises measurement reliability.

Northbridge keeps deliveries on the existing approved route while correcting the new configuration. The follow-on work focuses on quality control improvement: validating the inspection method, improving fixture maintenance, strengthening reaction plans, and training operators. It repeats affected verification, completes internal assessment, and submits the agreed evidence for customer approval.

The insight is not “the paperwork was incomplete.” It is that the proposed release lacked dependable evidence of conformity.

7. Strengths and Limitations

Strengths

  • Connects product and process readiness. A conforming sample cannot conceal an inadequately demonstrated production process.
  • Clarifies release dependencies. Executives can distinguish tooling, testing, capacity, and sub-supplier issues instead of debating a single readiness percentage.
  • Supports proportionate evidence. The seventh edition’s risk-based approach encourages necessary, relevant deliverables rather than documentation volume as an end in itself.

Limitations

Approval evidence represents defined configurations and conditions. Treating it as a permanent guarantee can create false confidence when production conditions change. A management dashboard should therefore expose evidence boundaries and unresolved assumptions.

PPA also does not replace the separate software-development, functional-safety, cybersecurity, or regulatory work applicable to a product. These disciplines may contribute evidence to approval, but they address questions that a manufacturing release package alone cannot resolve.

Finally, the framework exposes gaps; it does not itself repair tooling, improve measurement, train operators, or secure laboratory capacity. Its value depends on execution.

8. Common Pitfalls and How to Avoid Them

  • Starting with an obsolete template. Familiar forms can embed superseded assumptions. Confirm the governing edition and customer requirements before defining the evidence plan.
  • Pooling unlike production streams. Combined results can hide a weak cavity, fixture, or line. Preserve traceability and demonstrate equivalence before sharing evidence.
  • Confusing documents with proof. A completed report may contain irrelevant or unreliable results. Review acceptance criteria, configuration coverage, and measurement validity—not just file presence.
  • Using specially prepared samples. Engineering intervention can make results unrepresentative. Require transparent production records and document departures from the intended series process.
  • Misreading a submission waiver. A customer’s decision not to receive particular evidence does not remove the organization’s documentation responsibility. Maintain the underlying verification records.
  • Stopping at the gap list. Assign funded actions and named owners. Track technical closure separately from customer review and authorization.

9. How VDA 2 Production Process and Product Approval (PPA) Relates to Other Frameworks

APQP and failure analysis: Prepare the evidence

Advanced Product Quality Planning (APQP) organizes product and process quality planning upstream. Failure Mode and Effects Analysis (FMEA) identifies potential product and process failures. Use them before and alongside PPA: planning and risk analysis should shape verification, not be reconstructed after samples fail.

The Automotive Industry Action Group’s Production Part Approval Process (PPAP) also addresses production-part conformity and manufacturing capability. The purposes overlap, but teams should not assume that forms, submission arrangements, or approval conventions are interchangeable. Use the route required by the customer and map reusable evidence explicitly.

VDA 6.3: Examine process effectiveness

VDA 6.3 process auditing evaluates development and production processes. Prefer an audit when the question concerns how effectively the process operates; use PPA when the question concerns approval of a defined product and manufacturing scope. Audit findings can inform the evidence and corrective work needed for release.

10. Key Takeaways

  • PPA connects product conformity with production-process readiness; it is more than sample inspection.
  • Define precisely which revision, site, tooling, and variants the evidence covers.
  • Agree scope and timing early; necessary evidence matters more than document volume.
  • Convert gaps into corrective work, accountable decisions, and controlled release—not merely a dashboard.
  • Maintain the approved baseline and reassess relevant changes.

11. FAQs About VDA 2 Production Process and Product Approval (PPA)

Is VDA 2 PPA the same as PPAP?

No. They have closely related approval objectives, but their procedures and submission arrangements differ. Follow the customer-required route; reuse valid technical evidence only where its applicability and acceptance are established.

Which VDA 2 edition should we use?

The latest published edition is the seventh revised edition, September 2026. Establish its applicability with the customer, including contractual references and customer-specific requirements. Do not silently mix requirements or forms from different editions.

Does IATF 16949 certification replace PPA?

No. Certification concerns the quality management system; PPA concerns evidence and approval for a particular product and production scope. A certified supplier still needs to satisfy the applicable customer approval requirements.

What should a smaller supplier prioritize first?

Start with controlled requirements, clear configuration boundaries, trustworthy measurement, representative production evidence, and visible ownership of gaps. Keep the tracking system simple, but agree the necessary verification with the customer rather than reducing it unilaterally.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]