Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
2
datasets available to search
ShareScore release 0.9.0
Dataset results
2 results for “OCEL 2.0 standard”
Procure-To-Payment (P2P) Object-centric Event Log in OCEL 2.0 Standard
<p><strong>Short Description</strong></p> <p>This process describes the Procure-To-Pay (P2P) procedure within an organization, starting from the initiation of a purchase requirement up to the execution of payment. This simulation extensively uses genuine SAP transactions and object types to offer a realistic representation of the P2P process.</p> <p><strong>Overview</strong></p> <p>Within our simulated organization:</p> <ul> <li> <p>Procurement Initiatives: The procurement journey begins when a department or individual recognizes a need and creates a Purchase Requisition using transaction ME51N.</p> </li> <li> <p>Approval Process: Before the purchase can proceed, the requisition must be approved. This is carried out using transaction ME54N. Given the nature of our simulation, there may be instances where the approval process takes an unusually long time, exemplifying the Lengthy Approval Process behavior.</p> </li> <li> <p>Vendor Interactions:</p> <ul> <li>Upon approval, a Request for Quotation is sent out to potential vendors using transaction ME41.</li> <li>Vendors then submit their quotations, which are maintained in the system using transaction ME47.</li> </ul> </li> <li> <p>Purchase Order Creation: Once a vendor's quotation is selected, a Purchase Order is created using transaction ME21N. The purchase order is then subjected to an internal approval process (ME29N). Occasionally, maverick buying—where purchases are made without proper authorization—can be observed.</p> </li> <li> <p>Goods & Invoice Management:</p> <ul> <li>When the goods are received, a Goods Receipt is recorded using transaction MIGO.</li> <li>Invoices from vendors are then received and recorded. A three-way match, which checks the purchase order, goods receipt, and invoice for discrepancies, is performed using transaction MRBR.</li> </ul> </li> <li> <p>Payment: Once everything is verified, payments are executed using transaction F110. However, there may be instances of Duplicate Payments in our simulation, where the system mistakenly pays the same invoice more than once.</p> </li> </ul> <p><strong>Special Behaviors:</strong></p> <ul> <li>Maverick Buying: Unauthorized purchases, bypassing the standard procedure.</li> <li>Duplicate Payments: An error leading to the same invoice being paid multiple times.</li> <li>Lengthy Approval Process: Delays in approving purchase requisitions or purchase orders, which might lead to operational inefficiencies.</li> </ul> <p><strong>General Properties</strong></p> <p>An overview of log properties is given below.</p> <table> <thead> <tr> <th>Property</th> <th>Value</th> </tr> </thead> <tbody> <tr> <td>Event Types</td> <td>10</td> </tr> <tr> <td>Object Types</td> <td>7</td> </tr> <tr> <td>Events</td> <td>14671</td> </tr> <tr> <td>Objects</td> <td>9543</td> </tr> </tbody> </table> <p><strong>Authors</strong></p> <p>Gyunam Park and Leah Tacke genannt Unterberg</p> <p><strong>Contributing</strong></p> <p>To contribute, drop us an email! We are happy to receive your feedback.</p>
Order Management Object-centric Event Log in OCEL 2.0 Standard
<p><strong>General Description</strong></p> <p>This process describes the management of customer orders within a company, comprising both the registration and payment of incoming orders, as well as the process of packing and shipping these orders. For these tasks, our company deploys staff in their sales, warehousing, and shipment departments.</p> <p>This is an artificial event log according to the <a href="https://www.ocel-standard.org/">OCEL 2.0 Standard</a> simulated using CPN-Tools. Both the CPN and the SQLite can be downloaded. The simulation is an extension of the <a href="https://www.ocel-standard.org/beta/event-logs/simulations/legacy-logs">order management log</a> in the former OCEL standard.</p> <p><strong>Process Overview</strong></p> <p>At our company, <strong>customers</strong> place <strong>orders</strong> <em>(place order)</em> for different <strong>products</strong> in varying amounts. Each product type has a price and a weight. In the current market situation, there is an inflation that irregularly leads to an increase of prices. These price rises have a negative impact on customers’ purchasing power, i.e., on order volumes.</p> <p>When a customer places an order, this order is assigned to an <strong>employee</strong> of our company’s sales department. To foster customer satisfaction, our company has a single-face-to-customer policy. This means that per customer there is one primary sales representative who ought to render all services related to that customer. If that first representative is unavailable, a second sales representative should take care of the order. Should this employee be also unavailable, the order has to be managed by another employee. The tasks of sales employees comprise the registration <em>(confirm order)</em> as well as payment processing <em>(payment reminder, pay order)</em>.</p> <p>In parallel to this, the shipment of goods is prepared. For this, the stock of our company is checked by an employee of the warehousing department for the availability of the ordered <strong>items</strong>. If necessary, the warehouser reorders the item <em>(item out of stock, reorder item)</em>. Items ready for shipment are collected <em>(pick item)</em> for the placement into <strong>packages</strong> that are addressed to single customers. Here, it may happen that a package content relates to multiple orders, and order volumes are distributed over multiple packages.</p> <p>After all items allocated to a package have been picked, the package is compiled by a warehousing employee <em>(create package)</em>. Later on, this package is picked up by a shipment employee for transport <em>(send package)</em>. According to another policy, a warehousing employee should provide assistance to the shipment employee in loading the package. However, oftentimes shippers act contrary to that policy and load packages alone or together with a second shipment employee.</p> <p>Finally, the package is shipped. Deliveries may fail repeatedly <em>(failed delivery)</em> until successful delivery <em>(package delivered)</em>.</p> <p>The figure below depicts the process in a simplified manner, using an informal process notation to describe the control-flow and the involved object types. A formal description is given along with the artifacts in the next section.</p> <p>Further information can be found at: <a href="https://www.ocel-standard.org/event-logs/simulations/order-management/">https://www.ocel-standard.org/event-logs/simulations/order-management/</a></p> <p><strong>General Properties </strong></p> <p>An overview of log properties is given below.</p> <table> <thead> <tr> <th>Property</th> <th>Value</th> </tr> </thead> <tbody> <tr> <td>Event Types</td> <td>11</td> </tr> <tr> <td>Object Types</td> <td>6</td> </tr> <tr> <td>Events</td> <td>21008</td> </tr> <tr> <td>Objects</td> <td>10840</td> </tr> </tbody> </table> <p><strong>Control-Flow Behavior </strong></p> <p>The behavior of the log is described by a <a href="https://www.ocel-standard.org/beta/event-logs/simulations/logistics/images/full-ocpn.svg">respective object-centric Petri net</a>. Also, individual object types exhibit behavior that can be described by simpler Petri nets. See below.</p> <table> <thead> </thead> <tbody> <tr> <td><a href="https://www.ocel-standard.org/beta/event-logs/simulations/order-management/images/orders-ocpn.svg">orders</a></td> <td><a href="https://www.ocel-standard.org/beta/event-logs/simulations/order-management/images/customers-ocpn.svg">customers</a></td> </tr> <tr> <td><a href="https://www.ocel-standard.org/beta/event-logs/simulations/order-management/images/items-ocpn.svg">items</a></td> <td><a href="https://www.ocel-standard.org/beta/event-logs/simulations/order-management/images/employees-ocpn.svg">employees</a></td> </tr> <tr> <td><a href="https://www.ocel-standard.org/beta/event-logs/simulations/order-management/images/packages-ocpn.svg">packages</a></td> <td><a href="https://www.ocel-standard.org/beta/event-logs/simulations/order-management/images/products-ocpn.svg">products</a></td> </tr> <tr> <td><a href="https://www.ocel-standard.org/beta/event-logs/simulations/order-management/images/full-ocpn.svg"><strong>Full object-centric Petri net</strong></a></td> </tr> </tbody> </table> <p><strong>Object Relationships </strong></p> <p>The company pursues the "one-face-to-the-customer" policy, in which every customer has a dedicated sales representative as well as a deputy (secondary representative). These relationships are described in the log.</p> <table> <thead> <tr> <th>Source Object Type</th> <th>Target Object Type</th> <th>Qualifier</th> </tr> </thead> <tbody> <tr> <td>employees</td> <td>customers</td> <td>primarySalesRep</td> </tr> <tr> <td>employees</td> <td>customers</td> <td>secondarySalesRep</td> </tr> </tbody> </table> <p>Additionally, object-to-object relations can emerge at executions of specific activities:</p> <table> <thead> <tr> <th>Activity</th> <th>Source Object Type</th> <th>Target Object Type</th> <th>Qualifier</th> </tr> </thead> <tbody> <tr> <td>create package</td> <td>package</td> <td>employee</td> <td>packed by</td> </tr> <tr> <td>send package</td> <td>package</td> <td>employee</td> <td>forwarded by</td> </tr> <tr> <td>send package</td> <td>package</td> <td>employee</td> <td>shipped by</td> </tr> </tbody> </table> <p><strong>Simulation Model </strong></p> <p>The CPN used to create this event log can also be downloaded.To obtain simulated data, extract the linked ZIP file and play out the CPN therein, e.g., by using <a href="https://cpntools.org/">CPN Tools</a>.</p> <p>The play-out produces CSV files according to the schema of OCEL2.0. The provided jupyter notebook can be used to convert these files to an SQLite dump.</p> <p>For a technical documentation of the simulation model, please open the attached CPN with CPN Tools and see the annotations therein.</p> <p><strong>Acknowledgements</strong></p> <p>Funded under the Excellence Strategy of the Federal Government and the Länder<em>. </em>We also thank the Alexander von Humboldt (AvH) Stiftung for supporting our research.</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.