stat distribution cycle time from code

Question

question

Bryan Suharik asked Feb 07 2017 at 10:49 PM Bryan Suharik answered Feb 08 2017 at 1:13 AM

stat distribution cycle time from code

Hi,

I'm having trouble with the cycle time changing based on distribution coded in?

I have:

return normal(gettablenum("ProcessTime",getitemtype(item),2),20);

This is assigned to the cylcetime as script. It asks for a normally distributed number in which the Mean value is from a global table of row itemtype.

the problem is....the process doesn't select a different cycletime value for every new flow item, it just keeps processing for the value defined in the global table.

If the average is 50 hours, i need it to sometimes process for 50 hours, other times 60 hours, other times 40 hours etc.

Is it better to assign this code for the onEntry trigger?

Thanks for the assistance.

Bryan

code distributions cycle time

· 2

Matt Long commented · Feb 07 2017 at 11:05 PM

Seems to work just fine. Perhaps you can share your model so we can see what's wrong?

0 ·

Bryan Suharik commented · Feb 07 2017 at 11:32 PM

@Matt Long

Hi Matt, Attached is the model, but its quite complicated as the entire model is built from GUI1

To see the code, it's on the OnPress event of the SetUp Model of the GUI1. Specifically Row 694 is what i'm talking about where i do 2 things. First, assign the num of operators depedning on the item type and then define the Normal(gettablenum.... to define the cycle time.

But for some reason, everytime the unit comes through, it has the same time. I only know this because my dashboard doesn't change when i run the model. Always has the exact same average time by unit type. If it was a distribution, this number would change everytime but still be close.

Thanks, for the Help!denton-iap-model.fsm

0 ·

denton-iap-model.fsm (210.3 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-02-07T23:41:21Z

Matt Long answered Feb 07 2017 at 11:41 PM Matt Long commented Feb 08 2017 at 12:08 AM

Looks like you're doing some pretty crazy stuff. Might want to rethink how you're implementing your auto-build.

If it is for some reason necessary to add code to triggers, you need to include the following after setting the string value of the node:

switch_flexscript(theNode, 1);
buildnodeflexscript(theNode);

· 2

Bryan Suharik commented · Feb 07 2017 at 11:50 PM

@Matt Long

Hi Matt, i think that specific node is already flexscript and may not need to be switched. I tried your suggestion and i still have the same issue. When I run the model the overall PM TAT times from the dashboard are the same everytime. On Each run, they would be different if the distributions were taken into effect.

0 ·

Matt Long Bryan Suharik commented · Feb 08 2017 at 12:08 AM

The TAT numbers seem to change just fine each time I run the model.

Did you forget to turn off Repeat Random Streams?

1 ·

tat1.png (25.9 KiB)

tat2.png (26.1 KiB)

Answer 2 · 2017-02-08T01:13:45Z

Bryan Suharik answered Feb 08 2017 at 1:13 AM

That was it! Thank you sir!!!

Bryan

question