Subject complicated grouping
Author Olaf Kluge
Hello,



there are two different loading units available. A small unit (named as
paltyp = 1) (EURO-unit 1200mmX800mm) and a large unit (double euro-size)
(named as paltyp = 2).



Now, we have several picking-stations. Each have two roller tracks
(transport-system for the high bay warehouse), one left, one right. In our
Database we have declared for each roller track of each picking station a
number. For example picking station 1, left roller track number 11, right
roller track number 12. Each element has an attribute if there the paltyp =
1 or 2 available. For the large unit we have a virtual number created for
example 13 with paltyp 2;



Picking station 1:

Roller track 11, paltyp 1 = left

Roller track 12, paltyp 1 = right

Roller track 13, paltyp 2 = both (11 and 12)



What I would say. If roller track 11 is occupied with a unit (paltyp 1), I
can use the roller track (now named as RB) 12 for the next order. If RB 12
is occupied, the RB 11 is available. But in both cases the RB 13 is not
possible. Also if RB 13 is occupied, the RB 11 and RB 12 not available.



If I check one RB to the next, it can happen, that I return RB11 is free and
when I arrive the RB13, I see that this RB13 is occupied. In this case RB11
and RB12 must set to not available.



Example:

RB 11 (real) empty

RB 12 (real) empty

RB 13 (virtual) is empty too - all available



#2

RB11 occupied

RB12 empty - it is possible to get a new order

RB13 - not possible, because RB11 is occupied and RB13 needs both RB



#3

RB11 empty, but not possible (RB13 occupied)

RB12 empty, but not possible (RB13 occupied)

RB13 occupied.



I have tried to simplify the mission. In real, it is more complicated.



Thank you.





Best regards.



Olaf



[Non-text portions of this message have been removed]