To facilitate data integration between IBM Food Trust™ and the local systems of member organizations, compliant data is based on GS1 standards. Global Standards One (GS1) is a not-for-profit global business organization that develops and maintains standards and services for supply chain participants. GS1 standards enable businesses that use divergent processes and procedures to interact and transact with clarity and efficiency.
GS1 identifier types
GS1 provides a method for registering identifiers for company prefixes, locations, and products. Each registered identifier is a unique ID (UUID) that can be used on any supply chain, worldwide. The following GS1 Identifier Types are commonly used in IBM Food Trust™. A complete list of GS1 ID types is available on the GS1 site. Understanding the GS1 Business Data Model can also facilitate the data upload process.
|GTIN||Global Trade Item Number (products and services)||Milk, mangoes, tomatoes|
|GLN||Global Location Number (parties and locations)||Businesses, warehouses, retail stores|
|SSCC||Serial Shipping Container Code or Logistics units||Pallets, containers|
As shown in Table 1 below, IBM Food Trust uses GS1 URNs, which follow the GS1 Tag Data Standard.
Table 1. GS1 URNs
|Element||Example and syntax|
|EAN-13 / GTIN-13 formats||Attention: IBM Food Trust does not support EAN-13 / GTIN-13 formats; please add a leading zero (0) to construct a GTIN-14 URN.|
Valid Business Transaction Types = bol, desadv, inv, pedigree, po, poc, prodorder, recadv, rma
Valid bizSteps = accepting, arriving, assembling, collecting, commissioning, consigning, creating_class_instance, cycle_counting, decommissioning, departing, destroying, disassembling, dispensing, encoding, entering_exiting, holding, inspecting, installing, killing, loading, other, packing, picking, receiving, removing, repackaging, repairing, replacing, reserving, retail_selling, shipping, staging_outbound, stock_taking, stocking, storing, transforming, transporting, unloading, unpacking, void_shipping
Note: Custom bizSteps are supported, in the format of a valid HTTP URL starting with either
Valid Dispositions = active, container_closed, damaged, destroyed, dispensed, disposed, encoded, expired, in_progress, in_transit, inactive, no_pedigree_match, non_sellable_other, partially_dispensed, recalled, reserved, retail_sold, returned, sellable_accessible, sellable_not_accessible, stolen, unknown
Valid Source Destination Types = owning_party, possessing_party, location
For EPCIS Events on a vehicle or ship in transit, GS1 read point geo-coordinates are supported using RFC5870 compliant URNs. Valid geographic coordinates for <readPoint><geo> XML are comma-separated
latitude,longitude coordinates or comma-separated
latitude,longitude,altitude coordinates, as shown in the following examples:
IBM Food Trust surfaces read point data through the Trace API only, it is not available through the UI. For an example of IBM Food Trust read point upload syntax, see the annotated Commission Event XML. For GS1 read point details, refer to section 7.3.4 of the GS1 EPCIS Standard.