conveyor routing based on (1 flowitem characteristic, 2 cascading logic)

Question

question

edwin purwanto asked Jun 21 2016 at 2:48 AM edwin purwanto answered Jun 24 2016 at 3:54 AM

conveyor routing based on (1 flowitem characteristic, 2 cascading logic)

Hello,

So, I have this process

1. Flowitem enters conveyor circulation with itemtype 1 or 2.

2. From this point, they will be assigned directly a workzone (maybe a label at this point?)

a. The workzone assignment is based on how free it is (maybe settrackedvariable? or label?) so if one workzone is occupied, then 1/10 is occupied, so that it increases the number.

b. Assignment is based on parameter above, so dp2 and dp3 will compare each other, which one have less occupancy. Thus dp1 will direct the flowitem to dp2 if it has less occupancy and vice versa

3. Upon hitting either dp2 or dp3, itemtype one will enter smaller conveyor and itemtype 2 will enter bigger one.

My current problem as follow:

1. At first I thought using list. It worked before we deploy conveyor. If the conveyor is deployed, we have hard time figuring out the logic, plus this is somehow cascading. So that the first tier of routing is based on occupancy, second tier of logic is based on itemtype.

2. DP 2 and DP3 is inline within same conveyor, so whichever is directed to dp3, by dp2 will be redirected to dp2.

3. If we succesfully direct flowitem to dp3, it will appear to be teleported from dp2 to dp3

Thank you very much for taking time to examine this problem.

Best regards,

edwin

Software Version:

FlexSim 16.0.1

process flow conveyor synchronize list sorting

test.png (694.6 KiB)

· 1

______

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-06-21T15:32:38Z

Brandon Peterson answered Jun 21 2016 at 3:32 PM Brandon Peterson commented Jun 22 2016 at 5:14 PM

Edwin,

I have attached a sample model for you that uses a method of synchronizing with a process flow to make the decisions at the decision points on the conveyor. The main purpose of the process flow is to use the zone activities to keep track of the content in the different areas. The process logic is also responsible for setting the "SendTo" label on the 3D Item which is used by the decision points set the flow of the items on the conveyors.

The model has two examples. The first example (Zone Full) will send items to the first zone that is not full. The second example (Zone Distribute) will send items to a zone if it is not full and the content is <= the content of the remaining zones.

Here is how it works:

the process flow creates a token that is given a type (1 or 2) and a process time. The token then creates two children (1 for each zone)
Each child creates a 3D item and places it in the Entry Queue for its flow and then sets the color based on the type label
The child token then goes to a Push to List activity where it waits for the item to arrive at a decision point on the conveyor
When the item arrives at a decision point it starts a sub flow that will pull the token from the list
The child token then goes through some activities to decide whether or not to send the item into the current zone. If the item is to exit the main conveyor the token sets the "SendTo" label on the item to 2 or 3 depending on the type its type. **All of the activities between the push to list and where it sets the label on the item must occur in zero time.
If the item stays on the main conveyor the token will increment the "CurZone" label and either loop back to step 4 (if there are more zones) or it will wait for the item to exit the main conveyor.
If the item exits the main conveyor then the token will enter the current zone and then push to the synchronize list and wait for the item to finish conveying to the exit queue.
On entry of the exit queue the item will execute the prior sub flow and pull the child token from the synchronize list.
The child token will then execute the process time, exit the zone, and destroy the 3D item.
The child token will then die in a sink.

The difference between the two flows is that the Zone Full flow uses an Enter Zone activity to make the decision to either continue on the conveyor or enter the zone and the Zone Distribute flow uses a Decide Activity.

I hope that this helps you out with your model. Let me know if you have any questions!

Brandon

conveyor-control-v2016.fsm (50.3 KiB)

· 2

edwin purwanto commented · Jun 22 2016 at 11:29 AM

Hi Brandon,

Thank you very much for your answer. This is most likely the direction we are heading to. Your distributive model is the closest it is towards our models aim.

I attach my model to show you my current model, and also my difficulty is still as follow:

1. I have source already from my 3d model, so from your previous example, I delete several processflow token generator. Unfortunately, this is backfired, as so that the synchronization between 3d model and process flow is not there. There are several flowitem without SendTo Label.

2. Tokens are stuck in the w84finishconvey push to list activity..This is due to...I still do not know why this happen. Theoritically, push activity won't stuck, the pull activity is the one supposedly to stuck if there are no entry. This may lead to no 1 above, which only 1 token in a zone, lead to some token doesnt get SentTo label.

3. The convsync subflow activity doesnt seem to push anything.

Another key difference is that I am not using type anymore, I use curzone as the label that is getting pushed to SendTo label, but i dont think this may make a difference.

Thank you again for your help, your model was a great help, unfortunately it is that i need to learn more regarding list. Is there any resources available at the moment?

Best Regards,

Edwin

test3.fsm

0 ·

test3.fsm (3.6 MiB)

Brandon Peterson ♦ edwin purwanto commented · Jun 22 2016 at 5:14 PM

Edwin,

Here are some answers to your questions:

Add a label on the flowitems called "SendTo" and set it to 1. I would do this in one of three locations:
1. In the flowitem bin
2. In the OnCreation or OnExit trigger of the source that creates the flowitem
3. In an assign labels activity placed before the "w84convey2dp" activity in your main process flow (The Assign To field would be the label "item" on the token)
This is because you don't have the OnArrival triggers on the decision points set the same as the ones in the sample model I made (with the exception of DP3) **Also, your connections between decision points is different and this will affect the logic in the process flow and the value that the "SendTo" label needs to be set to.
This is due to the same problem that is causing #2

The "SendTo" label on the flowitem is an integral part of the sample I created. This is the method of communication between the processflow and the decision point. The OnArrival trigger of the decision points would cause the processflow to execute logic that would set the "SendTo" label on the flowitem. The OnContinue of the decision point would then send the flowitem to a downstream location based on the value of the "SendTo" label what was set in the processflow. Your model is not doing the same thing for three main reasons:

You don't have any of the triggers in the decision points executing the ConvSync flow prior to DP3. That flow is what is responsible for releasing the token in the main processflow.
The only OnContinue trigger on your decision points that uses the "SendTo" label to direct the flowitems is located on DP1. Because DP1 is located prior to DP3 there is no way that the "SendTo" label will be set prior to the OnContinue code on DP1
Your flowitems do not have the "SendTo" label on them. Without this label the model won't function correctly.

I hope that this helps,

Brandon

0 ·

Answer 2 · 2016-06-24T03:54:21Z

edwin purwanto answered Jun 24 2016 at 3:54 AM

Hello,

Thank you very much for your help. Now it is working, but i change the logic, because if the sorting of zone is done behind, it will make some zone unoccupied, eventhough there are free zone, so the flowitem sorting is then put on top, then zone enquiry is afterwards. Sorry that I got the logic not correct in the first hand.

Best Regards,

Edwin

test2.png

test2.png (56.8 KiB)

question