Data Structure

A consistent, standardized event structure is essential for establishing digital traceability across supply chains because it ensures that every actor records and shares information in the same predictable way. The EPCIS 2.0 Standard provides this structure by capturing traceability records through five core event types: Object, Aggregation, Association, Transformation and Transaction.

The GFTBL uses only three of the five event types:

• Object Event
  • Captures what happens to one or more items (identified objects) at a given time and place (e.g. commissioning, receiving, shipping, or moving cases in a warehouse).
• Aggregation Event
  • Records when items are grouped together or separated (e.g., packing products into a carton or breaking down a pallet).
• Transformation Event
  • Captures when inputs are changed into outputs (e.g., processing raw ingredients into finished goods).

Each event type follows a consistent structure built around the what, when, where, and why of the event that illustrates what occurred. This approach ensures event data is machine-readable, interoperable, and meaningful across systems and organizations. Appendix [INSERT NUMBER] illustrates the expected data attributes to be recorded with each event.

EPCIS 2.0 has published schemas for each event type. These schemas define the expected properties, data types, and relationships for various EPCIS event types (e.g., ObjectEvent, AggregationEvent, TransformationEvent), as well as common fields like eventTime, recordTime, epcList, bizStep, disposition, and readPoint.

JSON schemas are available at GS1s public code repository:EPCIS/JSON-Schema at master · gs1/EPCIS. Data will be validated using these schemas.