How to make one token to cycle in a process flow, create objects, push them to a list, and leave the activity?

Question

question

sanaz karamimoghaddam asked Nov 07 2016 at 5:05 AM Sam Stubbs commented Nov 08 2016 at 8:23 PM

How to make one token to cycle in a process flow, create objects, push them to a list, and leave the activity?

Hi,

I use a process flow ("Transportation Process Flow") in which the Task Executers are being pulled from a list at first, load and transport the items, and then are being pushed back to the list. The TEs are created using a process flow ("Task Executer Creation") and are being pushed to the TE List to be used by the first process flow. Now, I want to create the Task Executers one by one, and each creation should be at the same time the item needs to be loaded.

For this, I thought of a Process flow ("Schedule TE Creation") which creates one token at time 0, and sends it to a wait for event activity. Whenever a request for a TE arrives at the TE list, the token proceeds the next activity which is create object. Then using a Decide activity, the token decides if the number of TEs that are created in the process flow has reached the required number (Using two Process Flow Labels.) If that is the case, then the token sinks after pushing the last TE to the list. If not, The token goes back to the Wait for event activity and cycles again in the process flow.

When I tested this process flow, the token never leaves the Wait for event activity. When I Delete the decide activity, the token then never leaves the push to list activity, and it won't cycle in the process flow. I tried the "use max timer" with zero wait time option, and "Keep on Early Release", but it didn't work. I have attached an example of what I use, and what the new process flow would possibly look like. I would appreciate any ideas or suggestions than can solve this problem.

Thanks. eventtriggered-te-creation.fsm

Software Version:

FlexSim 16.2.1

Software Version:

Choose One

process flow push and pull list

eventtriggered-te-creation.fsm (41.1 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 · 2016-11-07T15:28:10Z

Sam Stubbs answered Nov 07 2016 at 3:28 PM Sam Stubbs commented Nov 08 2016 at 8:23 PM

The reason why it wasn't leaving the Wait for Event Activity, is because it wasn't connected to the Create Object activity. The line must have been deleted at some point.

It doesn't leave the Push to List activity, because the TE is never getting pulled from the list. The reason for this, is because in your Schedule TE Creation, you are pushing your created TEs onto the list under Partition 2, and in your Transportation Process Flow, you are pulling TEs from the list based on Partition 1. So, I changed the partition in the TE Creation to 1 as well.

However you may want to check, and make sure your Decide logic is working how you want it. I'm not sure if it's doing what you want it to, as the token never seems to leave the system, it seems to keep looping through and creating more TEs as the model runs. So you might want to change your condition there.

eventtriggered-te-creation.fsm

eventtriggered-te-creation.fsm (41.3 KiB)

· 2

sanaz karamimoghaddam commented · Nov 07 2016 at 6:38 PM

@Sam, Thanks, the problem with the decide was a bad object reference in the labels. Now I ran into another problem. First, I want the "Schedule TE Creation" Process Flow to continue creating TEs regardless of availability of other TEs, until the number of created TEs reach the limit. The items should get transferred with the newly created TEs during that time. To do this I guess I cannot use "On back Order Input Change" event on the wait for event activity. I tried to use "On Pull" Event, but I got the error of: "Bad Task Sequence/Task Executor reference" on the travel to loading area activity. I'd appreciate any comments on this too.

3573-eventtriggered-te-creation.fsm

0 ·

3573-eventtriggered-te-creation.fsm (41.4 KiB)

Sam Stubbs ♦ sanaz karamimoghaddam commented · Nov 08 2016 at 2:43 PM

What's the limit of number of TEs? I'm still a little unsure of how you are determining this. (I noticed your label was set to 5, is this just a hard set limit?) Also, If you are creating TEs to match the incoming items, could you have the Wait for Event listen to the incoming items on the Item List instead of the TE list? I don't know exactly where your final project is headed or what you have in mind though, so I don't know exactly what to advise you on.

I've reattached your model, and I rearranged the Process Flow a little, see if this is more along the lines of what you're looking for.

eventtriggered-te-creation.fsm

0 ·

eventtriggered-te-creation.fsm (41.6 KiB)

question