question

hikel avatar image
0 Likes"
hikel asked hikel commented

Split Order pick between drivers


I would like to split the token.OrderPicks between drivers as this is label represent Aisle within the warehouse split going to be based when you have 10 aisle picks for example and 3 drivers the first two drivers get 3 aisle each remaining get 4 and when it is equal split it equally @Felix Möhlmann do you have any suggestion for this one I tried batch activity and push to list but I didn't manage to solve it

1743105579240.png


shiftpick1.fsm

FlexSim 24.2.2
processs floworder pickingsplit
1743105579240.png (70.5 KiB)
shiftpick1.fsm (154.0 KiB)
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 hikel commented

You would need to alter the code in the Custom Code activity marked below. It currently creates the "OrderedPicks" array where the first 'layer' is split by aisle and contains the picks in that aisle. Instead you would add an additional layer to the array that splits the order into subtasks for one forklift each.

1743158484850.png

1743158492677.png

The token would then create child tokens in a Run Sub Flow activity equal to the number of entries in the array. Each of those would get assigned one entry from the array as their own "OrderedPicks" array, pull a Forklift and then run through the logic as before.

the big question is really by what rule to split up the tasks. Since you don't know how many forklifts will actually be available it doesn't make much sense to use a fixed number of subtasks. I think I would either split them completely by aisle and when a forklift is done with one aisle it becomes available to be pulled by a different token belonging to the same order before returning to drop off the pallet. Or you split by 'capacity', meaning after a fixed number of picked up items.

Another change that will be necessary is to create as many empty pallets are there are subtasks. Currently one empty pallet is created per order right at the start of the run. This would need happen after the actual number of subtasks in the order is known.


1743158484850.png (28.2 KiB)
1743158492677.png (19.1 KiB)
· 5
5 |100000

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