3.8 Recall drill procedure + “reverse genealogy report” template

A recall is not a “possibility”; it is a statistical certainty. When a raw material defect is discovered, the difference between a minor logistical annoyance (recalling 500 units) and a company-ending event (recalling 50,000 units) is the precision of your data scope. Traceability is the insurance policy; the Recall Drill is the fire inspection to prove the policy pays out.

The mandate: drill cadence

A crisis must not be waited for to test database query speed. A “Mock Recall” must be executed on a strict, recurring schedule.

• Frequency: Bi-Annual (Every 6 months).
• Method: Double-Blind approach. The Quality Manager selects a target (e.g. “Capacitor Lot X”) without providing warning to Operations or IT.
• Objective: Produce the complete Containment List within the defined SLA (Service Level Agreement) timeframe.

Drill scenarios

The traceability system must be tested against the three primary vectors of failure.

Scenario a: the poisoned ingredient (upstream)

• Trigger: A Supplier notifies you that Lot_A123 of Resistor_R1 is defective.
• Query Logic: Select all Parent_SN records where the associated Child_Lot = ‘Lot_A123’.
• Goal: Find every unique finished good containing this specific batch.

Scenario b: the process excursion (internal)

• Trigger: Maintenance discovers that Reflow Oven 3 had a broken circulation fan between 08:00 and 10:00 yesterday.
• Query Logic: Select all Parent_SN records where Machine_ID = ‘Oven_3’ AND Timestamp BETWEEN ‘08:00’ AND ‘10:00’.
• Goal: Quarantine only those specific units processed during the thermal excursion window.

Scenario c: the contagion (downstream/field)

• Trigger: A Customer returns 3 units from the field with cracked screens.
• Query Logic: Commonality Analysis must be performed by comparing the deep genealogy trees of the 3 failed units.
• Goal: Identify the most likely common factor (e.g. “All 3 units used Glass from Lot Z”).

Success criteria (the SLA)

A drill must be considered a “Fail” if it produces the correct data but does so too slowly to prevent further damage.

• Time-to-List (TTL): Target a return time of < 1 Hour. (If it naturally takes 24 hours to query the database, the shipment has likely already left the port).
• Completeness: Demand 100% accuracy. Missing a single unit implies a “False Negative” risk, potentially forcing the business to recall the entire month’s production to be safe.
• Containment: Expect physical quarantine confirmation of all WIP units within 4 Hours.

Pro-Tip: Relying solely on the ERP for deep tree traversal should be avoided, as ERP structures run flat. The native MES or a dedicated Graph Database (e.g. Neo4j) designed for deep genealogy queries must be used to ensure speed.

The “reverse genealogy” report template

When executive leadership asks “How bad is it?”, sending a raw SQL data dump should be avoided. It is much more effective to use a standardized template to categorize the risk clearly.

Section 1: scope definition

• Trigger: [Input Value, e.g. “Solder Paste Lot 99”]
• Date Range: [Start Date] to [End Date]
• Total Affected Count: [Integer]

Section 2: disposition matrix (the “where is it?” table)

Categorize the affected units by their current physical state to determine financial impact.

Category	Definition	Count	Action Required
WIP (Factory)	Units currently on the production line.	[Qty]	Immediate Stop. Route to Rework or Secure Scrap.
Inventory (FGI)	Units in the warehouse (Boxed).	[Qty]	Administrative Hold applied. Do not ship. Unbox for rework routing.
In-Transit	Shipped but not arrived at Customer.	[Qty]	Active Recall from Carrier. Intercept shipment.
Delivered	In Customer possession.	[Qty]	Initiate Field Recall. Issue RMA. (This represents the Highest Liability).
Scrapped	Units already destroyed during normal process.	[Qty]	None. (This is an Accounting Write-off only).

Section 3: the hit list (data extract)

(Attach as CSV)

• Parent_Serial_Number
• Current_Location (e.g. “Pallet 5, Rack B” or “Customer X”)
• Work_Order_ID
• Date_Produced

Post-drill analysis (the “autopsy”)

If the drill fails, fixing the system architecture immediately must be committed to.

• When Time-to-List > 4 Hours, index the Database properly. Your current query performance is inadequate for production scales.
• When “Ghost Units” are found (e.g. the System says FGI, but the Warehouse shelf is Empty), trigger a full Internal Inventory Audit.
• When a Data Gap is discovered (e.g. an “Unknown Component Lot” appears in the tree), halt the Line and firmly enforce the Supplier Interlocks discussed in Section 3.3.

Final Checkout: Recall drill procedure + “reverse genealogy report” template

Category	Metric / Control	Threshold / Rule
Cadence	Drill Frequency	Minimum 2x / Year (Bi-Annual).
Speed	Time-to-List	< 1 Hour to generate the list of affected Serial Numbers (SNs).
Accuracy	Capture Rate	100%. Zero tolerance for missing links.
Scope	Dimensions	Drill must test Supplier (Lot), Internal (Time), and Field (Serial Number) triggers.
Reporting	Disposition	Report must split counts by Work In Progress (WIP) / Finished Goods Inventory (FGI) / Shipped.
Containment	Physical Action	Affected Work In Progress (WIP) must be electronically locked (Hold status) immediately.