Possibility of Using Two Connectors without using Decide

Question

question

Aaupadhye asked Jun 30 2023 at 5:39 PM Natalie White commented Jul 05 2023 at 8:58 PM

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

Software Version:

FlexSim 23.0.8

processflow tasksequence

wcocmodeldraft3.fsm (74.6 KiB)

· 9

Julie Weller commented · Jun 30 2023 at 6:10 PM

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 ·

Aaupadhye Julie Weller commented · Jun 30 2023 at 6:58 PM

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 ·

Julie Weller Aaupadhye commented · Jun 30 2023 at 7:02 PM

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?

0 ·

1688151694874.png (60.0 KiB)

Show more comments

Natalie White commented · Jul 05 2023 at 8:58 PM

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 ·

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2023-06-30T21:14:04Z

Felix Möhlmann answered Jun 30 2023 at 9:14 PM Aaupadhye commented Jul 05 2023 at 7:46 PM

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

wcocmodeldraft3-fm.fsm (75.1 KiB)

· 8

Aaupadhye commented · Jul 03 2023 at 3:59 PM

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!

0 ·

packstationgroup.png (38.6 KiB)

Felix Möhlmann Aaupadhye commented · Jul 04 2023 at 10:20 AM

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 ·

wcocmodeldraft3-fm-1.fsm (70.6 KiB)

Aaupadhye Felix Möhlmann commented · Jul 05 2023 at 6:57 PM

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 ·

wcocmodeldraft3-fm-1.fsm (77.5 KiB)

Show more comments

Jason Lightfoot ♦♦ Aaupadhye commented · Jul 04 2023 at 9:04 AM

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 ·

question