Skip to content
Your Bookmarks
    No saved pages. Click the bookmark icon next to any article title to add it here.

    7.3 Test process quality: ICT/FCT & retest limits

    Testing is an appraisal process designed to verify the hardware. It’s important to understand that a test station does not fix poor quality; its role is to identify functional units and segregate failures. In high-reliability Electronics Manufacturing Services (EMS), one of the most concerning practices is “Testing Into Compliance”—repeatedly re-testing a failed unit until it passes. This introduces significant risk. When a PCBA fails an electrical test once, its integrity is suspect. If it passes on a subsequent attempt without a documented repair, an intermittent defect is likely present. The goal of Test Process Quality is to establish clear procedures and enforce consistent retest logic across the factory to prevent field failures.

    In-Circuit Testing (ICT): the structural audit

    Section titled “In-Circuit Testing (ICT): the structural audit”

    ICT functions as the electrical equivalent of an X-Ray. It verifies that discrete components are present, oriented correctly, and are not electrically shorted to their neighbors. It does not prove the complex device fully works; it only confirms the device was built to match the CAD schematic.

    False Call Management:

    ICT mechanical fixtures rely on thousands of spring-loaded “pogo pins” contacting tiny copper test points. Microscopic dust, flux residue, or slightly warped PCB substrates can cause false failures.

    • The Baseline Metric: The station’s First Pass Yield (FPY) should be sustained above 95%.
    • The Engineering Logic: Whenever the ICT FPY drops below 90%, it is necessary to pause the line. The fixture pins should be cleaned, and electrostatic debris should be vacuumed. The focus should be on verifying the strain gauge stress on the PCBA and addressing mechanical noise, rather than temporarily widening electrical test limits to ignore the issue.

    Functional Testing (FCT): the behavioral audit

    Section titled “Functional Testing (FCT): the behavioral audit”

    FCT actively simulates the customer’s real-world application. It powers up the board, injects real signals, and executes the compiled firmware.

    The “No Trouble Found” (NTF) Paradox:

    This scenario occurs when a unit fails the automated FCT on the line but passes when an engineer tests it manually on a laboratory bench.

    • The Risk: The automated FCT pneumatic fixture often imposes mechanical flexing stress or artificial timing constraints that differ from how the board is situated in its final enclosure.
    • The Action: Perform a formal Correlation Analysis. If the manual “Bench Pass” rate exceeds 90% for units that failed FCT, it suggests the software limits are set too tightly, or the fixture itself is mechanically unstable.

    Retest limits (the “three strikes” rule)

    Section titled “Retest limits (the “three strikes” rule)”

    It is beneficial to define and electronically lock a software limit on the number of times a unique serial number can be cycled through a test station. Allowing infinite manual loop testing can hide intermittent failures, such as fractured cold solder joints.

    Decision Logic for Retest:

    • Pass 1: The unit enters the test fixture for the first time.
      • Result: FAIL.
      • Action: The board should not be removed. Visually check the mechanical seating and cable connections. Then, retest precisely once (Pass 2).
    • Pass 2 (The Only Retest):
      • Scenario A:
        • Result: PASS.
        • Status: Conditional Pass.
        • The Risk: An intermittent structural contact or a marginal test pin may be present.
        • The Requirement: This unit must be visually inspected under a microscope for flux flooding or contamination on the failing test pads before it is released to the customer.
      • Scenario B:
        • Result: FAIL.
        • Status: Fail. The unit requires repair and should be routed to the Debug area.
    • Pass 3:
      • PROHIBITED. A unit failing the exact same test twice is typically a hardware defect, not a software glitch.
      • The Action: The Manufacturing Execution System (MES) should electronically lock the serial number. The unit should be tagged as defective and kept off the active production line until it is debugged.

    The “Bonepile” is the designated area for failed units. It is also a highly valuable source of engineering data in the factory.

    Rules of Engagement:

    1. Aging Limit: Units should not remain in the Bonepile for more than 3 shifts (24 hours) without attention.
    2. Disposition: Every board must be formally diagnosed (debugged to root cause) or scrapped.
    3. WIP Cap: If the Bonepile inventory exceeds 50 total units, production should be paused. This indicates that scrap is being produced faster than the team can resolve it.

    Test StageParameter / ConditionRequirement / LimitAction / Disposition
    ICTFirst Pass Yield (FPY)Sustain >95%. Critical threshold: <90%.Pause line. Clean fixture, vacuum debris. Verify mechanical stress.
    FCTNo Trouble Found (NTF) RateManual bench pass rate >90% for FCT failures.Perform formal Correlation Analysis. Review software limits & fixture stability.
    Retest LogicTest Attempt CountMaximum 2 attempts (Pass 1 + Pass 2). Pass 3 prohibited.Pass 1 Fail → Check seating/connections, retest once (Pass 2).
    Pass 2 Pass →Conditional Pass”. Mandatory microscope inspection before release.
    Pass 2 Fail → Route to Debug/Repair. MES lock serial number.
    Bonepile ManagementAging & VolumeMax aging: 3 shifts (24h). Max WIP: 50 units.Diagnose or scrap all units. FIFO mandatory. If >50 units, pause production.

    Сообщение об ошибке