Assembly-specification comparisons should establish whether identical product files can be manufactured and delivered consistently across the complete route, not which capability table has smaller minimum numbers. Individual-board, panel, carrier, and usable-work-area dimensions differ. Component dimensions, lead pitch, and placement accuracy are also different metrics. Complete actual inputs first, then ask suppliers to classify each object as suitable, needing verification, or missing information.
Align dimensions and units before comparing capability
At minimum, board outlines should specify length/width, thickness, irregular shapes or slots, conveyor direction, and allowable warpage. Double-sided assemblies also need bottom-side protrusions, edge connectors, and maximum component heights. Equipment may handle panels or carriers; an individual bare board fitting does not establish that a panel with rails fits the usable area. Bottom-side components also constrain support-pin locations.
Specify imperial versus metric package naming. Example: imperial 0201 commonly means approximately 0.6×0.3 mm, while metric 0201 uses a different size system. “0201” alone in a BOM does not establish shared understanding. 1 mil＝0.0254 mm, so 0.5 mm is approximately 19.69 mil. However, 0.5 mm ball pitch and 0.5 mm component length are entirely different objects; unit conversion does not remove that distinction.
| Specification Field | Ambiguous Notations | Unified Input |
|---|---|---|
| Board size | Write Only 80×50 | Individual board 80×50 mm, with panel outline and orientation |
| Thickness | Nominal Thickness Under All Conditions | Thickness, tolerances, local structures, and warpage requirements |
| Smallest Component | 0201 no system marking | Complete part number, package drawing, and actual dimensions |
| Fine-pitch | Use body width instead of pin pitch | Pitch, pad dimensions, and solder mask conditions |
| Height | Fill Only Top Surface Maximum Value | Heights on both sides, protrusion directions, and process states |
Package must be evaluated with surrounding conditions
Even within QFN or BGA, different pitches, thermal pads, solder-ball alloys, and board via structures create different work. Tall components near fine-pitch packages may affect placement, imaging, and rework. Heavy components on thin boards require support and bending checks. Include local layouts in actual reviews rather than combining independent limits into an apparently universally feasible table.
Nominal equipment placement accuracy describes only part of performance under specified conditions. Final connections also depend on PCB fabrication, print misalignment, component tolerances, coplanarity, and thermal history. Machine accuracy is not allowable pad misalignment, and independent minima do not necessarily apply simultaneously. Suppliers should state conditions and verification methods; unproven combinations remain subject to pilot production.
Establish compatibility matrix based on product risk
| On-Board Object | Association Constraint | Review Evidence | Output Status |
|---|---|---|---|
| Fine-Pitch QFN | Stencil release, thermal relief pads, and via treatment | Package drawing, stencil drawing, and trial print imaging | Confirmed or specific conditions requiring verification |
| BGA Processor | Pad definition, thermal warpage, and hidden connections | Ball map, measured profile, and inspection coverage | List Blind Spots and Supplementary Methods |
| Large Connectors | Conveyor, post-solder, fixtures, and test probe insertion | structural drawing versus actual assembly test | Clarify Sequential Processes and Fixtures |
| Thin Board Double-Sided Assembly | Bottom support, heavy items, and thermal process | Two-Side Layout and Carrier Verification | Approved Supports and Inspection Routes |
| Thermal Sensitive Device | allow thermal exposure and cleaning conditions | Manufacturer Restrictions and Process Grouping | post-install, masking, or special route |
Status labels need fixed meanings. “Confirmed” includes applicable files/evidence; “pilot production required” lists questions to resolve; “missing information” identifies absent drawings/constraints; “unsuitable” explains reasons and feasible adjustments. Do not mark unknown items as passing or hide known conflicts behind “subject to actual conditions.” Synchronize file revisions before recomparing changed board designs or panelization.
Inspection specifications must also use the same scope
Capability tables listing AOI, X-ray, in-circuit electrical testing, and functional testing do not establish quotation inclusion. For current boards, require reference designators, sides, individual-board versus sampling coverage, target defects, criteria, and retained records. “100% inspection” alone is insufficient; define whether the denominator for 100% is boards, a component category, or a process step.
For example, operating one interface on a dual-Ethernet board does not verify every port. X-ray imaging one BGA does not cover all hidden joints. Fix programs, loads, peripherals, and firmware revisions when comparing inspections. First-article demonstration reports establish execution under sample conditions, not passage of the entire current order.
How to identify incomparable entries in two capability tables
Engineering example: supplier A lists maximum board length, while B lists maximum panel area. The current product is a long board with an overhanging connector; small area does not establish conveyor-length or clamping compatibility. Draw the complete outline, component projections, and carrier first, then request responses to identical drawings. If A needs extra rails and B needs a carrier, both may work. Compare added preparation, stability, and later depanelization rather than original table values.
Similarly, if A says “small-component placement supported” while B provides package pilot-production records, compare record thicknesses, neighboring components, stencils, and inspection with the project. Historical samples cannot guarantee arbitrary layouts. This page's comparison method uses public capability-table fields without adopting other companies' minimum dimensions, accuracy, qualifications, or yields as this site's capabilities.
First-article converts specification comparison into actual conclusions
Before first articles, freeze Gerber, BOM, pick-and-place data, DNP, assembly drawings, and panelization; map high-risk objects to processes and inspections. Afterward retain printing, placement, profiles, post-solder, and functional records, checking uncovered conditions. Observe actual tooling, exception handling, and rework access rather than finished products alone. Pilot conclusions apply only to approved revisions/configurations; assess later thickness, package, or carrier changes.
Initial inquiries need not include every input. Start with application, major packages, quantity, and available documentation, then complete controlled files for formal review. For submissions, start with Assembly Scope confirm project object, then combine Test Delivery to determine record requirements rather than expecting a complete capability conclusion from one board photo.
Common specification comparison issues
Does higher placement accuracy always mean a better fit?
Material supply, printing, support, thermal history, and inspection must also fit. Accuracy is one condition, not complete assembly quality or quotation value.
Does panelization affect quantity only
It also affects processing outlines, support, datums, thermal behavior, inspection, and depanelization. Changing panelization after individual-board approval still requires reviewing these linked items.
How to express conditions in supplier response
For every specification, request applicable production conditions and validity scope. Directly feasible items need supporting bases; carrier- or pilot-dependent items need preparation/verification plans; incomplete items need missing-input lists. A package name in a capability table does not establish passing thermal limits, datums, or neighboring-component interference. Date responses so old equipment descriptions do not become indefinite current commitments. After file changes, use difference lists to revisit affected items rather than silently refilling the whole table. Thickness changes may affect conveying, support, and profiles; bottom-side component changes may affect carriers and probes. Unchanged package numbers do not establish unchanged conditions. Attach approved files and first-article conclusions to the final matrix so purchasing, design, and process teams share conditions. For outsourced processes, identify the actual provider, record contact, and change-notification method; a task in a prime contractor's capability table does not establish identical execution configurations at every location.
Source material and applicable scope
- Linked Electronics, “PCB Capabilities”; webpage version not identified; checked 2026-10-17; sections: Assembly Specifications and Inspection and Testing. Supports comparison of dimensional, package, and inspection fields; its values or promotional conclusions are not this site's capabilities.
- Texas Instruments, “SMT & packaging application notes”; directory-page version not identified; checked 2026-10-17; sections: QFN, BGA, and General packaging information. Supports routing documentation by package and thermal process; does not establish validation of specific part numbers.
