Detecting EPCIS exceptions in linked traceability streams across supply chain business processes

Monika Solanki; Christopher Brewster

doi:10.1145/2660517.2660524

Detecting EPCIS exceptions in linked traceability streams across supply chain business processes

Monika Solanki, Christopher Brewster

Research output: Chapter in Book/Published conference output › Conference publication

Abstract

The EPCIS specification provides an event oriented mechanism to record product movement information across stakeholders in supply chain business processes. Besides enabling the sharing of event-based traceability datasets, track and trace implementations must also be equipped with the capabilities to validate integrity constraints and detect runtime exceptions without compromising the time-to-deliver schedule of the shipping and receiving parties. In this paper we present a methodology for detecting exceptions arising during the processing of EPCIS event datasets. We propose an extension to the EEM ontology for modelling EPCIS exceptions and show how runtime exceptions can be detected and reported. We exemplify and evaluate our approach on an abstraction of pharmaceutical supply chains.

Original language	English
Title of host publication	SEM '14 : proceedings of the 10th international conference on Semantic Systems
Place of Publication	New York, NY (US)
Publisher	ACM
Pages	24-31
Number of pages	8
ISBN (Print)	978-1-4503-2927-9
DOIs	https://doi.org/10.1145/2660517.2660524
Publication status	Published - 4 Sept 2014
Event	10th international conference on Semantic Systems - Leipzig, Germany Duration: 4 Sept 2014 → 5 Sept 2014

Conference

Conference	10th international conference on Semantic Systems
Abbreviated title	SEM '14
Country/Territory	Germany
City	Leipzig
Period	4/09/14 → 5/09/14

Keywords

epcis
exceptions
linked data
pharmaceuticals
semantic web
stream processing
traceability

Access to Document

10.1145/2660517.2660524

Cite this

@inproceedings{cc4ca4f075dc424bb75bcacec7aee30d,

title = "Detecting EPCIS exceptions in linked traceability streams across supply chain business processes",

abstract = "The EPCIS specification provides an event oriented mechanism to record product movement information across stakeholders in supply chain business processes. Besides enabling the sharing of event-based traceability datasets, track and trace implementations must also be equipped with the capabilities to validate integrity constraints and detect runtime exceptions without compromising the time-to-deliver schedule of the shipping and receiving parties. In this paper we present a methodology for detecting exceptions arising during the processing of EPCIS event datasets. We propose an extension to the EEM ontology for modelling EPCIS exceptions and show how runtime exceptions can be detected and reported. We exemplify and evaluate our approach on an abstraction of pharmaceutical supply chains.",

keywords = "epcis, exceptions, linked data, pharmaceuticals, semantic web, stream processing, traceability",

author = "Monika Solanki and Christopher Brewster",

year = "2014",

month = sep,

day = "4",

doi = "10.1145/2660517.2660524",

language = "English",

isbn = "978-1-4503-2927-9",

pages = "24--31",

booktitle = "SEM '14 : proceedings of the 10th international conference on Semantic Systems",

publisher = "ACM",

address = "United States",

note = "10th international conference on Semantic Systems, SEM '14 ; Conference date: 04-09-2014 Through 05-09-2014",

}

TY - GEN

T1 - Detecting EPCIS exceptions in linked traceability streams across supply chain business processes

AU - Solanki, Monika

AU - Brewster, Christopher

PY - 2014/9/4

Y1 - 2014/9/4

N2 - The EPCIS specification provides an event oriented mechanism to record product movement information across stakeholders in supply chain business processes. Besides enabling the sharing of event-based traceability datasets, track and trace implementations must also be equipped with the capabilities to validate integrity constraints and detect runtime exceptions without compromising the time-to-deliver schedule of the shipping and receiving parties. In this paper we present a methodology for detecting exceptions arising during the processing of EPCIS event datasets. We propose an extension to the EEM ontology for modelling EPCIS exceptions and show how runtime exceptions can be detected and reported. We exemplify and evaluate our approach on an abstraction of pharmaceutical supply chains.

AB - The EPCIS specification provides an event oriented mechanism to record product movement information across stakeholders in supply chain business processes. Besides enabling the sharing of event-based traceability datasets, track and trace implementations must also be equipped with the capabilities to validate integrity constraints and detect runtime exceptions without compromising the time-to-deliver schedule of the shipping and receiving parties. In this paper we present a methodology for detecting exceptions arising during the processing of EPCIS event datasets. We propose an extension to the EEM ontology for modelling EPCIS exceptions and show how runtime exceptions can be detected and reported. We exemplify and evaluate our approach on an abstraction of pharmaceutical supply chains.

KW - epcis

KW - exceptions

KW - linked data

KW - pharmaceuticals

KW - semantic web

KW - stream processing

KW - traceability

UR - http://www.scopus.com/inward/record.url?scp=84937697207&partnerID=8YFLogxK

UR - http://dl.acm.org/citation.cfm?doid=2660517.2660524

U2 - 10.1145/2660517.2660524

DO - 10.1145/2660517.2660524

M3 - Conference publication

AN - SCOPUS:84937697207

SN - 978-1-4503-2927-9

SP - 24

EP - 31

BT - SEM '14 : proceedings of the 10th international conference on Semantic Systems

PB - ACM

CY - New York, NY (US)

T2 - 10th international conference on Semantic Systems

Y2 - 4 September 2014 through 5 September 2014

ER -

Detecting EPCIS exceptions in linked traceability streams across supply chain business processes

Abstract

Conference

Keywords

Access to Document

Other files and links

Fingerprint

Cite this