Send object depending on lable value

[erik_birgersson]

Hello,

I have an issue where I have one product made of 2 sorts of material, material 1 and material 2. 

Material 1 is produced 60% of the time and material 2 is produced the remaining 40%.

Both 1 and 2 goes through Queue1 and thereafter to Processor1.

Processor1 can handle material 1 in sequence. However, when material 2 enters Processor1 the processor have to produce material 1 in between before material 2 can be processed again.

In my model i have created this scenario with the lable 'material' that can be set as 1 or 2 onto the product Box.

So my questions are, how can I round robin material 1 and 2 when both are available in the queue? Continue to send material 1 if I only have material A available? Don't send material 2 if I only have material B available?

[moehlmann_fe · Accepted solution]

It is much easier to get the processor to pull the right item than to control what gets released by the queue.

I recommend to read through the Fixed Resource Logic page in the documentation. It explains the general behaviour of any Fixed Resource, including pulling items.

https://docs.flexsim.com/en/25.2/Reference/3DObjects/FixedResources/FixedResourcesConcepts/FixedReso...

There are two "modes" of pulling an item: Using port connections or using a list.

• Port Connections:
  The "Pull Strategy" field determines through which port the object will try to receive an item. The "Pull Requirement" determines whether an item that was released by an upstream object will be pulled or not (by returning 0 or 1). In this case you could use this to not pull material 2 if the previous item already had that type (for example by keeping track of the previous type through a label). What it can't do by itself is sort the items. That would have to happen by re-ordering the items in the upstream queue.
• List:
  The "Pull Strategy" field becomes a query in this case that can filter and/or sort the list entries. In your model you could use this to achieve your goals by using a different query string depending on what material was last received. An example is attached. The Pull Strategy is for the most part just the default "Pull From Item List" option. I only added lines 9-11 to the code to implement the distinction based on the previous material.

[erik_birgersson]

Hi,

Now when I read you explanation I understand how much easier it is to pull from the processor rather then sending the correct from the queue. 

This helped me a lot, thank you very much!