Prev Next

Timer Event - Standalone Intermediate Event

When a Timer Intermediate Event is used within the normal sequence flow as a standalone element, it acts as a delay mechanism.

Create BPMN Model

  • Create a Start Event called StartEvent1
  • Add a Sequence Flow to a target Parallel Gateway called Fork
  • Add Sequence Flows to:
         -  A Standalone Timer Intermediate Event called Delay15Minutes, and from that a Sequence Flow
            to an Activity called Task1
         -  An Activity called Task10Minutes, and from that a Sequence Flow to an Activity called Task2
         -  An Activity called Task20Minutes, and from that a Sequence Flow to an Activity called Task3
  • From Task1, Task2 and Task3 create Sequence Flows to a Merge Parallel Gateway called Merge
  • Add a Sequence Flow to a target EndEvent called EndEvent1

Configure BPSim

In this section, we create the Configuration Artifact, specify the model Package and configure the parameter values of each element.

Object

Action

Create Artifact and Package

  • Open the 'Configure BPSim' dialog ('Simulate > BPSim > Manage > Open BPSim Manager')
  • Create an Artifact named 'IntermediateEvent - Standalone - Timer' (in the 'Select/Create Artifact' field, click on the button and select its parent Package and click on the Add New button, then type in the element name and click on the Save button and the OK button)

Then all the BPMN elements will be loaded in to the 'Configure BPSim' dialog.

StartEvent1

  • In the element list on the left of the dialog, expand the 'StartEvent' group, then click on StartEvent1 and on the 'Control' tab
  • Click on the 'New Parameter' drop-down arrow and select 'Trigger Count', then type '1' in the 'Value' field

  • Click on the 'Properties' tab
  • Overtype New Property with dummyProperty; in the 'Value' field, click on the button and on 'Constant' and 'Numeric', and in the 'Constant Numeric' field type '0'

With this property, the 'Property Trace' dialog will be able to show the sequence of element flows during simulation.

Delay15Minutes

  • In the element list on the left of the dialog, expand the 'IntermediateEvent' group, then click on Delay15Minutes and on the 'Control' tab
  • Click on the 'New Parameter' drop-down arrow and select 'InterTriggerTimer', then set the 'Value' field to 15 minutes ('000:000:000 000:15:00')

Task10Minutes

  • In the element list on the left of the dialog, expand the 'Activity' group, then click on Task10Minutes and on the 'Time' tab
  • Click on the 'New Parameter' drop-down arrow and select 'ProcessingTime', then set the 'Value' field to 10 minutes ('000:000:000 000:10:00')

Task20Minutes

  • In the element list on the left of the dialog, expand the 'Activity' group, then click on Task20Minutes and on the 'Time' tab
  • Click on the 'New Parameter' drop-down arrow and select 'ProcessingTime', then set the 'Value' field to 20 minutes ('000:000:000 000:20:00')

Run Simulation

  • On the 'Configure BPSim' dialog Toolbar, click on the 'Run' icon to open the 'BPSim Simulation Controller' dialog
  • Click on the 'Run' icon drop-down arrow and select 'Standard Simulation'
  • After simulation, click on the button on the tool bar to display the 'BPSim PropertyParameter Values' dialog
  • Click on the Query button and on the 'Group by Property' tab

Analysis

The Fork Parallel Gateway will activate the outgoing Sequence Flows simultaneously (the order is undefined and not important). However, we would expect the order of the Tasks to be exactly:

  • Task2
  • Task1
  • Task3

This order is determined by the BPSim parameters set on two of the Activities (ProcessingTime) and the Timer Intermediate Event (InterTriggerTimer). The sequence shown in the 'BPSim PropertyParameter Values' dialog confirms that Task2 comes ahead of Task1, which comes ahead of Task3.