Access to this feature depends on your license.
With the multiple-cases simulation function you can simulate multiple process runs which take into account the configured quantitative figures and analyzing quantitative data and bottlenecks.
Before running the multiple-case simulation, configure a scenario on which the simulation is based on. Read the Managing simulation scenarios section.
During the simulation, the simulation tiles display the overall costs, total cycle time, resource consumption, and bottlenecks at the current position in the process (left column) and of the complete previous run (right column).
Cycle time: Refers to the amount of time between start and completion of a process.
Resource consumption is the overall time process participants committed to process execution.
Run the multiple-case simulation
Follow these steps:
Open the BPMN simulation tool. Read the Access the BPMN simulation tool section.
Select the Multiple Cases function.
To configure the duration of the simulation, click Duration.
Enter the required number of days and click Save.
Select a scenario and click Play.
The BPMN Simulator analyzes the selected scenario and displays the results in the process diagram and on the simulation tiles.
For detailed quantitative information on the current run, click More.
To simulate the another run through of all process instances in the previously calculated scenario, click Play.
The following table shows simulation outcomes on a diagram after running the multiple-case simulation:
|Waiting instances display as blue dots placed above the ingoing sequence flow.|
|Running instances display as blue dots within the border of a task.|
|Completed instances display as a stack next to corresponding task.|
After running the multiple case simulation, result metrics are available for the current run of the simulation.
The following metrics are available:
Total cycle time
To access the metrics, click the required metrics simulation tile.
The multiple case simulation calculates the average, minimum, maximum, and total costs. The simulation determines all cost types based on the simulation result. To access the Costs metrics, click the Costs tile.
The following table discusses the descriptions for each table in the Costs tile:
|Costs||The table displays the average, minimum, maximum and total costs for selected process instance.|
|Costs per task||The table displays the costs for every task of your process. It includes average, minimum, maximum and total costs for each task.|
Total cycle time
The multiple case simulation calculates the average, minimum, maximum and total cycle times. As for the costs, the simulation determines the cycle times based on the simulation result. To access the Total cycle time metrics, click the Total cycle time tile.
The total cycle time can exceed the simulation time span. This can happen for two reasons:
Your resources can't handle cases fast enough and process instances get delayed.
The cases that occur in the last hours / minutes of your simulation time frame exceed the time frame before they are completed.
The following table discusses the descriptions for each table in the Total cycle time tile:
|Cycle Time||The cycle time of a process instance is overall time needed for each process instance to complete from start to finish. The table shows the selected process instance's cycle times as well as the total sum of all run cycles.|
|Execution times incl. resources and waiting times||
The execution times of activities executed within a process instance can be influenced by the availability of resources as well as working schedules. The table shows the pure execution time taken for each activity including the time waiting for missing resources and the time taken due to working schedules. Waiting times due to missing resources are listed as bottlenecks and are available under Bottlenecks tile.
|Execution times incl. waiting times||
The table shows how long the execution time took for each activity including the working schedules and excluding all available resources. The values are the pure execution times of tasks in addition to the time a task had to wait because the assigned resource were unavailable.
For example, If a task with a duration of 60 minutes was assigned to a user, then while executing the task the user takes a 30 minute break, the execution time incl. waiting times would increase to 90 minutes instead of 60 minutes.
|Pure execution times||Within a process instance, several activities are executed. These values are the actual execution times of tasks where someone is actively working on the tasks. The execution can occur sub-sequentially, delayed or in parallel. The table displays how long the pure execution time took for each task.|
The resource consumption lists the consumed time and the workload for each process resource.
The consumed time is the total time a resource spends on executing activities. The workload is the percentage of the available time a resource is occupied with executing activities.
To access the Resource consumption metrics, click the Resource consumption tile.
The following table discusses the description for the table in the Resource consumption tile:
|Resource consumption||The execution of activities is performed by resources. The table shows the workload of all resources in your scenario. For each resource the consumed time and workload information is displayed.|
A bottleneck occurs when a resource's limited availability increases the waiting times of cases. Waiting times describe how long cases are idle because no resource is available to execute the current activity.
To access the Bottlenecks metrics, click the Bottlenecks tile.
The following table discusses the description for the table in the Bottlenecks tile:
|Bottlenecks||The execution of a process instance might be delayed due to a shortage of resources. When an activity is ready for execution but all resources are already allocated, the execution has to wait. The table shows all resources and activities with the their total waiting time that were delayed. The total waiting time is the overall time activities have to wait for a specific resource, because the resource was occupied by another task.|
Is this page helpful?
Do you have feedback for this page?