Composition of the Scheduling System

The scheduling system is composed of a back-end Core, front-end software packages which include implementation tools like RoboShop Pro and RDS. The image below shows the interface of the three software applications. In addition, the scheduling system also includes simulation robots and simulation devices to facilitate project simulation, reduce implementation costs, and improve implementation efficiency.

The various components of the scheduling system can communicate through multiple protocols such as HTTP, TCP, and ModbusTCP. Core connects with Roboshop Pro, RDS, Robots, and other devices through HTTP and TCP protocols. The scheduling system connects multiple devices through the network, allowing it to obtain device statuses and implement scheduling control over multiple devices.

Scheduling System Implements the Process of Transport Orders

The scheduling system first uses the front-end RDS to undertake the customer's business requirements and converts the customer's orders or tasks into transport orders issued to the back-end Core of the scheduling system. Transport orders are composed of blocks, and the Core will execute the blocks in the transport orders sequentially, breaking them down into Robot task lists and issuing them to the Robots. RDSCore monitors the execution status of the Robots in real time, controlling corresponding devices such as elevators or doors according to the Robots' positions and target points or the status of the transport orders or blocks, to accomplish the tasks.

Core allocates multiple Robots to transport goods from pickup points to drop-off points in a limited space according to the multiple orders issued by users or WMS. There are two difficulties in this process. The first difficulty is that in the case of poor network, the accurate position of the Robot cannot be confirmed. Therefore, the occupation of Robots in the scheduling system is not a spatial position, but a route, a set of mutually exclusive groups, and a detour area. Based on this, the scheduling system needs to enable multiple Robots to efficiently utilize spatial resources, maximize the efficiency of goods transportation, and avoid deadlock phenomena when multiple Robots occupy spatial resources. Another difficulty is in the unpredictability of transport orders, which requires the reasonable allocation of these orders to Robots to improve work efficiency. The following image shows a scenario of multi-Robot scheduling.

What is Core

Core is the backend program of the scheduling system, responsible for communicating with multiple devices, converting the issued waybill requirements into task sequences executable by the Robot, executing tasks in the waybill, and maintaining waybill status. The following diagram shows the functionality of Core in the scheduling system, which is the core of the scheduling system.