Saves elapsed time in delay

Question

question

Omar Aguilera Rico asked Oct 11 2018 at 8:04 PM Omar Aguilera Rico commented Oct 16 2018 at 2:49 PM

Saves elapsed time in delay

Hi all.

I have a question for you, is there any default option in FlexSim, when using the "Release Token" that extracts the "token" that are inside the "Delay", is saved the time that elapsed?

For example, I have a "Delay" with time of 20 seconds, some activity triggers the "Release Token", but the "token" that was in the "Delay", only 12 seconds passed. My question is to know if there is any way to save the time that elapsed within the "token" or the time it took inside the "token" to complete the 20 seconds, is this possible?

I thought about doing the following example model but using a "User Event", for when the "Release Token" extracts the token from the "Delay" by means of an "Assign Labels", assign the time that was needed.

Is there any other way to represent this?

schedule-1.fsm

Software Version:

FlexSim 18.2.2

save save time

schedule-1.fsm (52.9 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 · 2018-10-12T11:00:54Z

Sebastian Hemmann answered Oct 12 2018 at 11:00 AM Omar Aguilera Rico commented Oct 16 2018 at 2:49 PM

Hey, doesn´t "Save Token Context" do what you are looking for? You have to store the data before you are Releasing the token and as soon as you are pushing it back with "Restore Token Context" , it starts from where ever it was released from.

· 3

Omar Aguilera Rico commented · Oct 12 2018 at 3:21 PM

@sebastian.hemmann I thought of "Save Token Context" only that I need a "Restore Token Context" but what I would be doing is returning it to its location from where it was extracted. If you notice in the model that you attach, what I'm looking for is to extract the "token" at the moment that "Operadora1" has a "Schedule Down" so that the other operator goes to the process ("Processor1") and concludes the pending activity I stop doing the "Operator1". What I'm looking for is that the "token" that I extracted from the "Processor 1" stream only saves the processed time information. Can you think of an idea, apart from the one that implements the simplest?

1 ·

Sebastian Hemmann Omar Aguilera Rico commented · Oct 15 2018 at 8:31 AM

Sorry, I had a look into your model but because it was not in english it was quite hard for me to understand!

So what I would do to hold it simple: Add an "assign label" before process starts and set the time of process start and planed processtime in a label. As soon the token is released (because the operator is going down) I would throw the token at first into another "assign label" that calculates the missing Processtime.

This would be quiet easy now, because you already have all needed information in labels!?

2 ·

Omar Aguilera Rico commented · Oct 15 2018 at 3:10 PM

Perfect, it's a very good idea what you tell me. There are fewer events that would have to be evaluated. In my case, assign a label of the time of the process, and be decrese by the User Event every second, when the Release Token is detonated, I assign the token a new label of the remaining time. You can tell that they are more events, and it is not the most viable. Very good idea @sebastian.hemmann!

0 ·

question