Priority using a list in process flow

Question

question

Veera V asked Jun 5, '20 tannerp commented Jun 5, '20

Priority using a list in process flow

So the idea behind this process is that I have three queues which are assigned to labels and are pushed into a list of items. I want my resource(the robot) to pick all the items from a particular queue first, before it goes to another queue to pick items.
The idea is to push all the items/tokens into a list and arrange them in a ascending order to pull the tokens which have labels numbered 1, then move tokens which have 2 and then 3. But there are some random errors which I am unable to debug.
Is there a better way to do this?

This is the error: Priortizing error.PNG

This is the flexsim file: Priortizing.fsm?
Note: I need to use process flow. This is a small logical part of a bigger project.

Software Version:

FlexSim 18.1.2

process flow flexsim 18.1.2 prioritization

priortizing-error.png (74.5 KiB)

priortizing.fsm (46.2 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 · 2020-06-05T18:02:54Z

tannerp answered Jun 5, '20 tannerp commented Jun 5, '20

@Veera V,

You're really close to getting this to work. All that's missing is that you're pushing the token to the list rather than the item, as shown in the image below, so there's not a "Type" label field. This is why the Pull from Lists aren't able to access that field.

If you push the items themselves, this should be solved and work how you want it to. You could also do this by pushing the token, but then when you pull the token, you'll be referencing a label called "Type" on a label called "pulled" and then it becomes cumbersome. But know that that's also an option.

I also changed and cut out a few unnecessary things in the Process Flow so it was a little more simple.

priortizing_1.fsm

priortizing-1.fsm (42.7 KiB)

· 2

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.

Veera V commented · Jun 05, 2020 at 06:19 PM

Thank you very much! I think this works for me. So here the mistake was that I am unable to push the physical item onto the list right? I am just sending the token instead of the actual item. So it is trying to access the label instead. Does that make sense?

0 ·

tannerp Veera V commented · Jun 05, 2020 at 06:31 PM

Sorry, I may not have been very clear in my initial answer. You can either push the item or the token, but the list needs to be set up accordingly. For example, if I push the token and the "Type" label is on the token, I need to make a label field in the list called "Type". Then, when I pull from the list, I need to remember that I'm referencing the token that references the item. A pulled item would be accessed by "token.pulled.item" rather than "token.pulled" because you're going one level deeper. Does that help?

0 ·

question