Multiple different flow items on combiner

Multiple different flow items on combiner

Felix_Hagemeister
Contributor Contributor
62 Views
1 Reply
Message 1 of 2

Multiple different flow items on combiner

Felix_Hagemeister
Contributor
Contributor

Hi,

 

The current situation is as follows:

I have a queue (Queue6) that holds multiple different flow items (various pallets and boxes). The next step is a combiner (Combiner7), but the boxes waiting there need a tote to be loaded into. The required amount depends on the box type, which is defined by multiple labels.

However, if a pallet from Queue6 is processed by the combiner, it needs to be loaded with one specific newly generated box. This box type is independent and universally used for all pallets.

 

How can I implement this? Can my source generate pallets that are used for the boxes in Queue6, as well as a specific box type that is used to be loaded onto the pallets of Queue6?

In general, I know it’s possible to use a global table for a combiner when dealing with different products.

 

Thanks!!! 🙂

0 Likes
63 Views
1 Reply
Reply (1)
Message 2 of 2

moehlmann_fe
Enthusiast
Enthusiast

For this to work with a default combiner both the pallets from Queue6 and Totes need to be able to enter through the same port. This would require an intermediate queue which might complicate the timing/priority logic.

My opinion is that as soon as you would need to customize the behaviour of the combiner it is generally always simpler to just build the logic in Process Flow rather than fight the combiner's default behaviour.

 

In the attached model there are three sources: One creates boxes, one pallets and one totes. Boxes and totes enter one queue and totes another one. An Object Process Flow with a Processor as instance object reacts to items entering these queues and creates tokens for each. Boxes are pushed to a list from which the totes can pull the required items. Totes that have pulled all items and pallets then need to enter a zone with a maximum content of 1. This serves as "acquiring" the processor. Their are then moved to it and the token leaves the zone once the process has finished.

0 Likes