First of all, I would like to sincerely thank you for your help and support so far. Although I have made some progress, I have been struggling with the rest of the implementation. This is my last question for this exercise scenario, so I would really appreciate your guidance and advice on the following questions.
Weight Class Routing:
600Kg AGVs are exclusively used for handling Console, Longrail, RR Glass, Head Lining items.
1500Kg AGVs are designated for transporting R LBM items.
To clarify, I’ll use the Console as an example below. Kindly note that buffer AGVs are not relevant to this particular question.
Trigger Condition:
When an item enters Console InQueue5, a 600Kg AGV is assigned to handle the item transfer.Item Pulling Logic:
Items are pulled based on longest waiting time (older items have higher priority).AGV Pulling Logic:
AGVs are pulled based on the shortest travel distance between the AGV and the item.Transport Process:
The selected AGV loads the item and transports it to CS Task Queue 1, where it is unloaded.
Although not visually represented in the 3D model, a processing step (implemented via Delay in the Process Flow) occurs after unloading.Post-Processing Logic:
After processing is complete, the item is loaded again and transported to Console OutQueue5, where it is unloaded.Fallback Queues:
If CS Task Queue 1 is occupied, the next available queues will be used in the following order:
→ CS Task Queue 2, followed by CS Task Queue 3.
In this case, even if the item is placed in the queue, the AGV stays within the designated zone during the processing phase.Charging Behavior:
During processing (i.e., when the AGV is idle), it travels to the nearest available recharge point to begin charging.Preemptive Charging Interruption Logic:
Once CS Task Queue 1 becomes available:
The AGV waiting at CS Task Queue 2 stops charging immediately, loads the item, and transfers it to CS Task Queue 1.
After unloading, it travels to the nearest recharge point and resumes charging during the new processing phase.
Likewise, the AGV at CS Task Queue 3 follows up by unloading at CS Task Queue 2, then goes to charge.
Idle State Behavior:
If all CS Task Queues are occupied, AGVs with no assigned tasks automatically move to the nearest recharge point for charging.
