rhorn2 avatar image
rhorn2 asked Andrew O commented

Task Executer Movement

I believe I finally got the flow of items in the correct order.

I am questioning/debating a few things:

1) Should I have the last Combiner go directly to the task executer? Can the task executer handle holding 6 items/packs? I'm guessing not, which means I need join 6 packs (totes) of 14 sheets (boxes) as 1 item. I have the last Combiner set to join but seems to not create/establish a singular item for movement of the 6 packs/totes. A 7th pack/tote just adds right on.

2) I'm not as familiar with task executors/transporters from my initial training so I'm having trouble setting the task sequence list. I want the task executor to load up the 6 packs (or joined as 1 item/container); move to floor storage in front of it; and unload the item in the floor storage. How do I go about setting that up with Global Lists? Is it just a TSList set up?

My current model is attached.

Thank you for your help.

EDIT: can a joined item (the 1 container of the 6 packs/totes of 14 sheets/boxes) be separated once unloaded by a task executer or transporter? If not, what would be a feasible way to separate the joined item once it is away from the production line.

Thanks again.

Model 1 v2 Carleton.fsm

FlexSim 23.0.0
task executerwarehouse
· 1
5 |100000

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

Andrew O avatar image Andrew O ♦ commented ·

Hi @rhorn2, was Kavika F's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 Likes 0 ·

1 Answer

Kavika F avatar image
Kavika F answered Kavika F edited

Hey @rhorn2, I think I've got some answers for you. Let me know if you need more clarification.

1) Task Executers (TEs) can hold more than one item at a time. If select a TE and look at the Properties panel on the right, you'll see a "TaskExecuter" section. Under that, there's an option to change the capacity (default is one).


That means you don't have to combine the 6 totes before loading them into the TE.

2) Here's the documentation on Task Executer concepts you can reference. I can give you a brief overview though.

TEs are objects we use to simulate what their name implies - someone/something that performs a set of duties/tasks. A Task Sequence (TS) is a list of tasks a TE will perform in order. For example, when your Queue10 gets filled, your TE receives a TS to perform a number of tasks to deliver the totes to the FloorStorage:


(This screenshot is from the Tree - a view that shows you properties of objects. I'm currently looking at the TE's tree variables, one of which is "activetasksequence", a.k.a. the TS it's currently performing). You can program the logic of TEs through the 3D model and the properties panel (which I referenced earlier) or through Process Flow (or both!).

3) Yes, items can be separated once unloaded. You can either put them through a Separator or write some Process Flow logic to take care of it for you.

As for your model, I've modified it to perform (what I assume is) your expected behavior.

I assume that you wanted 6 full totes to be placed on a pallet. If so, then you had the right idea using a Combiner; however, your connections were in the wrong order. You had the Totes coming in through Port 1 and the pallets coming in through Port 2. A combiner's input connections matter - it expects to receive a pallet/tote/some flowitem that you can stack things on through Port 1. Then it expects X number of items from each other port (defined in the properties panel):


Note: this Components List table will add rows the more input ports it has. If instead you wanted to move all 6 together but keep them separate, then you can remove this Combiner and send them straight to Queue10.

Next, you had the Center Connection between Queue10 and the TaskExecuter1, but you still needed the Output Connection from Queue10 to FloorStorage1. Queue10 is declaring that it wants to send items to FloorStorage1 that way; however, we need to check the "Use Transport" box so then it knows to use our Center Object (the TE).


If you remove batching (since we now have the 6 totes on 1 pallet, thus it thinks it's 1 item), it will load the pallet and move it to the FloorStorage. (The pallet is too big to fit in the FloorStorage slots, so it will throw an error saying it wasn't given a slot).

Here's the other approach: I changed your model a bit so instead of packing all the boxes, Queue9 will batch 6 totes and the TE will load all 6 totes to take to the FloorStorage. There, it will unload each one individually.


(The model is sped up a lot, so it may look like the TE jumps around).


5 |100000

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

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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