|
|
|
The Core Event Types data definition module
specifies the Event Types that represent EPCIS data capture events.
These events are typically generated by an EPCIS Capturing Application
and provided to EPCIS infrastructure using the Core Capture Operations
Module defined by the EPCIS specification. These events are also
returned in response to query operations that retrieve events according
to query criteria.
|
|
|
The components of the Core Event Types
Module, adhering to the EPCIS specification’s definition of
content, are as follows:
|
|
|
|
|
|
• Value Types
• Event Types
• Event Fields
• Vocabulary Types
• Master Data Attributes
• Vocabulary Elements
|
|
|
|
|
|
The Core Event Types Module defines five event types, one very generic
event and four subclasses that can represent events arising from supply
chain activity across a wide variety of industries:
|
|
|
|
|
|
• EPCISEvent is a generic base class for all event types in this module as well as others.
• ObjectEvent represents an event that happened to one or more entities denoted by EPCs.
• AggregationEvent
represents an event that happened to one or more entities denoted by
EPCs that are physically aggregated together (physically constrained to
be in the same place at the same time, as when cases are aggregated to
a pallet).
• QuantityEvent represents
an event concerned with a specific quantity of entities sharing a
common EPC class, but where the individual identities of the entities
are not specified.
• TransactionEvent
represents an event in which one or more entities denoted by EPCs
become associated or disassociated with one or more identified business
transactions.
|
|
|
|
|
|
 |
|
|
|
|
|
Each of the core event types (not counting the generic EPCISEvent) has fields that represent four key dimensions of any EPCIS event. These four dimensions are:
1. the object(s) or other entities that are the subject of the event (i.e., “what”)
2. the date and time (i.e., “when”)
3. the location at which the event occurred (i.e., “where”)
4. the business context (i.e., “why”)
These four dimensions may be conveniently remembered as “what, when, where, and why” (respectively).
The “what” dimension varies depending on the event type
(e.g., for an ObjectEvent the “what” dimension is one or
more EPCs; for a QuantityEvent the “what” dimension is an
EPCClass and a count).
The “where” and “why” dimensions have both a retrospective aspect and a prospective aspect, represented by different fields.
|
|
|
|
|
|
The following table summarizes the fields of the event types that pertain to the four key dimensions: |
|
|
|
|
|
 |
|
|
|
|
|
In addition to the fields belonging to
the four key dimensions, events may carry additional descriptive
information in other fields. In this specification, the only
descriptive field is the bizTransactionList field of ObjectEvent and
AggregationEvent, which in each case indicates that the event occurred
within the context of a particular business transaction. (The
bizTransactionList field of TransactionEvent, however, is not
“additional descriptive information,” but rather the
primary subject (the “what” dimension) of the event.) It is
expected that the majority of additional descriptive information fields
will be defined by industry-specific specifications layered on top of
this one. |
|
|
|
|
|
The Core Event Types Module of the EPCIS
specification defines the following vocabulary types (depicted here
with their respective URI, used when the vocabulary must be referred to
by name across the EPCIS interface): |
|
|
|
|
|
ReadPointID
urn:epcglobal:epcis:vtype:ReadPoint
BusinessLocationID
urn:epcglobal:epcis:vtype:BusinessLocation
BusinessStepID
urn:epcglobal:epcis:vtype:BusinessStep
DispositionID
urn:epcglobal:epcis:vtype:Disposition
BusinessTransaction
urn:epcglobal:epcis:vtype:BusinessTransaction
BusinessTrasactionTypeID
urn:epcglobal:epcis:vtype:BusinessTransactionType
EPCClass
urn:epcglobal:epcis:vtype:EPCClass
|
|
|
|
|
|
|
|
