Find attached model (made in FlexSim 7.7.2).
I'm trying to send all the items from the various queues to the first rack (ground storage), then the second, and so on. The first available option doesn't seem to work. Any help would appreciated. 03-08-16-rack-first-available.fsm
The Fixed Object queue checks the current content of the first available Rack and the variable nroftransportsin of this rack to decide if there is enough capacitiy left to create the tasksequence for the transport. If there isn't any capacity (stored item + item in transit) left the queue creates the transport tasksequence for the next available rack. That the transporter works on a tasksequence for the second rack has something to do with the ability how many item's a rack can receive. If a rack is blocked by another transporter the dispatcher moves the next available tasksequence to the transporter. All this is documented in the manual for the fixed resource object.
Hi Jörg Vogel
Firstly, thanks for your response!
I read through the manual and understood how the nroftransportsin gets updated as soon as a flowitem enters the queue. With each flowitem entering the rack, the nroftransportsin and nroftransportsout get updated, and the task sequences are created.
However, I have ensured that the Flow in each queue is set as 'First Available', which should make sure that the first 10 items (max content of the rack) received at ANY of the queues should be assigned to the first rack (variable nroftransportsin = 10, nroftransportsout = 0). With each item entering the rack, the nroftransportsin should decrease by 1, and the nroftransportsout should increase by 1.
But that is not how FlexSim is assigning the flowitems to the rack. Take a look at this model:
03-08-16-rack-first-available-ver-2.fsm
Can you show me how to get the first 10 items received at any of the queues to be assigned to the first rack?
Update to FlexSim 2016 Update 1.
From the release notes:
"Changed the way that fixed resources (except the Combiner) receive items when they are being transported in. Previously, when they were notified that an item was being transported in, they would close their inputs and create an event to receive the next item. This would cause problems if the upstream objects had multiple items to send because their routing strategy would work differently when transporting vs not transporting. We have fixed this so that routing strategies will work the same when transporting as when not transporting. This may change the way that old models work because it changes the events that are created, and, obviously, it fixes routing strategy logic."
If you open this model in version 16.1.2, it behaves the way you want it to.
7 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
