How to randomly pick a resource meantime consider resource availability

Question

question

Jingyong P asked Nov 13, '20 Jason Lightfoot commented Nov 17, '20

How to randomly pick a resource meantime consider resource availability

Pick_A_Resource.fsmI have following situation want to fix in the process flow.

I have many identical tools were grouped in different Tool Groups. Each group has different tool count. Each resource has the same opportunity to be picked by next token/request as long as at least one tool is available in that group. In other words, I want the model has the capability to check resource availability before request.

For example, in the screenshot, Tool Group 1 and 2 already have backorders, so I want model to pick next resource from Tool Group 3 or 4 with equal opportunity.

Thank you in advance,.

Software Version:

FlexSim 20.2.3

flexsim 20.2.3 pick resource

1605309078875.png (52.8 KiB)

pick-a-resource.fsm (32.8 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-11-17T15:13:45Z

Jason Lightfoot answered Nov 17, '20 Jason Lightfoot commented Nov 17, '20

Here's a pure process flow example made to do something similar to what you descrive - but it digs into the tree so may not work in future releases or instanced process flows.

pick-a-resource_jl2.fsm

Better would be having tool objects in the model or tokens for the resources where capacity/availability can be tracked not only by those tools in use but also by the allocation/queue and expected processing times.

pick-a-resource-jl2.fsm (38.1 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.

Jingyong P commented · Nov 17, 2020 at 04:48 PM

Hi Jason, @jason.lightfoot

Thanks for your reply. somehow I could not open your file. It gives me the following error message:

exception: HTML Frame Load Error 102 Encountered: Frame load interrupted

0 ·

Jason Lightfoot ♦♦ Jingyong P commented · Nov 17, 2020 at 05:59 PM

Sorry - my fault I think - had the wrong version. Try this one.

pick-a-resource_jl3.fsm

0 ·

pick-a-resource-jl3.fsm (38.2 KiB)

Answer 2 · 2020-11-14T15:23:30Z

Ralf Gruber answered Nov 14, '20 Jingyong P commented Nov 17, '20

JingYong,

would you mind to explain the background of your setup? If you do not care, from which group a resource is acquired, why do you split into separate groups at all? I am not sure, if I understand what you´re aiming for.

Thx

Ralf

· 4

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.

Jingyong P commented · Nov 16, 2020 at 05:34 PM

Hello Ralf, @Ralf Gruber

Apologize if my 1st model confused you. Allow me to explain the purpose of this model. I also updated the model as well.

Large box can be processed on any of the tool groups. But Small box can only be processed on tool group 1 or 3.

In other words, I want to model to have dedication based on token labels. In my case,

Large Box --> Tool group 1, 2, 3, or 4

Small Box --> Tool group 1 or 3.

Please let me know if I am over complicated this problem.

Pick_A_Resource ver.2.fsm

0 ·

Ralf Gruber ♦ Jingyong P commented · Nov 17, 2020 at 10:18 AM

JingYong,

again: When then Small box can use Tool group 1 and 3, is there any reason not to combine those into 1 group? The same applies to 2 and 4.

However, in your case where you want to be able to check if a tool is available before pulling it, I would not use resources at all:

I would put the available tools on a list, because the "Pull from List" activity allows you to leave entries on the list after the pull and you can create more complex SQL queries for your pulls. If after evaluation of the pull you like the result, you can use a second pull where you actually pull the tool from the list.

Does that make sense?

Good luck

Ralf

0 ·

Jason Lightfoot ♦♦ Ralf Gruber ♦ commented · Nov 17, 2020 at 02:19 PM

And you can use Max Wait Timer in case your first query might not match anything and you can then run a different query in a second pull.

0 ·

Show more comments

question