Container Status Tracking

Container Status Tracking is the governed, electronic representation of a single container’s disposition and permissions at any moment in time. It unambiguously indicates whether a physical unit (drum, bin, tote, bag, vial, pallet, carrier, kit) is Quarantined, Released, Sampled, On Hold, Rejected, In-Use, Empty, Decommissioned, or under conditional states (e.g., Pending Results, Cleaning Required). The status is authoritative for use, movement, and shipment, and is time-stamped, user-attributed, and reason-coded under audit-trail control.

In an MES-centric architecture, status transitions are driven by qualified events: QA release decisions, sampling completion, laboratory results, expiry/retest checks, environmental alarms, deviations/CAPA links, and execution milestones (e.g., weigh/dispense start/complete). Operationally, this prevents inadvertent use of unapproved material, enforces segregation, and maintains material and lot genealogy continuity.

In pharmaceuticals, 21 CFR 211.82 requires quarantine and release of components, containers, and closures by the quality unit before use—necessitating container-level status control when inventory is split across multiple physical units. For medical devices, 21 CFR 820.86 requires acceptance status be identified throughout the product lifecycle to indicate conformance/nonconformance, which extends to single containers holding components or subassemblies. EU GMP Volume 4 (including expectations in Chapter 5 and Annex 11) requires unambiguous status identification, segregation, and validated computerized systems governing that status. These regulations align with ALCOA+ data integrity principles emphasized by MHRA, making time-stamped, attributable status and secure audit trails non-negotiable.

Practically, inspectors challenge ambiguous labelling (e.g., mixed lots or mixed status), undocumented overrides, or use of material with pending or failed results. Electronic Container Status Tracking mitigates such risks by embedding quality decisions into executable interlocks, preventing picking, weighing, or charging when status, expiry, or environmental conditions are not met, and ensuring complete, contemporaneous records consistent with Part 11.

ISA‑95 partitions responsibilities across enterprise planning (Level 4) and manufacturing operations (Level 3) while defining standard information objects (e.g., Material Definition, Material Lot/Sublot, Material Segment, Genealogy). Container Status Tracking lives primarily at Level 3 within the Production, Quality, and Inventory operations functions and interfaces to Level 4 (ERP, planning) and Level 2/1 (automation signals) via agreed interfaces. The container is typically modeled as a material sublot or handling unit bound to a specific location and equipment context, with events propagated to genealogy records.

A robust state model defines initial, intermediate, and terminal statuses with explicit entry criteria, required approvals, and allowed next states. Transitions must be event-driven and role-protected (e.g., QA approves Release; Production initiates Sampling; QC records OOS invoking automatic Hold). The state model also embeds conditional attributes (expiry/retest dates, storage conditions, temperature excursions, cleaning validity, sterility) that dynamically constrain actions.

Accurate status depends on authoritative identification. Each container must carry a unique ID (e.g., SSCC, internal handling unit) encoded via GS1‑128, GS1 DataMatrix, or RFID, linked to lot/sublot, quantity, UoM, expiry/retest, storage conditions, and hazard/allergen attributes. The master data model must define container types, reusability, cleaning validation requirements, and permissible contents. Scanning at every critical control point (receipt, sampling, release, move, pick, weigh, charge, pack/ship, destruction) anchors status transitions to the correct unit and user/action.

Status must actively control behavior. In MES and WMS, enforce pick/put/charge interlocks: a container in Quarantine or Hold cannot be picked for production; a Released container beyond expiry/retest cannot be charged; a refrigerated-only container cannot be staged outside temperature-controlled areas. LIMS-triggered OOS should auto‑apply Hold to all impacted containers and child WIP, with immediate propagation to movement blocks. Device-level interlocks (e.g., weigh scales, line controllers) must verify container status before dosing, with clear operator messaging and e-signature capture for authorized overrides.

Container status is a cross-system contract. ERP provides purchasing/lot creation and receives availability summaries; WMS governs physical moves and locations; MES enforces process eligibility; LIMS provides results that gate QA release; QMS manages deviations/CAPAs that can assert Hold. All status changes must be time-synchronized, user-attributed, and reason-coded with secure, computer-generated audit trails meeting 21 CFR Part 11 and Annex 11 expectations. Role-based access limits who can set or override status, and e-signatures must be applied for dispositions and high-risk overrides. System clocks should be synchronized to prevent temporal ambiguity in audit trails, and records should be readily retrievable for batch/eDHR review.

Data integrity expectations (ALCOA+) require that status events are legible, attributable (operator, system), contemporaneous (real-time capture at point-of-activity), original (system of record), and accurate (validated entry and logical checks). Interfaces should be transactional (e.g., message acknowledgements) to avoid status drift between MES and WMS. If offline printing or fallback is permitted, procedures must reconcile and re-enter events with appropriate flags and secondary review.

• Pharmaceuticals/biotech: Component quarantine and QA release per 21 CFR 211.82; integrate sampling/chain-of-custody; embed expiry/retest and temperature excursion logic; enforce sterile container requalification before aseptic areas.
• Medical devices: Acceptance status per 21 CFR 820.86; container status supports acceptance records, nonconformance, and segregation of suspect material.
• Food processing and cosmetics: Allergen and hazard segregation tied to status; disposition prevents cross-contact; time/temperature shelf-life gates readiness for use.
• Cannabis: Jurisdictional seed-to-sale trace requirements require container-level status alignment with statutory reporting; ensure unique identifiers and movement blocks reflect legal holds and destruction.

Reusable containers (IBCs, bins) require a parallel equipment lifecycle: post-Empty, cleaning verification and, where applicable, sterilization/bioburden checks must be satisfied before a container is re‑Released for refilling. For potent or sensitizing materials, status changes can trigger PPE and handling controls at pick/charge. For serialized packaging components, container status must remain aligned with serial/VIN pools and aggregation states to avoid reconciliation gaps.

Validate Container Status Tracking as a GxP computerized function per GAMP 5 (2nd ed): define the intended use (risk to product quality and patient safety), configure the state model and interlocks, and verify end-to-end workflows. Key tests include negative paths (prevent picking/charging on Quarantine/Hold/expired), role/privilege enforcement, e-signature prompts, audit-trail completeness/immutability, interface handshakes (MES↔WMS↔LIMS), and error recovery (network loss, printer failure). Performance qualification (PQ) should simulate realistic loads (multiple concurrent picks, partial container reconciliations, returns) and demonstrate timely propagation of OOS/hold events.

• Right‑first‑time pick/charge rate gated by status.
• Mean time to QA release from sampling to status change.
• Hold propagation latency (LIMS OOS to blocked use).
• Container status discrepancy rate (MES vs WMS).
• Genealogy completeness (containers with full status history).

Frequent deficiencies include containers without clear status labels; shared pallets containing mixed dispositions; manual spreadsheet status tracking disconnected from controlled systems; ad hoc overrides without reason codes or secondary review; delayed application of holds after OOS results; and discrepancies between MES and WMS due to asynchronous updates. Labels that omit expiry/retest or storage condition data also lead to mis-use during staging. Physical and electronic status must always agree; when conflicts occur, the more restrictive status should automatically prevail until reconciliation.

Another trap is incomplete modeling of partial consumption. Part-used containers demand rigorous reconciliation (tare/net), automatic rollback to Released or In‑Use as appropriate, and revalidation of environmental/cleanliness constraints before the next use. Where reusable containers are involved, failure to model the cleaning/sterilization “release” step (with its own status) often leads to audit comments.

Every status transition is a record event anchored to the container ID, including who, when, what, why (reason code), source system, and any linked artifacts (CoA, sampling record, deviation/CAPA, temperature map). These events roll up into batch records (eBMR) or device histories (eDHR), providing verifiable evidence that only properly Released containers were used and that holds or rejections were respected. Genealogy should reflect not just lot relationships but also the state at the time of consumption, enabling accurate lookback and potential recall scoping.

With robust status rules, Review by Exception becomes defensible: the system proves that no execution step could proceed unless the container had a permissible status and attributes within limits. This reduces manual record review load while maintaining compliance expectations for completeness, accuracy, and traceability.

In V5 Ultimate, container is a first-class master data entity linked to lot/sublot, locations, equipment, and execution steps. Status is maintained centrally and exposed consistently to MES, WMS, LIMS, QMS, and eBMR/eDHR. Interlocks prevent picks, weighs, charges, and shipments unless status, expiry/retest, storage, and cleanliness criteria are met. LIMS results and QA decisions automatically update status, with two-person e-signature support for risk-based overrides. All changes are captured in a Part 11-compliant audit trail and flow into batch/device history records with complete genealogy.