Locus Robotics Ideas Portal
We propose to create the exclusion zone by reloading the map with a temporary version which has an added no-go area. The no go area can be pre-defined and stored in until it is needed.
The active map in use has all the aisles available to drive. The system would also store aisle blocking map overlays. When the user wants to block one or more work areas, the user would select the required no-go overlays and once selected, the user would process a new merge and apply function. The no go overlay would be merged into the standard map and the merge map sent to the bots.
Once the user has completed the (MHE) tasks, the user would roll the map back to the standard active map thereby allowing he bots to access the now available aisles.
While the exclusion area is applied, a new wait state would be needed in the fleet management software to allow the bots to be redirected to a wait point. This wait would work in much the same way as the congestion management solution. The bot would go to the wait point and remain there until the map allowed for it.
Where the site/floor requires multiple aisles to be kept clear, the user should be able to select more than one exclusion map to merge with the active map.
|
Problem/opportunity trying to be solved
During operations, there is regularly a need to prevent bots from using aisles while MHE enters and performs put away and replenishment tasks. Given the bots will try every possible way to get to there destination, the area to exclude the bots from needs to have access to the area disabled. |
|
|
Quantify the problem/opportunity
We have new bids where the customer is saying the inability to block aisles for MHE access is a show stopper/barrier to implementing. |
|
|
What is the root cause of the problem/opportunity
robot navigation tries all available ways to get to a target location |
|
| Customer need date | Apr 30, 2024 |
| Urgent request | No |
| Report Tag | CSM, Tools |
Robot SW has future work planned for congestion management. This use case will be considered as part of that future effort. No timeline or commitment to develop this feature at this time.