What APQP and PPAP mean for an Indian supplier
Answer first: APQP (Advanced Product Quality Planning) is the timing plan a supplier runs from feasibility sign-off through product and process validation, gate by gate, aligned to the OEM's start-of-production (SOP) date. PPAP (Production Part Approval Process) is what APQP produces at the end — a document-backed submission package of up to 18 elements plus the Part Submission Warrant (PSW), asking the customer for approval to ship. For a Tier-1 or Tier-2 in Pune, Chennai, Gurgaon or Sanand, neither is optional: every Indian OEM, from Maruti Suzuki and Tata Motors to Bajaj, Hero, Ashok Leyland and Toyota Kirloskar, requires both before a new part is built in volume.
Keep the distinction simple: APQP is the plan; PPAP is the proof. A program can be well inside its APQP timing and still fail PPAP if the core-tool records don't hold up.
APQP: a stage-gated timing plan to SOP
APQP opens with a manufacturing-feasibility commitment, then runs five further phases to launch. Each gate has an owner, a target date and an actual date — the gap between the two is where a launch quietly slips.
A program dashboard showing every gate's owner, target and actual date — overdue gates flagged rather than buried in a status meeting — is what separates a plan being run from a Gantt chart mailed around. See What is APQP and automotive quality core tools.
Customer-specific requirements — what Indian OEMs add on top of IATF
IATF 16949 sets the baseline. In India, every OEM layers its own customer-specific requirements (CSRs) on top — its own vendor portal, document formats, submission-level defaults and escalation path for a missed gate. A supplier selling to more than one OEM runs several parallel rulebooks against the same core skeleton.
The Indian OEM landscape a Tier-1 or Tier-2 typically deals with:
- Maruti Suzuki — India's largest carmaker, with a strict supplier-quality regime and its own vendor portal.
- Tata Motors and Mahindra & Mahindra — detailed CSR sets across passenger and commercial vehicle lines.
- Bajaj Auto, Hero MotoCorp, TVS Motor — two-wheeler OEMs with their own PPAP formats and faster refresh cycles.
- Ashok Leyland and VE Commercial Vehicles — commercial-vehicle CSRs, heavier on durability data.
- Hyundai Motor India, Toyota Kirloskar, Kia India — global-parent CSRs, where AIAG-VDA alignment shows up most.
Each CSR answers the same questions differently — default submission level, run-at-rate expectations, which portal, how a missed gate is escalated — so treat the CSR, not this guide, as definitive. See IATF 16949 certification in India and automotive & IATF 16949 quality software.
PPAP: the 18 elements and the PSW
A full AIAG PPAP package is built from up to 18 elements, each a controlled document with its own approval status, closed out by the Part Submission Warrant (PSW) — the single-page summary stating the submission reason, level and whether the part meets all requirements.
Design & engineering evidence
- Design records (drawings, CAD data)
- Engineering change documents
- Customer engineering approval
Core tools & process evidence
- Design FMEA (DFMEA)
- Process flow diagram
- Process FMEA (PFMEA)
- Control plan
- Measurement System Analysis (MSA)
Parts & measurement evidence
- Dimensional results
- Material and performance test results
- Initial process studies (capability from run-at-rate)
- Qualified laboratory documentation
Samples, aids & sign-off
- Appearance Approval Report (AAR, where applicable)
- Sample production parts
- Master sample
- Checking aids
- Records of compliance with customer-specific requirements
- Part Submission Warrant (PSW)
Not every element applies to every part, but every applicable one needs a controlled, revision-tracked home. See What is PPAP for a fuller breakdown.
PPAP submission levels 1–5
AIAG defines five submission levels; the level sets how much of the 18-element package actually leaves the supplier versus stays on file, ready on request.
| Level | PSW | Product samples | Full supporting data | Typical use |
|---|---|---|---|---|
| Level 1 | Submitted | Retained | Retained | Low-risk parts, minor running changes |
| Level 2 | Submitted | Submitted | Limited data submitted | Moderate-risk parts by customer request |
| Level 3 | Submitted | Submitted | Submitted | The common default for most Indian OEMs |
| Level 4 | Customer-defined requirements | Whatever the specific CSR states | ||
| Level 5 | Submitted | Submitted | Reviewed at supplier's site | High-risk parts or new suppliers, on-site review |
Level 3 is the practical default across most Indian passenger- and commercial-vehicle programs, with Levels 1 and 5 handled as exceptions. The level for a given part is stated on the customer's PPAP request or CSR; it is not the supplier's choice.
Run-at-rate: proving the process before approval
A run-at-rate, or significant production run, is a continuous run — typically around 300 consecutive parts, or one to eight hours, figures that vary by OEM and part — made with the actual production tooling, process and cycle time meant for series production, not a lab setup or hand-picked samples. It is where the dimensional results, initial process capability (Cp/Cpk) and packaging evidence in the PPAP package come from.
Still assembling PPAP from folders on a shared drive?
See a live APQP program with owner/target/actual dates per gate, and a PPAP package where every element is a controlled document tracked to Accepted — in 30 minutes.
AIAG PPAP 4th edition vs AIAG-VDA in India
Most Indian Tier-1 and Tier-2 suppliers still work to AIAG PPAP 4th edition — the baseline most Indian OEM CSRs reference, and the 18-element structure above is the AIAG structure. A growing number of OEMs and joint ventures with European or global parents are moving specific programs to the AIAG-VDA FMEA handbook, particularly where a global engineering centre sets the standard.
This is a program-by-program decision, not an industry-wide switch: the same supplier may run pure AIAG PPAP on one customer's program and AIAG-VDA scoring (severity/occurrence/detection, 1–10, with an Action Priority rather than a single RPN) on another. Read the CSR before assuming either — see automotive quality core tools.
OEM portals, Tier-2 flow-down, and the loose-folder problem
Many Indian OEMs require the finished PPAP package uploaded to their own supplier portal, so the real work is upstream — assembling and internally approving the full pack before a file reaches the portal. It compounds down the chain: a Tier-1 must collect its sub-supplier's PPAP first, and a Tier-2 serving several Tier-1s runs this in parallel, in different formats each time. The everyday failure modes are consistent:
- PPAP kept as loose folders on a shared drive, no single owner, no record of which version was actually submitted.
- Chasing sub-suppliers for component PPAP every audit or deadline, with no standing tracker of what was owed.
- Re-submission chaos on every engineering change — nobody can say with confidence which control plan, FMEA and PPAP elements are now out of date.
The fix is structural: PPAP version-controlled from day one, submission level tracked per customer, re-PPAP triggered the moment a change is approved.
When one engineering change touches three PPAP packages
A Pune Tier-2 machines a bracket for a Chennai Tier-1's sub-assembly on Level 3 PPAP. A mid-life change moves one hole by 0.3 mm. On a shared drive this is a scramble over which revision is current. Tracked as a change, the request flags the affected FMEA line, the gauge is re-checked, and a re-PPAP is raised against the exact package it supersedes — one clean submission, not three conflicting folders.
How Fast Quality Software runs APQP & PPAP
Fast Quality Software, from Fast Technology / Improsys in Pune, runs cloud or on-premise, standalone or bundled in the Fast Suite. Mapped to the problems above:
Reference deployments include Nikhtish Engineering, Micro India, Kakade Laser and Shree Engineering. See quality software pricing, automotive & IATF 16949 quality software, and the foundational what is quality management software.
Frequently asked questions
What is the difference between APQP and PPAP?
APQP is the timing plan running from feasibility sign-off through product and process validation, gate by gate, toward the OEM's start-of-production date. PPAP is what that plan produces at the end — a document-backed package of up to 18 elements plus the Part Submission Warrant (PSW), proving the part and process are ready to ship.
What are the PPAP submission levels, and which one do Indian OEMs usually ask for?
AIAG defines five levels. Level 1 is PSW only. Level 2 adds product samples and limited data. Level 3 is PSW, samples and full supporting data — the common default most Indian OEMs and Tier-1s request. Level 4 is whatever the customer defines. Level 5 is reviewed at the supplier's own site rather than mailed in. The purchase order or CSR states which level applies.
What is a run-at-rate, and why does it matter for PPAP approval?
A run-at-rate, also called a significant production run, is a continuous run — typically around 300 consecutive parts, or one to eight hours, figures that vary by OEM and part — made with the actual production tooling and rate intended for series production. It generates the dimensional results, process capability and packaging evidence in the PPAP package, proving the process holds up at rate, not just on a handful of first-off samples.
Is PPAP in India still based on AIAG's 4th edition, or has AIAG-VDA taken over?
Most Indian Tier-1 and Tier-2 suppliers still work to AIAG PPAP 4th edition, the baseline most Indian OEM CSRs reference. A growing number of OEMs and joint ventures with European or global parents are moving specific programs to AIAG-VDA FMEA and, sometimes, AIAG-VDA-aligned submission requirements — so the CSR for that customer and program is the definitive source, not a blanket switch.
What happens to an approved PPAP when there is an engineering change?
An approved PPAP is only valid for the part, process and specifications it was submitted against. Any engineering change — a drawing revision, a process change, a new tool, a relocated line, a sub-supplier change — that affects form, fit, function or the original package's documents requires a change request, impact assessed against the FMEA and control plan, and, once approved, a re-submission of PPAP (full or partial, per the customer's requirement) before the changed part can ship.