Operator Task Sequence: Wait Until 1st Task is done

Question

question

komalkoli asked Jun 16 2024 at 1:15 AM Logan Gold commented Jul 03 2024 at 6:51 PM

Operator Task Sequence: Wait Until 1st Task is done

Here is the process flow for an operator:

Task 1: Operator waits until 100 items arrive at Queue1 and move these items

Task 2: After finishing 1st task, same operator move 50 items from Queue2

50 items arrive at Queue2 well before 100 items arrive at Queue1. So, operator is moving to Task 2 as soon as 50 items arrive at Queue2 & then completing Task 1. I would like him to finish Task 1 first and then complete task 2.

I tried Preempt option, priority option, and task sequencing option but it did not work. What is best way to sequencing the task 1 and then task 2?

Software Version:

FlexSim 24.1.0

operator task sequence priority

· 3

Felix Möhlmann commented · Jun 17 2024 at 8:57 AM

How do you control the operator so far? In a Process Flow it should be easy to set up two sequential task sequences for this.

0 ·

komalkoli Felix Möhlmann commented · Jun 17 2024 at 2:19 PM

I am using process flow. With the triggered source, I have two different task sequences. One for Task1 and another for Task2.

Can you give example how would you do two task sequences?

0 ·

Logan Gold ♦♦ commented · Jul 03 2024 at 6:51 PM

Hi @komalkoli, 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 · 2024-06-17T14:41:12Z

Felix Möhlmann answered Jun 17 2024 at 2:41 PM Felix Möhlmann edited Jun 19 2024 at 7:32 AM

If the tasks have to happen in a fixed sequence then build them as a single sequence. You can use lists to check for the needed quantity of items, so they can still accumulate independently without having to immediately start the transport when the threshold is reached.

transport-sequence.fsm

transport-sequence.fsm (33.9 KiB)

· 4

komalkoli commented · Jun 17 2024 at 2:54 PM

Thanks for your quick response!

In your example, you have used same source for Queue 1 & Queue 2. For my case, I have two different sources respectively for Task 1 & Task 2.

Can you send same example with two different sources and use of operator?

0 ·

Felix Möhlmann komalkoli commented · Jun 18 2024 at 6:11 AM

I don't see how the number of queues would have an impact on the logical structure. And using an operator just means to replace the Move activity with a task sequence to transport the items.

transport-sequence_1.fsm

0 ·

transport-sequence-1.fsm (40.6 KiB)

komalkoli Felix Möhlmann commented · Jun 18 2024 at 1:43 PM

Thank you for your response!

Please see attached picture how my process works. I have two different sources for two tasks. I want operator to pick items from Queue1 first and then from Queue2, no matter if all items at Queue2 arrive first. I don't know how I can use "Lists" with two different sources?

0 ·

queue-priority.png (40.7 KiB)

Show more comments

question