But depending the distance between the pick lcoation and the CM queue, sometimes you would want this value to be a few seconds (when the CM queue is far way) or maybe half minute/minute when the CM queue is quite far away. Ideally we would be able to set a Congestion.CongestionWaitReleaseIntervalMinutes for every CM position
|
Problem/opportunity trying to be solved
Customers using CM queues are not always able to put the CM queue close by. Sometimes they might be further out from the pick location and sometimes they might be very close by. Congestion.CongestionWaitReleaseIntervalMinutes is a static value and despite the distance from the CM queue to the pick location, the bots will take the same time to leave their CM queue |
|
|
Quantify the problem/opportunity
There are several sites where we cannot always make the CM queue to be close to the actual pick location and they often experience bots are taking too long to leave the CM queue |
|
|
What is the root cause of the problem/opportunity
We have a site-wide setting: Congestion.CongestionWaitReleaseIntervalMinutes. This is the time needed for the bot to leave the CM queue as soon as an LP becomes free. |
|
| Customer need date | Feb 1, 2026 |
| Urgent request | No |