Physical distribution management method, physical distribution management system, and physical distribution management program

Abstract

To provide a technique for implementing low-cost and consolidated work progress management in a physical distribution system.SOLUTION: A physical distribution management method to be executed by a processor includes: receiving work progress information from one or more systems that control articles handled in each of steps from receiving to shipping; converting the work progress information to standard work progress information represented in a predetermined uniform format; and generating an overall progress dashboard indicating the progress in a physical distribution warehouse based on the standard work progress information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a logistics management method, a logistics management system, and a logistics management program. [Background technology]

[0002] There is provided an article handling system that stores and retrieves articles from shelves, etc. Such an article handling system is composed of a warehouse management system (WMS) that supplies instructions for storing and retrieving articles, a warehouse control system (WCS) that performs storing and retrieving articles, and the like.

[0003] Generally, there are various types of WMS in one warehouse. Furthermore, there are various types of automated equipment controlled by the WCS, such as shelf transport robots, inter-process transport robots, picking robots, and sorters, depending on the warehousing and shipping processes.

[0004] Furthermore, for example, when retrieving (or storing) an item from the warehouse, there are multiple tasks, including tasks performed by a worker and tasks performed by a shelf transport robot. After completing the work, the worker typically uses a handheld terminal to directly notify the WMS of the work results (work progress). Meanwhile, the shelf transport robot uses a scanner or similar device to notify the WCS, which is the shelf transport robot control system, of the work results. The WCS then notifies the WMS of the work results via the warehouse execution system (WES, or WES Hub). In this way, there are multiple means of notifying the work results (work progress) even within the same process.

[0005] For example, Patent Document 1 discloses a technique for efficiently displaying work results from automated devices from different vendors. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Publication No. 2023-173239 Summary of the Invention [Problem to be solved by the invention]

[0007] Managing the work progress of various WCSs that control automated equipment using each WMS poses the problem of development difficulties due to the large number of possible combinations of WMSs and WCSs and the differences between each system. Therefore, there is a need for a WES that can absorb the differences between the multiple systems deployed within a warehouse. Furthermore, as mentioned above, there are multiple ways to notify work results even within the same process, and integrating management using a WES increases development costs.

[0008] The present invention has been made in light of the above circumstances, and its object is to provide a technology that enables integrated management of work progress at low cost in a logistics management system. [Means for solving the problem]

[0009] According to an embodiment, a logistics management method executed by a processor includes receiving work progress information from one or more systems that control items handled at each stage from arrival to shipment, converting the work progress information into standard work progress information expressed in a predetermined unified format, generating an overall progress dashboard that shows the progress status within a logistics warehouse based on the standard work progress information, and displaying the overall progress dashboard. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a logistics management system according to an embodiment. [Figure 2] FIG. 2 is a block diagram illustrating an example of the configuration of a WES Hub according to the embodiment. [Figure 3]FIG. 3 is a block diagram illustrating an example of the configuration of a WES according to the embodiment. [Figure 4] FIG. 4 is a flowchart illustrating an example of the operation of the WES Hub according to the embodiment. [Figure 5] FIG. 5 is a flowchart illustrating an example of the operation of the WES according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of an overall progress dashboard displayed on the display unit according to the embodiment. [Figure 7] FIG. 7 is a diagram showing an example of the productivity by process displayed on the display unit according to the embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the productivity by process (table) displayed on the display unit according to the embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the productivity (graph) by process displayed on the display unit according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] A warehouse operation method, a warehouse operation system, and a warehouse operation program will be described in detail below with reference to the drawings. In the following embodiments, parts with the same numbers perform similar operations, and redundant description will be omitted. For example, when there are multiple identical or similar elements, a common symbol may be used to describe each element without distinguishing between them, or a subnumber may be used in addition to the common symbol to describe each element with distinction between them.

[0012] In the following description, the term "A" or "B" means at least one of A or B, and the term "A," "B," or "C" means at least one of A, B, or C. Furthermore, the term "A" and "B" also means at least one of A and B, and the term "A," "B," and "C" means at least one of A, B, and C.

[0013] [Embodiment] (composition) A logistics management system according to an embodiment is a system that manages the process from receiving goods to shipping them in a logistics system or the like. For example, the logistics management system can manage multiple processes from receiving goods → receiving goods inspection → warehousing → replenishment → (replenishment) → shipping → shipping inspection → packaging → shipping (dispatch). Alternatively, the logistics management system may be a system that manages a series of processes from depanning, which is the unloading of goods loaded onto a vehicle such as a truck, to panning, which is the loading of goods to be shipped onto a vehicle such as a truck. Here, receiving goods refers to the process of receiving goods, and warehousing refers to the process of storing goods in a storage location such as a warehouse. Similarly, shipping refers to the process of dispatching goods, and shipping refers to the process of removing goods from a storage location such as a warehouse.

[0014] For example, the article management system is used in a distribution center, a warehouse, etc. However, the article management system is not limited to a distribution center, a warehouse, etc., and can also be used in, for example, a system for manufacturing articles.

[0015] FIG. 1 is a block diagram showing an example of the configuration of a logistics management system 1 according to an embodiment. As shown in FIG. 1, the logistics management system 1 is made up of a WMS 2, a WCS 3, a WES 4, a WES Hub 10, and the like.

[0016] It is assumed that the WMS 2, the WCS 3, and the WES Hub 10 are arranged in a warehouse within the logistics management system 1, that is, arranged in an on-premise environment.

[0017] The WES Hub 10 is connected to the WMS 2 and the WCS 3 via a local network, etc. Communication between the WES Hub 10 and the WMS 2 and the WCS 3 is possible in both directions. Furthermore, the WES Hub 10 is connected to the WES 4 via an external network, etc. Communication between the WES Hub 10 and the WES 4 is possible in one direction, from the WES Hub 10 to the WES 4.

[0018] Note that the logistics management system 1 may include additional components as needed in addition to the components shown in Figure 1, or certain components may be excluded from the logistics management system 1. For example, while Figure 1 shows one WMS 2 and one WCS 3, multiple WMSs 2 and multiple WCSs 3 may exist. Furthermore, for simplicity, Figure 1 according to this embodiment shows an example in which only the WMS 2 and the WCS 3, which are systems used in the receiving and shipping processes, are connected to the WES Hub 10. However, as described above, the logistics management system 1 may of course connect any number of systems used in each process from receiving to shipping to the WES Hub 10.

[0019] The WMS 2 is called a warehouse management system and can be realized by one or more computers. The WMS 2 also transmits various requests to the WCS 3 via the WES Hub 10.

[0020] For example, the WMS2 transmits a warehousing instruction to the WCS3 via the WES Hub 10, instructing the storage of an item onto a shelf or the like. For example, the warehousing instruction is made up of multiple warehousing slips. The WMS2 also transmits an outgoing instruction to the WCS3 instructing the removal of an item from a shelf or the like. For example, the outgoing instruction is made up of multiple outgoing slips. The WMS2 may also transmit information such as the planned handling quantity, which indicates the amount to be handled in one day, and worker working hours to the WES4 via the WES Hub 10. The WES Hub 10 may also transmit the contents of the warehousing or outgoing instruction to the WES4. By transmitting the contents of the instruction to the WES4, it becomes possible to process more detailed information in addition to the planned handling quantity.

[0021] Furthermore, the WMS 2 receives work results from the workers from handy terminals or the like, and transmits work progress information including the received work results to the WES Hub 10. Note that information included in the work progress information will be described later.

[0022] The WCS 3 is called a warehouse control system and can be realized by one or more computers. The WCS 3 controls automated equipment (material handling equipment) that processes items based on warehousing or shipping instructions from the WMS 2 via the WES Hub 10. For example, the WCS 3 controls a shelf transport robot that transports shelves as automated equipment. The WCS 3 controls the shelf transport robot to transport shelves for picking items or shelves for storing items. The automated equipment is not limited to shelf transport robots, and may be any equipment used for warehousing or shipping, including, for example, picking robots, inter-process transport robots, and sorters.

[0023] Furthermore, the WCS 3 receives work results as control results of the automated devices, creates work progress information including the work results, and transmits the work progress information to the WES Hub 10.

[0024] The WES 4 is called a warehouse operations management system and can be realized by one or more computers. The WES 4 executes various processes related to the operation of the logistics management system 1.

[0025] For example, the WES 4 acquires work progress information transmitted from the WMS 2 and the WCS 3 from the WES Hub 10, which will be described later. The WES 4 manages the received work progress information as a log.

[0026] WES4 also optimizes orders (warehousing inbound or shipping instructions) from WMS2. For example, WES4 optimizes the processing order (order of receiving slips or shipping slips) for an order. WES4 may also split an order into multiple orders. For example, if a shipping instruction contains a shipping slip indicating that the delivery truck departs at 6:00 PM and another shipping slip indicating that the delivery truck departs at 8:00 PM, WES4 will split the order into a shipping instruction including the 6:00 PM shipping slip and a shipping instruction including the 8:00 PM shipping slip.

[0027] Furthermore, as shown in FIG. 1, the WES 4 includes a display unit 46. The display unit 46 includes a display for displaying an overall progress dashboard generated based on the log (work progress information). The manager understands the progress status of the warehouse based on the information displayed on the display unit 46. Furthermore, because the WES 4 generates the information to be displayed on the display unit 46, the display unit 46 may be any display with general display functions and does not necessarily have to be included in the logistics management system 1.

[0028] The WES Hub 10 relays communication between the WMS 2 and the WCS 3. The WES Hub 10 also transmits work progress information transmitted from the WMS 2 and the WCS 3 to the WES 4.

[0029] FIG. 2 is a block diagram showing an example of the configuration of the WES Hub 10 according to the embodiment. As shown in FIG. 2, the WES Hub 10 includes a processor 11, a ROM 12, a RAM 13, an NVM 14, an operation unit 15, a display unit 16, a WMS interface 17, a WCS interface 18, and a WES interface 19.

[0030] The processor 11, the ROM 12, the RAM 13, the NVM 14, the operation unit 15, the display unit 16, the WMS interface 17, the WCS interface 18, and the WES interface 19 are connected to one another via a data bus or the like. Here, WMS2, WCS3, WES4, and WES Hub 10 communicate using a REST API. However, WMS2, WCS3, WES4, and WES Hub 10 may also communicate using a Web API. Furthermore, WES Hub 10 and WES4 may also communicate using any general API.

[0031] 2, the WES Hub 10 may be provided with other components as needed, or certain components may be excluded from the WES Hub 10. For example, if any system used in each process from receiving to shipping is connected, an interface corresponding to that system may be provided.

[0032] The processor 11 has a function of controlling the overall operation of the WES Hub 10. The processor 11 may also include an internal cache and various interfaces. The processor 11 performs various processes by executing programs stored in advance in the internal memory, the ROM 12, or the NVM 14.

[0033] Some of the various functions realized by the processor 11 executing the programs may be realized by hardware circuits. In this case, the processor 11 controls the functions executed by the hardware circuits.

[0034] The ROM 12 is a non-volatile memory that pre-stores control programs, control data, etc. The control programs and control data stored in the ROM 12 are pre-installed in accordance with the specifications of the WES Hub 10.

[0035] RAM 13 is a volatile memory. RAM 13 temporarily stores data being processed by processor 11. RAM 13 stores various application programs based on instructions from processor 11. RAM 13 may also store data required for executing application programs and execution results of application programs.

[0036] The NVM 14 is a nonvolatile memory to which data can be written and rewritten. For example, the NVM 14 is configured with a hard disk drive (HDD), a solid state drive (SSD), or flash memory. The NVM 14 stores control programs, applications, and various data according to the operational purpose of the WES Hub 10.

[0037] The operation unit 15 receives input of various operations from an operator. The operation unit 15 transmits a signal indicating the input operation to the processor 11. For example, the operation unit 15 is configured with a mouse, a keyboard, a touch panel, or the like.

[0038] The display unit 16 displays data from the processor 11. For example, the display unit 16 is configured with a liquid crystal monitor. Note that if the operation unit 15 is configured with a touch panel, the display unit 16 may be formed integrally with the touch panel that serves as the operation unit 15. Furthermore, since the processor 11 generates information to be displayed on the display unit 16, the display unit 16 may be any display having a general display function and does not necessarily have to be provided by the WES Hub 10.

[0039] The WMS interface 17 (first interface) is an interface that transmits and receives data to and from the WMS 2 through bidirectional communication. For example, the WMS interface 17 connects to the WMS 2 via a local network or the like. For example, the WMS interface 17 supports wired or wireless LAN (Local Area Network) connections.

[0040] For example, the WMS 2 receives information including the results of work performed by a worker in a warehousing or warehousing operation. Then, the WMS 2 generates work progress information including the received information and transmits it to the WES Hub 10.

[0041] The WMS interface 17 receives the work progress information sent by the WMS 2 and converts the work progress information into standard work progress information under the control of the processor 11. For example, the WMS interface 17 converts JSON (JavaScript (registered trademark) Object Notation) data used in the REST API into standard data (e.g., CSV (Comma Separated Values) data), or vice versa. Alternatively, the interface 17 converts the JSON data used in the REST API into standard data by remapping it to a predetermined format (i.e., converting JSON data directly into standard data). For example, under the control of the processor 11, the interface 17 converts JSON data into CSV data, converts CSV data into JSON data, or remaps the original data to convert work progress information in the data format used in the REST API into standard work progress information in the standard data format.

[0042] Here, the work progress information includes information such as the shipper, process, status (before work, in progress, work completed), work ID, worker, etc. The process includes information indicating receipt, shipping, warehousing, shipping, etc., as well as information indicating the work process, such as incoming inspection, storage / replenishment, and packaging, and information on the work area, etc. The work progress information may also include time information. Here, the time when the WES Hub 10 received the work progress information may be treated as the time information.

[0043] The WCS interface 18 is an interface that transmits and receives data bidirectionally to and from the WCS 3. For example, the WCS interface 18 connects to the WCS 3 via a local network or the like. For example, the WCS interface 18 supports wired or wireless LAN connections.

[0044] For example, the WCS 3 receives information including the work results of a process performed by a material handling device such as a shelf transport robot, etc. Then, the WCS 3 generates work progress information including the received information and transmits it to the WES Hub 10.

[0045] The WCS interface 18 receives the work progress information sent by the WCS 3 and converts the work progress information into standard work progress information under the control of the processor 11. For example, the WCS interface 18 converts the work progress information into standard work progress information by converting the JSON data format used in the REST API into a standard data format (e.g., CSV data) (or converting CSV data into JSON data, or remapping the original data). Here, the work progress information includes information such as the shipper, process, status (before work, during work, work completed), work ID, and equipment ID.

[0046] Generally, even if the work progress information sent by WCS3 and the work progress information sent by WMS2 use the JSON data format, the items included will differ depending on the worker and the automated equipment, the process, or the vendor that provides WMS2 or WCS3. For example, the items included in the work progress information do not have the same names because the vendors that supply WMS2 and WCS3 are different. Therefore, the work progress information received from WMS2 or WCS3 will be in a different format.

[0047] Therefore, in this embodiment, the WMS interface 18 and WCS interface 18 convert work progress information into standard work progress information so that the information has the same format under the control of the processor 11. Therefore, the WES Hub 10 converts work progress information that differs depending on the system to which it is connected into standard work progress information. For example, the WES Hub 10 can accept work progress information sent from a system in any format.

[0048] The WES interface 19 is an interface that transmits and receives data to and from the WES 4 via bidirectional communication. For example, the WES interface 19 connects to the WES 4 via an external network (e.g., the Internet). For example, the WES interface 19 supports wired or wireless LAN connections. For example, the WES interface 19 transmits standard work progress information to the WES 4 under the control of the processor 11.

[0049] The WMS interface 17, the WCS interface 18, and the WES interface 19 (or parts of these) may be integrally configured.

[0050] The WES Hub 10 may also be equipped with an interface for connecting to an external display unit. In this case, the WES Hub 10 does not need to be equipped with the display unit 16. Furthermore, if a system other than the WMS 2 and WCS 3 that handles processes from receiving to shipping is connected to the WES Hub 10, the WES Hub 10 may be equipped with an interface compatible with that system. The WES Hub 10 may then convert the work progress information received from that system into standard work progress information.

[0051] FIG. 3 is a block diagram showing an example of the configuration of the WES 4 according to the embodiment. As shown in FIG. 3, the WES 4 includes a processor 41, a ROM 42, a RAM 43, an NVM 44, an operation unit 45, a display unit 46, a WES Hub interface 47, and the like.

[0052] The processor 41, the ROM 42, the RAM 43, the NVM 44, the operation unit 45, the display unit 46, and the WES Hub interface 47 are connected to one another via a data bus or the like. It should be noted that the WES4 may include other components as required in addition to the components shown in FIG. 3, and certain components may be excluded from the WES4.

[0053] The processor 41 has a function of controlling the overall operation of the WES 4. The processor 41 may also include an internal cache and various interfaces. The processor 41 performs various processes by executing programs stored in advance in the internal memory, the ROM 42, or the NVM 44.

[0054] Some of the various functions realized by the processor 41 executing the programs may be realized by hardware circuits. In this case, the processor 41 controls the functions executed by the hardware circuits.

[0055] The ROM 42 is a non-volatile memory that pre-stores control programs, control data, etc. The control programs and control data stored in the ROM 42 are pre-installed in accordance with the WES4 specifications.

[0056] The RAM 43 is a volatile memory. The RAM 43 temporarily stores data being processed by the processor 41. The RAM 43 stores various application programs based on instructions from the processor 41. The RAM 43 may also store data necessary for executing the application programs and the execution results of the application programs.

[0057] The NVM 44 is a non-volatile memory to which data can be written and rewritten. For example, the NVM 44 may be configured with a HDD, SSD, or flash memory. The NVM 44 stores control programs, applications, and various data depending on the operational purpose of WES4.

[0058] The operation unit 45 receives input of various operations from an operator. The operation unit 45 transmits a signal indicating the input operation to the processor 41. For example, the operation unit 45 is configured with a mouse, a keyboard, a touch panel, or the like.

[0059] The display unit 46 displays data from the processor 41. For example, the display unit 46 is configured with a liquid crystal monitor. Note that, when the operation unit 45 is configured with a touch panel, the display unit 46 may be formed integrally with the touch panel serving as the operation unit 45.

[0060] The WES Hub interface 47 is an interface that transmits and receives data to and from the WES Hub 10 via one-way communication. For example, the WES Hub interface 47 connects to the WES Hub 10 via an external network (e.g., the Internet). For example, the WES Hub interface 47 supports wired or wireless LAN connections. The WES Hub interface 47 may be any general interface that can read standard work progress information. In other words, it does not have to be an interface that can read various data formats from the WMS2 and WCS3.

[0061] In this embodiment, the WES Hub 10 and the WES4 are described as separate devices, but they may be a single device. That is, the operations performed by the WES Hub 10 may be performed by the WES4, and vice versa.

[0062] (operation) First, an example of the operation of the WES Hub 10 will be described. FIG. 4 is a flowchart illustrating an example of the operation of the WES Hub 10 according to the embodiment. The operation of this flowchart is realized by the processor 11 of the WES Hub 10 reading and executing a program stored in the internal memory of the processor 11, the ROM 12, or the NVM 14.

[0063] For example, in a warehousing or receiving process, a worker uses a handheld terminal to send work results to the WMS 2. The WMS 2 starts this flowchart by sending work progress information, including the work results, to the WES Hub 10. Alternatively, an automated device uses a handheld scanner to send work results to the WCS 3. The WCS 3 starts this flowchart by sending work progress information, including the work results, to the WES Hub 10.

[0064] In step ST101, the processor 11 receives work progress information via the WMS interface 17 or the WCS interface 18.

[0065] In step ST102, processor 11 converts the work progress information into standard work progress information. For example, processor 11 converts work progress information stored in ROM 42 or the like into standard work progress information that represents items that differ depending on the acquisition destination and process in a unified format. Specifically, for example, processor 11 converts JSON data into CSV data that is represented in a predetermined unified format (or converts CSV data into JSON data that is represented in a predetermined unified format), thereby converting the work progress information into standard work progress information. Alternatively, processor 11 converts the JSON data (or CSV data) into JSON data (or CSV data) that is represented in a unified format by remapping the JSON data (or CSV data), thereby converting the work progress information into standard work progress information.

[0066] In step ST103, the processor 11 transmits the standard work progress information to the WES 4 via the WES interface 19.

[0067] In step ST104, the processor 11 determines whether the operation is continuing. If it is determined that the operation is continuing, the process returns to step ST101. For example, the processor 11 waits until new work progress information is received. On the other hand, if it is determined that the operation is not continuing, that is, that the operation has ended, the process ends.

[0068] Next, an example of the operation of WES4 will be described. FIG. 5 is a flowchart illustrating an example of the operation of the WES4 according to the embodiment. The operation of this flowchart is realized by the processor 41 of the WES4 reading and executing a program stored in the internal memory of the processor 41, the ROM 12, or the NVM 14.

[0069] For example, as described with reference to FIG. 4, this flowchart begins when the WES Hub 10 transmits standard work progress information to the WES 4 through the WES interface 19 .

[0070] In step ST201, the processor 41 receives standard work progress information through the WES Hub interface 47. The processor 41 may store the standard work progress information in the ROM 42 or the like.

[0071] In step ST202, the processor 41 updates the overall progress dashboard based on the standard work progress information. For example, if an overall progress dashboard has not been created, the processor 41 creates the overall progress dashboard based on the standard work progress stored in the ROM 42 or the like. Alternatively, if an overall progress dashboard has been created, the processor 41 updates the overall progress dashboard that was created immediately before, based on the standard work progress information.

[0072] In step ST203, the processor 41 controls so that the updated overall progress dashboard is displayed on the display unit 46. The manager can check the progress of the entire work from the overall progress dashboard displayed on the display unit 46.

[0073] FIG. 6 is a diagram showing an example of an overall progress dashboard displayed on the display unit 46 according to the embodiment. As shown in Figure 6, the overall progress dashboard can display all processes related to receiving and shipping. In other words, the overall progress dashboard includes processes from receiving to shipping. Furthermore, the overall progress dashboard can also display progress information for different areas within the same process. This is because WES4 can handle work related to all processes collectively by converting it into standard work progress information.

[0074] Furthermore, the overall progress dashboard is generated so that it can display the entire process from receipt to shipment. Using the generated overall progress dashboard, the manager can check which process is experiencing delays in work, etc.

[0075] As shown in Fig. 6, the overall progress dashboard is generated so that it can display the work process indicating which process it is, the completed quantity indicating the number of tasks completed, the planned progress indicating the progress of the planned work, the planned quantity to be handled indicating the amount to be handled in one day, and the predicted completion time. Furthermore, the overall progress dashboard is generated so that it can display the work progress (completed quantity / planned quantity to be handled) using a progress bar.

[0076] The planned progress is calculated, for example, by allocating evenly from the work start time to the estimated work time calculated in advance so that the entire planned handling quantity is completed. Here, the estimated work time is calculated, for example, from the truck departure time or the worker's working hours, or the estimated handling quantity received from the WMS 2 is calculated from the number of workers for that day and the past average working speed. Note that the past average working speed is assumed to be stored in the ROM 42 or the like. Furthermore, the work start time may be, for example, the time when the first work status was received or the time included in the standard work progress information.

[0077] In step ST204, the processor 41 determines whether there is a delay in the process. If the completed quantity is greater than the work progress, it indicates that the work is progressing smoothly. In this case, the process proceeds to step ST205. On the other hand, if the completed quantity is less than the planned progress, it indicates that the work is behind schedule. In such a case, the processor 41 generates an overall progress dashboard so that the progress bar and the relevant items are highlighted, for example, in red as a warning (in the example of FIG. 6, they are expressed in grayscale). In this case, the process proceeds to step ST206.

[0078] In step ST205, it is determined whether the operation is continuing. If it is determined that the operation is continuing, the process returns to step ST201. For example, if there are no delayed processes when checking the overall progress dashboard, it means that the work is progressing smoothly. Therefore, the manager can continue to check the updates of the overall progress dashboard until the operation is completed. On the other hand, if it is determined that the operation is not continuing, that is, the operation has completed, the process ends.

[0079] In step ST206, the processor 41 controls to display the productivity by process. If it is determined in step ST204 that there is a delay in a process, that is, if it is determined that the completed quantity is less than the planned progress, the processor 41 generates the productivity by process for the delayed process based on the standard work progress information. Then, the processor 41 controls to display the generated productivity by process on the display unit 46. Alternatively, if there is a process that is delayed, the manager presses the relevant process. Upon detecting the press, the processor 41 may generate the productivity by process based on the pressed information (i.e., which productivity by process is to be generated) and the standard work progress information, and control to display the productivity by process on the display unit 46.

[0080] FIG. 7 is a diagram showing an example of the productivity by process displayed on the display unit 46 according to the embodiment. As shown in Figure 7, productivity by process displays the reliability of the completion forecast, current productivity, work status, and data details. You can also check past performance by selecting a date from the calendar or entering a date directly. For example, by specifying a specific date or period, such as a day of the week, the beginning of the month, or the end of the month, you can use this information as a reference for the predicted completion time and logistics volume.

[0081] For example, the predicted completion time is updated based on the actual shipping work instruction quantity sent by WMS2. For example, if the planned handling quantity is 1000 and the actual shipping work instruction quantity is 1200, the predicted completion time can be set to the time when the work time is extended by 20%. Also, if the planned handling quantity is 1000 and work instruction quantities up to 500 have been received, the reliability of the completion prediction will be displayed as 50% (number received / planned quantity), which shows whether the predicted completion time is likely to be updated in the future.

[0082] Current productivity is a graph that shows the current productivity and the average productivity of the selected area, with time on the horizontal axis and the number of processed lines on the vertical axis. This graph shows how much the current productivity differs from the average.

[0083] The work status is a graph that shows the number of processed lines, the number of planned processed lines, the number of received lines, the estimated total number of lines, the estimated total number of lines, and the planned progress, with time on the horizontal axis and the number of lines on the vertical axis. This graph allows managers to understand the progress of work in more detail. For example, by looking at the work status at a specified time interval, it is possible to see times when work is behind schedule (when the quantity is low).

[0084] The data details are a table showing the details of the data used for each graph, and include information such as the number of lines received, the predicted number of lines, the number of lines processed, the predicted number of remaining lines, shipping productivity, progress, the average number of workers, and the predicted completion time. The predicted number of lines may be included in the standard progress information, but it may also be predicted from past actual values. For example, the average for the past few weeks on the same day of the week may be used. The predicted number of remaining lines is calculated by subtracting the number of lines received from the predicted number of lines.

[0085] In step ST207, processor 41 determines whether or not to display the individual productivity (table). For example, processor 41 determines whether or not the individual productivity display button displayed in the process productivity shown in FIG. 7 has been pressed. If it is determined that it has been pressed, the process proceeds to step ST208. On the other hand, if it is determined that it has not been pressed, the process proceeds to step ST205.

[0086] In step ST208, processor 41 performs control to display the individual productivity (table). Processor 41 generates the individual productivity (table) based on the pressed information (i.e., for which worker the productivity (table) is to be generated) and the standard work progress information. Then, processor 41 performs control to display the individual productivity (table) on display unit 46.

[0087] FIG. 8 is a diagram showing an example of personal productivity (table) displayed on the display unit 46 according to the embodiment. As shown in FIG. 8, the individual productivity (table) displays information on the cumulative amount of completed work for each task ID and worker at a predetermined time interval as man-hour productivity. In other words, the individual productivity displays the cumulative information on the standard work progress information for each worker. The processor 41 may also perform control so that man-hour productivity values ​​lower than a predetermined threshold are highlighted. In the example of FIG. 8, the highlighting is represented by diagonal lines. By displaying in this manner, the manager can grasp which worker is late and at what time.

[0088] In step ST209, processor 41 determines whether or not to display personal productivity (graph). For example, processor 41 determines whether or not the graph display button displayed in the personal productivity (table) shown in Fig. 8 has been pressed. If it is determined that it has been pressed, the process proceeds to step ST210. On the other hand, if it is determined that it has not been pressed, the process proceeds to step ST205.

[0089] In step ST210, processor 41 performs control to display the individual productivity (graph). Processor 41 generates the individual productivity (graph) based on the pressed button (i.e., an instruction as to which worker the graph is to be generated for) and the standard work progress information. Then, processor 41 performs control to display the individual productivity (graph) on display unit 46.

[0090] FIG. 9 is a diagram showing an example of personal productivity (graph) displayed on the display unit 46 according to the embodiment. As shown in Figure 9, the productivity of each worker is shown with time on the horizontal axis and labor-hour productivity on the vertical axis. This allows managers to understand the delays of each worker and the time periods when they were delayed.

[0091] In the above operation, an example has been described in which the overall progress dashboard, productivity by process, and individual productivity are displayed in that order. However, in this embodiment, it is not necessary to display them in this order. For example, if the manager wants to display individual productivity first, the individual productivity may be displayed first. That is, in this embodiment, the overall progress dashboard, productivity by process, and individual productivity may be displayed in any order on the display unit. Furthermore, the processor 11 may control the individual productivity (table) and individual productivity (graph) to be displayed together as individual productivity, or it may of course control the display so that either one of them is displayed as individual productivity. That is, in this embodiment, individual productivity refers to either or both of the individual productivity (table) and individual productivity (graph).

[0092] (Effects of the embodiment) According to the embodiment described above, WES Hub 10 converts work progress information received from WMS 2 and WCS 3 into standard work progress information and provides it to WES 4. As a result, WES 4 only needs to be equipped with an interface that can acquire the standard work progress information. In other words, WES 4 does not need to support work progress information in various data formats, and work progress management can be performed by WES 4 at low cost.

[0093] (Variation) There may be cases where work is performed solely by manual labor without any automated equipment, or where the WMS 2 acquires information from the WCS 3 and provides work progress information to the WES 4 via the WES Hub 10. In such cases, the WES Hub 10 only needs to be equipped with the WMS interface 17, which simplifies the configuration of the WES Hub 10.

[0094] Furthermore, the process of retrieving or retrieving goods may be managed as a single retrieving or retrieving process, rather than managing the automated equipment and the people separately. Alternatively, the same people may be managed separately by area.

[0095] The program according to this embodiment may be transferred in a state where it is stored in an electronic device, or in a state where it is not stored in an electronic device. In the latter case, the program may be transferred via a network, or in a state where it is stored in a storage medium. The storage medium is a non-transitory tangible medium. The storage medium is a computer-readable medium. The storage medium may be in any form, such as a CD-ROM or a memory card, as long as it is capable of storing the program and is computer-readable.

[0096] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0097] 1. Logistics management system 2. WMS 3…WCS 4…WES 41...Processor 42...ROM 43...RAM 44...NVM 45...Operation unit 46…Display section 47…WES Hub interface 10. WES Hub 11...Processor 12...ROM 13...RAM 14...NVM 15...Operation unit 16…Display section 17…WMS interface 18...WCS interface 19…WES interface

Claims

1. A logistics management method executed by a processor, comprising: receiving work progress information from one or more systems that control items handled at each stage from receiving to shipping; converting the work progress information into standard work progress information expressed in a predetermined unified format; generating an overall progress dashboard showing the progress status of each process based on the standard work progress information; A logistics management method comprising:

2. the converting converts the work progress information into the standard work progress information by remapping the work progress information; The logistics management method according to claim 1.

3. The converting converts the work progress information into the standard work progress information by converting JSON data into CSV data or vice versa. The logistics management method according to claim 1.

4. The overall progress dashboard includes the process from the receipt to the shipment. The logistics management method according to claim 1.

5. The overall progress dashboard is generated to display the process in order from the receipt to the shipment. The logistics management method according to claim 1.

6. the overall progress dashboard includes progress information for different areas within the same process; The logistics management method according to claim 1.

7. The overall progress dashboard is generated so as to display a completed quantity indicating the number of completed tasks, a planned progress indicating the progress of the planned tasks, a planned quantity to be handled in one day, and a predicted completion time, and highlights any cases where the completed quantity is less than the planned progress. The logistics management method according to claim 1.

8. If the completed quantity is less than the planned progress, a process-by-process productivity indicating the productivity of the process determined to have a small completed quantity is generated. The logistics management method according to claim 7.

9. The productivity by process includes at least a reliability of a completion prediction, and the reliability of the completion prediction is calculated based on the planned handling quantity. The logistics management method according to claim 8.

10. Displaying the overall progress dashboard or the process productivity; When displaying the productivity by process, determining whether or not to display individual productivity; When it is determined that the individual productivity progress is to be displayed, generating the individual productivity progress based on the standard work progress information; displaying said personal productivity progress; The logistics management method according to claim 8, further comprising:

11. Displaying the personal productivity includes displaying the number of tasks completed per predetermined time period as a cumulative total, and highlighting the cumulative total of the tasks completed within the predetermined time period if the cumulative total is equal to or less than a predetermined threshold. The logistics management method according to claim 10.

12. Displaying the individual productivity includes displaying the individual productivity for each worker as a graph. The logistics management method according to claim 10.

13. a warehouse operation system Hub connected to one or more systems that control items handled at each process from receiving to shipping; a warehouse operation system connected to the warehouse operation system hub; The warehouse operation system Hub comprises: an interface for receiving work progress information from the one or more systems; a processor that converts the work progress information into standard work progress information expressed in a predetermined unified format; a standard interface for transmitting the standard work progress information to the warehouse operation system; The warehouse operation system comprises: a processor for generating an overall progress dashboard based on the standard work progress information; A logistics management system equipped with

14. 1. A logistics management program comprising instructions for execution by a processor, the instructions comprising: receiving work progress information from one or more systems that control items handled at each stage from receiving to shipping; converting the work progress information into standard work progress information expressed in a predetermined unified format; generating an overall progress dashboard showing the progress status within the logistics warehouse based on the standard work progress information; A logistics management program that includes:

Images