4.1 Why Traceability Levels Matter

Traceability is the backbone of control in electronics manufacturing,manufacturing. turningIt turns a sea of parts, processes,parts and operatorsprocesses into a verifiable story of each unit’unit's creation. The chosenlevel depth—lotyou codes,choose uniqueis serials,a orfundamental fullstrategic componentdecision: genealogy—it determines how precisely failuresyou can beisolate isolatedfailures and how confidentlymuch auditsmoney you save or lose during a recall or customer returns are managed. More than a compliance checkbox, it is a strategic lever: the right level protects margins, credibility, and response speed when problems surface.return.

4.1.1 WhatTraceability: “traceability”The reallyManager's meansRisk (in 30 seconds)Gauge

TraceabilityIn simple terms, traceability ties a finished unit (or a lot of units)lot) back to who built it, when, where, with which materials, and what happened to it along(test theresults, way.rework history). Your genealogy model defines how deep that link goes—unit-levelgoes.

only,

The unit→subassemblies,Trade-off orAnalogy

all

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 wayexact 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 component lots. Pickpinpoint the rightcause depthof anda you’llfailure solve returns surgicallysurgically, instead of recallingquarantining aan warehouse.entire production run.

4.1.2 LevelsThe (comparedTraceability side-by-side)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 youYou serializeCapture	Genealogy depth capturedComplexity/Cost	TypicalConsequence cost/complexity	Whenof itFailure fits	The(Risk risk you can’t controlIsolation)
None	Nothing	$None (Lowest Cost)	$Guesswork. (cheapest)	Internal prototypes, lab builds	You can’tcannot isolate a bad batchbatch. atAll all.failures are treated as systemic.
Lot-levelLevel	Work orderOrder, /Date dateCode, codeLine/Shift, Paste Lot. on labels	(Process route + line/shift + materials only.)by lot	$$	Stable consumer builds where defects are rare and escapes are obvious(Standard)	High Cost Blanket Quarantine. If one unit fails, you must often quarantine (or recall) the wholeentire lot.batch or shift it was built with.
Unit-level (serial number)Level	Unique SNSerial Number (SN), perfull PCA/product	Fullprocess routeroute, +test results, operator/station + test results per unit	$$–$$$	Most volume products; strong RMA handling	You may still lack component-lot links unless you log them.
Unit + component-lot genealogy	SN and every critical component lot used	End-to-end: materials, processes, tests per unit.	$$$ (disciplineVolume + data)Standard)	RegulatedAccurate Scope. /You safetycan markets;pull tightthe customerfull contractshistory of the specific unit. You isolate only the affected units, saving recall costs.
Unit + Component Genealogy	MoreSN, scanningfull & data quality work; requires MES discipline.

You’ll wire whatever level you choose intoroute, labels/markings,AND the encoded data spec, and the scanners/MES links later in this chapter (4.2–4.5).

4.1.3 How the right level pays off during a return (RMA)

Scenario A — You have unit serialization + genealogy.

• Customer gives SN. You pull its build route, test logs, and component lots in minutes; scope impact to specific SNs or lots, not a whole quarter. Close the loop in MES.

Scenario B — Lot-level only.

• You can time-box the issue to an order/shift/date code, but you’ll likely quarantine more units than necessary while you sort root cause.

Scenario C — No traceability.

• You’re guessing. Expect broad quarantines, longer downtime, and thin evidence for suppliers or customers.
  

4.1.4 Compliance & customer contracts (why “deeper” may be mandatory)

Some industries and customers require tighter genealogy (think medical devices, safety-critical, high-reliability). Your quality system (ISO 9001, ISO 13485) and customer specs will call out what must be recorded and for how long. If they say component-level traceability, that’s your floor.

Also note: high-risk components often come with traceability and Certificate of Conformance expectations from approved sources—your genealogy should preserve those links to the component lot.

4.1.5 What to capture at each depth (a practical map)

• Lot-level: work order/date code, line, shift, reflow profile ID, paste lot, panel ID.
• Unit-level: add the unit SN, ICT/FCT results, AOI/AXI images/flags, rework records that update serial status (no “ghost” fixes).
• Unit + component-lot: on top of the above, scanevery critical component lotslot code (e.g., BGAs, powerFETs).

  $$$$ devices,(Maximum safetyDiscipline)

  Surgical parts)Isolation. atYou issue—eithercan atprove kittingwhich units received the faulty batch of a specific component, enabling the smallest, most defensible recall possible.

  4.1.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 placement—andcompensation.
  • Containment: linkThe ability to trace a problem to a specific lot of a single component (e.g., "Capacitor C12, Lot 55B") allows you to contain the unitissue SNto inonly MES.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:

  • WhereMandatory it lives:Depth: IDsIndustries livelike onmedical (ISO 13485) or aerospace may legally require labels/marksUnit + Component Genealogy to be maintained for many years.
  • High-Risk Components: Critical parts (whatlike &BGAs, formatpower inmodules) 4.3),often arerequire read bya scannersCertificate 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.4 Making the Decision Explicit

  The traceability decision cannot be left to chance on the line,factory floor. It must be locked down and flow via APIs to MES/ERP—that’s how you eliminate “shadow spreadsheets.”enforced.

  1. 4.1.6 MakeDocument the decisionLevel: explicit (before PVT)

  • State your chosen traceabilityTraceability levelLevel clearly in the Golden Data Pack and the label/traceabilityLabeling/Traceability specSpecification. This sets the standard for the entire production system.
  • Enforce with MES: (what’sConfigure encoded, where, and when to scan). Include BOM rev if customers care about visible configuration.
  • Configureyour MES routes/operations/WIP statesroutes to enforce the scansrequired scans. If you expect;choose ifLot-Level, it’sthe notsystem requiredmust force the operator to scan the Work Order before starting. If you choose Component Genealogy, the system must pause at the station,placement itstation won’tuntil happenthe underoperator pressure.scans the component's supplier lot ID.
    
• Encode

  
  

  the

  ---

  
  

  Conclusion:Data: EstablishingEnsure the properphysical traceabilitymarking level(like beforethe production2D lock-inbarcode) ensureson issuesthe arePCB containeditself swiftlyencodes andthe compliancedata isrequired met(e.g., withoutSerial overspending.Number, ByDate, enforcingBOM itRevision) throughso labels,external scanners,systems andcan MES,verify manufacturersthe gainunit's bothidentity.

risk isolation and customer trust.