Uploading data

Data identification

To find solutions to your business challenges, it is vital 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.

Once you have defined the scope of the data with one of the approaches, you can extract the data from the corresponding databases of your application landscape.

Data log types

There are two types of 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. The event log is necessary for a process investigation.

  • Case attribute log

    The case attribute log lists the core properties for 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. The case attribute log is optional for a process investigation.

Data requirements

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

  • Case ID: The unique identifier of the case the event is assigned to. For event logs, this ID may appear repeatedly, it is possible to have multiple events per case ID.
  • Activity: The name of the event (for example Invoice received).
  • End Timestamp: The exact date and time when the event was finished. The timestamp format must be the same for all timestamps in a column.

Note

In each of the three mandatory columns, every cell must contain a value in the expected data format, otherwise the import will fail.

The following table shows an example of an event log:

Event log
Case ID Activity End 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

In addition to the three required columns, the event log may have additional attribute columns. Unlike attributes in the case attribute log, these additional attributes are only associated with one event, not the complete case.

These columns may contain empty cells, but all cells of one attribute column must have the same data format or the import will fail.

The case attribute log can list additional properties that provide more details about cases in a process. This log must also contain the Case ID column. Here every row has a unique case ID, because the information in the other columns is related to a specific case.

Like for the event log, every cell in the case ID column must contain a value in the expected data format, otherwise the import will fail. The remaining columns may contain empty cells, but all entries in one attribute column must have the same data format.

The data is checked automatically for empty cells and unexpected formats.

../_images/data_quality.png

The following table shows an example of a case attribute log:

Case attribute log
Case ID Invoice due date Invoice value Material group
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 -

Each log type needs to be uploaded as a separate file. If you provide the data as a CSV file, the CSV’s delimiter can be defined.

Below you see an excerpt of an event log:

Case ID;Activity;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:

Case ID;invoice duedate;invoice value;material group
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;

Creating your process

You always upload data to a specific process.

  • If you have not previously created a process in Signavio Process Intelligence, click the Upload new process data button.
  • If you already have existing processes, but want to upload data for a new process, click the New process button in the upper right-hand corner of the All processes screen.
  • If you want to upload new data for an existing process, select the process from your process list on the All processes screen and click Process settings in the upper left-hand corner of the navigation menu.

When you’re creating a new process, you’re prompted to name this process. Use a name related to the business process the data originates from (i.e. “Procure-To-Pay”).

Next, you will see the Process settings page. Here you can select the files you want to upload.

Select the files to be imported by dragging and dropping them to the import area or by clicking browse.

Note

When using zip files, each zip file may only contain one file.

Defining data types for your data file

Next you need to define the data types for the data you want to upload.

../_images/select_columns.png

For columns containing timestamps, you can either select a matching timestamp format from the drop down menu, or specify your format in the text field above the dropdown menu. Sample is a responsive example of your chosen timestamp format and must match the actual timestamps in your data.

../_images/time_stamp_edit.png

The remaining (optional) columns are set to Choice by default. Other data and column type options are listed in the Type dropdown menu.

Hint

Setting the Type to Ignore means that no data from this column is uploaded. You can set problematic columns to Ignore and upload this data later, rather that cancelling the whole import.

After you have defined the data types, click Import in the lower left corner of the screen. You are redirected to the Process settings page while your file is imported.

You can check the status of your file in the Status column. Failed uploads are marked with an X, successful uploads are marked with a checkmark. Click the X for details.

../_images/upload_failed_new.png

Note

Data cannot be imported partially. If an import fails, no data from this data set was imported.

It’s not possible to make any changes to already imported data, altered data has to be uploaded again.

Deleting process data

To delete process data, click Process settings in the navigation bar on the left-hand side. From there, click the trash can icon next to the name of the file you want to delete. This will delete the file, but not the process itself.

If you want to delete all of your process data at once, click the Delete process button on the bottom left-hand side of the screen. This deletes the Process from the Process list, including all data files and investigations associated with it.

A confirmation dialog appears.

../_images/confirmation.png

Important

Deleted data is not archived. If you delete process data and later decide you need it again, you’ll need to re-upload it.