question

fiz avatar image
0 Likes"
fiz asked Felix Möhlmann commented

problem with my Coordinated task sequence

SimModel_MCCWarehouseAutomation_autosave.fsm,

My organization is still new to flexsim. I am facing a bit of challenge understanding interface between process flow and 3d model my model is to be able to do the following, when Transfer Area 1 or 2 is empty operator is suppose to fill in an empty trolley on the transfer area. subsequently there is a source (from queue 1) pulling in 2 bins in a normal distribution every 10 seconds. then the operator is suppose to transfer 2 bins from warehouse to transfer area. the agv will then collect the trolley+2bins to be delivered to queue1. i am having difficulty to request operator r to transport 2 bins from warehouse with a single process flow as the current process flow only transport 1 bin. since there will be more queue that will be added with different pulling request to queue 1 i am quite clueless how i could repeat the process flow rather than doing it one by one. i am open to any suggestions provided as flexsim interface and function is still relatively new to me. thank you!

FlexSim 21.1.5
simulations
5 |100000

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

1 Answer

Felix Möhlmann avatar image
0 Likes"
Felix Möhlmann answered Felix Möhlmann commented

You do not actually pull two bins in the Process Flow. And if you do, you need to use a subflow to load each item in the resulting array label.

To make the model scale more easily you can:

- Use groups:
You can bind the number of created tokens in a source to the amount of objects in a group. This can for example be used to create one initial token for each of the transfer areas. Similarly, an Event-Triggered Source or Wait for Event activity can listen to events for a whole group. You can then assign the "Event Object" to a label, so you know which object fired the event.

- Use Object Process Flows:
The queues demanding the items can be modeled well by using an Object Process Flow. This essentially runs an independent copy of the flow for each attached object. The instance object is always accessible in the flow through the variable current.

I have build some example logic structures in your model.

simmodel-mccwarehouseautomation-fm.fsm


· 8
5 |100000

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

fiz avatar image fiz commented ·

Thank you Felix, the model provided was really helpful for me to progress.

As for object process flow in the model, there is only 1 queue hence using the variable "current" is able to handle the simulation. Say for example i have multiple queues (e.g 5 different Queue with a different pulling rate, what variable may i use aside from current to differentiate the pulling of the different queue. Is declaring new different variable for the other Queue the way? How may i do so if thats the case.

0 Likes 0 ·
Felix Möhlmann avatar image Felix Möhlmann fiz commented ·

Any information unique to the instance objects should be stored on those objects in some way if possible.

For example, you can store the value that should be used in the source distribution on a label.

simmodel-mccwarehouseautomation-fm_1.fsm

0 Likes 0 ·
fiz avatar image fiz Felix Möhlmann commented ·

draft simmodel R1.fsm

Initially this current SimModel when running it was fine, but after saving and running the model again the operator are behaving weirdly and was different from the initial simulation ran although nothing was change.

1718764359025.png


in the initial simulation, the operator made the red path, however after saving and running the model the operators are making the blue path instead. any idea where I may have gone wrong?

0 Likes 0 ·
1718764359025.png (305.7 KiB)
draft-simmodel-r1.fsm (205.3 KiB)
Show more comments