question

Henry Paipa avatar image
0 Likes"
Henry Paipa asked Jason Lightfoot commented

Define logic for task executer according to the type of cargo

Hi Team,

I need support to be able to set up a Task Executor logic, I need to set up a logic that:

1. if the cargo goes to zone B or E or G (i.e., floor storage), the same forklift that unloaded the truck will transport it to that point.

2. If the cargo goes to the rack, an operator with a manual pallet truck will transport it.

How can I create a specific number of forklifts as a parameter? I tried with the option "Set number in people Group" and "Delete and Copy Group members" but when I created for example 20, all of them were directed to a single unloading dock, I would need at least 3, per dock.

I will be grateful for all your support. Thank you very much in advance.


1697713911075.png


1697713980480.png


TaskExecuter-Forklift.fsm


FlexSim 23.2.1
transportforklifttaskexecutorstasksequencescargo
· 3
5 |100000

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

Jeanette F avatar image Jeanette F ♦♦ commented ·

Hello @Henry Paipa,



Do you mean that a maximum of 3 forklifts will work on unloading a truck at a time? Do the fork lifts acquired for that truck need to finish the truck before moving onto the next truck?



1 Like 1 ·
Henry Paipa avatar image Henry Paipa Jeanette F ♦♦ commented ·

Just like that, as is. I would appreciate your support, please. @Jeanette F

0 Likes 0 ·
Jason Lightfoot avatar image Jason Lightfoot ♦ commented ·

Hi @Henry Paipa, was Joerg Vogel'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 comment back to reopen your question.

0 Likes 0 ·

1 Answer

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

In earlier FlexSim Versions we would dynamically build connections from a dispatcher cascade to taskexecuter objects. Nowadays we would use lists to push tasksequence transport jobs, pull and dispatch them to taskexecuter objects. If it comes to situations when an taskexecuter can preempt tasksequences back into a tasksequencequeue, we would set dynamically priorities and/or connect taskexecuter Output ports to a dispatcher object. Then this dispatcher can push received begun tasksequences back to involved lists.

· 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.

Felix Möhlmann avatar image Felix Möhlmann commented ·

Here's an attempt to build out the logic using lists. Each truck creates three tokens which each try to pull a forklift and unload the truck. They all access the "Cantidad" label on the parent token to know when the truck is empty.

Pending on the target zone of the pallet, it is either pushed to a list from which the operators can pull theirs tasks (not implemented). Or to a similar list for the forklifts. After a truck is unloaded, the forklifts check if there are pending pallets at their current position on that list. If so, they move them to the target queues, before being pushed back to the list.

taskexecuter-forklift-fm.fsm

0 Likes 0 ·