Issue with Complicated Predecessor String

Question

question

Lawrence B2 asked Jul 27, '18 Lawrence B2 commented Jul 27, '18

Issue with Complicated Predecessor String

I have a complicatedhhn-fed-simulation-building-arrivals-07232018-16.fsm bit of logic in a Predecessor field that is supposed to trigger the activity after a number of other activities have completed. Not sure why this isn't working! Maybe the labs aren't completing where they notify the activities they care about correctly?

Software Version:

FlexSim HC 5.3.4

healthcare string predecessors

hhn-fed-simulation-building-arrivals-07232018-16.fsm (2.5 MiB)

Answer 1 · 2018-07-27T17:10:18Z

Matthew Gillespie answered Jul 27, '18 Lawrence B2 commented Jul 27, '18

Take a look at the Activity Table for Patient 3 who finished 190, but didn't start 191:

Let's look at the conditions of your Predecessor requirement:

90 - True. The patient finished 90 at 1:01:39.

!101 || 101 - True. This is always true. You could remove this condition without changing anything.

!111 || 112 - False. 111 was done and 112 was not.

!121 || 129 - False. 121 was done and 129 was not.

!131 || 135 - False. 131 was done and 135 was not.

!181 || 181 - True. This is always true. You could remove this condition without changing anything.

190 - True. The patient finished 190 at 1:02:39.

In summary, 3 of your conditions are false and 2 are meaningless. Also you need to change the & to && or AND. Looking at the patient's activity table as the model runs can help you see what activities they've done:

Also, shouldn't the Predecessor for 100 be 90, not 80?

activitytable.png (99.3 KiB)

qp.png (627.6 KiB)

· 5

Lawrence B2 commented · Jul 27, 2018 at 05:48 PM

activity-191-pre-disposition-confusion.png

1. See screen shot - why are the &'s double in the Quick Properties and single in the activity table?

2. Fair enough on the tautologies.

3. I think (!131||135) evals as true b/c 133 pushes to 135 via an item destination activity assignment.

4. 90 isn't the predecessor for 100 b/c 90 can happen whenever after 80, whereas 100 is the next thing that must happen after 80.

Thank you,

0 ·

activity-191-pre-disposition-confusion.png (236.3 KiB)

Matthew Gillespie ♦♦ Lawrence B2 commented · Jul 27, 2018 at 06:00 PM

1. You're right, I think you can safely ignore my comment. You have it correct in Quick Properties.

3. Yeah, it looks like this one should evaluate as true later on once the item finishes and triggers 135.

0 ·

Lawrence B2 Matthew Gillespie ♦♦ commented · Jul 27, 2018 at 06:16 PM

actually it looks like 133 isn't kicking off 135 with that item destination bit - do you have a link on how to use this?

0 ·

Show more comments

question