Conformance Analysis - Revision history

Ollvihe: /* Top Deviations (in-memory) / Deviating Flows (Snowflake) */

2023-06-01T18:02:32Z

Top Deviations (in-memory) / Deviating Flows (Snowflake)

← Older revision		Revision as of 18:02, 1 June 2023
Line 17:		Line 17:

	== Top Deviations (in-memory) / Deviating Flows (Snowflake) ==		== Top Deviations (in-memory) / Deviating Flows (Snowflake) ==
	This table shows the ~~specific~~ conformance deviation ~~reasons~~ for the ~~nonconforming~~ cases. For the in-memory models, all deviations are shown, and for the Snowflake models, only the flow related deviations are shown. There are following columns:		This table shows specific reasons for the conformance deviation for the non conforming cases. For the in-memory models, all deviations are shown, and for the Snowflake models, only the flow related deviations are shown. There are following columns:
	* '''Top Deviating''': this column shows the type of deviation (i.e., the actual reason for the nonconformance). The types of deviations are as follows:		* '''Top Deviating''': this column shows the type of deviation (i.e., the actual reason for the nonconformance). The types of deviations are as follows:
	** '''Undesired event''': the event occurred in the eventlog, but it's not in the design model and thus it should not occur at all. This deviation is not shown in Snowflake models.		** '''Undesired event''': the event occurred in the eventlog, but it's not in the design model and thus it should not occur at all. This deviation is not shown in Snowflake models.

Ollvihe at 18:01, 1 June 2023

2023-06-01T18:01:37Z

← Older revision		Revision as of 18:01, 1 June 2023
Line 17:		Line 17:

	== Top Deviations (in-memory) / Deviating Flows (Snowflake) ==		== Top Deviations (in-memory) / Deviating Flows (Snowflake) ==
	This table shows the specific conformance ~~violation~~ reasons for the nonconforming cases. For the in-memory models, all ~~violations~~ are shown, and for the Snowflake models, only the flow related ~~violations~~ are shown. There are following columns:		This table shows the specific conformance deviation reasons for the nonconforming cases. For the in-memory models, all deviations are shown, and for the Snowflake models, only the flow related deviations are shown. There are following columns:
	* '''Top ~~Violations~~''': this column shows the type of ~~violation~~ (i.e., the actual reason for the nonconformance). The types of ~~violations~~ are as follows:		* '''Top Deviating''': this column shows the type of deviation (i.e., the actual reason for the nonconformance). The types of deviations are as follows:
	** '''Undesired event''': the event occurred in the eventlog, but it's not in the design model and thus it should not occur at all. This ~~violation~~ is not shown in Snowflake models.		** '''Undesired event''': the event occurred in the eventlog, but it's not in the design model and thus it should not occur at all. This deviation is not shown in Snowflake models.
	** '''<X> occurred directly after <Y>''': an event occurred in the wrong sequence in the eventlog, i.e. according to the design model, the event X should not occur right after event Y.		** '''<X> occurred directly after <Y>''': an event occurred in the wrong sequence in the eventlog, i.e. according to the design model, the event X should not occur right after event Y.
	** '''<X> is the starting event''': case starts with an event that is not allowed in the design model. This type of ~~violation~~ is reported when the first event in of the case can occur later in the process but not as the first event. If the event is not allowed at all in the process, the ~~violation~~ would be reported as ''undesired event''.		** '''<X> is the starting event''': case starts with an event that is not allowed in the design model. This type of deviation is reported when the first event in of the case can occur later in the process but not as the first event. If the event is not allowed at all in the process, the deviation would be reported as ''undesired event''.
	** '''<X> is the ending event''': case reaches its last event (thus far) in the eventlog, but according to the design model, the case should continue. Note that this "~~violation~~" may occur simply because the continuation events haven't yet occurred, and thus it's not a real ~~violation~~ in the process.		** '''<X> is the ending event''': case reaches its last event (thus far) in the eventlog, but according to the design model, the case should continue. Note that this "deviation" may occur simply because the continuation events haven't yet occurred, and thus it's not a real deviation in the process.
	* '''Cases''': Percentage of cases having the ~~violation~~.		* '''Cases''': Percentage of cases having the deviation.
	* '''Duration Impact''': Shows the impact the ~~violation~~ has on the case duration, i.e. the average duration of all cases compared with the average duration of the ~~violating~~ cases. For example, the Duration Impact might show that, on average, cases with the ~~violation~~ take 5 days longer to finish than on average.		* '''Duration Impact''': Shows the impact the deviation has on the case duration, i.e. the average duration of all cases compared with the average duration of the deviating cases. For example, the Duration Impact might show that, on average, cases with the deviation take 5 days longer to finish than on average.
	* '''Steps Impact''': Shows the impact the ~~violation~~ has on the number of events, i.e. the average number of events among all cases compared with the average number of events in the ~~violating~~ cases. For example, the Steps Impact might show that, on average, there are 1.5 events more in the cases with the ~~violation~~.		* '''Steps Impact''': Shows the impact the deviation has on the number of events, i.e. the average number of events among all cases compared with the average number of events in the deviating cases. For example, the Steps Impact might show that, on average, there are 1.5 events more in the cases with the deviation.

	== Undesired Events (Snowflake) ==		== Undesired Events (Snowflake) ==

Ollvihe: /* Show Root Causes for Violations */

2023-06-01T18:00:35Z

Show Root Causes for Violations

← Older revision		Revision as of 18:00, 1 June 2023
Line 40:		Line 40:
	Shows the most common variations in the process that are not conformant with the design model.		Shows the most common variations in the process that are not conformant with the design model.

	== Show Root Causes for ~~Violations~~ ==		== Show Root Causes for Deviations ==
	Clicking the '''Show Root Causes''' button opens a view showing the Root causes analysis listing case attribute values that correlate with conformance violations. You can go back to the previous violations view by clicking the '''Show Violations''' button.		Clicking the '''Show Root Causes''' button opens a view showing the Root causes analysis listing case attribute values that correlate with conformance violations. You can go back to the previous violations view by clicking the '''Show Violations''' button.

	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe: /* Conformance Flowchart */

2023-06-01T17:59:56Z

Conformance Flowchart

← Older revision		Revision as of 17:59, 1 June 2023
Line 31:		Line 31:

	== Conformance Flowchart ==		== Conformance Flowchart ==
	For ~~Snowflake~~, the flowchart highlights the deviating event types and flows with red color. The ~~violations~~ information is the same as in the [[#~~Top_Violations~~\|Top ~~Violations~~]] table with one exception: In the flowchart, for the ~~violating~~ event types also the incoming and outgoing flows are shown as ~~violations~~. These kind of ~~violating~~ flows are not listed in the ''Top ~~Violations~~'' table to make the table more readable because the listed undesired event already implies that the related flows are ~~violating~~.		For in-memory, the flowchart highlights the deviating event types and flows with red color. The deviations information is the same as in the [[#Top_Deviations\|Top Deviations]] table with one exception: In the flowchart, for the deviating event types also the incoming and outgoing flows are shown as deviations . These kind of deviating flows are not listed in the ''Top Deviations'' table to make the table more readable because the listed undesired event already implies that the related flows are deviating.

	In the flowchart, note that only the visible event types and flows may be shown as deviations, so there may be deviating event types and flows that are not shown due to the [[Process_Flowchart#Visibility_settings\|flowchart visibility settings]]. Note also that the conformance checking stops to the first ~~violating~~ flow while checking each case, and thus the checking might not detect correctly possible ~~violations~~ that are occurring after the first ~~violation~~. The first ~~violation~~ can be "skipped" by either filtering the model or changing the design model.		In the flowchart, note that only the visible event types and flows may be shown as deviations, so there may be deviating event types and flows that are not shown due to the [[Process_Flowchart#Visibility_settings\|flowchart visibility settings]]. Note also that the conformance checking stops to the first deviating flow while checking each case, and thus the checking might not detect correctly possible deviations that are occurring after the first deviation. The first deviation can be "skipped" by either filtering the model or changing the design model.

			For Snowflake, the Conformance Flowchart shows the deviating event types, but not deviating flows. Still, flows where the starting or ending event type is deviating, also the flow is shown as red.

	== Top Deviating Variations ==		== Top Deviating Variations ==

Ollvihe: /* Conformance Flowchart */

2023-06-01T17:57:34Z

Conformance Flowchart

← Older revision		Revision as of 17:57, 1 June 2023
Line 31:		Line 31:

	== Conformance Flowchart ==		== Conformance Flowchart ==
	~~The~~ flowchart highlights the deviating event types and flows with red color. The violations information is the same as in the [[#Top_Violations\|Top Violations]] table with one exception: In the flowchart, for the violating event types also the incoming and outgoing flows are shown as violations. These kind of violating flows are not listed in the ''Top Violations'' table to make the table more readable because the listed undesired event already implies that the related flows are violating.		For Snowflake, the flowchart highlights the deviating event types and flows with red color. The violations information is the same as in the [[#Top_Violations\|Top Violations]] table with one exception: In the flowchart, for the violating event types also the incoming and outgoing flows are shown as violations. These kind of violating flows are not listed in the ''Top Violations'' table to make the table more readable because the listed undesired event already implies that the related flows are violating.

	In the flowchart, note that only the visible event types and flows may be shown as ~~violations~~, so there may be ~~violating~~ event types and flows that are not shown due to the [[Process_Flowchart#Visibility_settings\|flowchart visibility settings]]. Note also that the conformance checking stops to the first violating flow while checking each case, and thus the checking might not detect correctly possible violations that are occurring after the first violation. The first violation can be "skipped" by either filtering the model or changing the design model.		In the flowchart, note that only the visible event types and flows may be shown as deviations, so there may be deviating event types and flows that are not shown due to the [[Process_Flowchart#Visibility_settings\|flowchart visibility settings]]. Note also that the conformance checking stops to the first violating flow while checking each case, and thus the checking might not detect correctly possible violations that are occurring after the first violation. The first violation can be "skipped" by either filtering the model or changing the design model.

	== Top Deviating Variations ==		== Top Deviating Variations ==

Ollvihe: /* Undesired Events (Snowflake) */

2023-06-01T17:55:45Z

Undesired Events (Snowflake)

← Older revision		Revision as of 17:55, 1 June 2023
Line 28:		Line 28:

	== Undesired Events (Snowflake) ==		== Undesired Events (Snowflake) ==
	~~The Undesired Events~~ table shows all event types that not ~~conformant~~ with the design model, i.e., they are event types appearing in the eventlog that ~~don't appear~~ in the design model at all. The table shows the ~~Duration~~ and ~~Steps~~ impact, similar to the Deviating Flows table.		This table shows all event types that not conforming with the design model, i.e., they are event types appearing in the eventlog that are not in the design model at all. The table shows the duration and steps impact, similar to the ''Deviating Flows'' table.

	== Conformance Flowchart ==		== Conformance Flowchart ==

Ollvihe: /* Top Deviations (in-memory) / Deviating Flows (Snowflake) */

2023-06-01T17:54:50Z

Top Deviations (in-memory) / Deviating Flows (Snowflake)

← Older revision		Revision as of 17:54, 1 June 2023
Line 26:		Line 26:
	* '''Duration Impact''': Shows the impact the violation has on the case duration, i.e. the average duration of all cases compared with the average duration of the violating cases. For example, the Duration Impact might show that, on average, cases with the violation take 5 days longer to finish than on average.		* '''Duration Impact''': Shows the impact the violation has on the case duration, i.e. the average duration of all cases compared with the average duration of the violating cases. For example, the Duration Impact might show that, on average, cases with the violation take 5 days longer to finish than on average.
	* '''Steps Impact''': Shows the impact the violation has on the number of events, i.e. the average number of events among all cases compared with the average number of events in the violating cases. For example, the Steps Impact might show that, on average, there are 1.5 events more in the cases with the violation.		* '''Steps Impact''': Shows the impact the violation has on the number of events, i.e. the average number of events among all cases compared with the average number of events in the violating cases. For example, the Steps Impact might show that, on average, there are 1.5 events more in the cases with the violation.
	~~Undesired Events (Snowflake)~~

			== Undesired Events (Snowflake) ==
	The Undesired Events table shows all event types that not conformant with the design model, i.e., they are event types appearing in the eventlog that don't appear in the design model at all. The table shows the Duration and Steps impact, similar to the Deviating Flows table.		The Undesired Events table shows all event types that not conformant with the design model, i.e., they are event types appearing in the eventlog that don't appear in the design model at all. The table shows the Duration and Steps impact, similar to the Deviating Flows table.

Ollvihe: /* Top Violating Variations */

2023-06-01T17:54:23Z

Top Violating Variations

← Older revision		Revision as of 17:54, 1 June 2023
Line 16:		Line 16:
	This chart shows the conforming cases count and total cases across time, which visualizes how the conformance rate has developed over time.		This chart shows the conforming cases count and total cases across time, which visualizes how the conformance rate has developed over time.

	== Top ~~Violations~~ ==		== Top Deviations (in-memory) / Deviating Flows (Snowflake) ==
	This table shows the specific conformance violation reasons for the nonconforming cases. For the in-memory models, all violations are shown, and for the Snowflake models, only the flow related violations are shown. There are following columns:		This table shows the specific conformance violation reasons for the nonconforming cases. For the in-memory models, all violations are shown, and for the Snowflake models, only the flow related violations are shown. There are following columns:
	* '''Top Violations''': this column shows the type of violation (i.e., the actual reason for the nonconformance). The types of violations are as follows:		* '''Top Violations''': this column shows the type of violation (i.e., the actual reason for the nonconformance). The types of violations are as follows:
Line 26:		Line 26:
	* '''Duration Impact''': Shows the impact the violation has on the case duration, i.e. the average duration of all cases compared with the average duration of the violating cases. For example, the Duration Impact might show that, on average, cases with the violation take 5 days longer to finish than on average.		* '''Duration Impact''': Shows the impact the violation has on the case duration, i.e. the average duration of all cases compared with the average duration of the violating cases. For example, the Duration Impact might show that, on average, cases with the violation take 5 days longer to finish than on average.
	* '''Steps Impact''': Shows the impact the violation has on the number of events, i.e. the average number of events among all cases compared with the average number of events in the violating cases. For example, the Steps Impact might show that, on average, there are 1.5 events more in the cases with the violation.		* '''Steps Impact''': Shows the impact the violation has on the number of events, i.e. the average number of events among all cases compared with the average number of events in the violating cases. For example, the Steps Impact might show that, on average, there are 1.5 events more in the cases with the violation.
			Undesired Events (Snowflake)

			The Undesired Events table shows all event types that not conformant with the design model, i.e., they are event types appearing in the eventlog that don't appear in the design model at all. The table shows the Duration and Steps impact, similar to the Deviating Flows table.

	== Conformance Flowchart ==		== Conformance Flowchart ==
	The flowchart highlights the ~~violating~~ event types and flows with red color. The violations information is the same as in the [[#Top_Violations\|Top Violations]] table with one exception: In the flowchart, for the violating event types also the incoming and outgoing flows are shown as violations. These kind of violating flows are not listed in the ''Top Violations'' table to make the table more readable because the listed undesired event already implies that the related flows are violating.		The flowchart highlights the deviating event types and flows with red color. The violations information is the same as in the [[#Top_Violations\|Top Violations]] table with one exception: In the flowchart, for the violating event types also the incoming and outgoing flows are shown as violations. These kind of violating flows are not listed in the ''Top Violations'' table to make the table more readable because the listed undesired event already implies that the related flows are violating.

	In the flowchart, note that only the visible event types and flows may be shown as violations, so there may be violating event types and flows that are not shown due to the [[Process_Flowchart#Visibility_settings\|flowchart visibility settings]]. Note also that the conformance checking stops to the first violating flow while checking each case, and thus the checking might not detect correctly possible violations that are occurring after the first violation. The first violation can be "skipped" by either filtering the model or changing the design model.		In the flowchart, note that only the visible event types and flows may be shown as violations, so there may be violating event types and flows that are not shown due to the [[Process_Flowchart#Visibility_settings\|flowchart visibility settings]]. Note also that the conformance checking stops to the first violating flow while checking each case, and thus the checking might not detect correctly possible violations that are occurring after the first violation. The first violation can be "skipped" by either filtering the model or changing the design model.

	== Top ~~Violating~~ Variations ==		== Top Deviating Variations ==
	Shows the most common variations in the process that ~~violate~~ the design model.		Shows the most common variations in the process that are not conformant with the design model.

	== Show Root Causes for Violations ==		== Show Root Causes for Violations ==

Ollvihe: /* Top Violations */

2023-05-08T12:39:29Z

Top Violations

← Older revision		Revision as of 12:39, 8 May 2023
Line 17:		Line 17:

	== Top Violations ==		== Top Violations ==
	This table shows violations ~~against~~ the ~~design model~~. There are following columns:		This table shows the specific conformance violation reasons for the nonconforming cases. For the in-memory models, all violations are shown, and for the Snowflake models, only the flow related violations are shown. There are following columns:
	* '''Top Violations''': this column shows the type of violation (i.e., the actual reason for the nonconformance). The types of violations are as follows:		* '''Top Violations''': this column shows the type of violation (i.e., the actual reason for the nonconformance). The types of violations are as follows:
	** '''Undesired event''': the event occurred in the eventlog, but it's not in the design model and thus it should not occur at all. This violation is not shown in Snowflake models.		** '''Undesired event''': the event occurred in the eventlog, but it's not in the design model and thus it should not occur at all. This violation is not shown in Snowflake models.

Ollvihe: /* Editing Design Model */

2023-04-18T22:23:55Z

Editing Design Model

← Older revision		Revision as of 22:23, 18 April 2023
Line 2:		Line 2:

	== Editing Design Model ==		== Editing Design Model ==
	The design model is the ~~set and order of events against which the data in the QPR ProcessAnalyzer model is tested. The design model is defined~~ using [https://www.omg.org/spec/BPMN/2.0/ BPMN 2.0] notation. The design model editor can be opened by clicking the '''Edit Design Model''' button. When editing the design model, only a subset of the BPMN elements are supported which are following: Start event, End event, Task, Gateway and Connector. Unsupported elements are not available in the tool palette.		The design model describes precisely how the process should go using [https://www.omg.org/spec/BPMN/2.0/ BPMN 2.0] notation. The design model editor can be opened by clicking the '''Edit Design Model''' button. When editing the design model, only a subset of the BPMN elements are supported which are following: Start event, End event, Task, Gateway and Connector. Unsupported elements are not available in the tool palette.

	It's recommended to create the design model automatically based on the data in the as-is model. To do this, select from the context menu either '''Auto-create tasks and flows''' or '''Auto-create tasks only''':		It's recommended to create the design model automatically based on the data in the as-is model. To do this, select from the context menu either '''Auto-create tasks and flows''' or '''Auto-create tasks only''':