Dynamic Locations Problem. Bug?

[SCHamoen]

[ FlexSim 20.2.3 ]

I got a question from a client that I couldn't answer. So I build a very simple model and it looks like it might be a bug. In the original question a small piece of code was used to determine from which group to take a location, but in the attached model I used the standard case statement. In the first go it takes a location but in the 2nd round it can't find one. Can somebody (@Matthew Gillespie ?) take a look and determine if I do something wrong or if it is indeed a bug?

PeopleBugModelLocation.fsm

[jason_lightfootVL7B4 · Accepted solution]

peoplebugmodellocation_jl.fsm

I think you need to uncheck "Same as last acquired" in the AcquireLocation advanced pull down options, and add a task to have the operator walk away from the location...?

[SCHamoen]

@jason.lightfoot Thanks it works, and I kind of understand why because you try to claim a location that is not in the group your searching. But should this checkbox not be off by default then......

[Matthew_Gillespie]

@steven.hamoen That checkbox is checked because it is very common in Healthcare models to reacquire the same nurse you were using in an earlier step. Modelling a loop with a dynamically changing resource is the less common use case.

[SCHamoen]

@Matthew Gillespie I agree with you for a staff resource but for a location resource?

[Matthew_Gillespie]

@steven.hamoen It happens sometimes and it's for consistency across the People resources. Acquire from the same resource if you want the same thing. If you don't want the same thing use a new resource or uncheck the Same As Last box.