PCB Manufacturing Data, Drawings & Configuration Control

The editable ECAD project is a design source. The released manufacturing package is the controlled interface used to build and inspect a specific product revision. Treating an ad hoc export directory as that interface invites missing layers, stale drill files, ambiguous polarity, BOM/placement disagreement, and untraceable shop-floor edits.

Define the package as a contract #

flowchart TB
  C["Controlled ECAD source"] --> E["Deterministic export"]
  E --> F["Fabrication data"]
  E --> A["Assembly data"]
  E --> D["Drawings and notes"]
  F --> R["Independent review"]
  A --> R
  D --> R
  R --> B["Signed release baseline"]
  B --> S["Supplier build records"]

A typical fabrication package includes:

• copper, solder-mask, legend, and other layer images with explicit function and polarity;
• plated and non-plated drill/rout data and a drill table;
• the finished board profile, cutouts, scoring or routing notes, and dimensional drawing;
• approved stackup, materials/substitution rules, finished thickness, copper, finish, mask, and acceptance class;
• controlled impedance requirements and coupon definition;
• fabrication notes, special processes, serialization, test, and certificate requirements;
• a CAD-derived netlist such as IPC-356 for independent electrical comparison when appropriate.

The assembly package commonly adds BOM, approved alternates, reference-designator list, centroid/placement data with a declared origin and rotation convention, paste layers, assembly drawings, polarity and variant information, special process instructions, programming/calibration data, and acceptance requirements.

Geometry and semantics #

The Gerber 2026.05 specification defines precise 2D geometry plus attributes for file function, apertures, pads, nets, components, drill/rout, CAD netlist, and assembly data. X2/X3 attributes reduce filename guessing and allow stronger automated checks. They do not eliminate drawings, stackup, tolerances, BOM, process requirements, or change control.

Standard Gerber/RS-274-D is deprecated because it separates aperture information and lacks the self-contained precision of current Gerber. Current exports should use explicit units, coordinate format, layer function, and attributes supported by both toolchain and supplier.

Intelligent formats such as IPC-2581 can carry linked stackup, geometry, component, and process semantics. Format choice should be agreed with suppliers and independently verified; “single file” does not mean “single source of truth” if the consuming tools silently discard fields.

Independent output review #

Never approve only the CAD view from which files were generated. Load the release in an independent viewer and check:

1. layer count, order, units, polarity, mirroring, origin, and profile;
2. drill and slot sizes, plating classification, drill-to-pad registration, and route paths;
3. copper-to-profile and copper-to-hole spacing, planes, clearances, and thermal reliefs;
4. mask and paste openings, fine dams, exposed pads, and via treatment;
5. reference designators, polarity, component side, centroid rotations, and unpopulated variants;
6. BOM-to-placement-to-drawing reference consistency;
7. netlist comparison between exported connectivity and controlled schematic intent;
8. notes, stackup, dimensions, and filenames for contradictory authority.

Use automated checks where possible, but preserve human review for intent. A syntactically valid file can still represent the wrong revision or mirrored bottom assembly.

Make every release reproducible #

Assign one product/revision identifier to the complete package. Generate into a clean, deterministic directory; include a manifest listing filenames, purpose, tool/version where required, and cryptographic hashes. Archive exactly what was sent and exactly what the supplier accepted. Do not allow files to be replaced under an existing released identifier.

Record open fabrication questions and their resolutions. If a supplier proposes a change—material, stack, annular ring, mask, finish, panel, stencil, or substitute part—route it through the product change authority. Email approval without baseline update creates a unit that cannot be reproduced or compared to qualification evidence.

Engineering changes must close every representation #

An engineering change may affect requirements, schematic, layout, BOM, firmware, mechanical model, drawings, test limits, fixtures, labels, regulatory evidence, work instructions, field spares, and inventory disposition. The change record should state reason, affected items, before/after configuration, analysis, verification to repeat, and effective serial or lot boundary.

Configuration control turns manufacturing evidence into engineering evidence. Without it, a pass or failure cannot be tied confidently to the design that customers receive.