Data preparation

To find solutions to your business challenges, it is crucially important to identify the required data correctly. There are two common approaches to process data identification:

  • Process-oriented data identification

    Define the beginning and end of your process and all tasks and events in between.

  • Business object-oriented data identification

    Identify business documents that are involved in the process - for examples orders or invoices - and follow the lifecycle of these documents.

When you have defined the scope of the data with one of the approaches, you can locate it by its IT footprint in the corresponding databases of your application landscape.

Transforming your data

After you have identified the data, you need to transform it to fit the structure Signavio Process Intelligence requires. The system requires two dimensions (data logs), which serve different purposes and should therefore be extracted separately.

  • Event log

    The event log lists the core properties of all events that occurred as part of the specified process.

  • Case attribute log

    The case attribute log lists the core properties each case (instance) of the specified process. These properties, like for example case creator, apply to a case in general, and are not dependent on specific events.

Data requirements

Below you will find a precise specification of how you should provide the event and case attribute logs so that Process Intelligence can import the data.

The event log needs to contain the following properties for each event it contains:

  • CaseId: The unique identifier of the case the event is assigned to.
  • EventName: The name of the event.
  • Timestamp: The exact date and time when the event occurred, in the format YYYY-MM-DDTHH:MM:SS.

The following table contains an example excerpt of an event log:

Event log
CaseId EventName Timestamp
100430031000112060012015 Create FI invoice by vendor 2014-11-20T00:00:00.000
100430031000112060012015 Post invoice in FI 2014-11-20T00:00:00.000
100430031000112060012015 Clear open item 2015-01-12T23:59:59.000

For each case, the case attribute log must contain the caseId property. It can list additional properties that provide more insight into the cases of the process. For each property with the exception of caseId, you need to specify a data type. The following data types are available:

  • TEXT, for example Invoice description
  • DOUBLE_PRECISION (number), for example 12.34
  • TIMESTAMP_WITH_TIME_ZONE, for example 2018-01-01T12:45:22. (Note that the name is misleading. The structure of the time stamp needs to be YYYY-MM-DDTHH:MM:SS (without time zone)),
  • CHOICE, for example any of the values DE, EN, FR.
  • CURRENCY, for example 5.21.
  • DURATION (in milliseconds), for example 268488000.

The following table contains an example excerpt of a case attribute log:

Case attribute log
CaseId Invoice due date (TIMESTAMP_WITH_TIME_ZONE) Invoice value (CURRENCY) Material group (CHOICE)
100430031000112060012015 2015-11-06T14:32:37.000 175.38 A001
100430031000112070012015 2015-06-10T06:45:38.000 0.41 -
100430031000112080012015 2015-06-19T14:48:50.000 0.20 -

You need to provide the data as two separate CSV files. The CSV’s value separator must be a semicolon (;).

Below you see an excerpt of an event log:

CaseId;EventName;Timestamp
100430031000112060012015;Create FI invoice by vendor;2014-11-20T00:00:00.000
100430031000112060012015;Post invoice in FI;2015-01-08T14:26:02.000
100430031000112060012015;Clear open item;2015-01-12T23:59:59.000

This is an excerpt of a case attribute log:

CaseId;invoice duedate (TIMESTAMP_WITH_TIME_ZONE);invoice value (CURRENCY);material group (CHOICE)
100430031000112060012015;2015-11-06T14:32:37.000;175.38;A001
100430031000112070012015;2015-06-10T06:45:38.000;0.41;
100430031000112080012015;2015-06-19T14:48:50.000;0.20;

Note that the data types are provided in parentheses after the property name.

Uploading data

Once your data is prepared, open the Process Intelligence application as described in Accessing Process Intelligence.

Then, click the Add business group button to create a new analysis area.

../_images/pi_add_business_group.png

Opening Process Intelligence

Business groups divide your workspaces into organizational units. Enter a name for the business group - for example Procurement and hit Enter.

Now, click ...add another process. Enter the process name and hit Enter.

Then, upload the event log and the case attribute log (‘process variables’).

Optionally, you can also reference a business process diagram from your Process Manager workspace and map the activities of the process diagram to the event IDs of the event log. This makes it possible to compare the documented (should) process to the current state (as-is) process.