<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>István Koren∗, Jan NiklasAdams, Alessandro Berti and Wil M.P. van der Aalst</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <string-name>Process Mining, Object-Centric Event Logs, OCEL 2.0, Simulation Models, Developer Support</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Chair of Process and Data Science, RWTH Aachen University</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>0000</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>Process mining has become a cornerstone of process analysis and improvement over the last few years. With the widespread adoption of process mining tools and libraries, the limitations of traditional process mining to deal with event data with multiple case identifiers, i.e., object-centric event data, have become apparent. As a response, the subfield of object-centric process mining has formed, including a file format standardization attempt in the form of OCEL 1.0, unifying the insights of previous developments in capturing object-centric event data. However, discussions among researchers and practitioners have shown that the proposed OCEL 1.0 standard does not go far enough. OCEL 2.0 has been proposed as an advanced refinement, including normative and explicit object-to-object relationships, qualifiers for objectto-object and event-to-object relationships, and evolving object attribute values. This demonstration presents the OCEL 2.0 website available under the URLhttps://www.ocel-standard.orgas a one-stop shop for the detailed specification, example event logs, and broad tool support to facilitate the adoption of the format.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>CEUR
ceur-ws.org</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>
        Process mining has permeated many organizations over the last few years. A wide range of
dedicated tools and functionalities within of-the-shelf software systems can perform process
analysis. Although process mining can yield powerful insights, there are currently some limiting
factors. Often, only case-based analysis is ofered. Therefore, for each new perspective on a
process or related processes, new extractions and transformations from the information systems
have to be performed. Traditional event logs stored in the XES standard format can only store
and provide case-based event data. Object-centric process mining addresses this limitation1,[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ],
broadening the horizon of many enterprises to look at intertwined processes within and across
their business units and organizations. The OCEL (1.0) format3[] has been initially introduced
as a standardization attempt to store and exchange object-centric event data. However, industry
and academia have found that this format is not expressive enough and should be moved
closer to reality, e.g., recording object changes and giving detailed information about object
nEvelop-O
LGOBE
CEUR
Workshop
Proceedings
https://istvank.eu (I. Koren); https://niklasadams.com/(J. N. Adams); https://www.alessandroberti.it/(A. Berti);
© 2023 Copyright for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).
relationships [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. These limitations are the motivation for the OCEL 2.0 standard, which refines
the original format introducingobject-to-object relationships, evolving object attribute values,
and qualifiers for object-to-object and event-to-object relationships altogether with an increased
interpretability of its specifications while maintaining backward compatibility to OCEL 1.0 and
graph-based object-centric storage formats. In this paper, we specifically introduce the OCEL 2.0
website, a one-stop shop for the OCEL 2.0 standard and its resources, featuring the specification
of the standard, multiple simulation models, event logs, and tool support to immediately benefit
from the new constructs. This comprehensive set of training materials is collected on the
website https://www.ocel-standard.org.
      </p>
    </sec>
    <sec id="sec-3">
      <title>2. Website</title>
      <p>The website serves as an exhaustive resource for both researchers and practitioners. It provides
access to the latest specification along with a scientific formalization of the standard, and a
number of event logs. Additionally, it ofers an array of libraries and examples to get started.</p>
      <sec id="sec-3-1">
        <title>2.1. Specification</title>
        <p>Figure 1 shows a screenshot of the website and the OCEL 2.0 metamodel. The greatest strength of
the format is that various relationships and their qualifiers are now directly incorporated. Events
now have a qualified relationship to objects, which means that the nature of the relationship
is explicitly annotated. Similarly, object-to-object relationships can be explicitly stored and
supplemented with a qualifier. Both reinforce the benefit of flexibility by storing various
intertwined processes without having to refer back to source data. In addition, changes to object
attribute values can now be tracked. We provide three file storage formats. TheXML variant is
human-readable and structured according to industry XML best practices. ThJeSON variant
features a lightweight structure that can be natively used in web environments. TheSQLite
variant allows for eficient SQL querying, eliminating the necessity to parse the entire event log.</p>
      </sec>
      <sec id="sec-3-2">
        <title>2.2. Event Logs</title>
        <p>The website initially provides four new event logs that target and demonstrate new features of
OCEL 2.0, available on the research data platform Zenodo.</p>
        <p>
          The Logistics [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] log describes the processes of a company selling goods overseas. After
receiving an order, the shipment of the goods is scheduled. According to the schedule, the
goods are picked up from the local production site and brought to a terminal, where a service
provider receives and ships them.
        </p>
        <p>
          The Order Management [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] simulation and event log deals with an imaginary e-commerce
enterprise. It comprises both the registration and payment of incoming orders, as well as the
process of packing and shipping them. For these tasks, the company deploys staf in their sales,
warehousing, and shipment departments.
        </p>
        <p>The Procure-to-Pay [7] log is a simulated event log that has been replicated with domain
knowledge of a real SAP system. It handles scenarios such as lengthy approvals and duplicate
payments. Resource availability is realistically mapped based on business hours, and the capacity
of human resources.</p>
        <p>The Angular GitHub Commits [8] is a real-world event log containing information on the
commits in the GitHub repository of the Angular project. Additionally, we converted some
event logs that have already been made available for OCEL 1.0.</p>
      </sec>
      <sec id="sec-3-3">
        <title>2.3. Tool Support</title>
        <p>Several tools and libraries have been developed to accommodate the OCEL 2.0 format:
• OC [9]: A standalone tool for object-centric process discovery, variant analysis, and
ifltering. OC  supports object-centric variants and filters based on frequency of behavior
across object types.
• Object-Centric Process Mining (OCPM) [10]: A JavaScript web application that provides
capabilities such as process discovery and visualization of object-centric models.
• Ocelot.pm: A web-based event log inspector for OCEL 2.0 files. It visualizes event and
object types as models and shows events and objects in searchable data tables.
• Oracle EBS Connector: A transformer connecting to Oracle databases, targeting tables
related to the Purchase-to-Pay process, and facilitating OCEL 2.0 export.
• Celonis OCDM Connector: A tool designed for the Celonis platform, enabling
import/export of object-centric event logs in OCEL 2.0 to the CelonisObject-Centric Data Model.
• ocpa library [11]: Focuses on processing object-centric event logs, process discovery,
model evaluation, performance analysis, and predictive monitoring.
• pm4js library: For JavaScript environments, it supports tasks like log flattening, statistics
generation, process discovery, and more.
• pm4py library [12]: A prominent Python library in process mining that has incorporated</p>
        <p>OCEL 2.0 support, compatible with the XML, JSON, and relational storage formats.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>3. Conclusion</title>
      <p>Using object-centric process mining, analysts can get a holistic overview of relationships
between diferent processes and their objects. The new OCEL 2.0 specification overcomes the
limitations of the OCEL 1.0 format by providing qualifiers, object-to-object relationships, and
changes to object attribute values. Our website builds a comprehensive one-stop shop with
all the content necessary to get started implementing connectors and custom process mining
analyses. In the future, we plan to extend the website with further content, such as additional
event logs and tools/libraries. We are open to external contributions, particularly those that
include real-life event logs.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>Funded by the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation) under
Germany’s Excellence Strategy - EXC-2023 Internet of Production - 390621612. We also thank
the Alexander von Humboldt (AvH) Stiftung for supporting our research.
[7] G. Park, L. Tacke Genannt Unterberg, Procure-to-Payment (P2P) Object-Centric event log
in OCEL 2.0 Standard, 2023. doi1:0.5281/zenodo.8412919.
[8] M. Pegoraro, Angular GitHub Commits Object-Centric Event Log, 2023. do1i:0.5281/
zenodo.8430331.
[9] J. N. Adams, W. M. P. van der Aalst, OC(π): Object-centric Process Insights, in: L.
Bernardinello, L. Petrucci (Eds.), Application and Theory of Petri Nets and Concurrency - 43rd
International Conference, PETRI NETS 2022, Bergen, Norway, June 19-24, 2022,
Proceedings, volume 13288 ofLecture notes in computer science, Springer, 2022, pp. 139–150.
doi:10.1007/978-3-031-06653-5_8.
[10] A. Berti, W. M. P. van der Aalst, OC-PM: analyzing object-centric event logs and
process models, Int. J. Softw. Tools Technol. Transf. 25 (2023) 1–17. doi:10.1007/
s10009-022-00668-w.
[11] J. N. Adams, G. Park, W. M. P. van der Aalst, ocpa: A Python library for object-centric
process analysis, Softw. Impacts 14 (2022) 100438. doi: 10.1016/j.simpa.2022.100438.
[12] A. Berti, S. van Zelst, D. Schuster, PM4Py: A process mining library for Python, Software
Impacts 17 (2023) 100556. doi:10.1016/j.simpa.2023.100556.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>W. M. P. van der Aalst</surname>
          </string-name>
          ,
          <article-title>Object-Centric Process Mining: Dealing with Divergence and Convergence in Event Data</article-title>
          , in: SEFM, Springer,
          <year>2019</year>
          , pp.
          <fpage>3</fpage>
          -
          <lpage>25</lpage>
          .
          <year>doi1</year>
          :
          <fpage>0</fpage>
          .1007/ 978-3-
          <fpage>030</fpage>
          -30446-
          <issue>1</issue>
          _
          <fpage>1</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>D.</given-names>
            <surname>Fahland</surname>
          </string-name>
          ,
          <article-title>Process Mining over Multiple Behavioral Dimensions with Event Knowledge Graphs</article-title>
          , in: Process Mining Handbook, Springer,
          <year>2022</year>
          , pp.
          <fpage>274</fpage>
          -
          <lpage>319</lpage>
          .
          <year>doi1</year>
          :
          <fpage>0</fpage>
          .1007/ 978-3-
          <fpage>031</fpage>
          -08848-
          <issue>3</issue>
          _
          <fpage>9</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Ghahfarokhi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Park</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Berti</surname>
          </string-name>
          ,
          <string-name>
            <surname>W. M. P. van der Aalst</surname>
          </string-name>
          , OCEL Standard (
          <year>2020</year>
          ). URL: https://www.ocel-standard.
          <source>org/1</source>
          .0/specification.pd.f
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M. T.</given-names>
            <surname>Wynn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Lebherz</surname>
          </string-name>
          ,
          <string-name>
            <surname>W. M. P. van der Aalst</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Accorsi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Ciccio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Jayarathna</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. M. W.</given-names>
            <surname>Verbeek</surname>
          </string-name>
          ,
          <article-title>Rethinking the Input for Process Mining: Insights from the XES Survey</article-title>
          and Workshop, in: ICPM Workshops, Springer,
          <year>2021</year>
          , pp.
          <fpage>3</fpage>
          -
          <lpage>16</lpage>
          . doi:
          <volume>10</volume>
          .1007/ 978-3-
          <fpage>030</fpage>
          -98581-
          <issue>3</issue>
          _
          <fpage>1</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>B.</given-names>
            <surname>Knopp</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Graves</surname>
          </string-name>
          ,
          <string-name>
            <surname>Container Logistics</surname>
          </string-name>
          Object-Centric Event Log,
          <year>2023</year>
          . do1i:
          <fpage>0</fpage>
          .5281/ ZENODO.8289899.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>B.</given-names>
            <surname>Knopp</surname>
          </string-name>
          ,
          <string-name>
            <surname>W. M. P. van der Aalst</surname>
          </string-name>
          ,
          <source>Order Management Object-Centric Event Log in OCEL 2.0 standard</source>
          ,
          <year>2023</year>
          . doi1:
          <fpage>0</fpage>
          .5281/zenodo.8337463.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>