Every build in a hardware programme exists to answer a question, and the parts inside it decide whether the answer can be trusted. An engineering build needs freedom to change things. A design validation build needs units that represent the product you intend to certify. A production validation build needs the real supply chain, on the real line. When purchasing runs on its own timetable, a team can pass its tests on a product it will never manufacture, and only find out when the first production lots behave differently.
This guide sets out how buying should change at each stage. For the wider difference between prototype and production work, see prototype versus production manufacturing.
EVT, DVT and PVT are conventions, not a standard
No standards body defines these stages. They are industry habit, and companies disagree even on whether the V stands for verification or validation. One published reference is Instrumental's guide to engineering builds (the PDF on its site dates from 2020), which describes them roughly like this:
- EVT (engineering validation test): the first build that combines the looks-like and works-like designs in one form factor, using production-intent materials and processes. Its exit is one configuration that meets the functional, performance and reliability requirements.
- DVT (design validation test): one configuration of the production-worthy design, made from parts off production tools and assembled on a line that follows production procedures.
- PVT (production validation test): a build to prove mass-production yields at mass-production speeds, with units intended for sale if they pass.
The same guide gives typical quantities of 100 to 1,000 units for EVT, 300 to 2,000 for DVT and 1,000 to 20,000 for PVT. Those ranges reflect high-volume consumer hardware. Many smaller programmes build far fewer units at each stage, which is fine as long as the test plan is covered.
Because the terms are loose, write your own gate charter. For each build it should name the required documents, the unit quantity and where each unit goes, the tests, the yield threshold and who signs the exit.
Issue one material baseline per build
Before any parts are ordered for a build, issue a dated package that defines it:
- the released BOM revision and approved vendor list;
- PCB fabrication and assembly data;
- mechanical drawings and finish requirements;
- firmware version and programming checksum;
- approved deviations and substitutions;
- build quantity and the unit allocation plan;
- incoming, in-process and final test instructions;
- the serial-number range the package applies to.
The buyer sources against that package and nothing else. If engineering changes a part, an approved change or deviation is raised before the new material enters the build. The paperwork is what lets you say later which configuration produced which result.
EVT: buy to learn, but buy the real parts
EVT exposes design weaknesses. Expect board rework, firmware changes and possibly a respin, and keep inventory exposure small accordingly. A few rules hold up well:
- Buy the exact production part numbers for anything the architecture depends on, even when a cheaper look-alike is in stock.
- Use authorised distributor stock for small quantities, so the parts are traceable.
- Record every substitute, bodge wire, removed part and value change against the unit's serial number.
- Look for alternates now for parts with a poor lifecycle or lead-time outlook.
- Reserve the long-lead parts that DVT will need, without buying the whole forecast.
Evaluation boards or hand-modified parts are fine for debugging, but label the units that contain them. They cannot later become evidence for a production-intent requirement.
EVT is also the cheapest moment to screen for obsolescence. IEC 62402:2019 treats obsolescence management as a process across an item's whole life and includes design strategies for it. Swapping a risky IC before DVT costs a respin; swapping it after certification can cost the certification. The guide to handling obsolete components covers what to do when it is already too late.
Close EVT with a known-good BOM revision, an open-risk list, test and failure-analysis results, recommended DVT quantities and a list of changes. Parts arriving is not a reason to start DVT.
DVT: the parts must represent what you will certify
DVT shows whether the intended product meets its requirements. Units are split across electrical, thermal, environmental, reliability, mechanical, firmware, safety and EMC tests, and the BOM should be released or very close to it.
Compliance-critical items need the most care: plastics, insulation, power supplies, batteries, fuses, relays and safety capacitors. They must match the configuration that goes to the test laboratory. UL Solutions says it evaluates representative samples of components and subassemblies and runs follow-up services to confirm continued compliance, so the parts you submit set expectations for production. In India, BIS's CRS FAQ allows a pre-certified safety-critical component of the same rating from another source to be used after intimating BIS, but requires retesting when the circuit, design or component changes. A shortage-driven substitution after DVT can therefore reopen testing. The consumer-electronics sourcing guide explains how that registration works.
Allocate units before you buy
Start from the test matrix, not a round number. One unit cannot go through two destructive tests. The allocation below is illustrative, for a small wearable:
| Test group | Units | Destructive? |
|---|---|---|
| Functional and performance | 8 | No |
| Thermal and power | 4 | No |
| EMC and safety pre-compliance | 6 | No |
| Drop, vibration and ingress | 10 | Yes |
| Reliability and life | 10 | Yes |
| Firmware and interoperability | 6 | No |
| Failure analysis and retest reserve | 6 | Partly |
| Retained reference units | 4 | No |
That is 54 tested units. If the team expects 10 per cent of assembled units to fail before test (again, an assumption for the example), it needs to build 60, because 60 less 10 per cent leaves 54.
Freeze substitutions
During DVT, every substitution goes through engineering, quality, compliance and programme approval. The approval should state which tests must be repeated and which serial numbers contain the change.
PVT: the purchasing process is under test too
PVT moves the focus from the design to the factory. The build uses the intended contract manufacturer, equipment, tooling, operators, work instructions, test fixtures and suppliers. Material rules tighten:
- Buy only against the released BOM and the approved vendor list.
- Use normal production packaging and normal kitting.
- Receive every line through the intended incoming inspection.
- Keep manufacturer, distributor, lot or date code and PO details linked to each unit.
- Program and serialise at production speed.
- Measure actual setup loss and placement attrition instead of assuming it.
Any part on hand-converted packaging, from an unapproved source or fitted under an undocumented substitute, is a recorded deviation. A PVT that needs constant engineering intervention has not shown a stable process.
Capture first-pass yield, a defect Pareto, false test failures, rework, scrap and cycle time, and link defects to component lot, machine, feeder, shift and serial number where you can. That separates design weakness from process variation and from a bad supplier lot. PVT also tests purchasing itself: order acknowledgements, scheduled deliveries, shortage escalation, incoming labels, storage, line-side replenishment and the routing of change notices.
Pilot: prove the operating chain
Some teams treat pilot and PVT as the same build; others run a larger pilot afterwards. Either is fine if the plan says which. A pilot should exercise the whole operating model: the signal from forecast to purchase order, supplier and assembler capacity, the normal import and customs route, lot-to-serial genealogy, final inspection and release, packaging and dispatch, spares for service, and the loop that brings field failures back to engineering.
Pilot units should be saleable unless the plan says otherwise. Quarantine any engineering units still around and give them a distinct serial range.
Quantities: work from the plan, round at the end
Work out units first. Gross units equal build-to-test units, plus destructive-test units, certification and customer samples, retained units and a yield allowance, minus usable stock from earlier builds that is still under control. For each component line, multiply gross units by quantity per unit, add line-specific loss and subtract confirmed usable inventory.
Round up to MOQ, standard pack or a machine-ready format only at the very end. A 0201 capacitor, a BGA processor, a custom cable and a display lose material in completely different ways, so one scrap percentage across the BOM will be wrong for most lines. For the packaging and rounding decisions in small quantities, see low-volume component sourcing.
Buying ahead of a gate
Long-lead parts often have to be ordered before the gate that would justify them. Make that a recorded decision, not a habit. The record should cover:
- how confident the team is in the design, and which test risks remain;
- how likely a change is, and whether an alternate would fit;
- quantity, cash exposure and cancellation terms;
- shelf life, storage and lifecycle concerns;
- whether another product could use the parts;
- who approved it.
The options range from a small risk buy to a supplier reservation, a scheduled release or a blanket order. Whatever is chosen, keep speculative stock visibly separate from confirmed production demand.
What to ask suppliers and the EMS partner before each build
- Which BOM and approved vendor list revision is this quote based on?
- Which lines are not from an authorised source? Under SAE AS6496, as ECIA summarises it, a distributor must say so in writing when it quotes.
- Is each line on the shelf, allocated, inbound or on factory lead time?
- What are the MOQ, pack, packaging and NCNR terms?
- Which component lots will go into this build?
- How are substitutes and deviations approved, and by whom?
- Can material be held across a respin without being forced into consumption?
- Who owns excess, obsolete and damaged stock after the build?
- What genealogy will link each finished serial number to its parts?
Common questions
How many units does each build need?
There is no standard number. Derive it from the test matrix, destructive tests, process setup, expected yield, certification samples, debug needs and retained units, as in the DVT example above.
Can EVT units use substitute parts?
Yes, when engineering approves the substitute and the change is recorded against the units that carry it. Those units must not be presented later as the final configuration without evidence.
What should happen to leftover build material?
Reconcile it by quantity, owner, revision, lot, shelf life and storage condition. Segregate anything obsolete or suspect, and carry usable stock forward under inventory control so the next build can count it.
If the next build needs new sources, forUdyog has directory categories for component distributors, PCB assembly and testing services, and you can post a QUICK RFQ on the RFQ page that names the BOM revision and build stage.
Sources
Each source was opened and checked on the date shown. Rules, rates and company details change, so confirm anything time-sensitive before you act on it.
Continue on forUdyog
- Product design and prototyping
- PCB fabrication and assembly
- Testing and certification
- Prototype vs production manufacturing
- Component distributors
Have a specific requirement? Describe it on the QUICK RFQ page.
