Essential Document Preparation Guide for Starting a PCBA OEM Project
To start a PCBA OEM project, release one controlled package containing PCB fabrication data, a detailed BOM, centroid data, assembly drawings, mechanical references, and applicable programming, testing, inspection, coating, and packaging instructions. Every file should identify the same approved revision, component population, polarity, substitutions, acceptance criteria, and customer-supplied materials.
Separate universally required manufacturing data from project-dependent test and special-process instructions.
Use manufacturer part numbers and reference designators, not descriptions alone.
Resolve cross-file conflicts before requesting a production quotation.
Agree on acceptance standards, revisions, and supplier evidence in writing.
Release PCB fabrication data
Provide Gerber or agreed intelligent data, NC drill files, board outline, stackup, materials, copper weight, finish, impedance requirements, tolerances, and panel instructions. The IPC-2221B scope published by IPC identifies design documentation as part of generic printed-board design requirements. This supports recording construction and tolerances explicitly rather than expecting a fabricator to infer them.
Make the BOM sourcing-ready
List quantity, reference designators, manufacturer, exact manufacturer part number, package, value, approved alternatives, do-not-fit status, lifecycle concerns, and customer-supplied items. State whether substitutions require written approval.
Align placement and assembly instructions
Supply centroid coordinates, units, origin, rotation convention, side, and reference designator. Add top and bottom assembly drawings showing polarity, pin 1, mechanical hardware, hand-soldering, press-fit, adhesive, cleaning, and other special instructions.
Define programming, test, and acceptance
Provide firmware files and checksums, target device, programming interface, configuration values, test procedure, fixture responsibilities, limits, expected outputs, inspection scope, and failure disposition. IPC describes IPC-A-610H as acceptance criteria for electronic assemblies; therefore, buyers should contractually agree on the applicable document, class, revision, and customer-specific criteria rather than writing only “IPC compliant.”
Control the release package
Use a manifest listing every filename, revision, date, and owner. Confirm that Gerbers, BOM, centroid data, drawings, firmware, test documents, mechanical models, and change notices describe the same build.
Can a supplier quote without centroid data?
A preliminary quote may be possible, but placement review and production planning remain incomplete. Label the quote assumptions and provide the file before release.
What if some components are unavailable?
Define approved alternates, prohibited substitutions, approval authority, and whether parts will be customer-supplied. Never authorize substitution from value and package alone.
What coating information is required?
Specify material, coverage, keep-out areas, thickness or agreed process criteria, cure, masking, inspection, rework, and acceptance requirements.
Project-dependent documents and constraints
Add enclosure drawings, STEP models, connector locations, keep-outs, mounting hardware, cable references, thermal interfaces, and dimensional limits when fit affects acceptance. For conformal coating, the IPC-CC-830C scope published by IPC addresses qualification and performance of insulating compounds. It supports specifying the coating material and acceptance basis, but it does not replace a board-specific masking and coverage drawing.
Quotation and engineering-review checklist
- Confirm quantities, build stage, delivery scope, packaging, and required records.
- Compare BOM designators with drawings and centroid data; reconcile missing, duplicate, or DNP positions.
- Verify board outline, layer count, drill data, polarity, origin, units, and revisions.
- Identify AOI, X-ray, electrical, functional, programming, coating, and traceability requirements.
- Record assumptions where information is unavailable; do not allow silent interpretation.
Confidentiality and controlled transfer
Agree on NDA coverage, authorized recipients, encryption, access control, retention, and deletion. The NIST SP 800-171 Revision 3 publication defines safeguards for controlled unclassified information in nonfederal systems. It is not automatically mandatory for every PCBA project, but it demonstrates why customers with controlled data should establish access and transfer requirements before sharing design files.
Common delay causes and supplier evidence
Typical blockers include mismatched revisions, BOMs without exact part numbers, ambiguous polarity, absent test limits, incomplete coating keep-outs, and undocumented customer-supplied inventory. Before launch, request the supplier's DFM findings, BOM exceptions, substitution list, programming plan, inspection and test plan, traceability proposal, special-process confirmation, open-question log, and final release acknowledgment. Review applicable standards and revisions contractually; do not infer certification from a capability statement.
