Warehouse Robot Tasking Microservices for Flexible System Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing warehouse management systems and AMR systems from different vendors require labor-intensive efforts for interface software customization and updates due to varying operating systems and warehouse layouts, leading to inefficiencies in inventory management.
Innovation Solution
A computer-based warehouse executive subsystem (WEX) and mobile robot automation subsystem (MAS) with a vehicle tasking subsystem (VTS) using microservice components, configured to be tightly designed and loosely coupled, allowing for flexible adaptation to different applications and reducing the need for semi-customization through parameterization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If interface software is customized for each warehouse application and updated for different operating system and application software versions, then system compatibility and functionality are improved, but labor intensity and maintenance effort increase significantly
Solution Approach 1:
The interface software is segmented into modular components including a connection manager, data translator, and configuration module. Each component handles specific tasks independently, allowing selective updates and reducing overall maintenance effort while maintaining adaptability to different warehouse systems.
Solution Approach 2:
The interface software is designed with universal communication protocols and standardized data structures that can interface with multiple warehouse management systems and AMR systems from different vendors. This multi-functional design reduces the need for extensive customization while maintaining broad system compatibility.
2Adaptability or versatility
If interface software is customized for every warehouse application, then specific application requirements are met, but system complexity and customization costs increase
Solution Approach 1:
The interface software employs dynamic configuration capabilities where connection parameters, data formats, and communication protocols can be adjusted at runtime based on the specific warehouse application. This dynamic approach allows the same software base to adapt to different applications without requiring complex customizations for each scenario.
Solution Approach 2:
An intermediary abstraction layer is introduced between the warehouse management system and the AMR system. This mediator handles application-specific requirements through standardized interfaces, reducing software complexity by isolating customization needs to the intermediary layer rather than throughout the entire system.
3Adaptability or versatility
If different vendors supply warehouse management systems and AMR systems, then system selection flexibility is improved, but integration difficulty and interface customization requirements increase
Solution Approach 1:
The interface software implements universal communication protocols and standardized data exchange formats that work with warehouse management systems and AMR systems from multiple vendors. This universality maintains vendor selection flexibility while reducing integration difficulty through consistent interface standards.
Solution Approach 2:
An intermediary integration layer is provided that abstracts vendor-specific protocols and communicates through standardized interfaces. This mediator simplifies integration between different vendor systems while maintaining the ability to connect to various warehouse management systems and AMR systems.
Data Source
AI summary
An automated warehouse material movement system and method of moving material in a warehouse, includes a computer based warehouse executive subsystem (WEX) that is programed with computer code to maintain inventory location and quantity information, schedule inventory movement and track inventory movement within the warehouse and a computer based mobile robot automation subsystem (MAS) that is programed with computer code to maintain information of floor layout of the warehouse, maintain information on mobile robots in the warehouse, allocate and deallocate mobile robots to particular missions, control and track movement of mobile robots and provide situational reporting of the mobile robots. A computer based vehicle tasking subsystem (VTS) is programed with computer code to respond to mission commands from the WEX to issue commands to the MAS to reserve and schedule mobile robots including movement of inventory between a source and a destination within the warehouse and to report status information from the MAS to the VTS regarding status of missions. At least one microservice component is configured to be tightly designed, stateless and loosely coupled with said WEX and MAS. The VTS is the at least one microservice component.