Work planning system and work planning method

Abstract

The present invention relates to a work plan system including a processor and a storage section connected to the processor, wherein the storage section stores a plurality of delivery slips, work network information relating to processes of a work required for delivery, and resource information relating to a plurality of resources available for the work, the processor classifies the work corresponding to the plurality of delivery slips into a plurality of tasks based on predetermined conditions and the work network information, and generates a process plan including allocation of resources to the processes for each of the tasks based on the resource information, and outputs the generated process plan.

Description

[0001] Cross-references

[0002] This application claims priority to Japanese application No. 2019-156030, filed on August 28, 2019 (Reiwa 1), and incorporates it hereby by reference to its contents. Technical Field

[0003] This invention relates to a technique for planning operations in warehouses and the like. Background Technology

[0004] As an existing work planning system, for example, the system described in Patent Document 1 (Japanese Patent Application Publication No. 2002-154615) can be cited. This system accumulates delivery notes into a database and divides them according to delivery operation elements such as delivery items and packaging units (e.g., boxes or pieces). It then performs quantitative analysis of the time required for each operation, including picking, transportation, and secondary sorting, and determines the combination of groups with the shortest delivery production cycle, thereby deciding on the grouping of delivery notes.

[0005] Existing technical documents

[0006] Patent documents

[0007] Patent Document 1: Japanese Patent Application Publication No. 2002-154615 Summary of the Invention

[0008] The problem that the invention aims to solve

[0009] In the system described in Patent Document 1, the order in which the work begins for grouping delivery orders is not studied, and the order is determined by the work manager. Therefore, the following problems exist: when work is delayed or advanced, there is a risk of insufficient or excessive resources (such as workers, machines or equipment used for the work), making it impossible to achieve overall optimization including resource allocation.

[0010] Technical solutions for solving the problem

[0011] To address at least one of the aforementioned issues, the present invention provides a job planning system having a processor and a storage unit connected to the processor. The job planning system is characterized in that the storage unit stores multiple delivery orders, job network information related to the procedures of the jobs required for delivery, and resource information related to multiple resources that can be used for the jobs. The processor, based on predetermined conditions and the job network information, classifies the jobs corresponding to the multiple delivery orders into multiple tasks, and based on the resource information, generates a procedure plan for each task, including the allocation of the resources to the procedures, and outputs the generated procedure plan.

[0012] Invention Effects

[0013] According to one aspect of the present invention, the overall allocation of resources for operations corresponding to delivery orders can be optimized. Other issues, structures, and effects beyond those described above will be clarified through the following description of embodiments. Attached Figure Description

[0014] Figure 1 This is a block diagram illustrating the structure of a job planning system according to an embodiment of the present invention.

[0015] Figure 2 This is a block diagram illustrating the structure of a server device according to an embodiment of the present invention.

[0016] Figure 3 This is a block diagram illustrating the structure of a client device according to an embodiment of the present invention.

[0017] Figure 4 This is an explanatory diagram outlining the process executed by the job planning system according to an embodiment of the present invention.

[0018] Figure 5 This is an explanatory diagram of the delivery note information saved in the work plan system of an embodiment of the present invention.

[0019] Figure 6 This is an explanatory diagram of task generation in the job planning system of an embodiment of the present invention.

[0020] Figure 7 This is an explanatory diagram of the process plan generated by the work planning system of an embodiment of the present invention.

[0021] Figure 8 This is a timing diagram illustrating the detailed processing of the job planning system according to an embodiment of the present invention. Detailed Implementation

[0022] Hereinafter, embodiments of the work planning system of the present invention will be described with reference to the accompanying drawings.

[0023] Figure 1 This is a block diagram illustrating the structure of a job planning system according to an embodiment of the present invention.

[0024] The work planning system 100 of this embodiment is a system for planning work within a warehouse, consisting of a server device 101 and a client device 102. The server device 101 and the client device 102 are connected to a warehouse management system (WMS) 103 and multiple resource machines 105 via a network 104.

[0025] The warehouse management system 103 manages customer delivery orders and inventory of items within the warehouse. The warehouse management system 103 can be the same as a typical warehouse management system, therefore, detailed descriptions are omitted. The work planning system 100 receives delivery orders from the warehouse management system 103, generates work plans, and then sends work instructions to each resource machine 105. The structure of the server device 101 and client device 102 included in the work planning system 100 will be described later.

[0026] Each resource machine 105 corresponds to a resource used to perform operations within the warehouse. For example, when manual operations are performed in the warehouse, the operator performing the operation is the resource, and the corresponding resource machine 105 is, for example, a terminal device (handheld terminal or other operator terminal) used by the operator.

[0027] Alternatively, when material handling machines are used for warehouse operations, such machines are considered resources and are themselves equivalent to resource machines 105. Examples of material handling machines include conveyors that transport goods, automated guided vehicles (AGVs) that transport goods across shelves, and picking robots that pick goods from shelves.

[0028] Alternatively, the work area (workstation) and workbench where the work is performed can be treated as resources. In this case, if there are machines corresponding to the workstation and workbench (such as terminals that provide information to the operator), they can also be used as resource machines 105.

[0029] Network 104 can be of any type as long as it enables communication between the work planning system 100 and the warehouse management system 103, communication between the work planning system 100 and each resource machine 105, and communication between the server device 101 and the client device 102. Furthermore, these communications can be either wired or wireless, or a combination thereof.

[0030] Figure 2 This is a block diagram illustrating the structure of a server device 101 according to an embodiment of the present invention.

[0031] The server device 101 in this embodiment includes a processor 201, a memory 202, a storage medium 203, an input device 204, an output device 205, and a communication device 206.

[0032] The processor 201 controls the server device 101 according to the program stored in the memory 202.

[0033] The memory 202 is, for example, a semiconductor memory, storing programs executed by the processor 201, data referenced by the processor 201, and data obtained as a result of processing performed by the processor 201. At least a portion of the programs and data stored in the storage medium 203 can be copied to the memory 202 as needed, and the obtained data can be copied from the memory 202 to the storage medium 203 as needed.

[0034] exist Figure 2 In this example, memory 202 stores a resource control system (RCS) monitoring program 207 and a task generation program 208. These are programs used to implement resource monitoring and task generation, which will be described later. The processing performed according to these programs will be described later.

[0035] Storage medium 203 is a non-volatile storage medium such as flash memory or hard disk. The resource control system database (RCS DB) 209 stored on storage medium 203 will be described later.

[0036] Input device 204 receives input from the operator of the job planning system 100. Specifically, input device 204 may include, for example, a keyboard, buttons, or a pointing device.

[0037] The output device 205 outputs information to the operator of the job planning system 100. Specifically, the output device 205 may include, for example, an image display device. For example, at least a portion of the information generated as a result of processing according to the program stored in the memory 202 may be output via the output device 205.

[0038] The communication device 206 is a device for exchanging data with the warehouse management system 103, the client device 102, and the resource machine 105 via a wired or wireless network 104, and may include, for example, a LAN (Local Area Network) adapter. For example, at least a portion of the information stored in the storage medium 203 may be input via the communication device 206, and at least a portion of the information generated as a result of processing according to the program stored in the memory 202 may be output via the communication device 206.

[0039] Figure 3 This is a block diagram illustrating the structure of the client device 102 according to an embodiment of the present invention.

[0040] The client device 102 in this embodiment includes a processor 301, a memory 302, a storage medium 303, an input device 304, an output device 305, and a communication device 306.

[0041] The processor 301 controls the client device 102 according to the program stored in the memory 302.

[0042] The memory 302 is, for example, a semiconductor memory, storing programs executed by the processor 301, data referenced by the processor 301, and data obtained as a result of the processing performed by the processor 301. At least a portion of the programs and data stored in the storage medium 303 can be copied to the memory 302 as needed, and the obtained data can be copied from the memory 302 to the storage medium 303 as needed.

[0043] exist Figure 3 In this example, a process plan generation program 307 is stored in memory 302. This is a program used to generate the process plan, which will be described later. The processing performed according to this program will be described later.

[0044] Storage medium 303 is, for example, a non-volatile storage medium such as flash memory or a hard disk. Figure 3 In this example, storage medium 303 stores quantity / resource information 308 and process plan 309. Quantity / resource information 308 is the basis for generating the process plan based on the process plan generation program 307, and includes, for example, the quantity of materials to be worked on, the quantity of resources available in the warehouse, and information indicating the productivity of each resource. Process plan 309 is data generated by the process plan generation program 307. These contents will be described later.

[0045] Input device 304 accepts input from the operator of the work planning system 100. Specifically, input device 304 may include, for example, a keyboard, buttons, or a pointing device.

[0046] The output device 305 outputs information to the operator of the work planning system 100. Specifically, the output device 305 includes, for example, an image display device. For example, at least a portion of the information generated as a result of processing according to the program stored in the memory 302 can be output via the output device 305.

[0047] The communication device 306 is a device for exchanging data with the server device 101 and the resource machine 105 via a wired or wireless network 140, and may include, for example, a LAN (Local Area Network) adapter. For example, at least a portion of the information stored in the storage medium 303 may be input via the communication device 306, and at least a portion of the information generated as a result of processing according to the program stored in the memory 302 may be output via the communication device 306.

[0048] In addition, Figures 1-3The example described illustrates a work planning system 100 consisting of a server device 101 and a client device 102. However, the work planning system 100 could also consist of a server device 101 and multiple client devices 102, or it could be a computer system integrating a server device 101 and client devices 102. Furthermore, the warehouse management system 103 could also be composed of... Figure 2 or Figure 3 Implemented on the same computer system.

[0049] Figure 4 This is an explanatory diagram outlining the processes performed by the job planning system 100 according to an embodiment of the present invention.

[0050] Multiple delivery orders 403 from multiple customers 401 are entered into the work planning system 100 via the inventory management system or sales management system of WMS 103. Here, a delivery order 403 is a collection of orders for more than one type of goods to be delivered to a delivery destination at the same time. The work planning system 100 generates instruction information 404, which includes work instructions for shipping the goods corresponding to the delivery order 403. The order in which the instruction information is generated based on the delivery order 403 can be achieved by currently known methods, and therefore its detailed description is omitted.

[0051] The job planning system 100 generates tasks 405 based on the instruction information 404. As a result, task information 406 is generated. At this time, the task information database 410 and the job network information task 411 can be referenced. The task information database 410 and the job network information task 411 can, for example, be contained in the resource control system database 209 of the server device 101.

[0052] Task generation 405 and the generated task information 406 will be described later. Here, an example of classifying multiple delivery orders 403 into multiple tasks will be explained. As a result, the instruction information 404 corresponding to each delivery order 403 is classified into the task corresponding to each delivery order 403. The generated task information 406 is stored in the task information database 410.

[0053] Then, the work planning system 100 generates a process plan 407 based on the task information 406. As a result, a process plan 408 is generated. The process plan generation 407 and the generated process plan 408 will be described later.

[0054] The work planning system 100 transmits instruction data 409 based on the process plan 408 and instruction information 404. Specifically, according to the generated process plan 408, the work instructions contained in the instruction information 404 are transmitted to the resource machine 105 corresponding to the work at an appropriate time (e.g., when to perform the work according to the process plan 408).

[0055] Figure 5 This is an explanatory diagram of the delivery note information maintained by the work planning system 100 according to an embodiment of the present invention.

[0056] For example, the work planning system 100 can generate delivery note information 500 that adds necessary items to a delivery note 403 from customer 401, and store it in task information DB 410. Figure 5 The shipping order information 500 shown includes multiple shipping orders 501 (e.g., shipping order 1_501-1, shipping order 2_501-2, ..., shipping order n_501-n). In the case of any common description among these, they are collectively referred to as shipping order 501.

[0057] In addition, multiple shipping orders 501 are typically generated corresponding to one shipping order 403. For example, if goods shipped according to one shipping order 403 are divided into multiple shipping boxes, a shipping order 501 is generated for each shipping box. Furthermore, if multiple processes (e.g., picking, inspection, packaging, etc.) are performed from one shipping order 403 until the goods are shipped, a shipping order 501 is generated for each process.

[0058] exist Figure 5 In the example, for each shipping order 501, the items include: shipping packaging key 511-1, shipping order number 511-2, task number 511-3, operation type 511-4, production 511-5, previous activity 511-6, next activity 511-7, quantity shipped 511-8, number of boxes 511-9, shipping date 511-10, operation date 511-11, shipping destination information 511-12, carrier information 511-13, merchant departure time 511-14, emergency flag 511-15, shipping stop flag 511-16, box information 511-17, gift flag 511-18, operation start time of process planning generation department 511-19, operation end time of process planning generation department 511-20, and product information 511-21.

[0059] Shipping Packaging Key 511-1 is a key information for each shipping box number that is used to package the goods shipped according to Shipping Order 501. For example, a sticker with a barcode printed on it indicating the value (number) of Shipping Packaging Key 511-1 can be affixed to the shipping box to identify it.

[0060] Shipping order number 511-2 is the number that identifies shipping order 403 corresponding to shipping order 501. Since the order and the shipping (delivery) unit are the same (i.e., goods shipped according to a shipping order 403 are shipped to the same destination at the same time), shipping order number 511-2 can also be used as a delivery order number.

[0061] Furthermore, when goods shipped according to a single shipping order 403 are divided into multiple shipping boxes for packaging, a shipping order 501 is generated for each shipping box. The shipping packaging key 511-1 of each shipping order 501 has a different value, while the shipping order number 511-2 has the same value.

[0062] Task number 511-3 is an inherent number assigned to the task as a result of task generation 405. As described later, multiple delivery orders 501 are classified based on priority conditions and smoothing conditions, thereby generating the task.

[0063] Job type 511-4 indicates the type of job (e.g., process) corresponding to the delivery note 501. For example, if picking, inspection, and packaging processes are required to ship goods according to a delivery note 403, three delivery notes 501 corresponding to the delivery note 403 are generated, and each is recorded as a job type 511-4, indicating the values ​​for picking, inspection, and packaging. In this embodiment, job type is synonymous with process and activity described later.

[0064] Productivity 511-5 represents the material throughput capacity per unit time for each process. Here, material throughput can be any of the following: number of pieces, number of boxes, or number of orders. In this embodiment, boxes are used as the unit of quantity. Furthermore, actual productivity may vary depending on various conditions such as the type of goods. In processes where operations are performed manually, it may vary depending on the operator's skill level and fatigue level. While such precise productivity can be used, the productivity 511-5 in this embodiment is an average productivity uniformly applied to each process. This can be calculated, for example, based on past performance.

[0065] The previous activity 511-6 indicates the activity performed before the activity corresponding to this delivery note 501 (i.e., the activity represented by operation type 511-4 of this delivery note 501). Similarly, the next activity 511-7 indicates the next activity to be performed after the activity corresponding to this delivery note 501. For example, if the operation needs to be performed in the order of picking, inspection, and packaging, the operation type 511-4 of the delivery note 501 corresponding to inspection is "inspection," the previous activity 511-6 is "picking," and the next activity 511-7 is "packaging."

[0066] Furthermore, information indicating the sequence of such operations is contained in the operation network information task 411. The operation planning system 100 generates a delivery note 501 corresponding to the required operations based on the operation network information task 411, and records the values ​​of each previous activity 511-6 and next activity 511-7.

[0067] The shipment quantity 511-8 is the sum of the quantities in the product information 511-21 described later.

[0068] The box count information 511-9 pertains to the number of boxes containing the goods to be shipped according to shipping order 403. For example, if all the goods to be shipped according to a single shipping order 403 are packaged in one shipping box, the box count information 511-9 for the corresponding shipping order 501 will be "1 / 1". If the goods to be shipped according to a single shipping order 403 are packaged in two separate shipping boxes, the box count information 511-9 for the corresponding shipping orders 501 will be "1 / 2" and "2 / 2" respectively.

[0069] Shipping date 511-10 indicates the date on which the goods included in shipping order 501 are shipped.

[0070] Operation day 511-11 is the date on which the operation to ship the goods contained in this shipping order 501 is performed, which is the shipping date or the day before.

[0071] The shipping destination information 511-12 indicates the destination (delivery destination) of the goods delivered according to this shipping order 501.

[0072] Carrier information 511-13 indicates the merchant responsible for transporting the goods.

[0073] Merchant departure time 511-14 is the time when the carrier picks up the goods. That is, merchant departure time 511-14 can also be considered as the scheduled time when the goods are shipped from the warehouse.

[0074] The emergency label 511-15 indicates that the shipment was made earlier than other shipping invoices 501.

[0075] The Stop Shipment sign 511-16 indicates that although work instructions were issued to the warehouse, they were subsequently cancelled.

[0076] Box information 511-17 indicates the size of the shipping box. Specifically, box information 511-17 can also be information indicating the dimensions (length, width, height) of the shipping box, such as names or symbols indicating size like "large", "medium", or "small".

[0077] The gift mark 511-18 indicates information about special operations such as packaging of gifts, such as affixing gift labels or packaging of cosmetic boxes.

[0078] The start time 511-19 and end time 511-20 of the process planning generation department represent the start and end times of the process operation corresponding to the delivery note 501, calculated by process planning generation 407.

[0079] Product information 511-21 is information related to the products included in the shipping order 501 (i.e., the products packaged in the shipping box corresponding to the shipping order 501 that are to be shipped according to the shipping order 403). When multiple varieties (e.g., n varieties) of products are packaged in a single shipping box, product information 511-21 contains information related to each variety (e.g., the first to the nth). Specifically, product information 511-21 includes a product code identifying the variety of product, a product name indicating the name of the product, and the quantity. As described above, the total quantity of all varieties included in a shipping order 501 is recorded as the shipment quantity 511-8.

[0080] Figure 5 The shipping order 501 shown includes: information indicating that the merchant's departure time 511-14, the emergency flag 511-15, and the shipping stop flag 511-16 are priority conditions; and information indicating that the box information 511-17 and the gift flag 511-18 are smoothing conditions. This information is referenced in the task generation 405 described later. Additionally, as described later, the product information 511-21 is also referenced in task generation 405.

[0081] Figure 6 This is an explanatory diagram of the task generation 405 of the job planning system 100 according to an embodiment of the present invention.

[0082] In this embodiment, a task is a collection of multiple shipping orders 501. Warehouse resources are allocated according to the tasks. Task generation 405 is the process of classifying multiple shipping orders 501 into multiple tasks. At this time, multiple shipping orders 501 corresponding to the same shipping box (for example, three shipping orders 501 corresponding to the picking, inspection, and packaging of goods shipped through a certain shipping box) must be classified into the same task.

[0083] Additionally, in this embodiment, task groups can be set. A task group is a collection of one or more tasks consisting of delivery orders 501 that have the same priority conditions.

[0084] The work planning system 100 will process multiple delivery orders 501 (e.g., delivery orders 501 generated based on accumulated delivery orders 403 over a period) based on specified priority and smoothing conditions (both referred to in the original text). Figure 5 Categorize into tasks.

[0085] Specifically, the work planning system 100 categorizes delivery orders 501 with the same priority value into the same task group. Priority is a condition regarding the priority of the work processes corresponding to delivery orders 501. For example, delivery orders 501 that are earlier than the merchant's departure time 511-14 need to be executed as soon as possible. Furthermore, the work on delivery orders 501 with urgency flags 511-15 (indicating urgency) should be prioritized over the work on other delivery orders 501. Additionally, the work on delivery orders 501 with cancellation flags 511-16 (indicating cancellation of shipment) is preferably postponed, and the work on other delivery orders 501 is prioritized.

[0086] Furthermore, the work planning system 100 categorizes the delivery orders 501, which are classified into task groups, into multiple tasks within each task group. At this time, the work planning system 100 categorizes the delivery orders 501, which have the same smoothing conditions set, in a way that evenly distributes them among the multiple tasks within the task group.

[0087] The smoothing condition refers to the attributes in delivery note 501 that should be distributed among tasks; that is, attributes that are believed to improve overall operational efficiency through smoothing (balancing) across tasks. Figure 5 In the example, box information 511-17 and gift mark 511-18 meet the smoothing conditions.

[0088] For example, if an automatic sealing machine for large shipping boxes and an automatic sealing machine for small shipping boxes are installed in each assigned task location, and one task focuses on shipping orders 501 for large shipping boxes while the other focuses on shipping orders 501 for small shipping boxes, congestion may occur in the automatic sealing machines at each task location, reducing overall productivity. The same applies to gift packaging. Therefore, by evenly distributing shipping orders 501 with the same smoothing conditions across multiple tasks, an improvement in overall operational efficiency can be expected.

[0089] For example, when you want to categorize a shipping order 501 with a "large" box size into any task, you can compare the ratio of shipping orders 501 with a "large" box size among all shipping orders 501 of the object with a "large" box size among the shipping orders 501 already categorized into tasks, and select the task with the smaller latter ratio as the categorization destination. Thus, for example, if you calculate the ratio of shipping orders 501 with "large," "medium," and "small" box sizes for each task, you can distribute shipping orders 501 with each attribute (e.g., "large," "medium," and "small" box sizes) among tasks in a way that makes this ratio approximately equal across tasks. Gift wrapping can also be distributed using the same method.

[0090] exist Figure 6 In this example, the merchant's departure time 511-14 (i.e., the shipping time) is used as the priority condition, and the box information 511-17 is used as the smoothing condition. In this example, shipping orders 1, 2, 3, 5, 6, and 8 with a shipping time of 17:00 are classified into task group (Gr) 1. Shipping orders 4, 7, 9, and 10 with a shipping time of 18:00 are classified into task group 2. That is, the jobs corresponding to shipping orders with different priority conditions are not classified into the same task.

[0091] Shipping orders 1, 3, and 6, which correspond to large-sized shipping boxes, from the shipping orders classified into task group 1, are further subdivided into tasks 11, 12, and 13 within task group 1. On the other hand, shipping orders 2, 5, and 8, which correspond to small-sized shipping boxes, from the shipping orders classified into task group 1, are further subdivided into tasks 11, 12, and 13 within task group 1.

[0092] Shipping orders 7 and 9, which correspond to large-sized shipping boxes, from the shipping orders classified into task group 2, are further subdivided into tasks 21 and 22 within task group 2. On the other hand, shipping orders 4 and 10, which correspond to small-sized shipping boxes, from the shipping orders classified into task group 2, are similarly subdivided into tasks 21 and 22 within task group 1.

[0093] Therefore, each task includes one shipping order for large-sized shipping boxes and one for small-sized shipping boxes, preventing the concentration of workload on specific resources and thus reducing operational efficiency. Furthermore, by grouping shipping orders with similar priorities into the same task group, it is possible to generate a process plan for completing the shipping boxes at the appropriate time.

[0094] Furthermore, the work planning system 100 can also classify the delivery note 501 into tasks by referring to the product information 511-21 of the delivery note 501 to increase the deviation of the variety of products included in the task. For example, when it is desired to classify a delivery note 501 into any of multiple tasks, if more than one delivery note 501 has already been classified into each task, the repetition rate of the same product variety is calculated between the shipping boxes of the delivery note 501 to be classified and the shipping boxes of the delivery notes 501 already classified into each task, and the delivery note 501 to be classified is classified into the task with the highest repetition rate.

[0095] At this point, the duplication rate can also be calculated, for example, by (the number of products with duplicate varieties) / (the number of products in the shipping boxes of the category object + the number of products already classified into the task + 1).

[0096] As described above, resources such as operators, machines used for operations, and work sites are allocated according to tasks. Therefore, by reducing the number of times goods need to be transported to shelves for purposes such as picking when there are deviations in the variety of goods involved in the task, it is possible to expect an overall improvement in operational efficiency.

[0097] Figure 7 This is an explanatory diagram of the process plan generated by the work planning system 100 according to an embodiment of the present invention.

[0098] exist Figure 4 In the process planning generation 407, the work planning system 100 generates process plans for each task. Specifically, it can calculate the required time for each process based on the productivity 511-5 of the delivery note 501 included in each task, the specific quantity of goods according to the product information 511-21, and the amount of resources allocated to each task.

[0099] The work planning system 100 creates a work plan in a manner that ensures all work processes within a task group are completed before the shipment time of that task group. At this time, the work planning system 100 creates a work plan so that each work process starts in the order specified in the work network information task 411 and finishes after the required time calculated using the method described above. There are no restrictions on the specific method used for this, but for example, the required time can be repeatedly calculated while changing the allocated resource amounts until a work plan is obtained in which all work processes are completed before the shipment time.

[0100] Figure 7 This example uses a bar chart to represent the process plan for four tasks (tasks 1 through 4) belonging to the same task group. In this example, the departure time is 16:00. The numbers displayed on the bars represent the number of operators (i.e., resources) allocated to each process. Furthermore, within each task, picking, inspection, and packaging operations are performed sequentially.

[0101] In this example, picking for Task 1 begins at 12:00. At this time, 13 operators are assigned. Then, as picking progresses, 6 of the 13 operators begin inspecting the picked items. At this point, the number of picking operators decreases to 7. Afterward, as inspection progresses, 3 of the 7 picking operators and 2 of the 6 inspection operators begin packing the inspected items. Later, when all items have been picked, 2 of the 4 picking operators move to inspection, and the remaining 2 move to packing. If all items have been inspected, all 6 inspection operators move to packing. Finally, if all items have been packed, Task 1 is complete.

[0102] In this example, task 1 is always assigned to 13 operators. Therefore, it's possible to create a process plan where, for example, 13 people perform picking, and when all items are picked, 13 people begin inspection. However, in this case, a significant amount of space is required to temporarily store items that have been picked but not yet inspected. Therefore, by moving a portion of resources to begin the next process (e.g., inspection) when the previous process (e.g., picking) has progressed to a certain point, as described above, it's possible to save temporary storage space while allowing the operation to proceed. The parameter indicating when to start the next process after the previous process has progressed can be, for example, pre-included in the quantity / resource information 308, or assigned when creating the process plan.

[0103] exist Figure 7 In the example, after the operation of Task 1 begins, the operations of Task 2 and Task 3 begin. These operations are also planned in the same way as Task 1, with the next operation starting when the previous operation has progressed to a certain point.

[0104] Furthermore, in Figure 7 In the example, after all the operations in Task 1 are completed, the operator assigned to Task 1 begins the operations in Task 4. The operations in Task 4 are also planned in the same way as those in Task 1, starting the next operation when the previous operation has progressed to a certain stage. Furthermore, it is planned that when all the operations in Tasks 2 and 3 are completed, the operator assigned to each will move to Task 4 and begin the operations in Task 4.

[0105] exist Figure 7 In the example, the operations for tasks 2 and 3 start later than those for task 1. Therefore, the operators assigned to tasks 2 and 3 have shorter time constraints, resulting in lower costs. The work planning system 100 can also generate work plans by referring to resource unit price information (such as operator hourly wages) to minimize overall costs. Resource unit price information can also be included in the quantity / resource information 308.

[0106] The work planning system 100 will generate a work plan with the start and end times of each task and each process (respectively). Figure 7 The start and end times of each process are recorded in the corresponding delivery note 501, with the process planning generation department's start time 511-19 and end time 511-20.

[0107] Figure 8 This is a timing diagram illustrating the details of the processing performed by the job planning system 100 according to an embodiment of the present invention.

[0108] Figure 8The resource control system (RCS) monitoring unit 801 and task generation unit 802 shown are functional blocks implemented by the processor 201 of the server device 101 executing the resource control system monitoring program 207 and the task generation program 208 stored in the memory 202. Therefore, in the following description, the processing performed by these units is actually executed by the processor 201 based on the program stored in the memory 202.

[0109] Similarly, the process planning generation unit 803 is a function block implemented by the processor 301 of the client device 102 executing the process planning generation program 307 stored in the memory 302. Therefore, in the following description, the processing performed by the process planning generation unit 803 is actually executed by the processor 301 based on the program stored in the memory 302.

[0110] When at least one of a work instruction or work performance is input (step 811), the resource control system database 209 updates the stored data based on them (step 812). For example, when a delivery note 403 is input into the server device 101 from the warehouse management system 103, it is appended to the resource control system database 209. Additionally, when information such as which task and which process has been completed is input into the server device 101 from the warehouse management system 103 as work performance, the performance data in the resource control system database 209 is updated based on this input. Thus, it is possible to identify which unexecuted task corresponds to the delivery note 403 received at that time.

[0111] The resource control system monitoring unit 801 periodically monitors the resource control system database 209 (step 813) and obtains data (steps 814, 815). Then, the resource control system monitoring unit 801 instructs the task generation unit 802 to generate tasks (step 816). For example, the resource control system monitoring unit 801 may instruct task generation for tasks that are not yet classified into any task in the operations corresponding to the delivery note 403 received at that time, or it may instruct task generation for tasks that have not yet been executed.

[0112] The task generation unit 802 performs task generation according to instructions (step 817) and stores the generated task information in the resource control system database 209 (steps 818, 819). In addition, if new work performance has been obtained before, the performance data in the resource control system database 209 is updated accordingly (step 819).

[0113] The above task generation process is equivalent to Figure 4Task generation 405. At this time, for the delivery note 403 that becomes the object of task generation, the task generation unit 802 can either generate a new task or classify it as an already generated task. For example, if the task generation unit 802 performs task generation again for a newly obtained delivery note 403 after performing task generation once, it can classify the job corresponding to the newly obtained delivery note 403 as a newly generated task or as an already generated task. Through the above task generation, at least the following is determined. Figure 5 The task number is 511-3, and its value is registered in the delivery note 511 in the resource control system database 209.

[0114] On the other hand, the warehouse operation manager 804 activates the process planning generation unit 803 of the client device 102 (step 820). The process planning generation unit 803 obtains task information and performance information from the resource control system database 209 (steps 821, 822), and generates process plan generation input data based on the obtained information (step 823), and generates the process plan (step 824).

[0115] At this time, the process planning generation unit 803 can also generate process plans based on information obtained from the resource control system database 209, targeting tasks for which process plans have not yet been generated. Alternatively, the process planning generation unit 803 can also refer to performance information to generate process plans not only for tasks for which process plans have not been generated, but also for tasks for which process plans have been created but not executed. In the latter case, even if a deviation occurs between the generated process plan and the actual progress, by generating what is considered the best process plan at the time, targeting all remaining tasks, the deviation can be absorbed, and overall work efficiency can be improved.

[0116] In addition, the process planning generation unit 803 can monitor the deviation between the generated process plan and the actual progress. If, for example, the deviation exceeds a predetermined benchmark or the deviation meets predetermined conditions, a process plan is generated for tasks for which a process plan has been created but has not yet been executed.

[0117] The processing in step 824 is as follows Figure 4 The process plan generation 407 has been explained. Afterwards, the process plan generation unit 803 draws the generated process plan (step 825). For example, the process plan generation unit 803 can draw... Figure 7 The bar chart shown is output from the output device 305 of the client device 102. The manager 804 refers to such a bar chart to determine whether the generated process plan is appropriate, and if necessary, can change the process plan or change the condition instructions to re-execute.

[0118] Subsequently, the process planning generation unit 803 registers the timetable based on the generated process plan (step 826). As a result, the timetable data is sent and stored in the resource control system database 209 (steps 827, 828). Consequently, based on the values ​​of the generated process plan, the start time 511-19 and end time 511-20 of the process planning generation unit for the task that is the object of process plan generation are registered. Figure 5 Additionally, if new work performance data has already been obtained, the performance data in the resource control system database 209 is updated accordingly (step 828).

[0119] Afterwards, the process planning generation unit 803 can obtain the registration result from the resource control system database 209 according to the generated process plan as needed (step 829).

[0120] Subsequently, the resource control system monitoring unit 801 periodically monitors the resource control system database 209 (step 830) and obtains data (steps 831, 832). Then, the resource control system monitoring unit 801 sends instruction data for instructing operations to each resource machine 105 at an appropriate time determined based on the generated process plan (step 833).

[0121] Specifically, when the resource being controlled is an operator, the resource control system monitoring unit 801 can send data as instruction data, such as displaying text images containing work details. Alternatively, when the resource being controlled is a machine such as a picking robot, data for controlling it can be generated and sent as instruction data.

[0122] As a result, resources are controlled at the appropriate time, optimizing operations within the warehouse.

[0123] Furthermore, the present invention is not limited to the embodiments described above and may include various modifications. For example, the embodiments described above are examples provided for a better understanding of the present invention and are not limited to having all the described structures. Additionally, a portion of the structure of one embodiment can be replaced with the structure of another embodiment, and a structure of another embodiment can be added to the structure of an embodiment. Furthermore, for a portion of the structure of each embodiment, other structures can be added, deleted, or replaced.

[0124] Furthermore, the aforementioned structures, functions, processing units, and processing methods can be partially or entirely implemented in hardware, for example, through design using integrated circuits. Alternatively, the aforementioned structures and functions can be implemented in software by a processor interpreting and executing programs that implement each function. Information such as programs, tables, and files that implement these functions can be stored in storage devices such as non-volatile semiconductor memory, hard disk drives, and SSDs (Solid State Drives), or in computer-readable, non-temporary data storage media such as IC cards, SD cards, and DVDs.

[0125] In addition, the control lines and information lines shown are those deemed necessary in the description, but it is not required that all control lines and information lines be shown on the product. In fact, it can be assumed that almost all structures are interconnected.

Claims

1. A job scheduling system comprising a processor and a storage unit connected to the processor, characterized in that, The aforementioned storage unit stores multiple delivery orders, operation network information related to the procedures required for delivery, resource information related to multiple resources that can be used for the operation, and performance information representing the actual performance of the operation. Regarding the aforementioned processors, Based on the first predetermined conditions and the aforementioned operational network information, the operations corresponding to the multiple delivery orders are categorized into multiple tasks according to operational procedures. Based on the aforementioned first predetermined conditions and the aforementioned task network information, the aforementioned multiple tasks are classified into multiple task groups. Based on the above resource information, a process plan is generated for each task in the above multiple task groups, including the allocation of the above resources to the above processes, the start time of the work, and the end time of the work. Output the generated process plan. The aforementioned first predetermined conditions include the priority and smoothing conditions for the operation of each of the aforementioned delivery orders. The smoothing conditions described above represent the attributes in the delivery note that should be distributed across tasks. The processor categorizes task groups so that each task group contains only one or more tasks that are classified as having an operation corresponding to the aforementioned delivery order with the same set priority. The aforementioned processor distributes shipping orders with the same smoothing conditions evenly across multiple tasks within the task group. After the process begins according to the generated process plan, and if information indicating the end of the work is input, the aforementioned performance information is updated. Based on the aforementioned performance information, the processor monitors the deviation between the actual performance of the aforementioned process and the aforementioned process plan. If the magnitude of the deviation exceeds a predetermined benchmark, the processor regenerates the aforementioned process plan for the aforementioned tasks for which the process has not started at that moment in a manner that absorbs the deviation and improves work efficiency.

2. The job planning system according to claim 1, characterized in that, The attributes of the aforementioned shipping order, which should be distributed across multiple tasks, are at least one of the following: the size of the shipping box and the presence or absence of gift wrapping.

3. The job planning system according to claim 1, characterized in that, The processor classifies the jobs corresponding to the multiple shipping orders into multiple tasks based on the information on the types of goods included in the multiple shipping orders, thereby increasing the deviation of the types of goods shipped.

4. The job planning system according to claim 1, characterized in that, The priority of the above operations is the delivery time. The processor generates the process plan for each of the tasks to ensure that all processes are completed before the shipping time.

5. The job planning system according to claim 1, characterized in that, The priority of the above tasks indicates whether they require urgent processing or indicate a halt to shipments.

6. The job planning system according to claim 1, characterized in that, The aforementioned operational network information includes information indicating the sequence of operations required for shipment. The aforementioned resource information includes information indicating the productivity of each resource in each of the aforementioned processes. The processor calculates the time required for each of the aforementioned tasks based on the quantity of resources allocated to each of the aforementioned processes, the aforementioned productivity, and the quantity of goods on the delivery slips classified to the aforementioned tasks. Generate the above process plan so that each process starts in the order contained in the above work network information and ends after the above required time.

7. The job planning system according to claim 6, characterized in that, The processor generates the process plan for each of the tasks to start the next process before all the previous processes have been completed, in accordance with the order contained in the job network information.

8. The job planning system according to claim 7, characterized in that, The processor generates the process plan so that, when the next process begins, a portion of the resources allocated to the preceding process are moved from the preceding process to the next process.

9. The job planning system according to claim 6, characterized in that, The above resource information includes information indicating the unit price of each of the above resources. The processor generates the process plan for each of the tasks to ensure that all processes are completed before the specified delivery time for each of the shipment orders, while reducing the required costs.

10. The job planning system according to claim 1, characterized in that, In the event of a new delivery order, the processor, based on the first predetermined condition, classifies the new delivery order into any one of the plurality of tasks or a new task, and For the aforementioned delivery orders for which the process has not yet started at that time, the aforementioned process plan is regenerated.

11. The job planning system according to claim 1, characterized in that, The processor generates work instruction data for the resources based on the delivery note, and outputs the work instruction data to the resources allocated to the process at a time determined based on the start time of the process in the generated work plan.

12. The job planning system according to claim 11, characterized in that, The aforementioned resources include the equipment used in the aforementioned processes. The processor generates data for controlling the device, which serves as the operation instruction data.

13. A job scheduling method, executed by a computer system having a processor and a storage unit connected to the processor, characterized in that, The aforementioned storage unit stores multiple delivery orders, operation network information related to the procedures required for delivery, resource information related to multiple resources that can be used for the operation, and performance information representing the actual performance of the operation. The above work planning method includes the following steps: In the first step, the processor classifies the operations corresponding to the multiple delivery orders into multiple tasks according to the operation procedures based on the first predetermined conditions and the operation network information, and classifies the multiple tasks into multiple task groups based on the first predetermined conditions and the operation network information. In step 2, the processor generates a process plan for each task in the plurality of task groups based on the resource information, including the allocation of resources to the process, the start time of the task, and the end time of the task; and Step 3: The processor outputs the generated process plan. The aforementioned first predetermined conditions include the priority and smoothing conditions for the operation of each of the aforementioned delivery orders. The smoothing conditions described above represent the attributes in the delivery note that should be distributed across tasks. Step 1 above includes the following steps: The processor classifies each task group so that each task group contains only one or more tasks that are classified as having an operation corresponding to the aforementioned delivery order with the same priority; the processor evenly distributes delivery orders with the same smoothing conditions to multiple tasks within the task group. The above-mentioned work planning methods also include: Step 4: After the process begins according to the generated process plan, and given the input of information indicating the end of the work, update the aforementioned performance information. The processor monitors the deviation between the actual performance of the above-mentioned process and the planned performance of the above-mentioned process based on the performance information. If the magnitude of the aforementioned deviation exceeds a predetermined baseline, the processor regenerates the aforementioned process plan by performing the aforementioned second step to absorb the aforementioned deviation and improve operational efficiency for the aforementioned tasks that have not yet started at that moment.

Images