Skip to main content

1.18 Why Traceability Levels Matter

Traceability is the backbone of control in electronics manufacturing. It turns a sea of parts and processes into a verifiable story of each unit's creation. The level you choose is a fundamental strategic decision: it determines how precisely you can isolate failures and how much money you save or lose during a recall or customer return.

4.1.18.1 Traceability: The Manager's Risk Gauge

In simple terms, traceability ties a finished unit (or a lot) back to who built it, when, where, with which materials, and what happened to it (test results, rework history). Your genealogy model defines how deep that link goes.

The Trade-off Analogy

Think of traceability as a medical record.

  • No Traceability: You know you were sick last week.
  • Lot-Level: You know you were treated at Hospital A on Tuesday.
  • Unit-Level: You know Nurse Jane treated you at 3:15 PM and Dr. Smith signed off.
  • Component-Level: You know the exact manufacturer's lot number of the single pill you were given.

You pay for the complexity of the record, but you gain the ability to pinpoint the cause of a failure surgically, instead of quarantining an entire production run.

4.1.18.2 The Traceability Trade-off: Cost vs. Isolation Depth

This table compares the four main levels of genealogy, outlining the direct cost of implementation against the risk isolation gained.

Level

What You Capture

Complexity/Cost

Consequence of Failure (Risk Isolation)

None

Nothing

$ (Lowest Cost)

Guesswork. You cannot isolate a bad batch. All failures are treated as systemic.

Lot-Level

Work Order, Date Code, Line/Shift, Paste Lot. (Process only.)

$$ (Standard)

High Cost Blanket Quarantine. If one unit fails, you must often quarantine (or recall) the entire batch or shift it was built with.

Unit-Level

Unique Serial Number (SN), full process route, test results, operator/station per unit.

$$$ (Volume Standard)

Accurate Scope. You can pull the full history of the specific unit. You isolate only the affected units, saving recall costs.

Unit + Component Genealogy

SN, full route, AND every critical component lot code (e.g., BGAs, FETs).

$$$$ (Maximum Discipline)

Surgical Isolation. You can prove which units received the faulty batch of a specific component, enabling the smallest, most defensible recall possible.

4.1.18.3 Traceability as a Strategic Value

Choosing the right level is not just a technical checklist; it is a strategic lever for risk management and compliance.

A. RMA and Failure Analysis

Traceability is the first step in solving a customer Return Material Authorization (RMA):

  • Fast Root Cause: If a unit with Unit-Level SN fails, you instantly pull its test logs, AOI images, and rework history. You find the cause in minutes.
  • Defensible Claims: With Component Genealogy, you can return to your supplier with undeniable proof that their lot caused your board failure, successfully pursuing credit or compensation.
  • Containment: The ability to trace a problem to a specific lot of a single component (e.g., "Capacitor C12, Lot 55B") allows you to contain the issue to only those products built with that material, protecting your entire inventory and market reputation.

B. Compliance and Customer Contracts

For high-reliability markets, compliance dictates your required level:

  • Mandatory Depth: Industries like medical (ISO 13485) or aerospace may legally require Unit + Component Genealogy to be maintained for many years.
  • High-Risk Components: Critical parts (like BGAs, power modules) often require a Certificate of Conformance (CoC) from the supplier. Your traceability system must capture the link between the unit's serial number and that specific component's CoC/lot ID.

6.1.18.4 Making the Decision Explicit

The traceability decision cannot be left to chance on the factory floor. It must be locked down and enforced.

  1. Document the Level: State your chosen Traceability Level clearly in the Golden Data Pack and the Labeling/Traceability Specification. This sets the standard for the entire production system.
  2. Enforce with MES: Configure your MES routes to enforce the required scans. If you choose Lot-Level, the system must force the operator to scan the Work Order before starting. If you choose Component Genealogy, the system must pause at the placement station until the operator scans the component's supplier lot ID.
  3. Encode the Data: Ensure the physical marking (like the 2D barcode) on the PCB itself encodes the data required (e.g., Serial Number, Date, BOM Revision) so external systems can verify the unit's identity.


Back to top