Split item based on label and send to specific port

Question

question

Eric R6 asked Feb 8, '21 Eric R6 edited Feb 12, '21

Split item based on label and send to specific port

I am trying to get my separator to split the incoming items into 3 different items. In the attached model I have two different items arriving at Separator1 based on an Arrival Sequence. If the item that shows up is SKU1, I want it split into 3 different items. Ideally these would be labeled wld1, wld2, and wld3. Wld1 and wld2 would then go to Queue1, and wld3 would go to Queue2.

If SKU2 shows up, I want it split into 3 different items. Ideally these would be labeled wld4, wld5, and wld6. Wld4 would go into Queue1, and wld5 and wld6 would go into Queue2.

My thoughts were to set this up using a process flow that runs a subflow depending on what SKU# arrives at the Separator. In my full model I will have about a dozen different SKUs that will get split and go to different Queues. Below is a visual of what I am trying to do.

Thank you

Software Version:

FlexSim 20.2.1

separator flexsim 20.2.1

1612901106251.png (31.5 KiB)

test-file-2.fsm (32.1 KiB)

· 1

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.

Joerg Vogel commented · Feb 09, 2021 at 10:00 PM

If you do this with process flow, then you use a simple processor or process flow processor object. If you do this in 3D object logic and exit trigger in a separator object, you might think about to label the items as wld’s after you decided where they go simple by counting. I mean you send them to the queues and then you set the label On exit.

0 ·

Answer 1 · 2021-02-10T02:21:32Z

Parker S answered Feb 10, '21 Eric R6 edited Feb 12, '21

@Eric R6

Here is a model that does what you want to achieve:

support_test-file-2.fsm

You were on the right track, it would be best to do this with process flow. The subflow I included assigns the WLD labels and moves the items to the wanted destination. I have 2 additional global tables that contain values for the WLD labels and the destinations (the "WLDassignments" looks like it could be combined with your "Table1").

I believe this could be modified for your application of more SKUs and queues, except if some SKUs need to be split into a different quantity than 3. In that case we may need to completely remove the 3D separator and handle the split logic in process flow.

I hope this helps!

support-test-file-2.fsm (36.1 KiB)

· 3

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.

Eric R6 commented · Feb 10, 2021 at 04:02 PM

@Parker S,

This does work really well for SKUs needing the same number of splits. In my expanded model I will have 12 total SKUs. Depending on the SKU they could be split between 3 and 7 different ways. Below is what my expanded model will include. I don't have to have the 3D separator in the model. With this many SKUs and splits would going fully to process flow be the way to go?

One work around that I found was to split everything 7 ways, and then change the destination to a sink if they weren't all needed. For example, if SKU1 was split in WLD1 through WLD7, and I only needed up to WLD3 that WLD4 through WLD7 would end up going into a sink.

Thank you,

Eric

0 ·

1612971438102.png (17.9 KiB)

1612972218996.png (7.8 KiB)

Parker S ♦ commented · Feb 10, 2021 at 05:10 PM

@Eric R6

I thought we may have to do everything in process flow, but this way works fine:

support_test-file-3.fsm

I have added a label on the Source arrivals named "SplitQuantity" and use that for the split quantity on the separator

and for the request and require numbers on the Pull from List activity

token.Items is assigned in the event-triggered source.

0 ·

1612976799061.png (7.8 KiB)

1612976850112.png (24.0 KiB)

support-test-file-3.fsm (38.8 KiB)

Eric R6 Parker S ♦ commented · Feb 12, 2021 at 07:35 PM

Hello @Parker S,

That is working properly. Thank you for the help on this one!

0 ·

question