Back order can not pull "age > 10" when use List

Question

question

jing.c asked Jul 07 2016 at 3:06 AM anthony.johnson commented Jul 07 2016 at 1:55 PM

Back order can not pull "age > 10" when use List

Hi! everyone

You can see my model attached. I want Processor10 can only pull the item in any queues who stays more than 10s. But, it seems not work. Is it the List Setting error or SQL error?

I had tried to use "WHERE queueSize > 3", and it works well, but "age > 10" can not work

cannotpullv16.fsm

Software Version:

FlexSim 16.0.1

list sql backorder

cannotpullv16.fsm (25.4 KiB)

· 1

______

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 · 2016-07-07T04:00:08Z

anthony.johnson answered Jul 07 2016 at 4:00 AM anthony.johnson commented Jul 07 2016 at 1:55 PM

The problem is that the value of your WHERE clause will change while the back order is active. In such cases, you need to set up back order re-evaluation events, so the list will know when to re-evaluate the back order's WHERE clause.

· 2

jing.c commented · Jul 07 2016 at 5:26 AM

Thanks @anthony.johnson

I will follow your advice and read this part in User Manuals. Before that Can you explain why "WHERE queueSize > 3" can work well while this WHERE clause also change while the back order is active?

0 ·

anthony.johnson ♦♦ jing.c commented · Jul 07 2016 at 1:55 PM

Using WHERE queueSize > 3 suffers from the same issues. It just looks like it's working right because when a fourth box enters a queue, it will be pushed onto the list. Pushing onto a list will trigger back order re-evaluation for THAT item pushed onto the list. This means that the back order will see the fourth item and pull it because the fourth item will satisfy the WHERE clause. However, it does NOT re-evaluate the back order for the first three items again. Maybe that's how you want it to happen, but I would assume that when the queue gets above 3 you want to pull the first (or oldest) item from the queue. In order to do that, you would have to add a back order re-evaluation event associated with the OnEntry event of up(value) (or, the queue's entry event).

2 ·

question