Multiple-case simulation

Note

This feature is available in the Enterprise Edition.

The multiple-cases simulation function allows you to simulate multiple process runs taking into account configured quantitative figures and analyzing quantitative data and bottlenecks.

Before running the n-case simulation, you might want to configure the scenario on which the simulation is based. You can find more information about scenarios in the chapter Manage scenarios.

Additionally, you can configure the period of time the simulation should cover. To do so, proceed as follows:

Click Duration:

Now type in the desired number of days and click Save:

To run the multiple-cases simulation, select a scenario and click the Play button:

The BPMN Simulator will now analyze the selected scenario and display the results in the process diagram and on the simulation tiles.

The simulation tiles display the overall costs, cycle time, resource consumption and bottlenecks of the current simulation scenario run (left column) and of the previous of run (right column).

The Multiple-Cases Simulation Dashboard

The Multiple-Cases Simulation Dashboard

It might be necessary to explain the difference between cycle time and resource consumption: Cycle time refers to the amount of time the process start and process completion while resource consumption is used as a term for the overall time process participants committed to process execution.

For detailed quantitative information, click the more link on the corresponding tile:

The simulation dashboard contains detailed quantitative information.

The simulation dashboard contains detailed quantitative information.

To restart the simulation, click the Restart button:

To simulate the run through all process instances of the previously calculated scenario, click the Play button on the lowest simulation tile:

In the diagram, waiting instances are displayed as blue dots place above the ingoing sequence flow:

Running instances are displayed as blue dots within the border of a task and already executed instances as a stack next to corresponding task: