Model 4c - Messages without an explicit Edge

Goals of this lesson

  • Learn how to use message events without drawing any message flows

How-to

For a better overview of a more complex simulation model, you are able to hide the Message Flow. For an implicit message flow between two Message Events both have to be named equally. This is the case in Model 4c. (Have a look at Linking Events to each other for more information on this matter.)

Model 4c - Messages without an explicit message flow
Figure 1. Model 4c - Messages without an explicit message flow / IYOPRO-Link
This possibility is not yet given for activities, those always need an explicit message flow.
Do not get confused with IYOPRO’s conformance warnings. It is right that receiving message events need an incoming message flow, but this does not matter for simulation or modeling purposes.

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 you note, the simulation of this model generated a report, that is very similar to the one from Model 4a

    • Its statistics indicate the same reason for inefficiency as the one from Model 4a

    • This is not a real surprise, because the models are almost equal

    • The only difference is that we replaced the activities with intermediate message events

model4c process histo
Figure 2. Histogram of the processing times
model4c process histo1
Figure 3. Processing times