Conveyance vehicle management device and conveyance vehicle management method
The guided vehicle management system addresses the challenge of obstacle management in warehouse environments by simulating operations and scheduling to ensure efficient order processing and obstacle removal, enhancing the operational efficiency of guided vehicles and maintaining logistics flow.
Patent Information
- Application Number
- PCT/JP2024/013665
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-04-02
- Publication Date
- 2024-11-21
AI Technical Summary
Existing guided vehicle management systems fail to effectively manage order processing and efficiently remove obstacles in warehouse environments, leading to reduced system throughput and increased stopping times due to obstacles caused by transported objects.
A guided vehicle management device and method that maintains order and layout information, simulates warehouse operations, and calculates schedules to quickly identify and remove obstacles, allowing for efficient operation of transport vehicles without halting the logistics process.
The solution enables appropriate order management and rapid obstacle removal, improving the efficiency of guided vehicle operations and maintaining logistics flow by avoiding obstacles and optimizing vehicle routes.
Smart Images

Figure JP2024013665_21112024_PF_FP_ABST
Abstract
Description
Transport vehicle management device and transport vehicle management method
[0001] The present invention relates to a transport vehicle management device and a transport vehicle management method, and more particularly to a transport vehicle management device and a transport vehicle management method that are suitable for supporting appropriate order management and quickly removing obstacles when obstacles to transport occur in an environment where transport vehicles operate, such as a warehouse, thereby improving the operational efficiency of transport vehicles.
[0002] In recent years, in logistics warehouses and other locations where a wide variety of goods are handled, autonomous robotic transport vehicles that transport and retrieve goods handled in warehouses according to instructions from a management system have become popular in order to address labor shortages and reduce labor costs.
[0003] Such a technology relating to a transport vehicle is disclosed, for example, in Patent Document 1. Patent Document 1 describes a technology for generating a route for a transport vehicle based on a route evaluation, and controlling and operating the transport vehicle based on the route evaluation.
[0004] Furthermore, Patent Document 2 discloses a transportation system that determines a transportation route taking into consideration environmental parameters that affect the object to be transported. In particular, the transportation algorithm describes dividing an area into a grid and operating it according to a search algorithm called A*.
[0005] JP 2022-72555 A JP 2022-139772 A
[0006] In logistics processing using such vehicles, the stoppage of the vehicle directly leads to the stoppage of logistics, so it is necessary to minimize the stoppage time as much as possible. The main causes of the stoppage of a vehicle are a breakdown of the vehicle itself, and also the occurrence of an obstacle caused by a dropped item on the vehicle.
[0007] The above-mentioned Patent Documents 1 and 2 do not take into consideration the control of guided vehicles when an obstacle occurs in a logistics warehouse. For example, they do not describe how to manage orders when such an obstacle occurs and the system throughput is taken into consideration. Furthermore, they do not describe support means for quickly removing an obstacle when it occurs in a warehouse, or how to control guided vehicles in such a situation.
[0008] An object of the present invention is to provide a transport vehicle management device and a transport vehicle management method that can support appropriate order management and quickly remove obstacles when obstacles to transport occur in an environment where transport vehicles operate, such as a warehouse, thereby improving the operational efficiency of transport vehicles.
[0009] The configuration of the transport vehicle management device of the present invention is preferably a transport vehicle management device that commands the operation of transport vehicles that transport items stored on shelves installed in a warehouse in accordance with a schedule, and holds order information related to orders including items, layout information indicating the positions of the transport vehicles, the positions of the shelves, the positions of the warehouse equipment, and the state of the warehouse within the warehouse, and schedule information related to the schedule for operating the transport vehicles, receives position information of obstacles within the warehouse from the transport vehicles, reflects the obstacle position information in the layout information, calculates a schedule for operating the transport vehicles based on the layout information including the obstacle position information and reflects this in the schedule information, simulates warehouse transport operations at multiple times based on the schedule information, and outputs the time at which obstacles should be removed in order to ship the orders included in the order information in time according to the results of the simulation of warehouse transport operations.
[0010] According to the present invention, it is possible to provide a transport vehicle management device and a transport vehicle management method that can support appropriate order management and quickly remove obstacles when obstacles to transport occur in an environment where transport vehicles operate, such as a warehouse, thereby improving the operational efficiency of the transport vehicles.
[0011] 1 is a diagram showing the configuration of a logistics management system using guided vehicles. FIG. 1 is a diagram showing the hardware and software configuration of a guided vehicle management device. FIG. 2 is a diagram showing the hardware and software configuration of a guided vehicle. FIG. 3 is a diagram showing a warehouse model in which logistics work is performed by guided vehicles (part 1). FIG. 4 is a diagram showing a warehouse model in which logistics work is performed by guided vehicles (part 2). FIG. 5 is a diagram showing an example of a layout management table. FIG. 6 is a diagram showing an example of a shelf information table. FIG. 7 is a diagram showing an example of a light position information table. FIG. 8 is a diagram showing an example of an order information table. FIG. 9 is a diagram showing an example of a scheduling table. FIG. 10 is a diagram showing an example of a PICK command. FIG. 11 is a diagram showing an example of a shelf return command. FIG. 12 is a diagram showing an example of a lock command. FIG. 13 is a diagram showing an example of an unlock command. FIG. 14 is a diagram showing an example of a light turn-off command. FIG. 15 is a flowchart showing the processing of the guided vehicle management device when throughput / order impact information related to an obstacle is displayed when an obstacle is detected. FIG. 16 is a flowchart showing the processing of the guided vehicle management device when an operator attempts to remove an obstacle (part 1). FIG. 17 is a flowchart showing the processing of the guided vehicle management device when an operator attempts to remove an obstacle (part 2). FIG. 18 is a diagram showing a state in which LED lights related to an obstacle recovery route are lit. FIG. 19 is an example of a warehouse operation utility screen (part 1). FIG. 20 is an example of a warehouse operation utility screen (part 2). FIG. 21 is an example of a simulation result screen.
[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The examples are illustrative for explaining the present invention, and appropriate omissions and simplifications have been made for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural. The position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc., in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.
[0013] Although various types of information may be described using expressions such as "table," "list," and "queue" as examples, the various types of information may also be expressed using data structures other than these. For example, various types of information such as "XX table," "XX list," and "XX queue" may also be expressed as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable.
[0014] When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. When there is no need to distinguish between these multiple components, the subscripts may be omitted.
[0015] In the embodiments, processing performed by executing a program may be described. Here, a computer executes the program using a processor (e.g., a CPU or a GPU) and performs processing defined by the program using storage resources (e.g., memory) and interface devices (e.g., communication ports). Therefore, the entity performing the processing by executing the program may be the processor. Similarly, the entity performing the processing by executing the program may be a controller, device, system, computer, or node having a processor. The entity performing the processing by executing the program may be any computing unit, and may include a dedicated circuit that performs specific processing. Here, the dedicated circuit may be, for example, an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a CPLD (Complex Programmable Logic Device).
[0016] A program may be installed on a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server may include a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. In addition, in the embodiments, two or more programs may be realized as one program, or one program may be realized as two or more programs.
[0017] An embodiment of the present invention will be described below with reference to FIGS. 1 to 17. FIG.
[0018] In the logistics management system of this embodiment, a transport vehicle lifts up shelves containing items installed in a logistics warehouse and transports them to a specified location in response to a command from a transport vehicle management device. A worker performs picking work by removing the items from the transported shelves.
[0019] As shown in FIG. 1, the logistics management system of this embodiment includes a warehouse management server 10, a transport vehicle management device 100, an AP (Access Point) 30, a light control device 40, an LED (light-emitting diode) light 41, and a transport vehicle 200.
[0020] The warehouse management server 10 is a server that manages the inflow and outflow of goods in the warehouse. The warehouse management server 10 instructs the guided vehicle management device 100 to outflow goods.
[0021] The entrance / exit locking mechanism 20 is a mechanism for locking and unlocking entrances through which people enter and exit the warehouse 50 in accordance with instructions from the transport vehicle management device 100 .
[0022] The light control device 40 is a device for controlling the turning on and off of the LED light 41 in response to a command from the transport vehicle management device 100 .
[0023] The LED lights 41 (denoted as 41 a, 41 b, . . . in FIG. 1 ) are lights for illuminating necessary parts of the warehouse in accordance with commands from the transport vehicle management device 100 .
[0024] The APs 30 (denoted as 30a, 30b, . . . in FIG. 1) are communication devices that allow the guided vehicle management device 100 and the guided vehicles 200 to exchange information wirelessly.
[0025] The transport vehicle management device 100 receives instructions from the warehouse management server 10 and controls the entrance / exit lock mechanism 20 and LED lights 41, which are equipment within the warehouse 50, schedules the transport vehicle 200, and issues instructions regarding the transport vehicle 200's retrieval of goods from the warehouse.
[0026] The vehicle management device 100 includes, as functional units, a warehouse operation unit 101, a transportation simulation unit 102, and a warehouse operation user interface unit 103. The vehicle management device 100 also stores, as databases, a layout management DB 300, an order / operation schedule DB 310, and an operation command DB 320.
[0027] The layout management DB 300 includes a layout management table 301, a shelf information table 302, and a light position information table 303. The order / operation schedule DB 310 includes an order information table 311 and a scheduling table 312. The operation command DB 320 includes a PICK command 321, a shelf return command 322, a lock command 323, an unlock command 324, a light command 325, and a light off command 326.
[0028] The details of each table and command will be explained later.
[0029] The warehouse operation unit 101 is a functional unit that issues commands to operate warehouse facilities and commands to the transport vehicle 200 regarding movement and retrieval of goods. The transport simulation unit 102 is a functional unit that simulates the transport of goods by the transport vehicle based on item order information, the warehouse status, and the transport vehicle schedule. The warehouse operation user interface unit 103 is a functional unit that displays to the warehouse manager and workers the current warehouse status, information related to item orders, information on the results of the transport simulation, as well as information on the occurrence of obstacles and routes for recovering obstacles (details will be described later), and accepts commands from the warehouse manager.
[0030] The guided vehicles 200 (denoted as 200a, 200b, . . . in FIG. 1) are autonomous robotic vehicles that load shelves in the warehouse 50 and transport them to a picking area in accordance with instructions from the guided vehicle management device 100.
[0031] The transport vehicle 200 includes a travel control unit 201, a transport control unit 202, and an obstacle detection unit 203 as functional units.
[0032] The travel control unit 201 is a functional unit that controls the motor, brakes, and other parts related to the travel of the transport vehicle. The transport control unit 202 is a functional unit that controls the transport disk that loads and unloads workpieces and its drive mechanism. The obstacle detection unit 203 is a functional unit that detects obstacles that occur within the warehouse 50 and notifies the transport vehicle management device 100 of the detection together with image information of the obstacle.
[0033] Next, the hardware and software configuration of the guided vehicle management device 100 will be described with reference to Fig. 2. The hardware configuration of the guided vehicle management device 100 is realized by, for example, a general information processing device such as a personal computer shown in Fig. 2.
[0034] The transport vehicle management device 100 comprises a CPU (Central Processing Unit) 402, a main memory 404, a network I / F (Interface) 406, a display I / F 408, an input / output I / F 410, and an auxiliary memory I / F 412, all connected by a bus.
[0035] The CPU 402 controls each unit of the transport vehicle management device 100, and loads necessary programs into the main memory 404 and executes them.
[0036] The main memory 404 is typically configured as a volatile memory such as a RAM, and stores the programs executed by the CPU 402 and the data referenced by the CPU 402.
[0037] The network I / F 406 is an interface for connecting to the network 5 .
[0038] The display I / F 408 is an interface for connecting a display device 420 such as an LCD (Liquid Crystal Display).
[0039] The input / output I / F 410 is an interface for connecting input / output devices. In the example of Fig. 2, a keyboard 430 and a mouse 432, which is a pointing device, are connected.
[0040] The auxiliary storage I / F 412 is an interface for connecting an auxiliary storage device such as a hard disk drive (HDD) 450 or a solid state drive (SSD).
[0041] The HDD 450 has a large storage capacity and stores programs for executing the present embodiment. A warehouse operation program 451, a transportation simulation program 452, and a warehouse operation user interface program 453 are installed in the guided vehicle management device 100.
[0042] The warehouse operation program 451, the transport simulation program 452, and the warehouse operation user interface program 453 are programs that realize the functions of the warehouse operation unit 101, the transport simulation unit 102, and the warehouse operation user interface unit 103, respectively.
[0043] The HDD 450 also stores a layout management DB 300, an order / operation schedule DB 310, and an operation command DB 320.
[0044] Next, the hardware and software configuration of the transport vehicle will be described using Figure 3. The transport vehicle 200 is an autonomous robot that travels and transports workpieces in response to commands from the transport vehicle management device 100, and as shown in Figure 3, an MPU (Micro Processing Unit) 502, main memory 504, communication device 506, obstacle detection sensor 508, non-volatile memory 510, travel mechanism 520, and transport mechanism 530 are connected by a bus, and the transport vehicle has a battery 540 for autonomous travel.
[0045] The MPU 502 controls each part of the transport vehicle 200, and loads necessary programs into the main memory 504 and executes them.
[0046] The main memory 504 is typically configured as a volatile memory such as a RAM, and stores the programs executed by the MPU 502 and data referenced by the MPU 502.
[0047] The communication device 506 includes an antenna and is a device for wirelessly communicating with the transport vehicle management device 100 via the AP 30 .
[0048] The nonvolatile memory 510 is a storage device such as a ROM (Read Only Memory) or a flash memory, from which data is not purged even when the power is turned off.
[0049] A travel control program 511, a transport control program 512, and an obstacle detection program 513 are installed in the non-volatile memory 510. The travel control program 511, the transport control program 512, and the obstacle detection program 513 are programs that execute the functions of the travel control unit 201, the transport control unit 202, and the obstacle detection unit 203, respectively.
[0050] The obstacle detection sensor 508 is a sensor that detects obstacles within a detection area during operation. The obstacle detection sensor 508 has a sensing function using a camera or the like, which enables it to sense images of obstacles and transmit them to the transport vehicle management device 100.
[0051] The travel mechanism 520 is a mechanism for moving the transport vehicle 200, and includes moving parts such as a motor, gears, brakes, and tires, although not shown.
[0052] The transport mechanism 530 is a mechanism by which the transport vehicle 200 loads the workpiece, and although not shown, includes a stepping motor, gears, and a disk on which the workpiece is mounted.
[0053] The battery 540 is a device that supplies power to each part of the transport vehicle 200, and is, for example, a rechargeable lithium-ion battery.
[0054] Next, a warehouse model in which logistics operations are performed using carrier vehicles will be described with reference to FIGS. 4A and 4B.
[0055] The transport vehicle 200 moves through the warehouse 50 in a unit time Δt (for example, 5 seconds), moving up, down, left, and right in an N×M grid 600 as shown in FIG. 4A.
[0056] Blocks E 601 on the periphery of grid 600 are entrances and exits for people to enter and exit. Blocks P 602 are blocks that indicate picking areas. In the picking areas, workers perform picking work by retrieving items from shelves that have been brought in by transport vehicles 200.
[0057] The S block 603 in the grid 600 is a block where a shelf is placed. The S block 603 must be placed in a designated shelf area 610.
[0058] The O block 604 in the grid 600 is an obstacle that may impede the transport of the transport vehicle 200, such as an item that has fallen off during transport by the transport vehicle 200.
[0059] A V block 605 in the grid 600 is a block in which the transport vehicle 200 exists. A VS block 606 in the grid 600 is a block that represents the state when the transport vehicle 200 transports a shelf.
[0060] The operation of the transport vehicle 200 must not overlap with the V block 605, VS block 606, or O block 604 at any given time. However, the shelf has a four-legged structure, and the transport vehicle can pass under the S block 603.
[0061] Here, the n transport vehicles 200 are represented by Vi (i=1, . . . , n).
[0062] When the vehicle management device 100 issues an instruction to ship an item in response to an order, the vehicle management device 100, the vehicle 200, and the worker perform the following actions: (1) The vehicle management device 100 obtains the shelf ID of the shelf where the item is stored from the item ID included in the order. (2) The vehicle management device 100 obtains the location of the square where the shelf ID is located from the current shelf status information. (3) The vehicle management device 100 instructs the vehicle 200 Vi on the route and operation from its current location to the location of the square of the shelf ID (moving to the square specified every Δt, stopping, loading the shelf), and the route and operation from the location of the square of the shelf ID to the location of the block adjacent to P block 602 (moving to the square specified every Δt, stopping). Priority is assigned to vehicles V1 to Vn, and instructions are given in the order of V1 to Vn. In this case, no route is created at the locations of V block 605, VS block 606, and O block 604. (4) In accordance with the instruction in (3), the transport vehicle 200 of Vi moves along the route from its current position to the position of the square with the shelf ID, loads the shelf, and moves to the position of the block adjacent to the P block 602. (5) When the worker inputs into the warehouse management terminal (not shown) that he or she has completed picking the item, the input is sent to the warehouse management server 10 and then to the transport vehicle management device 100. While picking the item, the transport vehicle 200 keeps the shelf raised. (6) In response to the communication in (5), the transport vehicle management device 100 instructs the transport vehicle 200 on the route and operation (moving the square, stopping, unloading the shelf) for each Δt from the position of the block adjacent to the P block 602 to the block in the shelf area where the currently loaded shelf will be unloaded (for example, the nearest empty block in the shelf area from the current position). (7) Following the instruction in (5), the transport vehicle 200 of Vi moves from the position of the block adjacent to the P block 602 to the block in the shelf area and unloads the shelf.
[0063] In the above phases (3) and (6), to find the route for the transport vehicle to move from the square of the current position, a route is created so that the transport vehicle moves to the adjacent block that gives the smallest evaluation value Eval in the following (Equation 1).
[0064] Eval=distance(next_square, target_square) (Equation 1) Here, distance(s1, s2) is the distance between square s1 and square s2, target_square is the square to which the transport vehicle 200 is moving, and next_square is the adjacent square to which the transport vehicle 200 can move from the current position.
[0065] Next, an example in which the warehouse model in which logistics operations are performed using carrier vehicles shown in FIG. 4A is expanded to specify a new block will be described with reference to FIG. 4B.
[0066] A C block C607 has been added to the grid 600 in Figure 4B. The C block 607 is a recovery path block that is placed as a single continuous path from the block next to the E block 601 on the periphery to the block next to the O block 604. The path can be calculated using the above (Equation 1).
[0067] The block made up of C blocks 607 is a route that a worker passes through to retrieve the items, and the transport vehicle 200 does not move through the C blocks 607 while the worker has finished retrieving the items and is leaving the square 600.
[0068] That is, the description of the above phase (3) reads, "...at this time, no paths are created in the blocks V block 605, VS block 606, O block 604, and C block 607."
[0069] When there are multiple E blocks 601, the entrance / exit should be selected so that the distance of the route formed by the C block 607 is the shortest. Also, when a worker is assigned to a specific entrance / exit, the C block should be calculated from the E block 601 at that entrance / exit.
[0070] By operating the transport vehicle 200 according to this expanded warehouse model, a worker attempting to retrieve an obstacle can do so safely, and there is no need to completely stop the operation of the transport vehicle 200 (with only the partial restriction that the position of the C block cannot be moved).
[0071] Next, the data structure used in the physical distribution management system of this embodiment will be described with reference to FIGS. 5 to 12B.
[0072] The layout management table 301 is a table that stores information about the layout of a logistics warehouse, and as shown in FIG. 5, has fields for block type 301a and position 301b.
[0073] 4A and 4B (E: entrance / exit, P: picking area, O: obstacle, V: transport vehicle, VS: shelf operation status of the transport vehicle, C: collection route). The position 301b stores the position of the block indicated by the block type 301a. In the example of this embodiment, the grid is 8x8, and the perimeter of the grid is 0th row, 9th row, 0th column, and 9th column.
[0074] Although not shown, the layout management DB 300 also stores information indicating the shelf area 610 in FIG. 4A.
[0075] The shelf information table 302 is a table showing the relationship between shelves and storage of items, and the current location of the shelves, and is made up of fields for shelf ID 302a, item list 302b, and location 302c.
[0076] The shelf ID 302a stores an ID that uniquely identifies the shelf. The item list 302b stores a list of items stored on the shelf. The location 302c stores the current location of the shelf.
[0077] The light position information table 303 is a table showing the correspondence between the light and the position of the grid block, and as shown in FIG. 7, is made up of fields for a light ID 303a and a position 303b.
[0078] The light ID 303a stores an ID that uniquely identifies a light for controlling turning on and off. The position 303b stores the position of the lighting block that the LED light identified by the light ID 303a is responsible for.
[0079] The order information table 311 is a table for storing information about orders from customers, and as shown in FIG. 8, it has fields for an order ID 311a, an orderer ID 311b, a shipping destination ID 311c, a deadline 311d, and an item list 311e.
[0080] The order ID 311a stores an ID that uniquely identifies the order. The orderer ID 311b stores an ID that uniquely identifies the orderer. The shipping destination ID 311c stores an ID that uniquely identifies the shipping destination. The deadline 311d stores the shipping deadline of the order. The item list 311e stores the IDs of the items included in the order in list format.
[0081] Although not shown in the figure, the name and surname of the orderer are stored in the orderer master table, the name, surname, address and telephone number of the shipping destination are stored in the shipping destination master table, and the name of the item and other details are stored in the item master table in a format corresponding to each ID separately.
[0082] The scheduling table 312 is a table that stores the movement and command execution schedules for each transport vehicle 200 scheduled by the transport vehicle management device 100, and as shown in Figure 9, has fields for transport vehicle ID 312a, position / command 312b1, position / command 312b2, ..., position / command 312bi, ... (in Figure 9, each field is represented as Δt, 2Δt, ..., iΔt, ...).
[0083] The transport vehicle ID 312a stores an ID that uniquely identifies the transport vehicle 200. The position / command 312bi (i = 1, ..., m) stores the position of the transport vehicle ID 312a i x Δt time from now or a command to be executed. In the example of Fig. 9, the command "Stop" is a command to stop the transport vehicle 200 for Δt, the command "Load" is a command to make the transport vehicle 200 lift up a shelf, and the command "Unload" is a command to make the transport vehicle 200 lower a shelf when returning to a block in the shelf area 610.
[0084] The PICK command 321 is a command that instructs the transport vehicle 200 to pick up a shelf, and as shown in FIG. 10A, has fields for transport vehicle ID 321a, command type 321b, position / command 321c1, position / command 321c2, ..., position / command 321ck, ...
[0085] The transport vehicle ID 312a stores an ID that uniquely identifies the transport vehicle 200. The command type 321b stores a character string or ID that indicates the command "PICK," and the position / command 321bi (i = 1, ..., k) stores the position of the transport vehicle ID 321a i x Δt time after the command is received or the command to be executed. The commands "Stop," "Load," and "Unload" are as already explained, and are subcommands of the PICK command.
[0086] When the transport vehicle 200 receives a PICK command from the transport vehicle management device 100, it follows the information in the position command 321c1, position command 321c2, ..., position command 321ck to go from its current position to the block in the S block where the shelf is located, loads the shelf onto the transport vehicle 200, and then moves to the position of the block adjacent to the P block 602.
[0087] The shelf return command 322 is a command for returning a loaded shelf to an available block in the shelf area during picking, and has fields for a transport vehicle ID 322a, a command type 322b, a position / command 322c1, a position / command 322c2, ..., a position / command 322c1, .... The meaning of each field is the same as that of the PICK command 321 shown in Fig. 10A. The command type 322b stores a character string or ID representing the command "RETURN_SHELF".
[0088] When the transport vehicle 200 receives a shelf return command from the transport vehicle management device 100, it moves from its current position to an empty block in the shelf area 610 in accordance with the information in the position command 322c1, position command 322c2, ..., position command 322ck, and unloads the shelf.
[0089] The lock command 323 is a command issued from the transport vehicle management device 100 to lock (lock) the entrance / exit locking mechanism 20, and as shown in FIG. 11A, has fields for an entrance / exit ID 323a and a command type 323b.
[0090] The gate ID 323a stores an ID that uniquely identifies the gate. The command type 323b stores a name or ID that identifies the command "LOCK."
[0091] Similarly, the unlock command 324 is a command issued from the transport vehicle management device 100 to unlock the entrance lock mechanism 20, and as shown in FIG. 11B, has fields for an entrance ID 324a and a command type 324b.
[0092] The command type 324b stores a name or ID representing the command "UNLOCK."
[0093] The light-on command 325 is a command issued by the transport vehicle management device 100 to the light control device 40 to turn on the LED light, and as shown in FIG. 12A, has fields for a light ID 325a and a command type 325b.
[0094] The light ID 325a stores an ID that uniquely identifies the LED light 41. The command type 323b stores a name or ID that indicates the command "ON."
[0095] Similarly, the light-off command 326 is a command issued by the transport vehicle management device 100 to the light control device 40 to turn off the LED light, and as shown in FIG. 12B, has fields for a light ID 326a and a command type 326b.
[0096] The light ID 326a stores an ID that uniquely identifies the LED light 41. The command type 323b stores a name or ID that indicates the command "OFF."
[0097] Next, the processing of the transport vehicle management device of this embodiment will be described with reference to FIGS.
[0098] First, the processing of the guided vehicle management device when an obstacle is detected will be described using Fig. 13. First, the guided vehicle management device 100 receives information from the guided vehicle 200 that has detected the obstacle, including information about the obstacle's detection, its location, and image information about the obstacle, and the warehouse operation unit 101 of the guided vehicle management device 100 adds information about the obstacle's block to the layout management table 301 (S100).
[0099] Next, the warehouse operation user interface unit 103 of the transport vehicle management device 100 displays a warehouse operation utility screen based on the information, and the user selects or commands the display of throughput / order impact information related to the obstacle (S101). A specific example of the user interface of the warehouse operation utility screen will be described later.
[0100] Next, the warehouse operation unit 101 of the transported vehicle management device 100 calculates an obstacle-avoiding route based on the layout management table 301, and reflects the route that avoids the obstacle in the scheduling table 312 (S102).
[0101] Next, the transportation simulation unit 102 of the transportation vehicle management device 100 performs a simulation based on the scheduling information when there is no obstacle, and a simulation based on the scheduling information when there is an obstacle in S101 (S103).
[0102] Next, the transportation simulation unit 102 of the transportation vehicle management device 100 calculates the throughput of warehouse operation when an obstacle is present, based on the results of each simulation in S103 (S103).
[0103] Next, the warehouse operation user interface unit 103 of the transport vehicle management device 100 compares the throughput of warehouse operations when there is no obstacle and the throughput of warehouse operations when there is an obstacle and displays the results on the display device 420 (S105).
[0104] A specific example of a user interface for displaying throughput will be described later.
[0105] Next, the transportation simulation unit 102 of the transport vehicle management device 100 refers to the order information table 311 in FIG. 8 and the simulation results, and determines whether there are any orders that will not meet their shipping deadline if the obstacle is left unattended (S106).
[0106] If there are no orders that will not meet the shipping deadline (S106: NO), the process ends, and if there are orders that will not meet the shipping deadline (S106: YES), the process proceeds to S107.
[0107] When there is an order that will not meet its shipping deadline, the transportation simulation unit 102 of the guided vehicle management device 100 performs a simulation for multiple candidate time settings for removing the obstacle, and determines the time to remove the obstacle that will meet the shipping deadline (S107). For example, a simulation is performed by setting the time for removing the obstacle every 30 minutes from the current time, and the time is determined by subtracting the time 30 minutes before the time when the order that will not meet the shipping deadline was generated. Here, the time for removing the obstacle that will meet the shipping deadline is determined based on the time by which the worker needs to pick the items related to the order, taking into account work time such as packing, data entry, and transportation, relative to the shipping deadline of the order.
[0108] Next, the warehouse operation user interface unit 103 of the transport vehicle management device 100 displays on the display device 420 information about the orders that will not meet the shipping deadline and the time required to remove the obstacles in order to meet the shipping deadline calculated in S107 (S108).
[0109] A specific user interface for information regarding orders that will not meet the shipping deadline will be described later.
[0110] Next, the process of the guided vehicle management device when a worker attempts to remove an obstacle will be described with reference to FIGS. 14A and 14B.
[0111] First, the transport vehicle management device 100 receives from the transport vehicle 200 that has detected an obstacle, information indicating that an obstacle has been detected, location information, and image information of the obstacle, and the warehouse operation unit 101 of the transport vehicle management device 100 adds information about the obstacle block to the layout management table 301 (S200).
[0112] Next, the warehouse operation user interface unit 103 of the transported vehicle management device 100 displays a warehouse operation utility screen based on the information (S201).
[0113] A specific example of the user interface of the warehouse operation utility screen will be described later.
[0114] When the operator issues a "recover obstacle" command on the warehouse operation utility screen, the process proceeds to S202, and when the operator issues a "recover later" command, the process ends.
[0115] When an "obstacle recovery" command is issued, the warehouse operation unit 101 of the transport vehicle management device 100 refers to the layout management table 301, calculates a continuous obstacle recovery route from the obstacle block to the block next to the entrance / exit block, and writes information about the blocks of the obstacle recovery route into the layout management table 301 (S202).
[0116] Next, the warehouse operation user interface unit 103 of the transported vehicle management device 100 displays the obstacle recovery route on the warehouse operation utility screen (S203).
[0117] A specific example of the warehouse operation utility screen at this time will be explained later.
[0118] Next, the warehouse operation unit 101 of the transport vehicle management device 100 refers to the layout management table 301 and reschedules the blocks for the operation of the transport vehicle 200 so that they do not overlap with the blocks of the obstacles and the blocks of the obstacle recovery route, and reflects this in the scheduling table 312 (S204).
[0119] Next, the warehouse operation unit 101 of the transport vehicle management device 100 operates the transport vehicle 200 based on the scheduling information of S204, and performs transport operations (S205).
[0120] Next, the worker checks whether there is a transport vehicle on the obstacle recovery route (S206), and if there is a transport vehicle on the obstacle recovery route (S206: YES), the process waits (S207), and if there is no transport vehicle on the obstacle recovery route (S206: NO), the process proceeds to S208.
[0121] When there are no more guided vehicles on the obstacle recovery route, the warehouse operation unit 101 of the guided vehicle management device 100 commands the entrance / exit lock mechanism 20 to unlock, and commands the light control device 40 to turn on the LED lights 41 associated with the obstacle recovery route (S208). When a command to turn on the LED lights associated with the obstacle recovery route is issued, as shown in Figure 15, the LED lights associated with the block of the obstacle recovery route 710 where the obstacle 720 is located are turned on based on the light position information table 303 in Figure 7. In Figure 15, ▽ indicates the on state 701 of the LED lights 41, and ▼ indicates the off state 702 of the LED lights 41.
[0122] The work area of a warehouse where a robot works may normally be dark, but with the transport system of this embodiment, the necessary areas are automatically lit when a person enters, allowing obstacle removal work to be carried out safely and efficiently.
[0123] The worker then enters the warehouse through a doorway, removes the obstacle, and exits the warehouse through the same doorway.
[0124] The warehouse operation unit 101 of the transport vehicle management device 100 determines whether or not a "collection complete" notification has been sent from the warehouse operation utility screen (S209), and if the "collection complete" notification has not been sent (S209: NO), it waits (S210), and if the "collection complete" notification has been sent (S209: YES), it goes to S211.
[0125] When the notification of "recovery completed" is made, the warehouse operation unit 101 of the transport vehicle management device 100 commands the entrance / exit locking mechanism 20 to lock (lock) and commands the light control device 40 to turn off the LED light 41 related to the obstacle recovery route (S211).
[0126] The warehouse operation user interface unit 103 of the guided vehicle management device 100 updates the warehouse operation utility screen with a message indicating that the obstacle has been removed and the warehouse layout information (S212).
[0127] The warehouse operation unit 101 of the transport vehicle management device 100 removes the information on the obstacle block and the information on the obstacle recovery route block from the layout management table 301, updates the layout management table 301, and performs rescheduling (S213).
[0128] Next, the warehouse operation unit 101 of the transport vehicle management device 100 operates the transport vehicle 200 based on the scheduling information of S212, and performs transport operations (S214).
[0129] Next, the user interface provided by the transported vehicle management device will be described with reference to FIGS. 16A to 17. FIG.
[0130] The warehouse operation utility screen 800 is a screen that displays the warehouse operation layout and information about obstacles, and is used to input commands related to obstacles and commands for displaying simulation results. As shown in FIG. 16A , the warehouse operation utility screen 800 includes a layout display area 810, an obstacle image display area 820, a start collection button 831, a collect later button 832, a display throughput / order impact button 833, and a complete collection button 834.
[0131] The layout display area 810 is an area that displays the status of each block in relation to the layout of the warehouse. The layout display area 810 normally displays the current position of the transport vehicle 200 (V block), the position of the shelf (S block), and the transport status of the shelf (VS block) by the transport vehicle 200, but when an obstacle is detected, information about the obstacle (O block) is displayed.
[0132] The E block (entrance / exit), P block (picking area), S block (shelf), and O block (obstacle) in FIG. 16A have already been explained with reference to FIG. 4A.
[0133] The obstacle image display area 820 displays an image of the obstacle sent from the transport vehicle 200 when the obstacle is detected.
[0134] The recovery start button 831 is a button that the worker presses to notify the guided vehicle control device 100 when recovering an obstacle ("recover obstacle" command in FIG. 14A).
[0135] The recover later button 832 is a button that is pressed when informing the transportation vehicle management device 100 that the worker will be recovered later ("recover later command" in FIG. 14A).
[0136] The throughput / order influence display button 833 is a button that is pressed when displaying a simulation result screen (described later) that shows information about the influence of the throughput and orders related to the obstacle (S101 in FIG. 13).
[0137] The recovery completion button 834 is a button that is pressed to notify the system when the obstacle has been recovered and removed (S209 in FIG. 14B).
[0138] When the Start Collection button 831 is pressed, the layout display area 810 of the warehouse operation utility screen 800 displays an obstacle collection route (block C) 814 from the block next to the entrance / exit (block E) to the obstacle (block O), as shown in FIG. 16B.
[0139] The simulation result screen 900 is a screen that displays information regarding the influence of obstacles on throughput and orders, and as shown in FIG. 17, is made up of a throughput display area 910 and an order information display area 920.
[0140] The throughput display area 910 is an area that displays a throughput graph 911 that compares when an obstacle is present and when it is not present. The horizontal axis of the throughput graph 911 represents time, and the vertical axis represents throughput. Throughput is, for example, the number of items released per unit time or the number of orders processed per unit time in warehouse operations. The throughput graph 911 displays, for each time period, a polygonal line 912a when the obstacle is removed and a polygonal line 912b when the obstacle is not removed. Naturally, throughput is better when the obstacle is removed, so the polygonal line 912a when the obstacle is removed will never be below the polygonal line 912b when the obstacle is not removed.
[0141] By displaying this throughput display area 910, the manager or worker can easily understand the comparison between when the obstacle is not removed and when it is removed, and can therefore make an accurate decision to remove the obstacle.
[0142] The order information display area 920 is an area for displaying information about the order when an obstacle is detected, and displays an order warning message 921, an obstacle removal recommendation message 922, and order information details 923.
[0143] The order warning message 921 is a message warning that the shipping deadline of the ordered item will not be met. The obstacle removal recommendation message 922 is a message indicating the time to remove the obstacle in order to meet the shipping deadline of the ordered item. The order information details 923 displays details of the order in question according to the contents of the order information table 311 shown in FIG. 8.
[0144] As described above, according to the vehicle management device of this embodiment, when an obstacle to transportation occurs in an environment where a vehicle operates, such as a warehouse, the device detects the obstacle and displays the impact of the obstacle on orders and throughput, thereby supporting warehouse operation management. Furthermore, by displaying an obstacle recovery route for a person to work to recover the obstacle and scheduling the operation of the vehicle so that the vehicle does not enter the obstacle recovery route, the worker can safely and quickly remove the obstacle, and the operational efficiency of the vehicle can be improved without stopping the operation of the vehicle.
[0145] 5...Network, 10...Warehouse management server, 20...Entrance / exit locking mechanism, 30...AP, 40...Light control device, 41...LED light, 50...Warehouse, 100...Transported vehicle management device, 101...Warehouse operation unit, 102...Transportation simulation unit, 103...Warehouse operation user interface unit, 200...Transported vehicle, 201...Travel control unit, 202...Transportation control unit, 203...Obstacle detection unit, 300...Layout management DB, 301...Layout management table, 302...Shelf information table, 303...Light position information table, 310...Order / operation schedule DB, 311...Order information table, 312...Scheduling table, 320...Operation instruction DB, 321...PICK command, 322...Shelf return command, 323...Lock command, 324...Unlock command, 325...Turn on command, 326...Turn off command
Claims
1. A vehicle management device that commands the operation of a vehicle that transports items stored on shelves installed in a warehouse according to a schedule, the vehicle management device storing order information related to orders including items, layout information indicating the positions of the vehicle, the positions of the shelves, the positions of warehouse equipment, and the state of the warehouse within the warehouse, and schedule information related to a schedule for operating the vehicle, receiving position information of an obstacle within the warehouse from the vehicle and reflecting the obstacle position information in the layout information, calculating a schedule for operating the vehicle based on the layout information including the obstacle position information and reflecting this in the schedule information, simulating warehouse transportation operations at multiple times based on the schedule information, and outputting the time at which the obstacle should be removed in order to ship the order included in the order information in time according to the results of the simulation of the warehouse transportation operations.
2. The vehicle management device as described in claim 1, characterized in that: a schedule for operating the vehicle is calculated based on first layout information not including position information of the obstacles, and reflected as first schedule information; a simulation of warehouse transportation operations at multiple times based on the first schedule information, and a first throughput for the multiple times based on the results of the simulation of the transportation operations is output; a schedule for operating the vehicle is calculated based on second layout information including position information of the obstacles, and reflected as second schedule information; a simulation of warehouse transportation operations at multiple times based on the second schedule information, and a second throughput for the multiple times based on the results of the simulation of the transportation operations is output; and the first throughput and the second throughput are displayed on a display means in a comparative format.
3. A vehicle management device that commands the operation of a vehicle that transports items stored on shelves installed in a warehouse according to a schedule, the vehicle management device storing order information relating to orders including items, layout information indicating the positions of the vehicle, the positions of the shelves, the positions of warehouse equipment, and the state of the warehouse within the warehouse, and schedule information relating to the schedule for operating the vehicle, receives position information of an obstacle within the warehouse from the vehicle, reflects the obstacle position information in the layout information, calculates an obstacle recovery route from a personnel entrance / exit to the obstacle based on the layout information including the obstacle position information, and displays the obstacle recovery route on a display means.
4. The vehicle management device according to claim 3, characterized in that: information about the obstacle recovery route is reflected in the layout information; a schedule for operating the vehicle is calculated based on the layout information so as to avoid passing through the obstacle and the location of the obstacle recovery route; the schedule information is reflected in the schedule information; and commands are given to the vehicle based on the schedule information.
5. The transport vehicle management device according to claim 3, further comprising: light position information indicating the correspondence between each position in the warehouse and a light; and based on the light position information, controlling the turning on and off of lights for positions on the obstacle recovery route.
6. A vehicle management method using a vehicle management device that commands the operation of a vehicle that transports items stored on shelves installed in a warehouse in accordance with a schedule, wherein the vehicle management device holds order information on orders including items, layout information indicating the positions of the vehicle, the positions of the shelves, the positions of warehouse equipment, and the state of the warehouse within the warehouse, and schedule information on a schedule for operating the vehicle, the vehicle management device having a step of receiving position information of an obstacle in the warehouse from the vehicle and reflecting the position information of the obstacle in the layout information, a step of the vehicle management device calculating a schedule for operating the vehicle based on the layout information including the position information of the obstacle and reflecting the calculated schedule in the schedule information, and a step of the vehicle management device simulating warehouse transportation operations at a plurality of times based on the schedule information, and outputting the time at which the obstacle should be removed in order to make the shipment of the order included in the order information in time according to the results of the simulation of the warehouse transportation operations.
Citation Information
Patent Citations
Modular multifunctional smart storage container
JP2018513817A
Operation controller and operation control system
JP2022052494A
Apparatus and method for warehouse zoning
US20200301432A1
