GS1 EPCIS (Electronic Product Code Information Services) is the event-based supply chain data exchange standard answering 4 KEY QUESTIONS: WHAT (which products), WHEN (date + time), WHERE (location), WHY (business step + disposition). EPCIS HISTORY: developed by EPCglobal (founded 2003, merged into GS1 2005); EPCIS v1.0 (2007) + v1.1 (2014) + v2.0 (2022); EPCIS is also ISO/IEC 19987:2015 (ISO international standard). EPCIS EVENT TYPES: (a) OBJECT EVENT - state-change of an individual object (e.g. commissioned + manifested + shipped + received + sold + recalled); (b) AGGREGATION EVENT - associations of objects (e.g. case-pallet relationships + parent-child); (c) TRANSACTION EVENT - associates objects with business transactions (orders + invoices + ASNs); (d) TRANSFORMATION EVENT - input-output transformations (e.g. raw materials to finished goods + ingredients to recipe); (e) ASSOCIATION EVENT (v2.0) - non-physical associations (e.g. instrument-physical-link). EPCIS DATA STRUCTURE: each event captures EPC (Electronic Product Code, often GTIN + serial) + Event Time + Recorded Time + Action (ADD + OBSERVE + DELETE) + Business Step + Disposition + Read Point + Business Location + Source + Destination + Business Transaction List + Quantity List + Source List + Destination List + Sensor Element List (v2.0 - environmental sensor data) + ILMD (Instance/Lot Master Data) + Custom Fields. CBV (Core Business Vocabulary) provides standardized + controlled vocabularies for EPCIS Business Step + Disposition values to ensure semantic interoperability; CBV is also ISO/IEC 19988:2017. EPCIS QUERY INTERFACE: standardized query + subscription API enabling trading partners + regulators + consumers to access EPCIS data; supports complex filtering + on-demand + standing-query + REST/JSON in v2.0; on-premise + cloud + hybrid deployments. ADOPTION: EU FMD (DataMatrix on pharma + EPCIS for verification); FDA DSCSA (US pharma serialization + interoperable exchange by Nov 2024); supply chain visibility platforms (IBM Food Trust + Microsoft Azure + Oracle + SAP); regulatory traceability (food + tobacco + pharma); IoT + sensor integration (cold chain + condition monitoring).
This control maps to 37 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 37 it maps to, and the evidence behind each claim, over MCP and REST.