Flattening an Object-Centric Log

An object-centric log keeps every business object an event touched. A flat event log has room for one case ID per event. Flattening picks one object type as the case and writes one flat log for it.

One flat log per object type

Take Order Management (OCEL 2.0). It has six object types, and each one gives a different flat log:

Follow each Cases Events Activities
Orders 2,000 6,566 4
Items 7,659 60,935 11
Packages 1,128 3,695 4
Employees 18 17,570 8
Products 20 54,697 11
Customers 15 4,000 2

What changes when you flatten

  • Events are copied. An event that touches five items appears once in each of those five item cases. Together the six logs above hold far more events than the 21,008 in the original log.
  • Some events drop out. The orders log keeps only the events linked to an order: place, confirm, pay and payment reminder. Picking, packing and shipping are linked to items and packages, not to orders, so they are not in it.
  • Counts can mislead. Because events are copied, adding up events across cases overstates how much work happened. Count events in the original log when the number matters.

When to keep it object-centric

Keep the object-centric log when the question crosses object types: how long an order waits for its last item, or which packages hold items from several orders. See Files, OCEL and Event Logs for loading an OCEL 2.0 file.

Object-Centric Logs lists every data set that comes as an object-centric log.