cff-version: 1.2.0
abstract: "Business process event data modeled as labeled property graphs<br><br>Data Format<br>-----------<br><br>The dataset comprises one labeled property graph in two different file formats.<br><br>#1) Neo4j .dump format<br><br>A neo4j (https://neo4j.com) database dump that contains the entire graph and can be imported into a fresh neo4j database instance using the following command, see also the neo4j documentation: https://neo4j.com/docs/<br><br>/bin/neo4j-admin.(bat|sh) load --database=graph.db --from=<br><br>The .dump was created with Neo4j v3.5.<br><br>#2) .graphml format<br><br>A .zip file containing a .graphml file of the entire graph<br><br><br>Data Schema<br>-----------<br><br>The graph is a labeled property graph over business process event data. Each graph uses the following concepts<br><br>:Event nodes - each event node describes a discrete event, i.e., an atomic observation described by attribute "Activity" that occurred at the given "timestamp"<br><br>:Entity nodes - each entity node describes an entity (e.g., an object or a user), it has an EntityType and an identifier (attribute "ID")<br><br>:Log nodes - describes a collection of events that were recorded together, most graphs only contain one log node<br><br>:Class nodes - each class node describes a type of observation that has been recorded, e.g., the different types of activities that can be observed, :Class nodes group events into sets of identical observations<br><br>:CORR relationships - from :Event to :Entity nodes, describes whether an event is correlated to a specific entity; an event can be correlated to multiple entities<br><br>:DF relationships - "directly-followed by" between two :Event nodes describes which event is directly-followed by which other event; both events in a :DF relationship must be correlated to the same entity node. All :DF relationships form a directed acyclic graph.<br><br>:HAS relationship - from a :Log to an :Event node, describes which events had been recorded in which event log<br><br>:OBSERVES relationship - from an :Event to a :Class node, describes to which event class an event belongs, i.e., which activity was observed in the graph<br><br>:REL relationship - placeholder for any structural relationship between two :Entity nodes<br><br>The concepts a further defined in Stefan Esser, Dirk Fahland: Multi-Dimensional Event Data in Graph Databases. CoRR abs/2005.14552 (2020) https://arxiv.org/abs/2005.14552<br><br><br>Data Contents<br>-------------<br><br>neo4j-bpic17-2021-02-17 (.dump|.graphml.zip)<br><br>An integrated graph describing the raw event data of the entire BPI Challenge 2017 dataset. <br>van Dongen, B.F. (Boudewijn) (2017): BPI Challenge 2017. 4TU.ResearchData. Collection. https://doi.org/10.4121/uuid:5f3067df-f10b-45da-b98b-86ae4c7a310b<br><br>This event log pertains to a loan application process of a Dutch financial institute. The data contains all applications filed trough an online system in 2016 and their subsequent events until February 1st 2017, 15:11. The company providing the data and the process under consideration is the same as doi:10.4121/uuid:3926db30-f712-4394-aebc-75976070e91f. However, the system supporting the process has changed in the meantime. In particular, the system now allows for multiple offers per application. These offers can be tracked through their IDs in the log.<br><br>The data contains the following entities and their events<br><br>- Application - a credit application document submitted by a customer to a Dutch financial institute<br>- Offer - a loan offer document created by the institute and sent to the customer<br>- Workflow - a logical grouping of activities by the case management system supporting workers at the financial institute to handle applications and offers<br>- Case_R - a user or worker of the financial institute<br>- Case_AO - a derived entity describing the reified relation between an offer and its related application<br>- Case_AW - a derived entity describing the reified relation between the workflow and its related application<br>- Case_WO - a derived entity describing the reified relation between an offer and its related workflow<br><br><br>Data Size<br>---------<br><br>BPIC17, nodes: 1425995, relationships: 10300197<br><br>"
authors:
  - family-names: Fahland
    given-names: Dirk
  - family-names: Esser
    given-names: Stefan
title: "Event Graph of BPI Challenge 2017"
keywords:
version: 1
identifiers:
  - type: doi
    value: 10.4121/14169584.v1
license: CC BY 4.0
date-released: 2021-04-22