Navigation Menu

Installation Instructions

1. Download the deployment package and extract its contents to a temporary folder.
2. Log in to your QPR UI.
3. Switch to My Workspace and delete possible previous versions of the deployment package views.
4. Import the views from the temporary folder into your QPR UI.
5. Publish at least the QPR ProcessAnalyzer - Frontpage view.

Views in the Package

Frontpage

This view contains links to all the other views in the deployment package. It's advisable to publish this view, so all users have access to it.

Process Discovery

This is a plain QPR ProcessAnalyzer view for process discovery.

Conformance Analysis

This 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:

1. Open Profiling Case Analysis using the drop down menu.
2. 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.
3. 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.

Data Import

This view is used to import data into the QPR ProcessAnalyzer service (direct database import is not supported). Note that you need to have sufficient rights to import data to the QPR ProcessAnalyzer service in order to use this view.

Step 1: Imported File

You can choose whether to import:

• cases or case attributes
• events or event attributes
• .xes or .pacm file.

With cases or case attributes and events or event attributes, the data needs to be imported from .csv files. A .xes or a .pacm file will contain both case and event data.

Step 2: CSV File Format

When importing from a csv file, here you can define in what format the data is in the file:

• Column delimiter: Column delimiter is the character that separates data cells in a row. Usually the column delimiter is a semicolon or tab. It's possible to define any character by selecting the "other" option.
• Date format: Date format is used to interpret date values in the csv file. Default format is: "yyyy-MM-dd HH:mm:ss,fff", where dd = zero-padded day of the month, from 01 through 31; MM = zero-padded month, from 01 through 12; yyyy = year as a four-digit number; HH = zero padded hour, using a 24-hour clock from 00 to 23; mm = zero-padded minute, from 00 through 59; ss = second, from 00 through 59; fff = millisecond. More information about formatting: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings.
• Text qualifier: Text qualifier is the character used to enclose text (string) values. Sometimes csv files don't contain text qualifiers at all.
• Header row number: The row number (staring from 1) in the file that contains the headers of the data. Usually the first row contains the headers, but the file may start with rows that need to be skipped.

Step 3: Import Destination

There are following ways to import data:

• New model to an existing project: You need to select an existing project to which the new model is to be created. You also need to define name for the new model.
• New model to a new project: You need to define the name of the new project and new model. Note that you can't define different names for the new project and the new model.
• Existing model: You need to select the project and model to which the data is to be created. You can click the Open button to check the model that is currently selected.

KPI Analysis Tester

This view is an example of the KPI Analysis Tester.

Model Manager

This view is intended for use by an administrator. Using this view requires that the QPR UI installation and the QPR ProcessAnalyzer service it uses reside in the same domain. The view enables the administrator to control which QPR ProcessAnalyzer models are loaded in memory for in-memory processing at the service. It is advisable not to publish this view.

Deployment Package Versions

• QPR UI 2018.7: https://files.qpr.com/releases/PADeploymentPackage/QPRPADeploymentPackageV004.zip (latest)
• QPR UI 2018.6: https://files.qpr.com/releases/PADeploymentPackage/QPRPADeploymentPackageV003.zip
• QPR UI 2018.5: https://files.qpr.com/releases/PADeploymentPackage/QPRPADeploymentPackageV002.zip
• QPR UI 2018.4: https://files.qpr.com/releases/PADeploymentPackage/QPRPADeploymentPackageV001.zip

View Identifiers

Each view in the deployment package has an identifier which is used when creating links between views. The identifiers are as follows:

• Frontpage: QPRProcessAnalyzerFrontPage
• Process Discovery: QPRProcessAnalyzerProcessDiscovery
• Conformance Analysis: QPRProcessAnalyzerConformanceAnalysis
• Conformance Root Causes Analysis: QPRProcessAnalyzerConformanceRootCausesAnalysis
• Process Benchmarking: QPRProcessAnalyzerProcessBenchmarking
• ChartView: QPRProcessAnalyzerChartView
• Data Import: QPRProcessAnalyzerDataImport
• KPI Analysis Tester: QPRProcessAnalyzerKPIAnalysisTester
• Model Manager: QPRProcessAnalyzerModelManager