YAWL-logs cannot interpreted correctly by ProM

pwagner

Hello together,

in our course "IT Management" we want to implement some ITIL processes (e.g. Incident Management) in YAWL and later analyze the event logs with ProM. There is no problem to get out the logs (in .XES format) from YAWL and to import them in ProM. Therefor I easily use the "Download Log"-Button at the admin surface of YAWL and then the "Import"-Button in ProM.
The problem is the log itselfs. YAWL splits every task in many unknown events and even more it subdivides the numbering of one instance. So it could be that events of the same instance got different numbers (e.g. 19 and 19.1 - see the extraction below).
Thus ProM cannot interpret the log as one connected process. Can someone of you tell me why YAWL generates such a log or how I can solve this problem?

Thanks a lot

---

<?xml version="1.0" encoding="UTF-8"?>
<log xes.version="1.0" xes.features="arbitrary-depth" openxes.version="1.5" xmlns="http://code.deckfour.org/xes">
  <!-- Generated by the YAWL Engine 2013.10.30 16:12:19 -->
  <!-- and then merged with the Resource Service log -->
  <extension name="Lifecycle" prefix="lifecycle" uri="http://code.fluxicon.com/xes/lifecycle.xesext"/>
  <extension name="Time" prefix="time" uri="http://code.fluxicon.com/xes/time.xesext"/>
  <extension name="Concept" prefix="concept" uri="http://code.fluxicon.com/xes/concept.xesext"/>
  <extension name="Semantic" prefix="semantic" uri="http://code.fluxicon.com/xes/semantic.xesext"/>
  <extension name="Organizational" prefix="org" uri="http://code.fluxicon.com/xes/org.xesext"/>
  <global scope="trace">
    <string key="concept:name" value="UNKNOWN"/>
  </global>
  <global scope="event">
    <date key="time:timestamp" value="1970-01-01T00:00:00.000+01:00"/>
    <string key="concept:name" value="UNKNOWN"/>
    <string key="lifecycle:transition" value="UNKNOWN"/>
    <string key="concept:instance" value="UNKNOWN"/>
  </global>
  <classifier name="Activity classifier" keys="concept:name concept:instance lifecycle:transition"/>
  <string key="concept:name" value="IncidentManagement - version 0.20"/>
  <trace>
    <string key="concept:name" value="19"/>
    <event>
      <date key="time:timestamp" value="2013-10-18T09:33:40.509+0200"/>
      <string key="concept:name" value="Incident_erfassen"/>
      <string key="lifecycle:transition" value="schedule"/>
      <string key="lifecycle:instance" value="19"/>
    </event>
    <event>
      <date key="time:timestamp" value="2013-10-18T09:33:40.549+0200"/>
      <string key="concept:name" value="Incident_erfassen"/>
      <string key="lifecycle:transition" value="unknown"/>
      <string key="lifecycle:instance" value="19"/>
    </event>
    <event>
      <date key="time:timestamp" value="2013-10-18T09:33:40.554+0200"/>
      <string key="concept:name" value="Incident_erfassen"/>
      <string key="lifecycle:transition" value="unknown"/>
      <string key="lifecycle:instance" value="19.1"/>
    </event>
    <event>

JBuijs

Dear Pwagner,

Each event in the XES format has, besides a name, also a lifecycle transition, indicating whether the activity has started, completed etc.
YAWL adds different lifecycle transitions, some of which are 'unknown' unfortunately.
In ProM you can filter out all events that have 'unknown' set, or only keep the ones with start/complete.

For more information about the lifecycle transitions, refer to the XES and OpenXES documentation.

pwagner

Well ok. And whats about the numbering problem?

JBuijs

I'm not experienced with the YAWL to ProM integration, so I can not answer that question unfortunately.

ahense

Indeed, the XES files from YAWL require some filtering before they can be used. I have posted a small script that removes double "complete" events:

http://yaug.org/content/stylesheet-removing-double-complete-events-yawl-xes-logs

JBuijs

Thank you for sharing the script 'ahense'!