Object-centric Process Mining Model - Revision history

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 ==

Ollvihe: /* Configure object-centric model */

2026-04-03T21:16:02Z

Configure object-centric model

← Older revision		Revision as of 21:16, 3 April 2026
Line 21:		Line 21:
	"EventToObject": "OCPM: event-to-object",		"EventToObject": "OCPM: event-to-object",
	"ObjectTypes": {		"ObjectTypes": {
	"Invoice": "OCPM object: Invoice",		"Invoice": {
	"Payment": "OCPM object: Payment",		"Datatable": "OCPM object: Invoice",
	"Purchase Order": "OCPM object: Purchase Order"		"Unit": "invoices"
			},
			"Payment": {
			"Datatable": "OCPM object: Payment",
			"Unit": "payments"
			},
			"Purchase Order": {
			"Datatable": "OCPM object: Purchase Order",
			"Unit": "orders"
			}
	},		},
	"EventTypes": {		"EventTypes": {

Ollvihe: /* Object-centric model structure */

2026-04-03T21:15:05Z

Object-centric model structure

← Older revision		Revision as of 21:15, 3 April 2026
Line 94:		Line 94:
	\|-		\|-
	\|\|Object type attributes (several datatables)		\|\|Object type attributes (several datatables)
	\|\|~~If there are object~~ type specific attributes (i.e., object attributes that only a certain object type has)~~, these tables~~ are ~~used~~ to ~~store them~~. These tables are optional, so a datatable is not needed if an object type doesn't have any object type specific attributes. Additionally, these tables don't need to contain all objects in the model, so if an object is not found in these tables, all object specific ~~attribute values~~ have a ''null'' ~~value~~.		\|\|Object type specific attributes (i.e., object attributes that only a certain object type has) are stored to these datatables. These tables are optional, so a datatable is not needed if an object type doesn't have any object type specific attributes. Additionally, these tables don't need to contain all objects in the model, so if an object is not found in these tables, all object specific attributes have ''null'' values.
	\|\|		\|\|
	* '''OcelObjectTypeObjectId''': Object id. Matches to the objects datatable ''OcelObjectId'' column.		* '''OcelObjectTypeObjectId''': Object id. Matches to the objects datatable ''OcelObjectId'' column.
Line 100:		Line 100:
	\|-		\|-
	\|\|Event type attributes (several datatables)		\|\|Event type attributes (several datatables)
	\|\|~~If there are event~~ type specific attributes (i.e., event attributes that only a certain event type has)~~, these tables~~ are ~~used~~ to ~~store them~~. These tables are optional, so a datatable is not needed if an event type doesn't have any event type specific attributes. Additionally, these tables don't need to contain all events in the model, so if an event is not found in these tables, all event specific ~~attribute values~~ have a ''null'' ~~value~~.		\|\|Event type specific attributes (i.e., event attributes that only a certain event type has) are stored to these datatables. These tables are optional, so a datatable is not needed if an event type doesn't have any event type specific attributes. Additionally, these tables don't need to contain all events in the model, so if an event is not found in these tables, all event specific attributes have ''null'' values.
	\|\|		\|\|
	* '''OcelEventTypeEventId''': Event id. Matches to the events datatable ''OcelEventId'' column.		* '''OcelEventTypeEventId''': Event id. Matches to the events datatable ''OcelEventId'' column.

TeeHiet: TK-63020

2026-03-27T09:05:52Z

TK-63020

← Older revision		Revision as of 09:05, 27 March 2026
Line 40:		Line 40:
	* '''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.		* '''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.		* '''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.

Ollvihe: /* Configure object-centric model */

2026-02-01T14:36:19Z

Configure object-centric model

← Older revision		Revision as of 14:36, 1 February 2026
Line 38:		Line 38:
	* '''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 ~~optional if there are no object-to-object relations~~.		* '''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 of object type datatable ~~names~~. Object type names need to match with object type names in the Objects datatable. ~~Contains datatables for each object types which are needed if~~ there ~~are~~ object type ~~specific attributes~~.		* '''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.
	* '''EventTypes''': Key-value-pairs of event type datatable ~~names~~. Event type names need to match with event type names in the Events datatable~~. Contains datatables for each event types which are needed if there are event type specific attributes~~.		* '''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 ==

Ollvihe: /* Filtering object-centric model */

2026-02-01T14:32:22Z

Filtering object-centric model

← Older revision		Revision as of 14:32, 1 February 2026
Line 44:		Line 44:

	== Filtering object-centric model ==		== Filtering object-centric model ==
	Object-centric models can be filtered with similar filter rules as the case-centric models. ~~The object~~-centric filter rules consist of similar parameters as the case-centric filter rules and in addition a [[Object-centric_Process_Mining_Model#Object-centric_perspectives\|perspective]]. The purpose of the perspective is to ~~map~~ the ~~calculated~~ case-centric filter rule an object-centric filter rule applied to the object-centric model.		Object-centric models can be filtered with similar filter rules as the case-centric models. Object-centric filter rules consist of similar parameters as the case-centric filter rules and in addition a [[Object-centric_Process_Mining_Model#Object-centric_perspectives\|perspective]]. The purpose of the perspective is to convert the case-centric filter rule to an object-centric filter rule which is then applied to the object-centric model.

	When the ''Object relation steps'' is not defined, all objects related to the base objects are included/excluded to the filtered dataset. When the object relation steps is zero, only the selected type of objects are included/excluded. ~~For example~~, when ~~including~~ items with object relation steps ~~zero, all other object types of objects than the base objects are excluded. Vice versa, when excluding items~~, all other object types than the base objects are included. When object relation steps is one, objects directly related to the ~~filtered~~ object with an object-to-object relation are included or excluded. When object relation steps is two or more, several object-to-object relations are followed to find the included or excluded objects.		When the ''Object relation steps'' is not defined, all objects related to the base objects are included to excluded from the filtered dataset. When the object relation steps is zero, only the selected type of base objects are included or excluded. Vice versa, when excluding items with the zero object relation steps, all other object types than the base objects are included. When object relation steps is one, objects directly related to the base object with an object-to-object relation are included or excluded. When object relation steps is two or more, several object-to-object relations are followed to find the included or excluded objects.

	Object-centric filter rules can be created for the entire dashboard by pressing the blue plus button in the dashboard header (requires that an object-centric model is selected for the dashboard). Object-centric filter rules can also be added for an individual chart/flowchart by opening the ''Filter'' tab in the chart/flowchart settings and pressing the '''Object-centric filter''' button.		Object-centric filter rules can be created for the entire dashboard by pressing the blue plus button in the dashboard header (requires that an object-centric model is selected for the dashboard). Object-centric filter rules can also be added for an individual chart or flowchart by opening the ''Filter'' tab in the chart or flowchart settings and pressing the '''Object-centric filter''' button.

	Alternatively, datapoints in ~~charts~~ can be selected to create object-centric filter rules. When making the selection, user can choose whether to '''Include Objects''' and '''Exclude Objects'''. If the selection represents events, there are also the '''Include Events for Objects''' and '''Exclude Events for Objects''' options available. The perspective parameters defined for the chart will also be set for the created object-centric filter rule.		Alternatively, items or datapoints in chart or flowchart can be selected to create object-centric filter rules. When making the selection, user can choose whether to '''Include Objects''' and '''Exclude Objects'''. If the selection represents events, there are also the '''Include Events for Objects''' and '''Exclude Events for Objects''' options available. The perspective parameters defined for the chart will also be set for the created object-centric filter rule.

	It's also possible to use the case-centric filtering by selecting '''Include Cases''', '''Exclude Cases''', '''Include Events''' or '''Exclude Events'''. Note that the case-centric filtering doesn't work ~~with other~~ charts having different ~~perspective~~ defined.		It's also possible to use the case-centric filtering by selecting '''Include Cases''', '''Exclude Cases''', '''Include Events''' or '''Exclude Events'''. Note that the case-centric filtering doesn't work across charts having different perspectives defined.

	== Object-centric model structure ==		== Object-centric model structure ==

Ollvihe: /* Filtering object-centric model */

2026-02-01T00:05:25Z

Filtering object-centric model

← Older revision		Revision as of 00:05, 1 February 2026
Line 50:		Line 50:
	Object-centric filter rules can be created for the entire dashboard by pressing the blue plus button in the dashboard header (requires that an object-centric model is selected for the dashboard). Object-centric filter rules can also be added for an individual chart/flowchart by opening the ''Filter'' tab in the chart/flowchart settings and pressing the '''Object-centric filter''' button.		Object-centric filter rules can be created for the entire dashboard by pressing the blue plus button in the dashboard header (requires that an object-centric model is selected for the dashboard). Object-centric filter rules can also be added for an individual chart/flowchart by opening the ''Filter'' tab in the chart/flowchart settings and pressing the '''Object-centric filter''' button.

	Alternatively, datapoints in ~~a chart~~ can be selected to create object-centric filter rules. When making the selection, user can choose whether to '''Include Objects''' and '''Exclude Objects'''. If the selection represents events, there are also the '''Include Events for Objects''' and '''Exclude Events for Objects''' options available.		Alternatively, datapoints in charts can be selected to create object-centric filter rules. When making the selection, user can choose whether to '''Include Objects''' and '''Exclude Objects'''. If the selection represents events, there are also the '''Include Events for Objects''' and '''Exclude Events for Objects''' options available. The perspective parameters defined for the chart will also be set for the created object-centric filter rule.

	It's also possible to use the case-centric filtering by selecting '''Include Cases''', '''Exclude Cases''', '''Include Events''' or '''Exclude Events'''. Note that the case-centric filtering doesn't work with other charts having different perspective defined.		It's also possible to use the case-centric filtering by selecting '''Include Cases''', '''Exclude Cases''', '''Include Events''' or '''Exclude Events'''. Note that the case-centric filtering doesn't work with other charts having different perspective defined.

Ollvihe: /* Filtering object-centric model */

2026-02-01T00:02:27Z

Filtering object-centric model

← Older revision		Revision as of 00:02, 1 February 2026
Line 44:		Line 44:

	== Filtering object-centric model ==		== Filtering object-centric model ==
	Object-centric models can be filtered with similar filter rules as the case-centric models. The object-centric filter rules consist of similar parameters as the case-centric filter rules and in addition a perspective.		Object-centric models can be filtered with similar filter rules as the case-centric models. The object-centric filter rules consist of similar parameters as the case-centric filter rules and in addition a [[Object-centric_Process_Mining_Model#Object-centric_perspectives\|perspective]]. The purpose of the perspective is to map the calculated case-centric filter rule an object-centric filter rule applied to the object-centric model.

	by object ~~attribute values (similar to filtering by case attribute values in case-centric models)~~. For the object ~~attribute filtering~~, ~~following settings~~ are ~~defined:~~		When the ''Object relation steps'' is not defined, all objects related to the base objects are included/excluded to the filtered dataset. When the object relation steps is zero, only the selected type of objects are included/excluded. For example, when including items with object relation steps zero, all other object types of objects than the base objects are excluded. Vice versa, when excluding items, all other object types than the base objects are included. When object relation steps is one, objects directly related to the filtered object with an object-to-object relation are included or excluded. When object relation steps is two or more, several object-to-object relations are followed to find the included or excluded objects.
	* Include or ~~exclude logic~~
	* Base object ~~type to be filtered~~
	* Object attribute name
	* Object attribute values
	* Object relation steps ~~(optional)~~

	~~When the ''~~Object ~~relation steps'' is not defined, all objects related to~~ the ~~base objects are included/excluded to~~ the ~~filtered dataset. When~~ the object ~~relation steps~~ is ~~zero, only~~ the ~~selected type of objects are included~~/~~excluded. For example, when including items with object relation steps zero, all other object types of objects than~~ the ~~base objects are excluded. Vice versa, when excluding items, all other object types than~~ the ~~base objects are included. When object relation steps is one, objects directly related to~~ the ~~filtered object with an object~~-~~to-object relation are included or excluded. When object relation steps is two or more, several object-to-object relations are followed to find the included or excluded objects~~.		Object-centric filter rules can be created for the entire dashboard by pressing the blue plus button in the dashboard header (requires that an object-centric model is selected for the dashboard). Object-centric filter rules can also be added for an individual chart/flowchart by opening the ''Filter'' tab in the chart/flowchart settings and pressing the '''Object-centric filter''' button.

	~~Object attribute filter rules~~ can be ~~created for the entire dashboard by pressing the blue plus button in the dashboard header (requires that an~~ object-centric ~~model is selected for the dashboard). Object attribute~~ filter rules can also ~~be added for an individual chart/flowchart by opening~~ the ''~~Filter~~'' ~~tab in the chart/flowchart settings~~ and ~~pressing the~~ '''~~Object-centric filter~~''' ~~button~~.		Alternatively, datapoints in a chart can be selected to create object-centric filter rules. When making the selection, user can choose whether to '''Include Objects''' and '''Exclude Objects'''. If the selection represents events, there are also the '''Include Events for Objects''' and '''Exclude Events for Objects''' options available.

	~~Alternatively, a chart showing object attribute values as dimension or columns, can be selected~~ to ~~start creating object attribute filter rules. When making~~ the ~~selection, user can choose between~~ '''Include ~~Objects~~''' ~~and~~ '''Exclude ~~Objects~~'''~~. It's also possible to use the case-centric filtering by selecting~~ '''Include ~~Cases~~''' or '''~~Cases Cases~~'''. Note that the case-centric ~~attribute~~ filtering doesn't work ~~with the object-centric flowchart and~~ with other charts having different perspective ~~selected~~.		It's also possible to use the case-centric filtering by selecting '''Include Cases''', '''Exclude Cases''', '''Include Events''' or '''Exclude Events'''. Note that the case-centric filtering doesn't work with other charts having different perspective defined.

	== Object-centric model structure ==		== Object-centric model structure ==

Ollvihe: /* Filtering object-centric model */

2026-01-31T23:56:31Z

Filtering object-centric model

← Older revision		Revision as of 23:56, 31 January 2026
Line 44:		Line 44:

	== Filtering object-centric model ==		== Filtering object-centric model ==
	Object-centric models can be filtered by object attribute values (similar to filtering by case attribute values in case-centric models). For the object attribute filtering, following settings are defined:		Object-centric models can be filtered with similar filter rules as the case-centric models. The object-centric filter rules consist of similar parameters as the case-centric filter rules and in addition a perspective.

			by object attribute values (similar to filtering by case attribute values in case-centric models). For the object attribute filtering, following settings are defined:
	* Include or exclude logic		* Include or exclude logic
	* Base object type to be filtered		* Base object type to be filtered