Critical event processing and its regulatory application

Michael Fang, George Q. Huang, Y. F. Zhang, T. Qu, Q. Y. Dai

Research output: Chapter in book / Conference proceedingConference article published in proceeding or bookAcademic researchpeer-review

Abstract

This paper discusses the use of complex event processing (CEP) technologies to propose an overall infrastructure for a real- Time critical event management system (CEMS). This system allows users to obtain interested and meaningful information from large numbers of primitive events captured from the AUTO-ID devices, such as barcode, RFID and etc, in real time. A hierarchical structure for the critical event definition is proposed in this paper for better understanding of the different event types. The CEMS framework provides an event graphical representation with Petri net for the critical events, allows user to define and edit the critical events easily in an intuitionistic way. A regulatory case is also provided in this paper to demonstrate how the CEMS applies.

Original languageEnglish
Title of host publicationProceedings of the 6th CIRP-Sponsored International Conference on Digital Enterprise Technology
PublisherSpringer Verlag
Pages1735-1742
Number of pages8
ISBN (Print)9783642104299
DOIs
Publication statusPublished - Dec 2009
Externally publishedYes
Event6th CIRP International Conference on Digital Enterprise Technology, DET 2009 - Hong Kong, Hong Kong
Duration: 14 Dec 200916 Dec 2009

Publication series

NameAdvances in Intelligent and Soft Computing
Volume66 AISC
ISSN (Print)1867-5662

Conference

Conference6th CIRP International Conference on Digital Enterprise Technology, DET 2009
Country/TerritoryHong Kong
CityHong Kong
Period14/12/0916/12/09

Keywords

  • AUTO-ID
  • Complex event processing
  • Critical event
  • Petri net
  • Regulatory

ASJC Scopus subject areas

  • General Computer Science

Fingerprint

Dive into the research topics of 'Critical event processing and its regulatory application'. Together they form a unique fingerprint.

Cite this