1.1 The GDP Standard: Formats, Directory & Integrity

The digital handoff serves as the deterministic foundation of the manufacturing process; any ambiguity in this transmission results in stochastic outcomes on the factory floor. The Golden Data Pack (GDP) is not a loose collection of files but a frozen, version-controlled configuration item. Compliance with rigid formatting and directory structures eliminates the risk of "version mismatch" and ensures that the data ingested by the Manufacturing Execution System (MES) matches the design intent bit-for-bit.

Data Formats and Hierarchy

The manufacturing industry relies on specific data standards to preserve design intelligence.

• Primary Format (Intelligent): ODB++ or IPC-2581 are the mandated exchange formats. These containers preserve netlist connectivity, stackup definitions, and component attributes that are lost in legacy formats.
• Secondary Format (Graphic): Gerber X2 is the acceptable fallback. Legacy RS-274D and RS-274X Extended Gerber files are classified as "Risk Level High" due to the need for manual reverse-engineering of netlists.
• Directory Map (DSDM): The archive must adhere to the Dannie Standard Directory Map. The root folder must use the naming convention [Project_Name]_. Subdirectories must be strictly compartmentalized:
  • /01_Manufacturing_Data (Gerber/ODB++)
  • /02_Assembly_Data (BOM, Centroid/XY)
  • /03_Drawings (Fab Drawing, Assy Drawing)
  • /04_Firmware (Hex/Binaries)

Order of Precedence

Conflicts between data sources are a primary cause of engineering holds. The hierarchy of truth is established as follows:

1. Purchase Order (PO): Defines the legal and commercial requirements (Quantity, Delivery).
2. Master Fabrication Drawing: Defines the physical requirements (Material, Finish, IPC Class).
3. Electronic Data (ODB++/Gerber): Defines the geometry.
4. IPC Standards: The default fallback for unspecified parameters (e.g., IPC-6012 Class 2). Note: If the Gerber file shows a 1.0 mm hole but the Drill Table in the Drawing specifies 0.8 mm, the Drawing takes precedence.

Data Integrity

Transmission errors can corrupt binary data. A cryptographic hash (MD5 or SHA-256) is required for the root archive. The value must be included in a manifest.txt file within the root directory to allow automated verification upon ingestion.

Final Checklist