Root cause analysis with enriched process logs

S. Suriadi, C. Ouyang, W.M.P. Aalst, van der, A.H.M. Hofstede, ter

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

61 Citations (Scopus)

Abstract

n the field of process mining, the use of event logs for the purpose of root cause analysis is increasingly studied. In such an analysis, the availability of attributes/features that may explain the root cause of some phenomena is crucial. Currently, the process of obtaining these attributes from raw event logs is performed more or less on a case-by-case basis: there is still a lack of generalized systematic approach that captures this process. This paper proposes a systematic approach to enrich and transform event logs in order to obtain the required attributes for root cause analysis using classical data mining techniques, the classification techniques. This approach is formalized and its applicability has been validated using both self-generated and publicly-available logs.
Original languageEnglish
Title of host publicationBusiness Process Management Workshops : BPM 2012 International Workshops, Tallinn, Estonia, September 3, 2012. Revised Papers
EditorsM. La Rosa, P. Soffer
Place of PublicationBerlin
PublisherSpringer
Pages174-186
ISBN (Print)978-3-642-36284-2
DOIs
Publication statusPublished - 2013
Event8th International Workshop on Business Process Intelligence (BPI 2012) - Tallinn, Estonia
Duration: 3 Sept 20123 Sept 2012
Conference number: 8

Publication series

NameLecture Notes in Business Information Processing
Volume132
ISSN (Print)1865-1348

Workshop

Workshop8th International Workshop on Business Process Intelligence (BPI 2012)
Abbreviated titleBPI 2012
Country/TerritoryEstonia
CityTallinn
Period3/09/123/09/12
OtherWorkshop held in conjunction with the 10th International Conference on Business Process Management (BPM 2012)

Fingerprint

Dive into the research topics of 'Root cause analysis with enriched process logs'. Together they form a unique fingerprint.

Cite this