I have two locations and two staffs in the same group. I have set one location and one staff operating only half day as below. However, the model stops running when it hits the 12:00am.
Why the simulation stops running when it hits the downtime?
FlexSim 20.2.2
@Jun J2 It's almost impossible to say without seeing your model. Could you attach it?
Yes. However, my model is too big to attached. Could you send me a link to upload my model? Thanks!
@Jun J2 Here's an upload link: https://nextcloud.flexsim.com/s/GtA5nieCKpNLc6f
I changed the downtime behavior from "offschedule" to "Break 1" and it works now. By the way, could you explain to me how to choose "Down State". I saw there are 40 items and it seems that "12-schedule" is the default one. Thanks!
@Jun J2 That seems weird that Break1 would make it start working. The main difference is that OffSchedule doesn't let the staff/location be acquired at all during that time, whereas Break1 will let the break be interrupted if a higher priority task comes along. So, it's probably not what you want since the staff could start working on something between 12-8.
Since you're using a down behavior, the down state isn't used at all. The state comes from the state specified on the down behavior.
I'm not seeing your issue. When I run your model with the time table set to either OffSchedule or Break1 the model runs all the way to your set stop time of 12 AM on 8/25/2020.
I did notice one issue with your model, you've used the wrong Experiment variable for changing the number of objects in a group and it's causing exceptions. You want to use the "Number of Objects in People Group" variable and not the "Number of Objects in Group" option.
Also, your model is only 22 MB and, as you can see below, attaches fine to this forum.
Thank you, Matthew! Could you explain to me the difference of these two options?
The top one deletes all the members of the group except for the first one, then it creates copies of the first member until you get to specified number of objects. That's why all your beds are stacked on top of each other. This option is not very good in People/Healthcare models where you often have a bunch of distinct staff members in a group with each staff member assigned a specific place in the model and a specific work schedule. This option works best for when you have a bunch of nameless duplicate "operators".
The bottom option doesn't delete any objects, nor does it add any new objects so you have to have the maximum number already in the model. It instead removes members from the group from the bottom of the list until it gets to the specified number. The members removed from the group get a black box drawn around them so you can tell visually that they're not available. And since they're removed from the group they will never be used when you say "Any Member from ...group".
12 People are following this question.
