Repeating Tasksequence

Hello FlexSimers,

I need to know the best way to accomplish the following with the attached model. I need the transporter to repeat the following delivery cycle once per month:
1) Dropoff and Pickup at Site 1B
2) Dropoff and Pickup at Site 1A
3) Dropoff and Pickup at Site A
4) Dropoff and Pickup at Site B

When the sim starts there will be nothing to drop off for steps 1 and 2, nor to pickup at steps 3 and 4. I'm using network nodes because I need to enter in a virtual distance between the three sites.

My original method did not end up working so I'm approaching this with a blank slate to see what you have in terms of ideas. I eventually need to incorporate item type footprint and transporter capacity so if you have thoughts on that, I'd appreciate it.

Regards,

LG

Lorrenzo Guiterezz,

Can you explain in detail,What you want?

Hello Lorenzo,

There are many ways to do this, i.e. you could close all pick up output ports at reset and open the first once per month, using a user event. At the exit of the last item, close the port again and open the port of the next pick up station.

My answer was created without taking a look at your model. After opening your model I am not sure what you want to do, so I am not sure my answer will help you...

Esther

Thank you arunkrmahadeva - Sorry for the confusion. I hope this helps: I have four queues, two at Site 1 which are 1A and 1B. The other two are Site A and Site B. I need the transporter to repeat a monthly schedule of:
1) Dropping off and Picking up at Site 1B, then
2) Dropping off and Picking up at Site 1A, then
3) Dropping off and Picking up at Site A, then
4) Dropoff and Pickup at Site B

This needs to happen once per month.

Thanks

LG

Thank you Esther. I'll try implementing your suggestion. So I guess I would have the user event repeat every month?

Yes Lorenzo, repeat the user event every month is what I mean.

Lorenzo,

I am attaching your model that I have modified. I changed all the Use Transport code (in the Flow tab) of each Pickup queue to be 0 (so the queues still know to use a transport, but the 0 indicates there is a custom task sequence being used).

Then, I created a User Event that sends a message to Transporter21 every so often. In the example, it is every 100 seconds starting at 50 seconds. This message sends a number 1 as message parameter 1, and this parameter is used as part of a switch statement in the OnMessage trigger of Transporter21.

The OnMessage trigger of Transporter21 should be somewhat straightforward. I have also included comments to help explain. It basically creates a task sequence for each queue, one at a time. The task sequence will have the transporter either pick up or drop off any items at the current queue. It also sends the transporter to the next queue and (upon arrival) will send a delayed message of time 0 to itself to start the task sequence for the next queue.

Thanks Logan. I'm learning a lot through the model you posted which I honestly only noticed was posted on Friday so my apologies for the delay. I'm dissecting it bit by bit to fully understand it. Thank you.

Originally Posted by logangold

Lorenzo,

I am attaching your model that I have modified. I changed all the Use Transport code (in the Flow tab) of each Pickup queue to be 0 (so the queues still know to use a transport, but the 0 indicates there is a custom task sequence being used).

Then, I created a User Event that sends a message to Transporter21 every so often. In the example, it is every 100 seconds starting at 50 seconds. This message sends a number 1 as message parameter 1, and this parameter is used as part of a switch statement in the OnMessage trigger of Transporter21.

The OnMessage trigger of Transporter21 should be somewhat straightforward. I have also included comments to help explain. It basically creates a task sequence for each queue, one at a time. The task sequence will have the transporter either pick up or drop off any items at the current queue. It also sends the transporter to the next queue and (upon arrival) will send a delayed message of time 0 to itself to start the task sequence for the next queue.

Logan,

Thank you for your model. To reinforce what I learned with it, I created a simplified version of it. I have included it here to benefit anyone else who wants something similar (and less chaotic then the one I originally attached to this thread which you modified for me).

It took me a while to figure out how you were initiating the "dropoff" label on the flow items. I finally looked in the tree and learned what you did, which was to initiate the label by editing the default label settings of the item type within tree. Very cool!

Another very important thing you taught me was that a custom ts is "expected" when you return a 0 on a "use transport" field.

Logic for the model is just like you created, and located within:
1) User Event - kicks off TS and gives it a repeat interval
2) On Msg of transporter (I really like the switch + for loop logic)
3) On Exit of the queues to set its dropoff label

Thank you, thank you, thank you!!

Lorenzo