question

Tee Hiett avatar image
0 Likes"
Tee Hiett asked Tee Hiett commented

Why doesn't patient 35 go into the the elevator with companion?

In the attached model only patients with PCI 3 are being processed. When patient ID 35 completes the 2nd floor process. The patient and the companion go to the elevator. The companion enters the elevator and the patient waits for the next elevator. When the companion gets to the 3rd floor process (before the patient), the program stops and a dialogue box pops up saying the destination for that companion could not be determined . This same event happens for patient 217 and patient 323. If I remove the Repeat Random Streams, the event occurs with different patients during the day. Thanks for your help with this. This problem has cost me considerable hours but I didn't want to send it in until I had what I think is a good example to show what is happening. Teeelevators-th-02-21-2017.fsm

FlexSim HC 5.1.0
healthcareelevatorhealthcare hc
5 |100000

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

1 Answer

Matthew Gillespie avatar image
1 Like"
Matthew Gillespie answered Tee Hiett commented

You are sending a message to SecondFloorProcess twice whenever a patient leaves it. One is in the On Exit trigger of SecondFloorProcess. The other is in the Activity Finished trigger of Activity 20. You should only be calling it once so you need to get rid of one of those triggers.

Amazingly, this is working for most cases since by the time the second dispatch companions code is executed both the patient and the companion are at the destination already. However, in the case where the patient and companion take separate elevators this second call is not working correctly since the patient is still on the elevator.

· 1
5 |100000

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

Tee Hiett avatar image Tee Hiett commented ·

Thanks, Matthew, I thought sure I had corrected all of those but, obviously, I hadn't :-(.

Tee

0 Likes 0 ·