Process Mining Concepts - Revision history

TeeHiet: TK-56394

2025-03-03T12:56:46Z

TK-56394

← Older revision		Revision as of 12:56, 3 March 2025
Line 52:		Line 52:
	Filters are used to choose specific parts of a model for more detailed analysis, i.e. slice the model in a smaller part. Filter consist of one or more filter rules.		Filters are used to choose specific parts of a model for more detailed analysis, i.e. slice the model in a smaller part. Filter consist of one or more filter rules.

	There are ~~two~~ kinds of filter rules: case filter ~~rules and~~ event type filter rule. ~~Case~~ filter rules filter cases, and thus the number of cases in the eventlog decreases. The event type filters filter events of specific types, and thus the number of cases don't decrease but the process flow in individual cases may change as some events are left out. Note that event type filter rules may filter out all events of a case, which results in cases that don't have events at all. Cases that don't have events, are not shown as cases in the analysis.		There are three kinds of filter rules: case filter rule, event type filter rule, and object attribute filter rule.
			* The case filter rules filter cases, and thus the number of cases in the eventlog decreases.
			* The event type filters filter events of specific types, and thus the number of cases don't decrease but the process flow in individual cases may change as some events are left out. Note that event type filter rules may filter out all events of a case, which results in cases that don't have events at all. Cases that don't have events, are not shown as cases in the analysis.
			* The object attribute filter rule filters the original object-centric model, and thus the number of objects in the analysis decreases.

	Details about filter rules:		Details about filter rules:

Ollvihe: /* Secure string */

2024-10-03T08:53:45Z

Secure string

← Older revision		Revision as of 08:53, 3 October 2024
Line 68:		Line 68:
	Datatables are a generic storage of tabular data. Datatables can be used to store events (eventlog) and cases (case attributes), and in addition any intermediate results needed by ETL. Also additional data needed by dashboards can be stored to datatables.		Datatables are a generic storage of tabular data. Datatables can be used to store events (eventlog) and cases (case attributes), and in addition any intermediate results needed by ETL. Also additional data needed by dashboards can be stored to datatables.

	== ~~Secure string~~ ==		== Secret ==
	~~Secure strings~~ are texts which need to be kept secret, and passwords to be used to login to the datasources for data extraction can be stored as secure strings. Secure strings can be added, changed and used in scripts, but their contents cannot be viewed, keeping the data secure.		Secrets are texts which need to be kept secret, and passwords to be used to login to the datasources for data extraction can be stored as secure strings. Secure strings can be added, changed and used in scripts, but their contents cannot be viewed, keeping the data secure.

Ollvihe: /* Model */

2021-09-29T19:19:44Z

Model

← Older revision		Revision as of 19:19, 29 September 2021
Line 47:		Line 47:

	== Model ==		== Model ==
	~~In QPR ProcessAnalyzer, a model~~ consists of a list of events and cases, forming an eventlog. Separate models should be created for each analyzed process. Processes can be e.g. Purchase-to-pay, Quote-to-cash, Request-to-resolution or Idea-to-product.		Model consists of a list of events and cases, forming an eventlog. Separate models should be created for each analyzed process. Processes can be e.g. Purchase-to-pay, Quote-to-cash, Request-to-resolution or Idea-to-product. Models belong to projects in QPR ProcessAnalyzer, helping to organize content.

	== Filter and Filter Rule ==		== Filter and Filter Rule ==

Ollvihe: /* Project */

2021-09-29T19:18:47Z

Project

← Older revision		Revision as of 19:18, 29 September 2021
Line 43:		Line 43:

	== Project==		== Project==
			Project is a collection of related dashboards, models, datatables, scripts and secure strings, e.g. they belong to the same analyzed process. Projects can also be created hierarchically by adding child projects to a project. Projects are also import for the access control, because user rights are set in the project level.
	~~Projects are collections~~ of dashboards, models, datatables, scripts and secure strings ~~that are related~~ to same process ~~etc~~. Projects can ~~form a hierarchy, so projects can have~~ child projects. ~~User~~ rights are ~~also~~ set on project level.
	[[File:ProcessAnalyzer concepts.png\|right\|700px]]		[[File:ProcessAnalyzer concepts.png\|right\|700px]]

Ollvihe: /* Project */

2021-09-29T15:26:00Z

Project

← Older revision		Revision as of 15:26, 29 September 2021
Line 45:		Line 45:

	Projects are collections of dashboards, models, datatables, scripts and secure strings that are related to same process etc. Projects can form a hierarchy, so projects can have child projects. User rights are also set on project level.		Projects are collections of dashboards, models, datatables, scripts and secure strings that are related to same process etc. Projects can form a hierarchy, so projects can have child projects. User rights are also set on project level.
	[[File:ProcessAnalyzer concepts.png\|right\|~~800px~~]]		[[File:ProcessAnalyzer concepts.png\|right\|700px]]

	== Model ==		== Model ==

Ollvihe at 15:25, 29 September 2021

2021-09-29T15:25:45Z

← Older revision		Revision as of 15:25, 29 September 2021
Line 41:		Line 41:

	In QPR ProcessAnalyzer, case attributes are stored to a datatable, where there is a row for each case and column for each case attributes. There needs to be one column for the case id to identify the row. Case attributes have a certain data type, such as string, integer, decimal number, date, boolean or duration. Event attributes are stored as additional columns in the events (eventlog) datatable. Note that also event type and event timestamps can also be perceived as event attributes, but in QPR ProcessAnalyzer these basic information of the eventlog are not part of the event attributes.		In QPR ProcessAnalyzer, case attributes are stored to a datatable, where there is a row for each case and column for each case attributes. There needs to be one column for the case id to identify the row. Case attributes have a certain data type, such as string, integer, decimal number, date, boolean or duration. Event attributes are stored as additional columns in the events (eventlog) datatable. Note that also event type and event timestamps can also be perceived as event attributes, but in QPR ProcessAnalyzer these basic information of the eventlog are not part of the event attributes.

			== Project==

			Projects are collections of dashboards, models, datatables, scripts and secure strings that are related to same process etc. Projects can form a hierarchy, so projects can have child projects. User rights are also set on project level.
			[[File:ProcessAnalyzer concepts.png\|right\|800px]]

	== Model ==		== Model ==
Line 58:		Line 63:
	Note that filters are only for filtering eventlogs. The expression language provides more generic filtering capabilities for any objects.		Note that filters are only for filtering eventlogs. The expression language provides more generic filtering capabilities for any objects.

	== ~~Project~~==		== Script ==
			Scripts are programmed routines to perform e.g. ETL tasks, e.g fetch data from source systems and store to datatables.

	~~[[File:ProcessAnalyzer concepts~~.~~png\|right\|800px]]~~		== Datatable ==
			Datatables are a generic storage of tabular data. Datatables can be used to store events (eventlog) and cases (case attributes), and in addition any intermediate results needed by ETL. Also additional data needed by dashboards can be stored to datatables.

	== Secure string ==		== Secure string ==
			Secure strings are texts which need to be kept secret, and passwords to be used to login to the datasources for data extraction can be stored as secure strings. Secure strings can be added, changed and used in scripts, but their contents cannot be viewed, keeping the data secure.
	~~== Script ==~~

	~~== Datatable ==~~

Ollvihe at 15:17, 29 September 2021

2021-09-29T15:17:54Z

← Older revision		Revision as of 15:17, 29 September 2021
Line 57:		Line 57:

	Note that filters are only for filtering eventlogs. The expression language provides more generic filtering capabilities for any objects.		Note that filters are only for filtering eventlogs. The expression language provides more generic filtering capabilities for any objects.

			== Project==

			[[File:ProcessAnalyzer concepts.png\|right\|800px]]

			== Secure string ==

			== Script ==

			== Datatable ==

Ollvihe at 14:18, 27 September 2021

2021-09-27T14:18:34Z

← Older revision		Revision as of 14:18, 27 September 2021
Line 1:		Line 1:
	~~Process~~ mining ~~and~~ QPR ProcessAnalyzer ~~uses the basic concepts that~~ are defined ~~and described~~ in this page.		The process mining concepts that are used by QPR ProcessAnalyzer, are defined in this page and their relations are shown in the diagram.

	[[File:Process mining concepts.png\|right\|800px]]		[[File:Process mining concepts.png\|right\|800px]]

Ollvihe at 14:16, 27 September 2021

2021-09-27T14:16:08Z

← Older revision		Revision as of 14:16, 27 September 2021
Line 1:		Line 1:
	Process mining and QPR ProcessAnalyzer uses the basic concepts that are defined and described in this page.		Process mining and QPR ProcessAnalyzer uses the basic concepts that are defined and described in this page.

			[[File:Process mining concepts.png\|right\|800px]]

	== Case ==		== Case ==

	Case is an instance in the process which flow is analyzed. Cases can be chosen differently depending on the analysis. A case consist of a sequence of events describing how the case flows through the process.		Case is an instance in the process which flow is analyzed. Cases can be chosen differently depending on the analysis. A case consist of a sequence of events describing how the case flows through the process.

Ollvihe: /* Model */

2021-08-23T11:50:15Z

Model

@@ Line 40: / Line 40: @@
 == Model ==
-In an organizational context, a process is the way that people work together and apply methods and tools, to accomplish predefined common objectives. The objectives include the value that the output of the process is expected to produce to its stakeholders.
+In QPR ProcessAnalyzer, a model consists of a list of events and cases, forming an eventlog. Separate models should be created for each analyzed process. Processes can be e.g. Purchase-to-pay, Quote-to-cash, Request-to-resolution or Idea-to-product.
 == Filter and Filter Rule ==