linking transformations in epcis governing supply chain business processes

EC-Web, 2nd September 2014, Munich

Modelling and Linking transformations inEPCIS governing supply chain

business processes

Monika Solankihttps://w3id.org/people/msolanki

@nimonika

Aston Business SchoolAston University, Birmingham, UK

Broad Outline

Motivation

Exemplifying scenario

Ontologies and Mappings

Queries and Implementation

Conclusions

m.solanki@aston.ac.uk Linking transformations in EPCIS governing supply chain business processes

MotivationData integration in supply chains for the purposes oftracking, tracing and transparency is increasinglybecoming an important challenge.Agri-food: A domain where data interlinking and sharingissues in the supply chain are most prevalent.Tracking and tracing of foods in the context of health andsafety: prevent and respond to food emergencies (madcow disease, and most recently E. Coli).Growing desire on part of the food consumers to knowmore about their food.

Electronic Product CodeRFID tags/Barcodes enable the capture of the identity andlocation of physical items and goods as they move alongthe supply chain.The Electronic Product Code (EPC)* provides productswith unique, serialised identities.Encoded on data carriers: Active/Passive RFID tags,Barcodes, Human Readable Number and more.

*http://en.wikipedia.org/wiki/Electronic_Product_Code

EPCIS v1.1 and CBV v1.1Electronic Product Code Information Services (EPCIS)*:ratified EPCglobal standard that provides a set ofspecifications for the syntactic capture and informalsemantic interpretation of EPC based product information.Events as abstractions for traceability.Core Business Vocabulary (CBV): companion* standard toEPCIS.CBV supplements EPCIS by defining the structure ofvocabularies and specific values for the vocabularyelements.

*http://www.gs1.org/gsmp/kc/epcglobal/epcis*http://www.gs1.org/gsmp/kc/epcglobal/cbv

EPCIS Events: An informal IntuitionEvent data (continuous) and Master data (static).Event data: captured through EPCIS capture interfacesand made available for query through the EPCIS queryinterfaces.Master data: context for interpreting the event data.Data persisted (Information dimensions):What(product(s)), Where(location), When(time), andWhy(business step and status) of events (productmovement) occurring in any supply chain.Event data model made available as an EPCglobal baseXML schema*.

*http://www.gs1.org/gsmp/kc/epcglobal/epcis/epcis_1_1-standard-20140520

EPCIS Events: An informal IntuitionOne generic and four specific physical event types

EPCISEvent: the generic EPCIS event.ObjectEvent: an event that occurred as a result of someaction on one or more entities denoted by EPCs.“This list of objects was observed entering DC #9 at10:01AM, during Receiving”.AggregationEvent: an event that happened to one or moreEPC-denoted entities that are physically aggregated.“This list of objects was just Palletized with this Pallet ID atPalletizer #27 at 12:32PM”.

EPCIS Events: An informal IntuitionOne generic and four specific physical event types.

TransactionEvent: an event in which one or more entitiesdenoted by EPCs become associated or disassociatedwith one or more identified business transactions.“Order #123 was fulfilled with objects x, y and z”.TransformationEvent (new in 1.1): an event in which one ormore physical or digital objects are fully or partiallyconsumed as inputs and one or more objects are producedas outputs.“50 kgs of tomato and 7 kgs of sugar were used to produce20 litres of tomato ketchup”.

QuantityEvent has been deprecated

Transformation eventsCapture information that are part of an event or a series ofevents in which one or more physical objects areconsumed as inputs to produce one or more outputs.Could provide valuable insights while investigating andidentifying causes of food outbreaks and epidemics.Event based traceability information made available aslinked data could seamlessly enable tracing back fromfinished goods to processing facilities, ingredients andeven further back to the crop growing and cattle harvestingconditions in the farm.

Exemplifying scenario: Wine production

Datasets to be integratedEvent-based data (timing, location and business context)Process related information such as data about the inputsand machinery used in the processingEnvironmental variables such as temperature and humidityInfrastructure used for the storage of intermediateproducts,Meteorological and botanical information on the grapesused in wine production.

Exemplifying scenario: Wine production

EPCIS events generated during the wine processing stages

Typical queries

1 Tracking ingredients: What were the inputs consumedduring processing in the batch of wine bottles shipped ondate X?

2 Tracking provenance: Which winery staff were present atthe winery when the wine bottles were aggregated incases with identifiers X and Y?

3 Tracking external data: Retrieve the average values forthe growth temperature for grapes used in the production ofa batch of wine to be shipped to Destination D on date X.

EPCIS Data model components

EPCsTimeRead PointsBusiness LocationBusiness stepsDispositionTransaction typesActionQuantities and measurementsSources and DestinationsILMD (Instance Lot Master Data)

EEM*: The EPCIS Event Model

Focuses on a tight conformance with the EPCIS 1.1standard and Simplicity.Explicitly defines relationships with CBV entities throughCBVVocab*.EEM has been mapped* to PROV-O*.

*http://purl.org/eem#*www.w3.org/ns/prov-o*http://purl.org/cbv#

*http://fispace.aston.ac.uk/ontologies/eem_prov.html

EEM Modules

EEM Entities: Axiomatisation

Modelling the generic EPCISEvent

An EPCIS event has three temporal properties associatedwith it.An EPCIS event occurs at a unique location and is part ofa singular business process.

Modelling the generic EPCISEvent

Class: EPCISEventSubClassOf:

eventTimeZoneOffset exactly 1 xsd:dateTime,eventRecordedAt exactly 1 xsd:dateTime,eventOccurredAt exactly 1 xsd:dateTime

ObjectProperty: hasReadPointLocationCharacteristics:

FunctionalDomain:

EPCISEventRange:

ReadPointLocation

Modelling ObjectEvent

An ObjectEvent is an EPCISEvent.An ObjectEvent is required to have associated EPCs,and an action type.

Class: ObjectEventSubClassOf:

(actionType some Action)and (associatedWithEPCList some SetofEPCs),

EPCISEvent

Modelling TransformationEvent

Class: TransformationEventSubClassOf:(((associatedWithInputEPCList some SetofEPCs)and (hasInputQuantityList some InputQuantityList))and ((associatedWithOutputEPCList some SetofEPCs)and (hasOutputQuantityList some OutputQuantityList)))or ((((associatedWithInputEPCList some SetofEPCs)and (hasInputQuantityList some InputQuantityList))or ((associatedWithOutputEPCList some SetofEPCs)and (hasOutputQuantityList some OutputQuantityList)))and (associatedWithTransformationEvent some TransformationEvent)),EPCISEvent

A TransformationEvent is an EPCISEvent.

Input and Outputs EPCs lists for transformation events arerepresented as SetOFEPCs

InputQuantityList and OutputQuantityList arecomposed of QuantityElement

A TransformationEvent may be associated with otherTransformationEvent

EPCIS defines an attribute, “TransformationID”.Replaced with transitive and symmetric property,associatedWithTransformationEvent.

EEM Entities: Mapping to PROV-O

Implementing EEM: LinkedEPCIS library

EEM is a complex data model.Non trivial to generate class assertions and complexqueries without knowing the structure of the model andnomenclature of the entities.LinkedEPCIS* - an open source Java API to,

Encourage the uptake of EEM among EPCIS conformingorganisations and industriesEase the creation of EEM instancesFacilitate querying over the instantiated datasets

* https://github.com/nimonika/LinkedEPCIS

Interlinking EPCIS Event data

Framework

Tracking ingredients(Q1)

What were the inputs consumed during processing in the batchof wine bottles?PREFIX eem: <http://purl.org/eem#>PREFIX co: <http://purl.org/co/>PREFIX prov: <http://www.w3.org/ns/prov#>PREFIX ssn: <http://purl.oclc.org/NET/ssnx/ssn#>SELECT ?input1 ?input2 WHERE{

?event1 a eem:TransformationEvent;eem:associatedWithTransformationEvent ?event2;eem:eventOccurredAt ?occurred;eem:hasInputQuantityList ?iql1;

?iql1 co:item/co:itemContent ?input1.?event2 eem:eventOccurredAt ?occurred;

eem:hasInputQuantityList ?iql2.?iq2 co:item /co:itemContent ?input2.

Tracking provenance(Q2)

Which winery staff were present at the winery when the winebottles were aggregated in cases with identifiers X and Y?

SELECT ?staff ?x WHERE{?event a prov:Entity;

eem:hasAggregationURI ?x;eem:action ?action.

?action prov:wasAssociatedWith ?staff.

Tracking provenance(Q2)

Which winery staff were present at the winery when the winebottles were aggregated in cases with identifiers X and Y?

SELECT ?staff ?x WHERE{?event a prov:Entity;

eem:hasAggregationURI ?x;eem:action ?action.

?action prov:wasAssociatedWith ?staff.

Tracking external data(Q3)

SELECT ?temperature WHERE{?event a eem:TransactionEvent;

eem:destination ?d;eem:eventOccurredAt ?x;eem:associatedWithEPCList ?epcTList.

?epcTList co:element ?epcAgg.?aevent a eem:AggregationEvent;

eem:hasAggregationURI ?epcAgg.eem:associatedWithEPCList ?epcList.

?tevent a eem:TransformationEvent.eem:associatedWithOutputEPCs ?epcOutList;eem:hasInputQuantityList ?qtyInList;?qtyInList co:item/co:itemContent ?input.

?input a GrapeVariety;gr:grownAt ?loc;

?loc a prov:Location.?sensor a ssn:SensingDevice;

prov:atLocation ?loc;ssn:madeObservation ?temp.

?temp ssn:hasValue ?tempValue.BIND (AVG(?tempValue) AS ?temperature)}

ConclusionsData visibility (tracking and tracing) in supply chains hasreceived considerable attention in recent years.EEM based linked datasets can be exploited in order toimprove visibility, accuracy and automation along thesupply chain.We have extended EEM with a new EPCIS event type,“TransformationEvent” that enables internal traceability,specifically in the production and manufacturing sectors.We have mapped EEM to PROV-O.We have exemplified our approach for traceability in thewine supply chain.

Further informationM. Solanki and C. Brewster. Consuming Linked data in Supply Chains:Enabling data visibility via Linked Pedigrees. COLD2013 at ISWC,volume Vol-1034. CEUR-WS.org proceedings, 2013.

M. Solanki and C. Brewster. Representing Supply Chain Events on theWeb of Data. DeRiVE at ISWC. CEUR-WS.org proceedings, 2013.

M. Solanki and C. Brewster. EPCIS event based traceability inpharmaceutical supply chains via automated generation of linkedpedigrees. ISWC 2014. Springer-Verlag.

M. Solanki and C. Brewster. Modelling and Linking transformations inEPCIS governing supply chain business processes. EC-Web 2014.Springer-LNBIP.

M. Solanki and C. Brewster. Detecting EPCIS Exceptions in linkedtraceability streams across supply chain business processes.SEMANTICS 2014. ACM-ICPS.

http://windermere.aston.ac.uk/~monika/ontologies.html

http://windermere.aston.ac.uk/~monika/publication.html

linking transformations in epcis governing supply chain business processes

Education

alice mukaru, trafikverket och gs1 epcis standard för...

epcis: enabling visibility from source to...

empowering supply chain visibility with epcis traceability

epcis barcode

aules...

efficacy of the epcis for traceabilitysupply chain...

introduction to epc information services (epcis)in a...

modelling and linking transformations in epcis governing...

epcis: enabling visibility from source to shelves

enhancing visibility in epcis governing agri-food supply...

epcis fosstrak installation

amerisourcebergen serialized data exchange (epcis)

epc adgroup epcis 0309

epc information services (epcis) version 1.0...

epcis lunch craigrepec - gs1...epcis for lunch an...

epcis event based traceability in pharmaceutical supply...

epc information services (epcis) version 1.0 specification -...

efficacy of the epcis for traceability - gs1nz.org...rfid...

epcis 1 0 presentation 20070619

transformations -...