Warehouse work management system, warehouse work management method and program

Abstract

To allow a user to quickly correct a delay of progress due to troubles during warehouse work.SOLUTION: A warehouse work management system for managing a work amount based on the staff for each step of warehouse work and the order of shipping acquires completion information for each work step of the entire warehouse, compares the acquired completion information and work steps in a work plan made in advance, calculates the progress of the work steps, issues an alert on the basis of the result of the calculation when the progress of the work steps is not larger than a threshold value, makes a recovery plan with changed staff and / or changed work contents every time the alert is issued, simulates the made recovery plan, and calculates the benefit of the total work for the day on the basis of the recovery plan.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technology that is effective for real-time optimization of warehouse operations. [Background technology]

[0002] Systems for optimizing warehouse work have been proposed in the past. For example, Patent Document 1 discloses a work planning system that can create and optimize an overall work plan, including resource allocation, for work according to multiple shipping orders. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-33873 Summary of the Invention [Problem to be solved by the invention]

[0004] However, even if a warehouse work plan is made, on the day, a warehouse worker may be unable to come to work due to illness or other reasons, resulting in changes to the warehouse workforce, or a shipping order may be generated that requires an emergency response, causing a change in the amount of work, and the planned warehouse work plan may fall apart on the day. In this case, it is necessary to change the original work plan to accommodate the shipping order, but even in such a case, it is desirable that the profit from the warehouse work on that day does not deviate significantly from the original work plan. Therefore, the inventors focused on a system that would grasp the progress of warehouse work in real time while the warehouse is in operation, and provide a simulation of how to change the work plan to maximize profits from the warehouse work on that day.

[0005] An object of the present invention is to provide a warehouse operation management system, a warehouse operation management method, and a program that enable quick correction of delays in progress due to problems during warehouse operations. [Means for solving the problem]

[0006] The present invention is a warehouse operation management system that manages the amount of work based on the number of workers and shipping orders in each process of warehouse operations, an acquisition unit that acquires completion information of each work process in the entire warehouse; a calculation unit that compares the acquired completion information with a work process in a work plan that has been created in advance, and calculates a progress status of the work process; an alert notification unit that issues an alert when the progress of the work process is equal to or less than a threshold based on the calculation result; a creation unit that creates a recovery plan in which the workers and / or work content are changed each time the alert is notified; a simulator that simulates the created recovery plan and calculates the profit of the entire work for that day based on the recovery plan; The present invention provides a warehouse operation management system comprising:

[0007] According to the present invention, a warehouse work management system that manages the amount of work based on the number of workers and shipping orders at each process of warehouse operations acquires completion information for each work process throughout the warehouse, compares the acquired completion information with the work processes in a work plan created in advance, calculates the progress of the work process, and based on the calculation results, issues an alert if the progress of the work process is below a threshold value.Each time the alert is issued, a recovery plan is created in which the number of workers and / or the work content are changed, the created recovery plan is simulated, and the profit for the entire work for that day based on the recovery plan is calculated.

[0008] Although the present invention is categorized as a system, the same effects and advantages can be obtained even when it is a method or a program. [Effects of the Invention]

[0009] According to the present invention, it is possible to quickly correct delays in progress due to problems during warehouse operations. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an overview of a warehouse operation management system 1. [Figure 2] FIG. 1 is a diagram illustrating a functional configuration of a warehouse operation management system 1. [Figure 3] FIG. 10 is a flowchart of a shipping order acquisition process executed by the warehouse operation management system 1. [Figure 4] 10 is a flowchart showing a work plan acquisition process executed by the warehouse work management system 1. FIG. [Figure 5] 10 is a flowchart showing a manpower shortage notification process executed by the warehouse operation management system 1. FIG. [Figure 6] 10 is a flowchart showing an alert notification process executed by the warehouse operation management system 1. FIG. [Figure 7] FIG. 6 is a diagram showing an example of a calculation result 60. [Figure 8] 10 is a diagram showing an example of an alert 70 sent to the administrator terminal 40. FIG. [Figure 9] FIG. 10 is a flowchart of a recovery plan creation process executed by the warehouse operation management system 1. [Figure 10] 10 is a diagram showing an example of a change input UI 80 displayed on the administrator terminal 40. FIG. [Figure 11] 10 is a diagram showing an example of a change input UI 86 displayed on the administrator terminal 40. FIG. [Figure 12] 10 is a flowchart showing a work plan determination process executed by the warehouse work management system 1. FIG. [Figure 13] FIG. 10 is a diagram schematically illustrating an example of a simulation result. [Figure 14] FIG. 10 is a diagram schematically illustrating an example of a simulation result in which rearrangement is performed. [Figure 15] FIG. 10 is a diagram schematically illustrating an example of a simulation result in which rearrangement is performed. [Figure 16] 10 is a diagram showing an example of a simulation result 90 output to the administrator terminal 40. FIG. [Figure 17] 10 is a diagram showing an example of a simulation result 90 output to the administrator terminal 40. FIG. [Figure 18] 10 is a diagram showing an example of a simulation result 90 output to the administrator terminal 40. FIG. [Figure 19] 10 is a diagram showing an example of a simulation result 90 output to the administrator terminal 40. FIG. [Figure 20] FIG. 10 is a flowchart showing a process of notifying the warehouse operation management system 1 that the work can be advanced. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention (hereinafter referred to as "embodiments") will be described in detail with reference to the accompanying drawings. In the following drawings, the same elements are designated by the same numbers or symbols throughout the description of the embodiments.

[0012] [Basic concept / basic configuration] 1 is a diagram illustrating an overview of a warehouse operation management system 1. The warehouse operation management system 1 is a system equipped with at least a computer 10 and managing the amount of work based on the number of workers and shipping orders in each process of warehouse operations. In this embodiment, the warehouse operation management system 1 is a system connected so as to be able to perform data communications with a computer 10, a WMS (Warehouse Management System) 20 that manages shipping orders, an RCS (Resource Control System) 30 that manages work plans, a manager terminal 40 carried by a manager that manages warehouse workers and work contents, and a shift management system 50 that is an attendance management system that manages the working status of each warehouse worker, such as attendance, working hours, lateness, early departure, breaks, and absences, using shift data and the like.

[0013] This embodiment is based on the premise that a work plan for the day has been created or saved in advance, and this work plan is used. It is desirable that the work plan be automatically created by the RCS 30 and automatically output to the computer 10, but this is not a limitation. While the warehouse work processes are assumed to include receiving, warehousing, picking, distribution processing, packaging, and shipping, the processes are not limited to these. In this specification, profit includes not only simple gross profit but also sales, expenses, income and expenditure, and profit margin.

[0014] An outline of the processing steps when the warehouse operation management system 1 calculates the profit of the entire operation for the day based on changes in the number of workers and / or the operation content will be described with reference to FIG.

[0015] The computer 10 acquires the shipping orders and work plans for the day (step S0). The shipping order is data including, for example, a product ID, shipping quantity, and deadline date and time. The work plan is, for example, the number of warehouse workers for each process in the warehouse work and the work content (for example, work time, work volume). The WMS 20 receives shipping orders from an administrator via the administrator terminal 40. Of the received shipping orders, the WMS 20 transmits those for the day to the computer 10. Note that the WMS 20 can also be configured to transmit shipping orders acquired from a customer system managed by the customer to the computer 10. The RCS 30 transmits the work plan for the day among the work plans that have been created or saved to the computer 10 . The computer 10 receives these shipping orders and work plans from the WMS 20 or the RCS 30, thereby obtaining the shipping orders and work plans for the current day.

[0016] The computer 10 acquires completion information for each work process in the entire warehouse (step S1). The computer 10 acquires completion information for each work process that has been completed in the entire warehouse in real time. The RCS 30 transmits information on the completion of each work process in the entire warehouse to the computer 10 . The computer 10 receives this completion information and thereby acquires the completion information.

[0017] The computer 10 compares the acquired completion information with the work process in the work plan created in advance, and calculates the progress of the work process (step S2). The progress status may be, for example, the impact on the work plan (progress rate against the work plan, amount of work completed, and amount of work required according to the work plan), the difference in profit due to the progress status (impact on income and expenditure), and the man-hours required to recover the progress status (required man-hours). The computer 10 compares the acquired completion information with the work process in the acquired work plan for the day, and calculates the progress of the work process in the entire warehouse in real time.

[0018] Based on the calculation result, if the progress of the work process is equal to or less than the threshold, the computer 10 issues an alert (step S3). The computer 10 creates an alert that includes a floor map showing the location where a work process has occurred where the progress of the work process is below a threshold, the progress status, received orders, etc. The computer 10 transmits the created alert to the manager terminal 40. The administrator terminal 40 receives this alert and displays it on its own display unit. The computer 10 displays the created alert on the manager's terminal 40, and notifies the manager of the alert if the progress of the work process is below a threshold based on the calculation results. More preferably, the computer 10 simulates a plan in which the work is carried out without compensation for the progress, calculates the expected profit for the entire work for that day, and notifies the manager's terminal 40 of the overtime work. Here, if the result is that the time specified in the shipping order is exceeded, an error may be displayed indicating that the plan is difficult. The administrator can see the displayed alert and become aware of the delay in progress.

[0019] The computer 10 creates a recovery plan with changes to the workers and / or work content each time an alert is notified (step S4). Every time an alert is issued, the computer 10 accepts, via the administrator terminal 40, a request to change the workers and / or the work content for the work plan created in advance. The manager checks the alert notified to the manager terminal 40 and determines whether or not it is necessary to change the allocation of workers and / or input changes to the work content. The manager terminal 40 can accept inputs of changes to the allocation of workers and / or changes to the work content, and if the manager determines that changes to the work content are necessary, he or she inputs the changes. The specific changes are as follows: For example, these plans include a plan to reassign work that is behind schedule to other workers, a plan to divide the day into morning and afternoon, maintaining the original work assignments in the morning except for the work that is behind schedule, and reassigning work that is behind schedule in the afternoon, a plan to extract work that is not a problem or will cause little problem if the number of workers is reduced from among the work that was originally assigned to multiple people, and reassigning workers to the work that is behind schedule, a plan to extract work that is not a problem if it is performed the next day or later, reassigning that work to the next day or later, consolidating it into work that can be done by the current workers, and re-creating the work and reassigning the workers, etc. The administrator terminal 40 may accept such change plans one by one, or may be capable of inputting multiple plans, or may be capable of inputting multiple plans along with their priorities. The administrator terminal 40 transmits the accepted changes to the computer 10 for the above-mentioned purposes. By receiving the changes, the computer 10 accepts changes to the workers and / or work details for the acquired work plan. The computer 10 creates a recovery plan for the work plan based on the received changes. Based on these changes, the computer 10 creates a recovery plan, which is a work plan that compensates for the work process that is behind schedule in the original work plan for that day. This recovery plan reflects the above-mentioned changes in the work plan for that day from the time of selection onwards.

[0020] The computer 10 simulates the created recovery plan and calculates the profit of the entire work for that day based on the recovery plan (step S5). The computer 10 simulates the created recovery plan and calculates sales and expenses for the recovery plan. The computer 10 subtracts expenses from the calculated sales to calculate income and expenditures. By performing these calculations, the computer 10 calculates profits. Furthermore, the computer 10 calculates the work efficiency (total required time, cut time margin, margin rate, excess man-hours) for the recovery plan. The total required time is the time taken in the simulation results (the time it would actually take if warehouse work was performed according to this recovery plan), and is the time required from the start time of the work to the end time of the work. The cut time is the deadline set for each package to be shipped. The cut time slack time is the time obtained by subtracting the total required time from the cut time (the time between the end time of the work and the cut time). The slack rate is the ratio of the cut time slack time to this cut time. The excess manpower time is the number of people required per unit time when the cut time slack time is negative.

[0021] Based on the recovery plan thus obtained, the computer 10 determines the work plan for the day after the selection time. The warehouse workers perform the actual warehouse work in accordance with the determined work plan. Although the above description is based on an example in which a worker accepts a change to the work plan acquired by the computer 10, the same applies when the amount of work changes. The computer 10 notifies the manager terminal 40 of the change in the amount of work, and notifies the manager terminal 40 of whether the work can be completed within the scheduled work time, and more preferably, calculates the profit and notifies the manager terminal 40 of the deviation from the original plan (profit loss).

[0022] Such a warehouse operation management system 1 makes it possible to quickly correct delays in progress due to problems during warehouse operations. In addition, if the manpower plan and work plan predicted the previous day differ from the shipping order for that day, it is possible to recommend how to change the predicted manpower plan and work plan to meet the shipping order in time, and to perform a balance simulation in that case.

[0023] [Function Configuration] The functional configuration of the warehouse operation management system 1 will be described with reference to FIG. The warehouse operation management system 1 includes at least a computer 10, which is connected to a WMS 20 that manages shipping orders, an RCS 30 that manages work plans, a manager terminal 40 carried by a manager that manages warehouse workers and work contents, and a shift management system 50 that is an attendance management system that manages the working status of each warehouse worker using shift data, etc., via a network 9 such as a public line network or an intranet, so that data can be communicated. The warehouse operation management system 1 may include, in addition to the computer 10, a WMS 20, an RCS 30, a manager terminal 40, a shift management system 50, and other terminals and devices. In this case, the warehouse operation management system 1 executes the processes described below using any one or a combination of the included terminals, devices, systems, etc.

[0024] The computer 10 is a computer with server functionality, a personal computer, or the like, and manages the workload based on the number of workers and shipping orders in each process of warehouse operations. The computer 10 may be realized, for example, by a single computer, or by multiple computers, such as a cloud computer. The cloud computer in this specification may refer to either a computer that uses any computer in a scalable manner to perform a specific function, or a computer that includes multiple functional modules to realize a system and uses the functions in any combination.

[0025] The computer 10 has a control unit including a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), etc., and a communication unit including a device for enabling communication with other terminals and devices, an acquisition unit 11 for acquiring completion information of work processes, and an alert notification unit 12 for notifying alerts depending on the progress of the work processes. The computer 10 also includes a data storage unit such as a hard disk, semiconductor memory, storage medium, or memory card as a storage unit. The computer 10 also includes, as processing units, various devices that execute various processes, a calculation unit 13 that calculates the progress of the work process, a creation unit 14 that creates a recovery plan with changes to the workers and / or work content, and a simulator 15 that simulates the recovery plan and calculates profits.

[0026] In computer 10, the control unit loads a specified program and works in cooperation with the communication unit to realize a shipping order acquisition module, a work plan acquisition module, a shift data acquisition module, a personnel shortage notification module, a completion information acquisition module, an alert notification module, a change acceptance module, a recovery plan output module, a selection acceptance module, and an advancement possibility notification module. In addition, in the computer 10, the control unit reads a predetermined program, thereby realizing a shipping order storage module, a work plan storage module, and a recovery plan storage module in cooperation with the storage unit. In addition, in computer 10, the control unit reads a specified program and works in cooperation with the processing unit to realize a shortage personnel detection module, a shortage personnel judgment module, a shortage personnel assignment work identification module, a progress status calculation module, a progress status judgment module, an alert creation module, a recovery plan creation module, a simulation module, a profit calculation module, a work efficiency calculation module, a simulation result creation module, a sorting module, a work plan determination module, and an early termination judgment module.

[0027] The WMS 20 may be a general-purpose system for managing the inflow and outflow of goods from a warehouse, and a detailed description thereof will be omitted. RCS30 is sufficient as long as it is a system for managing general-purpose warehouse equipment, and details thereof will be omitted. The administrator terminal 40 is a terminal such as a mobile terminal such as a mobile phone, smartphone, tablet terminal, or personal computer owned by the administrator, and is equipped with a CPU, GPU, RAM, ROM, etc. as a terminal control unit, devices for enabling communication with the computer 10 as a communication unit, and various devices for performing input and output of screens, data, etc. as an input / output unit. The shift management system 50 may be a general-purpose system for managing the working status of warehouse workers, and details thereof will be omitted.

[0028] Hereinafter, each process executed by the warehouse operation management system 1 will be described together with the process executed by each of the modules described above. In this embodiment, the processes assumed in warehouse operations include receiving goods, storing goods, picking, distribution processing, packaging, shipping, etc., and profit includes not only simple gross profit but also sales, expenses, income and expenditure, and profit margin.

[0029] [Shipping order acquisition process executed by computer 10] The shipping order acquisition process executed by the computer 10 will be described with reference to Fig. 3. The figure shows a flowchart of the shipping order acquisition process executed by the computer 10. The shipping order acquisition process is a detailed flow related to the shipping order acquisition process among the above-mentioned processes (step S0) for acquiring a shipping order and a work plan.

[0030] The shipping order acquisition module acquires shipping orders for the day (step S10). As mentioned above, the shipping order is data that includes the product ID, shipping quantity, deadline date and time, etc. The manager terminal 40 accepts the input of a shipping order from the manager, and transmits the accepted shipping order to the WMS 20. The WMS 20 receives this shipping order and stores it in its own memory, etc. The WMS 20 extracts shipping orders for the current day from the stored shipping orders and transmits them to the computer 10. Note that the WMS 20 can also be configured to transmit shipping orders obtained from a customer system managed by the customer to the computer 10. The shipping order acquisition module receives this shipping order and acquires the shipping orders for that day.

[0031] The shipping order storage module stores the acquired shipping order (step S11). The shipping order storage module stores the acquired shipping order in association with the identifier of this shipping order (name, ID, management number, serial number, etc.).

[0032] This completes the shipping order acquisition process. The shipping order acquisition process is a process that is performed whenever a shipping order is updated, at predetermined intervals, or whenever a shipping order is completed, etc. The computer 10 executes the process described below using the shipping order acquired by the above-described shipping order acquisition process. The computer 10 may be configured to execute the process described below without storing the shipping order in the shipping order acquisition process. In this case, the acquired shipping order may be used as is in the process described below.

[0033] [Work plan acquisition process executed by computer 10] The work plan acquisition process executed by the computer 10 will be described with reference to Fig. 4. The figure is a flowchart of the work plan acquisition process executed by the computer 10. The work plan acquisition process is a detailed flow relating to the work plan acquisition process among the above-mentioned processes (step S0) for acquiring a shipping order and a work plan.

[0034] The work plan acquisition module acquires the work plan for the day (step S20). As described above, the work plan includes the number of warehouse workers to be worked in each process in the warehouse, the work content (for example, work time, work volume), the work process, etc. The RCS 30 extracts the work plan for the day from the work plans created in advance and transmits it to the computer 10. The work plan acquisition module receives this work plan and acquires the work plan for the day. Note that the source of the work plan is not limited to the RCS 30.

[0035] The work plan storage module stores the acquired work plan (step S21). The work plan storage module stores the acquired work plan in association with the identifier (name, ID, management number, serial number, etc.) of this work plan.

[0036] This completes the work plan acquisition process. The work plan acquisition process is a process that is performed whenever the work plan is updated, at predetermined intervals, a predetermined time before the work start time, after the work end time, etc. The computer 10 executes the process described below using the work plan acquired by the above-mentioned work plan acquisition process. Note that the computer 10 may be configured to execute the process described below without storing the work plan in the work plan acquisition process, in which case the acquired work plan may be used as is in the process described below.

[0037] [Shortage notification process executed by computer 10] The personnel shortage notification process executed by the computer 10 will be described with reference to Fig. 5. Fig. 5 is a flowchart of the personnel shortage notification process executed by the computer 10.

[0038] The shift data acquisition module acquires the shift data for the current day (step S30). The shift management system 50 extracts the shift data for the current day and transmits it to the computer 10. The shift data acquisition module receives this shift data and acquires the shift data for the day.

[0039] The staff shortage detection module detects staff shortages in the acquired shift data for the day (step S31). The shortage detection module analyzes the acquired shift data for the day, and among the warehouse workers for that day, if there are any changes such as absence, lateness, or early departure, it detects warehouse workers who are unable to perform some or all of the warehouse work assigned to them for that day as shortage personnel, and detects other warehouse workers who are on duty as workers who are able to perform the scheduled work.

[0040] The manpower shortage determination module determines whether or not there is a manpower shortage based on the detection result (step S32). If the personnel shortage determination module determines that there is no personnel shortage (step S32 NO), the computer 10 ends the personnel shortage notification process.

[0041] On the other hand, if the manpower shortage detection module determines that a manpower shortage exists in the detection result (YES in step S32), the manpower shortage assignment work specification module specifies the work content assigned to the detected manpower shortage (step S33). The understaffed work assignment specification module refers to the work plan acquired by the above-mentioned work plan acquisition process and specifies the work content assigned to the detected understaffed work. Note that the understaffed work assignment specification module may also refer to the acquired shift data and specify the work content assigned to the detected understaffed work.

[0042] The staff shortage notification module notifies the staff shortage (step S34). The personnel shortage notification module transmits the number of personnel shortages, the work content and period of work assigned to the personnel shortages for the day to the manager terminal 40. The period is one day if the personnel shortage is due to absence, and is morning, afternoon, a specified time period, etc. if the personnel shortage is due to lateness or early departure. The manager terminal 40 receives the number of personnel shortages, the work contents and periods assigned to the personnel shortages for the day, and displays them on its own display unit. The manpower shortage notification module notifies the manager terminal 40 of the manpower shortage by displaying the number of manpower shortages, the work contents and duration for the day assigned to the manpower shortages.

[0043] This completes the personnel shortage notification process.

[0044] [Alert notification process executed by computer 10] The alert notification process executed by the computer 10 will be described with reference to Fig. 6. This figure is a diagram showing a flowchart of the alert notification process executed by the computer 10. The alert notification process is details of the process of acquiring work process completion information (step S1), the process of calculating the progress of the work process (step S2), and the alert notification process of issuing an alert according to the progress of the work process (step S3), and is a process that is performed simultaneously with or after the work plan acquisition process described above.

[0045] The completion information acquisition module acquires completion information for each work process in the entire warehouse (step S40). The completion information includes the content of the completed work process, the time of completion, the work time, etc. The completion information acquisition module acquires completion information for each completed work process in the entire warehouse at the time the alert notification process is executed, that is, in real time. The RCS 30 transmits this completion information to the computer 10 . The completion information acquisition module receives this completion information and acquires the completion information of each work process in the entire warehouse. The completion information acquired by the completion information acquisition module may be completion information for each process that has already been completed and the process currently being worked on at the time of acquisition, or it may be completion information for only the process currently being worked on at the time of acquisition.

[0046] The progress calculation module compares the acquired completion information with the work process in the work plan created in advance, and calculates the progress of the work process (step S41). As mentioned above, progress refers to the degree of impact on the work plan (progress rate against the work plan, amount of work completed, and amount of work required according to the work plan), the difference in profit due to progress (impact on income and expenditure), and the amount of work required to recover progress (required man-hours). The progress calculation module calculates the progress rate against the plan, the amount of work, the estimated time to complete, the margin rate, the excess man-hours, and the gross profit rate (see FIG. 7). The progress calculation module calculates the progress of the work process based on the completion information and the work plan for the day acquired by the above-mentioned work plan acquisition process. The progress calculation module compares the completed work process in the process in the completion information with the work process for this process in the work plan for that time, and calculates the progress of this process. The progress calculation module may compare the completion information of each process that has already been completed and the process currently being worked on at the time of acquisition with the work processes in the work plan created in advance, or may compare the completion information of the work process of the process currently being worked on at the time of acquisition with the work processes in the work plan created in advance.

[0047] The progress of the work process calculated by the progress calculation module will be described with reference to Fig. 7. The figure is a diagram showing an example of the calculation result calculated by the progress calculation module. The figure shows an example of the calculation result of the progress in picking calculated by the progress calculation module. The progress calculation module displays the calculation results 60 in the form of a progress table 61, which summarizes the numbers and details of the calculated progress as a table, and a progress graph 62, which summarizes the numbers and details of the calculated progress as a graph. In the progress table 61, the impact on the work plan is shown as follows: work progress rate against plan 73%, work volume 560 / 768, estimated completion time 20:47 (+3:47), and slack rate -32.1%. The difference in profit due to the progress is shown as gross profit rate -8.1%, and the man-hours required to recover the progress are shown as excess man-hours of 11 man-hours. The progress graph 62 summarizes these contents in the form of a graph.

[0048] Such delays in progress may be caused by a shortage of personnel detected in the personnel shortage notification process described above, or by the occurrence of unexpected trouble.

[0049] Returning to FIG. 6, the alert notification process will be further described. The progress determination module determines whether the progress of the work process is equal to or less than a threshold based on the calculation result (step S42). The threshold is set in advance, and is, for example, a percentage or a number set for the progress rate, remaining work amount, start time, or expected completion time. The progress determination module determines whether or not all or some of these are below a set threshold. If the progress determination module determines that the calculated progress is greater than the threshold value (NO in step S42), the computer 10 ends the alert notification process.

[0050] On the other hand, if the progress determination module determines that the calculated progress is equal to or less than the threshold value (YES in step S42), the alert creation module creates an alert (step S43). The alert creation module creates an alert that summarizes the progress status and received orders, etc., along with a floor map that displays the location of a work process where the calculated progress status is below the threshold (see Figure 8). The alert creation module displays this location on the floor map by, for example, highlighting, enclosing it, filling it in, or adding an icon. The alert creation module also creates tables and other visualizations of the progress status and received orders. In addition to these, the alert creation module also creates visualizations using graphs and other visualizations of the progress of the entire work, the processing capacity for the entire work, and personnel allocation.

[0051] The alerts created by the alert creation module will be described with reference to Fig. 8. This figure is a diagram showing a schematic example of an alert created by the alert creation module. In the alert 70, a floor map 71, progress status 72, and received orders 73 are shown. On the floor map 71, the location of a work process where a delay in progress (progress below a threshold) has occurred is indicated by an encircling line 74. Also shown near the floor map 71 are a progress status 72 that visualizes the calculated progress status and the processes in which delays have occurred as a table, and a received order 73 that visualizes the acquired received orders as a table. The layout and display modes (display mode of locations where delays in progress have occurred, display mode of floor maps, display mode of progress status, display mode of received orders) can be changed as appropriate. The alert 70 may also include some of these, such as only the progress status, or only the floor map and the progress status. In addition to these, the alert 70 may also include visualizations of the progress of the entire work, the processing capacity for the entire work, personnel allocation, etc., using graphs or the like.

[0052] Returning to FIG. 6, the alert notification process will be further described. The alert notification module notifies the created alert (step S44). The alert notification module transmits the created alert to the administrator terminal 40. The administrator terminal 40 receives this alert and displays it on its own display unit. The administrator terminal 40 displays the alert 70 shown in Fig. 8 on its own display unit. The alert notification module notifies the created alert by displaying the created alert on the administrator terminal 40. Upon receiving an input in response to the displayed alert, the administrator terminal 40 transitions to a screen displaying the calculation result 60 shown in FIG. 7 above. By viewing this alert 70, the administrator can understand that a delay has occurred in progress, the location of the delay, the progress status, and the like.

[0053] This completes the alert notification process.

[0054] [Recovery plan creation process executed by computer 10] The recovery plan creation process executed by the computer 10 will be described with reference to Fig. 9. The same figure is a diagram showing a flowchart of the recovery plan creation process executed by the computer 10. The recovery plan creation process is a detailed version of the recovery plan creation process (step S4) described above, and is a process that is performed each time the alert notification process described above is executed and an alert is notified.

[0055] The change acceptance module accepts changes to the workers and / or work content (step S50). The manager terminal 40 accepts input of changes to the workers and / or work content from the manager who viewed the alert. Based on the progress status in the alert notified by the above-mentioned alert notification process, the manager terminal 40 accepts input of changes to the allocation of workers and / or changes to the work content in order to correct the delay in this progress status. In addition, changes to work content may be necessary not only when an alert occurs, but also when there is a discrepancy between the workforce plan and work plan drawn up the day before and the actual shipping order. An example of when such a change in work plan is necessary is when the actual shipping orders for that day differ from the personnel plan and work plan that were created when the shipping orders for the next day were predicted the day before. Specifically, if there are significantly more shipping orders than predicted, it is necessary to cancel the work content for the next day's shipping and change it to the work content for that day's shipping, or to adjust the workforce (e.g., by having workers work overtime). Also, if there are more shipping orders that require manual work than predicted, it is necessary to reduce the number of workers working on automated tasks and increase the number of workers working on manual tasks. Also, if there are more shipping orders with faster cut times than predicted, it is necessary to concentrate workforce from shipping orders with slower cut times to shipping orders with shorter cut times so that the work can be completed quickly. The system also accepts input for changes in worker allocation and / or work content to resolve these issues. The changes that can be input are, for example, as follows: That is, tasks that are behind schedule are reassigned to other workers; tasks that divide a day into morning and afternoon, maintaining the original work assignments for the morning except for the delays, but reassigning the work that is behind schedule in the afternoon; tasks that were originally assigned to multiple people are extracted for which there are no or few problems even if the number of people is reduced, and workers are reassigned from there to the tasks that are behind schedule; tasks that can be performed the following day or later are extracted and reassigned to the following day or later, and tasks that can be performed by the current workers are reorganized and reassigned. In addition to these, if there are significantly more shipping orders than predicted, the work for the next day's shipments will be canceled and changed to work for that day's shipments, the number of workers for automated work will be reduced and the number of workers for manual work will be increased, if there are more shipping orders that must be done manually than predicted, the number of workers for automated work will be reduced and the number of workers for manual work will be increased, and if there are more shipping orders with faster cut times than predicted, the number of workers will be concentrated on these shipping orders instead of the shipping orders with slower cut times so that the work can be completed sooner. The administrator terminal 40 may be a type that accepts input of such change plans one at a time, or may be a type that allows input of multiple plans, or may be a type that allows input of multiple plans together with their priorities.

[0056] The changes accepted by the change acceptance module will be described below. When an alert is issued for picking, the manager terminal 40 accepts an input to change a predetermined number of packing workers (for example, one person) to picking (see FIG. 10). The manager terminal 40 also accepts an input to change a predetermined number of distribution processing and packing workers (for example, one person each) to picking in the afternoon (see FIG. 10). The manager terminal 40 also accepts an input to reduce the workload for shipments from the next day onwards (see FIG. 11). When the computer 10 issues an alert for any one or a combination of multiple processes, the manager terminal 40 similarly accepts changes to the allocation of workers and changes to the work content from processes for which no alert has been issued.

[0057] The UI (User Interface) when the manager terminal 40 accepts input for changes to workers will be described with reference to Fig. 10. This figure is a diagram that schematically shows an example of a change input UI that is displayed when the manager terminal 40 accepts input for changes to workers. The administrator terminal 40 displays the change input UI 80 on its own display unit and accepts input from the administrator. The manager terminal 40 accepts input of the identifier of the worker to whom the worker is to be assigned in the worker input field 81. Here, the manager terminal 40 accepts input to the icon 84, and accepts the selection input of the worker using a pull-down menu. The manager terminal 40 accepts input of the process to which the worker is to be assigned in the process input field 82. Here, the manager terminal 40 accepts input to the icon 84, and accepts the selection input of the process via a pull-down menu. The manager terminal 40 accepts input of the period for which the worker is assigned in the time input field 83. Here, the manager terminal 40 accepts input to the icon 84, and accepts the selection and input of the start time and end time of the period using a pull-down menu. Note that this UI for inputting changes is merely an example, and the display contents, display order, input contents, etc. are not limited to the UI shown in Fig. 10. For example, it does not have to be a pull-down menu using icons 84, and other display contents, display order, input contents, etc. are also possible.

[0058] The UI when the administrator terminal 40 accepts input for changing the work content will be described with reference to Fig. 11. This figure is a diagram that schematically shows an example of a change input UI that is displayed when the administrator terminal 40 accepts input for changing the work content. The administrator terminal 40 displays the change input UI 86 on its own display unit and accepts input from the administrator. This change input UI 86 is based on the created shipping order. The manager terminal 40 accepts input for shipping orders for the next day and thereafter that will reduce the amount of work. Specifically, the manager accepts input for the shipping order to be reduced by accepting selection input for the shipping order desired by the manager from among the shipping orders displayed in the change input UI 86. The manager terminal 40 indicates that the input has been accepted by adding a check mark to the box in the date field 87 of the shipping order for which input has been accepted in the change input UI 86. Note that this UI for inputting changes is merely an example, and the display content, display order, input content, etc. are not limited to the UI shown in Fig. 11. For example, check marks do not need to be added, and other display content, display order, input content, etc. are also possible.

[0059] Returning to FIG. 9, the continuation of the processing of step S50 in the recovery plan creation processing will be explained. The administrator terminal 40 transmits the inputted changes to the computer 10. The change acceptance module receives the change content and accepts the change of the workers and / or the work content. If the change reception module receives only one change from the administrator terminal 40, it performs the processing described below for only that one change. If the change reception module receives multiple changes, it performs the processing described below for each change. If the change reception module receives changes along with their priority, it performs the processing according to that priority. Furthermore, although the change acceptance module has been described as being configured to accept changes via the administrator terminal 40, the change acceptance module may also be configured to accept changes directly. For example, the change acceptance module may learn the correlation between the work content and the workers, and based on the learning results, accept changes to the workers and / or work content when an alert is issued. Furthermore, when an alert is issued, the change acceptance module may accept changes to the workers and / or work content based on preset workers and / or work content.

[0060] The recovery plan creation module creates a recovery plan for the operation plan based on the received changes (step S51). The recovery plan creation module creates a recovery plan that reflects the accepted changes in the work plan for the day from the time of selection onwards. That is, the recovery plan created by the recovery plan creation module reflects the accepted changes in the work personnel and / or work content in the work plan for the day from the time of selection onwards. If only one change is received, the recovery plan creation module creates one recovery plan based on this one change, and if multiple change contents are received, the recovery plan creation module creates multiple recovery plans based on each of the change contents. In the following explanation, the recovery plan creation module will be described as creating recovery plan 1, in which one distribution processing worker is changed to picking, recovery plan 2, in which one distribution processing worker and one packing worker are changed to picking in the afternoon, and recovery plan 3, in which the amount of work for shipments from the next day onwards is reduced. The number of recovery plans is not limited to the above, and may be greater or less than that, and is created as appropriate depending on the number of workers and / or work contents accepted. Furthermore, although the recovery plan creation module has been described as being configured to create a recovery plan, it may also be configured to acquire a recovery plan created by an administrator. For example, the administrator terminal 40 accepts input of a recovery plan created by an administrator, or the administrator terminal 40 creates a recovery plan based on the changes accepted as input, and sends this recovery plan to the computer 10. The computer 10 can also be configured to be considered to have created a recovery plan by receiving this recovery plan.

[0061] The recovery plan storage module stores the created recovery plan (step S52). The recovery plan storage module stores the created recovery plan in association with the identifier of this recovery plan (name, ID, management number, serial number, etc.). The recovery plan storage module stores recovery plan 1, recovery plan 2, and recovery plan 3.

[0062] This completes the recovery plan creation process. The computer 10 executes the processing described below using the recovery plan created by the recovery plan creation processing. The computer 10 can also be configured to execute the processing described below without storing a recovery plan in the recovery plan creation processing, in which case the created recovery plan can be used as is in the processing described below.

[0063] [Work plan determination process executed by computer 10] The work plan determination process executed by the computer 10 will be described with reference to Fig. 12. This figure is a flowchart of the work plan determination process executed by the computer 10. The work plan determination process is a detailed calculation process of the profit for the entire work for the day (step S5), and is a process that is performed after the recovery plan creation process described above.

[0064] The simulation module executes a simulation of the created recovery plan (step S60). The simulate module executes a simulation of the recovery plan created by the above-mentioned recovery plan creation process. The content of the simulation executed by the simulate module may be any content that simulates each process performed by workers in the created recovery plan. The simulate module simultaneously simulates recovery plan 1, recovery plan 2, and recovery plan 3. If only one recovery plan has been created, the simulation module simulates this one recovery plan, and if multiple recovery plans have been created, the simulation module simulates multiple recovery plans simultaneously.

[0065] The profit calculation module calculates the profit of the entire work for the day based on the recovery plan (step S61). The profit calculation module calculates sales, expenditures, and balance for each process in the recovery plan. Here, expenditures are synonymous with expenses, and balances are synonymous with profits, and balances are calculated by subtracting expenditures from sales. Here, sales for each process are the delivery costs paid by the shipper allocated to each process or allocated to each process in advance. Furthermore, expenditures are the labor costs of the workers assigned to each process. The profit calculation module calculates sales, expenses, and income / expenses for each process: receiving, warehousing, picking, distribution processing, packaging, and shipping. The profit calculation module calculates the sum of sales, the sum of expenses, and the sum of income / expenses for each of these processes. The profit calculation module divides the sum of income / expenses by the sum of sales and calculates the calculated value as a percentage as the profit rate. Based on these calculation results, the profit calculation module calculates the sales, expenses, income / expenses, and profit rate for the entire work for that day based on the recovery plan as the total income / expenses. The profit calculation module calculates the sales for all work on that day based on recovery plan 1 to be 420,000 yen, expenses to be 383,040 yen, income and expenditure to be 36,960 yen, and profit margin to be 8.8%; the sales for all work on that day based on recovery plan 2 to be 450,000 yen, expenses to be 390,600 yen, income and expenditure to be 59,400 yen, and profit margin to be 13.2%; and the sales for all work on that day based on recovery plan 3 to be 434,786 yen, expenses to be 382,354 yen, income and expenditure to be 52,432 yen, and profit margin to be 12.1%.The following processing will be explained assuming this. The figures for each item are calculated appropriately based on the shipping order, work plan, accepted work personnel and / or work content, etc.

[0066] The work efficiency calculation module calculates the work efficiency of the entire work for the day based on the recovery plan (step S62). Work efficiency is the total time required, cut time margin, margin rate, and excess man-hours. The work efficiency calculation module calculates the amount of work for each process: receiving, warehousing, picking, distribution processing, packaging, and shipping. The work efficiency calculation module calculates the total required time based on the time required in the simulation results (the time it would actually take to perform warehouse work according to this recovery plan). The cut time is the deadline set for each package to be shipped, and is the time required from the start time to the end time of the work. The work efficiency calculation module calculates the cut time slack based on the time obtained by subtracting the total required time from the cut time. The work efficiency calculation module also calculates the slack rate as the ratio of the cut time slack to the cut time. A positive value for the cut time slack means there is slack in the work time, and a negative value for the cut time slack means there is insufficient work time. The work efficiency calculation module calculates excess man-hours as the number of people required per unit time when the cut time slack is negative. In this embodiment, the work efficiency calculation module calculates the total required time for all work on that day based on recovery plan 1 to be 12 hours 7 minutes (12 hours 7 minutes), the cut time margin to be -4:07 (minus 4 hours 7 minutes), the margin rate to be -17.5%, and the excess man-hours to be 13 man-hours; the total required time for all work on that day based on recovery plan 2 to be 9 hours 14 minutes (9 hours 14 minutes), the cut time margin to be -1:14 (minus 1 hour 14 minutes), the margin rate to be -13.4%, and the excess man-hours to be 6 man-hours; and the total required time for all work on that day based on recovery plan 3 to be 7 hours 57 minutes (7 hours 57 minutes), the cut time margin to be 0:03 (0 hours 3 minutes), the margin rate to be 0.6%, and the excess man-hours to be 0 man-hours.The following processing will be explained. The figures for each item are calculated appropriately based on the shipping order, work plan, accepted work personnel and / or work content, etc.

[0067] The simulation result creation module creates the simulation result (step S63). The simulation result creation module creates a simulation result that summarizes the profits and work efficiency for each recovery plan calculated by the processing of steps S61 and S62 described above for each recovery plan. The simulation result creation module creates a simulation result that summarizes the identifier of each recovery plan, the changes in the number of workers and / or work content for this recovery plan, the calculated sales, expenses, income and expenditure, and profit margin for that day for this recovery plan (including the sales, expenses, and income and expenditure for each process), the calculated total required time for that day for this recovery plan, cut time slack time, slack rate, excess man-hours, and the simulated contents of each recovery plan such as overall progress (the amount of work in each process, the rate of work completion, etc.), processing capacity, and personnel allocation, visualized in graphs, tables, etc. (see FIG. 13). In Figure 13, the simulation result creation module creates a simulation result that compiles the name of each recovery plan, the change content, the work efficiency and profit margin for the entire work for that day in this recovery plan, and detailed icons 88 linked to other content. The simulation results created by the simulation result creation module are not limited to those shown in Fig. 13, and may include other content, or may include any one or a combination of these. Also, instead of displaying the results as detailed icons 88, the other content itself may be displayed.

[0068] Returning to FIG. 12, the rest of the work plan determination process will be described. The sorting module sorts the recovery plans in the created simulation results into a predetermined order (step S64). The predetermined order is an order based on profit and / or work efficiency. Specifically, in the case of profit, it is an order based on the overall profit (profit rate) for the day's work. In the case of work efficiency, it is an order that optimizes work efficiency, and is one or a combination of the following: an optimal total required time order, an optimal cut time slack order, an optimal excess man-hour order, and an optimal slack rate order. In addition, if multiple changes are accepted by the administrator along with priorities, the items are rearranged according to the priorities. An example of the sorting performed by the sorting module will now be described. The sorting module sorts the order of recovery plans in the created simulation results in order of the largest profit for the entire work for that day, based on the profit calculated for each recovery plan (see Figure 14). In Figure 14, the sorting module sorts the order of recovery plans in the simulation results shown in Figure 13 in order of the largest profit rate: recovery plan 2, recovery plan 3, and recovery plan 1. Furthermore, the sorting module sorts the order of the recovery plans in the created simulation results into the order of the optimal cutoff time margins based on the cutoff time margins calculated for each recovery plan (see Figure 15). In Figure 15, the sorting module sorts the order of the recovery plans in the simulation results shown in Figure 13 into the order of the optimal cutoff time margins for recovery plan 3, recovery plan 2, and recovery plan 1. The sorting module can also sort the order of recovery plans in the created simulation results to the order of the contents of optimal work efficiency based on the contents of work efficiency calculated in each recovery plan, for other work efficiency contents as well. The sorting module can be configured not only to sort the order of recovery plans in the created simulation results based on only one content, but also to sort the order of recovery plans based on a combination of multiple contents. For example, the sorting module can be configured to sort the order of recovery plans in order of greatest profit and optimal cutoff time margin. When sorting the order of recovery plans based on multiple contents like this, it is sufficient to set priorities, thresholds, etc. for each content and sort based on the priorities, thresholds, etc.

[0069] Returning to FIG. 12, the rest of the work plan determination process will be described. The recovery plan output module outputs the simulated recovery plan (step S65). The recovery plan output module transmits the simulation results, which have been rearranged in the above-mentioned predetermined order (such as the order of greatest profit for the entire work for that day, the order of optimal work efficiency for the entire work for that day, etc.), to the manager terminal 40. In this embodiment, the recovery plan output module will be described as transmitting the results, which have been rearranged in the order of cut time margin time shown in FIG. The administrator terminal 40 receives the simulation results and displays them on its own display unit or the like (see FIG. 16). The recovery plan output module outputs the simulated recovery plan by displaying the simulation results on the administrator terminal 40.

[0070] The simulation results displayed on the manager terminal 40 will be described with reference to Fig. 16. The figure is a diagram showing an example of the simulation results displayed on the manager terminal 40. The administrator terminal 40 displays the simulation result 90 on its own display unit based on the received simulation result. The administrator terminal 40 accepts an input such as a tap operation on the detail icon 91, and transitions to a screen showing the simulation content associated with the detail icon 91, such as graphs of overall progress, processing capacity, personnel allocation, etc., overall progress, progress of each process, overall balance, balance of each process, etc. (see FIGS. 17 and 18). FIG. 17 is a diagram illustrating an example of a screen displaying the simulation results 90. In FIG. 17, the administrator terminal 40 displays, as simulation results 90, the recovery plan identifier, changes to the workforce and / or work content in the recovery plan, the calculated profit margin for the day in the recovery plan, the calculated total required time for the day in the recovery plan, cut time margin, margin rate, excess man-hours, overall progress (e.g., the amount of work in each process, the work completion rate), processing capacity, and personnel allocation, all visualized in graphs, tables, and the like. Furthermore, the administrator terminal 40 changes the content displayed in the simulation results 90 to the content shown in FIG. 18 by accepting a predetermined input. Furthermore, the administrator terminal 40 changes the content displayed in the simulation results 90 to the content shown in FIG. 16 by accepting a predetermined input. FIG. 18 is a diagram illustrating an example of a screen displaying the simulation results 90. In FIG. 18, the administrator terminal 40 displays, as simulation results 90, the recovery plan identifier, changes to the workforce and / or work content in the recovery plan, the calculated sales, expenses, income / expenses, and profit margins for the day in the recovery plan (including the sales, expenses, and income / expenses for each process), the calculated total required time for the day in the recovery plan, cut time margin, margin rate, excess man-hours, and the simulated contents of each recovery plan, such as overall progress, processing capacity, and personnel allocation, all visualized in graphs and tables. Furthermore, the administrator terminal 40 changes the content displayed in the simulation results 90 to the content shown in FIG. 17 by accepting a predetermined input. Furthermore, the administrator terminal 40 changes the content displayed in the simulation results 90 to the content shown in FIG. 16 by accepting a predetermined input.

[0071] In the above explanation, the computer 10 is configured to output all simulated recovery plans, but it may also be configured to output a recovery plan in which all work processes in the warehouse for that day are completed within the same day. Specifically, the recovery plan output module extracts from the simulation results only those recovery plans for which the calculated cut time margin is 0 minutes or more, and outputs the simulation results of only the extracted recovery plans to the manager terminal 40. In the case of this embodiment, the recovery plan output module extracts only recovery plan 3 from the simulation results, and outputs the simulation results of only this recovery plan 3 to the manager terminal 40 (see FIG. 19).

[0072] Returning to FIG. 12, the rest of the work plan determination process will be described. The selection receiving module receives a selection for the output recovery plan (step S66). The administrator terminal 40 accepts a selection input for a recovery plan desired by the administrator from among the simulation results displayed on the administrator terminal 40, and sends the accepted recovery plan to the computer 10. The administrator terminal 40 accepts a selection input for a recovery plan in the simulation results 90 shown in FIG. 16, and sends the accepted recovery plan to the computer 10. The selection receiving module receives this recovery plan and thereby receives a selection for the output recovery plan.

[0073] The work plan determination module determines the received recovery plan as the work plan for the day after the selection (step S67). The work plan determination module changes the original work plan for the day acquired in the above-mentioned work plan acquisition process to the workers and work content in the accepted recovery plan, and determines it as the work plan for the day from the time of selection onwards.

[0074] The above is the work plan determination process. The computer 10 may notify the warehouse workers or managers of the determined work plan, thereby informing them of the new work plan, or may execute processing related to adjusting the operation of equipment related to warehouse work based on the determined work plan.

[0075] [Processing for notifying advancement of work availability executed by computer 10] The process of notifying that work can be moved forward, which is executed by the computer 10, will be described with reference to Fig. 20. The figure shows a flowchart of the process of notifying that work can be moved forward, which is executed by the computer 10. The process of notifying that work can be moved forward is related to the work plan determination process described above, and is performed after the process of step S66 described above.

[0076] The early termination determination module determines whether the selected recovery plan is a recovery plan in which the work end time for the day is completed earlier than the normally set work end time (step S70). The normally set work end time is the work end time in the original work plan or a work end time that has been set in advance. The early termination judgment module judges whether the cut time margin in the selected recovery plan is a positive time. At this time, if the cut time margin is positive, the early termination judgment module does not need to consider the length of that time, but preferably judges whether the cut time margin is a positive amount of time that the specified work content in the shipping order and work plan for the next day and thereafter can be executed. If the early termination determination module determines that the selected recovery plan is not a recovery plan in which the work end time for that day is completed earlier than the normally set work end time (step S70 NO), the computer 10 terminates the advance work possibility notification process.

[0077] On the other hand, if the early termination judgment module determines that the selected recovery plan is a recovery plan in which the end time of the work for that day will be completed earlier than the normally set end time of the work (step S70 YES), the advancement possibility notification module notifies that the work content for the following day and beyond can be carried forward (step S71). The advancement possibility notification module creates a notification that the work contents for the next day and thereafter can be carried forward, and transmits this notification to the manager terminal 40. The administrator terminal 40 receives this notification and displays it on its own display unit. The advancement possibility notification module notifies the administrator that the work contents from the next day onwards can be carried forward by displaying this notification on the administrator terminal 40. By viewing this notification, the manager can understand that the work for the following day and beyond can be carried forward, which may encourage the manager to make further changes to the work plan for the day after the selection.

[0078] In the above explanation, the computer 10 determines whether the selected recovery plan will be completed earlier than the work end time. However, the computer 10 may be configured to determine whether the selected recovery plan will be completed earlier than the work end time for all simulated recovery plans, not just the selected recovery plan. In this case, the early completion determination module determines whether the cut time margin for each simulated recovery plan is positive. The advancement possibility notification module can be configured to include the identifier of a positive recovery plan in a notification that the work content for the next day or later can be advanced, and output this to the administrator terminal 40.

[0079] This completes the process for notifying that work can be advanced.

[0080] Although the above-described processes are described as separate processes, the computer 10 can be configured to execute a combination of some or all of the above-described processes. Also, the computer 10 can be configured to execute each process at a timing other than the timing described.

[0081] The above-described means and functions are realized by a computer (including a CPU, an information processing device, and various terminals) reading and executing a predetermined program. The program may be provided, for example, from a computer via a network (Software as a Service (SaaS)) or as a cloud service. The program may also be provided in a form recorded on a computer-readable recording medium. In this case, the computer reads the program from the recording medium, transfers it to an internal or external recording device, records it, and executes it. The program may also be pre-recorded on a recording device (recording medium) and provided to the computer from the recording device via a communication line.

[0082] Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. Furthermore, the effects described in the embodiments of the present invention are merely a list of the most preferable effects resulting from the present invention, and the effects of the present invention are not limited to those described in the embodiments of the present invention.

[0083] (1) A warehouse operation management system that manages the workload based on the number of workers and shipping orders in each process of warehouse operations (e.g., receiving, warehousing, picking, distribution processing, packaging, shipping), an acquisition unit (e.g., acquisition unit 11, completion information acquisition module) that acquires completion information of each work process in the entire warehouse; a calculation unit (e.g., calculation unit 13, progress calculation module) that compares the acquired completion information with a work process in a work plan created in advance and calculates a progress status of the work process; an alert notification unit (e.g., alert notification unit 12, alert notification module) that issues an alert when the progress of the work process is equal to or less than a threshold based on the calculation result; A creation unit (e.g., creation unit 14, recovery plan creation module) that creates a recovery plan in which the workers and / or work content are changed each time the alert is notified; a simulator (e.g., simulator 15, simulation module, profit calculation module) that simulates the created recovery plan and calculates the profit of the entire work for that day based on the recovery plan; A warehouse operation management system comprising:

[0084] According to the invention of (1), it is possible to quickly correct delays in progress due to problems during warehouse work. Also, if the manpower plan and work plan predicted the previous day differ from the current shipping order, it is possible to recommend how to change the predicted manpower plan and work plan to meet the shipping order on time, and to perform a balance sheet simulation in that case.

[0085] (2) the creation unit creates a plurality of the recovery plans, The simulator simulates the plurality of recovery plans and calculates the profit of the entire work for that day based on each recovery plan. The warehouse operation management system described in (1).

[0086] According to the invention of (2), it is possible to simulate multiple recovery plans and grasp the profit of the entire work for the day based on each recovery plan.

[0087] (3) an output unit (e.g., a recovery plan output module) that simultaneously outputs the simulated recovery plans; a selection receiving unit (for example, a selection receiving module) that receives a selection from the plurality of output recovery plans; A determination unit (for example, an operation plan determination module) that determines the selected recovery plan as the operation plan for the day after the selection; The warehouse operation management system according to (2) further comprises:

[0088] According to the invention of (3), it is possible to use the recovery plan decided by the manager or the like from among the created recovery plans as the work plan.

[0089] (4) The output unit outputs the simulated recovery plans in descending order of the overall profit of the work for that day. (3) The warehouse operation management system described in (3).

[0090] According to the invention of (4), it becomes easy for managers and the like to grasp recovery plans that are effective in ensuring profits.

[0091] (5) The output unit outputs the simulated recovery plans in order of optimal work efficiency for the entire work for that day. (3) The warehouse operation management system described in (3).

[0092] According to the invention of (5), it becomes easy for managers to grasp recovery plans that are effective in terms of work efficiency. Recovery plans that are efficient in work efficiency can prevent work delays and discrepancies in progress.

[0093] (6) an advancement possibility notification unit (for example, an advancement possibility notification module) that notifies the user that the work content for the next day and thereafter can be advanced if the selected recovery plan is a recovery plan in which the work end time for the day is completed earlier than the normally set work end time; The warehouse operation management system according to (3) further comprises:

[0094] According to the invention of (6), it becomes possible to carry out work for the following day ahead of schedule.

[0095] (7) A warehouse operation management method executed by a computer that manages the amount of work based on the number of workers and shipping orders in each process of warehouse operations, comprising: A step of acquiring completion information of each work process in the entire warehouse (for example, step S40); A step (e.g., step S41) of comparing the acquired completion information with a work process in a work plan created in advance and calculating a progress of the work process; a step of issuing an alert when the progress of the work process is equal to or less than a threshold based on the calculation result (e.g., step S44); A step of creating a recovery plan in which the workers and / or work content are changed each time the alert is notified (for example, step S51); A step of simulating the created recovery plan and calculating the profit of the entire work for that day based on the recovery plan (for example, step S60, step S61); A warehouse operation management method comprising:

[0096] (8) A computer that manages the workload based on the number of workers and shipping orders in each process of warehouse operations, A step of acquiring completion information of each work process in the entire warehouse (e.g., step S40); A step of comparing the acquired completion information with the work process in a work plan created in advance and calculating the progress of the work process (e.g., step S41); a step of issuing an alert when the progress of the work process is equal to or less than a threshold based on the calculation result (e.g., step S44); A step of creating a recovery plan in which the workers and / or work content are changed each time the alert is notified (for example, step S51); A step of simulating the created recovery plan and calculating the profit of the entire work for that day based on the recovery plan (e.g., step S60, step S61); A computer-readable program for executing the program. [Explanation of symbols]

[0097] 1 Warehouse operation management system 9 Network 10. Computers 20 WMS 30 RCS 40 Administrator terminal 50 Shift Management System 60 Calculation results 61 Progress Table 62 Progress Graph 70 Alerts 71 Floor mats 72 Progress 73 Sales Order 74 Enclosure 80 Change input UI 81 Worker input field 82 Process input field 83 Time input field 84 icons 86 Change input UI 87 Date column 88 Details Icon 90 Simulated results 91 Details Icon

Claims

1. A warehouse operation management system that manages the amount of work based on the number of workers and shipping orders in each process of warehouse operations, an acquisition unit that acquires completion information of each work process in the entire warehouse; a calculation unit that compares the acquired completion information with a work process in a work plan for the day that has been created in advance, and calculates the progress of the work process; an alert notification unit that, when the progress of the work process is equal to or less than a threshold based on the calculation result, issues an alert that visually indicates the progress of the work process; a change receiving unit that receives changes to the number of workers and / or work content based on the notified alert so as to compensate for the work process whose progress is below the threshold; and a creation unit that creates a recovery plan by changing the number of workers and / or the work content of the original work plan for that day based on the received changes; a simulator that simulates the created recovery plan and calculates the profit of the entire work for that day based on the recovery plan; A warehouse operation management system comprising:

2. The change acceptance unit accepts a plurality of the change contents, The creation unit creates a plurality of the recovery plans based on each of the plurality of change contents, The simulator simulates the plurality of recovery plans and calculates the profit of the entire work for that day based on each recovery plan. The warehouse operation management system according to claim 1 .

3. an output unit that simultaneously outputs the plurality of simulated recovery plans; a selection receiving unit that receives a selection from the plurality of output recovery plans; a determination unit that determines the selected recovery plan as the operation plan for the day from the time of selection onward; The warehouse operation management system according to claim 2 , further comprising:

4. The output unit outputs the simulated recovery plans in descending order of overall profit for the day's work. The warehouse operation management system according to claim 3 .

5. The output unit outputs the simulated recovery plans in order of optimal work efficiency for the entire work for that day. The warehouse operation management system according to claim 3 .

6. an advancement possibility notification unit that notifies the user that work content from the next day onwards can be carried out ahead of schedule when the selected recovery plan is a recovery plan in which the work end time for the day is completed earlier than the normally set work end time; The warehouse operation management system according to claim 3 , further comprising:

7. A warehouse operation management method executed by a computer that manages the amount of work based on the number of workers and shipping orders in each process of warehouse operations, comprising: acquiring completion information of each work process in the entire warehouse; a step of comparing the acquired completion information with a work process in a work plan for the day that has been created in advance, and calculating a progress status of the work process; If the progress of the work process is equal to or less than a threshold based on the calculation result, notifying an alert visually indicating the progress of the work process; receiving, based on the notified alert, changes to the number of workers and / or the work content so as to compensate for the work process whose progress is below the threshold; creating a recovery plan in which the number of workers and / or work content are changed from the original work plan for that day based on the received changes; A step of simulating the created recovery plan and calculating the profit of the entire work for that day based on the recovery plan; A warehouse operation management method comprising:

8. A computer that manages the workload based on the number of workers and shipping orders in each process of warehouse operations. A step of acquiring completion information of each work process in the entire warehouse; a step of comparing the acquired completion information with a work process in a work plan for the day that has been created in advance, and calculating a progress status of the work process; a step of notifying an alert visually indicating the progress of the work process when the progress of the work process is equal to or less than a threshold based on the calculation result; receiving, based on the notified alert, changes to the number of workers and / or the work content so as to compensate for the work process whose progress is below the threshold; creating a recovery plan in which the work personnel and / or work content are changed from the original work plan for that day based on the received changes; a step of simulating the created recovery plan and calculating the profit of the entire work for that day based on the recovery plan; A computer-readable program for executing the program.

Images