3.4 FAI Build Evidence Pack and MP Release

First Article Inspection (FAI) serves as the forensic audit of the manufacturing process. Its purpose extends beyond simply proving a product can be built; it demonstrates that the process is robust, repeatable, and statistically capable of scaling to Mass Production without exponential cost growth or quality escapes. The FAI Build Evidence Pack is the mechanism that transforms a physical build event into the concrete data required for the final “Go/No-Go” decision. Launching Mass Production (MP) without this validated evidence constitutes an unnecessary inventory risk.

The FAI Evidence Pack Requirements

The Evidence Pack must be submitted as a single, consolidated PDF or digital archive containing the following validated datasets. To maintain clarity and auditability, you should avoid accepting scattered emails, chat messages, or verbal confirmations from the factory floor.

1. Yield Summary and Defect Pareto

Aggregate the assembly line yield data to identify systemic process weaknesses.

• First Pass Yield (FPY): Report the exact percentage of units that passed all manufacturing and inspection processes—such as SPI, AOI, X-Ray, ICT, and FCT—on their very first attempt, with zero rework. A high final yield combined with a low FPY often indicates a hidden, expensive rework cost structure that needs to be addressed.
• Defect Pareto: Categorize the top failure modes to guide corrective actions.
  • If solder bridges are the top defect, the engineering team should review stencil aperture design and solder paste print pressure.
  • If part misalignment is the top defect, the review should focus on SMT nozzle selection, placement speed, and vision recognition system data.

2. The “As-Built” Configuration (Traceability)

Early NPI builds rarely match the initial documentation perfectly. The Evidence Pack must accurately capture what actually occurred on the shop floor.

• Redline BOM: Submit the Bill of Materials with clear markings showing any alternative components used, temporary substitutions, or value changes that were required for proper board functionality.
• EQ/ECO Log: Compile all Engineering Queries (EQ) raised by the factory during the build and document all resulting Engineering Change Orders (ECO).
• Reflow Profile: Attach the measured thermal profile (temperature vs. time), directly overlaid onto the solder paste manufacturer’s specified tolerance window for verification.

3. Test and Programming Proof

• Programming Verification: Provide a log summary confirming that the correct checksums and firmware versions were successfully loaded into the devices.
• Test Data: Submit actual parametric test results—such as voltage, current, and frequency readings—rather than just Pass/Fail booleans. This data establishes the baseline statistical quality distribution (Cₚₖ) for the product.

Critical Factor

You should avoid accepting “NFF” (No Fault Found) as a root cause during the FAI stage. When a unit fails a test and then subsequently passes on a retest without any modification, it typically indicates an unstable test process. These instances should be labeled as “Process Instability,” prompting an investigation into test fixture contact reliability or measurement tolerances.

The MP Release Gate

The transition from NPI into Mass Production is a formal “Gate Review.” This step requires a definitive freeze of the Golden Data Pack.

Sign-off Authority

Three distinct signatures are mandatory to authorize the move to Mass Production:

1. Manufacturing Engineering: Confirms the manufacturing process capability and fixture stability.
2. Quality Assurance: Confirms all critical dimensions and cosmetic standards meet the Acceptable Quality Limit (AQL).
3. Product/Design Engineering: Confirms the device functions as intended by the original design.

The Frozen State

Upon official MP Release, the following elements become Read-Only:

• Gerber and ODB++ Fabrication Files.
• Pick & Place Centroid Data.
• The Approved Vendor List (AVL).
• Test Limits and Firmware Checksums.

Any modification to these files after this point, no matter how minor, requires a formal Process Change Notification (PCN).

Re-FAI Triggers

While continuous improvement is encouraged, uncontrolled changes introduce significant risk. Clear triggers must be defined that formally invalidate the previous FAI and mandate a new qualification build.

Trigger Logic:

• If a Critical Component (such as an MCU, Sensor, or PCB Laminate) changes manufacturer, a Delta-FAI—a partial qualification focused on the change—must be performed.
• If production is moved to a New Facility or a new SMT Line with different equipment capabilities, a Full FAI must be performed.
• If the product has been dormant and unbuilt for 12 months or more, a “Refresher” FAI must be performed to validate the integrity of expired solder paste, aging components, and drifted machine settings.

---

Recap: FAI Build Evidence Pack and MP Release

Parameter	Requirement	Value / Criterion	Action / Status
First Pass Yield (FPY)	Report units passing all processes on first attempt.	Exact percentage. High final yield with low FPY indicates hidden rework cost.	Submit in Yield Summary.
Defect Pareto	Categorize top failure modes.	Identify primary defect (e.g., solder bridges, part misalignment).	Guide corrective action (e.g., review stencil design, placement settings).
As-Built Configuration	Document actual build vs. design.	Redline BOM, EQ/ECO Log, Reflow Profile vs. spec.	Submit validated datasets.
Test Proof	Provide parametric test data.	Actual voltage/current/frequency results; establish Cₚₖ baseline. Label retest passes as “Process Instability,” not NFF.	Submit test logs and results.
MP Release Gate	Formal authorization to proceed.	Mandatory sign-off: Manufacturing Engineering, Quality Assurance, Product/Design Engineering.	Freeze Golden Data Pack (Gerbers, AVL, test limits, firmware).
Re-FAI Trigger	Change invalidating prior FAI.	Critical component manufacturer change, new production facility/line, or product dormant ≥12 months.	Execute Delta-FAI or Full FAI.