DVP/DV/PV and Verification Strategy —— Boundaries, Batches, and Stage Gates for Design and Production Verification

One: Confusion in DV, PV, DVP Verification Stages Can Derail Mass Production

NPI teams often casually mention “doing verification,” but the goals, batches, and environments for Design Verification (DV), Production Verification (PV), and Process Verification are distinct. Confusion can lead to:

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

This article clarifies the boundaries, batch requirements, and alignment with APQP stage gates for DVP/DV/PV and verification strategies.

Two: Core Concept Comparison

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

Three: 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/pre-PPAP, etc.)
7. Actual results and conclusions (filled upon closure)

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

Four: What Must Be Done and What Cannot Be Done in the DV Stage

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 studies)
• Full-size reports (PPAP element, batch must represent production intent)

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

Five: PV Stage: Proving “Production Line Readiness”

PV success criteria typically include:

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

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

Six: Verification Strategy and APQP Stage Gates

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

Seven: Enhanced Verification 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 plans and PV data should cross-reference

Auditors often ask: “Was SC tested in DV? Are the PV batch samples consistent with CP sampling?”

Eight: Verification Boundaries for Suppliers and Subassemblies

• Buy Parts: Supplier DV/PV reports should be included in the assembly DVP matrix
• Subassemblies: Interface verification (dimensions, function, software version) should be clearly defined in the assembly DVP, specifying who tests and what is tested
• Avoid OEMs assuming suppliers have “verified” without evidence linkage

Nine: Documentation and Record Requirements

• DVP versions are controlled and linked to ECN
• Each test: raw data + conclusions + approval must be traceable
• Failures/retests: deviation explanation + impact assessment, do not overwrite original records
• PPAP test reports version and batch number should match PV planning

Ten: Common Misconceptions and Countermeasures

Eleven: Checklist for PQE

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

Twelve: Relationship Between Run@Rate and PV

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

• Clearly define target pace, duration, and acceptable defect rate
• Use the same batch or consecutive batches as initial process studies
• 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.

Thirteen: Verification Strategy Document Package (Recommended for Archiving)

• DVP (controlled version) + compliance matrix (specification clauses ↔ test items)
• DV report summary + list of unclosed items
• PV planning + PV report + initial process studies
• MSA report (for critical gauges)
• Gate review minutes (including DV/PV closure status)

Fourteen: Additional Considerations for Software and Electronic Products

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

Fifteen: Linking with Knowledge Base and 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 connecting them.

Sixteen: 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-referencing of verification and risk documents in DMR/DHF; consumer electronics can compress the DV cycle, but PV must align with the production supply chain and cannot be skipped.

Seventeen: PQE Weekly Meeting Verification Status Board

It is suggested to use red, yellow, green to track DVP closure rates, PV batch plans, MSA status, and unclosed deviations — on the same screen as project weekly meetings to avoid “invisible” quality verification progress. One of the most common reasons for PPAP rejection is inconsistent test batches with planning; the weekly status board should explicitly list PPAP deadlines and PV completion dates.

The essence of verification strategy is answering the right questions at the right time with the right batches — not just piling up test reports.

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

Knowledge Number: 8.2.3

Version: v20260702

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