question

1. I'm not familiar with the case study, so I can't comment on what it suggests to do. But your model does use the "MaxWait" label in the pull strategy of the "Too Long Wait" queue. Did you add this yourself?

2. The default way to change the combiner's components list is through the pick option "Update Combiner Component List With Labels" in the OnEntry trigger. This option assumes that you have set up a global table in which each column represents the component list for the corresponding value of the label you use in the trigger option.

To change the value between one and three you would first assign that value to a label (which you already do) and then refer to a global like the following to set the list.

Since in this case the column number and value are equal you can also add that option to the trigger and then customize the code to use the empirical value directly without needing to use a global table inbetween.

3. Some small issues that I noticed:

- The "Switching" queue pulls customers where age < 90 when it should be age > 90, so people who are willing to switch will do so immediately upon entering the queue.

- The DoughLine queue content is compared to the value 5 when pulling customers instead of the respective customer label ("MaxLine"). Is this by design?

The main reason why you are not getting any customers that leave the queue due to wait time is that the condition will only be evaluated for each customer once - when it first enters the queue. You need to add an event that tells FlexSim to reevaluate the back orders when the age increases past the threshold.

One way to do this would be to add a reevalution event to the list that listens for message to the "DoughLine" queue. Then, in its OnEntry trigger, it can send delayed messages to itself just after the thresholds of 90s and "MaxWait" (would) have been reached.