Skip to main content

Migrating apps for use in Process Mining

Introduction​

This page describes how to migrate apps from Process Mining on-premises (standalone) to Process Mining Automation Suite. Process Mining on-premises (standalone) and Process Mining Automation Suite are built on a different technology stack. In Process Mining Automation Suite, both data transformations and dashboards are combined in a single process app. In Process Mining standalone, data transformations and dashboards are separated in a connector (.mvp) and an app (.mvp). Moving to the new technology stack requires the main Process Mining standalone artifacts, apps, and connectors, to be recreated in a single process app in Process Mining Automation Suite.

Legacy product versus Modern product

List requirements​

It is advised to assess which processes are to be recreated in the new Process Mining product. Not all process apps in Process Mining on-premises (standalone) might be equally valuable and worth the effort of recreating.

For the apps that are selected, assess which KPIs and dashboards are needed.

From the list of KPIs, create a list of data tables and fields, and logic that needs to be recreated.

Select App template​

In Process Mining, an app template contains a predefined set of dashboards and KPIs for process analysis that can be used as the starting point for creating your process apps. If available, an app template can include a built-in connector for a specific combination of a process and source system.

To start recreating an app in Process Mining, select the App Template that’s most applicable for the desired process (refer to App Templates).

The app templates in Process Mining contain dashboards to analyze a given process as well as the data transformations to load the data from a specific source system.

Process Mining on-premises standalone

App template

Purchase-to-Pay on SAP

SAP Purchase-to-Pay

Order-to-Cash on SAP

SAP Order-to-Cash

AppOne/TemplateOne

  • Specific process : If a specific app template is available for a use case, use that. E.g. Salesforce – Lead-to-Order.

  • Event log : If your input data is a single event log file.

  • Custom process : if your input data consists of multiple files.

note

Although the data models of the app templates in Process Mining are similar to the data models of the app in Process Mining on-premises (standalone), you may have to make small changes in the existing .mvp connector to adjust the data to the data model for the Process Mining process app.

Data transformations​

To recreate the data transformations of a Process Mining on-premises (standalone) .mvp connector and a a Process Mining on-premises (standalone) .mvp app, the transformations have to be rewritten in SQL.

Use the list of KPIs and data tables that were created earlier, to step-by-step add custom tables and fields to the data transformations in SQL.

Dashboards​

The dashboards can be recreated one-by-one using the Dashboard editor. Check out Creating a new app and Creating dashboards for more information.

note

Since Process Mining on-premises (standalone) has a different technology stack, there are differences in the types of dashboards that can be created, and the specific features to configure them. It might not be possible to recreate a dashboard exactly as it is in Process Mining on-premises (standalone).

Metrics​

Each custom dashboard might need additional metrics, or data fields. Be aware that some metrics can be defined directly in the Data manager, check out Data manager. However, some metrics might require adding additional fields in SQL. Check out Data transformations editor.