PCBA inspection coverage: AOI X-ray and functional test boundaries

A PCBA quotation that lists AOI, X-ray and functional testing can still leave important faults outside its acceptance plan. The names describe methods, not the exact features inspected or behaviors exercised. To understand coverage, connect each requirement to a defined observation, an acceptance criterion and a retained result.

This guide proposes a coverage review for a populated controller board. It focuses on the boundaries between inspection and electrical testing, including how to document gaps and approve changes. It does not claim that a particular machine, supplier or sequence detects every possible defect. The useful deliverable is a reviewable coverage matrix for the actual board revision.

Define what the word coverage means in the quotation

Start by separating population coverage from defect coverage. Inspecting every board does not mean inspecting every joint, and inspecting every visible joint does not mean detecting every relevant fault. Ask the supplier what the claimed percentage counts: boards, components, pins, nets, solder joints, test requirements or another defined population.

Keep the denominator visible in every report. If a board contains one hundred defined test requirements and eighty are exercised, the remaining twenty need a disposition. A statement that all shipped boards passed the available eighty checks does not close those gaps. The two statements can both be true while describing very different levels of assurance.

Include the planned methods in the assembly inspection and testing scope, but require the coverage matrix as a separate deliverable. This helps purchasing compare proposals without assuming that identical method names represent identical programs, access or acceptance criteria.

Write rows for faults and requirements, not machine names

For each important feature, identify the fault or requirement that matters. Examples include a reversed polarized component, a missing connector pin connection, a wrong programmed revision or a sensor channel that responds incorrectly to a known input. Give each row a unique identifier so that discussion and approval remain tied to a specific question.

Then identify the proposed evidence. A visible orientation mark may support a polarity inspection; an electrical stimulus and response may support a channel check. State the conditions under which that evidence is meaningful. If a marking is hidden after assembly or the channel cannot be stimulated through the available fixture, the planned method needs revision before it can be counted as coverage.

Avoid filling the matrix with an unchecked list of everything the equipment vendor says a platform can do. The installed options, fixture, program and board access determine what is actually implemented. Ask the test engineer to distinguish implemented checks from proposed checks and from capabilities that are unavailable for this design.

Make optical access part of the inspection claim

For an optical inspection row, identify the feature to be observed and the assembly stage at which it remains visible. Tall parts, shielding and enclosure work can change access. Record whether inspection occurs before those obstructions are fitted, and how the inspected board remains associated with the later completed product.

Ask for representative images from the actual setup when the observation is uncertain. A clear view of one component does not establish the same visibility for a similar component surrounded by different hardware. Where the program depends on a marking, confirm that the supplied component packaging and approved alternatives retain a usable feature.

Record how an ambiguous optical call is reviewed. The operator should know which image, reference or acceptance document governs the decision, and the system should preserve the disposition. Repeatedly accepting a call because the board eventually works can undermine the purpose of an independent assembly inspection.

Use X-ray to address a defined hidden feature

OMRON’s January 2024 technical paper on CT-type automated X-ray inspection discusses solder joints beneath components that are inaccessible to optical methods. It also describes overlapping structures in transmission images and the use of reconstructed CT data to separate features. This supports asking which imaging method and view address the specific joint, rather than treating every X-ray image as equivalent evidence.

Specify the locations, image conditions and acceptance rules that the inspection plan will use. If the proposal covers only selected packages, list them. If sampling is planned, document the sampling basis and the action when a suspect condition appears. Do not let the phrase “X-ray included” conceal a scope that changes informally from one batch to the next.

Keep image interpretation separate from an electrical conclusion. The coverage row should say what physical feature the image evaluates. A functional requirement still needs evidence appropriate to that requirement. Conversely, a board that passes a limited functional test does not automatically resolve an unacceptable physical observation at a hidden joint.

Define electrical tests in the context of the actual circuit

Keysight’s technical overview Electronic Components Tolerance and Test Limits for In-Circuit Test, document 5992-2186EN, explains that assembled-circuit measurements depend on parallel paths, circuit topology and the measurement setup. It discusses guarding and measurement uncertainty when establishing limits. A bare component’s nominal value and tolerance therefore do not automatically provide a complete production-test limit.

For each electrical row, identify the stimulus, measurement points, operating state and decision limits. Ask who approves the method and what evidence supports repeatability. If a fixture contact or an inaccessible node prevents a planned measurement, mark the row as an open coverage issue. Do not count a test merely because its name appears in the program file.

Maintain a connection between the test program and the schematic revision. A component change can alter the measured path even when the test-point labels remain the same. The responsible engineer should review the affected checks and record why their methods and limits remain valid or what must change.

Separate a boot check from functional acceptance

A controller that starts and reports a version string has demonstrated a useful behavior, but it has not necessarily exercised every input, output or operating mode. Define which functions the production test covers, including the external equipment or fixtures needed to stimulate them. Identify requirements that remain part of engineering validation rather than routine production screening.

For an illustrative analog input, specify the applied reference condition, relevant configuration, expected response and decision method. For a communication interface, define the transaction to be completed and the counterpart used in the test. Avoid accepting a generic “communication passed” entry when the test only establishes that a connection was opened.

Record the firmware and configuration actually tested. If programming occurs after an earlier electrical screen, preserve that sequence in the record. If software changes later, the test owner must decide which results remain applicable. A serial number can stay constant while the behavior under test changes substantially.

Review a worked coverage example before approving the batch

Imagine a controller with a hidden-joint processor, a visible polarized capacitor, two sensor inputs and a relay output. The proposed process uses optical inspection, selected X-ray views and a brief power-on test. Ask the supplier to describe the evidence for each of these four feature groups rather than giving one overall pass statement.

The capacitor orientation may have an agreed visible inspection feature. The processor joints may need the selected imaging program and a defined interpretation criterion. The two sensor inputs require an appropriate stimulus if their behavior is to be accepted. The relay output requires a check that addresses the intended output condition, rather than assuming that processor boot implies correct relay operation.

This example is a planning exercise, not a prescribed universal test sequence. Its purpose is to expose rows for which the proposed method does not answer the requirement. Engineering can then decide whether to add access, change a fixture, introduce another check or accept a specifically documented limitation. The unresolved rows should remain visible in the quotation and release decision.

Validate the response to faults and uncertain results

Ask the test engineer how each important check was shown to discriminate the intended condition. The evaluation may use approved reference samples, controlled fault simulations or other appropriate validation evidence. Define the method without damaging production stock or introducing uncontrolled modifications into units intended for shipment.

Keep false calls and confirmed defects distinguishable in the records. An inspection station that generates many ambiguous calls needs a review process, but reducing calls by removing checks can also reduce coverage. Record any program change with its reason and its effect on the matrix. A better apparent pass rate is not, by itself, proof that the test became more effective.

Specify what happens after a failed unit is repaired. Identify the checks invalidated by the repair and the required retest route. Preserve the original failure and the final disposition against the unit. Replacing the first result with a later pass loses information that can help distinguish an intermittent problem from a completed repair.

Release a coverage package that purchasing can compare

The final package should name the board and assembly revisions, inspection and test program revisions, covered locations, functional requirements, acceptance criteria and record-retention scope. Include an explicit gap list with engineering dispositions. Keep the approved matrix under change control so that a repeat order does not silently inherit a different inspection scope.

Use the quotation comparison tool to record differences in fixture development, program validation, routine inspection and supplied test records. A lower quotation may simply omit work that another supplier included. Resolve those differences before comparing unit prices or accepting a claim of equivalent coverage.

For a project test-scope review, provide the schematic, BOM, board files, intended functions and known access constraints. The result should be an agreed set of checks and openly documented limits, allowing the manufacturing team and product owner to make the same acceptance decision from the same evidence.