question

Aaupadhye avatar image
0 Likes"
Aaupadhye asked Natalie White commented

Possibility of Using Two Connectors without using Decide

Hi all,


Technically my model works fine right now but there is something that will be an issue later on. I want a task sequence to be triggered on entry of a box in box station A, and a different task sequence to be triggered on entry of a box in box station B. Is there a way to route the process flow to two different task sequences without having to use the Decide block?


WCOCModelDraft3.fsm

FlexSim 23.0.8
processflowtasksequence
wcocmodeldraft3.fsm (74.6 KiB)
· 9
5 |100000

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

Julie Weller avatar image Julie Weller commented ·
Hey @Aaupadhye! Do you want it to choose still or just run both at the same time? You could use either the Create Tokens activity or the Split maybe, depending on what you want to do
0 Likes 0 ·
Aaupadhye avatar image Aaupadhye Julie Weller commented ·

I would have it choose based on if the box enters the box station. So if the box enters boxing station A, then the first task sequence will be ran. When the other box enters packing station B, then the other task sequence will be ran.

0 Likes 0 ·
Julie Weller avatar image Julie Weller Aaupadhye commented ·

You would probably want to experiment with using the create tokens activity then and the activity by case clause, you'll also probably want to add a sink. You might have to write some custom code to do it. Just curious, why won't a decide work?

1688151694874.png

0 Likes 0 ·
1688151694874.png (60.0 KiB)
Show more comments
Natalie White avatar image Natalie White commented ·

Hi @Aaupadhye, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.

0 Likes 0 ·

1 Answer

·
Felix Möhlmann avatar image
1 Like"
Felix Möhlmann answered Aaupadhye commented

Nice to hear!.

I would still like to propose a different solution. If you add the queues to a group you can listen for the box entering any of them with a single Wait for Event activity. In the activity you can assign the triggering object to a label on the token and use it to send then token through the correct connector.

wcocmodeldraft3_fm.fsm


· 8
5 |100000

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

Aaupadhye avatar image Aaupadhye commented ·

Hi Felix, this was great. I was also wondering if I could apply the same logic to my pack stations, in which once an arrival is completely taken off either pack station, the items on the pouching buffer are sent to either one of them. However, is there a way to give packing station A priority when doing this? Thanks!packstationgroup.png

0 Likes 0 ·
Felix Möhlmann avatar image Felix Möhlmann Aaupadhye commented ·

As Jason suggests, you can use a list (or a resource that references the queues) to both manage the availability as well as priority.

I tried to build an example which hopefully depicts what you are trying to achieve.

wcocmodeldraft3-fm_1.fsm

2 Likes 2 ·
Aaupadhye avatar image Aaupadhye Felix Möhlmann commented ·

Hi Felix,


This was super helpful, and I even made some edits to it to better model what I want. My only question is once the spheres are put into the box/ tote/pallet, how can the operator bring this entire combination to the lone conveyor? Attached below are the edits I have made.


wcocmodeldraft3-fm-1.fsm

0 Likes 0 ·
Show more comments
Jason Lightfoot avatar image Jason Lightfoot ♦ Aaupadhye commented ·
You could instead push to a list and using sql's ORDER BY clause prioritize the pull using the attributes (priority label) of the value (packstation)
1 Like 1 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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