There are four ways to use Charts in QPR ProcessAnalyzer Process Discovery and Dashboards:
*Using default analysis elements in Process Discovery
*Using presets
*Creating your own ChartView analysis elements
*Creating custom KPIs with ExpressionLanguage

= Default analysis elements in Process Discovery =
In Process Discovery you can use the default analysis elements by browsing the header tabs on top of the ChartView. You can see more options by clicking on the left and right arrows. Each type of analysis is explained below.

[[File:ProcessDiscoveryAnalysisView1.png|450px]]
== Cases ==

[[File:Tabs 1cases.png|600px]]
*'''Case ID:''' The individual identifier assigned to a case.
*'''Case start:''' Time stamp of the first event of the case.
*'''Case end:''' Time stamp of the last event of the case.
*'''Case duration:''' End-to-end duration from the first event of the case to the last event of the case.
*'''Latest event:''' Last event in the chain of events of the case.
*'''Events:''' Count of event occurrences in the case.
*'''Event types:''' Count of event types in the case.

== Events ==

[[File:Tabs 2events.png|600px]]
*'''Case ID:''' The individual identifier assigned to a case.
*'''Event type:''' Name of the event.
*'''Event time:''' Time stamp of the event.
*'''Duration from case start:''' Duration between the event and the first event of the case.
*'''Duration from previous event:''' Duration between the event and the event preceeding it.
*'''Event order number:''' Sequence/index number of the event within the case.

== Event Types ==

[[File:Tabs 3eventtypes.png|600px]]
*'''Event type:''' Name of the event.
*'''Cases:''' Count of cases containing the event type.
*'''Events occured:''' Event count of the event type in all (filtered) cases.
*'''Incoming flows:''' Number of event types directly preceeding the event type within the selected cases.
*'''Outgoing flows:''' Number of event types directly following the event type within the selected cases.
*'''Events per case:''' Calculation rule: ''Events occurred / Cases''.

== Case Attribute profiling ==

[[File:Tabs 4caseattributes.png|600px]]

Case Attribute profiling visualizes the break down of the case count according to Case Attribute values. You can choose different Case Attributes to analyze by toggling the drop down menu. The Visualization defaults to bar chart which you can change from the "General" tab of the Chart Settings.

== Event Attribute Profiling ==

[[File:Tabs 5eventattributes.png|600px]]

Event Attribute profiling visualizes the break down of the event count according to Event Attribute values. You can choose different Event Attributes to analyze by toggling the drop down menu. The Visualization defaults to bar chart which you can change from the "General" tab of the Chart Settings.
== Case duration analysis ==

[[File:Tabs 6caseduration.png|600px]]

Case duration analysis breaks down the case count according to the duration of the cases within the (filtered) dataset. You can choose the granularity of the case durations from the dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.

== Event duration analysis ==

[[File:Tabs 7eventduration.png|600px]]

Event duration analysis breaks down the flow duration between two selected events. You can choose the analysis target by either:
*Selecting a flow from the flowchart.
*Toggling the "Start" and "End" drop down menus and selecting the desired events.

You can choose the granularity of the event durations from the "Time unit" dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Case counts ==

[[File:Tabs 8casecounts.png|600px]]

Case Counts analysis breaks down the Case Count based on the starting time of the (filtered) Cases in the data. You can choose the granularity of the time periods from the "Period" drop down menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Event counts ==
[[File:Tabs 9eventcounts.png|600px]]

Event Counts analysis breaks down the Event Count based on the starting time of the (filtered) Events in the data. You can choose the granularity of the time periods from the "Period" drop down menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Variations ==
[[File:Tabs 10variations.png|600px]]

Variations analysis aggregates Case Counts of identical process flows and sorts them in a descending order of Case Count. When Events in case > Event types in case, there is rework and/or looping in the process.
*'''Cases:''' Count of cases containing the specific process flow variation
*'''Average duration:''' Average duration of the specific process flow variation
*'''Events in case:''' Count of occurred events in the process flow variation
*'''Event types in case:''' Count of event types in the process flow variation
== Flows ==
[[File:Tabs 11flows.png|600px]]

Flows analysis aggregates all start event to end event flows and sorts them in a descending order of Average duration of the flows.
*'''Start:''' Name of the start event of the flow.
*'''End:''' Name of the end event of the flow.
*'''Average duration:''' Average duration of the flow.
*'''Median duration:''' Median duration of the flow.
*'''Cases:''' Count of cases which contain the flow.
*'''Occurrences:''' Count of flow occurrences.
*'''Looping:''' Looping percentage (repetition per case count). Calculation rule: ''(Occurrences / Cases - 1) * 100''.
*'''St.dev.:''' Standard deviation of the duration of the flow.
== Root causes ==
[[File:Tabs 12rootcauses2.png|600px]]

The idea of Root-cause analysis is to see whether some Subsets of data (=Case Attributes) correlate with any selected process behavior. Moreover, to provide insights where to focus business initiatives to maximize or minimize the selected process behavior.
For example: Order Price Change ratio is on average 17%. Is it 17% through all the case attributes such as Purchasing Country or is the Order Price Change ratio potentially 2% in Country X and 9% in Country Z. -> Best practices from Country X to be rolled into Country Z operations.

Header: Average of the analyzed feature in whole data model. Used as a benchmark for all the data subsets e.g. dimensioning with all case attribute values and seeing whether there are any subsets of data which have a higher or lower average.
2nd Column: Subset of data: Case Attribute + Concerned Case Attribute value e.g. Case Attribute: SO: Customer Country: United Kingdom
3rd Column: Case count within the Subset of data (see column #2), 24 700 cases

4th Column: Percentage of the cases having the analyzed feature in the concerned subset of data e.g. Case Attribute Value SO: Customer country: United Kingdom has 7.8% of orders having the analyzed features (Order Price Changes). Note. Clearly lower than global average 17%.

1st Column: Because the subset of data (e.g. concerned case attribute value for example SO: Customer country: United Kingdom) has a lower or a higher percentage of cases having the concerned feature compared to global average, it is responsible for X% of the whole featured effect.
In other words, how many cases too many/too little there are in this Data subset compared to global average. Finally, this number of cases is divided by the total number of cases having the analyzed feature to make it a “contribution percentage”. This means that global average is now 15% lower than it would be if United Kingdom was on a global average level 17% (contracts to 7.8% what it currently has).

== Clustering ==
[[File:Tabs 13clustering.png|600px]]

* '''Feature''' and '''Value''': These two columns list the case attribute and other values that are common to the cases in the cluster.
* '''Cluster Density %''': Share of cases having this feature value within the cluster (i.e. the number of cases having the value shown on the row in this particular cluster divided by the number of cases in the cluster * 100).
* '''Total Density %''': Share of cases having this feature value in the whole data set (i.e. the total number of cases having the value shown on the row divided by the total number of cases * 100).
* '''Contribution %''': Amount of cases that can be explained to belong to this cluster because of this feature value. The scale is such that 0% means that the feature value isn't specific to this cluster and 100% means that all cases belonging to this cluster can be explained by this feature value.

= Using presets =
[[File:ProcessDiscoveryAnalysisView2.png|right|450px]]You can expand your selection of analyses to 50+ pre-made presets. To open the presets you need to:
*Click on the ChartView area
*Click on the cog on the top-right corner to open the Chart Settings
*Select you preferred analysis from the use cases in the "Presets" tab

= Creating your own ChartView analysis elements =
To create your own customized analysis views you can toggle the values directly in Chart Settings. Most of the time you can understand "Dimensions" as the X-axis of the chart and "Measures" as the Y-axis of the chart. To get started please see [[QPR ProcessAnalyzer Chart]] or reach out to QPR staff for advice. In order to avoid any unexpected errors it is adviced to start from a blank ChartView by clicking "Create New" under the "Presets" tab.
= Creating custom KPIs with ExpressionLanguage =
For more complicated calculations which cannot be done with standard configuration options you need to use ExpressionLanguage code. ExpressionLanguage is a JSON based QPR language that is used for building KPIs in QPR ProcessAnalyzer. To get started please see [[QPR ProcessAnalyzer Expressions]] or reach out to QPR staff for advice.

2020-08-27T14:27:05Z

OllKomu:

There are four ways to use the Process Discovery Analysis View (right side view)
*Using default analysis elements from the header tabs
*Using presets
*Creating your own ChartView analysis elements
*Creating custom KPIs with ExpressionLanguage

= Default analysis elements from the header tabs =
You can use the default analysis elements by browsing the header tabs on top of the ChartView. You can see more options by clicking on the left and right arrows. Each type of analysis is explained below.

[[File:ProcessDiscoveryAnalysisView1.png|450px]]
== Cases ==

[[File:Tabs 1cases.png|600px]]
*'''Case ID:''' The individual identifier assigned to a case.
*'''Case start:''' Time stamp of the first event of the case.
*'''Case end:''' Time stamp of the last event of the case.
*'''Case duration:''' End-to-end duration from the first event of the case to the last event of the case.
*'''Latest event:''' Last event in the chain of events of the case.
*'''Events:''' Count of event occurrences in the case.
*'''Event types:''' Count of event types in the case.

== Events ==
*'''Case ID:''' The individual identifier assigned to a case.
*'''Event type:''' Name of the event.
*'''Event time:''' Time stamp of the event.
*'''Duration from case start:''' Duration between the event and the first event of the case.
*'''Duration from previous event:''' Duration between the event and the event preceeding it.
*'''Event order number:''' Sequence/index number of the event within the case.
== Event Types ==
*'''Event type:''' Name of the event.
*'''Cases:''' Count of cases containing the event type.
*'''Events occured:''' Event count of the event type in all (filtered) cases.
*'''Incoming flows:''' Number of event types directly preceeding the event type within the selected cases.
*'''Outgoing flows:''' Number of event types directly following the event type within the selected cases.
*'''Events per case:''' Calculation rule: ''Events occurred / Cases''.
== Case Attribute profiling ==
Case Attribute profiling visualizes the break down of the case count according to Case Attribute values. You can choose different Case Attributes to analyze by toggling the drop down menu. The Visualization defaults to bar chart which you can change from the "General" tab of the Chart Settings.
== Event Attribute Profiling ==
Event Attribute profiling visualizes the break down of the event count according to Event Attribute values. You can choose different Event Attributes to analyze by toggling the drop down menu. The Visualization defaults to bar chart which you can change from the "General" tab of the Chart Settings.
== Case duration analysis ==
Case duration analysis breaks down the case count according to the duration of the cases within the (filtered) dataset. You can choose the granularity of the case durations from the dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Event duration analysis ==
Event duration analysis breaks down the flow duration between two selected events. You can choose the analysis target by either:
*Selecting a flow from the flowchart.
*Toggling the "Start" and "End" drop down menus and selecting the desired events.

You can choose the granularity of the event durations from the "Time unit" dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Case counts ==
Case Counts analysis breaks down the Case Count based on the starting time of the (filtered) Cases in the data. You can choose the granularity of the time periods from the "Period" drop down menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Event counts ==
Event Counts analysis breaks down the Event Count based on the starting time of the (filtered) Events in the data. You can choose the granularity of the time periods from the "Period" drop down menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Variations ==
Variations analysis aggregates Case Counts of identical process flows and sorts them in a descending order of Case Count. When Events in case > Event types in case, there is rework and/or looping in the process.
*'''Cases:''' Count of cases containing the specific process flow variation
*'''Average duration:''' Average duration of the specific process flow variation
*'''Events in case:''' Count of occurred events in the process flow variation
*'''Event types in case:''' Count of event types in the process flow variation
== Flows ==
Flows analysis aggregates all start event to end event flows and sorts them in a descending order of Average duration of the flows.
*'''Start:''' Name of the start event of the flow.
*'''End:''' Name of the end event of the flow.
*'''Average duration:''' Average duration of the flow.
*'''Median duration:''' Median duration of the flow.
*'''Cases:''' Count of cases which contain the flow.
*'''Occurrences:''' Count of flow occurrences.
*'''Looping:''' Looping percentage (repetition per case count). Calculation rule: ''(Occurrences / Cases - 1) * 100''.
*'''St.dev.:''' Duration standard deviation of the flow.
== Root causes ==
To be updated
== Clustering ==
To be updated

= Using presets =
[[File:ProcessDiscoveryAnalysisView2.png|right|450px]]You can expand your selection of analyses to 50+ pre-made presets. To open the presets you need to:
*Click on the ChartView area
*Click on the cog on the top-right corner to open the Chart Settings
*Select you preferred analysis from the use cases in the "Presets" tab

= Creating your own ChartView analysis elements =
To create your own customized analysis views you can toggle the values directly in Chart Settings. Most of the time you can understand "Dimensions" as the X-axis of the chart and "Measures" as the Y-axis of the chart. To get started please see [[QPR ProcessAnalyzer Chart]] or reach out to QPR staff for advice. In order to avoid any unexpected errors it is adviced to start from a blank ChartView by clicking "Create New" under the "Presets" tab.
= Creating custom KPIs with ExpressionLanguage =
For more complicated calculations which cannot be done with standard configuration options you need to use ExpressionLanguage code. ExpressionLanguage is a JSON based QPR language that is used for building KPIs in QPR ProcessAnalyzer. To get started please see [[QPR ProcessAnalyzer Expressions]] or reach out to QPR staff for advice.

Process Discovery Analysis View

2020-08-27T14:25:21Z

OllKomu: /* Cases */

There are four ways to use the Process Discovery Analysis View (right side view)
*Using default analysis elements from the header tabs
*Using presets
*Creating your own ChartView analysis elements
*Creating custom KPIs with ExpressionLanguage

= Default analysis elements from the header tabs =
You can use the default analysis elements by browsing the header tabs on top of the ChartView. You can see more options by clicking on the left and right arrows. Each type of analysis is explained below.

[[File:ProcessDiscoveryAnalysisView1.png|450px]]
== Cases ==

[[File:Tabs 1cases.png|600px|right]]

*'''Case ID:''' The individual identifier assigned to a case.
*'''Case start:''' Time stamp of the first event of the case.
*'''Case end:''' Time stamp of the last event of the case.
*'''Case duration:''' End-to-end duration from the first event of the case to the last event of the case.
*'''Latest event:''' Last event in the chain of events of the case.
*'''Events:''' Count of event occurrences in the case.
*'''Event types:''' Count of event types in the case.

== Events ==
*'''Case ID:''' The individual identifier assigned to a case.
*'''Event type:''' Name of the event.
*'''Event time:''' Time stamp of the event.
*'''Duration from case start:''' Duration between the event and the first event of the case.
*'''Duration from previous event:''' Duration between the event and the event preceeding it.
*'''Event order number:''' Sequence/index number of the event within the case.
== Event Types ==
*'''Event type:''' Name of the event.
*'''Cases:''' Count of cases containing the event type.
*'''Events occured:''' Event count of the event type in all (filtered) cases.
*'''Incoming flows:''' Number of event types directly preceeding the event type within the selected cases.
*'''Outgoing flows:''' Number of event types directly following the event type within the selected cases.
*'''Events per case:''' Calculation rule: ''Events occurred / Cases''.
== Case Attribute profiling ==
Case Attribute profiling visualizes the break down of the case count according to Case Attribute values. You can choose different Case Attributes to analyze by toggling the drop down menu. The Visualization defaults to bar chart which you can change from the "General" tab of the Chart Settings.
== Event Attribute Profiling ==
Event Attribute profiling visualizes the break down of the event count according to Event Attribute values. You can choose different Event Attributes to analyze by toggling the drop down menu. The Visualization defaults to bar chart which you can change from the "General" tab of the Chart Settings.
== Case duration analysis ==
Case duration analysis breaks down the case count according to the duration of the cases within the (filtered) dataset. You can choose the granularity of the case durations from the dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Event duration analysis ==
Event duration analysis breaks down the flow duration between two selected events. You can choose the analysis target by either:
*Selecting a flow from the flowchart.
*Toggling the "Start" and "End" drop down menus and selecting the desired events.

You can choose the granularity of the event durations from the "Time unit" dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Case counts ==
Case Counts analysis breaks down the Case Count based on the starting time of the (filtered) Cases in the data. You can choose the granularity of the time periods from the "Period" drop down menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Event counts ==
Event Counts analysis breaks down the Event Count based on the starting time of the (filtered) Events in the data. You can choose the granularity of the time periods from the "Period" drop down menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.
== Variations ==
Variations analysis aggregates Case Counts of identical process flows and sorts them in a descending order of Case Count. When Events in case > Event types in case, there is rework and/or looping in the process.
*'''Cases:''' Count of cases containing the specific process flow variation
*'''Average duration:''' Average duration of the specific process flow variation
*'''Events in case:''' Count of occurred events in the process flow variation
*'''Event types in case:''' Count of event types in the process flow variation
== Flows ==
Flows analysis aggregates all start event to end event flows and sorts them in a descending order of Average duration of the flows.
*'''Start:''' Name of the start event of the flow.
*'''End:''' Name of the end event of the flow.
*'''Average duration:''' Average duration of the flow.
*'''Median duration:''' Median duration of the flow.
*'''Cases:''' Count of cases which contain the flow.
*'''Occurrences:''' Count of flow occurrences.
*'''Looping:''' Looping percentage (repetition per case count). Calculation rule: ''(Occurrences / Cases - 1) * 100''.
*'''St.dev.:''' Duration standard deviation of the flow.
== Root causes ==
To be updated
== Clustering ==
To be updated

= Using presets =
[[File:ProcessDiscoveryAnalysisView2.png|right|450px]]You can expand your selection of analyses to 50+ pre-made presets. To open the presets you need to:
*Click on the ChartView area
*Click on the cog on the top-right corner to open the Chart Settings
*Select you preferred analysis from the use cases in the "Presets" tab

= Creating your own ChartView analysis elements =
To create your own customized analysis views you can toggle the values directly in Chart Settings. Most of the time you can understand "Dimensions" as the X-axis of the chart and "Measures" as the Y-axis of the chart. To get started please see [[QPR ProcessAnalyzer Chart]] or reach out to QPR staff for advice. In order to avoid any unexpected errors it is adviced to start from a blank ChartView by clicking "Create New" under the "Presets" tab.
= Creating custom KPIs with ExpressionLanguage =
For more complicated calculations which cannot be done with standard configuration options you need to use ExpressionLanguage code. ExpressionLanguage is a JSON based QPR language that is used for building KPIs in QPR ProcessAnalyzer. To get started please see [[QPR ProcessAnalyzer Expressions]] or reach out to QPR staff for advice.

2019-06-07T09:24:15Z

OllKomu:

Calculated attributes enable to create case and event attributes using an expression (calculation formula) based on data in the QPR ProcessAnalyzer model.

== Introduction and Usecases==
Data to '''case attributes''' and '''event attributes''' can be originated as follows:
* '''importing''' them into QPR ProcessAnalyzer from a source system, csv file etc.
* '''calculating''' attribute values when the model is loaded using an [[QPR ProcessAnalyzer Expressions|expression]].

Calculated attributes have following use cases:
* Conversions: If an imported attribute data is not in a suitable format, the data can be overridden by defining a calculated attribute with the same name. The calculated attribute expression performs conversions for the data.
* Aggregations: It's possible to aggregate e.g. event level information to case level using a calculated case attribute.
* Performance: If there is an expression to aggregate event level information to a case level, the aggregation can be done already in the model loading using a calculated case attribute for better performance.

== Functioning Principle ==
Calculated attributes work as follows:
* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and influence analyses.
* Calculated attributes are calculated when the model is loaded, and thus calculated attribute values don't change after the model loading during the time the model is in the memory. If attributes need to be calculated again, the model needs to be reloaded.
* Calculated attribute values are stored into the memory like the imported attributes, meaning the model requires more memory, the more there are calculated attributes.
* For calculated case attributes, the expression is evaluated in each case's context, and for calculated event attributes, for each event's context. It's thus possible to access the entire model data in the expressions, such as variations, event types, flow and flow occurrences.
* Calculated event attributes are processed before calculated case attributes, so it's possible to use calculated event attributes in calculated case attributes expressions. Also, calculated case and event attributes are processed in the order they are defined, so it's possible to use an earlier defined calculated attribute in expressions of later attributes.
* Calculated attribute will replace an imported attribute, if there is an imported attribute with the same name. Note that it's not possible to override event timestamp, event type name or case id.
* If there is an error in the calculated attribute expression, the model loading fails, and the error needs to be corrected before the model can be used.

Calculated case and event attributes are configured to the model JSON settings are follows:
{| class="wikitable"
!'''Property'''
! '''Description'''
|-
||
CaseAttributes
||
Array of calculated case attributes with the following properties:
* '''name''': Calculated attribute name. There are no restrictions for the attribute names, but avoid names starting or ending with spaces to avoid confusion.
*'''expression''': Expression to calculate the calculated attribute. The expression is calculated in the case's or event's context. Only when an expression has been defined, the attribute is a calculated attribute.
|-
||
EventAttributes
||
Calculated event attributes are defined using the same structure as calculated case attributes.
|}

== Examples ==
Example 1: One calculated case attribute:
<pre>
{
"CaseAttributes": [
{
"name": "Cost",
"expression": "Cost * 1.5"
}
]
}
</pre>

Example 2: Two calculated event attributes:
<pre>
{
"EventAttributes": [
{
"name": "Event Month",
"expression": "Timestamp.Truncate(\"month\")"
},
{
"name": "Duration to Next Event",
"expression": "If(IsNull(_.NextInCase), null, (_.NextInCase.Timestamp-_.Timestamp))"
}
]
}
</pre>

Example 3: Several calculated case and event attributes:
<pre>
{
"CaseAttributes": [
{
"name": "myBooleanAttribute1",
"expression": "CURRENCYCODE == \"RUB\""
},
{
"name": "Combined status",
"expression": "PurchaseStatus+ \" \" + PurchaseType"
},
{
"name": "Repeated Events Count",
"expression": "Count(_.Events)-Count(Distinct(_.Events.Type))"
},
{
"name": "Duration between \"Invoice Sent\" and \"Payment Received\"",
"expression": "if(Count(_.EventsByType(\"Invoice Sent\")) == 0 || Count(_.EventsByType(\"Purchase Order Line Created\")) == 0, null, (GetAtReverse(0,_.EventsByType([\"Invoice Sent\", \"Payment Received\"])).Timestamp-GetAt(0,_.EventsByType([\"Invoice Sent\", \"Payment Received\"])).Timestamp))"
}
],
"EventAttributes": [
{
"name": "Event type occurrence number",
"expression": "Let(\"name\", _.Typename);Count(_.Recurse(_.PreviousInCase).Where(_.Typename==name))"
}
]
}
</pre>

Example 4: Segregation of duties:
<pre>
{
"CaseAttributes": [
{
"name": "KPI_SegregationOfDuties",
"expression":
"If(Count(
Intersect(
_.EventsByType(\"Purchase Order Created\").Attribute(\"User\"),
_.EventsByType(\"Purchase Order Approved\").Attribute(\"User\")).
Where(!Isnull(_) && _!=\"\"))>0, \"False\", \"True\") "
}
]
}</pre>

[[Category: QPR ProcessAnalyzer]]

QPR ProcessAnalyzer Deployment Package installs QPR ProcessAnalyzer UI to QPR UI.

== Installing Deployment Package ==
<div class="downloadButton" style="width:300px;float:right;margin:15px 20px 0px 30px;">[[QPR_Product_Downloads#QPR_ProcessAnalyzer_Deployment_Package|Download Deployment Package<br />for QPR ProcessAnalyzer]]</div>

# Download the deployment package (link on the right) and extract its contents to a temporary folder.
# In QPR UI, delete the possible previous versions of the QPR ProcessAnalyzer Deployment Package views. If the views have been ''published'', to need to ''unpublish'' and ''unlock'' the views to be able to delete them.
# Go to the '''My Workspace''' screen, import all the views (.qprmdb files) from your temporary folder.
# In the My Workspace screen, open the '''QPR ProcessAnalyzer''' view, click the menu on top right (three dots), click '''Show Header''', from the appearing header click '''File''', click '''Lock views and panels''', click '''File''' again, click '''Publish view'''.
# It's recommended to set the deployment package home page as the [[QPR_UI_System_Settings#Other_settings|default view]] in QPR UI (DEFAULT_VIEW_PATH setting with value "/QPRProcessAnalyzerHome").

== Deployment Package Contents ==
This chapter introduces all the views that are in the deployment package. Note that the deployment packages manipulates QPR UI header by hiding the Help and Selections buttons.

=== Home (QPR ProcessAnalyzer) ===
The Home page contains buttons to open all views in the deployment package. Note that the view name of the Home page is ''QPR ProcessAnalyzer''.

=== Process Discovery ===
This [[QPR_ProcessAnalyzer_Presentation_Object_(PAPO)|QPR ProcessAnalyzer]] view is for analysts to discover the process.

=== Conformance Analysis ===
The [[QPR ProcessAnalyzer - Conformance Analysis View|Conformance Analysis View]] incorporates the [[Conformance Checking in QPR ProcessAnalyzer]] capability of QPR ProcessAnalyzer. There are two views in the conformance analysis: the other shows the nonconformance reasons, and the other shows possible root causes for the nonconformance using the Influence Analysis for Case Attributes.

=== Process Benchmarking ===
Process Benchmarking can be used to compare process flows e.g. between two selected case attribute values. The view works as follows:
# Open Profiling Case Analysis using the drop down menu.
# For the compared case attribute values, create a filter in the left side view and another filter in the right side view for another attribute value.
# Go back to the flowchart view using the drop down menu. Now you can see two flowcharts to make the benchmarking.

=== ChartView ===
The ChartView allows the creation of customized charts to answer specific business needs, with measures and dimensions the user has selected. If you edit this view, make sure that the ChartView panel is placed on top of the QPR ProcessAnalyzer panel (you can do this by having the ChartView panel the last panel that you have moved), so that the BPMN editor is shown correctly.

=== Clustering Analysis ===
The [[QPR_ProcessAnalyzer_-_Clustering_Analysis_View|Clustering Analysis View]] analyzes though the process mining data, and divides cases into similar groups based on case attributes and occurred types of events. Use it to get a deep understanding of the analyzed process mining data and also to validate the data.

=== Data Import ===
Use this view to import models and datatables into QPR ProcessAnalyzer from files. Models can be imported from .csv, .pacm and .xes files and datatables from .csv files. For details, see [[Importing Data to QPR ProcessAnalyzer]].

=== KPI Expressions Tester ===
This view is for testing QPR ProcessAnalyzer expressions, e.g. before using the expressions in the dashboards. The expressions are written in the left side using a JSON format. When the '''Run KPI Expression''' button is clicked, the defined query is run and results appear to a table in the right side. Details of the JSON format can be found in [[QPR_ProcessAnalyzer_Expression_Analysis|QPR ProcessAnalyzer Expression Analysis]].

=== Model Manager ===
Model Manager is intended for administrators to see a list of all models in the system and manage their memory loading status. When selecting one or several models (while Ctrl key pressed) and clicking the right mouse button, a popup menu appears containing functions to load models into memory and drop them from the memory. It's also possible to export models in the .pacm format.

More columns can be added to the table by clicking the '''Columns''' button in the top right and clicking checkboxes for the additional columns. Note that the new columns appear to the right and they can be seen by scrolling the table to the right.

The models list can be sorted by any column by clicking the column header. Visible models can also be filtered by clicking the filter icon next to the column header.

Functionalities available in the context menu:
* '''Refresh View''': The view contents is reloaded from the server to get the latest status of the models.
* '''View Model''': The model is opened in the Process Discovery view. Note that if the model loading takes much time, it might be better to use the ''Load Model'' function first, because that loads the model in background.
* '''Load Model''': The selected model(s) are loaded into the memory.
* '''Drop Model''': The selected model(s) are dropped from the memory to free memory resources.
* '''Reload Model''': The selected model(s) are dropped from the memory and loaded again into the memory. Use the reloading to get the latest model data, e.g. when new data is loaded into the model.
* '''Export as .pacm''': Export the model as a .pacm file. The .pacm file can be imported into another QPR ProcessAnalyzer environment.

__NOTOC__

[[Category: QPR ProcessAnalyzer]]
[[Category: Deployment Packages]]
[[Category: QPR UI]]

QPR ProcessAnalyzer Deployment Package installs QPR ProcessAnalyzer UI to QPR UI.

== Installing Deployment Package ==
<div class="downloadButton" style="width:300px;float:right;margin:15px 20px 0px 30px;">[[QPR_Product_Downloads#QPR_ProcessAnalyzer_Deployment_Package|Download Deployment Package<br />for QPR ProcessAnalyzer]]</div>

# Download the deployment package (link on the right) and extract its contents to a temporary folder.
# In QPR UI, delete the possible previous versions of the QPR ProcessAnalyzer Deployment Package views. If the views have been ''published'', to need to ''unpublish'' and ''unlock'' the views to be able to delete them.
# Go to the '''My Workspace''' screen, import all the views (.qprmdb files) from your temporary folder.
# In the My Workspace screen, open the '''QPR ProcessAnalyzer''' view, click the menu on top right (three dots), click '''Show Header''', from the appearing header click '''File''', click '''Lock views and panels''', click '''File''' again, click '''Publish view'''.
# It's recommended to set the deployment package home page (identifier: "QPRProcessAnalyzerHome") as the [[QPR_UI_System_Settings#Other_settings|default view]] in QPR UI (see the DEFAULT_VIEW_PATH setting).

== Deployment Package Contents ==
This chapter introduces all the views that are in the deployment package. Note that the deployment packages manipulates QPR UI header by hiding the Help and Selections buttons.

=== Home (QPR ProcessAnalyzer) ===
The Home page contains buttons to open all views in the deployment package. Note that the view name of the Home page is ''QPR ProcessAnalyzer''.

=== Process Discovery ===
This [[QPR_ProcessAnalyzer_Presentation_Object_(PAPO)|QPR ProcessAnalyzer]] view is for analysts to discover the process.

=== Conformance Analysis ===
The [[QPR ProcessAnalyzer - Conformance Analysis View|Conformance Analysis View]] incorporates the [[Conformance Checking in QPR ProcessAnalyzer]] capability of QPR ProcessAnalyzer. There are two views in the conformance analysis: the other shows the nonconformance reasons, and the other shows possible root causes for the nonconformance using the Influence Analysis for Case Attributes.

=== Process Benchmarking ===
Process Benchmarking can be used to compare process flows e.g. between two selected case attribute values. The view works as follows:
# Open Profiling Case Analysis using the drop down menu.
# For the compared case attribute values, create a filter in the left side view and another filter in the right side view for another attribute value.
# Go back to the flowchart view using the drop down menu. Now you can see two flowcharts to make the benchmarking.

=== ChartView ===
The ChartView allows the creation of customized charts to answer specific business needs, with measures and dimensions the user has selected. If you edit this view, make sure that the ChartView panel is placed on top of the QPR ProcessAnalyzer panel (you can do this by having the ChartView panel the last panel that you have moved), so that the BPMN editor is shown correctly.

=== Clustering Analysis ===
The [[QPR_ProcessAnalyzer_-_Clustering_Analysis_View|Clustering Analysis View]] analyzes though the process mining data, and divides cases into similar groups based on case attributes and occurred types of events. Use it to get a deep understanding of the analyzed process mining data and also to validate the data.

=== Data Import ===
Use this view to import models and datatables into QPR ProcessAnalyzer from files. Models can be imported from .csv, .pacm and .xes files and datatables from .csv files. For details, see [[Importing Data to QPR ProcessAnalyzer]].

=== KPI Expressions Tester ===
This view is for testing QPR ProcessAnalyzer expressions, e.g. before using the expressions in the dashboards. The expressions are written in the left side using a JSON format. When the '''Run KPI Expression''' button is clicked, the defined query is run and results appear to a table in the right side. Details of the JSON format can be found in [[QPR_ProcessAnalyzer_Expression_Analysis|QPR ProcessAnalyzer Expression Analysis]].

=== Model Manager ===
Model Manager is intended for administrators to see a list of all models in the system and manage their memory loading status. When selecting one or several models (while Ctrl key pressed) and clicking the right mouse button, a popup menu appears containing functions to load models into memory and drop them from the memory. It's also possible to export models in the .pacm format.

More columns can be added to the table by clicking the '''Columns''' button in the top right and clicking checkboxes for the additional columns. Note that the new columns appear to the right and they can be seen by scrolling the table to the right.

The models list can be sorted by any column by clicking the column header. Visible models can also be filtered by clicking the filter icon next to the column header.

Functionalities available in the context menu:
* '''Refresh View''': The view contents is reloaded from the server to get the latest status of the models.
* '''View Model''': The model is opened in the Process Discovery view. Note that if the model loading takes much time, it might be better to use the ''Load Model'' function first, because that loads the model in background.
* '''Load Model''': The selected model(s) are loaded into the memory.
* '''Drop Model''': The selected model(s) are dropped from the memory to free memory resources.
* '''Reload Model''': The selected model(s) are dropped from the memory and loaded again into the memory. Use the reloading to get the latest model data, e.g. when new data is loaded into the model.
* '''Export as .pacm''': Export the model as a .pacm file. The .pacm file can be imported into another QPR ProcessAnalyzer environment.

__NOTOC__

[[Category: QPR ProcessAnalyzer]]
[[Category: Deployment Packages]]
[[Category: QPR UI]]

QPR ProcessAnalyzer Wiki - User contributions [en]

QPR ProcessAnalyzer Chart

QPR ProcessAnalyzer KPI Card

QPR ProcessAnalyzer Graph Charts

QPR ProcessAnalyzer Table

QPR ProcessAnalyzer Table

QPR ProcessAnalyzer Table

Chart Basics

Chart Basics

Chart Basics

Chart Basics

Chart Basics

Chart Basics

File:Tabs 12rootcauses2.png

Chart Basics

Process Discovery Analysis View

Process Discovery Analysis View

File:Tabs 13clustering.png

File:Tabs 12rootcauses.png

File:Tabs 11flows.png

File:Tabs 10variations.png

File:Tabs 9eventcounts.png

File:Tabs 8casecounts.png

File:Tabs 7eventduration.png

File:Tabs 6caseduration.png

File:Tabs 5eventattributes.png

File:Tabs 4caseattributes.png

File:Tabs 3eventtypes.png

File:Tabs 2events.png

Process Discovery Analysis View

Process Discovery Analysis View

File:Tabs 1cases.png

QPR ProcessAnalyzer Chart

QPR ProcessAnalyzer Chart

QPR ProcessAnalyzer Chart

Sample Eventlog Files

Importing Data to QPR ProcessAnalyzer

Importing Data to QPR ProcessAnalyzer

Importing Data to QPR ProcessAnalyzer

QPR ProcessAnalyzer System Requirements

QPR ProcessAnalyzer System Requirements

Calculated Attributes in QPR ProcessAnalyzer

Navigation Menu

Navigation Menu