Allocation cost determination device, allocation cost determination method, and allocation cost determination program
The allocation cost determination device addresses the issue of inaccurate allocation tables by using past data and business rules to create a corrected allocation table, ensuring appropriate task assignment and reducing operational risks.
Patent Information
- Application Number
- JP2023501696
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-24
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2041-02-24
AI Technical Summary
Existing allocation cost determination systems fail to accurately reflect real-world business rules and worker skills, leading to inaccurate allocation tables that may not match actual worker capabilities, resulting in potential accidents and inefficiencies.
An allocation cost determination device that incorporates past allocation tables, human information, task information, and business rules to create a corrected allocation table by analyzing and adjusting the average adoption ratio of business rules, ensuring that the allocation cost values accurately reflect real-world conditions.
The device enables the creation of an allocation table that accurately reflects real-world conditions, allowing for appropriate task assignment to workers, reducing the risk of accidents and improving operational efficiency.
Smart Images

Figure 0007586282000001 
Figure 0007586282000002 
Figure 0007586282000003
Abstract
Description
[Technical field]
[0001] The present invention relates to an allocation cost determination device, an allocation cost determination method, and an allocation cost determination program. [Background technology]
[0002] An allocator who allocates tasks to workers creates task skill values and the like of the workers while considering various task rules. The allocator then combines consideration information such as task skill values with task difficulty and the like to create an allocation cost value. However, there is a problem that an allocation table created by performing optimization calculations using the created allocation cost value cannot actually be used. For example, in the created allocation table, problems occur such as workers not being assigned to tasks to which they are desired to be assigned, or the created task skill value differs from the actual task skill of the worker, resulting in accidents due to insufficient task skill of the worker. The main reasons why an allocation table cannot actually be used are, for example, the consideration information changes depending on the situation, so the accuracy of the calculated allocation cost value is low, and information about the allocation table that the allocator has manually corrected cannot be reflected in various values used when creating the allocation cost value.
[0003] For example, Patent Document 1 discloses a technique for creating an allocation table taking into consideration the differences in the capabilities of each worker. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Japanese Patent Application Publication No. 2017-211921 Summary of the Invention [Problem to be solved by the invention]
[0005] However, Patent Document 1 does not take into consideration business rules, and therefore does not resolve the reason why the above-mentioned allocation table cannot be actually used.
[0006] An object of the present invention is to make it possible to actually utilize the allocation cost value by reflecting an allocation table manually corrected by an allocator in various values used to calculate the allocation cost value. [Means for solving the problem]
[0007] In order to solve the above problem, the allocation cost determination device of the present invention has an acquisition unit that receives input information including a past allocation table indicating which tasks each of a plurality of workers performed, input preparation information including human information indicating the situation or state of each of the workers and preparation information for consideration at the time of allocation including task information indicating the tasks related to the tasks, a pre-correction allocation table and a post-correction allocation table indicating the assigned tasks of each of the workers before and after correction by an allocator, and a desired allocation table indicating the target workers and target tasks to be assigned this time among the workers and the tasks, a rule creation unit that creates business rules by combining each attribute of the human information and each task of the task information, a ratio generation unit that generates an average adoption ratio indicating the ratio to which each of the business rules was adopted in the past allocation table, and a comparison unit that compares the pre-correction allocation table with the post-correction allocation table and determines the adoption ratio in the pre-correction allocation table for the target workers. a classification unit which classifies the tasks into an unmodified task rule corresponding to a case where the task assigned to the worker in the unmodified assignment table is the same as the task assigned in the modified assignment table, a pre-modification task rule corresponding to a case where the task is assigned to the worker in the pre-modification assignment table but not assigned in the modified assignment table, and a modified task rule corresponding to a case where the task is not assigned to the worker in the pre-modification assignment table but is assigned in the modified assignment table; a ratio correction unit which decreases the average adoption ratio of the task rules corresponding to the pre-modification task rules and corrects the average adoption ratios of the task rules corresponding to the unmodified task rules and the modified task rules so as to be the same or increased; and an allocation cost determination unit which calculates an allocation cost value for assigning the target worker to the target task based on the corrected average adoption ratio. Effect of the Invention
[0008] According to one aspect of the present invention, the allocation cost value can be more easily utilized by reflecting the allocation table manually modified by the allocator in various values used to calculate the allocation cost value. Therefore, the allocator can assign appropriate tasks to workers based on the allocation cost value. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a schematic diagram showing an example of an allocator and an assigned work determination device including an assigned cost determination device according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing an example of a hardware configuration of the assigned work determination device. [Diagram 3] FIG. 3 is a block diagram showing a functional configuration of the assigned work determination device. [Figure 4] FIG. 4 is a flowchart showing an example of an average adoption ratio generation operation of business rules of the task assignment determination device. [Diagram 5] FIG. 5 is a diagram showing an example of the past allocation table. [Figure 6A] FIG. 6A is a diagram illustrating an example of human information included in the allocation consideration preparation information. [Figure 6B] FIG. 6B is a diagram illustrating an example of task information included in the allocation consideration preparation information. [Figure 7] FIG. 7 is a diagram showing an example of a method for creating business rules. [Figure 8] FIG. 8 is a diagram showing an example for determining a business rule adopted in the past combination of the worker and the task shown in FIG. [Figure 9] FIG. 9 is a diagram showing an example of the adoption determination result of the business rule for the combination of worker A and task I shown in FIG. [Figure 10] FIG. 10 is a diagram showing an example of the number of adopted business rules. [Figure 11] FIG. 11 is a diagram showing an example of the results of calculating the adoption ratio of each business rule. [Figure 12]FIG. 12 is a diagram showing an example of the average adoption ratio of each business rule. [Figure 13] FIG. 13 is a part of a flowchart showing an example of an allocation cost determination operation. [Figure 14] FIG. 14 is a diagram showing an example of the pre-correction allocation table and the post-correction allocation table. [Figure 15] FIG. 15 is a diagram showing an example of personnel information and task information in the normal allocation consideration information and personnel information and task information in the allocation consideration information. [Figure 16] FIG. 16 is a diagram showing an example of personnel information and task information of normal allocation consideration information and personnel information and task information of allocation consideration information. [Figure 17] FIG. 17 is a diagram showing an example of personnel information and task information of normal allocation consideration information and personnel information and task information of allocation consideration information. [Figure 18] FIG. 18 is a diagram showing an example of personnel information and task information of normal allocation consideration information and personnel information and task information of allocation consideration information. [Figure 19] FIG. 19 is a part of a flowchart showing an example of the operation after the process of the allocation cost determination operation proceeds to A. [Figure 20] FIG. 20 is a diagram showing business rules applicable to a case where a worker and an operation are combined. [Figure 21] FIG. 21 is a diagram showing an example of classification of business rules. [Figure 22] FIG. 22 is a diagram showing a table of average adoption ratios when the sorting results of FIG. 21 are applied. [Figure 23] FIG. 23 is a diagram illustrating an example of the corrected average adoption ratio. [Figure 24] FIG. 24 is a flowchart showing an example of the operation after the process of the allocation cost determination operation proceeds to C. [Diagram 25] FIG. 25 is a diagram showing the average adoption ratio including the personnel information, task information, and newly added business rules. [Figure 26] FIG. 26 is a diagram showing a specific example of the personnel information and task information of the allocation consideration information. [Figure 27] FIG. 27 is a diagram illustrating an example of the corrected average adoption ratio. [Figure 28] FIG. 28 is a diagram showing an example of the personnel information, task information, and average adoption ratio of the information considered at the time of allocation included in the input information. [Figure 29] FIG. 29 is a flowchart showing an example of the operation after the process of the allocation cost determination operation proceeds to E. [Diagram 30] FIG. 30 is a diagram showing an example of a method for determining a business rule corresponding to each cell of the request allocation table. [Diagram 31] FIG. 31 is a diagram showing three patterns of allocation cost values that are determined when a worker assigns a task. [Diagram 32] FIG. 32 is a diagram showing an example of business rules and cost values in a case where the only business rule that applies to a cell in the request allocation table is an allowable rule. [Diagram 33] FIG. 33 is a diagram showing an example of business rules and calculated allocation cost values when the business rules corresponding to a cell in the request allocation table are a mixture of absolute rules and permissive rules. [Diagram 34] FIG. 34 is a diagram showing an example of the allocation cost value calculated by the allocation cost determination unit. [Diagram 35] FIG. 35 is a diagram illustrating an example of an allocation plan calculated by the solver calculation. [Figure 36A] FIG. 36A is a diagram showing an example of human information and an average adoption ratio of information considered at the time of allocation when a policy is changed. [Figure 36B] FIG. 36B is a diagram showing an example of human information and an average adoption ratio of the allocation consideration information when a policy is changed. [Figure 37] FIG. 37 is a diagram showing an example of correcting the average adoption ratio when there is no data on past accidents. [Figure 38] FIG. 38 is a diagram showing an example of correcting the average adoption ratio when data on past accidents is available. [Figure 39] FIG. 39 is a flowchart showing an example of an operation for setting an allowable average adoption ratio. [Diagram 40] FIG. 40 is a diagram showing an example of setting the degree of likelihood of an accident occurring according to the accident occurrence frequency. [Diagram 41] FIG. 41 is a diagram showing an example of setting the degree of influence according to human damage and facility damage. [Diagram 42] FIG. 42 is a diagram showing an example of an unacceptable range of the degree of likelihood of an accident occurring and the degree of impact. [Diagram 43] FIG. 43 is a diagram showing an example of which of the average adoption ratios is set as the allowable average adoption ratio. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. [composition] FIG. 1 is a schematic diagram showing an example of an allocator 1 and an assigned work determination device 2 including an assigned cost determination device according to an embodiment of the present invention.
[0011] The work assignment determination device 2 may be a mobile terminal type information processing device such as a smartphone, or a stationary type information processing device such as a personal computer. In FIG. 1, the work assignment determination device 2 is shown as one information processing device for the sake of simplicity, but may include multiple information processing devices. For example, the work assignment determination device 2 may be composed of a mobile terminal type first information processing device and a stationary type second information processing device, and the first information processing device may transmit information input by the allocator 1 to the second information processing device, receive an allocation table calculated by the second information processing device, and display the allocation table to the allocator 1.
[0012] FIG. 2 is a block diagram showing an example of a hardware configuration of the assigned work determination device 2. As shown in FIG. The assigned work determination device 2 has a hardware processor 201 such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). A program memory 202, a data memory 203, a communication interface 204, and an input / output interface 205 are connected to this processor 201 via a bus 206. In addition, in Fig. 2, the "input / output interface" is written as "input / output IF".
[0013] The program memory 202 may be a storage medium that can be used by combining a non-volatile memory that can be written to and read from at any time, such as an EPROM (Erasable Programmable Read Only Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive), with a non-volatile memory such as a ROM (Read Only Memory). The program memory 202 stores programs necessary for executing various processes. In other words, all of the processing function units in the assigned work determination device 2 can be realized by reading and executing the programs stored in the program memory 202 by the processor 201.
[0014] The data memory 203 is a storage that uses a combination of a non-volatile memory that can be written to and read from at any time, such as a HDD or a memory card, and a volatile memory such as a RAM (Random Access Memory), as a storage medium. The data memory 203 is used to store data acquired and generated in the course of various processes performed by the processor 201 by executing a program.
[0015] The communication interface 204 includes one or more wired or wireless communication modules. For example, the communication interface 204 includes a communication module for wired or wireless connection to other devices. The communication interface 204 may further include a wireless communication module for wireless connection to a Wi-Fi access point, a base station, or the like. The communication interface 204 may further include a wireless communication module for wireless connection to other devices using short-range wireless technology. That is, the communication interface 204 may be a general communication interface as long as it can communicate with other devices and the like under the control of the processor 201 and transmit and receive various information.
[0016] An input unit 207 and a display unit 208 are connected to the input / output interface 205 .
[0017] The input unit 207 is, for example, an input detection sheet that employs an electrostatic or pressure method and is placed on the display screen of a display device that is the display unit 208, and outputs the touch position of the assignee 1 to the processor 201 via the input / output interface 205.
[0018] The display unit 208 is a display device that uses, for example, liquid crystal, organic EL (Electro Luminescence), or the like, and displays images and messages according to signals input from the input / output interface 205 .
[0019] FIG. 3 is a block diagram showing a functional configuration of the assigned work determination device 2. As shown in FIG.
[0020] The assigned work determination device 2 includes an acquisition unit 301, a business rule creation unit 302, a business rule analysis unit 303, an average adoption ratio generation unit 304, an output unit 305, an assignment consideration information determination unit 306, a business rule detection unit 307, a business rule sorting unit 308, an average adoption ratio correction unit 309, a business rule addition unit 310, an adoption ratio calculation unit 311, a business rule classification unit 312, an assignment cost determination unit 313, a weight value determination unit 314, and an assignment plan creation unit 315. Here, the acquisition unit 301, business rule creation unit 302, business rule analysis unit 303, average adoption ratio generation unit 304, output unit 305, allocation consideration information determination unit 306, business rule detection unit 307, business rule sorting unit 308, average adoption ratio correction unit 309, business rule addition unit 310, adoption ratio calculation unit 311, business rule classification unit 312, allocation cost determination unit 313, weight value determination unit 314, and allocation plan creation unit 315 are processing function units realized by the processor 201 reading out and executing programs stored in the program memory 202. In addition, the acquisition unit 301, the business rule creation unit 302, the business rule analysis unit 303, the average adoption ratio generation unit 304, the allocation consideration information determination unit 306, the business rule detection unit 307, the business rule sorting unit 308, the average adoption ratio correction unit 309, the business rule addition unit 310, the adoption ratio calculation unit 311, the business rule classification unit 312, the allocation cost determination unit 313, and the weight value determination unit 314 can constitute an allocation cost determination device 21 according to one embodiment of the present invention.
[0021] The acquiring unit 301 receives the input preparation information and input information input by the allocator 1 from the input unit 207. The input preparation information includes a past allocation table and information to be considered at the time of allocation. The allocator 1 prepares the past allocation table and the information to be considered at the time of allocation, and inputs them as input preparation information from the input unit 207. The acquiring unit 301 transmits the input preparation information received from the input unit 207 to the business rule creating unit 302.
[0022] The past allocation table is, for example, data in a table format showing which worker has been assigned to which task. Here, the past allocation table may be an allocation table in which the allocator 1 has actually assigned tasks to workers in the past, or may be an allocation table created by a predetermined simulation. For example, the past allocation table may be an allocation table created by the allocator 1 in the past by hand or as data, an allocation table created by the allocator 1 in the past by hand based on past experience using simulation data of a disaster or the like, or an allocation table created in the past by machine learning such as AI (Artificial Intelligence) or a solver. That is, the past allocation table may be any allocation table that shows which tasks each of multiple workers performed. In addition, the past allocation table includes N allocation tables, which is an integer equal to or greater than 1. In addition, if there is an allocation table created in an emergency such as a disaster, the allocator 1 may include this in the past allocation table, or may separately organize it as an emergency past allocation table that includes only allocation tables for past emergency situations. In addition, when using an emergency past allocation table, N is an integer equal to or greater than 2.
[0023] The allocation preparation information includes human information and task information. The human information indicates whether each worker corresponds to a number of attributes that indicate the situation and state of the worker, such as the worker's skills, and the task information indicates whether each task corresponds to a number of tasks related to the task. The allocation preparation information including the human information and task information is known to the allocator 1, and therefore can be prepared by the allocator 1. Here, the human information and task information can be, for example, tabular data represented by the worker and task at the desired date and time, and the attribute and task, and whether the worker and task correspond to each attribute and task is represented by a bit value. For example, if they correspond, the bit value is represented as "1", and if they do not correspond, the bit value is represented as "0" or blank. In the following description, if the bit value is "1", it is described that the bit value is set. A more detailed description of the allocation preparation information including the human information and task information will be given later.
[0024] The input information includes the pre-revision allocation table, the post-revision allocation table, the desired allocation table, information considered at the time of allocation, the average adoption rate of each business rule (hereinafter may be simply referred to as the average adoption rate), and the number of cases that a worker can usually handle. The allocator 1 prepares the pre-revision allocation table, the post-revision allocation table, information considered at the time of allocation, the average adoption rate of each business rule, and the number of cases that a worker can usually handle, and inputs them as input information from the input unit 207. The acquisition unit 301 transmits the input information received from the input unit 207 to the allocation consideration information determination unit 306.
[0025] The pre-revision allocation table is an allocation table before the allocator 1 made the revision, and indicates which task each of multiple workers was scheduled to perform. Like the past allocation table, the pre-revision allocation table is, for example, tabular data indicating which worker was assigned to which task. Here, the pre-revision allocation table may be any allocation table, such as an allocation table calculated in the past by the assigned task determination device 2, or an allocation table created by a predetermined simulation.
[0026] The revised allocation table is an allocation table in which the allocator 1 has revised an allocation table such as the pre-revision allocation table, and indicates which tasks each of multiple workers performed. Like the past allocation table, it is tabular data that indicates, for example, which worker was assigned to which task. In other words, the pre-revision allocation table and the post-revision allocation table indicate the assigned tasks of each worker before and after revision by the allocator 1. Here, the pre-revision allocation table and the post-revision allocation table may be allocation tables for tasks performed after the past allocation table. In other words, the pre-revision allocation table and the post-revision allocation table may be allocation tables for the most recent tasks.
[0027] The desired allocation table is data in a table format that indicates the workers and tasks to be assigned this time. For example, the desired allocation table is expressed as the workers at the desired date and time and the tasks to be assigned to one of the workers. Note that in the input desired allocation table, the values of each cell are left blank.
[0028] The allocation time consideration information includes human information and task information, similar to the allocation time consideration preparation information. Note that the allocation time consideration information may include the same human information and task information as the allocation time consideration preparation information, or may include different human information and task information.
[0029] The average adoption ratio of each business rule is a value indicating the ratio of which business rule from the past allocation table was adopted among the business rules generated based on each attribute of the human information of the allocation preparation information and each task of the task information. The method of generating business rules and the method of calculating the average adoption ratio will be described later. The calculated average adoption ratio can be stored in the data memory 203. Therefore, the average adoption ratio of the business rules included in the input information may not be the one prepared by the allocator 1, but may be the average adoption ratio of the business rules stored in the data memory 203.
[0030] The number of cases that a worker can normally handle is the number of tasks that the worker can handle during the desired time shown in the desired allocation table. For example, the allocator 1 calculates the number of tasks that the worker can handle per unit time from a past allocation table or the like. Then, the number of tasks that a worker can normally handle, that is, the number of tasks that the worker can handle during the desired time shown in the desired allocation table, may be a value calculated based on the calculated value.
[0031] The business rule creation unit 302 creates business rules based on the allocation consideration preparation information included in the input preparation information. The business rules are created by exhaustively searching combinations of each attribute of the person information and each task of the task information. The business rule creation unit 302 transmits various information including the created business rules and the input preparation information received from the acquisition unit 301 to the business rule analysis unit 303.
[0032] The business rule analysis unit 303 analyzes what business rules were adopted in past tasks based on the business rules and the N past allocation tables included in the input preparation information. Specifically, the business rule analysis unit 303 counts how much each business rule was adopted in each past allocation table. The business rule analysis unit 303 transmits various information including the analyzed information and the input preparation information to the average adoption ratio generation unit 304.
[0033] The average adoption ratio generating unit 304 calculates an average adoption ratio indicating to what extent each business rule was adopted in the N past allocation tables based on the count number in each past allocation table. The method of calculating the average adoption ratio will be described later. The average adoption ratio generating unit 304 transmits the calculated average adoption ratio to the output unit 305.
[0034] The output unit 305 displays the average adoption ratio created by the average adoption ratio generation unit 304 to the allocator 1 via the display unit 208. In addition, the assigned work determination device 2 stores in the data memory 203 the allocation time consideration preparation information included in the input preparation information as normal allocation time consideration information, and the average adoption ratio as the normal average adoption ratio.
[0035] The allocation time consideration information determination unit 306 compares information on each column of personnel information and task information of the allocation time consideration information included in the input information with each column of personnel information and task information of the normal allocation time consideration information stored in the data memory 203. Then, as a result of the comparison, the allocation time consideration information determination unit 306 determines whether the allocation time consideration information is data for normal queues or data for policy changes.
[0036] Furthermore, the allocation consideration information determination unit 306 reads the number of rows of personnel information and task information in the allocation consideration information included in the input information, i.e., the number of tasks and the number of workers. If the number of tasks is smaller than the product of the number of workers and the number of tasks that can be normally handled, the allocation consideration information determination unit 306 determines that the allocation consideration information is data for normal times. Conversely, if the number of tasks is greater than the product of the worker and the number of tasks that can be normally handled, the allocation consideration information determination unit 306 determines that the allocation consideration information is data for emergency times.
[0037] Then, the allocation time consideration information determination unit 306 determines which of the following four data classifications the input information falls into based on the determination of the columns and rows of the allocation time consideration information. (1) When it is determined that the input information is data for normal columns by comparing the columns of human information and task information and that it is data for normal times based on the number of rows of human information and task information, the input information is a data group for normal columns. (2) When it is determined that the input information is data for normal times by comparing the columns of human information and task information and that it is data for emergency times based on the number of rows of human information and task information, the input information is a data group for emergency times. (3) When it is determined that the input information is data for policy change by comparing the columns of human information and task information and that it is data for normal times based on the number of rows of human information and task information, the input information is a data group for policy change. (4) When it is determined that the input information is data for policy change by comparing the columns of human information and task information and that it is data for emergency times based on the number of rows of human information and task information, the input information is a data group for policy change and emergency times. When the allocation consideration information determination unit 306 determines that the input information is a data group at normal times or a data group at emergency times, it transmits information indicating that the input information is a data group at normal times or a data group at emergency times and various information including the input information to the business rule detection unit 307. On the other hand, when the allocation consideration information determination unit 306 determines that the input information is a data group at the time of a policy change or a data group at the time of a policy change and emergency times, it transmits information indicating that the input information is a data group at the time of a policy change or a data group at the time of a policy change and emergency times and various information including the input information to the business rule addition unit 310.
[0038] The business rule detection unit 307 detects business rules that apply when workers and tasks are combined in the pre-correction and post-correction allocation tables. The business rule detection unit 307 detects business rules that apply to the combinations of workers and tasks in each allocation table, using the normal average adoption ratio stored in the data memory 203. Then, the business rule detection unit 307 transmits various information, including the detected information and input information, to the business rule sorting unit 308.
[0039] The business rule sorting unit 308 compares the business rules corresponding to the combinations of workers and tasks in each assignment table with the information detected by the business rule detection unit 307, and sorts the business rules. For example, the business rule sorting unit 308 sorts the business rules into an unmodified business rule corresponding to the case where the task assigned to the worker before modification is the same as the task assigned in the modified assignment table, a pre-modification business rule corresponding to the case where the task is assigned to the worker in the pre-modification assignment table but not assigned in the modified assignment table, and a modified business rule corresponding to the case where the task is not assigned to the worker in the pre-modification assignment table but is assigned in the modified assignment table. The business rule sorting unit 308 then transmits various information including information on the sorting result and input information to the average adoption ratio modification unit 309.
[0040] The average adoption ratio correction unit 309 corrects the average adoption ratio of the corresponding business rule based on the information on the sorting result. For example, the average adoption ratio correction unit 309 corrects the pre-correction business rule by decreasing the ratio as a rejected business rule, and corrects the post-correction business rule by increasing the ratio as an adopted business rule. The method of correcting the average adoption ratio of a business rule will be described later. The average adoption ratio correction unit 309 stores the corrected average adoption ratio in the data memory 203 as the post-correction average adoption ratio, and transmits the post-correction average adoption ratio and the input information to the business rule classification unit 312.
[0041] The business rule adding unit 310 adds a new business rule using the allocation consideration information and the average adoption ratio included in the input information. For example, the business rule adding unit 310 generates a business rule by performing a round-robin search of combinations of attributes of each row of the human information of the allocation consideration information included in the input information and each task of the task information. Then, the business rule adding unit 310 compares the business rule of the normal average adoption ratio stored in the data memory 203 with the generated business rule, and adds a rule that is not included in the business rule of the normal average adoption ratio, i.e., a new business rule, to the business rule of the average adoption ratio. The business rule adding unit 310 transmits various information including information on the normal average adoption ratio having the added business rule and the input information to the adoption ratio calculation unit 311.
[0042] The adoption ratio calculation unit 311 calculates the adoption ratio for each newly added business rule. The method of calculating the adoption ratio is the same as the method of calculating the average adoption ratio, and therefore a detailed description thereof will be omitted here. The adoption ratio calculation unit 311 transmits various information including information on the normal average adoption ratio having the adoption ratio of the newly added business rule and input information to the business rule detection unit 307. The business rule detection unit 307, the business rule classification unit 308, and the average adoption ratio correction unit 309 that receive the normal average adoption ratio having the adoption ratio of the newly added business rule have the same configurations as those described above, and therefore a detailed description thereof will be omitted here. The method of correcting the adoption ratio of the newly added business rule will be described later.
[0043] The business rule classification unit 312 classifies business rules into absolute rules, violation rules, and permissible rules based on the corrected average adoption ratio. Here, an absolute rule is a business rule that has always been adopted in the past allocation table and has a maximum corrected average adoption ratio. A violation rule is a business rule that has never been adopted in the past allocation table and has a minimum corrected average adoption ratio. A permissible rule is a business rule that has been adopted in some cases and not adopted in the allocation table and has a corrected average adoption ratio that is greater than the minimum value and less than the maximum value. The business rule classification unit 312 transmits various information, including information on the classification of this business rule, the corrected average adoption ratio received from the average adoption ratio modification unit 309, and input information, to the allocation cost determination unit 313.
[0044] The allocation cost determination unit 313 determines what kind of business rule has a bit of the corresponding worker in the human information set and a bit of the corresponding task in the task information set in each cell of the worker and task in the desired allocation table included in the input information. Furthermore, the allocation cost determination unit 313 determines whether the corresponding business rule in each cell is an absolute rule, a permissive rule, or a violation rule. Then, the allocation cost determination unit 313 judges whether the allocation cost value can be calculated based on the three determined rules. The allocation cost value is a numerical representation of "the degree to which a worker is desired to be assigned to each task." Therefore, the higher the allocation cost value, the more suitable the task is considered to be. In one embodiment, the allocation cost value is expressed as 0 to 100. For example, if the allocation cost determination unit 313 determines that all the corresponding business rules are absolute rules, the allocation cost value is 100, which is the maximum value. Furthermore, if the allocation cost determination unit 313 determines that the corresponding business rules include at least one violation rule, the allocation cost value is 0, which is the minimum value. In these cases, the allocation cost determination unit 313 can uniquely determine the allocation cost value. On the other hand, if it is determined that the business rule is only an allowable rule, or an allowable rule and an absolute rule, the allocation cost value is either a value greater than the minimum value and less than the maximum value (i.e., 0<allocation cost value<100). Then, the allocation cost determination unit 313 cannot determine what value the allocation cost value will be. If the allocation cost determination unit 313 determines that it can calculate the allocation cost value for all cells in the desired allocation table, the allocation cost determination unit 313 determines the allocation cost value for each cell. On the other hand, if it cannot determine the allocation cost value for all cells in the desired allocation table, the allocation cost determination unit 313 transmits various information such as the average adoption ratio for the cells for which the allocation cost value cannot be determined to the weight value determination unit 314.
[0045] The weight value determination unit 314 determines a weight value k for each business rule based on the average adoption ratio of business rules in cells for which an allocation cost value cannot be determined, the number of business rules in the cell, and the maximum value of the average adoption ratios of business rules in the cell. The method of determining the weight value k will be described later. The weight value determination unit 314 determines a weight value for each cell for which an allocation cost value cannot be determined, and transmits the determined weight value to the allocation cost determination unit 313.
[0046] The allocation cost determination unit 313 can determine the allocation cost value of each cell of the desired allocation table based on the weight value received from the weight value determination unit 314. Then, the allocation cost determination unit 313 transmits various information including information on the determined allocation cost value of each cell of the desired allocation table to the allocation plan creation unit 315.
[0047] The allocation plan creating unit 315 creates an allocation plan by, for example, performing a solver calculation on the allocation cost values of the received desired allocation table. The allocation plan creating unit 315 transmits the determined allocation plan to the output unit 305.
[0048] The output unit 305 displays the allocation plan created by the allocation plan creating unit 315 to the allocator 1 via the display unit 208. The allocator 1 can allocate tasks to workers based on the allocation plan displayed on the display unit 208.
[0049] [Operation] (Average hiring rate generation) 4 is a flowchart showing an example of an average adoption ratio generation operation of business rules by the work assignment determination device 2. The processor 201 of the work assignment determination device 2 reads out and executes a program stored in the program memory 202, thereby realizing the operation of this flowchart.
[0050] The acquisition unit 301 of the assigned work determination device 2 receives (401) the input preparation information including the past assignment table and assignment time consideration preparation information input by the allocator 1 via the input unit 207. The acquisition unit 301 transmits the received input preparation information to the business rule creation unit 302.
[0051] FIG. 5 is a diagram showing an example of a past allocation table. According to the example shown in FIG. 5, it is shown that between 9:00 and 12:00 on a certain day, worker A performed task I, worker B performed task II, and worker C performed task III. In other words, the past allocation table is information indicating what tasks each worker performed during a certain period. Here, it is assumed that there are N past allocation tables, where N is an integer equal to or greater than 1. Therefore, the past allocation tables included in the input preparation information include N tables as shown in FIG. 5.
[0052] FIG. 6A is a diagram showing an example of human information included in the allocation preparation information. In FIG. 6A, an example of an attribute related to a worker is shown in each row, and each worker is shown in each column. The attributes shown in FIG. 6A are veteran, novice, and dexterous. In the example of FIG. 6A, whether each worker corresponds to each attribute is represented by a bit value. In the example of FIG. 6A, since worker A is a veteran, a bit value is set for the veteran attribute, since worker B is a novice, a bit value is set for the novice attribute, and since worker C is dexterous, a bit value is set for the dexterous attribute.
[0053] Fig. 6B is a diagram showing an example of task information included in the allocation consideration preparation information. In Fig. 6B, an example of a task for each work is shown in each row, and an example of a type of work is shown in each column. Each task shown in Fig. 6B is a work type, an area, necessary equipment, etc. For simplification, the example shown in Fig. 6B shows only the work type, and the work type is, for example, work type 1 (electric pole inspection), work type 2 (manhole inspection), and work type 3 (branch line inspection).
[0054] Note that the attributes and tasks shown in FIG. 6A and FIG. 6B are merely examples, and the attributes may be any one related to the worker, and the tasks may be any one related to the work.
[0055] The business rule creation unit 302 of the task allocation determination device 2 creates business rules from the allocation time consideration preparation information included in the received input preparation information (402). FIG. 7 is a diagram showing an example of a method for creating business rules. As shown by the arrows in FIG. 7, the business rule creation unit 302 creates business rules by exhaustively searching combinations of each attribute of the personnel information included in the allocation time consideration preparation information and each task of the task information. For example, three business rules, business rules 1 to 3, are created by combining a veteran in the personnel information with each of the three tasks of the task information. That is, business rule 1: veteran workers are assigned to work type 1 (electric pole inspection), business rule 2: veteran workers are assigned to work type 2 (manhole inspection), and business rule 3: veteran workers are assigned to work type 3 (branch line inspection). The business rule creation unit 302 creates business rules for newcomers and dexterity, which are other attributes of the personnel information, in the same manner as above. The business rule creation unit 302 can also operate as a rule creation unit. The business rule creation unit 302 transmits the created business rules and various information including input information preparation to the business rule analysis unit 303 .
[0056] The business rule analysis unit 303 analyzes the received business rule (403). First, for each of the N past allocation tables, the business rule analysis unit 303 counts which business rules have been adopted in both the person information and the task information among the business rules created by the business rule creation unit 302. The business rule analysis unit 303 determines that a business rule with a bit value set in both the person information and the task information is a business rule that has been adopted for a combination of worker and task that has been assigned in the past.
[0057] FIG. 8 is a diagram showing an example for determining a business rule adopted in the past combination of the worker and the task shown in FIG. 5. The human information and the task information have bit values as shown in FIG. 8, as shown in FIG. 6A and FIG. 6B. For example, for the business rule 1, the bit values of both the human information and the task information are set. Then, the combination of the worker A and the task I in the combination of the worker and the task shown in FIG. 5 matches this business rule 1, so the business rule analysis unit 303 determines that the business rule 1 is a business rule adopted in the past. In contrast, for the business rule 2, the bit value of the human information is set, but the bit value of the task information is blank, and there is no combination that matches the combination of the worker and the task shown in FIG. 5. Therefore, the business rule analysis unit 303 determines that the business rule 2 is a business rule that has not been adopted in the past. The business rule analysis unit 303 makes such a determination for all the business rules created by the business rule creation unit 302.
[0058] FIG. 9 is a diagram showing an example of a result of determining whether or not a business rule is adopted for the combination of worker A and work I shown in FIG. 5. As shown in FIG. 9, the business rule analysis unit 303 determines that business rules 1, 3, etc. are adopted business rules for the combination of worker A and work I, and business rule 2, etc. are not adopted business rules. The business rule analysis unit 303 stores the number of adoptions of each business rule in the data memory 203, while incrementing the number of adoptions by +1 for business rules determined to be adopted business rules and leaving the number of adoptions unchanged for business rules determined to be not adopted business rules. The business rule analysis unit 303 repeats the above-mentioned determination and storage for the number of workers shown in FIG. 5 and counts which business rules have been adopted per past allocation table, thereby determining the total number of adoptions.
[0059] Fig. 10 is a diagram showing an example of the number of adopted business rules. As shown in Fig. 10, the above-mentioned counting determines the total number of business rules adopted per past assignment table for the combination of worker and task shown in Fig. 5.
[0060] The business rule analysis unit 303 performs this determination for each of the N past allocation tables. Then, the business rule analysis unit 303 transmits various information including the total number of adopted business rules for each past allocation table, the business rules, and input information to the average adoption ratio generation unit 304.
[0061] The average adoption ratio generating unit 304 generates an average adoption ratio (404). The average adoption ratio generating unit 304 can also operate as a ratio generating unit. First, the average adoption ratio generating unit 304 calculates the maximum number of business rules per past allocation table based on the number of cells with bit values set in the personnel information and task information included in the allocation consideration preparation information. For example, when determining the maximum number of business rules 1: "Experienced workers are assigned to work type 1 (electric pole inspection)" per past allocation table, the average adoption ratio generating unit 304 calculates the sum of bit values in the veteran column of the personnel information shown in Fig. 6A and the work type 1 column of the task information shown in Fig. 6B. The total bit value in the veteran column is the maximum number of business rules 1 in the personnel information, and the total bit value in the work type 1 column is the maximum number of business rules 1 in the task information.
[0062] Next, the average adoption ratio generating unit 304 compares the maximum number of business rules 1 in the human information with the maximum number of business rules 1 in the task information, and the smaller value is set as the maximum number of business rules 1 per past allocation table. If the maximum numbers are equal, the smaller value is set as the maximum number of business rules per past allocation table. As a result of the comparison, the smaller value is set as the maximum number of business rules per past allocation table because the adoption of a business rule corresponds to the case where the bit value of the attribute of the human information and the task of the task information are set. In other words, when the total of the bit values of each column is compared between the human information and the task information, there are no business rules adopted that are greater than the smaller number. For example, if there are five workers with a bit value set in the veteran column of the human information, and there are two tasks with a bit value set in the task type 1 column of the task information, the combination of the human information and the task information that adopts the business rule will be at most two. Therefore, the smaller value is adopted as the maximum number of business rules per allocation table, and the adopted value represents the maximum number of combinations that adopt the business rule. 6A and 6B, the maximum number of business rules 1 per one allocation table is 1 because the maximum number of business rules 1 for people information and the maximum number of business rules 1 for task information are both 1. The average adoption ratio generation unit 304 calculates the maximum number for each of all business rules per one allocation table.
[0063] Next, the average adoption ratio generating unit 304 calculates the adoption ratio of each business rule as follows: Business rule adoption ratio (%)=100*total number of adopted business rules per allocation table / maximum number of business rules per allocation table. For example, with reference to FIG. 10, the total number of adopted business rules 1 per allocation table is 1, and the maximum number of business rules 1 is also 1 as described above. Therefore, the adoption ratio of business rule 1 is 100%. The average adoption ratio generating unit 304 similarly calculates the adoption ratios of the other business rules.
[0064] Fig. 11 is a diagram showing an example of the results of calculating the adoption rate of each business rule. In the example shown in Fig. 11, the adoption rate of business rule 1 is 100% as described above, the adoption rate of business rule 2 is 0%, and the adoption rate of business rule 3 is 50%.
[0065] The average adoption ratio generation unit 304 calculates this adoption ratio for all N past allocation tables. Then, the average adoption ratio generation unit 304 calculates the average adoption ratio for each business rule from the adoption allocation for these N tables. For example, the average adoption ratio for business rule 1 is calculated as follows: Average adoption ratio = (adoption ratio in the first past allocation table + adoption ratio in the second past allocation table + ... + adoption ratio in the Nth past allocation table) / N.
[0066] Fig. 12 is a diagram showing an example of the average adoption rate of each business rule. In the example shown in Fig. 12, the average adoption rate of business rule 1 is 100%, the average adoption rate of business rule 2 is 0%, and the average adoption rate of business rule 3 is 40%.
[0067] The average adoption ratio generation unit 304 transmits information about a table of the calculated average adoption ratios of each business rule as shown in Fig. 12 to the output unit 305. The output unit 305 displays the average adoption ratio to the allocator 1 via the display unit 208. In addition, the assigned work determination device 2 stores in the data memory 203 the allocation time consideration preparation information included in the input preparation information as normal allocation time consideration information and the average adoption ratio as a normal average adoption ratio.
[0068] (Average hiring rate corrected) 13 is a part of a flowchart showing an example of an assigned cost determination operation. The processor 201 of the assigned work determination device 2 reads out and executes a program stored in the program memory 202, thereby realizing the operation of this flowchart.
[0069] The acquisition unit 301 of the assigned work determination device 2 receives (1301) input information including the pre-correction assignment table, the corrected assignment table, the desired assignment table, information considered at the time of assignment, the normal average adoption rate, and the number of cases that a worker can normally handle, which have been input by the allocator 1 via the input unit 207. Note that the normal average adoption rate may not be included in the input information input by the allocator 1, since the normal average adoption rate stored in the data memory 203 may be used.
[0070] Fig. 14 is a diagram showing an example of an allocation table before and after correction. Fig. 14(a) is the allocation table before correction, and Fig. 14(b) is the allocation table after correction. Comparing the allocation table before and after correction, the allocation of worker B has been changed from task II to task III, and the allocation of worker C has been changed from task II to task II.
[0071] The allocation time consideration information determination unit 306 determines whether the allocation time consideration information is data for normal queuing based on the column information in the person information and task information of the allocation time consideration information included in the input information (1302). The allocation time consideration information determination unit 306 compares the person information and task information of the normal allocation time consideration information stored in the data memory 203 with each attribute and the number of columns entered in the columns of the person information and task information of the allocation time consideration information. If there is no change in each attribute and the number of columns, the allocation time consideration information determination unit 306 determines that the data is data for normal queuing, and if there is a change in either each attribute or the number of columns, it determines that the data is data for a policy change.
[0072] FIG. 15 is a diagram showing an example of human information and task information of the normal allocation consideration information, and human information and task information of the allocation consideration information. FIG. 15(a) is a diagram showing an example of human information of the normal allocation consideration information, FIG. 15(b) is a diagram showing an example of human information of the allocation consideration information, FIG. 15(c) is a diagram showing an example of task information of the normal allocation consideration information, and FIG. 15(d) is a diagram showing an example of task information of the allocation consideration information. Comparing FIG. 15(a) and FIG. 15(b), there is no change in each attribute and the number of columns inputted in the columns. Furthermore, comparing FIG. 15(c) and FIG. 15(d), there is no change in each attribute and the number of columns inputted in the columns. Therefore, in the example shown in FIG. 15, since there is no change in each attribute and the number of columns of the allocation consideration information, the allocation consideration information determination unit 306 determines that the allocation consideration information is data at the time of normal columns, that is, there is no change in the business rule.
[0073] FIG. 16 is a diagram showing an example of human information and task information of the normal allocation consideration information, and human information and task information of the allocation consideration information. FIG. 16 is similar to FIG. 15, in which (a) of FIG. 16 shows an example of human information of the normal allocation consideration information, (b) shows an example of human information of the allocation consideration information, (c) shows an example of task information of the normal allocation consideration information, and (d) shows an example of task information of the allocation consideration information. Comparing (a) and (b) of FIG. 16, a new column called equipment (mask) has been added, and the number of columns has increased (the area surrounded by a thick line in FIG. 16(b)). Furthermore, comparing (c) and (d) of FIG. 16, the attribute entered in the first column has been changed from work type 1 (electric pole inspection) to work type 4 (hole digging) (the area surrounded by a thick line in FIG. 16(d)). In this way, when a change occurs in either the attributes input in the columns or the number of columns, the allocation time consideration information determination unit 306 determines that the allocation time consideration information is data at the time of a policy change, that is, a change has occurred in the business rules.
[0074] When it is determined that the allocation consideration information is data for normal queues, the allocation consideration information determination unit 306 determines whether the allocation consideration information for normal queues is data for normal times (1303). The allocation consideration information determination unit 306 recognizes the number of rows of human information, i.e., the number of workers, and the number of rows of task information, i.e., the number of tasks, in the allocation consideration information. Then, it determines whether the recognized number of tasks is equal to or less than the product of the number of workers and the number of tasks that can be normally handled. When it is determined that the number of tasks is equal to or less than the product of the number of workers and the number of tasks that can be normally handled, the allocation consideration information determination unit 306 determines that the allocation consideration information is data for normal times. On the other hand, when the number of tasks is greater than the product of the number of workers and the number of tasks that can be normally handled, the allocation consideration information determination unit 306 determines that the allocation consideration information is data for emergency times.
[0075] FIG. 17 is a diagram showing an example of human information and task information of the normal allocation consideration information, and human information and task information of the allocation consideration information. FIG. 17(a) is a diagram showing an example of human information of the allocation consideration information, and FIG. 17(b) is a diagram showing an example of task information of the allocation consideration information. As shown in FIG. 17(a), the number of rows (number of workers) of the human information of the allocation consideration information is 3, and as shown in FIG. 17(b), the number of rows of task information of the allocation consideration information is also 3. In addition, for example, if the number of cases that can be normally handled is 1, the number of operations (3 cases)≦workers (3 people)×number of cases that can be normally handled (1 case). In this case, the allocation consideration information determination unit 306 determines that the allocation consideration information is data for normal times.
[0076] FIG. 18 is a diagram showing an example of human information and task information of normal allocation consideration information, and human information and task information of allocation consideration information. FIG. 18(a) is a diagram showing an example of human information of allocation consideration information, and FIG. 18(b) is a diagram showing an example of task information of allocation consideration information. As shown in FIG. 18(a), the number of rows (number of workers) of human information of allocation consideration information is 3, and as shown in FIG. 18(b), the number of rows of task information of allocation consideration information is 4. Also, for example, if the number of cases that can be normally handled is 1, then the number of operations (4 cases)>workers (3 people)×number of cases that can be normally handled (1 case). In this case, the allocation consideration information determination unit 306 determines that the allocation consideration information is data for an emergency.
[0077] When it is determined that the allocation time consideration information is data for normal times, the allocation time consideration information determination unit 306 determines that the input information is a data group for normal times. Then, the allocation time consideration information determination unit 306 transmits information indicating that the input information is a data group for normal times and the input information to the business rule detection unit 307 (1304). Then, the processing proceeds to A. On the other hand, when it is determined that the input information is a data group for emergency times, the allocation time consideration information determination unit 306 determines that the input information is a data group for emergency times. Then, the allocation time consideration information determination unit 306 transmits information indicating that the input information is a data group for emergency times and the input information to the business rule detection unit 307 (1305). Then, the processing proceeds to A.
[0078] When it is determined in 1302 that the allocation time consideration information is data at the time of a policy change, the allocation time consideration information determination unit 306 determines whether the allocation time consideration information is data at the time of normal operation (1306). The allocation time consideration information determination unit 306 recognizes the number of lines of human information, i.e., the number of workers, and the number of lines of task information, i.e., the number of tasks, in the allocation time consideration information. Then, it determines whether the recognized number of tasks is equal to or less than the product of the number of workers and the number of tasks that can be normally handled. When it is determined that the number of tasks is equal to or less than the product of the number of workers and the number of tasks that can be normally handled, the allocation time consideration information determination unit 306 determines that the allocation time consideration information is data at the time of a policy change. On the other hand, when the number of tasks is greater than the product of the number of workers and the number of tasks that can be normally handled, the allocation time consideration information determination unit 306 determines that the allocation time consideration information is data at the time of a policy change and emergency. Note that these operations are the same as the determination in 1303.
[0079] When it is determined that the allocation time consideration information is data for normal times, the allocation time consideration information determination unit 306 determines that the input information is a data group for when a policy is changed. Then, the allocation time consideration information determination unit 306 transmits information indicating that the input information is a data group for when a policy is changed and the input information to the business rule adding unit 310 (1307). Then, the process proceeds to C. On the other hand, when it is determined that the input information is a data group for when an emergency occurs, the allocation time consideration information determination unit 306 determines that the input information is a data group for when a policy is changed and an emergency. Then, the allocation time consideration information determination unit 306 transmits information indicating that the input information is a data group for when a policy is changed and an emergency and the input information to the business rule adding unit 310 (1308), and the process proceeds to C.
[0080] 19 is a part of a flowchart showing an example of the operation when the processing of the assigned cost determination operation proceeds to A after the input information and information indicating that the input information is a data group under normal conditions are transmitted to the business rule detection unit 307 in 1304. The operation of this flowchart is realized by the processor 201 of the assigned work determination device 2 reading and executing a program stored in the program memory 202.
[0081] The business rule detection unit 307 detects a business rule that corresponds to a combination of a worker and an operation using the allocation consideration information and the normal average adoption ratio (1901). The business rule detection unit 307 detects a business rule that corresponds to a combination of a worker and an operation in each allocation table using the normal average adoption ratio. For example, referring to (b) and (d) of FIG. 12 and FIG. 15, when a veteran worker A performs an operation I, the corresponding business rules are business rule 1 and business rule 3. Similarly, when worker A performs an operation II, the corresponding business rule is business rule 2. Similarly, the business rule that corresponds to all combinations of workers and operations is detected. Then, the business rule detection unit 307 transmits various information including information on the detected business rule and input information to the business rule classification unit 308.
[0082] Fig. 20 is a diagram showing business rules that apply when a worker and an operation are combined. For simplicity, in Fig. 20, business rules that apply when a worker and an operation are combined are simply indicated by numbers.
[0083] The business rule sorting unit 308 compares the pre-correction allocation table with the post-correction allocation table and sorts the business rules (1902). Here, the business rule sorting unit 308 can also operate as a sorting unit. From the information detected by the business rule detection unit 307, the business rules corresponding to the combination of the worker and the task in each allocation table are compared and the business rules are sorted. As a result of the comparison, the business rule sorting unit 308 sorts the business rules into (A) uncorrected business rules corresponding to the business rules whose business rules are the same in the pre-correction allocation table and the post-correction allocation table, (B) pre-correction business rules corresponding to the business rules that matched in the pre-correction allocation table but did not match in the post-correction allocation table, and (C) post-correction business rules corresponding to the business rules that did not match in the pre-correction allocation table but matched in the post-correction allocation table. The business rule sorting unit 308 transmits various information including information on the sorting result and input information to the average adoption ratio correction unit 309.
[0084] FIG. 21 is a diagram showing an example of classification of business rules. FIG. 21(a) is a diagram showing an allocation table before correction, FIG. 21(b) is a diagram showing an allocation table after correction, and FIG. 21(c) is a diagram showing an example of classification of business rules. Comparing FIG. 21(a) and FIG. 21(b), while the worker A remains in task I, the worker B has changed from task II to task III, and the worker C has changed from task III to task II. Therefore, as shown in FIG. 21(c), the business rule classification unit 308 classifies business rules 1 and 3 corresponding to the combination of worker A and task I as unmodified business rules, classifies business rules 5 and 9 corresponding to worker B and task II and worker C and task III as pre-modified business rules, and classifies business rules 6 and 8 corresponding to worker B and task III and worker C and task II as modified business rules.
[0085] The average adoption rate correction unit 309 corrects the average adoption rate based on the sorted business rules (1903). Here, the average adoption rate correction unit 309 can also operate as a rate correction unit. The average adoption rate correction unit 309 calculates the corrected average adoption rate by (normal average adoption rate for each business rule * N + corrected adoption rate) / (number of past allocation tables + 1). The corrected average adoption rate is calculated by multiplying the average adoption rate for each business rule of the normal average adoption rate by N, and since the corrected allocation table increases the number of allocation tables by one, adding "+1" to the denominator and adding the corrected adoption rate to the numerator. Note that if the corrected average adoption rate exceeds the maximum value (e.g., 100%) or falls below the minimum value (e.g., 0%), the average adoption rate correction unit 309 calculates the corrected average adoption rate to be the maximum value or the minimum value, respectively.
[0086] Here, the average adoption rate correction unit 309 calculates the modified adoption rate as (Aa-Bb+Cc) / (Aa+Bb+Cc). Here, A, B, and C are bit values indicating whether or not there is an unmodified business rule, a pre-modified business rule, and a post-modified business rule, respectively, and are values that are "1" if there is a corresponding business rule, and "0" if there is not. Furthermore, a, b, and c are the numbers of unmodified business rules, pre-modified business rules, and post-modified business rules, respectively. A business rule corresponding to an unmodified business rule is a business rule that should be adopted without modification, so it is reflected in the modified adoption rate as a positive value. A business rule corresponding to a pre-modified business rule is a business rule that was not adopted after modification, and the business rule should not have been adopted, so it is adopted in the modified adoption rate as a negative value. And a business rule corresponding to a post-modified business rule is a business rule that was adopted after modification, and the business rule should have been adopted, so it is reflected in the modified adoption rate as a positive value.
[0087] The average adoption ratio correcting unit 309 calculates the corrected average adoption ratio (1904). The average adoption ratio correcting unit 309 calculates the corrected average adoption ratio by having the business rule sorting unit 308 calculate the average adoption ratios for the business rules corresponding to the unmodified business rules, the pre-modification business rules, and the post-modification business rules. The average adoption ratio correcting unit 309 transmits various information including the calculated corrected average adoption ratio and the input information to the business rule classification unit 312. Then, the process proceeds to E.
[0088] Fig. 22 is a diagram showing a table of average adoption ratios when the sorting results of Fig. 21 are applied. As shown in Fig. 22, the average adoption ratio modification unit 309 determines that business rules 1 and 3 are unmodified business rules, business rules 5 and 9 are pre-modified business rules, and business rules 6 and 8 are post-modified business rules. Furthermore, the average adoption ratio modification unit 309 does not modify the average adoption ratios for business rules 2, 4, and 7, which do not fall under any of the unmodified business rules, pre-modified business rules, or post-modified business rules, based on the sorting results.
[0089] Fig. 23 is a diagram showing an example of the modified average adoption ratio. As shown in Fig. 23, the modified average adoption ratios corresponding to the unmodified business rules and the modified business rules are the same as or have increased compared to the average adoption ratio. Similarly, the modified average adoption ratio corresponding to the pre-modified business rules is decreased compared to the average adoption ratio.
[0090] The allocation cost determination operation in the case where the process proceeds to A after the input information and the information indicating that the input information is a data group in an emergency are transmitted to the business rule detection unit 307 in 1305 is also as shown in Fig. 19. For example, even if a new task such as task IV is added to the revised allocation table as shown in Fig. 18(b), no business rule is added. Therefore, the business rule detection unit 307 can detect the business rule corresponding to each worker and task IV. Therefore, the allocation cost determination device 21 can perform the same process as when the input information is a data group in a normal state, and therefore a detailed description will be omitted here.
[0091] 24 is a flowchart showing an example of the operation when the processing of the assigned cost determination operation proceeds to C after the input information and information indicating that the input information is a data group at the time of a policy change are sent to the business rule adding unit 310 in 1307. The operation of this flowchart is realized by the processor 201 of the assigned work determination device 2 reading and executing a program stored in the program memory 202.
[0092] The business rule adding unit 310 adds a new business rule using the allocation consideration information and the average adoption ratio included in the input information (2401). For example, the business rule adding unit 310 generates a business rule by performing a round-robin search of combinations of attributes of each row of the human information considered at the time of allocation included in the input information and each task of the task information. Then, the business rule adding unit 310 compares the generated business rule with the business rule of the normal average adoption ratio stored in the data memory 203, and adds a rule that is not included in the business rule of the normal average adoption ratio, i.e., a new business rule, to the business rule of the average adoption ratio. Then, the business rule adding unit 310 transmits various information including information on the average adoption ratio to which the newly added business rule has been added and the input information to the adoption ratio calculation unit 311.
[0093] FIG. 25 is a diagram showing the average adoption ratio including the personnel information, task information, and newly added business rules. FIG. 25 (a) shows personnel information, (b) shows task information, and (c) shows the average adoption ratio including the newly added business rule. As shown in FIG. 25 (a), the personnel information has an attribute of equipment (mask) added to it compared to the personnel information in the allocation time consideration preparation information. Also, as shown in FIG. 25 (b), the task information has a task changed from work type 1 (electric pole inspection) to work type (hole digging) compared to the task information in the allocation time consideration preparation information, and further, a task of mask required has been added. The business rule adding unit 310 adds the newly added business rules by these added or changed tasks to the normal time average adoption ratio.
[0094] The adoption ratio calculation unit 311 calculates the adoption ratio for each newly added business rule (2402). The adoption ratio calculation unit 311 calculates the sum of bit values in the column of attributes newly added to the human information of the allocation preparation information. Similarly, the adoption ratio calculation unit 311 calculates the sum of bit values in the column of tasks newly added to the task information of the allocation consideration information. The adoption ratio calculation unit 311 then determines the smaller of the total values as the maximum number of business rules per revised allocation table. The reason for adopting the smaller of the total numbers is the same as the reason for using the smaller of the maximum number of business rules for human information and the maximum number of business rules for task information, which are used when the average adoption ratio generation unit 304 calculates the average adoption ratio.
[0095] Fig. 26 is a diagram showing a specific example of personnel information and task information of the allocation consideration information. As shown in Fig. 26, the sum of the bit values included in the column of equipment (mask), which is a newly added attribute in the personnel information, and the sum of the bit values included in the column of mask mandatory, which is a newly added task in the task information, are both 2. Therefore, the adoption ratio calculation unit 311 calculates the maximum number of business rules per revised allocation table to be "2".
[0096] Next, the adoption ratio calculation unit 311 calculates the adoption ratio of the newly added business rule by: adoption ratio of business rule (%) = 100 * total number of adopted business rules per revised allocation table / maximum number of business rules per revised allocation table. Note that this calculation method is the same as the method used by the average adoption ratio generation unit 304 when calculating the average adoption ratio, and further detailed explanation will be omitted here. The adoption ratio calculation unit 311 transmits various information including the normal average adoption ratio having the calculated adoption ratio of the newly added business rule and the input information to the business rule detection unit 307.
[0097] The business rule detection unit 307 detects a business rule that corresponds to a combination of workers and tasks using the allocation consideration information and the normal average adoption ratio (2403). The business rule detection unit 307 detects a business rule that corresponds to a combination of workers and tasks in each allocation table using the normal average adoption ratio that has the adoption ratio of the newly added business rule. Note that the business rule detection unit 307 performs the same process as 1901 described using FIG. 19 except that it uses the normal average adoption ratio that has the adoption ratio of the newly added business rule as the normal average adoption ratio, so further description here will be omitted.
[0098] The business rule sorting unit 308 compares the pre-correction allocation table with the corrected allocation table and sorts the business rules (2404). The business rules corresponding to the combinations of workers and tasks in each allocation table are compared from the information detected by the business rule detection unit 307, and the business rules are sorted. Note that the business rule sorting unit 308 performs the same process as 1902 described using FIG. 19 except that it uses the normal average adoption ratio, which has the adoption ratio of the newly added business rule, as the normal average adoption ratio, and therefore further explanation here is omitted.
[0099] The average adoption rate modification unit 309 modifies the average adoption rate based on the sorted business rules (2405). The average adoption rate modification unit 309 calculates the modified average adoption rate by (normal average adoption rate for each business rule * N + modified adoption rate) / (number of past allocation tables + 1). The modified average adoption rate is calculated by multiplying the average adoption rate for each business rule of the normal average adoption rate by N, and since the modified allocation table increases the number of allocation tables by one, adding "+1" to the denominator and adding the modified adoption rate to the numerator. Note that if the modified average adoption rate exceeds the maximum value (e.g., 100%) or falls below the minimum value (e.g., 0%), the average adoption rate modification unit 309 calculates the modified average adoption rate to be the maximum value or the minimum value, respectively. However, when calculating the average adoption rate for a newly added business rule, since there is no past data, N is set to 0 to calculate the modified average adoption rate. The method for calculating the revised adoption ratio is the same as the method for calculating the revised adoption ratio explained in 1903 of FIG. 19, so further explanation will be omitted here.
[0100] The average adoption ratio correcting unit 309 calculates the corrected average adoption ratio (2406). The average adoption ratio correcting unit 309 calculates the corrected average adoption ratio by having the business rule sorting unit 308 calculate the average adoption ratios for the business rules corresponding to the unmodified business rules, the pre-modification business rules, and the post-modification business rules. The average adoption ratio correcting unit 309 transmits various information including the calculated corrected average adoption ratio and the input information to the business rule classification unit 312. Then, the process proceeds to E.
[0101] 27 is a diagram showing an example of the corrected average adoption ratio. As shown in FIG 27, the average adoption ratio of the newly added business rules 10 and 11 can be calculated.
[0102] The allocation cost determination operation in the case where the process proceeds to C after the input information and the information indicating that the input information is a data group at the time of a policy change and an emergency are transmitted to the business rule detection unit 307 in 1308 is also as shown in Fig. 24. For example, even if a new task such as task IV is added to the revised allocation table as shown in Fig. 18(b), a business rule is not added. Therefore, the business rule detection unit 307 can detect the business rule corresponding to each worker and task IV. Therefore, the allocation cost determination device 21 can perform the same process as when the input information is a data group at the time of a policy change, and therefore a detailed description thereof will be omitted here.
[0103] (Application example 1) Application example 1 in one embodiment will be described below. The task assignment determination device 2 can receive input information multiple times, for example. In this case, as described above with reference to Figs. 13 to 27, the task assignment determination device 2 calculates a corrected average ratio based on the assignment consideration information included in each received input information. At this time, the number of times that the assignment consideration information is determined to be data at the time of policy change or data at the time of policy change and emergency may be greater than the number of times that the assignment consideration information is determined to be data at the time of normal time or data at the time of emergency. In this case, the assignment cost determination device 21 can change the corrected average adoption ratio to the normal average adoption ratio. This data can be used by the allocator 1, etc. when creating a manual or analyzing data, making it easier for the allocator 1, etc. to grasp the current situation.
[0104] (Application example 2) Application example 2 in one embodiment will be described below. FIG. 28 is a diagram showing an example of the personnel information, task information, and average adoption ratio of the allocation consideration information included in the input information. FIG. 28 (a) shows personnel information, (b) shows task information, and (c) shows the average adoption ratio. In this example, the bit value of the attribute of black telephone (dial type) in the fourth column of FIG. 28 (a) or the task of black telephone correspondence possible in the fourth column of FIG. 28 (b) is not set a predetermined number of times. Here, the predetermined number of times may be, for example, N, which is the number of past allocation information. The personnel information or task information of the allocation consideration information indicates that the attribute or task in the fourth column is not necessary. Therefore, in 1302 of FIG. 13, if the bit value is not set a predetermined number of times, the allocation consideration information determination unit 306 can delete the information in the fourth column. At this time, the allocation consideration information determination unit 306 also deletes the business rule 11 corresponding to the unused normal average adoption ratio surrounded by the dotted line frame shown in FIG. 28 (c). By periodically deleting column information that is no longer in use and the normal average adoption ratio in this manner, it is possible to prevent information on data that is no longer in use from remaining stored in the database.
[0105] (Allocation cost calculation) 29 is a flowchart showing an example of the operation after the processing of the assigned cost determination operation has progressed to E. The operation of this flowchart is realized by the processor 201 of the assigned work determination device 2 reading and executing a program stored in the program memory 202.
[0106] The business rule classification unit 312 classifies the business rules into three rules based on the adjusted average adoption ratio (2901). The business rule classification unit 312 classifies each business rule into an absolute rule, a violation rule, or a permissible rule according to the calculated adjusted average adoption ratio of each business rule. An absolute rule is one whose adjusted average adoption ratio is 100%, which is the maximum value, a violation rule is one whose adjusted average adoption ratio is 0%, which is the minimum value, and a permissible rule is one whose adjusted average adoption ratio is greater than the minimum value and less than the maximum value. In the example of FIG. 23, business rule 1 whose adjusted average adoption ratio is 100% is classified as an absolute rule, business rule 2 whose average adoption ratio is 0% is classified as a violation rule, and business rule 3 whose average adoption ratio is greater than 0% and less than 100% is classified as a permissible rule. Then, the business rule classification unit 312 transmits various information including information on the classification result of the business rules, the number of business rules adopted, the business rules, and input information to the allocation cost determination unit 313.
[0107] Based on the received information, the allocation cost determination unit 313 judges whether the allocation cost value of each cell in the request allocation table can be calculated as follows (2902). First, the allocation cost determination unit 313 determines a business rule corresponding to each cell of the desired allocation table based on the allocation consideration information. FIG. 30 is a diagram showing an example of a method for determining a business rule corresponding to each cell of the desired allocation table. In the figure, (a) is an example of the desired allocation table, and (b) and (c) are diagrams in which a part of the human information and task information included in the allocation consideration information shown in (c) and (d) of FIG. 15 are respectively excerpted. The balloon shown for the desired allocation table in (a) shows a business rule in which the bit value is set for both the worker A and the work I in the allocation consideration information. The cells shown in the balloon, that is, the business rules corresponding to the allocation of the worker A to the work I are business rule 1: "Experienced" workers are assigned to the work of "work type 1" and business rule 3: "Experienced" workers are assigned to the work of "work type 3". The allocation cost determination unit 313 also determines which business rule applies to the other cells shown in (a) of FIG. 30.
[0108] Next, the allocation cost determination unit 313 determines the allocation cost value based on the business rule applied to each cell. FIG. 31 is a diagram showing three patterns of the allocation cost value determined when a worker allocates a task. For example, if all the corresponding business rules are absolute rules, the allocation cost value is 100 (pattern 1), and if there is even one violation rule, the allocation cost value is 0 (pattern 2). If all the corresponding business rules are permissive rules, or if permissive rules and absolute rules are mixed, the allocation cost value is any value greater than the minimum value and less than the maximum value (pattern 3). If the allocation cost value is any value greater than the minimum value and less than the maximum value, the allocation cost determination unit 313 cannot determine the allocation cost value because the allocation cost value is not determined to one value (note that this is indicated by "??" in FIG. 31).
[0109] When each cell is an absolute rule or a violation rule, the allocation cost determination unit 313 can determine the allocation cost value of each cell, and therefore determines in 2902 that the allocation cost value of each cell in the desired allocation table can be calculated, and the process proceeds to 2905. On the other hand, when one of the cells is only a permissible rule, or a permissible rule and an absolute rule, the allocation cost determination unit 313 determines that the allocation cost value of each cell in the desired allocation table cannot be calculated, and the process proceeds to 2903.
[0110] When the allocation cost determination unit 313 determines that it cannot calculate the allocation cost value of each cell of the desired allocation table, it transmits various information including the average adoption ratio of business rules in each cell to the weight value determination unit 314. The weight value determination unit 314 calculates (2903) a weight value k for the allocation cost value of a cell in the received desired allocation table where the corresponding business rule is only a permissible rule, or a permissible rule and an absolute rule.
[0111] Fig. 32 is a diagram showing an example of business rules and cost values when the only business rule that applies to a cell in the desired allocation table is an allowable rule. As shown in Fig. 32, when the number of business rules when allocating task I to worker A is two, the weight value determination unit 314 refers to the average adoption ratio of each business rule and calculates the weight value k for each business rule that is an allowable rule by the following formula. Weight value k for business rules = average adoption rate of business rules / (number of business rules in the corresponding cell * maximum value of average adoption rate) For example, when calculating the weight value of business rule 1 shown in FIG. 32, the corrected average adoption ratio is 41%, the number of applicable business rules is 2, and the maximum average adoption ratio in the applicable cell is 49%. By applying these values to the above formula, the weight value k1 for business rule 1 is 0.42. The weight value determination unit 314 also applies the above formula to the other business rules to determine the weight value for each business rule. For example, the weight value k2 for business rule 3 is calculated to be 0.5. Then, the weight value determination unit 314 transmits information about the determined weight value to the assigned cost determination unit 313.
[0112] The allocation cost determination unit 313 determines the allocation cost value based on the weight value (2904). The allocation cost determination unit 313 determines the allocation cost value by adding up the values of each k and multiplying the sum by 100 (a value for normalization). For example, the allocation cost value when assigning the above-mentioned work I to the worker A is 100*(k1+k2)=92, as shown in FIG.
[0113] Fig. 33 is a diagram showing an example of business rules and calculated allocation cost values when the business rules corresponding to a cell in the desired allocation table are a mixture of absolute rules and permissible rules. In the example shown in Fig. 33, business rule 1 is a permissible rule, while business rule 3 is an absolute rule. In this case, the weight value determination unit 314 calculates the weight value of the business rule that is a permissible rule in the same way as in the case where the business rule is only a permissible rule as described above. Then, the weight value determination unit 314 transmits the determined weight value to the allocation cost determination unit 313.
[0114] The allocation cost determination unit 313 determines the allocation cost value based on the received weight value (2904). First, the allocation cost determination unit 313 calculates the allocation cost value in the absolute rule as 100*number of absolute rules in the corresponding cell / total number of rules in the corresponding cell. In the example of FIG. 33, the number of absolute rules in the corresponding cell is 1, and the total number of rules in the corresponding cell is 2, so the allocation cost value in the absolute rule is 100 / 2. Next, the allocation cost determination unit 313 calculates the allocation cost value in the cell of the desired allocation table by adding 100 / 2, which is the allocation cost value in the absolute rule, and (100-100 / 2)*(k1), which is the allocation cost value based on the weight value. For example, if k1=0.42 as in FIG. 32, the allocation cost value is 71 as shown in FIG. 33.
[0115] The allocation cost determination unit 313 transmits information on the allocation cost value of each cell of the desired allocation table calculated based on the weight value in this manner to the allocation plan creation unit 315.
[0116] Furthermore, if the allocation cost determination unit 313 determines that the allocation cost value for each cell in the desired allocation table can be calculated, it calculates the allocation cost value and transmits information about the allocation cost value for each cell in the desired allocation table to the allocation plan creation unit 315.
[0117] 34 shows an example of the allocation cost value thus calculated by the allocation cost determination unit 313. The allocation cost determination unit 313 transmits information on the calculated allocation cost value to the allocation plan creation unit 315.
[0118] The allocation plan creating unit 315 creates an allocation plan based on the received allocation cost value (2905). The allocation plan creating unit 315 performs, for example, a solver calculation using the calculated allocation cost value. For example, the allocation plan creating unit 315 sets the total value of the allocation cost values as an objective function and calculates the optimal solution by finding the maximum value of the objective function. FIG. 35 is a diagram showing an example of an allocation plan calculated by a solver calculation. The allocation plan creating unit 315 transmits the calculated allocation plan to the output unit 305.
[0119] The output unit 305 displays the allocation plan to the allocator 1 on the display unit 208 (2906). The allocator 1 uses the displayed allocation plan to allocate tasks to each worker.
[0120] (Application example 1 of allocation cost calculation) The following describes application example 1 when calculating allocation costs. 36A and 36B are diagrams showing examples of human information and average adoption ratios of allocation consideration information when a policy is changed. In each diagram, (a) shows human information, and (b) shows the average adoption ratio. FIG. 36A shows a case where an attribute of human information is deleted, and FIG. 36B shows a case where an attribute of human information is added. When an attribute of human information is deleted as shown in FIG. 36A, the allocation cost determination unit 313 calculates the allocation cost value without considering the value of the average adoption ratio corresponding to the deleted attribute. Conversely, when an attribute of human information is added as shown in FIG. 36B, the allocation cost determination unit 313 calculates the allocation cost value using the corrected average adoption ratio described above.
[0121] (When a revised allocation table with accident data is entered) The following describes the processing of the allocation cost determination operation when the corrected allocation table includes accident data. When the corrected allocation table includes accident data, the allocation cost determination operation is the same as the various operations described with reference to Figures 13, 19, 24, and 29 except for the operation in the average adoption rate correction unit 309, so a description of this operation will be omitted. Also, since the operation of the average adoption rate correction unit 309 differs depending on whether or not the allocation cost determination device 21 has an allocation table in which an accident has occurred in the past, the following will be described separately for two cases.
[0122] (When the allocation cost determination device 21 does not store an allocation table in which an accident has occurred in the past) FIG. 37 is a diagram showing an example of correcting the average adoption ratio when there is no data on past accidents. FIG. 37(a) shows a corrected allocation table, FIG. 37(b) shows business rules corresponding to the tasks and workers in the corrected allocation table, and FIG. 37(c) shows an example of correction of the average adoption ratio due to an accident. In this example, a case where no accident has occurred in the past will be described. In other words, hereinafter, a case where the data memory 203 does not store an allocation table in which an accident has occurred in the past will be described. It is assumed that the accident occurred when worker C, enclosed in a square in FIG. 37(a), performed task II. Also, for simplicity, it is assumed that the allocation consideration information is the same as the allocation consideration preparation information.
[0123] The average adoption rate correction unit 309 recognizes that an accident occurred when worker C performed task II from the revised allocation table included in the input information. For example, the input information may include flag information indicating that an accident occurred at a corresponding location in the revised allocation table, and the average adoption rate correction unit 309 may recognize the accident by recognizing this flag. For example, the average adoption rate correction unit 309 recognizes that business rule 8 enclosed in a square in (b) of FIG. 37 is the business rule that corresponds to the accident. After that, the average adoption rate correction unit 309, having identified the flag, searches the data memory 203 and determines whether it has past accident data.
[0124] If it is determined that there is no past accident data, the average adoption rate correction unit 309 corrects the average adoption rate of the business rule corresponding to the worker and task in which the accident occurred to 0 when correcting the average adoption rate. In the example of (c) in Fig. 37, the average adoption rate correction unit 309 corrects the average adoption rate of the recognized business rule 8 from 30% to 0%.
[0125] (When the allocation cost determination device 21 stores an allocation table in which an accident has occurred in the past) FIG. 38 is a diagram showing an example of correcting the average adoption ratio when data on a past accident has been stored. FIG. 38 (a) shows a corrected allocation table, (b) shows business rules corresponding to the tasks and workers in the corrected allocation table, (c) shows accident data corresponding to each business rule, (d) shows an example of an asymptote when the accident occurrence probability and the average adoption ratio are divided into three clusters by cluster analysis, and (e) shows an example of correction of the average adoption ratio due to an accident. In this example, a case where an accident has occurred in the past will be described. That is, hereinafter, a case where an allocation table on which an accident has occurred in the past is stored in the data memory 203 will be described. The accident occurred when the worker C enclosed in the square in FIG. 38 (a) performed the task II. For simplification, the allocation consideration information is assumed to be the same as the allocation consideration preparation information.
[0126] The average adoption rate correction unit 309 recognizes that an accident occurred when worker C performed task II from the revised allocation table included in the input information. For example, the input information may include a flag indicating that an accident occurred at a corresponding location in the revised allocation table, and the average adoption rate correction unit 309 may recognize the accident by recognizing this flag. For example, the average adoption rate correction unit 309 recognizes that business rule 8 enclosed in a square in (b) of FIG. 38 is the business rule that corresponds to the accident. After that, the average adoption rate correction unit 309, having identified the flag, searches the data memory 203 and determines whether it has past accident data.
[0127] When it is determined that past accident data is available, the average adoption rate correction unit 309 calculates the past accident occurrence probability for each business rule by dividing the number of accidents that occurred in each business rule by the number of data in which accidents occurred in the past when correcting the average adoption rate. (c) of FIG. 38 is a diagram showing an example of the accident occurrence probability for each business rule. As shown in (c) of FIG. 38, the accident occurrence probability is 0% for business rule 1, 95% for business rule 2, 30% for business rule 3, . . . , 20% for business rule 8, and 50% for business rule 9. The average adoption rate correction unit 309 then performs cluster analysis on the past accident data, divides it into a predetermined number of clusters, and draws an asymptote at the center point of the cluster. For example, (d) of FIG. 38 shows an example of an asymptote when the accident occurrence probability and the average adoption rate are divided into three clusters by cluster analysis. Then, an allowable average adoption rate is set as a threshold value based on a set value (e.g., 30%) of the accident occurrence probability. The method of determining the set value will be described later. If the average adoption rate of the relevant business rule is equal to or greater than the threshold, the average adoption rate modification unit 309 does not modify the value of the average adoption rate, and if the average adoption rate of the relevant business rule is less than the threshold, the average adoption rate modification unit 309 modifies the average adoption rate of the relevant business rule to 0. Figure 38 (e) shows that if the average adoption rate of business rule 8 recognized as an accident is 80%, which is equal to or greater than the threshold (30%), the average adoption rate modification unit 309 does not modify the value of the average adoption rate, and if it is 25%, which is less than 30%, the average adoption rate modifies from 25% to 0%.
[0128] Figure 39 is a flowchart showing an example of the operation for setting an acceptable average adoption ratio. The operation of this flowchart is realized by the processor 201 of the assigned work determination device 2 reading and executing a program stored in the program memory 202. The acceptable average adoption ratio can be set before or during the correction of the average adoption ratio. Also, various data such as the date and time when the accident occurred, the combination of worker and work, and the human damage and facility damage caused by the accident are assumed to be stored in the data memory 203 by the allocator 1, etc.
[0129] The processor 201 sets the degree of likelihood of an accident (3901). The processor 201 calculates the frequency of accidents (times / 10 years) based on, for example, the number of tasks over 10 years multiplied by the past accident occurrence probability of the business rule corresponding to the combination of the worker and the task. In this example, the number of tasks over 10 years is used, but this is not limited thereto, and any period may be used as long as it is the number of tasks in a predetermined period. Then, the processor 201 sets the degree of likelihood of an accident depending on the frequency of accidents. The processor 201 may equally divide the frequency of accidents into a required number and set the degree of likelihood of an accident depending on the result of the equal division, or may set the degree of likelihood of an accident based on a predetermined setting value input by the assigner 1.
[0130] FIG. 40 is a diagram showing an example of setting the degree of likelihood of accidents according to the frequency of accident occurrence. As shown in FIG. 40, for example, when the frequency of accidents is less than once in 10 years, the processor 201 sets the degree of likelihood of accidents to the lowest value, "1". When the frequency of accidents is more than once in 10 years and less than once in 5 years, the processor 201 sets the degree of likelihood of accidents to "2", which is higher than "1". When the frequency of accidents is more than once in 5 years and less than three times a year, the processor 201 sets the degree of likelihood of accidents to "3", which is higher than "2". When the frequency of accidents is more than three times a year, the processor 201 sets the degree of likelihood of accidents to "4", which is the highest value.
[0131] The processor 201 sets the degree of impact of the accident (3902). The processor 201 sets the degree of impact of the accident according to the human damage and facility damage corresponding to the accident stored in the data memory 203. The processor 201 may equally divide the degree of impact of the accident into a required number of parts and set the degree of impact of the accident according to the result of the division, or may set the degree of impact based on a predetermined setting value input by the assigner 1.
[0132] FIG. 41 is a diagram showing an example of setting the impact level according to the human damage and the equipment damage. As shown in FIG. 41, for example, when the worker is not injured or there is no equipment damage, the lowest impact level is set to "1". Similarly, when the worker's injury is a minor injury such as a scratch or the equipment damage amount is less than 100 million yen, the impact level is set to "2" higher than "1". Furthermore, when the worker's injury is a serious injury such as a fracture or the equipment damage amount is 100 million yen or more but less than 300 million yen, the impact level is set to "3" higher than "2". Furthermore, when the worker dies or the equipment damage amount is 300 million yen or more, the impact level is set to the highest level "4". The processor 201 may be set to adopt the higher of the impact level of the human damage and the impact level of the equipment damage, or may be set to adopt the impact level of the human damage. Moreover, the human damage and the equipment damage shown in FIG. 41 are merely examples, and it goes without saying that any attribute related to the accident can be set.
[0133] The processor 201 sets an unacceptable range (3903). The processor 201 sets which range of the accident likelihood and impact levels set in 3901 and 3902 is unacceptable. Note that before this range is determined, an input of the unacceptable range is made by the allocator 1 or the like, and the data memory 203 stores the range set by the allocator 1. The processor 201 sets the degree and impact level that include the stored range as the unacceptable range.
[0134] FIG. 42 is a diagram showing an example of an unacceptable range of the degree of likelihood of an accident and the degree of impact. FIG. 42(a) is a diagram showing an unacceptable range of the degree of likelihood of an accident, and FIG. 42(b) is a diagram showing an unacceptable range of the degree of impact. As shown in FIG. 42(a) and (b), the unacceptable range is surrounded by a thick line. In the example of FIG. 42(a) and (b), the processor 201 sets the case where the degree of likelihood of an accident is 4 or the degree of impact is either 3 or 4 as the unacceptable range.
[0135] The processor 201 sets an acceptable average adoption rate (3904). The processor 201 searches the assignment tables where there have been accidents that fall within the unacceptable range set in 3903, and sets the highest average adoption rate among the business rules corresponding to the searched workers and tasks as the acceptable average adoption rate.
[0136] Fig. 43 is a diagram showing an example of which of the average adoption rates is set as an acceptable average adoption rate. In Fig. 43, for example, it is assumed that business rules 2 and 5 are business rules that are in an unacceptable range (encircled by a thick line in Fig. 43). The processor 201 determines that the average adoption rate of business rule 2 is 0% and that the average adoption rate of business rule 5 is 10%. Then, the processor 201 sets the average adoption rate of business rule 5 as an acceptable average adoption rate.
[0137] [Effects] The allocation cost determination device 21 can correct the average adoption ratio of each business rule by using the allocation table manually corrected by the allocator 1. The allocation cost determination device 21 can calculate the allocation cost value based on the average adoption ratio of each corrected business rule, thereby making it possible to allocate the allocation cost value to an appropriate worker.
[0138] Therefore, it is possible to create an appropriate allocation table that is in line with real-world problems. This allocation plan makes it possible to allocate appropriate tasks to workers.
[0139] [Other embodiments] It should be noted that the present invention is not limited to the above embodiment. For example, the personnel information and task information included in the allocation consideration information are not limited to those described above. For example, the personnel information may include various attributes related to workers, such as available for night shifts, available for weekends, good physical condition, work area, and other arbitrary attributes. Furthermore, the task information may include arbitrary tasks such as night shifts, weekends, and outside work. The personnel information and task information are not limited to those described here, and may include any information related to workers or work.
[0140] The method described in the above embodiment can be stored as a program (software means) that can be executed by a calculator (computer) in a storage medium such as a magnetic disk (floppy (registered trademark) disk, hard disk, etc.), optical disk (CD-ROM, DVD, MO, etc.), semiconductor memory (ROM, RAM, flash memory, etc.), and can also be distributed by transmitting it via a communication medium. The program stored on the medium side also includes a setting program that configures the software means (including not only execution programs but also tables and data structures) that the calculator executes in the computer. The computer that realizes this device reads the program stored in the storage medium, and in some cases, configures the software means by the setting program, and executes the above-mentioned processing by controlling the operation of the software means. The storage medium referred to in this specification is not limited to a storage medium for distribution, but also includes a storage medium such as a magnetic disk or semiconductor memory provided inside the computer or in a device connected via a network.
[0141] In short, this invention is not limited to the above-mentioned embodiment, and various modifications can be made in the implementation stage without departing from the gist of the invention. Moreover, each embodiment may be implemented in combination as appropriate as possible, in which case the combined effect can be obtained. Furthermore, the above-mentioned embodiment includes inventions at various stages, and various inventions can be extracted by appropriate combinations of the disclosed constituent elements. [Explanation of symbols]
[0142] 1...Assigner 2...Work allocation determination device 21... Allocation cost determination device 201…Processor 202…Program memory 203…Data memory 204...Communication interface 205... Input / Output Interface 206…Bus 207...Input section 208...Display section 301…Acquisition Department 302…Business Rules Creation Department 303…Business Rule Analysis Department 304…Average Recruitment Ratio Generation Section 305...Output section 306...Allocation consideration information determination unit 307…Business rule detection unit 308…Business Rules Sorting Department 309…Average Recruitment Rate Correction Section 310…Business rule addition section 311…Recruitment Rate Calculation Department 312…Business rule classification section 313... Allocation cost determination unit 314... Weight value determination unit 315…Allocation Proposal Preparation Division
Claims
1. an acquisition unit that receives input information including: input preparation information including a past allocation table indicating which tasks each of a plurality of workers performed; allocation time consideration preparation information including human information indicating the situation or state of each of the workers and task information indicating the tasks related to the tasks; a pre-correction allocation table and a revised allocation table indicating the assigned tasks of each of the workers before and after correction by an allocator; and a desired allocation table indicating the target workers and target tasks to be assigned this time among the workers and tasks; a rule creation unit that creates business rules by combining each attribute of the human information and each task of the task information; a ratio generating unit that generates an average adoption ratio indicating the ratio of the adoption of each of the business rules in the past allocation table; a sorting unit which compares the pre-modification allocation table with the revised allocation table, and sorts the work into an unmodified work rule corresponding to a case where a task assigned to the target worker in the pre-modification allocation table is the same as a task assigned in the revised allocation table, a pre-modification work rule corresponding to a case where a task is assigned to the worker in the pre-modification allocation table but not assigned in the revised allocation table, and a revised work rule corresponding to a case where a task is not assigned to the worker in the pre-modification allocation table but is assigned in the revised allocation table; a ratio modification unit that reduces the average adoption ratio of the business rule corresponding to the pre-modification business rule and modifies the average adoption ratios of the business rules corresponding to the unmodified business rule and the modified business rule so as to be the same or increased; an allocation cost determination unit that calculates an allocation cost value for allocating the target worker to the target task based on the revised average hiring ratio; An allocation cost determination device comprising:
2. The acquisition unit further receives allocation consideration information including human information and task information that are the same as or different from the allocation consideration preparation information, and a number of normally available tasks that represents the number of tasks that the target worker can handle during the desired time indicated in the desired allocation table, The allocation cost determination device of claim 1, further comprising a determination unit that determines the data classification to which the input information belongs by comparing the attributes of the human information and the tasks of the task information of the allocation consideration information with the attributes of the human information and the tasks of the task information of the allocation consideration preparation information.
3. when it is determined that an attribute of the person information or a task of the task information of the assignment consideration information has been changed or increased, the determination unit determines that the data classification of the input information is a data group at the time of a policy change; The allocation cost determination device according to claim 2, further comprising a rule addition unit that adds to the average adoption ratio a new business rule corresponding to the attributes of the human information of the allocation consideration information or the tasks of the task information that have been determined to have been changed or increased.
4. 4. The allocation cost determination device according to claim 3, wherein the ratio modification unit modifies the average adoption ratio of the newly added business rule depending on whether the newly added business rule corresponds to the unmodified business rule, the pre-modification business rule, or the post-modification business rule.
5. When it is determined that the attributes of the human information of the assignment consideration information or the tasks of the task information are the same, the determination unit determines that the data classification of the input information is a normal data group; The acquisition unit receives the input information a plurality of times, The allocation cost determination device of claim 3 or 4, wherein when the determination unit determines that there is more input information that is determined to be a data group at the time of the policy change than that is determined to be a data group at the normal time, the allocation cost determination device replaces the allocation consideration preparation information with the allocation consideration information.
6. The input information further includes a flag indicating that an accident has occurred in any of the combinations in the revised allocation table, 6. The allocation cost determination device according to claim 1, wherein the ratio modification unit sets the average adoption ratio of a business rule corresponding to a combination of a worker and an operation indicated by the flag to 0, or, if the average adoption ratio of the corresponding business rule is smaller than a predetermined threshold, sets the average adoption ratio of the corresponding business rule to 0, and if the average adoption ratio of the corresponding business rule is larger than the predetermined threshold, does not modify the average adoption ratio of the corresponding business rule.
7. An allocation cost determination method executed by a processor of an allocation cost determination device, comprising: receiving input preparation information including a past allocation table indicating which tasks each of a plurality of workers performed, and allocation preparation information including human information indicating the situation or state of each of the workers and task information indicating the tasks related to the tasks, as well as input information including a pre-correction allocation table and a corrected allocation table indicating the assigned tasks of each of the workers before and after correction by an allocator, and a desired allocation table indicating the target workers and target tasks to be assigned this time among the workers and tasks; creating a business rule by combining each attribute of the personnel information and each task of the task information; generating an average adoption ratio indicating the ratio of how much each of the business rules was adopted in the past allocation table; comparing the pre-modification allocation table with the revised allocation table, and classifying the work into an unmodified work rule corresponding to a case where a task assigned to the target worker in the pre-modification allocation table is the same as a task assigned in the revised allocation table, a pre-modification work rule corresponding to a case where a task is assigned to the worker in the pre-modification allocation table but not assigned in the revised allocation table, and a revised work rule corresponding to a case where a task is not assigned to the worker in the pre-modification allocation table but is assigned in the revised allocation table; decreasing the average adoption ratio of the business rule corresponding to the pre-modification business rule, and modifying the business rule so as to maintain the same or increase the average adoption ratio of the business rule corresponding to the unmodified business rule and the modified business rule; Calculating an allocation cost value for allocating the target worker to the target task based on the revised average hiring ratio; The allocation cost determination method comprises:
8. An allocation cost determination program that causes a processor to function as each of the units of the allocation cost determination device according to any one of claims 1 to 6.
Citation Information
Patent Citations
Method and apparatus for allocating work process
JP2006171824A
Person in charge allocation support device, person in charge allocation support method, and program
JP2013045414A
System and method for automatically assigning worker
JP2014191390A
Scheduling method, scheduling device and scheduling program
JP2017211921A
