interpreting list synchronization

Question

question

Anggoro P asked Nov 17 2017 at 10:03 AM Mischa Spelt commented Nov 20 2017 at 1:42 PM

interpreting list synchronization

Hi, I have a question regarding how to interpret the captured result from my simulation

Here I have a plant, a DC, and demands. My idea is to model the DC in the form of list. Production is pushed ans stored in DC. When there is a demand, it will pull from the list (DC) if not available, it will be sink as lost sales. After I run it for a while. I got some tokens still in push to DC. Virtually, it seems that they haven't went inside the DC. Meanwhile, in DC, there are also several products stored.

After reading about list synchronization, it seems that my interpretation is wrong. Some tokens are still in push to DC because production rate is bigger than customer demand rate. If that is the case, is that correct if the total inventory = tokens still in push to DC + tokens in List: DC?

So, what exactly is tokens inside list: DC?

Thanks so much

@steven.hamoen

Software Version:

Choose One

list

a.jpg (38.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 · 2017-11-20T13:08:31Z

Mischa Spelt answered Nov 20 2017 at 1:08 PM Mischa Spelt commented Nov 20 2017 at 1:42 PM

Hi Anggoro,

The activity block at the bottom of your screenshot does not have a Sink activity. So even tokens that have been pulled from the list, will remain in the activity, simply because they have nowhere to go!

Also I don't understand the "Scrapping" activity - if I were you I'd have a look at the "max. wait timer" option on the pull activity. You can use that to reroute a token to an alternative destination (such as output connector 2) if the pull does not succeed within a given time.

· 2

Anggoro P commented · Nov 20 2017 at 1:37 PM

@Mischa Spelt

In another word, the number at the bottom just shows the accumulated tokens produced, doesn't it? And although some tokens have been pulled from the list, it doesn't mean that they merged with 'customer demand' tokens, right?

So it's better to make a sink below the push to DC activity, because it would only delete the tokens that have been pulled from the list.

Thanks Mischa!

0 ·

Mischa Spelt commented · Nov 20 2017 at 1:42 PM

Hi @Anggoro P. No tokens are getting "merged": what the customer demand tokens pull from the list is a reference to the production token: the pulled tokens continue going through their own flow (as you can see when you add another activity such as a Delay or Custom Code below the Push) and the pulling tokens just point to them. If you look at the Pulled label on the Customer Demand tokens, you will see that it says something like "id: xxx" - this is not really a token but basically just the unique ID that all tokens get when they are created. If you add a Sink, you will see the reference change to "0x0": if you destroy the tokens that the pullers point to, they won't be pointing to anything anymore! If you want to keep the pulled reference valid, you should keep the tokens that you put on the list alive until all pullers are done with them.

0 ·

question