Transferring item and moving item between Rack and Queue (Repost)

Question

question

Jirawat J asked May 31, '19 Joseph Gillespie answered Jun 3, '19

Transferring item and moving item between Rack and Queue (Repost)

Due to my interest in building a model that simulates the flow of item between TS,TE, Rack, and Queue.

I designed the model and process flow where...

1. I want TE to carry the item that receives from Source2 and travel along the way in network nodes, then stop in the blue-marked network node.

2. TE will transfer the item to TS which already waited there in the nearby network node.

3. TE will continue travel from the current point to Sink and start all over the process again

4. While TE is travelling, TS will move the item to Rack and unload it down

5. While TE is travelling back to the blue-marked network node, TS will move the item from Rack to Queue

6. When TE is arrived, TS will come back and pick up the item and do the same process as in process 4-5

7. The loop will continue non-stop

Here're attached files

kcd2-layout-plan2-return-container.fsm

Software Version:

FlexSim 19.1.0

flexsim commands task executer transporter process flow network nodes

19532-1.png (79.2 KiB)

19533-2.png (35.7 KiB)

kcd2-layout-plan2-return-container.fsm (126.9 KiB)

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Answer 1 · 2019-06-03T17:42:24Z

Joseph Gillespie answered Jun 3, '19

@Jirawat J

I'll attach here the model of the solution I found. Some of the problems I found in your model:

1. Trying to mix 3D logic and process flow. For example, you had a dispatcher controlling both TaskExecutors even though you wanted TruckTractor_DI to perform different tasks than TruckTractor_RE. In the solution model I sent you, I removed the dispatcher and gave TruckTractor_DI its own source so that it could be independent of the other TaskExecutor. I also removed the 3D logic for transporting between DM1 and M_R1 and moved that logic to ProcessFlow.

2. Syncronization. The "Push to List" and "Pull from List" accomplish what you wanted to do with syncronization, since the token going through "Push to List" cannot proceed until the item has been pulled from the list. I therefore removed the "Syncronize" activities and it works fine.

I also made a few adjustments to the ProcessFlow to make it simpler.

The updated model: kcd2answer.fsm

kcd2answer.fsm (125.8 KiB)

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

question