GSII serialization & lifecycle
Track every serialized item across custody, status, and lineage with GSII state machines and lifecycle event logs.
Feature profile
Primary API
GSII / Serialization
Engine
Provenance Ledger
Artifacts
GlobalSerializedItemInstance + SerialLifecycleEventLog
Problem
Serialized assets lose provenance once they leave the dock.
Teams can create serial numbers, but tracking state changes, custody transfers, and compliance proofs across systems is slow and error-prone.
Operational impact
- Manual reconciliation between ERP, WMS, and service systems
- Missing chain-of-custody evidence during audits
- Slow recalls when lineage cannot be traced
Engine
Provenance Ledger (SerialLifecycleEventLog)
A universal chain-of-custody ledger that captures every GSII event, status change, and transformation.
- Event taxonomy for serialized lifecycle changes
- Lineage tracking between source and destination GSIIs
- Custody and location transitions with audit context
Engine promise
This engine anchors the feature with reusable operational logic, ensuring every workflow stays aligned with tenant-owned data models.
Workflow
How the workflow moves from signal to action.
Step 1
Serialize a new GSII
Create a GSII from a SKU and capture initial status, lot, and location context.
Step 2
Move and update custody
Record location changes, LPN moves, and status transitions with lifecycle events.
Step 3
Consume or transform
Track consumption, relabeling, or repackaging with lineage links and event logs.
Step 4
Query provenance
Retrieve GSII detail and lifecycle history for audits, recalls, and service logs.
Data artifacts
Tenant-owned artifacts that power downstream systems.
Every workflow produces structured records that stay in the customer domain.
GlobalSerializedItemInstance
The GSII record capturing serial, SKU, quantity, status, and current location.
SerialLifecycleEventLog
Immutable event log of every status change, move, and transformation.
Lineage origin
Reference fields connect transformed or repackaged items to their source GSII.
API preview
The endpoints teams integrate first.
The API surface remains consistent across industries, with schema-stable event hooks.
/api/gsiis Create a new GSII with SKU, serial, and initial location.
/api/gsiis/{sqid}/move Move a GSII to a new LPN or location and record lifecycle events.
/api/gsiis/{sqid} Fetch GSII details and lifecycle history for provenance queries.
Cross-industry examples
One engine, many instantiations.
The same operational logic adapts across manufacturing, healthcare, logistics, and regulated industries.
Pharma
DSCSA track-and-trace with lot, expiry, and custody evidence per vial.
Aerospace
As-maintained histories for serialized parts and overhaul documentation.
Food traceability
Farm-to-fork lineage with shipment, inspection, and recall-ready logs.
Embedded operations
Serialized product tracking from prototype through EVT/DVT/PVT and into mass production with full custody lineage.
FAQ
Answers for security, data, and rollout teams.
How are lifecycle events stored?
Each GSII change writes a SerialLifecycleEventLog entry with event type, timestamp, and optional context details.
Can GSII lineage show transformations or repackaging?
Yes. Lifecycle events capture source/destination relationships so transformed or relabeled GSIIs retain lineage back to the origin.
Where do valid GSII statuses come from?
Status options are exposed through the GSII status endpoint and enforced in lifecycle transitions.
Explore more