How to create transport and equipment on demand in people flow

Question

question

Patrick Cloutier asked Jun 22 2018 at 8:16 PM Patrick Cloutier commented Jun 26 2018 at 8:55 PM

How to create transport and equipment on demand in people flow

I'm modeling thousands of patients and employees walking through an hospital. I create them as needed with Create Person. I also create people accompanying people as needed. I create people at their origins and destroy them at their destination. Its a flow analysis model. That works fine.

I'm trying to also create transport and equipment on demand so that I don't have to have a group of thousands of wheelchairs and gurneys at the beginning of the simulation waiting to be used.

What would be the command(s) to Create WheelChair, Create Gurney and Create Equipment and then acquire them properly with Acquire Equipment and Acquire Transport ? All this in ProcessFlow.

Thanks

Software Version:

FlexSim 18.1.1

people flow create equipment create transport

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2018-06-22T21:40:14Z

Regan Blackett answered Jun 22 2018 at 9:40 PM Patrick Cloutier commented Jun 26 2018 at 8:55 PM

Here's a little fuller example, using the same concept with a patient TaskExecuter instanced flow to mimic a patient track. The big key is creating a single Staff, Transport or Equipment object in the model and then using Create Object activities to make copies of them (just sample the object on the 'Object' field of Create Object).

stafftransportondemand.fsm

stafftransportondemand.fsm (37.0 KiB)

· 6

Joshua S commented · Jun 22 2018 at 9:44 PM

A much better example. Something I noticed with both our examples is since the objects were duplicated, the duplicated wheel chairs will start stacking on each other over time, so something will need to destroy them in process flow, or else on reset your are going to have a large amount of wheelchairs pile up.

0 ·

Regan Blackett ♦ commented · Jun 22 2018 at 9:47 PM

I destroy my Staff and Transports when they aren't needed any more, and also flag them to be destroyed on reset so you don't get left overs if you happen to start over while they are still in use.

0 ·

Patrick Cloutier commented · Jun 24 2018 at 11:59 AM

That is so simple. Wow.

Question 1: Why can't I just use current.staff instead of token.staff since I'm in an instanced flow?

Question 2: Is it possible to create the objects where I want? Now whatever I specify in CreateIn or CreateAt, they are created on top of where the current one is. Not convenient because I have more than 15 entrances.

Comment 1: I'm using Astar so I added a contextdragconnection right after the create to attach the created object to Astar.

Comment 2: I use CreatePerson instead of CreateObject to create the staff and it works just as well.

0 ·

Regan Blackett ♦ Patrick Cloutier commented · Jun 26 2018 at 3:03 PM

Answer 1: You probably can. 'current' there would refer to the Patient object and so if you assign the label to current, that seems fine. I probably assigned it to token more out of habit than anything.

Answer 2: With 'Create in' and 'Create at' you need some object to act as the target for where to put things, but you could follow up the creation activity with a Change Visual and adjust the coordinates if you want to place them someplace specific. I may be misinterpreting your question, if so let me know.

Comment to Comment 1: You don't have to do that. The 'Create Person' activity automatically attaches people to an A* navigator (if it exists) upon creation.

Comment to Comment 2: Good! I again probably used 'Create Object out of habit

0 ·

Patrick Cloutier Regan Blackett ♦ commented · Jun 26 2018 at 3:48 PM

About Question 2. I import an Excel table in a Process Flow Schedule. This creates 2 pointer labels on the tokens: Origin (Orig) and Destination (Dest).

These are always Door locations. The persons are created at token.Orig. Then in the instanced Flow (see picture), if a person needs a wheelchair for example, its process flow branch has a CreateObject wheelchair like you showed me to do. In the CreateAt field I put current.Orig

This should create the wheelchair in whatever origin (door) is specified on the pointer label. But it does not. The wheelchair is always created on top of the original wheelchair which serves as the copy model.

But surprisingly it works for the cart. If a person needs to push a cart, then the cart is created at whatever door location specified in current.Orig. It's like createobject behaves differently if its an equipment (cart) VS a transport (chair or gurney).

0 ·

capture.jpg (134.6 KiB)

Show more comments

Answer 2 · 2018-06-22T20:39:41Z

Joshua S answered Jun 22 2018 at 8:39 PM Joshua S converted comment to answer Jun 22 2018 at 9:42 PM

This is a very simple example using a Wheelchair and a PortableEKG.equipment-and-transport-on-demand.fsm

equipment-and-transport-on-demand.fsm (24.7 KiB)

question