Parallel Branches
Use the AND type branching to model parallel performance of task models in a diagram. Branches that exit the AND point can later be either merged in some point or have no merge point at all. Different modeling techniques are used in different notations to display parallel branches (Figures 1-4):
For Basic Flowchart/Cross-functional Flowchart, the AND type branching point is a task shape that has several outgoing Precedence arrows. A merging point is a task with several incoming Precedence arrows that are part of the branches outgone from the same branching point somewhere in a diagram.
For EPC, the AND operator is the AND type branching/merging point.
For BPMN, a Parallel gateway is the AND type branching point as well as a task shape that has several outgoing arrows. A merging point is a Parallel gateway.
When the simulation engine enters the AND type branching point it continues creating simulation task instances in accordance with each parallel branch. When it enters the merging point, then it stops and waits until all the task instances of all parallel branches finish their performance.
The waiting time can be limited, if you set up a synchronization time. When one parallel branch enters the merging point, the synchronization period starts. The simulation process instance is waiting for other parallel branches in the merging point during this period. In case a synchronization period ends, and some parallel branches have not entered the point, simulation process instance ends its performance.
Synchronization time is set up for the AND merging operator if the diagram is in the EPC notation (Figure 5).
For BPMN, synchronization time is set up for the Parallel gateway.
If your diagrams are in Basic Flowchart/Cross-functional Flowchart notations, synchronization time is the same for all these diagrams and is set up in the Synchronization time for Flowcharts property (Main Menu → Process Analysis → Simulation Properties).
