How to use TimeTable along Down Behaviors in ProcessFlow

Question

question

Ghadir S asked Apr 11 2023 at 11:31 AM Felix Möhlmann commented Apr 12 2023 at 7:04 AM

How to use TimeTable along Down Behaviors in ProcessFlow

Hi,

So, I created 3 differents shift/group (each contains 4 operators and work 8h/day). I set a schedule for each shift with TimeTable & Down Behavior. I also created a group which contains all operators and added to Resource Operator.

However, when I launch the simulation, the system doesn't work properly and after a while, I get some errors.

Can anyone analysis my model and tell me what I'm doing wrong please ?

I should also mention that without any timetable or schedule, the model works perfectly.

LigneP3_V5.fsm

Software Version:

FlexSim 21.2.4

processflow timetable down behavior resource operator

lignep3-v5.fsm (7.1 MiB)

______

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 · 2023-04-11T14:34:08Z

Felix Möhlmann answered Apr 11 2023 at 2:34 PM Felix Möhlmann commented Apr 12 2023 at 7:04 AM

The state of an object doesn't stop a token from acquiring it as a resource. As long as it is in the group it can be acquired.

One way to deal with this is to use the query field to filter for actually available operators. First, you have to define a new field in the advanced properties of the Process Flow resource. This could be a label that denotes whether the operator is currently busy or not. In the attached example I simply check if the operator has an active task sequence. If not, the IsIdle field will have a value of 1.

In the acquire activity, I use this to filter for available operators. Since a request will not automatically reevaluated when the operator finishes a task sequence, I opted to have the tokens enter a Wait for Event activity which sends them back to the Acquire activity whenever a resource is released or a group member becomes available (finishes a task sequence).

Lastly I also changed your Process Flow to use task sequences instead of individual tasks. This means the operators will not interrupt their current task for a break. If you do want partial tasks to be possible (one operator starting a manual processor and passing to another operator) you will have to use preemption activities. (Have a separate token listen for the On Stop event of the time table for the respective operator and then preempt the token away from the current flow to acquire a new operator.)

lignep3-v5-fm.fsm

1681223246054.png (10.0 KiB)

1681223298546.png (7.8 KiB)

1681223570775.png (4.4 KiB)

lignep3-v5-fm.fsm (7.1 MiB)

· 4

Ghadir S commented · Apr 11 2023 at 7:27 PM

I'm honstly speechless, thank you. I'm starting to understand what you did. So you're telling me that if I want to test wheter the operator is busy or not in the "state of an object" I have to write down this code ?

!objectexists(value.as(TaskExecuter).activeTaskSequence)

I assume with a code similaire to this, is how I can test if an object entered in a queue or not..
I have so much to learn despite everything I did and watched/read on internet and it's not easy. So if I may ask. Is there any book I can buy despite everything we have on internet ?

0 ·

Felix Möhlmann Ghadir S commented · Apr 12 2023 at 6:18 AM

The expression I used specifically checks if the task executer has an active task sequence. Another possible way would be to check the object state (idle, busy, travelling, etc...)

value.as(Object).stats.state().value == STATE_IDLE

The only book I know of is the one available on the FlexSim site.

https://www.flexsim.com/store/

The previous (4th) edition can be viewed here:

https://www.flexsim.com/wp-content/uploads/sites/2/2020/06/FlexSim-Primer_2020-Update-1.pdf

A decent starting point to understand more about the coding possibilities in FlexSim is in my opinion the online manual.

https://docs.flexsim.com/en/21.2/Reference/CodingInFlexSim/WritingLogic/WritingLogic.html

Some more information about how the used expression works:

The command objectexists() checks if the passed in parameter is a valid pointer to a treenode.

When a Process Flow resource is connected to a group it internally becomes a list which is where the feature to define the fields comes from. For lists, value is a reference to the thing that was put onto the list (so in this case the operators). This reference then gets cast as either a Task Executer class variable or an Object class variable to be able to access the class specific properties/methods. These can also be found in the manual in the FlexScript class reference section.

https://docs.flexsim.com/en/21.2/Reference/CodingInFlexSim/FlexScriptAPIReference/TaskExecuter/TaskExecuter.html

0 ·

Ghadir S Felix Möhlmann commented · Apr 12 2023 at 6:59 AM

I truly appreciate your effort and time. I don't know how else I could thank you so I gave all the point I had.

Hopefully one day I can reach your level. Have a nice day @Felix Möhlmann

0 ·

Show more comments

question