Event Graph of BPI Challenge 2017

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>建模为带标签属性图（labeled property graph）的业务流程事件数据 数据格式 ----------- 本数据集包含一份带标签属性图，提供两种不同文件格式。 #1) Neo4j .dump 格式 该文件为Neo4j数据库导出文件，包含完整的图结构，可通过以下命令导入至全新的Neo4j数据库实例，具体可参考Neo4j官方文档：https://neo4j.com/docs/ /bin/neo4j-admin.(bat|sh) load --database=graph.db --from=< 该.dump文件基于Neo4j v3.5版本生成。 #2) .graphml 格式 一份压缩包（.zip），内含完整图结构的.graphml文件。 数据模式 ----------- 本图为面向业务流程事件数据的带标签属性图，采用以下核心概念： :Event（事件）节点：每个事件节点描述一个离散事件，即由属性"Activity（活动）"定义的原子观测行为，其发生时间由属性"timestamp（时间戳）"标注。 :Entity（实体）节点：每个实体节点描述一类实体（如对象或用户），包含EntityType（实体类型）与ID（属性"ID"）作为唯一标识。 :Log（日志）节点：描述一组被同步记录的事件集合，多数图仅包含一个日志节点。 :Class（类别）节点：描述一类已被记录的观测类型，例如可被观测到的各类活动；:Class节点将事件按完全一致的观测结果划分为集合。 :CORR（关联）关系：从:Event节点指向:Entity节点，用于描述事件与特定实体的关联关系；一个事件可关联至多个实体。 :DF（直接后继）关系：在两个:Event节点之间定义"直接后继"关系，用于描述某一事件紧随另一事件发生；处于:DF关系中的两个事件必须关联至同一个实体节点。所有:DF关系共同构成一张有向无环图。 :HAS（包含）关系：从:Log节点指向:Event节点，用于描述某事件被记录于哪一个事件日志中。 :OBSERVES（观测）关系：从:Event节点指向:Class节点，用于描述某事件所属的事件类别，即该图中观测到的具体活动类型。 :REL（关系）：作为任意两个:Entity节点之间结构关系的占位符。 上述概念的详细定义可参考：Stefan Esser、Dirk Fahland发表于《CoRR abs/2005.14552 (2020)》的论文《Multi-Dimensional Event Data in Graph Databases》（图数据库中的多维度事件数据），论文链接：https://arxiv.org/abs/2005.14552 数据内容 ------------- neo4j-bpic17-2021-02-17 (.dump|.graphml.zip) 本数据集为整合后的图结构，完整描述BPI Challenge 2017数据集的原始事件数据。数据来源：van Dongen, B.F. (Boudewijn) (2017): BPI Challenge 2017. 4TU.ResearchData. 数据集，DOI链接：https://doi.org/10.4121/uuid:5f3067df-f10b-45da-b98b-86ae4c7a310b 本事件日志对应荷兰某金融机构的贷款申请流程。数据涵盖2016年通过线上系统提交的全部贷款申请，以及截至2017年2月1日15:11的所有后续流程事件。提供本数据与流程的机构与DOI:10.4121/uuid:3926db30-f712-4394-aebc-75976070e91f所述一致，但该流程的支撑系统在此期间已完成更新。具体而言，新系统支持为单个申请提供多份贷款报价，此类报价可通过日志中的ID进行追踪。 本数据集包含以下实体及其对应事件： - Application（申请）：客户向荷兰金融机构提交的信贷申请文件 - Offer（报价）：金融机构生成并发送给客户的贷款报价文件 - Workflow（工作流）：由案件管理系统对活动进行的逻辑分组，用于辅助金融机构工作人员处理申请与报价 - Case_R（案例参与者）：金融机构的用户或工作人员 - Case_AO（案例关联申请与报价）：派生实体，用于描述报价与其关联申请之间的具象化关系 - Case_AW（案例关联工作流与申请）：派生实体，用于描述工作流与其关联申请之间的具象化关系 - Case_WO（案例关联工作流与报价）：派生实体，用于描述报价与其关联工作流之间的具象化关系 数据规模 --------- BPIC17数据集：节点数1425995，关系数10300197