I need help, I'm new to FlexSim and I have some questions. In the shared model, I would like to have the operator load the pallet with a box according to the color of the pallet, and then this process is done directly from the conveyor belt, I made countless attempts without success. I would appreciate it if anyone could help me with the solution. Is there a logic to unloading the boxes according to the color of the pallet?
The attached model uses an Object Process Flow to control the loading. The DPs are the instance objects, other important objects are referenced through centerport connections. A label on the DP denotes whether the item will be moved by an operator or via conveyor.
Good morning @Felix Möhlmann , I would like to thank you for your help, I believe that I am slowly starting to understand FlexSim, although I still have some doubts. I also apologize for so many questions, I just have to thank the community for so much help.
Good afternoon, Thank you very much for your help, a question? Imagine that I have 3 independent assembly lines in the same model, so in this model I could not use the same internal list for all 3, correct? I created 2 lists for the others, in addition to the internal list named Items, but it didn't work. I also tried to connect lists, but I was unsuccessful, remembering that I made the necessary changes referencing each object on each line, that is, the events according to each object on each line. I believe that my problem is in the internal list, and in my model I adopted a system for each of the 3 assembly lines, so there were 3 similar but independent logics. I would appreciate it if you could provide any ideas that would help me solve the model.
Operators search for boxes on other lines and do not understand that their actions must be exclusive to the Queue that is connected.
One question would be that I can use the same Label "Type" on all 3 lines or would I have to change it since there are 3 lines on the same model?
The Process Flow in the model is an Object Process Flow. This means that every linked object (in this case the decision points) runs its own, mostly independent, copy of the flow.
This means that adding the logic a second time to the flow will have each item pushed to the list twice and each pallet would also receive two items at each decision point.
The reason that the operators take items from different lines is that the copied list is set to be "global", meaning it is shared between all instances of the Process Flow. The original list is "local", so each instance possesses its own independent list. Which is why the stations can only pull items from 'their' queue.
That is the beauty of using instanced flows. To add additional lines, all you need to do is link the decision points to the flow and make sure they have the correct centerport-connections (one to the operator/photo eye and one to the queue) so the relevant objects can be referenced in the flow.
Interesting, I replicated the model presented for 3 identical lines and it worked. Now imagine if a line didn't have the same configuration, which is my case. one line and fully supplied by operators. different from the others. In addition to having more supply points
Would you have to make a logic for each right? and can the internal list be the same for the 3 lines?
@Felix Möhlmann I tried to do the logic using the old logic for the boxes using Type color "blue", but it seems that only the first boxes deposited by the AGV are transferred to the second row, the second is in row 2 and is not transferred.
@Felix Möhlmann Unfortunately, I tried to apply the old logic but it gave me an error as shown in the photo. I thought that was correct, but there comes a point where the boxes don't go to the second row.
The only way it worked was when you mentioned the packaging has the same Type as the box. However, I have four points on the production line, so different types were used for the totes to reach the correct locations. And when it is delivered, the pallet has a type, for example type 5, only once does the assembler place the box on the pallet. I can't figure out how to resolve this, the pallet accepts more than one type. Thank you if you can help.as shown in the last photo
For the line with all blue pallets, I used the old logic that you presented as in the photo and it worked very well, however in the second photo I have three colors of pallets in the same simulation, but I still have the problem with the Type number of the boxes, that is, I need that the pallet accepts Type1, type2 and type3 for 3 boxes of the same color.
So would there be a way for a pallet to accept different types of boxes?
I have a pallet, which is loaded with 3 yellow boxes, but with different type numbers. This is my problem if you can help. I thank
@Felix Möhlmann I have a big problem, as shown in the photo, if the line only produces blue pallets, however, each blue box has a different Type number, 1, 2, 3. How do I get it to assemble more than one Type per pallet, I went in Source and I put 2 labels Type 1 and 2 and it gave an error. If you can help. I thank
As these pieces arrive inside the Tote, we have two counters for packed boxes and then unpacked ones.
I thought that if the box has type color and the tote has type number would it be possible? I tried applying a laber color to the pallets and the "demand" counter and it didn't work.
I believe I need to find some way that makes the pallet accept more than one Type. I tried to put several labels in Sorce but it didn't work.
Thank you if you can help.
@Felix Möhlmann One question, in this model operator 5 only assembles red boxes so when the blue pallet passes he does not assemble it. How could I do this? If you can help.
You could add a label to the DPs that denotes which types are "valid" at the station and check the pallet type against those in the Process Flow.
11 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
