DVP/DV/PV and Validation Strategy —— Boundaries, Batch Requirements, and Stage Gates

1. DV, PV, DVP: Confusion in Validation Stages Can Lead to Production Failures

The NPI team often talks about "doing validation," but the objectives, batch requirements, and environments for design verification (DV), production verification (PV), and process verification are different. Confusion can lead to:

• Using DV data from hand-made prototypes to report PPAP process capability;
• PV batches completed at a trial mold rate, resulting in a collapse of production FTQ;
• DVP lists not aligned with customer specifications, leading to last-minute testing during audits.

This article clarifies the boundaries, batch requirements, and connections with APQP stage gates for DVP/DV/PV and validation strategy.

2. Key Concept Comparison

Mnemonic: DV verifies if the design is correct; PV verifies if the production line can meet requirements; DVP is the test roadmap.

3. How to Write a Usable DVP

Each DVP test item should include:

1. Test ID and name
2. Verified requirement/specification clause (traceable)
3. Method standard (e.g., ISO, GB, customer TM)
4. Sample size and acceptance criteria
5. Responsible department (design/lab/supplier)
6. Planned completion stage (Alpha/Beta/PPAP, etc.)
7. Actual results and conclusions (filled in upon closure)

Alignment with Customer Specifications: Automotive CSR often specifies the minimum sample size for DV/PV; any missing items must be marked as deviation approval in the PQP.

4. DV Stage: What Must Be Done and What Cannot Be Done

DV Should Cover:

• Function, performance, reliability (per DVP)
• Tests related to special characteristics
• Software/electronic: HIL, EMC, etc. (if applicable)
• Boundary conditions and worst-case combinations

DV Should Not Replace:

• PV at production pace
• Long-term SPC process capability (use PV/initial process study)
• Full-size reports (PPAP elements, batches must represent production intent)

Sample Source: DV can use rapid prototypes, but the report must state the differences and risks compared to production materials/processes.

5. PV Stage: Proving "Production Line Readiness"

PV success criteria typically include:

• Use of production tooling, molds, and fixtures (or customer-approved equivalents)
• Production pace or customer-defined Run@Rate
• Operators following production SOPs
• MSA passing for key characteristics (or customer concession)
• Initial process study Ppk/Cpk meeting CSR
• Full-size and material/function tests completed per PPAP level

Common Failures: PV passes in the trial mold shop, but the first week of production FTQ < 85% — the root cause is that PV does not represent the actual production line.

6. Validation Strategy and APQP Stage Gates

Each Quality Gate should check: DVP closure rate, risks of un-closed items, and whether they affect Go/No-Go decisions.

7. Enhanced Validation for Special Characteristics (SC/CC)

For customer SC/CC or internal KCC:

• Separately list test items in the DVP, do not combine with regular characteristics
• PV batches must include complete data for all SC/CC measurement points
• Control plan and PV data should cross-reference

Auditors often ask: "Was SC tested in DV? Are the PV batches consistent with the sampling in the CP?"

8. Validation Boundaries for Suppliers and Sub-assemblies

• Buy parts: Supplier DV/PV reports should be included in the overall DVP matrix
• Sub-assemblies: Interface verification (dimensions, function, software version) should be clearly defined in the overall DVP, specifying who tests and what is tested
• Avoid OEMs assuming suppliers have "verified" without evidence linkage

9. Documentation and Record Requirements

• DVP versions are controlled and linked to ECNs
• Each test: raw data + conclusion + approval is traceable
• Failure/retest: deviation explanation + impact assessment, original records must not be overwritten
• PPAP package test reports version and batch number should match the PV plan

10. Common Misconceptions and Countermeasures

11. Checklist for PQE

1. Is each DVP item linked to a specification clause?
2. Are DV and PV batches, tooling, and pace clearly stated in the PQP?
3. Is MSA completed before PV?
4. Are PPAP test reports from the PV planned batches?
5. Do un-closed DVP items affect Gate decisions?

12. Relationship Between Run@Rate and PV

Run@Rate (or similar customer requirements) evaluates the sustained output capability at the pace, often planned together with PV:

• Clearly define target pace, duration, and acceptable defect rate
• Use the same or consecutive batches as the initial process study
• No separate "holidays" for equipment OEE, changeover, or material shortages — otherwise, Run@Rate will be inaccurate

Customer audits often cross-check: Run@Rate report batch number = CP sampling batch = PPAP process study data.

13. Validation Strategy Document Package (Recommended for Archiving)

• DVP (controlled version) + compliance matrix (specification clause ↔ test item)
• DV report summary + list of un-closed items
• PV plan + PV report + initial process study
• MSA report (for key gauges)
• Gate review minutes (including DV/PV closure status)

14. Additional Considerations for Software and Electronic Products

• Software version included in DVP (function, regression, cybersecurity if applicable)
• DV can complete some items in HIL/SiL environments, but PV must be replicated on production-representative ECU/test tooling
• OTA updates trigger a subset of validation, which must be defined in the PQP as a regression test package

15. Linking with Think Tank/APQP Materials

It is recommended to cross-read with PFMEA (Material 38), CP (37), PPAP (39) course materials and advanced planning (8.1) articles; PQP serves as the project-level index linking them.

16. Deviation and Retest Rules

When a test fails or a sample is abnormal: do not silently retest. Follow the deviation/concession process, assess the impact on submitted DV/PV conclusions, and if necessary, retrace Gate status and notify the customer.

Medical Devices industry must distinguish design validation (meeting user needs) from DV and maintain cross-references between validation and risk documents in the DMR/DHF; consumer electronics can compress the DV cycle, but PV must align with the production supply chain.

17. PQE Weekly Meeting Validation Status Board

It is recommended to use red, yellow, green to track DVP closure rate, PV batch planning, MSA status, and un-closed deviations — on the same screen as the project weekly meeting to avoid "invisible" quality validation progress. One of the most common reasons for PPAP rejection is inconsistent test batches with the plan; the weekly meeting board should explicitly list PPAP deadlines and PV completion dates.

The essence of validation strategy is to answer the right questions at the right time with the right batches — not to pile up test reports.

The litmus test for PV: Can the capability in PPAP be replicated on a different production line or with a different shift of operators?

Knowledge code: 8.2.3

Version: v20260702

Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic knowledge, methodologies, and practical tools for quality management professionals, helping companies continuously improve their quality capabilities.