Problem with task sequence (task executor)

Question

question

Paula P7 asked Feb 03 2022 at 9:20 AM Paula P7 commented Feb 07 2022 at 1:25 PM

Problem with task sequence (task executor)

Hello!

I have a problem with task sequence. The idea of this model should be: task executer delivering one palette when the process is finished and just after that taking back that pallete which is done.

All processes have different processing time. I tried to use the preempt option and prioritize tasks. Everything works perfectly until finished process interrupts delivering palette to the sink (because I prioritized delivering palette, if I don’t task executer is delivering and collecting pallets separately). Any ideas how to fix it?

The problem starts about 9800 s (what’s more the task executer takes more than one pallete though it’s capacity is 1).

The model is based on standard 3D model with connections. :)

model2.fsm

Software Version:

FlexSim 20.2.3

processflow tasksequence taskexecutor

model2.fsm (225.0 KiB)

______

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 · 2022-02-03T13:45:29Z

Felix Möhlmann answered Feb 03 2022 at 1:45 PM Paula P7 commented Feb 07 2022 at 1:25 PM

The transport capacity only really matters for the "Break To" option, which determines whether another item should be loaded before delivering the current one. Preempting a task will cause the task executer to work on the new task regardless of current load.

That said, I don't think preemption makes a lot of sense in your model, since the task executer travels on a strict one way circuit anyway and the source and sink are close to each other. So unloading an already loaded empty pallet before bringing a new one costs very little time.

My suggestion would be to only increase the priority of bringing new pallets but not preempt. That way, if there are multiple tasks to choose from, delivering new pallets is always done first.

· 3

Paula P7 commented · Feb 07 2022 at 8:40 AM

Thank you for your answer. Unfortunately increasing priority doesn't work. The idea of this model is to load new palette when the process is finished, so the task executor has to exchange pallets. When increasing priority that doesn't work. Just in the beginning task executor takes green (processed) palette and delivering it to the sink, then he's loading a new palette. Also while task executor is idle he should be waiting around source to be ready to take palette.

0 ·

Felix Möhlmann Paula P7 commented · Feb 07 2022 at 12:10 PM

So what needs to be done is to make sure that the task to get a new pallet is created before the task to retrieve the old one. In the first attached model I do this by placing a floor storage with a minimum dwell time of 0s between the processors and their respective queues. This 0s delay before the pallet enters the queue makes sure the logic to bring a new pallet to the now empty processor fires first.

I also have the source move the fresh pallets into a queue first, so more than one processor can request one at a time (a source is limited to one outgoing item at a time).

The only instance where this will likely not work is if two or processors finish at the exact same time (unlikely but theoretically possible). In that case the transport would first bring all new pallets before retrieving the old ones.

model2_fm1.fsm

In this second model I instead use the "On Receive Task Sequence" trigger to listen for a new task to bring a new pallet. I then check if there is an item in the respective and add tasks to bring it back to sink to the task sequence manually. This will work as long as these are the only tasks the transport receives. Otherwise more checks would be needed to determine if the received task sequences does involve bringing a new pallet.

model2_fm2.fsm

In both models I also use the "On Resource Available" trigger to have the transport drive to the source if there are no pending tasks.

0 ·

model2-fm1.fsm (106.6 KiB)

model2-fm2.fsm (97.1 KiB)

Paula P7 commented · Feb 07 2022 at 1:25 PM

Thank you! :)

0 ·

question