In computer science, Electronic Product Code Information Services (EPCIS) is a global GS1 Standard for creating and sharing visibility event data, both within and across enterprises, to enable users to gain a shared view of physical or digital objects within a relevant business context. "Objects" in the context of EPCIS typically refers to physical objects that are handled in physical steps of an overall business process involving one or more organizations. Examples of such physical objects include trade items (products), logistic units, returnable assets, fixed assets, physical documents, etc. "Objects" may also refer to digital objects which participate in comparable business process steps. Examples of such digital objects include digital trade items (music downloads, electronic books, etc.), digital documents (electronic coupons, etc.), and so forth.
The EPCIS standard was originally conceived as part of a broader effort to enhance collaboration between trading partners by sharing of detailed information about physical or digital objects. The name EPCIS reflects the origins of this effort in the development of the Electronic Product Code (EPC). However, EPCIS does not require the use of Electronic Product Codes, nor of Radio-Frequency Identification (RFID) data carriers, and as of EPCIS 1.1 does not even require instance-level identification (for which the Electronic Product Code was originally designed). The EPCIS standard applies to all situations in which visibility event data is to be captured and shared, and the presence of "EPC" within the name is of historical significance only.
EPCIS 1.0 was first ratified by EPCglobal in April, 2007. At the time of ratification, over 30 companies had used the draft EPCIS standard to exchange data and collaborate with trading partners As of 2014, 24 commercial products had received certificates of compliance to the EPCIS standard from GS1. EPCIS 1.1 was ratified by GS1 in May, 2014. EPCIS 1.2 was ratified by GS1 (in conjunction with CBV 1.2) in September, 2016.
In 2001, the MIT Auto-ID Center published a paper proposing the Physical Markup Language (PML), intended as "a common 'language' for describing physical objects, processes and environments". PML was one of four components of an "intelligent infrastructure" envisioned by the Auto-ID Center, the other three components being RFID tags, the Electronic Product Code, and the Object Naming Service. As the work of the MIT Auto-ID Center was taken up by EPCglobal in 2004, the PML concept was renamed Electronic Product Code Information Services (EPCIS), and efforts began to create a global standard. In 2005, the first version of the EPCglobal Architecture Framework was published, which introduced EPCIS as a standard under development and showed how it related to other components of an envisioned architecture for RFID-based tracking of physical objects within supply chains.
EPCIS 1.0 was first ratified by EPCglobal in April, 2007. A companion standard, the EPC Core Business Vocabulary 1.0, was ratified by EPCglobal in October, 2010. Despite the RFID-oriented origins of EPCIS, it came to be used in applications that used bar codes exclusively or bar codes in combination with RFID tags.
EPCIS 1.1 and CBV 1.1 were ratified by GS1 in May, 2014. New features in EPCIS 1.1 include support for class-level identification (needed especially in bar code applications), a new event type to describe processes where inputs are transformed into outputs, and additional event data to describe business transfers and instance- or lot-level master data.
EPCIS 1.2 and CBV 1.2 were ratified by GS1 in September, 2016. New features include a mechanism to declare a previous event as being erroneous, and a mechanism for including master data into the EPCIS document header.
A key principle of EPCIS is that unlike raw data captured from data carriers such as bar codes and RFID tags, EPCIS events include additional information that imbues the raw observations with meaning relative to the physical or digital world and to specific steps in operational or analytical business processes. An EPCIS event, while containing much of the same data as an RFID tag read or a bar code scan, is at a semantically higher level because it incorporates an understanding of the business context in which the identifier data were obtained. Moreover, there is no requirement that an EPCIS event be directly related to a specific physical data carrier observation. For example, an EPCIS event may indicate that a perishable trade item has just crossed its expiration date; such an event may be generated purely by software.
The EPCIS standard includes these parts:
EPCIS is intended to be used in conjunction with the GS1 Core Business Vocabulary (CBV) standard. The CBV standard provides definitions of data values that may be used to populate the data structures defined in the EPCIS standard.
The basic unit of data in EPCIS is a structure that describes the completion of one business step within an overall business process; this structure is called an EPCIS event. A collection of EPCIS events provides a detailed picture of a business process over time and place. The information content of a single EPCIS event is organized into four dimensions:
Each of the business steps in the process illustrated in the figure could be the source of an EPCIS event. The details of the content of each of those events are different depending on the business step, but all have the same four-dimensional structure.
All EPCIS events have the four-dimensional information content of what, where, when, and why. The EPCIS standard defines five different event types to allow for variations in the structure of the what dimension and associated variations in the semantics of the event.
|Event Type||Content of what Dimension||Meaning||Example|
|Object Event||Identifiers of one or more objects||The specified objects participated in an event||Serial #s 111, 112, and 113 of Product X were observed at 10:23am on March 15, 2014, at Location ABC, during a "shipping" operation|
|Aggregation Event||Identifier of a parent object, and identifiers of one or more child objects||The specified child objects were physically aggregated to (or disaggregated from) the specified parent object||Serial #s 111, 112, and 113 of Product X were placed into Bin #1234 at 10:23am on March 15, 2014, at Location ABC, during a "packing" operation|
|Transformation Event||Identifiers of one or more input objects, and of one or more output objects||The specified input objects were consumed and the specified output objects were produced||10 units of Raw Material X and 10 units of Raw Material Y were mixed together to create 100 units of Product Z, at 10:23am on March 15, 2014, at Location ABC, during a "mixing" operation|
|Transaction Event||Identifier of a parent object (optional), identifiers of one or more child objects, and identifiers of one or more business transactions||The specified objects were definitively associated (or disassociated) with the specified business transactions||Serial #s 111, 112, and 113 of Product X were designated to fulfill Purchase Order 9876 at 10:23am on March 15, 2014|
|Quantity Event(deprecated)||A class-level identifier and a quantity||The specified quantity of the specified class participated in an event
The Quantity Event is deprecated in EPCIS 1.1, as it is subsumed by new features added to the Object Event in EPCIS 1.1
|100 units of Product X were observed at 10:23am on March 15, 2014, at Location ABC, during a "shipping" operation|
The EPCIS Capture Interface provides a means for EPCIS data to be delivered from a capturing application to an EPCIS repository or other system capable of receiving EPCIS data. Often the capturing application is interacting with the physical world through scanning bar codes or reading RFID tags. The EPCIS Capture Interface specifies the delivery of an "EPCIS Document" containing one or more EPCIS events, using an XML format for EPCIS events defined by an XML schema provided in the standard. The EPCIS Standard provides bindings of the EPCIS Capture Interface that use either a message queue or HTTP.
The EPCIS Query Interface provides a means by which EPCIS Accessing Applications and trading partners may obtain EPCIS data subsequent to capture, typically by interacting with an EPCIS Repository. The Query Interface is defined as a web service supporting the following operations:
|Query Interface Operation||Description|
|poll||Queries for EPCIS events matching specified criteria, immediately returning the results.|
|subscribe||Register a standing query for EPCIS events matching specified criteria. New events matching the query criteria are sent asynchronously to the subscriber on a specified schedule.|
|unsubscribe||Remove a previously registered subscription.|
|getSubscriptionIDs||Return a list of active subscriptions.|
|getQueryNames||Return a list of the types of queries supported by the service.|
|getStandardVersion||Return the version number of the EPCIS standard supported by the service (e.g., "1.2").|
|getVendorVersion||Return a vendor-defined string identifying any non-standard extensions supported by the service.|
Commercial software products may be certified by GS1 as compliant to the EPCIS standard. Products may be certified as conforming to the EPCIS Capture Interface, the EPCIS Query Interface, or both. As of 2014, 24 commercial products had received certification. Among these is one open-source implementation, FossTrak.
Manage research, learning and skills at defaultlogic.com. Create an account using LinkedIn to manage and organize your omni-channel knowledge. defaultlogic.com is like a shopping cart for information -- helping you to save, discuss and share.