What I was thinking is to see if we could use the solution we have implemented in combination with our fire units where we can set up 'no stop zones'. When the fire alarm triggers our fire integration unit, bots would keep driving till they get out of the no-stop zones. It might be good to set this up for LP blocked to avoid that bots would stop on places where they hinder other bots/people/etc
|
Problem/opportunity trying to be solved
VF Sint Nik (but it's basically all customers that to a certain extend experience this) is reporting that bots often stop showing 'LP blocked' on locations which are not the most convenient for them and blocking other bots/traffic. |
|
|
Quantify the problem/opportunity
VF Sint Nik is reporting they see this more often in the last 2-3 weeks, but nothing has changed so we guess this is really just a coincidence and caused by something on the customer side (e.g. more orders with picks from the same LPs). |
|
|
What is the root cause of the problem/opportunity
We have set up Congestion Management and we have been thinking if we could do something with that. But at VF Sint Nik we have smaller aisle width where no bots can pass. Therefore we are limiting the traffic into an aisle section with a maximum of 3 bots, but in those aisle sections we have >3 LPs available. Maybe when we want to avoid LP blocked we need to bring the max bots back to 2 per aisle section, but ideally we would want this advance CM setup (LSA-I-908) where we would like to use an LP twice in order to avoid LP blocked. I also read about the Wait positions (https://locusrobotics.atlassian.net/wiki/x/EgD8CgE) we might be able to use for this purpose and even though it shows a target release of 25.2, I'm not sure if that's confirmed |
|
| Customer need date | Aug 1, 2025 |
| Urgent request | No |
| Report Tag | CSM, OSD |