Oracle Pedigree and Serialization Manager Process Guide Release 1.2 Part Number E36379-01

Contents

Previous

Next

Understanding the EPCIS Repository

This chapter covers the following topics:

• EPCIS Repository Overview

EPCIS Repository Overview

In this section, we will provide an overview of EPCIS (Electronic Product Code Information Services) and the EPCIS repository.

EPCIS Overview

Electronic Product Code Information Services (EPCIS) is the EPCglobal® standard for capturing and communicating the business events for tracking and tracing products within an enterprise and across the supply chain. EPCIS is a standard that defines interfaces for representation and exchange of data.

The EPCIS standard provides interface specifications built on top of widely used business and Internet standards. EPCIS facilitates internal data capture as well as secure external sharing of information about movement and status of goods in the physical world.

The EPCIS data model specifies a standard way to represent visibility information about physical objects, including descriptions of product movements in a supply chain. The main components of the data model include EPC, Event Time, Business Step, Disposition, Read Point, Business Location, and Business Transaction. The data model is designed to be extended by industries and end users without revising the specification itself.

Visibility information in EPCIS takes the form of "events" that describe specific occurrences in the supply chain. An example event would be that EPC 123 (product) was Received (business step) in Non Sellable condition (disposition) at Distribution Center X (location) yesterday at 2pm EDT (time). A quick way to summarize the components of an EPCIS event are what (product), when (time), where (location), and why (business step and disposition).

EPCIS Repository Overview

EPCIS Repository High-Level Overview

The EPCIS repository resides in the same database as the Oracle Pedigree and Serialization Manager (OPSM) application. The repository can store all of the EPCIS-level events for the products generated by one or more EPCIS external event capturing systems. These events include:

• Accepting

• Arriving

• Assembling

• Collecting

• Commissioning

• Decommissioning

• Departing

• Destroying

• Disassembling

• Encoding

• Entering_exiting

• Holding

• Inspecting

• Installing

• Killing

• Loading

• Other

• Packing

• Picking

• Receiving

• Removing

• Repackaging

• Repairing

• Replacing

• Reserving

• Retail_selling

• Shipping

• Staging_outbound

• Stocking

• Storing

• Transforming

Using the EPCIS Capture web service, events from external systems or trading partners can be populated into the EPCIS repository. This can be achieved using HTTP Post and JMS Capture. For HTTP Post or JMS Capture, any errors will be visible to you in the Web Service Exceptions page using a the Web Service Name of captureEpcisDoc or HTTPPost. The EPCIS Capture web service uses the EPCIS setup information (preferences) that you define in OPSM to determine the data that can be captured.

Using the EPCIS Query web service, you can query on EPCIS data (business events) initiated internally, from external trading partners, or regulatory agencies. The result of this query is provided to the accessing application in XML format with a list of EPCIS Event instances. The EPCIS Query web service uses the EPCIS setup information (preferences, policies, and users) that you define in OPSM to determine the EPCIS events that can be accessed.

For more information, see:

• Understanding the EPCIS Repository Setup Process.

• Web Services Overview.

Copyright © 2013, Oracle and/or its affiliates. All rights reserved.