Ben Miller, Mph Diary And Food Insp Division Minn Dept Of Ag


Published on

Presentation regarding Produce Traceability as presented to FDA & FSIS on December 9 & 10, 2009 in Washington, D.C.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ben Miller, Mph Diary And Food Insp Division Minn Dept Of Ag

  1. 1. Core Information Elements of a Product Tracing System Benjamin Miller MPH Miller, Dairy and Food Inspection Division y p Operations and Response Section Manager
  2. 2. Core Elements in Effective Systems • Systems concept critical – Modifications without a standardized system will not significantly improve traceability • System should be: – Standardized – Required of all entities in the supply chain – Electronic
  3. 3. Core Elements in Effective Systems Traceability should identify the the, – Who – What – When – Where – How of product creation and movement f
  4. 4. Core Elements in Effective Systems • An effectively designed system will protect public health by facilitating: – The identification of a vehicle during a traceback investigation • Triangulation of plausible exposures in an outbreak – Quick and efficient identification of all product(s) involved in a recall during a traceforward investigation
  5. 5. Core Elements in Effective Systems • Lot Coding g – A form of lot coding for all food – Where feasible, lot code feasible should appear on consumer unit – “Lot” defined by grower Lot grower, manufacturer, etc., but should be small enough to facilitate effective identification and recall of product
  6. 6. Core Elements in Effective Systems • Standardization – Links data across the supply chain – Allows maintenance of current “One Up / One One Down” system – Exists today and is in use by industry • Human and machine readable • GS1 • Application Identifiers – Does not “reinvent-the-wheel”
  7. 7. Core Elements in Effective Systems
  8. 8. Critical Tracing Identification Assignment and Retrieval Ship From Entity Ship To Entity Regulatory Inquiry Critical Tracking CTID Query sent to Listening GLN1 WebServer Events: CTID Assignment Server Step 7 Step 6 Regulatory CTIN – Must be unique Regulator or 3rd Party Controlled rv N2 Querying Database Se GL er eb to CT Querying CTID shows that g W ent ID GTIN3 was manufactured nin s As – Identified on te ery sig at GLN1 and further L is Q u ne investigation shows the ID source as contaminated d CT Shipment Initiated raw ingredients. invoices or via EDI CTID: ACB123 CTID: ACB123 Step 5 CTID Transmitted – “Key” to link other Internal Shipper DESADV DESADV Internal Receiver Database CTE4 Received Database Regulatory Agency tracing data CTE3 Identifies Food Safety Issue With GTIN3 • i.e. GS1 standards Warehouse – GLN2 Manufacturer - GLN1 Product Shipped Step 4 – Allows trading GTIN3 Step 3 partners to maintain “One-Step” One Step SSCC1 SSCC2 Step 2 SSCC1 SSCC2 traceability Micro GTIN1 GTIN2 GTIN3 GTIN4 GTIN1 GTIN2 GTIN3 GTIN4 Sample p Collected Step 1 Multiple Raw Ingredient Inputs