Problem with Sorting Process

Question

question

Kadircan T asked May 2, '23 Kadircan T commented May 3, '23

Problem with Sorting Process

In my process, the personnel first bring the packages to the sort area and then sort them to certain areas. I have assigned a capacity to each chute and when each chute reaches a certain number, no more packages should be placed in that chute. Then a personnel takes the packages from the chute and moves them to the other Queue.

Here is the problem I have here:

* For example, there are 3 packages in the chute but the staff is only taking 2 of them.

* The model stops at some point and does not continue, I don't understand why.

I am sharing my model below, can you help me with the issue?

Thank you very much.

Software Version:

FlexSim 22.2.0

list decide sorting

wsort5223.fsm (126.7 KiB)

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.

Answer 1 · 2023-05-02T11:16:05Z

Felix Möhlmann answered May 2, '23 Kadircan T commented May 3, '23

There are multiple queues with the same Target label value. When pulling from the list based on that label, you are not guaranteed that all items are in the same queue. I don't see a need to even use a list here? You already know from which queue you want to the items at that point.

The Sorting section of the Process Flow is an infinite if an operator is available but the chute is not. You need to let the token wait until the chute is free again before it loops back around.

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

Kadircan T commented · May 02, 2023 at 12:06 PM

Hello,

There are 16 regions in total and I have 2 designs. The first one is like the bottom of the image, two seperate modules are placed. In the 2nd design, we connect the midpoints of these two modules. In other words, since there are the same 16 regions on both sides of the module, I had to make Target definitions in this way. Target represents each region.

0 ·

701d27cf-02f0-47fd-b8c3-6256f60cb53f.png (840.9 KiB)

d58ff37e-9773-4fcb-908c-17af06faa5d5.jpeg (229.9 KiB)

Felix Möhlmann Kadircan T commented · May 02, 2023 at 01:27 PM

I realized why the labels were set that way. I wanted to point out that the duplicate labels are the reason your current logic is not working as expected.

As Mischa also pointed out: You list is not actually needed and just makes the logic unnecessarily complex.

Edit: Here's an updated version without the list. I rebuild parts of your Process Flow to make it hopefully work as it should. Notably, the chute status is now updated when an item is pending for transport to a chute, not when in enters (as that could allow too many items per chute at a time)

wsort5223-fm.fsm

0 ·

wsort5223-fm.fsm (124.7 KiB)

Kadircan T Felix Möhlmann commented · May 03, 2023 at 06:09 AM

Thank you very much. This model solves my problem. I understand better how I should think when building such a model.

0 ·

Answer 2 · 2023-05-02T11:17:29Z

Mischa Spelt answered May 2, '23 Kadircan T commented May 3, '23

Sometimes you have two chutes with the same product. Then when your operator tries to collect a batch of three, it gets two items from one chute and a third item from another chute.

It's better to avoid the list and in the Load subflow, directly reference the items you want to load when the chute is full:

1683026244684.png (28.5 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.

Kadircan T commented · May 03, 2023 at 06:07 AM

Thank you very much for your support, I understand what the problem is.

0 ·

question