Object-centric Process Mining Model - Revision history

Ollvihe: /* Configure object-centric model */

2026-06-22T18:10:02Z

Configure object-centric model

← Older revision		Revision as of 18:10, 22 June 2026
Line 56:		Line 56:
	** '''Datatable''': Name of the datatable for this object type. This datatable is optional, so this field can be omitted.		** '''Datatable''': Name of the datatable for this object type. This datatable is optional, so this field can be omitted.
	** '''Unit''': Unit text describing the count of this type of objects (e.g., orders, deliveries, customers, products etc.). The unit may also be an empty string, if desired not to show any specific unit. This field is optional, and if not defined, the shown unit is "objects".		** '''Unit''': Unit text describing the count of this type of objects (e.g., orders, deliveries, customers, products etc.). The unit may also be an empty string, if desired not to show any specific unit. This field is optional, and if not defined, the shown unit is "objects".
	** '''Category''': Object ~~type~~ can be categorized either to a '''Master''' or '''Transaction''' (default) ~~object~~. Master data objects act as traversal terminals when perspectives are created: master data objects are included in results when reached but traversal does not continue through them. Typically, master data consists of the long-living entities, such as material, customers, suppliers, equipment, factories etc. Typically, transactions are those objects that flow though the process, such as orders, deliveries, invoices, service tickets etc. The idea is that each case in the perspective only contains transaction objects that are directly related to each other, but other transaction objects linked though the master data objects are not part of the case. For example, a case may contain an order and related invoices, but not all orders and invoices to the same customer (even though they are linked by the customer master data record).		** '''Category''': Object types can be categorized either to '''Master''' or '''Transaction''' (default) objects. Master data objects act as traversal terminals when perspectives are created: master data objects are included in results when reached but traversal does not continue through them. Typically, master data consists of the long-living entities, such as material, customers, suppliers, equipment, factories etc. Typically, transactions are those objects that flow though the process, such as orders, deliveries, invoices, service tickets etc. The idea is that each case in the perspective only contains transaction objects that are directly related to each other, but other transaction objects linked though the master data objects are not part of the case. For example, a case may contain an order and related invoices, but not all orders and invoices to the same customer (even though they are linked by the customer master data record).
	* '''EventTypes''': Key-value-pairs from event type name to the event type datatable name. Event type names in the configuration need to match with event type names in the ''Events'' datatable.		* '''EventTypes''': Key-value-pairs from event type name to the event type datatable name. Event type names in the configuration need to match with event type names in the ''Events'' datatable.
	* '''Objects''': Objects datatable name. This datatable is mandatory.		* '''Objects''': Objects datatable name. This datatable is mandatory.

Ollvihe: /* Object-centric perspectives */

2026-06-17T10:25:56Z

Object-centric perspectives

← Older revision		Revision as of 10:25, 17 June 2026
Line 125:		Line 125:

	== Object-centric perspectives ==		== Object-centric perspectives ==
	Perspectives convert an object-centric model into a traditional case-centric eventlog, allowing to ~~view and~~ analyze object-centric models in Snowflake charts. ~~A single~~ perspective is not able describe the object-centric model entirely, but it's a projection from a certain viewpoint. By ~~using~~ analyses with ~~several~~ perspectives, it's possible to get a ~~more~~ complete picture of the object-centric model. The perspective starts from a certain object type and traverses ~~all the~~ object-to-object relations to find related objects and events.		Perspectives convert an object-centric model into a traditional case-centric eventlog, allowing to analyze object-centric models in Snowflake charts. Any individual perspective is not able describe the object-centric model entirely, but it's only a projection from a certain viewpoint. By applying analyses with different perspectives, it's possible to get a complete picture of the object-centric model. The perspective starts from a certain object type and traverses object-to-object relations to find related objects and events.

	The perspective is included to ~~the~~ stored filter. When a stored filter is selected, also the perspective in the filter is applied to the dashboard. This allows to quickly change ~~perspectives~~ for the entire dashboard. ~~The~~ chart specific perspective overrides the dashboard level perspective, so the dashboard level perspective is only applied for charts that don't have the chart specific perspective defined.		The perspective can be included to a stored filter. When a stored filter is selected, also the perspective in the filter is applied to the dashboard. This allows to quickly change the perspective for the entire dashboard. Additionally, the chart-specific perspective overrides the dashboard-level perspective, so the dashboard-level perspective is only applied for charts that don't have the chart-specific perspective defined.

	Perspectives can be modified in the [[Filtering_in_QPR_ProcessAnalyzer#Saving_filters\|stored filter dialog]] in the '''Perspective''' tab.		Perspectives can be modified in the [[Filtering_in_QPR_ProcessAnalyzer#Saving_filters\|stored filter dialog]] in the '''Perspective''' tab.

	To define a perspective, the following settings ~~are~~ defined in the chart settings:		To define a perspective, the following settings can be defined in the chart settings:
	* '''Base Object Type''': Object of this type will be cases in the perspective eventlog.		* '''Base Object Type''': Object of this type will be cases in the perspective eventlog.
	* '''Show Event Types''': List of event types which are included into the perspective eventlog. If no events are defined, all events will be included, but their event attributes are not included.		* '''Show Event Types''': List of event types which are included into the perspective eventlog. If no events are defined, all events will be included, but their event attributes are not included.
	* '''Object Relation Steps''': Specifies how many object-to-object relations will be traversed in order to find events connected to the base objects. Value zero means that only those events are returned that are directly connected to the base objects. This setting is optional, and if leaving it empty, all relations are traversed.		* '''Object Relation Steps''': Specifies how many object-to-object relations will be traversed in order to find events connected to the base objects. Value zero means that only those events are returned that are directly connected to the base objects. This setting is optional, and if leaving it empty, all relations are traversed.
	* '''Master Data Object Types''': ~~Array~~ of object type names that act as traversal terminals during object-to-object relation expansion. When an object of a listed type is reached during traversal, it is included in the related object set but is not used as a starting point for further outward traversal. If not defined, the ~~value is derived from~~ the model configuration ~~by collecting all object types~~ that ~~have Type set to "Master" in their OcelDataSource ObjectTypes configuration. Has~~ no effect when ~~RecursionDepth~~ is set to 0, since no traversal occurs in that case. There is no user-interface for this setting yet.		* '''Master Data Object Types''': List of object type names that act as traversal terminals during object-to-object relation expansion. When an object of a listed type is reached during traversal, it is included in the related object set but is not used as a starting point for further outward traversal. If not defined, the defaults defined in the model configuration are applied. Note that this setting has no effect when ''Object Relation Steps'' is set to zero, since no traversal occurs in that case. (There is no user-interface for this setting yet.)

	== Perspective eventlog ==		== Perspective eventlog ==

Ollvihe: /* Configure object-centric model */

2026-06-17T10:18:24Z

Configure object-centric model

← Older revision		Revision as of 10:18, 17 June 2026
Line 19:		Line 19:
	"Invoice": {		"Invoice": {
	"Datatable": "OCPM object: Invoice",		"Datatable": "OCPM object: Invoice",
	"Unit": "invoices"		"Unit": "invoices",
			"Category": "Transaction"
	},		},
	"Payment": {		"Payment": {
	"Datatable": "OCPM object: Payment",		"Datatable": "OCPM object: Payment",
	"Unit": "payments"		"Unit": "payments",
			"Category": "Transaction"
	},		},
	"Purchase Order": {		"Purchase Order": {
	"Datatable": "OCPM object: Purchase Order",		"Datatable": "OCPM object: Purchase Order",
	"Unit": "orders"		"Unit": "orders",
			"Category": "Transaction"
	},		},
	"Customer": {		"Customer": {

Ollvihe: /* Configure object-centric model */

2026-06-17T10:17:49Z

Configure object-centric model

← Older revision		Revision as of 10:17, 17 June 2026
Line 53:		Line 53:
	** '''Datatable''': Name of the datatable for this object type. This datatable is optional, so this field can be omitted.		** '''Datatable''': Name of the datatable for this object type. This datatable is optional, so this field can be omitted.
	** '''Unit''': Unit text describing the count of this type of objects (e.g., orders, deliveries, customers, products etc.). The unit may also be an empty string, if desired not to show any specific unit. This field is optional, and if not defined, the shown unit is "objects".		** '''Unit''': Unit text describing the count of this type of objects (e.g., orders, deliveries, customers, products etc.). The unit may also be an empty string, if desired not to show any specific unit. This field is optional, and if not defined, the shown unit is "objects".
	** '''Category''': Object type can either be '''Master''' or '''Transaction''' (default). Master data ~~object types~~ act as traversal terminals when ~~the perspective is~~ created: master data objects are included in results when reached but traversal does not continue through them. Typically master data ~~are~~ the long-living entities, such as ~~products~~, customers ~~and~~ suppliers. Typically transactions are ~~the object types~~ that flow though the process, such as orders, deliveries ~~and~~ invoices. The idea is that each case in the perspective only contains transaction objects that are directly related to each other, but transaction objects ~~related~~ though master data objects. For example a case ~~should~~ contain an order and ~~its~~ invoices, but not all orders and invoices ~~for~~ the same customer (even though they are linked ~~though~~ the customer record).		** '''Category''': Object type can be categorized either to a '''Master''' or '''Transaction''' (default) object. Master data objects act as traversal terminals when perspectives are created: master data objects are included in results when reached but traversal does not continue through them. Typically, master data consists of the long-living entities, such as material, customers, suppliers, equipment, factories etc. Typically, transactions are those objects that flow though the process, such as orders, deliveries, invoices, service tickets etc. The idea is that each case in the perspective only contains transaction objects that are directly related to each other, but other transaction objects linked though the master data objects are not part of the case. For example, a case may contain an order and related invoices, but not all orders and invoices to the same customer (even though they are linked by the customer master data record).
	* '''EventTypes''': Key-value-pairs from event type name to the event type datatable name. Event type names in the configuration need to match with event type names in the ''Events'' datatable.		* '''EventTypes''': Key-value-pairs from event type name to the event type datatable name. Event type names in the configuration need to match with event type names in the ''Events'' datatable.
	* '''Objects''': Objects datatable name. This datatable is mandatory.		* '''Objects''': Objects datatable name. This datatable is mandatory.

Ollvihe: /* Object-centric perspectives */

2026-06-16T19:05:15Z

Object-centric perspectives

← Older revision		Revision as of 19:05, 16 June 2026
Line 129:		Line 129:

	To define a perspective, the following settings are defined in the chart settings:		To define a perspective, the following settings are defined in the chart settings:
	* '''Base Object ~~type~~''': Object of this type will be cases in the perspective eventlog.		* '''Base Object Type''': Object of this type will be cases in the perspective eventlog.
	* '''Show Event Types''': List of event types which are included into the perspective eventlog. If no events are defined, all events will be included, but their event attributes are not included.		* '''Show Event Types''': List of event types which are included into the perspective eventlog. If no events are defined, all events will be included, but their event attributes are not included.
	* '''Object Relation Steps''': Specifies how many object-to-object relations will be traversed in order to find events connected to the base objects. Value zero means that only those events are returned that are directly connected to the base objects. This setting is optional, and if leaving it empty, all relations are traversed.		* '''Object Relation Steps''': Specifies how many object-to-object relations will be traversed in order to find events connected to the base objects. Value zero means that only those events are returned that are directly connected to the base objects. This setting is optional, and if leaving it empty, all relations are traversed.

Ollvihe: /* Object-centric perspectives */

2026-06-16T19:04:03Z

Object-centric perspectives

← Older revision		Revision as of 19:04, 16 June 2026
Line 132:		Line 132:
	* '''Show Event Types''': List of event types which are included into the perspective eventlog. If no events are defined, all events will be included, but their event attributes are not included.		* '''Show Event Types''': List of event types which are included into the perspective eventlog. If no events are defined, all events will be included, but their event attributes are not included.
	* '''Object Relation Steps''': Specifies how many object-to-object relations will be traversed in order to find events connected to the base objects. Value zero means that only those events are returned that are directly connected to the base objects. This setting is optional, and if leaving it empty, all relations are traversed.		* '''Object Relation Steps''': Specifies how many object-to-object relations will be traversed in order to find events connected to the base objects. Value zero means that only those events are returned that are directly connected to the base objects. This setting is optional, and if leaving it empty, all relations are traversed.
			* '''Master Data Object Types''': Array of object type names that act as traversal terminals during object-to-object relation expansion. When an object of a listed type is reached during traversal, it is included in the related object set but is not used as a starting point for further outward traversal. If not defined, the value is derived from the model configuration by collecting all object types that have Type set to "Master" in their OcelDataSource ObjectTypes configuration. Has no effect when RecursionDepth is set to 0, since no traversal occurs in that case. There is no user-interface for this setting yet.

	== Perspective eventlog ==		== Perspective eventlog ==

Ollvihe: /* Configure object-centric model */

2026-06-16T18:30:38Z

Configure object-centric model

← Older revision		Revision as of 18:30, 16 June 2026
Line 53:		Line 53:
	** '''Datatable''': Name of the datatable for this object type. This datatable is optional, so this field can be omitted.		** '''Datatable''': Name of the datatable for this object type. This datatable is optional, so this field can be omitted.
	** '''Unit''': Unit text describing the count of this type of objects (e.g., orders, deliveries, customers, products etc.). The unit may also be an empty string, if desired not to show any specific unit. This field is optional, and if not defined, the shown unit is "objects".		** '''Unit''': Unit text describing the count of this type of objects (e.g., orders, deliveries, customers, products etc.). The unit may also be an empty string, if desired not to show any specific unit. This field is optional, and if not defined, the shown unit is "objects".
			** '''Category''': Object type can either be '''Master''' or '''Transaction''' (default). Master data object types act as traversal terminals when the perspective is created: master data objects are included in results when reached but traversal does not continue through them. Typically master data are the long-living entities, such as products, customers and suppliers. Typically transactions are the object types that flow though the process, such as orders, deliveries and invoices. The idea is that each case in the perspective only contains transaction objects that are directly related to each other, but transaction objects related though master data objects. For example a case should contain an order and its invoices, but not all orders and invoices for the same customer (even though they are linked though the customer record).
	* '''EventTypes''': Key-value-pairs from event type name to the event type datatable name. Event type names in the configuration need to match with event type names in the ''Events'' datatable.		* '''EventTypes''': Key-value-pairs from event type name to the event type datatable name. Event type names in the configuration need to match with event type names in the ''Events'' datatable.
	* '''Objects''': Objects datatable name. This datatable is mandatory.		* '''Objects''': Objects datatable name. This datatable is mandatory.

Ollvihe: /* Configure object-centric model */

2026-06-16T18:09:42Z

Configure object-centric model

← Older revision		Revision as of 18:09, 16 June 2026
Line 28:		Line 28:
	"Datatable": "OCPM object: Purchase Order",		"Datatable": "OCPM object: Purchase Order",
	"Unit": "orders"		"Unit": "orders"
			},
			"Customer": {
			"Datatable": "OCPM object: Customer",
			"Unit": "customers",
			"Category": "Master"
	}		}
	},		},

Ollvihe: /* Configure object-centric model */

2026-04-03T21:19:46Z

Configure object-centric model

← Older revision		Revision as of 21:19, 3 April 2026
Line 16:		Line 16:
	<pre>		<pre>
	{		{
	~~"Objects": "OCPM: objects",~~
	~~"Events": "OCPM: events",~~
	~~"ObjectToObject": "OCPM: object-to-object",~~
	~~"EventToObject": "OCPM: event-to-object",~~
	"ObjectTypes": {		"ObjectTypes": {
	"Invoice": {		"Invoice": {
Line 40:		Line 36:
	"Insert Invoice": "OCPM event: Insert Invoice",		"Insert Invoice": "OCPM event: Insert Invoice",
	"Insert Payment": "OCPM event: Insert Payment"		"Insert Payment": "OCPM event: Insert Payment"
	}		},
			"Objects": "OCPM: objects",
			"Events": "OCPM: events",
			"ObjectToObject": "OCPM: object-to-object",
			"EventToObject": "OCPM: event-to-object"
	}		}
	</pre>		</pre>

Ollvihe: /* Configure object-centric model */

2026-04-03T21:19:31Z

Configure object-centric model

← Older revision		Revision as of 21:19, 3 April 2026
Line 45:		Line 45:

	The datasource configuration can have following properties:		The datasource configuration can have following properties:
			* '''ObjectTypes''': Key-value-pairs from object type name to a dictionary of object type specific properties. Object type names in the configuration need to match with object type names in the ''Objects'' datatable. The following fields can be defined:
			** '''Datatable''': Name of the datatable for this object type. This datatable is optional, so this field can be omitted.
			** '''Unit''': Unit text describing the count of this type of objects (e.g., orders, deliveries, customers, products etc.). The unit may also be an empty string, if desired not to show any specific unit. This field is optional, and if not defined, the shown unit is "objects".
			* '''EventTypes''': Key-value-pairs from event type name to the event type datatable name. Event type names in the configuration need to match with event type names in the ''Events'' datatable.
	* '''Objects''': Objects datatable name. This datatable is mandatory.		* '''Objects''': Objects datatable name. This datatable is mandatory.
	* '''Events''': Events datatable name. This datatable is mandatory.		* '''Events''': Events datatable name. This datatable is mandatory.
	* '''ObjectToObject''': Object-to-object relations datatable name. This datatable is mandatory.		* '''ObjectToObject''': Object-to-object relations datatable name. This datatable is mandatory.
	* '''EventToObject''': Event-to-object relations datatable name. This datatable is mandatory.		* '''EventToObject''': Event-to-object relations datatable name. This datatable is mandatory.
	* '''ObjectTypes''': Key-value-pairs from object type name to object type datatable name. Object type names in the configuration need to match with object type names in the ''Objects'' datatable. If there is no object type table existing, define ''null'' as the value. The value is either a string or an object. The string value defines a datatable name. When defined as an object, the following optional fields can be defined:
	** '''Datatable''': Name of the datatable for this object type.
	** '''Unit''': Unit text describing the count of this type of objects (e.g., orders, delivieries, customers, products etc.).
	* '''EventTypes''': Key-value-pairs from event type name to the event type datatable name. Event type names in the configuration need to match with event type names in the ''Events'' datatable.

	== Filtering object-centric model ==		== Filtering object-centric model ==