Waiting Line OnEntry trigger adds all waiting patient

Question

question

Sebastien asked Jan 18, '22 Ryan Clark commented Jan 21, '22

Waiting Line OnEntry trigger adds all waiting patient

Hello,

In order to manage the solution from my previous post:

https://answers.flexsim.com/questions/114135/extract-real-waiting-time-from-a-patient-in-a-wait.html

we are implementing a separated Process Flow for managing Entry/Exit of patient in a waiting line and storing the waiting time.

Yet, when a patient enters a waiting line, the OnEntry trigger fires but adds all the patient that are already in the waiting line, which in our case adds patient exponentially. (see attached model)

Are we missing something for only assigning the entering patient in the source event or is this a normal behavior ?

Test Waiting Line.fsm

Software Version:

FlexSim 20.2.3

waiting line event-triggered source

test-waiting-line.fsm (42.1 KiB)

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Ryan Clark commented · Jan 21, 2022 at 06:48 PM

Hi @Sebastien, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 ·

Answer 1 · 2022-01-18T10:26:54Z

Felix Möhlmann answered Jan 18, '22

The "Person Flow" is an instanced process flow, meaning each patient runs it's own copy of the process flow so to speak. Each of those instances reacts to the entry event and creates their own token.

The logic taking care of gathering the waiting time should either be part of a separate process flow or you can sort out the "wrong" the tokens in a decide activity by comparing the arriving patient ("token.pax") to the instance object ("person").

When using a separate process flow, it can either be a "general" flow, with sources listening to each waiting line, or an instanced flow but with the waiting line as instance object. In the latter case, you can listen to an event happening on the instance object ("current"), instead of having to add events for each waiting line in the model (see the attached model in the last comment on your previous post).

1642501601995.png (22.2 KiB)

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

question