Model 5 - Sending Signals to Multiple Process Instances

Goals of this lesson

  • Learn how to use signal events

How-to

As in the Message Events in Model 4c all linked Signal Events have to use the same name to identify them as linked. In contrast to messages, signals can be sent to multiple receivers.

simulation tutorial model 5
Figure 1. Model 5 - Sending Signals to Multiple Process Instances / IYOPRO-Link

Parametrization

  • The model and its settings show that the upper process sends a signal every 4 TU.

  • The lower process starts every 1 TU.

Explanation

This means, that always 4 instances of the lower process wait for a signal from the upper process, and the incoming signal always re-activates these four process instances of the lower processing pool.

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

  • Retrospective:

    • The receiving process starts every hour

    • The sending process starts every 4 hours

    • Which means that there are always 4 process instances of the receiving process waiting for a signal from the top process

  • This exact correlation can be found in the report

  • The receiving pool’s lead time is 1 hour and 30 minutes

    • The 1st process instance starts at time 1 and has to wait 3 hours for the signal

    • The 2nd process instance starts at time 2 and has to wait 2 hours for the signal

    • The 3rd process instance starts at time 3 and has to wait 1 hour for the signal

    • The 4th process instance starts at time 4 and receives the signal instantly

    • Summing up these values results in 6 hours, which must be divided by 4 (process instances) for the average of 1.5 or 1 hour and 30 minutes

NewItem743
Figure 2. The processing times
NewItem744
Figure 3. The Report’s event details