Operators connected to dispatchers

Question

question

Felipe T asked Oct 27 2017 at 3:01 AM Felipe T commented Nov 09 2017 at 3:08 PM

Operators connected to dispatchers

Hi!

I have been dealing with some modeling issues regarding the execution of tasks linked to processors and multiprocessors, via operators connected to dispatchers. In the model, there are several aligned processors with short operating times in which operators are intercalating between them. Is there any strategy I can use to hold the operators on the same processor until the end of the items on queue?

Thank you!

Software Version:

FlexSim 17.2.2

operator dispatcher

· 4

Michael Machado commented · Oct 27 2017 at 3:22 AM

Yes, there is some ways to take care of that, but, please, is it possible to share your model with us here in the answer's website to look at and provide more assertive answer to you?

0 ·

Felipe T Michael Machado commented · Oct 27 2017 at 3:14 PM

Yes, sure!

This is just an example, a tiny part of the process.

Thank you.

(You can also answer in portuguese)

exemplo-dispatcher.fsm

0 ·

exemplo-dispatcher.fsm (93.6 KiB)

Sam Stubbs ♦ Michael Machado commented · Nov 01 2017 at 1:22 PM

So just to understand your request. You are looking to hold the operator for the same item till the end?

0 ·

Felipe T Michael Machado commented · Nov 08 2017 at 12:11 PM

@Sam Stubbs, Yes, I'm looking to hold the operator at the same processor until the end of items on queue. Each processor in this sequence is equivalent to a manufacturing step in which the operators don't change place.

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 · 2017-11-09T10:09:07Z

Raja Sekaran answered Nov 09 2017 at 10:09 AM Felipe T commented Nov 09 2017 at 3:08 PM

Hi @Felipe T ,

Instead of using Dispatcher, Resource-Shared assets would be a better option to hold the operator at the same processor until queue becomes empty. I have attached the sample model. After acquiring the operator it will not release until queue becomes empty. I hope this will help you.

resource-shared assets.fsm

Thanks.

resource-sharedassets.fsm (54.5 KiB)

· 1

question