topic Changing number of staff or locations - Best practise in FlexSim Forum

Changing number of staff or locations - Best practise

christian_norregaard — Fri, 28 Jun 2019 12:12:32 GMT

[ FlexSim 19.1.1 ]

Hello all.

When working with the People Module, what is the 'correct' way to easily change the number of resources in a group of location or staff?

I would like to control it from a global table - as shown below. In a GP model, I would have used a 'Resource' and set the 'Count' value to point to the table, but that doesn't seem to be an option in the 'Staff Resource' of the People Module.

Is there a simple way to use table values like this one to control the number of People Module resources, or would I have to use a reset trigger and edit group members or something like that?

There is probably some kind of simple and obvious solution to this, but I haven't found it so far.

Thanks in advance.

/Christian

Re: Changing number of staff or locations - Best practise

zac_h_adsk — Fri, 28 Jun 2019 14:55:39 GMT

@christian.norregaard

When using Staff Resource it gets a little more difficult. But the easiest way to reference a global table and create the amount of doctors/nurses needed in the simulation is to use a normal resource. (When using Staff Resource, you have to create the 3D models first and create them in a Group. The Staff Resource also functions more like a list.)

Re: Changing number of staff or locations - Best practise

JordanLJohnson — Fri, 28 Jun 2019 18:25:14 GMT

This is something we are working on for 2019 Update 2; we want it to work seamlessly and easily, and it is hard to get that working well in the current version.

The best way would probably be to create the maximum number of each item that you want. Then write an OnModelReset script that adds or removes the objects from the People groups (or their subgroups). This way, the Statistics Tables and People Resources will all ignore those objects.

Re: Changing number of staff or locations - Best practise

christian_norregaard — Fri, 28 Jun 2019 18:57:06 GMT

Thanks, Zachary.

I suspected there was not currently a simple out of the box solution. I will probably use Jordan's solution with the reset trigger until 19.2.0.