1.5 Release Checklist and Freeze Rules
For an EMS provider, the NPI (New Product Introduction) Data Intake Gate is a critical control point that manages liability. Once a data pack is formally accepted and the manufacturing Traveler is released to the production floor, responsibility for the outcome transfers to the EMS. If ambiguous input data is processed based on assumptions, any resulting scrap becomes a direct financial loss for the provider.
This gate must be used to enforce a clear “Stop/Go” policy. Projects should not proceed into Procurement or Computer-Aided Manufacturing (CAM) processing until the Golden Data Pack (GDP) is validated as a complete, locked, and cohesive set of files.
The Mechanics of the Freeze: Integrity Checks
Section titled “The Mechanics of the Freeze: Integrity Checks”The primary operational task is to confirm a complete design freeze. Receiving an archive with a name like “Draft_v3_Final.zip” is a strong indicator of a potential problem.
1. The Checksum Validation
Section titled “1. The Checksum Validation”When the GDP archive is received over the network, its integrity must be confirmed before proceeding.
- Action: Run a SHA-256 (or MD5) hash check on the downloaded ZIP file.
- Review: If the computed hash does not match the value provided by the customer in the Purchase Order (PO) or release email, the file must be rejected. A mismatch indicates the file was corrupted or altered during transit.
2. The Timestamp Audit
Section titled “2. The Timestamp Audit”After extracting the archive, review the “Date Modified” timestamps of the internal files.
- The Red Flag: A significant discrepancy, such as Gerber files timestamped on a Monday while the Bill of Materials (BOM) is timestamped on a Wednesday, is a clear sign the package is out of sync.
- Review: When timestamps show a large variance (e.g., more than 48 hours between schematic BOM generation and CAD output), place the data pack on hold. Proceed only after receiving explicit written confirmation that the newly generated BOM is an exact match for the older board revision.
3. The Ban on “Email Patches”
Section titled “3. The Ban on “Email Patches””Accepting file updates through informal channels—like an email saying, “Please use this updated Pick & Place file instead of the one in the zip”—is not permitted.
- The Rule: The GDP must be treated as a single, cohesive unit.
- Action: If an updated file is necessary, it requires the creation and transmission of a completely new GDP Revision (e.g., moving from Rev A to Rev B). Manually overwriting files in the local CAM directory breaks system traceability and is not allowed.
The Intake Checklist: Acceptance Criteria
Section titled “The Intake Checklist: Acceptance Criteria”Before data is entered into the ERP or CAM systems, it must pass an Initial Review. This checklist prevents wasting engineering time on invalid or incomplete datasets.
| Category | Inspection Step | Go/No-Go Metric |
|---|---|---|
| The Manifest | Verify the presence of a README or Manifest file. | File exists and lists the exact EDA Tool Versions used. |
| Sync Check | Cross-check the Revision string in the BOM, Gerbers, and drawings. | All Revisions match perfectly (e.g., all are “Rev 05”). |
| Completeness | Verify the critical file triad is present. | Netlist, Solder Paste Layer, and Centroid XY data all exist. |
| Machine Readability | Open BOM and XY files in a raw text editor. | Text is cleanly delimited with no binary or unreadable characters. |
| BOM Status | Scan the MPN column for placeholders like “TBD” or “Contact Engineering”. | 0% “To Be Determined” entries are allowed. |
| Authorization | Check for “Released” watermarks or PLM status. | No “DRAFT” or “PRELIMINARY” watermarks on any drawings. |
Stop-Build Triggers
Section titled “Stop-Build Triggers”Specific conditions must be defined that require halting the intake process and returning the data pack. Delaying a project launch by 24 hours is far better than procuring $50,000 worth of incorrect components.
Trigger 1: The Mixed-Revision Pack
Section titled “Trigger 1: The Mixed-Revision Pack”- Observation: The Pick & Place file contains Reference Designator locators (e.g., U50, C12) for components that do not exist in the BOM.
- Action: Reject the pack. The assembly instructions would direct the machine to place parts that were never ordered for procurement.
Trigger 2: The Silent Specification
Section titled “Trigger 2: The Silent Specification”- Observation: The Fabrication Drawing calls for “Impedance Controlled” traces but provides no stackup table or target impedance values.
- Action: Place on Hold for an Engineering Query (EQ). It is unacceptable to require CAM engineers to guess at dielectric thickness or other critical parameters.
Trigger 3: The Unsigned Traveler
Section titled “Trigger 3: The Unsigned Traveler”- Observation: A customer requests a “Quick Turn” build but has not formally approved the GDP in their Product Lifecycle Management (PLM) system or linked it to a Purchase Order.
- Action: Place on Hold. Without formal approval, so-called “Golden” data is merely a suggestion, not an instruction.
Recap: 1.5 Release Checklist and Freeze Rules
Section titled “Recap: 1.5 Release Checklist and Freeze Rules”| Parameter | Requirement | Action | Condition |
|---|---|---|---|
| Revision Synchronization | All files (BOM, Gerber, drawings) have identical revision strings. | Suspend / Reject | Any discrepancy. |
| File Completeness | Netlist, Solder Paste Layer, and Centroid (XY) data files are present. | Reject | Any file missing. |
| BOM Status | 0% “TBD” or “Contact Engineering” entries in MPN column. | Reject | Any placeholder present. |
| Package Authorization | No “DRAFT” or “PRELIMINARY” watermarks; formal PLM/PO approval exists. | Suspend / Hold | Unapproved or draft status. |
| Data Consistency | All RefDes in Pick & Place file exist in the BOM. | Reject | Any mismatch. |
| Timestamp Synchronization | Internal file timestamps are within 48 hours of each other. | Place on Hold | Variance >48 hours without written confirmation. |
| Checksum Integrity | SHA-256/MD5 hash of received archive matches customer-provided value. | Reject | Any mismatch. |
| Specification Completeness | Fabrication drawings with impedance control must include a stackup table with target values. | Place on Hold for EQ | Missing critical parameters. |