How to implement Time Tables

Question

question

LaurenK asked Dec 10 2024 at 11:35 PM LaurenK commented Dec 11 2024 at 4:50 PM

How to implement Time Tables

Hi Team,

Looking for a bit of help creating a time table to implement 2 breaks and 1 lunch. I created the tables, and added the dispatchers instead of individual operators (operators are tied to parameters). But I receive an error that notes the event time is in the past and I'm not sure how to correct this error. I also don't see the breaks added to how the operator spends their time on the dashboard graph I have (Op Time Spent).

Thank you,

Lauren

CB Model 7.fsm

Software Version:

FlexSim 24.2.1

time tables breaks

cb-model-7.fsm (260.6 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 · 2024-12-11T08:05:26Z

Felix Möhlmann answered Dec 11 2024 at 8:05 AM LaurenK commented Dec 11 2024 at 4:50 PM

I don't get any errors when running the model. Not sure where those came from.

By default the down times in the time tables set the operators to the "Scheduled Down" state. In the default state table this state is "Excluded", meaning it does not appear in utilization charts. You can either change that setting or choose a different state for the down times.

If the down times apply to the same set of objects then there is also not reason to put them into separate time tables.

capture1.png (66.1 KiB)

· 5

Paula LG commented · Dec 11 2024 at 8:15 AM

The "event time in the past" errors are only noticeable if you already have the system console open. I run the model and I'm definitely getting them too.

Eventhough I've been able to identify the cause (the A* Navigator, specifically the collision avoidance option), I don't know how to solve the issue. I also suspect it's affecting model repeatability, because it never happens at the same run time.

1 ·

Felix Möhlmann Paula LG commented · Dec 11 2024 at 8:54 AM

Thanks for the heads up. The model not being repeatable is actually caused by loading items from a conveyor without updating their location. The operators will travel to the last known location which depends on when the tote was last rendered and could be as far back as the start of the conveyor (where the location should be updated as part of the entry event).

After adding a code snippet to update the tote location when it is stopped, the model became repeatable and the error also didn't appear anymore. It also seems to be connected to using a finite acceleration/deceleration. Setting those to 0 also prevented the errors.

0 ·

capture1.png (15.7 KiB)

Paula LG Felix Möhlmann commented · Dec 11 2024 at 9:39 AM

Thank you, Felix! I'll try what you suggested on a model where I'm currently having a similar issue.

0 ·

Show more comments

question