You are in the final stages of importing data into LANA, but somehow loading the transformed data into the system doesn’t work? Error messages, misallocation of data points or uninterpretable results rob you of your last nerve?
Don’t worry, you’re just a few clicks away from your more than deserved analysis results! We have compiled the most important points for you to consider before loading and configuring the data.
Before you upload the log file to LANA, check the following points:
1. The log file is in CSV format.
Case ID – unique identification of the individual cases.
Start – Time at which activity starts.
Activity – Task or activity in a process.
End – Time of the activity end.
Event attributes – Properties of the process activities or events.
Case attributes – Properties of the process instance.
If there is no second timestamp, set the first timestamp or “Start” to “Complete” when configuring the log file.
3. Each timestamp forms a column. The start and end timestamps contain the date and time. If this is not the case, merge the date and time columns directly in the CSV file before uploading.
4. When configuring the log file in LANA, note the following aspects:
• The Case ID column is identified as such and is the only column named “Case ID”.
• The Activity column is called “Action” and is also the only column with this name.
• The same applies to the timestamps: only one column may be designated as the start point “Start” and the end point “Complete”.
• Check whether the attributes have been correctly classified and not identified, for example, as another “Action” column.
The following classifications can be assigned to the attribute columns:
• Numerical attributes – e.g. number of pieces of production parts
• Categorical attributes – e.g. location
• Impact attributes – e.g. costs
Need help loading data? Please contact us here!
5. In addition to event attributes, have you given any of the cases some of the other attributes mentioned? Here is the difference:
Event attributes describe the properties of the process activities or events.
• Event attributes are assigned to individual events.
• Any number of event attributes can occur per event
Example: Manufacturing process
The same Case ID is listed in several lines. In this example, the attributes drill tip (“Bohrspitze”) and carton size (“Kartongröße”) are given. If one or both of the attributes are assigned to the activities, there is a corresponding description in the line.
The number of attributes depends on the process itself and the selected data extract.
Case attributes describe properties of the process instance.
Case attributes are saved as a separate file:
A Case ID is listed in only one line. Here the case attributes gearbox cover (“Getriebedeckel) and hub (“Nabe”) are given. These two properties are assigned to the entire case or business transaction 01 and 02.
For some numerical attributes, it makes sense to mark them as impact attributes during log configuration. This allows variants, cases or activities to be prioritized during analysis, which is of analytical interest, for example, for costs or order volumes. LANA aggregates and prioritizes these values for example in the Variants or Action view.