Hi, I have problems with my attached model, I would like the right queue managed by the yellow operator to contain only one item to be processed and one already processed at the same time. I'm using process flow for this logic but I'm probably doing something wrong. Can some one help me?
The project excede the dimension of the uploadable file so i linked in on dropbox
https://www.dropbox.com/s/n2u1z0u4ku04h3e/Spaggiari%202%20baie_1.fsm?dl=0
This seems to be an altered version of the model in this previous question.
Note how in the model I attached there, the processors push the items onto a list, instead of the sending them through one of the port connections. This is what allows the tokens in the process flow to pull one item at a time.
In this version of the model Queue10 seems to take the place of the processors, sending the items back to the BAIA-queues. As such it should be set to push the items onto the list. The 'Port By Case' would then have to integrated into the pull logic in the process flow.
So each token needs to know which 'Cassetto' value it should pull. This could be determined by a label on the queue the token belongs to.
The same logic also applies to the IN and OUT queues. Whenever you want to limit the number of items in a queue the way I do in the other post, the inObjects must push the items onto a list, so that a token can pull them one by one, not send directly.
Two other things I noticed:
- The list in the Logica BAIA 1 flow is not linked to the global list.
- The 'Send Token To' field in the Wait for Event activity in Logica BAIA 1 is configured wrong. It looks like you typed in "Next Activity". The default text 'Next Activity' is just a placeholder value. By typing something in you set the return value of the code, which either expects the name or rank of a connection or a reference to an activity in the process flow. The text "Next Activity" is neither. To reset the field to its default, just delete the text.
I don't know what exact logic you want to achieve so I can only try to give some hints based on what I understand.
1) Since the IN and OUT queues that are connected to the rack only go into one direction now, they don't need any custom logic. You already set them up to use the Pull Strategy, so the upper section of the process flow, that controlled the flow from the rack to the queues is not needed anymore.
2) As I understand it, the BAIA 1 and BAIA 2 queues (marked orange) are the ones the rule of one inbound and one outbound item at time apply to.
They have a batch setting of 2, which contradicts the rule that they should only ever contain one outbound item. (At the start of the model, if only one item can enter from the rack, they will never release it).
That contradiction aside, since they both receive non-processed items, as well as processed ones, they need two tokens, one for each type of item.
The flow that is currently in the model pulls processed items (lavoro == 11). You would essentially just need to copy this and adjust the query to pull non-processed items (lavoro < 11). As mentioned before, all inObjects of those queues (marked blue), have to be set to push their items to the item list in the 'Send to Port' option.
18 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.
