Warehouse Obstacle Detection and Path Reassignment for Mobile Robots
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional inventory systems lack effective methods for obstacle detection and avoidance in warehouse and sortation facilities, leading to inefficiencies and delays as robotic devices encounter obstacles like fallen objects, congestion, and restricted spaces.
Innovation Solution
An obstacle management engine is implemented within the workspace management module to detect obstacles using navigational information and sensor data from mobile drive units, generating obstacle information and performing remedial actions such as path reassignment or cancellation to avoid or mitigate the impact of detected obstacles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional inventory systems operate without advanced obstacle detection, then device complexity is reduced, but productivity decreases due to task completion delays
Solution Approach 1:
An obstacle management engine is introduced as an intermediary component that receives sensor data from mobile drive units, processes obstacle information, and generates remedial actions. This mediator handles the complexity of obstacle detection and response, allowing the core inventory management system to maintain simplicity while achieving improved productivity through automated obstacle avoidance and task reassignment
Solution Approach 2:
The system performs preliminary obstacle detection by continuously monitoring sensor data from mobile drive units before obstacles can cause task delays. By detecting obstacles early and generating remedial actions in advance, the system prevents productivity losses rather than reacting after delays occur
2Reliability
If real-time obstacle detection is implemented, then reliability of task completion improves, but device complexity increases due to additional sensors and processing
Solution Approach 1:
Mobile drive units are equipped with sensors that enable them to self-detect obstacles in their environment. The obstacle management engine processes this self-generated sensor data and automatically generates remedial actions without requiring external intervention. This self-service approach improves task completion reliability by enabling autonomous obstacle avoidance while minimizing the need for complex external detection infrastructure
Solution Approach 2:
The system implements continuous feedback loops where sensor data from mobile drive units is constantly monitored, processed by the obstacle management engine, and used to generate real-time remedial actions. This feedback mechanism ensures high task completion reliability by continuously adapting to changing conditions and maintaining awareness of obstacles that could impact task execution
3Loss of time
If proactive obstacle avoidance is implemented, then loss of time is reduced, but device complexity increases due to path reassignment capabilities
Solution Approach 1:
The obstacle management engine performs preliminary analysis of sensor data to predict potential obstacles before they can cause task delays. By generating remedial actions and alternative paths in advance, the system minimizes task delay time without requiring complex real-time path recalculation when obstacles are encountered
Solution Approach 2:
The system dynamically adjusts task paths and assignments based on real-time obstacle detection. The obstacle management engine continuously monitors the workspace environment and modifies navigation paths and task assignments on-the-fly, enabling proactive obstacle avoidance that reduces task delays while maintaining flexible, adaptive path management
Data Source
AI summary
Systems and methods are provided herein for obstacle detection and avoidance. An obstacle (e.g., a fallen object, an area of congestion, etc.) may be detected utilizing sensor data and/or navigational information provided by various components of a workspace (e.g., mobile drive units, standalone sensors, etc.). Obstacle information corresponding to the obstacle may be utilized to identify tasks within the workspace that may be affected by the obstacle. Paths for these affected tasks may be altered and any subsequent path generated by the system may be generated based at least in part on the obstacle, so long as the obstacle exists. Utilizing the techniques provided herein, the workflows/tasks/paths of the components of the system may be managed so as to avoid interactions between the components of the system and any known obstacle.