AOI, X-ray, ICT, and Functional Test: What Each One Actually Catches

Jul 03
Quality & Test

AOI, X-ray, ICT, and Functional Test: What Each One Actually Catches

Inspection and test are not interchangeable. Each method sees a different part of the build: visible workmanship, hidden solder joints, circuit-level defects, and real-world product behavior.

4major inspection and test methods
Bettercoverage through the right combination
EarlierDFT planning reduces test surprises
PCB assembly inspection and test coverage illustration A stylized PCB surrounded by AOI, X-ray, ICT, and functional test checkpoints, showing that each method checks a different kind of issue. AOI visible defects X-ray hidden joints ICT circuit faults FCT behavior
The big idea

Inspection and test answer different questions.

When an OEM asks whether a board has been “tested,” the answer should usually be more specific. Was it optically inspected? X-rayed? Electrically checked at the component and net level? Powered up and exercised like the finished product?

AOI, X-ray, ICT, and functional test all reduce risk, but they do not catch the same issues. A strong electronics manufacturing strategy uses the right method for the right failure mode instead of assuming one inspection step can prove everything.

At Micron, this matters because high-mix, low-volume PCB assemblies often have different combinations of SMT parts, through-hole components, firmware, customer-specific acceptance criteria, and test requirements. The right coverage depends on the product, the design data, the volume, and the risk of a field failure.

Quick Answer

What each method is best at catching

Think of these as four different lenses. Each one sees something the others may miss.

A

AOI

Best for visible assembly conditions: missing parts, skewed components, polarity, solder bridges, insufficient solder, and placement issues.

X

X-ray

Best for hidden solder joints and features AOI cannot see, including BGA/QFN joints, voiding, shorts, and hidden alignment issues.

I

ICT

Best for circuit-level manufacturing faults: opens, shorts, incorrect values, orientation, basic powered checks, and net-level coverage.

F

Functional Test

Best for proving behavior: power-up, interfaces, sensors, firmware, calibration, loads, communication, and real-world operation.

Coverage Flow

A stronger test strategy layers coverage

The most practical approach is usually not “pick one.” It is to decide which risks matter, then build a coverage plan that catches issues as early and efficiently as possible.

Layered inspection and test strategy A process map showing AOI, X-ray, ICT, and functional test as layered checkpoints moving from assembly verification to product behavior verification. AOI Visible assembly conditions X-ray Hidden solder and voids ICT Component and net faults Functional Product behavior and firmware
Coverage Matrix

What each method catches — and what it does not

No single inspection or test method catches everything. The best test strategy depends on the board design, component types, risk level, available test access, and what the product needs to prove before shipment.

AOI

Automated Optical Inspection

Good at catching

Missing parts, wrong polarity, visible solder defects, skewed components, obvious placement issues.

May not catch

Hidden solder joints, internal opens, marginal electrical behavior, firmware or functional issues.

Most useful when

The board has visible SMT joints and the goal is fast, consistent workmanship inspection.

X-ray

X-ray Inspection

Good at catching

Hidden joint issues under BGAs, QFNs, LGAs, bottom-terminated parts, solder bridges, voiding, opens.

May not catch

Incorrect firmware, software behavior, many functional failures, or issues unrelated to hidden solder joints.

Most useful when

The assembly includes components where solder joints cannot be fully inspected visually.

ICT

In-Circuit Test

Good at catching

Opens, shorts, wrong values, missing components, many component-level and net-level electrical issues.

May not catch

Full product behavior, user-interface issues, wireless behavior, enclosure-level issues, final system performance.

Most useful when

The design has adequate test access and repeat production volume justifies a fixture or defined test setup.

Functional

Functional Test

Good at catching

Power-up failures, firmware issues, input/output problems, communication failures, product-level behavior.

May not catch

Some hidden solder defects, marginal component values, or process issues that do not affect the tested functions.

Most useful when

The assembly must prove that it behaves correctly in a realistic operating condition before shipment.

Method by Method

A closer look at the four checkpoints

Each method has a role. The best choice depends on what the design needs to prove.

A

AOI: automated optical inspection

AOI is a visual inspection tool. It uses cameras and programmed criteria to compare the assembled board against expected placement, orientation, and solder conditions.

  • Catches missing, shifted, skewed, or tombstoned components.
  • Helps flag visible solder bridges, insufficient solder, and polarity issues.
  • Works well as a fast process-control checkpoint after SMT assembly.
X

X-ray: seeing hidden solder joints

X-ray inspection is used when important joints are not visible from the outside. It is especially helpful for BGAs, QFNs, bottom-terminated parts, and dense assemblies.

  • Helps evaluate hidden bridges, opens, solder volume, and voiding.
  • Useful when AOI cannot see the actual solder interface.
  • Can support documentation needs when image retention is requested.
I

ICT: circuit-level manufacturing test

In-circuit test uses physical access to the board to check electrical conditions at the component and net level. It is strongest when test access is designed in early.

  • Catches opens, shorts, incorrect values, missing parts, and some orientation problems.
  • Can provide fast fault isolation compared with a broad functional failure.
  • Depends heavily on probe access, net coverage, fixture design, and DFT planning.
F

Functional test: proving the product works

Functional test checks whether the assembly behaves as intended. It may include power-up, firmware, communication, load, sensor, interface, calibration, and end-of-line checks.

  • Catches behavior-level problems that visual inspection cannot prove.
  • Validates firmware loading, I/O, communications, sensors, and expected outputs.
  • Works best when pass/fail criteria and test steps are defined before production.
Practical Sequence

A common way to think about order

The exact order depends on the board and the test plan, but many assemblies move through a layered sequence like this.

Inspect the build

Use AOI and visual review to confirm placement, polarity, and visible solder conditions after assembly.

Check what is hidden

Use X-ray where the solder joint or termination cannot be verified optically.

Verify the circuit

Use ICT or flying-probe style checks when net-level or component-level coverage is needed.

Prove behavior

Use functional test to confirm the assembly performs the job the product requires.

Customer Planning

What to share when planning inspection and test

The earlier an EMS partner understands your test intent, the easier it is to recommend practical coverage and avoid late surprises.

For AOI and X-ray

  • Assembly drawings and polarity/orientation notes.
  • Critical components, BGAs, QFNs, fine-pitch ICs, and bottom-terminated parts.
  • Customer-specific inspection criteria, image retention needs, and reporting expectations.

For ICT or flying-probe

  • Gerbers/ODB++, netlist, BOM, and test-point information.
  • Known critical nets, programming headers, boundary-scan requirements, and access constraints.
  • Expected test coverage, pass/fail criteria, and whether a fixture is justified by volume.

For functional test

  • Power requirements, safe startup sequence, and current limits.
  • Firmware files, programming instructions, communications interfaces, and expected outputs.
  • Calibration steps, fixtures, scripts, golden units, logs, and acceptance limits.

For documentation

  • Required records, lot-level traceability, serial numbers, labels, and traveler requirements.
  • Whether the build needs AOI/X-ray images, test reports, programming logs, or certificates.
  • Revision level for the BOM, PCB files, firmware, test procedure, and customer drawings.
External Reference

Standards help define what “good” means

Inspection and test only work when expectations are clear. IPC standards are a useful external reference for electronics manufacturing quality, reliability, and consistency expectations. For an OEM, the practical takeaway is to define workmanship class, inspection needs, test requirements, and acceptance criteria early.

Related Micron Capabilities

Inspection and test planning connects directly to assembly, NPI, programming, documentation, and repeat-build readiness.

The right question is not “Was it tested?” It is “What risks did the test strategy cover?”

AOI helps confirm visible assembly quality. X-ray helps verify hidden solder conditions. ICT helps isolate circuit-level manufacturing faults. Functional test helps prove the assembly behaves as intended.

For many products, the best answer is a practical combination. Micron can help review the design data, test intent, critical components, quantities, and documentation needs to recommend a coverage plan that fits the build.

  • Share BOM, Gerbers/ODB++, pick-and-place data, assembly drawings, and test intent.
  • Identify critical components, firmware needs, serialization, calibration, and reporting requirements.
  • Clarify whether the build is a prototype, pilot run, or repeat production program.

What to Send an EMS Partner for a Faster, More Accurate Quote

Jun 12
EMS Basics

What to Send an EMS Partner for a Faster, More Accurate Quote

A practical quote-package checklist for OEMs preparing a PCB assembly, prototype, pilot run, or production build.

Quote readiness BOM + Gerbers Test + programming notes
BOM Gerbers / ODB++ Assembly Drawing Test Plan Quote Review scope, risk, schedule

Quote package

12

point checklist for a complete request.

What improves

Fewer gapsFaster reviewBetter scope

Clear inputs help engineering, sourcing, and production quote with fewer assumptions.

New blog direction: practical manufacturing guidance from the Micron floor, built to help customers move from design to reliable assembly with fewer surprises.

When you are ready to quote a new electronics build, the quality of the information you send matters. A complete quote package helps your EMS partner understand the scope, identify potential issues early, and respond with a more accurate cost and timeline.

Transitioning the blog

Good quotes start before the board reaches the floor.

As Micron’s blog expands beyond recent tariff-focused content, we will be sharing more practical guidance from the manufacturing floor: what helps projects move smoothly, what causes delays, and how OEMs can reduce risk from prototype through production.

This first topic is one of the most important: what to send your EMS partner when requesting a quote.

Quote package BOM Gerbers
A complete quote package gives engineering, sourcing, and production teams the context they need to quote with fewer assumptions.

The takeaway: a quote package does not need to be complicated. It does need to be complete, current, and clear enough for an EMS partner to evaluate materials, assembly, test, documentation, and schedule.

Files and design data

The core files your EMS partner needs.

The first group of files defines the product: what parts go on the board, where they go, how the board is fabricated, and what the finished assembly should look like.

Core quote files Four inputs that help define the product before quoting begins. BOM MPNs, quantities, alternates Gerbers Layers, mask, drill, copper PnP / Centroid X/Y, rotation, board side Drawings Orientation, notes, hardware
The best quote requests include both machine-readable data and human-readable drawings, so engineering and production can see the same intent.

1. Bill of Materials

The BOM is one of the most important files in any quote package. It should include manufacturer part numbers, reference designators, quantities per assembly, descriptions, approved alternates, do-not-install notes, RoHS or leaded requirements, and revision level.

Approved alternates are especially helpful. Component availability can change quickly, and pre-approved alternate parts can prevent delays during quoting, sourcing, and production.

2. Gerber or ODB++ files

Your EMS partner will need the fabrication data for the printed circuit board. These files help the manufacturing team understand the board layout, copper layers, solder mask, silkscreen, drill data, and other important PCB details.

3. Pick-and-place or centroid data

Pick-and-place data tells the assembly equipment where each component should be placed. Accurate centroid data helps reduce setup time and prevents errors during machine programming.

4. Assembly drawings

Assembly drawings provide the human-readable instructions for how the board should be built. They are especially important for mixed-technology builds, through-hole parts, connectors, mechanical hardware, labels, or anything that may not be obvious from the BOM alone.

5. PCB fabrication drawing

If your EMS partner is also quoting the bare board or managing a turnkey build, include the PCB fabrication drawing. Board dimensions, material requirements, copper weight, finish, thickness, stackup, tolerances, and controlled impedance notes can affect cost and lead time.

Scope and assumptions

Quote the build, not just the board.

Two projects can use the same PCB data and still require very different quoting assumptions. Share the business and production context behind the build.

01

Quantities

Include prototype, pilot, production, and annual volume targets when available.

02

Schedule

Explain whether the build supports a demo, regulatory test, replenishment order, or hard ship date.

03

Revision control

Confirm that BOM, Gerbers, drawings, firmware, and instructions all match the current revision.

It is also helpful to clarify whether the build is consigned, turnkey, or hybrid. Each model can work well, but they affect quoting, scheduling, receiving, inventory control, and risk management.

Context changes the quote. Prototype, pilot, and production builds often need different planning assumptions. Prototype 5 to 10 units Pilot 25 to 100 units Production Repeat demand Program Forecast + revs
The same PCB may quote differently depending on the quantity, stage of the program, sourcing model, and schedule pressure.

End-of-line readiness

Bring test and programming into the quote early.

Testing and programming are easy to under-scope during quoting, but they can have a major impact on cost, schedule, documentation, and production flow.

Test and programming are part of the build. Define procedures, fixtures, firmware, and pass/fail criteria before production launch. Test procedure Fixture + DUT Programming log
Defining test, programming, serialization, and verification requirements early helps prevent late-stage production delays.

Test requirements

If test requirements are known, include in-circuit test, flying-probe test, functional test procedure, power-up instructions, calibration steps, fixture needs, pass/fail criteria, and required reports. If no test process exists yet, say so. Your EMS partner may be able to help define a practical approach.

Programming requirements

If the assembly requires firmware loading, serialization, MAC addresses, keys, device provisioning, or verification logs, include the programming files and instructions up front.

The practical list

A simple quote package checklist.

Before sending your next PCB assembly quote request, gather the following:

BOMManufacturer part numbers, quantities, alternates, notes, and revision.
Gerbers or ODB++Fabrication data for PCB layout and manufacturing review.
Pick-and-place dataReference designators, coordinates, rotation, and board side.
Assembly drawingHuman-readable build instructions and special notes.
Fabrication drawingBoard dimensions, stackup, material, finish, and tolerances.
QuantitiesPrototype, pilot, production, and annual volume expectations.
ScheduleDesired timing and the business reason behind the deadline.
Test requirementsICT, flying probe, functional test, fixtures, and pass/fail criteria.
Programming instructionsFirmware, serialization, MAC addresses, tools, and verification steps.
Special processesConformal coating, labels, packaging, cleaning, or reporting needs.
Build modelConsigned, turnkey, or hybrid material preference.
Revision controlConfirm all files match the current design revision.

Final thought

The best EMS projects start with clarity.

The best EMS projects start before the first board reaches the production floor. They start with clear data, clear expectations, and early communication.

If you have a new prototype, pilot run, or production build coming up, sending a complete quote package is one of the simplest ways to save time and reduce risk.

Have a build ready to quote?

Send your BOM, Gerbers, drawings, test notes, programming requirements, and schedule goals. Micron can review the package and help identify the clearest path from design data to reliable assembly.

EMAIL OR CALL US
(781) 949-3500