
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.
48–72 h assembly option after build-ready release; confirm kit, tooling, programs, capacity and agreed inspection/test.
Gerber/ODB++, BOM/AVL, assembly, and test-access risks returned for disposition.
Revision-controlled traveler with agreed FAI photos, inspection logs, test status and ECO records per lot.
FIRST-BUILD DECISIONS
A first-build approval should identify the unit and configuration reviewed, the evidence considered and the next operation or remaining quantity it authorizes. Agree the review windows before setup so an approval of placement photos is not mistaken for acceptance of hidden solder joints, powered operation or the whole product.
| Review Window | Reference to Define | Evidence to Review | Permission to Confirm |
|---|---|---|---|
| Before the first reflow | Assembly side, populated variant, DNP status, rotation, pin-1 and polarity against the approved BOM, placement data and drawing. | The agreed placement/setup check on the identified first board; resolve reference or orientation mismatches while accessible. | Whether that setup can proceed to reflow. Placement evidence does not establish solder-joint acceptance. |
| After reflow, before access is obstructed | Critical joints and the later connectors, shields or hardware that may limit inspection or rework. | Agreed optical/visual evidence and, where specified, X-ray evidence for selected hidden connections; identify features still unverified. | Whether later insertion or hardware fitting may proceed, and which inspections remain open. No method is assumed to reveal every hidden feature. |
| First THT, manual or mechanical operations | Connector orientation, seating/standoff and any assembly-drawing constraints for the actual first-unit configuration. | The specified dimensional, visual or process checks and the disposition of any exception. | Whether the demonstrated operation can continue on the remaining quantity; identify deviations requiring customer approval. |
| Before programming or powered testing | Hardware revision, released image identifier, procedure, fixture and pass/fail limits for the intended test. | Readiness of the agreed programming/test inputs, followed by results for the services included in the order. | What programming or test activity is authorized, and what remains untested. Assembly inspection approval is a separate decision from functional acceptance. |
| Before the remaining build continues | Named approver, unit/configuration, evidence reviewed, accepted deviations and the proposed next operations or quantity. | A recorded decision linked to the released revision and the scope already reviewed. | Exactly what may proceed and what stays on hold. Manufacturing permission does not replace the customer’s product or system validation. |
Review windows, first-article quantity, hold points and records are agreed for the actual program. In the enquiry, name critical reference designators, the evidence you want to review, the approval contact and availability, and the permission needed before the rest of the build proceeds. Use PCBA testing and quality to select test coverage, and the first-article inspection reference for the boundary between FAI and qualification.
You can start an NPI feasibility enquiry with the files and open questions available today. Mark provisional BOM, assembly, firmware or test decisions explicitly; the review can identify what is needed for a committed build. For findings that must be verified across later lots, use NPI and small-batch planning rather than treating first-unit approval as proof of a production ramp.
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. Panel, stencil, polarity, assembly, test-access and BOM/AVL risks are reviewed for disposition. Flying probe, ICT/FCT, firmware loading, result logging and retest support are available within the agreed test scope.
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.