How to make operators only do certain jobs when any operator on break

Question

question

Yunjukuo asked Jul 10 2022 at 8:06 AM Jason Lightfoot commented Jul 13 2022 at 9:14 AM

How to make operators only do certain jobs when any operator on break

This model has 3 operators, and operators take turns to take a break according to the TimeTable setting. How to make operators(one not taking break) only do utilize task in the red area in the figure below when any operator is taking a break? (If there is a transportation task in the red area, the operator will not deal with it first.)

Only when no one is taking a break, will all operator be allow to do any task.

Because there are many Multiprocessors in the model, I do not consider using ProcessFlow to dispatch operators, and I hope to keep using Dispatcher to dispatch operators.

In the model, the items of Source1 will be processed through the yellow, orange and blue machines in sequence, and the finished products will be placed in "Finish_Product" (Queue).

The items of Source2 will pass through all the green machines in sequence and then enter Sink2.

OnlyDoCertainProcess_WhenOPOnBreak.fsm

Software Version:

FlexSim 16.1.2

operator dispatcher timetables

1657440273918.png (184.7 KiB)

onlydocertainprocess-whenoponbreak.fsm (34.3 KiB)

· 2

______

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-07-12T08:45:51Z

Jason Lightfoot answered Jul 12 2022 at 8:45 AM Jason Lightfoot commented Jul 13 2022 at 9:14 AM

Use two dispatchers and when a break starts/ends, use stopoutput/resumeoutput on one of the dispatchers to prevent it from issuing jobs.

(Please note your FlexSim version has reached 'end-of-life' status and we recommend you update to a supported version).

onlydocertainprocess-whenoponbreak_jl.fsm

onlydocertainprocess-whenoponbreak-jl.fsm (35.2 KiB)

· 4

Yunjukuo commented · Jul 12 2022 at 2:39 PM

Thank you. This solution solve my problem. However, I found that this solution doesn't work when I choose "Shortest Distance" rule on both dispatchers, I still can't figure out the reason until now.

Also, I'm curious that will one operator been connected to two or more dispatchers create any conflict or possible error?

Is it possible that two dispatchers assign tasks to same operator at the same time? If that happen, which task will operator do first?

0 ·

Andrew O Yunjukuo commented · Jul 12 2022 at 8:21 PM

Hi @Yunjukuo,

First, to answer your question about the Shortest Distance rule not working for the dispatchers, we would need to clarify if you are using Shortest Distance or Shortest Distance if Available. Shortest Distance does not take into account if the operators are busy or not, and will assign tasks to the operator closest to the destination even if they are on break. The issue may be fixed if you use Shortest Distance if Available, which does take into account a Busy status on an operator.

One operator can be attached to multiple dispatchers without error. By design, both dispatchers cannot assign tasks at the exact same time, so the system will prioritize whichever dispatcher's code executes first.

0 ·

Yunjukuo Andrew O commented · Jul 13 2022 at 7:31 AM

Thanks! This problem appear in "Shortest Distance" (not Shortest Distance if Available). So in conclusion, "stopouput(Dispatcher)" command won't work if choosing a dispatch rule that doesn't consider whether an operator is available?

Since the advance case I'm handling will assign specific operator to do specific jobs. That is, the dispatching rule is to assign the corresponding operator according to the job type, and do not consider if operator is available, if operator is on break the job will be delay.

In such case, is there any command like ""stopouput() " but can prevent dispatcher from output operator when not considering if operator is available ?

0 ·

Show more comments

question