1.5 Release Checklist and Freeze Rules

For the EMS provider, the NPI (New Product Introduction) Data Intake Gate serves as a critical liability shield. Once a data pack is formally accepted and the Traveler is released to the manufacturing floor, ownership of the outcome transfers to the EMS. If ambiguous input data is processed based on assumptions, the resulting scrap constitutes a direct financial loss.

This intake gate must be utilized to enforce a rigorous “Stop/Go” policy. Projects are strictly prohibited from passing into Procurement or Computer-Aided Manufacturing (CAM) processing until the Golden Data Pack (GDP) is validated as a locked, cohesive entity.

The Mechanics of the Freeze: Integrity Checks

The primary operational duty is verifying the cessation of design changes. Receiving an archive named “Draft_v3_Final.zip” is an immediate critical failure vector.

1. The Checksum Validation

Upon receiving the GDP archive over the network, its integrity must be verified.

• Action: A SHA-256 (or MD5) hash check must be run on the downloaded ZIP file.
• Review: When the computed hash diverges from the customer’s stated hash in the Purchase Order (PO) or release email, the file must be rejected. The file is corrupted or was intercepted during transit.

2. The Timestamp Audit

The archive must be extracted and the “Date Modified” timestamps of the internal files must be audited.

• The Red Flag: If the Gerber files are timestamped Monday, but the Bill of Materials (BOM) is timestamped Wednesday, the package is out of sync.
• Review: When the timestamps show significant variance (e.g., >48 hours divergence between schematic BOM generation and CAD output generation), the data pack is placed on hold. Explicit written certification that the newly generated BOM perfectly matches the older board revision is required.

3. The Ban on “Email Patches”

Accepting “patch” updates via informal channels (e.g., “Hey, please use this updated Pick & Place file instead of the one in the zip”) is strictly prohibited.

• The Rule: The GDP is an atomic entity.
• Action: When an updated file is transmitted, a completely new GDP Revision (e.g., Rev A ⭢ Rev B) is required. Manually overwriting files in the local CAM directory destroys system traceability and is forbidden.

The Intake Checklist: Acceptance Criteria

Before data enters the ERP or CAM tools, it must clear the Initial Review. This checklist prevents the waste of engineering hours on invalid datasets.

The Category	The Inspection Step	The Go/No-Go Metric
The Manifest	Verification of README or Manifest file presence.	File exists and lists exact EDA Tool Versions.
Sync Check	Cross-checking Revision string in BOM vs. Gerbers vs. Drawings.	All Revisions perfectly match (e.g., all are “Rev 05”).
Completeness	Verification that the critical file triad exists.	Netlist, Solder Paste Layer, and Centroid XY data are all present.
Machine Readability	Opening BOM and XY files in a raw text editor.	Text is cleanly delimited; zero binary garbage characters.
BOM Status	Scanning the MPN column for “TBD” or “Contact Engineering”.	0% “To Be Determined” entries allowed.
Authorization	Checking for “Released” watermarks or PLM status.	Zero “DRAFT” or “PRELIMINARY” watermarks on drawings.

Stop-Build Triggers

Specific triggers must be defined that mandate stopping the intake process and returning the data pack. Delaying a launch by 24 hours is operationally superior to procuring $50,000 of incorrect components.

Trigger 1: The Mixed-Revision Pack

• Observation: The Pick & Place file contains RefDes locators (e.g., U50, C12) that physically do not exist in the BOM.
• Action: Reject. The assembly instructions command the machine to place parts that the procurement instructions did not buy.

Trigger 2: The Silent Specification

• Observation: The Fab Drawing demands “Impedance Controlled,” but absolutely no stackup table or target values are provided.
• Action: Hold for Engineering Query (EQ). Allowing CAM engineers to guess the dielectric thickness is prohibited.

Trigger 3: The Unsigned Traveler

• Observation: The customer demands a “Quick Turn” build but has not formally approved the GDP in their PLM or tied it to a Purchase Order.
• Action: Hold. Without formal approval, “Golden” data is just a suggestion.

Pro-Tip: When a “Conditional Release” is mandated (e.g., to order long-lead-time silicon while the bare board design is finalizing), a specific “Risk Buy Waiver” form must be executed. The risk must be isolated entirely to procurement; hard tooling must not commence.

Final Checkout: Release checklist and freeze rules

The Control Point	The Operational Requirement	The Go/No-Go Metric
Intake Hash	Checksum verified against sender’s data.	Matches perfectly (Green Light).
File Architecture	Standard 00-05 folder structure.	Zero “misc” or “old_versions” folders exist.
Revision Sync	BOM/CAD/Drawing revisions align.	100% string match across all headers.
Constraint Check	Fab Drawing notes reviewed.	Materials and tolerances are physically achievable in your factory.
Authorization	The PO references the exact GDP filename.	The formal link is established.