question

Daniel Z4 avatar image
0 Likes"
Daniel Z4 asked Matthew Gillespie commented

How to control the content of a floor spot (people module)

Hello,

I am facing difficulties to masterize my floor spot with the people module.

My target: identify simultaneously the number of patients and the number of transports that are located into my floor spot.

Attached I simulated 2 situations with separated dashboards:


V1: the patient is moved from a transport to another while moving to another floor spot. The problem, my "Bed" stay counted in the floor spot "transfert" but as soon as I move it to another floor spot, the model doesn't want to count it anymore.

Any idea for both problems:
How to avoid that the bed is still counted even though the patient is transferred to another place?

How to count the bed in a floor spot when it does arrive? (I can solve that with a move object, but, in my opinion, it is not a good way to do it, and finally it makes no sense that once it counts and the other one not).


V2: the patient is moved from a transport to another in the same floor spot before being moved to another one, which is the final situation of my project as the patient might wait after having changed is transport.

The problem here is that for a short time, I get 2 WIP in my floor spot "transfert 2". How can I avoid that?

Trial Content With People Module.fsm

Thank you very much for your answers, best regards,
Daniel Zimmermann


FlexSim 20.1.3
people modulefloor spot
· 4
5 |100000

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

Matthew Gillespie avatar image Matthew Gillespie ♦♦ commented ·

@daniel.z4

When a transport with a patient in it is placed in a floor spot do you want the content to be 1 or 2 (1 for the transport and 1 for the patient)?

0 Likes 0 ·
Daniel Z4 avatar image Daniel Z4 Matthew Gillespie ♦♦ commented ·

The best case would be to have a content of 2 with a separation between the bed and the patient. And also that when you transport a single bed without patient to a floor spot, it still counts as an input (currently a equipment without patient doesn't count at all in a floor spot).

0 Likes 0 ·
Matthew Gillespie avatar image Matthew Gillespie ♦♦ commented ·

I don't understand what you mean when you say, "How to avoid that the bed is still counted even though the patient is transferred to another place?"

Are you talking about the brief period of time that the bed is still in Transfert after the patient leaves? You want Transfert to show a content of 0 at that point?

0 Likes 0 ·
Daniel Z4 avatar image Daniel Z4 Matthew Gillespie ♦♦ commented ·

There is here two situations:
1. Effectively, during a short period the content will be 2, which is a problem because there is one patient and 2 beds. Either it stays 1 (patient) either it shows 3 (1 patient, 2 beds) with a separation in the census between bed and patient, to be able to analyse it at the end.


2. When the patient will leave the floor spot (where we had a content of 1 before moving anything which is a patient in a bed in the floor spot) the current content will stay one... But when we move a single bed to another floor spot, it shows nothing/empty.

0 Likes 0 ·

1 Answer

·
Matthew Gillespie avatar image
0 Likes"
Matthew Gillespie answered Matthew Gillespie commented

For V1 you should just move the bed into the floor spot with a move object. You say it doesn't make sense why the Transport Person activity moves the bed into the floor spot, but the Move Equipment doesn't. Basically, you're trying to model something different than what the activities assume you're tying to do. The Transport Person activity only moves the bed into the spot if you check the Keep Person on Transport checkbox. Otherwise the patient gets off the transport and gets into the floor spot. In the People module Location objects only ever have patients placed inside of them. The Transport Person activity makes a small exception when you check the Keep on Transport checkbox because it's treating the bed with a patient inside it as a single unit representing the patient.

V2 doesn't make any sense to me. Why are you moving both transports into one object? Shouldn't you put a 2nd floor spot next to Transfert2 where you can place the other tranpsort?

· 2
5 |100000

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

Daniel Z4 avatar image Daniel Z4 commented ·

I will use the V1 and make a move object. The problem will stay with the content of the transfert which stays at "1" with an empty bed when the patient is going away. I will overtake this problem by making the transfert somewhere else (in a temporare floorspot). But in my opinion it is not a good way to solve it, because if we focus on the patient, which makes sens, the floor spot should not care about an empty bed, which is actually not the case.

Nevermind, I assume that we have not the same vision of the utilisation of the people module and we are working on that. To be honnest, for complexe systems, people module makes things much harder to modelize than FlexSim industry for the moment (especially with the aquires which are way harder to use than lists).

Thanks for the answer,

DZ

0 Likes 0 ·
Matthew Gillespie avatar image Matthew Gillespie ♦♦ Daniel Z4 commented ·

If you want the floor spot to only show content when there's a patient there then use the Location charts, you are not currently using the People module charts.

No one's forcing you to use the People module. The acquire and release activities are generally viewed as easier than lists which is why People module uses them (it's all designed for less technical users). However, behind the scenes the People module is really just using lists. All the locations are on the Locations list. Feel free to stop using People module activities and use Lists however you want.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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