Operator group with state change event troubleshoot

Question

question

G C asked Jan 18 2017 at 11:55 AM G C commented Jan 31 2017 at 7:38 PM

Operator group with state change event troubleshoot

I have a backorder re-evaluation event on my operators and they should be pushed to the list (see under "MainFlows" "opVaOutGrp" under the advanced view). I use this to acquire an idle "opVa" operator based on "isIdle" expression. It seems to work fine but will eventually break and only 1 of the 3 operators will be re-evaluated (seems to be after my "BatchAndTransport" subflow is used??).

If you watch the "opVa" operators after the "VaOut1" "routingNumber" process (see globaltable "processControl") this is where it starts to go haywire.

I can't for the life of me figure out what I am doing wrong.

Software Version:

FlexSim 16.0.6

process flow groups

help.fsm (860.2 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 · 2017-01-18T21:37:03Z

Jacob Gillespie answered Jan 18 2017 at 9:37 PM G C commented Jan 31 2017 at 7:38 PM

When I run your model these two tokens are quickly stranded here trying to Acquire stnMannix1.

As you can see the selected token has Acquired opVaOut1 and the other token has opVaOut2. These two operators are forever waiting for stnMannix1 to have no content but it never empties.

So it seems your problem isn't the "isIdle" expression. I hope this helps you figure out your problem.

troubleshoot.png (30.2 KiB)

· 3

Jacob Gillespie ♦ commented · Jan 31 2017 at 7:29 PM

@G C I'm not sure how you got it working. Following your description didn't fix the issue for me.

The reason these two tokens are never able to acquire the station is because they use this query:

The problem is that this is never reevaluted. To make it reevaluate you need to click the advanced button under the resource's menu and then set a Back Order Reevaluation Event under the Back Orders tab of the properties window.

2 ·

query.png (9.2 KiB)

backorderreevaluation.png (18.1 KiB)

G C Jacob Gillespie ♦ commented · Jan 31 2017 at 7:38 PM

Yes, sorry I never followed up with this, but that is how I eventually resolved this as well.

0 ·

G C commented · Jan 18 2017 at 10:16 PM

So I added stnMannix1 into its own group (even though there is only 1) and re-referenced the corresponding activity (under "MainFlows") and now it seems to be working. However, I don't understand why I had to make it a group.

0 ·

question