How to attach event trigger to arrival time inside Schedule Source?

Question

question

Vedran RL asked Dec 31 2020 at 9:18 AM Jeanette F commented Jan 06 2021 at 2:24 AM

How to attach event trigger to arrival time inside Schedule Source?

Question.fsm

Software Version:

FlexSim 20.0.0

flexsim 20.0.0 arrivals schedule source

capture.jpg (191.9 KiB)

question.fsm (68.2 KiB)

· 3

Joerg Vogel commented · Dec 31 2020 at 9:43 AM

You can identify a second scheduled arrival by assigning a label value. You can assign a label value by source code and this code can send a message to get an event you can listen to. Or a next activity will evaluate this label to do something.

In fact there is already an event. It is called On Creation. But it is up to you to filter this event to be evaluated only for tokens that are created upon the second arrival.

0 ·

Vedran RL Joerg Vogel commented · Jan 01 2021 at 8:20 AM

Hi Jorg,

Thank you on answer , can you show me on one case how to do it? Thank you in advance and Happy New Year. :)

0 ·

Jeanette F ♦♦ commented · Jan 06 2021 at 2:24 AM

Hi @Vedran RL, was jason.lightfoot's answer helpful? If so, please click the red "Accept" button on their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 ·

______

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 · 2021-01-01T23:27:29Z

Jason Lightfoot answered Jan 01 2021 at 11:27 PM Jason Lightfoot edited Jan 02 2021 at 1:11 PM

Attached an example using a label on the process flow to record the time of the last arrival and thereby have a unique token created and retained for each arrival event, regardless of the number of tokens generated by the arrival.

DetectScheduleArrivalEvents.fsm

detectschedulearrivalevents.fsm (28.6 KiB)

question