3.8 Recall drill procedure + “reverse genealogy report” template

A recall is not a “possibility”; it is a statistical certainty. When a defect in a raw material is discovered, the difference between a minor logistical issue—like recalling 500 units—and a catastrophic event that could threaten the company—such as recalling 50,000 units—comes down to the precision of your data. Traceability is your insurance policy; the Recall Drill is the regular fire inspection that proves the policy will pay out when needed.

Mandatory Drill Schedule

You should not wait for a crisis to test how quickly your database can be queried. A “Mock Recall” must be executed on a strict, recurring schedule.

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

Drill scenarios

Your traceability system should 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 Serial Number records where the associated Child Lot is ‘Lot_A123’.
Goal: Identify every unique finished good that contains this specific batch of material.

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 Serial Number records where the Machine_ID is ‘Oven_3’ and the Timestamp falls between ‘08:00’ and ‘10:00’.
Goal: Quarantine only those specific units processed during the identified thermal excursion window.

Scenario C: The contagion (downstream/field)

Trigger: A customer returns three units from the field with cracked screens.
Query Logic: Perform a Commonality Analysis by comparing the deep genealogy trees of the three failed units.
Goal: Identify the most likely common factor (e.g., “All three units used Glass from Lot Z”).

Success criteria (the SLA)

A drill should be considered a failure if it produces the correct data but does so too slowly to prevent further operational or financial damage.

Time-to-List (TTL): Target a return time of less than 1 hour. If it naturally takes 24 hours to query the database, the affected shipment has likely already left the port.
Completeness: Demand 100% accuracy. Missing even a single unit creates a risk of a false negative, which could force the business to recall an entire month’s production out of an abundance of caution.
Containment: Expect physical quarantine confirmation of all Work-In-Progress (WIP) units within 4 hours.

The “reverse genealogy” report template

When executive leadership asks, “How bad is it?”, avoid sending a raw SQL data dump. It is far more effective to use a standardized template that clearly categorizes the risk.

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 the financial and operational 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 (Root Cause Analysis)

If the drill fails, you must commit to fixing the underlying system architecture immediately.

If the Time-to-List exceeds 4 hours, your database likely requires proper indexing. The current query performance is inadequate for production-scale operations.
If “Ghost Units” are found (e.g., the system lists a unit as Finished Goods Inventory, but the warehouse shelf is empty), trigger a full internal inventory audit.
If a Data Gap is discovered (e.g., an “Unknown Component Lot” appears in the genealogy tree), halt the production line and enforce the supplier data interlocks discussed in Section 3.3.

Recap: Recall Drill Procedure and Reverse Genealogy Report

Parameter	Requirement	Value	Action on Failure
Drill Frequency	Mandatory double-blind test	Semi-annual (every 6 months)	N/A
Time-to-List (TTL)	Generate complete containment list	< 1 hour	Fix database indexing
Data Completeness	Containment list accuracy	100%	N/A
WIP Containment	Physically quarantine all affected WIP units	< 4 hours	N/A
System Performance	Execute deep genealogy queries	Use MES/Graph DB (not ERP)	N/A