EPCIS 2.0 Explained: Better Supply Chains Through APIs

EPCIS (Electronic Product Code Information Services) is a GS1 standard for capturing and querying supply chain events. EPCIS is especially valuable to facilitate the seamless exchange of information in supply chains that span multiple organizations. The EPCIS 2.0 standard was ratified in July 2002 by the GS1 working group.
EPCIS systems communicate by sending events. EPCIS supports five event types, namely ObjectEvent, AggregationEvent, AssociationEvent, TransformationEvent and TransactionEvent. But you can also specify your own type, if necessary. EPCIS events are snapshots of supply chain transactions, describing the following:
- What: One or more items (pallet, individual products, etc...) that are concerned
- When: At what time did this event occur
- Where: The place where items are being shipped, received and where items are being expected
- Why: The business context that describes the process-related information
- How: This dimension was added in 2.0 and is used to capture IoT data (sensor information) from and about events.
An EPCIS repository is an append-only database, because events are snapshots of the state of a supply chain. This is important to ensure transparency, accountability and traceability. If for example a supplier ships 10 pallets to a manufacturer and that shipment only contains 5 pallets on arrival, the manufacturer will not ask the supplier to change the event. Instead, the manufacturer will create a new EPCIS event that captures the discrepancy.
Unlike previous versions which were XML based, by default EPCIS 2.0 encodes EPCIS events as JSON (in fact, JSON-LD) objects.
- OpenAPI spec with Swagger UI: api.epcis.tools
- EPCIS landing page (documents, examples, ets.): www.gs1.org/st...
- epcis2.js - Digimarcʼs open source client SDK (collaboration with Zebra): js.epcis.tools
- A set of EPCIS 1.2 to 2.0 tools: tools.openepci...

[@TeamJackassTV]

What a great video! #IOTA

[@ErikWilde]

thanks, and all the credits go to dom, of course!

[@kdeasc5124]

The links don't seem to work?

[@ErikWilde]

Which one specifically?