AOI: defect coverage and limitations

Automated optical inspection, or AOI, provides evidence about features observable by the configured optical inspection process. Its coverage depends on the production stage, inspected surfaces, reference data, and inspection program. Ask what was inspected and how findings were handled before treating “AOI passed” as a complete quality statement.

KLA’s PCB inspection and metrology overview distinguishes automated optical defect inspection from panel measurements. This distinction is useful when specifying records: detecting a visual difference and measuring a dimension are related but different tasks. Equipment descriptions from a vendor do not establish which inspection services a particular fabricator performs.

Identify the inspection stage

For a bare-board project, specify whether the discussion concerns an exposed circuit layer during fabrication or a later board condition. For an assembled board, component and solder-joint inspection is a different scope. Keep the inspected object and stage in the report title or accompanying record.

Distinguish an indication from a disposition

In a fictional review, an inspection system marks 12 locations for evaluation. The manufacturing record should explain how those indications were classified and resolved. The count alone does not identify accepted boards, rejected boards, repaired features, or false calls. Request the decision record appropriate to the project’s quality requirements.

If a feature is modified after inspection, determine what reinspection is required. Keep the original finding and the later disposition connected so the record does not become a disconnected collection of pass/fail screenshots.

Make coverage gaps explicit

Write a list of acceptance requirements and identify the method used for each. An optical check may contribute to one requirement while electrical testing, dimensional inspection, or construction analysis addresses another. A blank method assignment is a question to resolve before release.

For rigid-flex, relate this list to the region map. If a feature at a transition is important, identify the process stage at which it can be inspected and the record that will establish its acceptance. Do not assume an overall board report describes every regional detail.

Ask for proportionate records

Start with the feature that matters

An inspection requirement should identify the feature and the reason for checking it. For an exposed copper pattern, the concern might be an unintended interruption or connection visible at that process stage. For a later surface, the question may concern an opening or alignment. Write these as separate inspection objectives rather than assuming one generic AOI operation addresses every feature on the finished board.

Ask the process owner how the proposed setup covers the relevant geometry. The answer should connect the feature size, surface condition, reference data, and inspection configuration to the acceptance requirement. A machine’s advertised capability is useful background, but it does not by itself establish the performance of a particular production program. Keep the inquiry focused on the actual product and inspection stage.

Separate machine indications from affected boards

Return to the fictional set of twelve marked locations. Suppose review classifies seven as acceptable variations, three as confirmed defects on one board, and two as unresolved indications on a second board. There are twelve machine indications, three confirmed defect locations, one board with confirmed defects, and another board awaiting disposition. These are different counts, and none alone tells the reader the final shipment quantity.

If the lot contains twenty boards, dividing twelve indications by twenty boards gives 0.6 indications per board. It does not mean a 60 percent board rejection rate. Likewise, dividing the three confirmed locations by twelve indications describes the classification of those indications, not the fraction of all defects that the inspection detected. That latter question requires evidence about defects that may have been missed.

Use precise labels in any summary. Distinguish inspected units, indicated locations, confirmed defects, affected units, and final dispositions. The example is invented to explain counting conventions and is not production performance data. Its practical lesson is that a quality trend becomes misleading when its numerator and denominator change without explanation.

Validate the reference before interpreting a pass

An inspection compares the observed product with a defined basis. Identify the released design revision behind that basis and how the inspection program was created or updated. A correct comparison against obsolete reference data can still produce the wrong acceptance decision for the current order. Revision control therefore belongs in the inspection record, not only in the fabrication drawing archive.

When the design changes, review which inspection features are affected. A moved opening, altered copper pattern, or changed panel layout may require an updated program or a new setup check. Record the change and its verification. Do not assume that an unchanged board name means the inspection reference is unchanged, or that every program adjustment is automatically covered by a previous approval.

Plan around visibility over the process sequence

A feature may be accessible at one stage and hidden at a later stage. Map the requirement to the point in the process where useful evidence can be obtained. If a circuit layer is inspected before it becomes internal, retain the association between that inspection and the later assembly. A final surface image does not recreate the earlier opportunity to examine that buried pattern directly.

For a rigid-flex design, use the regional drawing to identify features that need particular attention. The rigid region, flexible span, and transition may have different surfaces or constructions at a given stage. Ask the fabricator to explain the inspection sequence for the relevant requirement. This creates a concrete coverage discussion without assuming that all regions are inspected in exactly the same physical condition.

Define complementary evidence by the question it answers

Optical inspection and electrical testing provide different kinds of evidence. A visible pattern comparison does not directly measure every net’s continuity or isolation under an electrical test condition. Conversely, an electrical pass does not describe every geometric feature or surface condition. An acceptance plan should assign methods to requirements and identify where the methods complement one another.

Other requirements may involve dimensions, coating characteristics, or internal construction. Choose the appropriate method with the responsible specialist rather than expanding the meaning of “AOI” to cover them all. The useful question is not whether a method is generally good, but whether the proposed evidence supports the specific acceptance statement being made for this board.

Make the disposition workflow traceable

For each significant finding, retain the location, classification, acceptance basis, and authorized disposition. If a repair or other modification is permitted, record what happened and what verification followed. A final pass should be connected to that history so a reviewer can understand how an initially indicated feature reached its accepted state.

Do not treat every indication as a manufacturing defect, and do not dismiss repeated indications without understanding their cause. Repeated calls at one feature may prompt review of the reference, setup, or process. The appropriate response depends on the evidence. The record should make that reasoning visible without turning an unconfirmed observation into a claim about shipped product quality.

Keep comparisons consistent over time

When reviewing a trend across lots, check that the inspection stage, program, acceptance basis, and counting convention stayed comparable. A reduced indication count after a program change may reflect fewer false calls, changed coverage, or a process improvement. The count alone cannot distinguish these possibilities. Preserve the change history and use supporting evidence before assigning a cause.

Also separate product changes from process changes. A simpler pattern may generate a different inspection workload even when production quality is unchanged. If the purpose is to compare process performance, choose a meaningful basis and document the limitations of the comparison. This makes a trend useful for engineering decisions rather than merely attractive in a report.

Request a report that supports a decision

A concise report can be sufficient when it identifies the board and revision, inspected quantity and stage, applicable program or reference, acceptance basis, and disposition of exceptions. More detail may be needed for an investigation or a specific customer requirement. Agree that scope before production so the necessary information is captured at the point where it exists.

The receiving team should be able to answer three questions from the record: what was checked, what conclusion was reached, and what remains outside that conclusion. If those answers are unclear, request clarification about the evidence rather than simply requesting a larger bundle of images. Good inspection documentation connects a defined method to a defined requirement and preserves the limits of that connection.

Agree the required report content before ordering. Useful fields include part revision, inspected stage, reference/program revision, acceptance basis, and disposition of exceptions. The objective is evidence that supports your acceptance decision, rather than a large file collection without traceability.

See our inspection and testing overview and quality documentation guide. Send your inspection coverage requirements through the inquiry form with the relevant drawing details.