Model 3c - Inclusive Gateways

Goals of this lesson

  • Usage of inclusive Gateways

How-to

Contrary to exclusive gateways the conditions in inclusive branching gateways do not have to be exclusive.

NewItem726
Figure 1. Model 3c - Inclusive Gateways / IYOPRO-Link

  1. First create a stochastic attribute as explained in lesson Assignment of Stochastic Process Variables

    1. Call the attribute X and assign it with a Discrete Uniform Distribution with a lower bound of 1 and an upper bound of 3

    2. This will represent the decision basis for the inclusive gateway in the model

  2. Set these conditions:

    1. Upper edge:

      Result=(X>=2);

    2. Lower edge:

      Result=(X<=2);
(Due to the equality) our conditions will both be met, when X is 2, which then will trigger two sub-processes being started on each sequence flow. The merging inclusive gateway therefore waits (similarly to the parallel gateway) until all (alive) sub-processes (tokens) arrive.
3c process attribute editor1
Figure 2. IYOPRO’S Simulation Process Attribute Editor

Report

See below for the run configuration, which we set up to receive the report statistics from below.

Please refer to the section Experiment Results for more information on the report specific data.

Run configuration

  • Stochastic Seed: 12345

  • Simulation start date: 1/1/2014 12:00:00 a.m.

  • Simulation stop time: 240

  • Simulation stop time unit: Hours

Report statistics

  • As mentioned before, we configured the branching inclusive gateway such that in 33% of cases both sequence flows will be followed.

    • The process variable has been assigned a Discrete Uniform Distribution with a minimum value of 1 and a maximum value of 3

  • The statistics from the figures (see below) make this correlation evident

  • The process has been executed 114 times (Figure 3)

  • The activity "Stochastic initialization of process variable" has been executed 118 times

  • The gateway details (Figure 4) show us that the top sequence flow has been followed 78 times

    • and the bottom sequence flow 79 times

    • which sums up to 157 in total

  • This means that we have got at least 39 (157 - 118) process instances, in which the gateway fires twice

  • Also you can recognize from the activity details (Figure 5) that the top activity has been executed 74 times

    • and the bottom one 79 times

    • which sums up to 153 in total

  • This tells us that in at least 39 (153 - 114 = 39) finished process instances the gateway fired twice

    • which is approximately 34% of all cases (just like we intended to)

model3c process cycle stats
Figure 3. Process Cycle Time
model3c gateway1
Figure 4. Gateway details
model3c activity
Figure 5. Activities' processing time