Direct Answer
A PCBA quote should name setup or first-article checks, SPI when solder paste volume is critical, AOI for visible placement and solder defects, X-ray or AXI for hidden joints, ICT or flying probe when electrical access and program ownership are defined, programming when firmware is part of release, and FCT when powered behavior must be verified before shipment.
Decision Model
Quote-ready inspection scope = board risk trigger + selected inspection or test method + coverage boundary + owner of fixture, program, firmware, and limits + acceptance evidence required at shipment.
Why It Matters
Turn SMT inspection and test acronyms into quote-ready scope, ownership, coverage, and acceptance evidence. Late discovery changes cost, schedule, yield, or acceptance evidence after engineering and procurement have already made assumptions.
Engineering Principles
- Choose inspection by failure visibility: visible SMT defects belong to SPI, AOI, first-article, or visual scope; hidden joints need X-ray or AXI scope.
- Choose test by electrical risk: ICT, flying probe, boundary scan, programming, or FCT only become comparable quote items when access, program ownership, limits, and records are named.
- Do not buy inspection acronyms. Buy a defined acceptance handoff: method, side, packages, coverage expectation, pass/fail owner, log requirement, and rework path.
Example
A BGA and connector-heavy board should state AOI scope, X-ray coverage, fixture or probe access, programming image, FCT pass criteria, and required inspection or test logs.
Comparison
- AOI covers visible assembly risk; X-ray or AXI covers hidden-joint risk.
- ICT and flying probe check electrical conditions when access and programs exist; FCT checks product behavior against supplied limits.
- Inspection evidence should be scoped before quote because fixture, program, log, and sampling expectations change cost and schedule.
RFQ Inputs
- Gerber or ODB++, BOM, centroid, assembly drawing, revision, quantity, and side information.
- Packages or features that trigger SPI, AOI, X-ray, AXI, ICT, flying probe, programming, or FCT.
- Fixture ownership, test-program ownership, firmware image, calibration state, pass/fail limits, and retest rules.
- Required evidence at shipment: first-article notes, AOI/X-ray logs, ICT/FCT logs, photos, or exception reports.
FAQ
Should every PCBA quote include AOI, X-ray, ICT, and FCT?
No. Include the methods that remove real board risk. A simple SMT board may need AOI and visual checks; a BGA or QFN board needs hidden-joint review; a programmed product may need FCT.
Can AOI replace functional test?
No. AOI checks visible assembly quality. Functional test verifies powered behavior, firmware state, interfaces, sensors, outputs, and customer-defined pass criteria.
What makes ICT or FCT quote-ready?
ICT or FCT becomes quote-ready when the RFQ defines access, fixture ownership, test-program ownership, firmware image, measurement limits, retest rules, and required logs.
Source Notes
- Soldered assembly process boundary - IPC J-STD-001J requirements for soldered electrical and electronic assemblies (standard).
Source fact: IPC J-STD-001 is the source boundary for soldered electrical and electronic assembly process requirements. Omini interpretation: Use this to explain why an industrial PCBA quote should name soldering process assumptions, workmanship class ownership, inspection scope, and acceptance handoff before production release. Allowed usage: Use on SMT assembly, industrial automation PCBA, inspection planning, and RFQ readiness pages when soldered-assembly process boundaries matter.
- Electronic assembly acceptability boundary - IPC-A-610J acceptability of electronic assemblies (standard).
Source fact: IPC-A-610 is the source boundary for electronic assembly acceptability and inspection context. Omini interpretation: Use this to frame AOI, visual inspection, and human review as scoped acceptance activities that need defined class, defect ownership, and pass/fail evidence rather than generic quality claims. Allowed usage: Use on inspection, industrial automation PCBA, AOI, X-ray, and assembly quality pages.
- Automated inspection process-control boundary - IPC-9716A requirements for automated inspection process control (standard).
Source fact: IPC-9716A is the source boundary for automated inspection process-control context, including SPI, AOI, and AXI for printed board assemblies. Omini interpretation: Use this to frame automated inspection as a scoped process-control activity that needs board side, component coverage, method, and acceptance handoff before production release. Allowed usage: Use on AOI, SPI, AXI, SMT inspection, AOI versus X-ray comparison, and quote-handoff pages when explaining automated inspection scope.
- BGA inspection and assembly boundary - IPC-7095E Design and Assembly Process Guidance for Ball Grid Arrays (standard).
Source fact: IPC-7095E covers BGA and fine-pitch BGA design and assembly implementation topics, including inspection, rework, repair, and troubleshooting scope. Omini interpretation: Use this to justify X-ray review when critical solder joints are hidden below BGA or fine-pitch area-array packages and optical inspection cannot see the joint interface. Allowed usage: Use on X-ray inspection, BGA assembly, AOI versus X-ray comparison, via-in-pad, and hidden-joint inspection pages.
- ICT manufacturing test boundary - Keysight in-circuit test for manufacturing (manufacturer).
Source fact: Keysight presents in-circuit test as a manufacturing test method for assembled boards, focused on detecting assembly faults and verifying circuit-level conditions. Omini interpretation: Use this to require explicit ICT access, fixture readiness, net coverage, program ownership, and pass/fail evidence when a PCBA quote includes ICT. Allowed usage: Use on SMT inspection, PCBA quote scope, ICT, DFT, and production-test handoff pages.
- PCBA functional test automation boundary - NI PCB Assembly Test Toolkit (manufacturer).
Source fact: NI publishes PCBA test automation resources for electrical functional test workflows and test-station development. Omini interpretation: Use this to separate inspection from functional test: FCT needs fixtures, firmware state, measurement steps, limits, and a pass/fail handoff defined before quote. Allowed usage: Use on functional test, PCBA quote scope, programming, fixture, and production-test handoff pages.
- Existing OminiPCB repository content (internal): May seed structure and internal links; engineering claims still need external verification when specifications are involved.
CTA
Request a PCB quote when the design files and acceptance requirements are ready for engineering review.