Acquire closest task executer on process flow

Question

question

Leandro Meirelles asked Apr 30 2024 at 2:56 AM Felix Möhlmann answered May 03 2024 at 7:24 AM

Acquire closest task executer on process flow

Hello,

I have a group of task executer and a group of operators, when I acquire both for a task, I need to acquire the task executer which is closest to the operator. How do i do that on process flow? I believe I need to write a query to filter it on the acquire block, but i don't know how.

Hope I was clear enough, otherwise I'll link my model and give more details on comments bellow. Thanks!

Software Version:

FlexSim 24.1.0

task executer aquire closest

· 4

Joerg Vogel commented · Apr 30 2024 at 7:29 AM

You choose first your operator. When you acquire a taskexecuter, you pass in a puller. This must be in a way be able to reference a location of your operator in a dynamic field of your resources to compute a distance to list values. Then you can order by this distance field the list values and acquire a resource.

0 ·

Leandro Meirelles Joerg Vogel commented · Apr 30 2024 at 5:51 PM

I created a list "Carts list" and placed a "pull from list" before the acquire and and "push to list" before the release. But when i change the resource "Carts" to use the list instead of the group it gets errors, what I am doing wrong?

Follows attached the model: problem acquire.fsm

0 ·

problem-acquire.fsm (6.8 MiB)

Gustavo Teodoro Leandro Meirelles commented · May 02 2024 at 2:25 PM

@Leandro Meirelles Which errors are happening? I ran the model and no errors appeared in the FlexSim console.

0 ·

Show more comments

______

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-05-03T07:24:00Z

Felix Möhlmann answered May 03 2024 at 7:24 AM

You are correct, you do not need a separate list. A resource that is linked to actual objects already creates a list for those internally and functions the same, just with fewer settings in the Acquire activity then in Pull from List.

One of those missing options is the ability to set who the "puller" is, so you need to shift the reference in the list field code. (The base for the list expression is the "distance" option from the "Fixed Resource" category)

capture1.png (48.4 KiB)

question