Inspection engineering 繚 勛圖tv
ICT test planning for assembled circuit boards
Plan in-circuit testing around unique required nets, practical probe access and testable component behavior. Separate contact access from demonstrated fault coverage.
Share the product revision, required checks and expected records. Early questions are welcome.

Does 95% test-point access mean 95% defect coverage?
No. Access describes whether the tester can contact required locations. Fault coverage also depends on circuit topology, isolation, measurement limits, program design and the defects being considered. State the denominator before using any coverage percentage.
What is in-circuit testing?
In-circuit testing, or ICT, makes programmed electrical measurements on an assembled circuit board through an appropriate contact interface. It is commonly used to find manufacturing-related electrical problems and check selected component or network characteristics. A dedicated bed-of-nails fixture can provide many contacts for efficient repeated access on a stable product.
The usable measurement set depends on the circuit, accessible nodes, instruments, program and fixture. Resistances, capacitances, diode characteristics, connectivity and selected device or powered checks may be included where the system and design support them. The phrase ���ICT tested��� does not mean that every component has been electrically isolated or every product function has been exercised.
ICT is most valuable when design-for-test decisions are made before the layout is frozen. The schematic identifies what must be measured; the layout and fixture determine whether the required nodes can be reached reliably. A good scope also identifies what cannot be tested and which other method addresses the remaining product risk.
ICT versus flying probe and functional test
| Method | Primary planning question | Evidence to request |
|---|---|---|
| Fixture-based ICT | Can the required nodes and component checks be accessed repeatably? | Test program scope, coverage exceptions and fixture validation |
| Flying probe | Can moving probes perform the required measurements at the needed throughput? | Accessible locations, measurement set and cycle assumptions |
| Functional test | Does the assembly meet specified behavior under defined stimuli? | Requirements, firmware, measured results and approved limits |
| Optical or X-ray inspection | Is the specified visible or hidden geometry acceptable? | Images, review outcomes and interpretation criteria |
Compare flying-probe testing when product changes or fixture investment influence the choice. Use functional-test planning when the question concerns operating states, communications, outputs or performance under load. A structural test and a product-function test can both be necessary.
Do not compare coverage percentages unless they use the same fault model and denominator. Percent of nets contacted, components assigned a test, modeled faults detected and product requirements exercised are different metrics. A report should name the metric rather than presenting an unexplained ���coverage��� number.
Plan unique-net access and physical contact quality
Create an inventory of required electrical nodes from the test strategy, then map each one to a suitable physical contact. Multiple accessible pads on the same net are alternative contact locations, not multiple unique nets. Some nets need more than one contact for the chosen measurement, while other circuit areas may remain inaccessible or unsuitable for a particular test.
Review probe landing area, solder-mask opening, surrounding component height and the expected positional variation. Board support and fixture actuation should avoid excessive deformation. A fixture that reaches every point in the CAD model can still produce poor measurements if contacts are inconsistent or the board moves during actuation.
Keep test-point conventions consistent between design, fixture and test program. Document top and bottom side mapping, origins, net names and any panel-level handling. If a test point is removed or moved during an ECO, update the fixture and test data together. A valid BOM revision does not guarantee that the physical test interface is current.
Use product- and equipment-specific contact rules. This page intentionally does not give a universal test-pad diameter or probe pitch. The fixture supplier and test engineer must confirm the geometry for the actual system, expected life and measurement needs.
ICT access planner: separate access from fault coverage
Enter the number of unique nets required by your ICT strategy. Classify them once as accessible, inaccessible or not yet reviewed. The tool checks that the categories add up and reports both physical access and review completeness. It never converts these counts into a claim of electrical fault coverage.
ICT Unique-Net Access Planner
For example, a design can have 80 accessible nets out of 100 required nets while 10 remain inaccessible and 10 have not been reviewed. That is 80% declared physical access and 90% review completeness. It says nothing by itself about the ability to isolate components, detect every modeled defect or exercise product functions.
Use the open-net list in the engineering review. An inaccessible node may justify a layout change, an alternative accessible point, a different measurement approach or a documented complementary test. The correct choice depends on the product risk and the required fault model, not simply on improving the percentage.
Circuit interactions can limit the measurement
Components are connected to other components. Parallel resistive or capacitive paths can influence an in-circuit reading, and semiconductor junctions or power rails can affect how a measurement is made. Guarding, isolation strategies or different instruments may help in particular cases, but they must be designed and verified for the actual circuit.
A component marked ���tested��� in a coverage list should have an identifiable measurement and defect objective. Is the test checking presence, a value range, orientation, a connection or a powered behavior? These are not interchangeable. Keep unsupported fault types and exclusions visible so the product owner can make an informed decision.
Some assemblies can combine ICT with programming, boundary scan or selected powered tests. Those are system- and product-dependent capabilities, not a default promise on this page. They require compatible device data, test resources, electrical conditions and a validated program. A supplier should confirm the exact proposed scope.
Validate the fixture as part of the measurement system
The fixture is an electrical and mechanical interface. Wiring continuity, probe presence, shorts, alignment, contact force and board support all affect reliable measurement. A defect in the fixture can look like a product defect or create an untested connection. Fixture verification therefore belongs in the release and maintenance plan.
Use the bed-of-nails fixture access and force worksheet when defining targets, probe loading, board support and maintenance. Its physical-access count remains separate from ICT fault coverage.
describes verification of contacts and wiring in an ICT interface. It is a useful equipment-source reference for this distinction; it does not identify the tester used for a specific 勛圖tv order.
Use controlled reference methods and the approved verification procedure when introducing or modifying a fixture. A known-good assembly can support checks but should not be treated as an unlimited metrology standard. Define how probe wear, contamination, wiring changes and repeat-contact problems are detected and addressed.

Files, standards and report requirements
Prepare the schematic, BOM, placement data, test-point map and relevant CAD export with aligned revision identifiers. Include component tolerances, critical checks, variants, DNP rules and any restrictions on powered testing. State whether firmware or device programming is part of the requested route and who owns the program image and expected result.
IPC-A-610 and J-STD-001 address assembly acceptance and soldered-assembly requirements in their respective roles. The product-specific electrical test specification defines ICT measurements and limits. Confirm the applicable revisions and class through the contract and ; an in-circuit measurement cannot substitute for every workmanship requirement.
Request a report that identifies the unit or lot, test-program and fixture revisions, measured values where required, failure location and disposition. Define the handling of retries and reworked units. Reported yield should distinguish first-pass results from final results after intervention when that distinction is relevant to the customer.
ICT cost includes test engineering, fixture design and build, program verification, cycle time, maintenance and reporting. Quote these consistently when comparing suppliers. A low per-board figure can conceal setup or untested scope; ask for the included measurements and exceptions alongside the price.
Connect hidden-joint concerns to X-ray inspection and visible-feature concerns to AOI. Use first-piece review before continuing a new or changed setup. For manufacturing support, return to PCB Assembly and quality assurance with the required test scope.
ICT coverage review: ask for more than a percentage
Use these fields to scope the report with your quotation. The table is a planning example, not a 勛圖tv test result or a promise that every record is included by default.
| Record item | Information to include | Why it matters |
|---|---|---|
| Access map | Required unique nets, accessible nets and unresolved locations | Duplicate pads on one net do not increase unique-net coverage. |
| Fixture readiness | Support, alignment, contact verification and maintenance basis | Poor contact can create false failures or unstable readings. |
| Test definition | Measured component/net, stimulus, limits and program revision | Parallel paths can constrain what a reading proves. |
| Coverage exceptions | Untestable characteristics, alternative checks and open decisions | Assign an owner to each material gap. |
Walk through an engineering example
Illustrative review: two test pads connect to the same power net. Adding the second pad may help current injection or contact reliability, but it does not add a second unique tested net. Review the schematic and fixture strategy before increasing the reported access count.
Continue to define the operating functions that ICT does not establish.
The email link opens a draft for you to complete. Contact is a separate form; these pages do not send messages automatically.
Questions engineers and buyers ask
Does 100% net access mean 100% fault coverage?
No. Access is a physical opportunity to contact a net. Fault coverage depends on the circuit, measurement strategy, instruments and defined fault model.
Can ICT replace functional testing?
Not automatically. ICT can detect selected structural or component-related issues. Product behavior under defined operating conditions requires the applicable functional test cases.
Can every component be measured independently in circuit?
No. Parallel paths and active circuitry can limit isolation and interpretation. The test engineer must establish which measurements are valid and document exclusions.
What happens after a layout change?
Review test-point positions, net mapping, board support, fixture and program revisions. Revalidate the affected interface and measurements before relying on repeat results.
Turn the inspection question into an agreed scope
Send the current files, product revision, quantity and the requirements that matter to your application. Identify any unfinished criteria so the engineering review can address them explicitly.
Request the method, coverage, acceptance basis and report format with your quotation. Tool briefs can support the discussion; the Contact form does not automatically receive this page���s entered data.
Engineering references reviewed September 2026. Illustrations explain methods; equipment photographs do not establish product-specific coverage, inspection results or certification.