
Released build package
DFX findings, BOM/AVL risks, substitutions, assembly notes, and test intent are dispositioned against one revision before release.
DFXBOM/AVL

ENGINEERING RELEASE TO PILOT
NPI PCB assembly is the controlled transition from released design data to repeatable first builds and pilot production, with DFX, first-article evidence, test disposition, and revision control at each gate.
Each first build is tied to an approved revision, documented inspection evidence, and an explicit release decision.
Assembly-only scheduling for released, build-ready packages.
Gerber/ODB++, BOM/AVL, assembly, and test-access risks returned for disposition.
Traveler, FAI photos, inspection logs, test status, and ECO baseline packaged per lot.
NPI PROGRAM
The program advances only when data, material risk, first-article evidence, test results, and revision status have a named disposition.
Engineering release
Gerber/ODB++, BOM, centroid, drawings, and test intent are checked against one revision before the work order is released.
First-article build and disposition
Seven SMT lines support NPI scheduling, with SPI/AOI, risk-based X-ray, FAI review, and controlled rework before lot release.
Pilot transfer package
Golden-unit status, approved ECOs, recipes, travelers, inspection evidence, and test disposition establish the repeatable baseline.

PLAYBOOK
Six release gates keep every revision aligned with the evidence the pilot-production team needs later.
Release build data
Gerber/ODB++, BOM/AVL, centroid, drawings, test intent, target quantity, and revision identifier.
Disposition DFX and supply risk
Resolve stack-up, stencil, polarity, access, AVL, lifecycle, and substitution questions before purchase and setup.
Build and release the first article
NPI-scheduled SMT runs SPI/AOI, risk-based X-ray, FAI review, and documented nonconformance disposition.
Disposition test results
Record firmware, access maps, flying-probe or ICT/FCT results, failed-unit analysis, and retest status.
Control ECO and pilot handoff
Lock the golden unit, approved ECO baseline, recipes, travelers, FAI record, and pilot transfer package.
NPI CONTROL POINTS
Speed matters, but NPI becomes repeatable only when engineering decisions, first-article evidence, and the approved baseline travel together.



CAPABILITIES
Assembly, inspection, test, and documentation are tied to the same revision so first-build findings can become a stable pilot baseline.
MSD controls, offline kitting, work-order revision checks, and ECO disposition keep each first build tied to its approved baseline.



QUALITY
Inspection data is useful only when it is tied to the released revision, dispositioned findings, and the baseline selected for pilot transfer.
Stack-up, stencil, assembly, and access reviews are linked to FAI photos and dimensional checks for the released revision.
SPI/AOI, targeted X-ray, MSD controls, and rework records show what passed, what changed, and what requires approval.
Flying-probe or ICT/FCT plans, boundary-scan, firmware version, golden-unit status, and retest results are captured in travelers.
Build focus: released data, DFX findings, first articles, and functional test. Exit decision: the design meets agreed functional acceptance criteria and every issue has an owner.
Build focus: design robustness, inspection and test coverage, and root causes for recurring rework. Exit decision: validation passes without undocumented manual workarounds.
Build focus: production tooling, work instructions, line balance, and process evidence. Exit decision: agreed yield and test thresholds hold across the pilot lot without uncontrolled intervention.
Build focus: approved BOM/AVL, golden unit, programs, recipes, travelers, ECO status, and open actions. Exit decision: the customer approves the controlled production baseline.

NPI RELEASE-GATE MATRIX
Each gate names the decision, evidence, and controlled output needed before the program advances.
Engineering release
First build
Pilot handoff
NPI control
NPI control
NPI control
Everything you need to know about HDI PCB technology
Upload the release package to receive a DFX- and BOM-risk review tied to the first-build and pilot-handoff requirements.