Lot Pedigree

Lot pedigree is the authoritative, audit-ready dossier for a unique lot (or sublot), capturing source identity, custody chain, in-plant transformations, equipment and personnel context, quality testing, release decisions, and distribution handoffs. It extends basic genealogy beyond parent-child relationships to include the who, when, where, and under-what-conditions each event occurred, with secure linkage to the governing batch or device history and electronic signatures.

In regulated plants, the pedigree must support both backward and forward queries within minutes, be contemporaneously recorded, and be complete enough to substantiate release, deviation impact assessment, and recall scope. It spans receiving (raw materials) through processing, packaging, labeling, storage, and shipment, and persists identifiers such as supplier lot, internal lot, GTIN/UDI, and SSCCs, with a defensible audit trail consistent with 21 CFR Part 11 and good computerized systems practice.

ISA‑95 positions material and production tracking as Level 3 responsibilities: linking work-in-process, equipment, personnel, and quality states to material lots as they are transformed. Lot pedigree sits squarely in Level 3, while drawing identifiers and master data from Level 4 (ERP) and executing with Level 2/1 signals. Sector regulations set minimum content and retrievability: 21 CFR 211.188 defines batch record content for drugs; 21 CFR 820.65 requires traceability for selected devices and components; 21 CFR Part 1 Subpart S (FSMA 204) mandates traceability key data elements and critical tracking events for covered foods; and 21 CFR 1271.290 prescribes tracking for HCT/Ps.

Pharma/biotech: 21 CFR 211.188 requires batch production and control records that enable full traceability of components, processing steps, in‑process controls, and results. Pedigree must link supplier lots, internal lots, processing parameters, yield reconciliations, and release signatures. For radiopharma and sterile operations, pedigree supports rapid isolation of affected vials from a single parent batch during excursions.

Medical devices: 21 CFR 820.65 mandates traceability where appropriate, including retention of component and finished device identification to respond to quality problems or recalls. The device pedigree typically ties UDI-DI to manufacturing lot/serial, components, special process records, and distribution. Foods: FSMA 204 (21 CFR Part 1 Subpart S) defines Key Data Elements (KDEs) at Critical Tracking Events (CTEs); the food pedigree must capture and be able to retrieve KDEs like lot codes, quantities, and locations across receipt, transformation, and shipping. HCT/Ps: 21 CFR 1271.290 requires a tracking method from donor to recipient; the HCT/P pedigree links donor eligibility, processing steps, distribution, and recall communication paths.

A durable pedigree relies on stable keys and event semantics. Core identifiers include supplier lot, internal lot (and sublot), container IDs, SSCC for logistics units, GTIN for trade items, and UDI elements for medical devices. Each event attaches timestamps with time zone, location, equipment, operator, and disposition. Audit trails record who created or changed each element, the reason, and before/after values, supporting Part 11-compliant reconstruction.

• Parent-child links must be bijective enough to reconstruct both directions without manual inference.
• Timestamp sources should be harmonized (e.g., NTP-synchronized) to avoid causal ambiguities in event ordering.
• Identifiers should be immutable; corrections occur via superseding events, never silent edits.

Pedigree quality is determined at the point of execution. MES should enforce material scans and weigh‑by‑barcode, bind dispenses to containers and lots, verify equipment state and cleaning, and capture in‑process controls. Each recipe step creating or consuming material must log the lot, quantity (net), unit of measure, potency adjustments, and reconciliation footprint, with operator identification and review signatures where required. For devices, special processes (e.g., sterilization, welding) must tie back to lot or serial with process parameters and verification.

• Receiving: verify supplier lot, CoA, quarantine, and sampling links.
• Dispense: enforce verified scales, tare-and-net capture, double-witness where necessary.
• Process: bind equipment IDs, setpoints, alarms, deviations, and holds to material events.
• Packaging: link packaging material lots to finished lots or serials; record label issuance and reconciliation.
• Storage and shipment: capture location, SSCC aggregation, and release status checks at pick/ship.

Real-world pedigrees must handle merges (many-to-one), splits (one-to-many), and rework/returns. The data model should use event-driven associations rather than static foreign keys so that each transformation is time-stamped and reversible in analysis. Yield and loss accounting must reconcile to theoretical within tolerances to prevent phantom WIP. For potency-corrected components or assay-adjusted charges, store both gross and potency-adjusted net to support accurate backward impact analysis.

• Merges: retain proportional allocation factors for each input to support quantitative attribution during backward traces.
• Splits: prevent orphan sublots by inheriting all upstream links unless explicitly branched.
• Rework: close the original quality decision loop; ensure the reworked lot inherits full upstream pedigree plus a new transformation branch.
• Customer returns: model as reverse logistics events with regrade or quarantine paths; never overwrite the original shipment record.

Under 21 CFR 211.188, batch records must include in-process and laboratory data sufficient to determine if specifications were met; Part 11 requires that electronic records and signatures are trustworthy and reliable. Pedigree must therefore bind each test result and review decision to the lot with controlled method IDs, instrument IDs, analyst identity, and reviewer signatures, plus an audit trail capturing who did what, when, and why. Review-by-exception is acceptable when the system enforces completeness checks and exception workflows with secure, time-sequenced audit logs.

• Ensure every quality decision (approve, reject, conditional release) is time-aligned to material disposition changes.
• Link sample IDs to lots and containerized aliquots; record chain of custody through LIMS handoffs.
• Require role-based access with reason-for-change prompts to maintain audit integrity.
• Prohibit uncontrolled deletion; corrections occur via superseding entries with traceable justification.

Pedigree spans plant and supply chain. ERP provides item masters and lot policies; WMS provides location and logistics unit lineage (SSCC); LIMS provides test results and method status; and EPCIS events can externalize custody and aggregation. Align master data keys so that MES lot IDs map unambiguously to ERP lots, and configure GS1-compliant label content to keep SSCC and GTIN synchronized. When exposing pedigree to partners, use EPCIS event streams for receive, transform, and ship events while retaining the richer, regulated eBMR/eDHR pedigree internally.

Pedigree is only valuable if it is complete and retrievable on demand. Governance should define data owners, retention, and periodic verification via mock recalls and data integrity audits. KPIs include time-to-assemble pedigree for a finished lot, percentage of events with verified scans, audit-trail exception rates, yield reconciliation delta, and proportion of lots released with complete test-result linkage. For FSMA 204 foods, monitor KDE capture completeness by CTE. For devices, validate that UDI and component linkages support 820.65 trace requests within target SLAs.

• Target pedigree retrieval (end-to-end) under 2 hours for high-risk products; under 24 hours for others.
• Event scan verification rate greater than 99.5% for regulated consumption events.
• Zero orphan lots or containers in weekly data-quality sweeps.
• 100% audit trail review coverage for release-affecting changes.

V5 Ultimate persists a single, versioned execution record per lot that unifies MES transformations, QMS decisions, eBMR/eDHR signatures, LIMS results, WMS SSCC aggregations, and maintenance/equipment states. Parent-child, custody, and quality gates are modeled as immutable events linked by globally unique IDs and synchronized timestamps. Part 11 controls enforce signature meaning, time, and intent; integration adapters align GS1 identifiers to ERP and WMS. Backward and forward traces materialize instantly via indexed graphs, and review-by-exception dashboards surface missing KDEs and reconciliation gaps before release.

Typical findings include incomplete parent-child links during bulk-to-retail repack; manual lot entry at weigh or label issuance; audit trails missing reason-for-change; timestamps not synchronized across subsystems; and rework performed without updating impact assessment. In foods, missing KDEs at transform events subvert FSMA 204. In devices, UDI not bound to component lots undermines 820.65 responsiveness. In HCT/Ps, gaps in donor-to-recipient tracking violate 1271.290 mandates.

1. Eliminate free-text lot capture at all critical events; enforce scans and system pick-lists.
2. Synchronize time sources across MES, LIMS, WMS, and printers to preserve event order.
3. Design rework as a first-class transformation with new quality decisions and signatures.
4. Treat returns and regrades as new custody events, not data edits to historical shipments.
5. Continuously reconcile theoretical vs. actual yields to detect hidden orphan or ghost WIP.