Team task management device, team task management method, and program

Abstract

The present invention makes tasks included in a schedule for each worker A, B, C and changes in concentration levels to be learned, and makes it possible to predict the change in concentration level due to task assignment. Then, the work efficiency of important joint work (collaborative task) Th is improved by scheduling a task Tu, which improves concentration levels, immediately before the important joint work (collaborative task) Th so as to align the timings at which all team members' concentration levels are ensured.

Description

Team task management device, team task management method and program

[0001] An embodiment of the present invention relates to a team task management device, a team task management method, and a program that perform task scheduling according to the concentration levels of team members so as to improve the productivity of the entire team in team activities.

[0002] Conventionally, there have been proposed mood change support devices, mood change support methods, and mood change support programs that aim to appropriately restore the concentration required for work without interfering with work (see, for example, Patent Document 1).

[0003] The mood change support device performs the following processes: - Measures the change in the worker's workload over time. - From the measured change in workload over time, predicts times when attention is needed for work, and sets a mood change time to finish before that time. - At the set time, notifies the worker of the details of the mood change (stretching, mindfulness, etc.). - By following the instructions in the displayed video, the worker can appropriately recover the concentration needed for work. - The worker wears a wearable device, allowing them to prioritize recovery actions that are most effective in recovering concentration.

[0004] Japanese Patent Application Publication No. 2018-159979

[0005] Conventional mood-change support devices encourage workers to take a break by avoiding peak work hours so as not to disrupt work, and work to maintain and restore workers' concentration. However, in tasks that require teamwork, maintaining and restoring individual worker concentration alone cannot improve productivity across the organization. Therefore, when performing tasks that require collaboration, it is necessary to consider the time transitions in the concentration levels of all team members.

[0006] The present invention has been made in light of these problems, and aims to provide a team task management device, a team task management method, and a program that can synchronize the time to ensure concentration among all team members, thereby improving productivity by generating synergistic effects and increasing work efficiency.

[0007] A team task management device according to an embodiment of the present invention is equipped with a control unit that executes the following process: predicts the time progression of concentration levels corresponding to a schedule for each of a plurality of workers that includes collaborative tasks performed by the plurality of workers, based on a prediction model for each of the plurality of workers for predicting the time progression of concentration levels corresponding to a schedule including a plurality of tasks; and if the concentration level corresponding to the collaborative task among the predicted time progressions of concentration levels is less than a predetermined concentration level, modifies the schedule for tasks other than the collaborative task included in the schedule so that the concentration level corresponding to the collaborative task is equal to or greater than the predetermined concentration level.

[0008] The team task management device according to the embodiment of the present invention ensures that team members are able to concentrate at times when a particularly high level of cooperation is required, such as when team members are participating in important meetings or collaborative work. This can improve productivity by, for example, generating synergistic effects through lively discussions and the creation of various ideas, or by increasing the speed of work.

[0009] FIG. 1 is a block diagram showing an example of the configuration of a team task management system 1 relating to a team task management device, a team task management method, and a program according to an embodiment. FIG. 2 is a diagram outlining the prediction of concentration levels by pre-learning performed in the team task management system 1 and the ensuring of team members' concentration levels for collaborative tasks. FIG. 3 is a diagram illustrating an image of a specific example of the ensuring of team members' concentration levels for collaborative tasks performed in the team task management system 1. FIG. 4 is a functional block diagram showing an example of the main functional configuration of the team task management system 1. FIG. 5 is a block diagram showing the hardware configuration of a team task management server 10 in the team task management system 1. FIG. 6 is a flowchart showing an example of processing operations corresponding to the concentration model pre-learning function (step SP) performed by the team task management server 10. FIG. 7 is a flowchart showing an example of processing operations corresponding to the concentration level ensuring scheduling function (step ST) performed by the team task management server 10. FIG. 8 is a flowchart showing an example of processing operations corresponding to the schedule change function (step TR) performed by the team task management server 10. FIG. 9 is a flowchart showing an example of processing operations corresponding to the schedule change function (step RX) due to task exchange / addition performed by the team task management server 10. FIG. 10 is a diagram showing a specific example of schedule information (table) Tsc acquired as training data in the concentration model pre-learning process (SP) of the team task management server 10. FIG. 11 is a diagram showing a specific example of information targeted in the collaborative task characteristic / importance input process and schedule acquisition process in the scheduling process (ST) of the team task management server 10. FIG. 12 is a diagram showing a specific example of information targeted in the importance reference / member priority processing order setting process in the scheduling process (ST) of the team task management server 10. FIG. 13 is a diagram showing a specific example of information targeted in the scheduling start process, concentration level prediction, and collaborative task concentration level acquisition process in the scheduling process (ST) of the team task management server 10. FIG. 14 is a diagram showing a specific example of information targeted in the concentration level determination process in the scheduling process (ST) of the team task management server 10.FIG. 15 is a diagram showing a specific example of information targeted in the task replacement total pattern calculation process and the personal schedule pattern search process in the schedule change process (TR) of the team task management server 10. FIG. 16 is a diagram showing a specific example of information targeted in the concentration level determination process in the schedule change process (TR) of the team task management server 10. FIG. 17 is a diagram showing a specific example of information targeted in the task allocation list reading and addable task extraction processes in the task exchange / additional schedule change process (RX) of the team task management server 10. FIG. 18 is a diagram explaining a specific example (part 1) of task exchange taking into account priority level i in the task exchange / additional schedule change process (RX) of the team task management server 10. FIG. 19 is a diagram explaining a specific example (part 2) of task exchange taking into account priority level i in the task exchange / additional schedule change process (RX) of the team task management server 10. FIG. 20 is a diagram explaining a specific example (part 3) of task exchange taking into account priority level i in the task exchange / additional schedule change process (RX) of the team task management server 10. Fig. 21 is a diagram showing a specific example of information that is the target of the personal schedule pattern search and schedule output process in the task exchange and additional schedule change process (RX) of the team task management server 10. Fig. 22 is a diagram showing a specific example of information that is the target of the concentration level determination process in the task exchange and additional schedule change process (RX) of the team task management server 10.

[0010] Hereinafter, a team task management device, a team task management method, and a program according to an embodiment will be described with reference to the drawings.

[0011] (Overall Configuration of the Embodiment) FIG. 1 is a block diagram showing an example of the configuration of a team task management system 1 relating to a team task management device, a team task management method, and a program according to an embodiment.

[0012] The team task management system 1 comprises a team task management server 10 (team task management device), and a plurality of worker terminals 20 and an administrator terminal 30 that are communicatively connected to the team task management server 10 via a communication network N such as a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet.

[0013] The worker terminal 20 is a terminal of a worker who performs a task (work), and is, for example, a terminal operated by each team member (all workers who share a task) who performs various collaborative tasks (tasks that require cooperation within the team) that occur from time to time.

[0014] The manager terminal 30 is a terminal operated by a manager who manages tasks and teams.

[0015] The plurality of worker terminals 20 and the manager terminal 30 are each configured as a personal computer (PC), a tablet terminal, a smartphone, a personal digital assistant (PDA), or the like.

[0016] A concentration measurement device Ec such as a wearable device or sensor is connected to the worker terminal 20 to measure the worker's concentration level (a value indicating how concentrated the worker is) when performing a task, and data on the measured concentration level is obtained.

[0017] The team task management server 10 has main functions consisting of the following steps (1) to (3): (1) Concentration model pre-learning function: A function that models the concentration of a worker using machine learning processing and makes it possible to predict the concentration of the worker on a task (step SP). (2) Learning result DB saving function: A function that saves (stores) the concentration prediction model generated as a result of learning in a DB (database) (step SQ). (3) Concentration ensuring scheduling function: A function that uses the concentration prediction model built by pre-learning to schedule team members so that they can ensure (achieve) a higher concentration level than the requested level for the collaborative task that has arisen (step ST).

[0018] The team task management system 1 configured as above can learn the tasks and fluctuations in concentration level for each worker and predict fluctuations in concentration level due to task allocation. Then, by scheduling a task that improves concentration level immediately before an important collaborative work (collaborative task), it becomes possible to improve the work efficiency of the important collaborative work (collaborative task) by aligning the timing to ensure the concentration levels of all team members.

[0019] (Outline of the embodiment) In the embodiment, it is predicted that the concentration level of a worker is controlled by the amount of cognitive load of the task imposed on the worker.

[0020] FIG. 2 is a diagram illustrating an overview of the prediction of concentration levels through pre-learning performed in the team task management system 1 and ensuring team members' concentration levels for collaborative tasks. Prediction of concentration levels through pre-learning (see FIG. 2(A)) Data is collected using the task characteristics (start and end times of work / task type: specific task overview (e.g., replying to emails, creating documents)) assigned to each worker A and the importance of the task as explanatory variables (data required to predict the concentration level entered during pre-learning). The worker inputs the importance of each task from the worker terminal 20. The importance of a task is a number from 1 to 10 indicating how important each task is, with the number increasing as the importance increases. The worker inputs the importance level when a new task occurs.

[0021] The concentration level of each worker during work is obtained from a concentration measurement device Ec such as a wearable sensor, and data is collected using the time progression of the obtained concentration level as the objective variable (an object to be made predictable as a result of pre-learning, which in this embodiment refers to concentration level). The relationship between the task characteristics assigned to each worker and concentration level is learned and modeled, and a prediction model of each worker's concentration level is generated. Modeling continues until concentration level can be predicted from the task characteristics. Based on the prediction model of each worker's concentration level, the time progression of concentration level corresponding to each worker A's original schedule Asc1 is predicted (concentration level prediction). Note that a schedule is a list of tasks arranged in the order in which events are planned to occur.

[0022] - Ensuring team members' concentration on collaborative tasks (see Figure 2 (B)) When there is a collaborative task that requires cooperation with team members, the manager inputs the reference values ​​for importance and concentration from the manager terminal 30, and schedules each worker A using the predictive model generated by learning so that the team members' concentration exceeds the reference values.

[0023] Figure 2 (B) shows schedule Asc2 for worker A, which is scheduled based on the predicted time progression of concentration corresponding to worker A's original schedule Asc1 (see Figure 2 (A)), by replacing the task ``Document creation'', which will increase worker A's concentration, with the task ``Idea generation'', which is located immediately before the collaborative task ``Important meeting'', as shown by arrow a, so that worker A's concentration in the collaborative task ``Important meeting'' will increase, as shown by arrow b.

[0024] FIG. 3 is a diagram showing an image of a specific example of ensuring the concentration of team members on a collaborative task performed in the team task management system 1.

[0025] As shown in Figure 3A, the time transition of the concentration level corresponding to the initial schedule of each of team members A, B, and C for the collaborative task (the lower part of Figure 3A shows the initial schedule Asc1 of worker A) is predicted based on the concentration prediction model for each of workers A, B, and C. In worker A's initial schedule Asc1, "document creation" is predicted to be a task Tu for which the concentration level will increase. Similarly, for workers B and C, tasks Tu for which the concentration level will increase and tasks Td for which the concentration level will decrease are predicted in each schedule.

[0026] As shown in Figure 3(B), when a collaborative task that requires a high level of concentration (for example, "an important meeting from 16:00") is scheduled, manager M inputs the task characteristics of the collaborative task that has occurred from manager terminal 30 and sets them in team task management system 1. Based on tasks Tu that will increase the level of concentration for each worker and tasks Td that will decrease the level of concentration predicted in each worker's original schedule, team task management system 1 performs scheduling that incorporates the collaborative task, as shown in Figure 3(C).

[0027] In the case of worker A, task Tu1, which was predicted to have a high level of concentration, is swapped with the task immediately preceding the collaborative task Th, "important meeting from 4:00 PM," "idea generation from 3:00 PM," as indicated by arrow a1, and the schedule is changed to schedule Asc2, which increases the level of concentration on the collaborative task Th, as indicated by arrow b1. In the case of worker B, for example, task Td2, which was predicted to have a relatively high level of concentration at the start of the original schedule, is swapped with the task immediately preceding the collaborative task Th, as indicated by arrow a2, and the schedule is changed to preserve the relatively high level of concentration (Tu2), as indicated by arrow b2. In the case of worker C, for example, as shown by arrow a3, task Tu3, which is predicted to have a higher concentration level, is added to the task preceding collaborative task "important meeting" Th, which is predicted to have a relatively low concentration level, and the schedule is changed to increase the concentration level on collaborative task "important meeting" Th, as shown by arrow b3.

[0028] As a result, when a cooperative task Th occurs, the original schedules of team members A, B, and C can be changed to schedules that increase the concentration of all team members when executing the cooperative task Th.

[0029] (System Configuration of the Embodiment) FIG. 4 is a functional block diagram showing an example of the main functional configuration of the team task management system 1. As shown in FIG.

[0030] The team task management server 10 includes a schedule acquisition function unit 11, an assigned task DB 11M, a scheduling assigned task DB 11ML, a concentration level learning function unit 14, a teacher data DB 14M1, an accuracy determination threshold DB 14M2, a learning model DB 14M3, a scheduling function unit 16, a current day processing task DB 16M1, and a member DB 16M2. The worker terminal 20 includes a worker concentration level acquisition function unit 13 and a concentration level measurement device (wearable device, sensor, etc.) Ec. The administrator terminal 30 includes an administrator input function unit 15.

[0031] The schedule acquisition function unit 11 acquires task characteristics, including task start and end times and task types, included in the schedule assigned to each worker A, who is a team member, from the assigned task DB 11M. The worker importance input function unit 12 allows the worker A to input the importance of the assigned task. The worker concentration acquisition function unit 13 uses a wearable device, sensor, or other concentration measurement device Ec to measure the concentration of worker A when performing tasks corresponding to, for example, the daily schedule, and acquires data.

[0032] The teacher data DB 14M1 stores data acquired at a higher level (including task characteristics, importance, and concentration level), along with worker IDs and dates. The concentration level learning function unit 14 uses the data stored in the teacher data DB 14M1 to learn the relationship between the tasks corresponding to each worker's schedule and their concentration levels. The accuracy of the learned model is verified and determined by referencing a threshold value for determining the error between the correct answer data and predicted data, which is stored in the accuracy determination threshold DB 14M2. The learning model DB 14M3 stores a prediction model of each worker A's concentration level generated as a result of learning (associated with the worker ID and date).

[0033] The scheduling assignment task DB 11ML stores newly assigned tasks after learning in the form of a task allocation list (a list listing the tasks to be done within the team and the members who can allocate each task). When a collaborative task is assigned, the manager M inputs the importance of the collaborative task and the minimum required concentration level (the minimum required concentration level Cr for starting a collaborative task), and the manager input function unit 15 acquires this data.

[0034] The current day processing task DB 16M1 stores data input and acquired at a higher level (including task characteristics and their importance included in the schedule assigned to each worker A, the importance of collaborative tasks and the minimum required concentration level Cr, and a task allocation list). The member DB 16M2 stores the upper limit number of tasks (upper limit task number r) that team members and each worker A can complete in one day. The scheduling function unit 16 uses the data stored in the current day processing task DB 16M1 and a prediction model of each worker A's concentration level stored in the learning model DB 14M3 to generate an optimal schedule from the tasks assigned to each worker ID of the team members so that each worker A's concentration level on the collaborative task (predicted concentration level C at the start of the collaborative task) is equal to or greater than the minimum required concentration level Cr, and presents this schedule to each worker A.

[0035] FIG. 5 is a block diagram showing the hardware configuration of the team task management server 10 in the team task management system 1. As shown in FIG.

[0036] As shown in FIG. 5, the team task management server 10 includes a control circuit (processor) 41 which is a control unit.

[0037] The control circuit 41 is connected via a system and data bus to a memory 42 such as a flash ROM, a hard disk drive 43 including a storage medium 43a such as a magnetic disk, a user interface 44 including keys, switches, external input terminals for user operation from the outside, and a display, speaker, printer, and external output terminals for outputting data, a wired communication module 45 and / or a wireless communication module 46 for communicating with the outside, and the like.

[0038] The worker terminal 20 and the manager terminal 30 may be connected to the team task management server 10 via a communication network N (see FIG. 1), for example, via a wired communication module 45 and / or a wireless communication module 46 .

[0039] The control circuit 41 controls the operation of each part of the team task management server 10 in accordance with a control program that controls the processing of the team task management server 10 and is stored in a control program area 42a of the memory 42, and based on management information that is stored in or read from a management information area 42b of the memory 42. The control circuit (processor) 41 is not limited to one processor, and may include multiple processors.

[0040] The control program stored in the control program area 42a of the team task management server 10 includes functions corresponding to the processes performed by the schedule acquisition function unit 11, worker importance input function unit 12, worker concentration level acquisition function unit 13, concentration level learning function unit 14, administrator input function unit 15, and scheduling function unit 16 described with reference to Figure 4.

[0041] In addition, the management information area 42b of the team task management server 10 also functions as a database (DB) corresponding to the assigned task DB11M, teacher data DB14M1, accuracy judgment threshold DB14M2, learning model DB14M3, scheduling assigned task DB11ML, current day processing task DB16M1, and member DB16M2 described with reference to Figure 4, and stores or reads out data that is input, acquired, generated, updated, output, etc. in accordance with each process performed by the schedule acquisition function unit 11, worker importance input function unit 12, worker concentration level acquisition function unit 13, concentration level learning function unit 14, administrator input function unit 15, and scheduling function unit 16.

[0042] The worker terminal 20 and the manager terminal 30 are configured with the same hardware as the team task management server 10. Functions corresponding to the processes performed by the worker importance input function unit 12 and the worker concentration level acquisition function unit 13 may be executed in cooperation with a control unit (processor) of the worker terminal 20. Furthermore, functions corresponding to the processes performed by the manager input function unit 15 may be executed in cooperation with a control unit (processor) of the manager terminal 30.

[0043] In the team task management system 1 configured in this manner, the control circuits (control units) of the team task management server 10, worker terminal 20, and manager terminal 30 control the operation of each unit in accordance with the commands written in the control program, and the software and hardware work together to realize various functions as described in the operation explanation below.

[0044] (Operation of the embodiment) Next, the operation of the team task management system 1 of the embodiment will be described.

[0045] FIG. 6 is a flowchart showing an example of a processing operation corresponding to the concentration model advance learning function (step SP) performed by the team task management server 10.

[0046] In the concentration model pre-learning process (SP), prediction models for Nm team members are generated. This is repeated every day until accuracy below the error judgment threshold is ensured (steps Ps to Pe).

[0047] <Collection of explanatory variables> Acquire teacher data for explanatory variables of pre-learning. In step P1, the schedule acquisition function unit 11 acquires the schedule (task characteristics, importance) for each worker from the assigned task DB 11M. It is assumed that the worker has input the importance into their daily schedule using the worker importance input function unit 12.

[0048] <Collection of objective variables> - Acquire training data for objective variables from pre-learning. In step P2, the worker concentration level acquisition function unit 13 acquires the worker's concentration level when performing the task. The concentration level is measured using data measured by a concentration level measurement device Ec, such as a wearable device worn by the worker. The average concentration level during the work time is calculated, and this value is used as the objective variable.

[0049] In step P3, the data collected in steps P1 and P2 is stored in the teacher data DB 14M1.

[0050] <Data Processing> In step P4, the concentration learning function unit 14 performs data preprocessing on the data stored in the teacher data DB 14M1 so that the data can be used for learning. In step P5, the concentration learning function unit 14 divides the data into training and evaluation data to determine the accuracy of machine learning.

[0051] <Machine Learning> In step P6, the concentration learning function unit 14 performs machine learning processing using the training data preprocessed and divided in steps P4 and P5, and learns the relationship between task characteristics and the time transition of the worker's concentration.

[0052] In step P7, the concentration learning function unit 14 evaluates the concentration prediction using the evaluation data, and in step P8, if the error is less than a threshold, it determines that learning is complete. The accuracy assurance determination method for evaluating the concentration prediction calculates the difference between the correct data and the predicted data, and if the difference is less than a threshold set in the accuracy determination threshold DB14M2, it determines that prediction accuracy has been ensured.

[0053] <Data Storage and Verification> In step SQ, the concentration prediction model, which is a learning model for Nm team members, is stored in the learning model DB 14M3 in association with the worker ID, and the concentration model pre-learning process (SP) is terminated.

[0054] FIG. 7 is a flowchart showing an example of a processing operation corresponding to the concentration ensuring scheduling function (step ST) performed by the team task management server 10.

[0055] <Before Scheduling Execution> In step T1, if there is a collaborative task for that day, the administrator input function unit 15 inputs the task characteristics (start and end times, task type) and the minimum required concentration level Cr of the collaborative task input by the administrator. In step T2, the administrator input function unit 15 inputs the importance of the collaborative task input by the administrator.

[0056] A process of acquiring schedules for all members (Nm in number) of the team to be scheduled is performed (steps Ts1 to Te1). In step T3, the schedule acquisition function unit 11 reads the schedules of all Nm team members, and in step T4, acquires the minimum concentration level Cr required for the collaborative task entered in step T1. In step T5, the worker importance input function unit 12 inputs the importance of the collaborative task entered by all team members. In step T6, the worker importance input function unit 12 acquires a list of the importance levels entered by the manager and each member (worker).

[0057] In step T7, the scheduling function unit 16 refers to the list of importance acquired in step T6, and in step T8, sets a priority level i for the scheduling process. The priority level i is set by referring to the importance levels in the list and determining the priority level i for the schedule of each worker to be scheduled using a method selected by the manager, such as using only the importance level entered by the manager or the sum of the importance levels entered by the worker and the manager. That is, in the process from the start of scheduling to the end of scheduling (steps Ts2 to Te2) described below, a scheduling loop is executed using the priority level i as an iterator.

[0058] <Creating a Schedule Based on Concentration Degree Prediction> In steps Ts2 to Te2, the scheduling function unit 16 starts scheduling for each worker of all members Nm of a team having a collaborative task in the order of priority i.

[0059] In step T9, the scheduling function unit 16 refers to the schedule of the i-th worker, and in step T10, predicts the trend in the concentration level of the corresponding worker on that day using a concentration level prediction model, which is a learning model stored in the learning model DB14M3.

[0060] In step T11, the scheduling function unit 16 obtains the concentration level C at the time when the collaborative task is to be performed from the transition of the concentration level predicted in accordance with the schedule of the i-th worker.

[0061] In step T12, the scheduling function unit 16 compares the minimum required concentration level Cr with the predicted concentration level C to determine whether to change the schedule. If the predicted concentration level C is equal to or greater than the minimum required concentration level Cr (C≧Cr) (step T12 (Yes)), the scheduling function unit 16 retains and outputs the original schedule of the corresponding worker in steps T13 and T14. This confirms that the original schedule including the collaborative task of the worker currently being scheduled is a schedule in which the predicted concentration level C of the collaborative task is equal to or greater than the minimum required concentration level Cr.

[0062] On the other hand, if the predicted concentration level C is less than the minimum required concentration level Cr (C<Cr) (step T12 (No)), the scheduling function unit 16 proceeds to step TR (first change process) and executes a schedule change process on the original schedule of the corresponding worker. That is, the schedule is changed so as to ensure the concentration level of each worker who is a team member.

[0063] <Schedule Change> FIG. 8 is a flowchart showing an example of a processing operation corresponding to the schedule change function (step TR) performed by the team task management server 10. As shown in FIG.

[0064] In the schedule change process (TR) (first change process), each worker is scheduled so that the number of workers whose predicted concentration level C corresponding to the collaborative task is equal to or greater than the minimum required concentration level Cr (C≧Cr) is maximized.

[0065] In step R1, the scheduling function unit 16 swaps tasks in the schedule of the worker who is the target of the scheduling process. That is, assuming that the number of tasks that can be swapped in a time slot in the schedule of the worker for the day being scheduled is Nt, all Nt! schedule patterns with swapped tasks are output and saved.

[0066] In steps Rs to Re (searching for individual schedule patterns), the scheduling function unit 16 loops through all Nt! schedule patterns with task swaps for each pattern, predicts the time progression of concentration using a concentration prediction model, which is a learning model for the corresponding worker (step R2), and obtains the concentration level C at the time when the collaborative task is performed (step R3).

[0067] In step R4, if there is a schedule pattern in which the concentration level C of the collaborative task acquired in step R3 is equal to or greater than the minimum required concentration level Cr (C≧Cr) (step R4 (Yes)), the scheduling function unit 16 ends the loop and outputs the schedule (step T14). Here, because performing calculations for all patterns would result in a time loss, the loop ends if the predicted concentration level C is equal to or greater than the reference concentration level Cr.

[0068] As a result, if the predicted concentration level C of the collaborative task in the initial schedule including the collaborative task of the workers during the scheduling process is less than the minimum required concentration level Cr, the schedule can be changed to a pattern of schedules among all patterns of schedules in which the time slot can be interchanged, in which the concentration level C of the collaborative task is equal to or greater than the minimum required concentration level Cr.

[0069] On the other hand, if there is no schedule pattern in which the concentration level C of the acquired collaborative task is equal to or greater than the minimum required concentration level Cr (C≧Cr) (step R4 (No)), that is, if the concentration level C of the collaborative task does not become equal to or greater than the reference value Cr simply by rearranging the tasks in the schedule of the worker currently processing, in step R5, the scheduling function unit 16 saves all calculation results (schedules of all patterns and their predicted concentration levels C of the collaborative tasks) after the loop ends, and executes schedule change processing by exchanging and adding tasks (step RX) (second change processing).

[0070] In the schedule change process (RX) (second change process) due to task exchange / addition, a schedule change process is carried out by exchanging / adding a task included in the schedule of a team member worker (see FIG. 9).

[0071] The process of saving all schedule patterns and the predicted concentration level C of the collaborative task, which is performed in step R5 of the schedule change process (TR), is necessary in the schedule change process (RX) by task exchange / addition in order to output a schedule pattern in which the concentration level C of the collaborative task is maximized if the concentration level C does not exceed the reference value after the task exchange process with a task included in the schedule of a team member worker.

[0072] FIG. 9 is a flowchart showing an example of a processing operation corresponding to the schedule change function (step RX) by task exchange / addition performed by the team task management server 10.

[0073] In step X1, the scheduling function unit 16 reads a task allocation list (a list of tasks to be performed within a team (including the execution date) and members who can allocate each task) from the current day processing task DB 16M1.

[0074] In steps Xs1 to Xe1 (extraction of addable tasks), the scheduling function unit 16 extracts tasks that can be exchanged with or added to the schedule of the worker currently undergoing scheduling processing, based on the tasks shared with team members in the loaded task allocation list, the number of times corresponding to the number of tasks Ts (scheduled tasks) in the task allocation list.

[0075] First, in steps X2 and X3, the scheduling function unit 16 determines whether each task in the task allocation list can be assigned to the worker currently processing the task (yourself) and whether the task will be performed on the day (today).

[0076] Next, in steps X4 and X5, the scheduling function unit 16 refers to the priority i of the worker who will perform the scheduling set in step T8 of FIG. 7 for the task that was determined in steps X2 and X3 to be allocable to the worker currently processing the task and to be performed on the same day, and determines whether the scheduling priority i of the worker who was scheduled to perform the task is lower than the priority i of the worker currently processing the task (whether it is a task of the (i+1)th to Nmth worker).

[0077] Then, in step X6, the scheduling function unit 16 adds to the list of tasks that can be added those that are to be carried out on the day and that can be executed by the worker currently processing, among the tasks of members (workers) whose priority i of the scheduling process obtained through steps X2 to X5 is lower than that of the worker currently processing.

[0078] Here, tasks scheduled to be performed by members (workers) with a lower priority i than the worker currently processing the task are extracted as tasks to be added to the schedule of the worker currently processing the task, and the schedule is changed.Therefore, even if the concentration level C corresponding to the collaborative task in the schedule of the member (worker) who was scheduled to perform the extracted task is equal to or greater than the minimum required concentration level Cr (C≧Cr), the extracted task will be subject to the scheduling process (steps Ts2 to Te2).

[0079] In step X7, the scheduling function unit 16 determines whether the tasks in the addable task list generated in steps Xs1 to Xe1 are empty, that is, whether there are any tasks that can be added among the tasks scheduled to be performed by a member (worker) with a low processing priority i in the schedule of the worker currently processing.

[0080] If it is determined that the list of tasks that can be added is empty (step X7 (Yes)), in step X12, the scheduling function unit 16 refers to all patterns of schedules of the worker currently processing the task that were saved in step R5 of FIG. 8 and the concentration level C of the collaborative task that is the predicted result, and in steps X13 and T14, changes the schedule of the worker currently processing the task to the schedule with the maximum concentration level C and outputs it.

[0081] As a result, in an initial schedule including a collaborative task of workers during scheduling processing, if the predicted concentration level C of the collaborative task is less than the minimum required concentration level Cr and there is no task that can be added among the tasks scheduled to be performed by a member (worker) with a low priority i in the processing order, the schedule can be changed to a schedule that maximizes the predicted concentration level C among all schedule patterns in which time periods can be swapped.

[0082] On the other hand, in step X7, if it is determined that the list of tasks that can be added is not empty, that is, if it is determined that there is a task that can be added to the schedule of the worker currently processing among the tasks scheduled to be performed by a member (worker) with a low priority i in the processing order (step X7 (No)), in step X8, the scheduling function unit 16 adds the tasks in the list of tasks that can be added to the schedule of the worker currently processing, and calculates schedule rearrangement patterns according to (Nm+T)Pr permutations, where T is the number of tasks that can be added and r is the maximum number of tasks that can be performed in one day by the worker currently processing.

[0083] In steps Xs2 to Xe2 (search for individual schedule patterns), the scheduling function unit 16 loops through all the schedules of all the replacement patterns according to the (Nm+T)Pr permutations in which addable tasks have been added, predicts the time transition of the concentration level using a prediction model of the corresponding worker's concentration level (step X9), and obtains the concentration level C at the time when the collaborative task is performed (step X10). Note that here, the schedules of each added replacement pattern are searched for in the order from the addable task scheduled to be performed by the member (worker) with the lowest priority i (Nmth) to the addable task scheduled to be performed by the (i+1)th member (worker).

[0084] In step X11, if there is a schedule pattern in which the concentration level C of the collaborative task acquired in step X10 is equal to or greater than the minimum required concentration level Cr (C≧Cr) (step X11 (Yes)), the scheduling function unit 16 ends the loop and outputs the schedule (step T14).

[0085] As a result, even if the predicted concentration level C of the collaborative task in the original schedule including the collaborative task of the worker currently undergoing scheduling processing is less than the minimum required concentration level Cr, and further, even if the predicted concentration level C of the collaborative task is less than the minimum required concentration level Cr in all schedule patterns in which the tasks in the schedule are swapped, it is possible to change to a swap pattern schedule in which the concentration level C of the collaborative task is equal to or greater than the minimum required concentration level Cr among all swap pattern schedules in which a member (worker) with a low priority i in the processing order extracts and adds tasks that can be added from among the tasks scheduled to be performed (tasks that can be shared by the worker currently processing and that will be performed on the day).

[0086] On the other hand, if there is no schedule exchange pattern in which the concentration level C of the collaborative task is equal to or greater than the minimum required concentration level Cr in step X11 (step X11 (No)), in step X12, the scheduling function unit 16 refers to all schedule patterns of the currently processing worker saved in step R5 of FIG. 8 and the predicted concentration level C of the collaborative task, and in steps X13 and T14, changes the schedule of the currently processing worker to a schedule with the maximum concentration level C and outputs it. Note that in the loop of the task exchange / additional schedule change process (RX) with high priority i, if the task of the currently processing worker has already been exchanged with the schedule of a worker with high priority i, the schedule exchange pattern containing the relevant task is deleted in advance in step X8.

[0087] As a result, if the predicted concentration level C of the collaborative task in the initial schedule including the collaborative task of the workers during the scheduling process is less than the minimum required concentration level Cr, and if the predicted concentration level C of the collaborative task is less than the minimum required concentration level Cr in all schedule patterns in which the tasks in the schedule are swapped, and further if the predicted concentration level C of the collaborative task is less than the minimum required concentration level Cr in all swapping pattern schedules in which tasks that can be added to the schedule are added and swapped, then the schedule can be changed to a pattern schedule in which the concentration level C of the collaborative task is greatest among all schedule patterns in which time periods can be swapped.

[0088] <Concentration Model Pre-Learning Process (SP)> FIG. 10 is a diagram showing a specific example of schedule information (table) Tsc acquired as training data in the concentration model pre-learning process (SP) of the team task management server 10. As shown in FIG.

[0089] In the concentration model pre-learning process (SP) (see Figure 6), the schedule acquisition function unit 11 acquires task characteristics, such as task processing time (start / end) and task type, as explanatory variables for the schedule information Tsc for each worker, as shown in Figure 10, and the worker importance input function unit 12 acquires the importance input by the worker as part of the schedule information Tsc (step P1).

[0090] Furthermore, the worker concentration level acquisition function unit 13 acquires the concentration level during the execution of each task as a target variable (step P2).

[0091] The training data acquired in steps P1 and P2 as explanatory variables and objective variables for the schedule information Tsc is stored in the training data DB 14M1 (step P3).

[0092] As part of data preprocessing, the concentration learning function unit 14 adds a column Cbf for "concentration level during task execution t hours ago" to the schedule information (table) Tsc acquired in steps P1 and P2. t may be, for example, 1 to 7 hours. Furthermore, if not much time has passed since the start of the task, processing such as setting the concentration level to "0" may be added. Processing such as data cleansing may also be added (step P4). Note that the technique of adding past values ​​as explanatory variables in data preprocessing is common, and further explanation will be omitted.

[0093] The concentration learning function unit 14 divides the acquired data into training data and verification data (step P5).

[0094] The concentration level learning function unit 14 performs machine learning processing using the pre-processed and divided training data in accordance with an existing established machine learning method (for example, a supervised learning regression method that predicts the number of service usages in the next month from the customer's past behavioral data), and learns the relationship between the task characteristics of each worker and the time transition of the worker's concentration level (step P6). An example of the regression model used here is a linear regression model.

[0095] The concentration learning function unit 14 evaluates the concentration prediction using preset evaluation data (step P7), and if the error is less than the threshold and the target accuracy is achieved, it determines that learning is complete (step P8 (Yes)).If the error is greater than the threshold and the target accuracy is not achieved, it performs processing such as collecting data again or changing explanatory variables, and repeats this process until the target accuracy is achieved (step P8 (No) → P1).

[0096] The concentration learning function unit 14 stores the concentration prediction model, which is the learning model for each worker for which the target accuracy has been ensured in steps P7 and P8, in the learning model DB 14M3 in association with the worker ID (step Pe→SQ).

[0097] The pre-learning process including data collection, data pre-processing, machine learning, and evaluation performed in steps Ps to SQ is an existing established method, and further explanation will be omitted.

[0098] <Concentration Level Ensuring Scheduling Process (ST)> FIG. 11 is a diagram showing a specific example of information that is the subject of input processing of cooperative task characteristics and importance and schedule acquisition processing in the scheduling process (ST) of the team task management server 10. In FIG.

[0099] The administrator input function unit 15 stores the task characteristics of the collaborative task, "Time: 16:00-17:00 / Type: Policy Meeting," importance level: 10, required concentration level: 7 (=Cr), and team members "A, B, C" (Nm people), entered by the administrator M from the administrator terminal 30 when the collaborative task occurred, in the current day processing task DB 16M1 (steps T1 and T2). The administrator M may decide whether the importance of the collaborative task is uniform for all members or varies for each member.

[0100] The schedule acquisition function unit 11 reads the schedules of each of the team members, workers "A, B, and C" (step T3). The worker importance input function unit 12 acquires the importance input by each worker on the worker terminal 20 for the added collaborative task "Policy Meeting" and the importance input by manager M (steps T4 to T6). The schedule read in FIG. 11 shows a specific example of schedule information (table) TAsc for worker A, in which the importance input by manager M for the collaborative task "Policy Meeting" is "10" and the importance input by worker A is "8." A column for the concentration level is added to the table TAsc of the schedule to which the collaborative tasks of each worker have been added, allowing input of the concentration level predicted for each task.

[0101] FIG. 12 is a diagram showing a specific example of information that is the subject of the importance reference and member priority processing order setting process in the scheduling process (ST) of the team task management server 10.

[0102] The scheduling function unit 16 generates an importance table Tim by calculating the importance "10" entered by the manager M for the collaborative task "Policy Meeting" stored in the current day processing task DB 16M1 and the importance "8, 10, 7" entered by each worker "A, B, C."The scheduling function unit 16 then prioritizes the scheduling process in descending order of the importance calculation results ai, and generates a priority order table Tpr by determining the priority order i "B → A → C" for each worker performing scheduling (steps T7 and T8).

[0103] The method of calculating the importance may be selected as an option, such as by adding the importance input by the worker and the manager, weighting the input values ​​of the worker and the manager, or by using only the input value of the manager.

[0104] FIG. 13 is a diagram showing a specific example of information that is the target of the scheduling process (ST) of the team task management server 10 from the scheduling start process to the concentration degree prediction and collaborative task concentration degree acquisition process.

[0105] The scheduling function unit 16 starts scheduling in the order of priority i "B → A → C" for the schedule (TAsc, TBsc, TCsc) to which the collaborative task "Policy Meeting" for all members Nm=3 (three members A, B, and C) of the team performing the collaborative task has been added (step Ts2).

[0106] The scheduling function unit 16 first refers to the schedule table TBsc of worker B, who has the highest priority (step T9).

[0107] The scheduling function unit 16 predicts the time transition of the concentration level corresponding to the schedule (TBsc) of worker "B" using the prediction model of the concentration level of worker "B" from among the learning models for each worker "A, B, C" generated in the pre-learning process (SP) and stored in the learning model DB 14M3 (step T10), and obtains the concentration level C (here, C=5) corresponding to the time of the collaborative task "policy meeting" (step T11). The scheduling process is performed in the same order for workers "B → A → C" according to the priority i.

[0108] FIG. 14 is a diagram showing a specific example of information that is the subject of the concentration level determination process in the scheduling process (ST) of the team task management server 10. In FIG.

[0109] The scheduling function unit 16 acquires the minimum required concentration level Cr (here, Cr = 7) for the collaborative task "Policy Meeting" acquired in step T4 and stored in the current day processing task DB 16M1. Then, the scheduling function unit 16 compares the minimum required concentration level Cr with the concentration level C corresponding to the collaborative task "Policy Meeting" of the worker currently undergoing scheduling processing acquired in step T11, and determines whether to change the original schedule to which the collaborative task of the relevant worker has been added (step T12).

[0110] 14A shows the initial schedule (TAsc) of worker A. In the initial schedule (TAsc) of worker A, the concentration level C corresponding to the collaborative task "policy meeting" is predicted to be 9, and it is determined that the minimum required concentration level Cr is 7 or more (C≧Cr: determination result OK) (step T12 (Yes)). The scheduling function unit 16 outputs the current (initial) schedule (steps T13 and T14).

[0111] 14B shows the initial schedule (TBsc) of worker B. In worker B's initial schedule (TBsc), the concentration level C corresponding to the collaborative task "policy meeting" is predicted to be 5, and it is determined that this is less than the minimum required concentration level Cr of 7 (C<Cr: determination result NG) (step T12 (No)). The scheduling function unit 16 proceeds to schedule change processing (step TR).

[0112] <Schedule Change Processing (TR)> FIG. 15 is a diagram showing a specific example of information that is the subject of the task replacement total pattern calculation processing and personal schedule pattern search processing in the schedule change processing (TR) of the team task management server 10. In FIG.

[0113] The scheduling function unit 16 outputs and saves all Nt! schedule patterns obtained by rearranging tasks in the schedule for the worker B during the scheduling process, assuming that the number of tasks in the schedule is Nt (step R1). The calculation of all task rearrangement patterns in Figure 15 shows an image of schedules (TBsc1, 2, 3, ...) corresponding to 5! rearrangement patterns calculated based on the initial schedule TBsc (number of tasks Nt = 5) of worker B, who is the target of the change.

[0114] The scheduling function unit 16 predicts the transition of the concentration level for each task replacement pattern in the schedule of the worker currently processing using a prediction model of the worker's concentration level (steps Rs and R2). The personal schedule pattern search in Figure 15 shows schedule TBsc3 of replacement pattern "3" in which the task "document creation" and the task "clerical processing" are swapped and the task "organizing items" and the task "idea generation" are swapped for the original schedule TBsc (=TBsc1) of worker B shown in Figure 14 (B), and predicts the transition of the concentration level C corresponding to each task.

[0115] FIG. 16 is a diagram showing a specific example of information that is the subject of the concentration level determination process in the schedule change process (TR) of the team task management server 10.

[0116] In the loop of searching for the personal schedule patterns of each replacement pattern of worker B, the scheduling function unit 16 obtains the predicted concentration level C corresponding to the collaborative task "policy meeting" (step R3) and compares it with the minimum required concentration level Cr (here, Cr = 7) (step R4).

[0117] 16A, when the concentration level C (here, C=8) corresponding to the collaborative task "policy meeting" is acquired in the schedule TBsc3 of the replacement pattern "3" of worker B, the scheduling function unit 16 determines that C≧Cr (determination result OK) (step R4 (Yes)) and outputs the schedule TBsc3 of the replacement pattern "3" (step T14). If a replacement pattern determined to be C≧Cr is found (step R4 (Yes)) during the loop (steps Rs to Re) of the schedules of all replacement patterns (5!: TBsc1 to TBsc120), the loop is terminated and the corresponding schedule is output (step T14).

[0118] On the other hand, for example, as shown in FIG. 16B, if the concentration level C (here, C = 6) corresponding to the collaborative task "Policy Meeting" is obtained in the schedule TBsc120 of the replacement pattern "120" of worker B and it is determined that C < Cr (determination result NG) (step R4 (No)), that is, if the concentration levels C of the collaborative task "Policy Meeting" in the schedules (TBsc1 to TBsc120) of all replacement patterns (120 combinations) are all determined to be C < Cr (determination result NG) and the concentration level condition is not satisfied (step R4 (No) → Re), the scheduling function unit 16 saves the schedules of all replacement patterns (here, TBsc1 to TBsc120) and the predicted concentration level C of the collaborative task (step R5), and proceeds to schedule change processing by task exchange / addition (step RX).

[0119] <Task Exchange and Additional Schedule Change Processing (RX)> FIG. 17 is a diagram showing a specific example of information that is the target of the task allocation list reading and addable task extraction processing in the task exchange and additional schedule change processing (RX) of the team task management server 10. In FIG.

[0120] When the task exchange / additional schedule change process is executed, the scheduling function unit 16 reads the task allocation list Lt to extract tasks that can be added to the original schedule of the worker currently processing (schedule TBsc in the case of worker B) (step X1).

[0121] Figure 17 (A) shows a specific example of a task allocation list Lt for three (Nm) team members, "A, B, C," and shows that, for example, worker B can allocate the task "Preparing minutes" included in worker A's schedule.

[0122] Based on the task allocation list Lt, the scheduling function unit 16 extracts tasks to be added or replaced from the schedule of the worker currently processing the task, provided that the tasks are tasks that can be assigned to the worker currently processing the task, that the execution date is the current day, and that the tasks are included in the schedule of workers (i+1 to Nm-th workers) who have a lower processing priority i than the worker currently processing the task (steps X2 to X5), and adds the extracted tasks to the list of tasks that can be added (step X6).

[0123] 17B shows a specific example of the priority order table Tpr set in the member priority order setting process (step T8), where the priority order i of each worker to be scheduled is set as "B → A → C." Therefore, in this example, the task "Prepare minutes," which has already been added to worker A's schedule, is extracted and added to the list of tasks that can be added, so that the number of tasks to be added becomes 1.

[0124] If there is no team member with a lower priority i than the currently processing worker (in this case, the currently processing worker C), the process of extracting addable tasks (steps X1 to X6) is not performed, and the scheduling process from step X8 onwards is performed by changing the schedule of the currently processing worker to one that allows for leeway in the execution time of the tasks included in the schedule of the currently processing worker, adding a "break" to the schedule, or adding tasks to be performed from tomorrow onwards.

[0125] FIG. 18 is a diagram for explaining a specific example (part 1) of task exchange taking into consideration the priority i in the task exchange and additional schedule change process (RX) of the team task management server 10. In FIG.

[0126] If the currently processing worker is B (priority i=1), and the task "Write minutes" included in the schedule (TAsc) of worker A (priority i=2) is added to the list of tasks that can be added through the addable task extraction process (steps X1 to X6), and if the task "Write minutes" tx is added to worker B's schedule (TBsc) as shown by arrow x, and the concentration level C corresponding to the collaborative task "Policy meeting" becomes equal to or greater than the minimum required concentration level Cr (C≧Cr), then the task "Write minutes" tx will be deleted from worker A's schedule (TAsc).

[0127] Furthermore, even if the schedule (TAsc) of worker A, who has the task to be exchanged or added (here, "minutes preparation"), already satisfies the concentration condition (C≧Cr: here, 9>7) for the collaborative task "policy meeting," if the priority i is lower than that of the worker currently undergoing scheduling (here, worker B), the task will be subject to exchange or addition.

[0128] FIG. 19 is a diagram for explaining a specific example (part 2) of task exchange taking into consideration the priority i in the task exchange and additional schedule change process (RX) of the team task management server 10. In FIG.

[0129] Figure 19 shows the task allocation list Lt1 after the scheduling process for worker B (priority i = 1) adds the addable task ``Preparing minutes'' extracted from the schedule of worker A (priority i = 2) to the schedule of worker B.

[0130] In the scheduling process for worker A (priority i=2), if the concentration condition (C≧Cr) for the collaborative task "policy meeting" is not satisfied by simply changing the schedule by rearranging the tasks included in the schedule (TAsc) after deleting the task "minutes preparation" that was added (handed over) to worker B's schedule (steps R1 to R4 (No)), the scheduling function unit 16 reads the task allocation list Lt1 (step X1).

[0131] Then, the task to be added or replaced in the schedule of the currently processing worker A (here, "research on materials") is extracted (steps X2 to X5), based on the condition that the task is a task that can be assigned to the currently processing worker A, that the task is to be performed on the current day, and that the task is included in the schedule of a worker (here, worker C) with a lower processing priority i than the currently processing worker A, and the extracted task "research on materials" is added to the list of tasks that can be added (step X6).

[0132] FIG. 20 is a diagram for explaining a specific example (part 3) of task exchange taking into consideration the priority i in the task exchange and additional schedule change process (RX) of the team task management server 10. In FIG.

[0133] In the case where worker A (priority i=2) is currently processing and the task "Document Research" included in the schedule (TCsc) of worker C (priority i=3) is added to the list of tasks that can be added through the addable task extraction process (steps X1 to X6), and as shown by arrow x, the task "Document Research" tx is added to the schedule (TAsc1) after worker A has deleted the task "Preparing Minutes" that he passed on to worker B, and the concentration level C corresponding to the collaborative task "Policy Meeting" becomes equal to or greater than the minimum required concentration level Cr (C≧Cr), then the task "Document Research" tx will be deleted from worker C's schedule (TCsc).

[0134] If there is no team member with a lower priority i than the currently processing worker (in this case, the currently processing worker C), the process of extracting addable tasks (steps X1 to X6) is not performed, and the scheduling process from step X8 onwards is performed by changing the schedule of the currently processing worker to one that allows for leeway in the execution time of the tasks included in the schedule of the currently processing worker, adding a "break" to the schedule, or adding tasks to be performed from tomorrow onwards.

[0135] FIG. 21 is a diagram showing a specific example of information that is the subject of the personal schedule pattern search and schedule output process in the task exchange and additional schedule change process (RX) of the team task management server 10.

[0136] Figure 21 shows the case where worker B is in the process of scheduling, and the scheduling function unit 16 adds the task "Preparing minutes" that has been added to the list of tasks that can be added according to the processing in steps X1 to X6 to worker B's schedule (TBsc) as shown in Figure 21 (A).

[0137] Then, for the schedule (TBsc) to which the task "Prepare minutes" has been added, (1) schedules for all replacement patterns for task exchanges and replacements are calculated without omissions or overlaps, according to permutations and combinations, and (2) schedules for all replacement patterns for task additions and replacements are calculated without omissions or overlaps, according to permutations and combinations (step X7 (Yes) → X8). Note that task exchanges and replacements occur when there are tasks that can be shared between each task in the schedule of the worker currently in progress and each task in the schedule of a worker with a lower priority i in the task allocation list Lt1.

[0138] The scheduling function unit 16 (3) predicts the concentration level C of worker B for the schedule TBsc1, 2, ..., n of all replacement patterns calculated in step X8 (step X9), and determines whether the concentration level condition (C ≥ Cr) corresponding to the collaborative task "minute-taking" is met (steps X10, X11).

[0139] For example, as shown in Figure 21 (B), when a concentration level C (here, C = 8) corresponding to the collaborative task "Policy Meeting" is obtained in the schedule TBscn of worker B's replacement pattern "n," the scheduling function unit 16 determines that C ≥ Cr (determination result OK) (step X11 (Yes)) and outputs the schedule TBscn of the replacement pattern "n" (step T14).

[0140] FIG. 22 is a diagram showing a specific example of information that is the subject of the concentration level determination process in the task exchange and additional schedule change process (RX) of the team task management server 10.

[0141] For example, as shown in Figure 22 (A), when the concentration level C (here C = 7) corresponding to the collaborative task "Policy Meeting" is obtained, and a schedule (TBscn) of replacement pattern "n" that satisfies the concentration level condition (C ≥ Cr = 7) is searched for (steps X9 to X11 (Yes)), the loop is terminated and the corresponding schedule (TBscn) is output (step T14).

[0142] On the other hand, for example, as shown in Figure 22 (B), if the concentration level C of the collaborative task "Policy Meeting" in all of the schedules (TBsc1 to TBscm) of all replacement patterns (m combinations) of worker B is judged to be C < Cr (judgment result NG), and the concentration level condition is not met (step X11 (No) → Xe2), the scheduling function unit 16 refers to all of the schedules of worker B's patterns saved in step R5 of Figure 8 and the predicted concentration level C of the collaborative task (step X12), and changes worker B's schedule to the schedule with the maximum concentration level C and outputs it (step X13 → T14).

[0143] When the schedule of the worker currently being processed (here, worker B: priority i=1) is output, the scheduling function unit 16 shifts the processing to the worker with priority i of the next scheduling process (here, worker A: priority i=2), and repeatedly executes the scheduling process in steps Ts2 to Te2 in FIG. 7 until the scheduling process for all workers (here, "B → A → C") is completed.

[0144] (Summary of the embodiment) According to the team task management system 1 of the embodiment, data is collected on the daily schedules of each worker (including the time and type of each task) which include multiple tasks each worker performs, and the concentration level measured for each worker while working, and the relationship between the tasks included in each worker's schedule and the worker's concentration level over time is learned, and a prediction model of the concentration level for each worker is generated.

[0145] When a collaborative task occurs in which multiple workers (team members) work together, a schedule for each worker including the collaborative task is obtained, and based on a concentration prediction model for each worker, the time transition of the concentration corresponding to the obtained schedule is predicted, and the concentration C corresponding to the working time of the collaborative task is obtained. If the concentration C predicted for the collaborative task is equal to or greater than the minimum required concentration Cr (C≧Cr) preset by, for example, an administrator, the current schedule is output as the schedule for the relevant worker without being changed.

[0146] On the other hand, if the concentration level C predicted for the collaborative task is less than the minimum required concentration level Cr (C<Cr), the system calculates and obtains schedules for all replacement patterns in which the time periods of tasks other than the collaborative task included in the schedule are swapped, and based on the prediction model, determines whether the concentration level C corresponding to the collaborative task predicted in sequence for the schedule of each replacement pattern is equal to or greater than the minimum required concentration level Cr (C≧Cr), and outputs the schedule of the replacement pattern (swapping of tasks by time period) determined to be (C≧Cr) as the changed schedule for the corresponding worker (first change process).

[0147] Furthermore, for a schedule of a total replacement pattern in which the time periods of tasks are swapped, if the predicted concentration level C corresponding to the collaborative task is less than the minimum required concentration level Cr (C<Cr), for example, a schedule of a total replacement pattern in which tasks are swapped and added with the schedules of other workers in the team (workers with a processing priority i lower than that of the worker currently processing the task: priority i is set according to the importance of the collaborative task for each worker) is calculated and obtained, and based on the prediction model, it is determined whether the concentration level C corresponding to the collaborative task predicted in sequence for each replacement pattern schedule is equal to or greater than the minimum required concentration level Cr (C≧Cr), and the schedule of the replacement pattern (replacement by swapping and adding tasks) determined to be (C≧Cr) is output as the changed schedule for the relevant worker (second change process).

[0148] Then, for a schedule of all replacement patterns resulting from task exchange / addition, if the concentration level C predicted for the collaborative task is less than the minimum required concentration level Cr (C<Cr), the schedule with the maximum concentration level C predicted for the collaborative task for the schedule of all replacement patterns in which the time periods of the tasks are exchanged is output as the changed schedule for the relevant worker.

[0149] Therefore, according to the team task management system 1 of the embodiment, the schedules of each team member worker can be scheduled so that the individual's concentration on the collaborative task is ensured, and the work on important tasks can be made more efficient.

[0150] This ensures that team members can concentrate when a particularly high level of collaboration is required, such as during important meetings or collaborative work. This can improve productivity by, for example, generating synergistic effects through lively discussions and the creation of various ideas, and by speeding up work.

[0151] The present invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in appropriate combinations, in which case the combined effects can be obtained. Furthermore, the above-described embodiments include various inventions, and various inventions can be extracted by combining selected elements from the disclosed elements. For example, if the problem can be solved and the desired effect can be obtained even if some elements are deleted from all elements shown in the embodiments, the configuration from which these elements are deleted can be extracted as an invention.

[0152] 1...Team task management system 10...Team task management server 11...Schedule acquisition function unit 11M...Assigned task DB 11ML...Scheduling assigned task DB 12...Worker importance input function unit 13...Worker concentration acquisition function unit 14...Concentration learning function unit 14M1...Teacher data DB 14M2...Accuracy judgment threshold DB 14M3...Learning model DB 15...Administrator input function unit 16...Scheduling function unit 16M1...Today's processing task DB 16M2...Member DB 20...Worker terminal Ec...Concentration measurement device 30...Administrator terminal N...Communication network 41...Control circuit (control unit) 42...Memory 43...Disk drive 44...User interface 45...Wired communication module 46...Wireless communication module Tsc...Schedule table (schedule information) Tim...Importance table Tpr...Priority order table i...Priority order Lt...Task allocation list

Claims

1. A team task management device having a control unit that executes the following process: predicting, for each of a plurality of workers, the time progression of concentration corresponding to a schedule for each of the plurality of workers that includes collaborative tasks performed by the plurality of workers, based on a prediction model for each of the workers for predicting the time progression of concentration corresponding to a schedule including a plurality of tasks; and, if the concentration corresponding to the collaborative task among the predicted time progressions of concentration is less than a predetermined concentration level, modifying the schedule for tasks other than the collaborative task included in the schedule so that the concentration corresponding to the collaborative task becomes equal to or greater than the predetermined concentration level.

2. The team task management device of claim 1, wherein the tasks include information on the times at which the tasks are to be executed, and the process of changing the schedule is a first change process that changes the schedule by swapping the times at which tasks other than the collaborative tasks included in the schedule are to be executed.

3. The team task management device of claim 2, wherein the control unit executes a second change process to change the schedule by swapping the tasks between the schedule of the worker to be changed and the schedule of another worker that includes the collaborative task, or by adding a task included in the schedule of the other worker to the schedule of the worker to be changed, when the concentration level corresponding to the collaborative task predicted in accordance with the schedule changed by the first change process is less than a predetermined concentration level.

4. The team task management device of claim 3, wherein the control unit executes a process to acquire the importance of the collaborative task input by a manager of the collaborative task and the importance of the collaborative task input by multiple workers who perform the collaborative task, and to set a priority order for the worker to be changed based on the importance of the collaborative task input by the manager and the importance of the collaborative task input by the multiple workers, and the second change process changes the schedule by swapping or adding the tasks between the schedule of the worker to be changed and the schedule of the other worker who has a lower priority than the worker to be changed.

5. The team task management device according to claim 4, wherein the control unit executes the following process: if the concentration levels corresponding to the collaborative tasks predicted for all schedules in all swapping patterns obtained by swapping the execution times of the tasks through the first change process are all lower than a preset concentration level, the control unit saves in memory the schedules of all swapping patterns and the concentration levels corresponding to the collaborative tasks predicted for the schedules; and if the concentration levels corresponding to the collaborative tasks predicted for the schedules changed through the second change process are lower than a preset concentration level, the control unit changes the schedules of all the saved swapping patterns to the swapping pattern schedule that has the highest concentration level for the saved collaborative tasks.

6. The team task management device according to claim 5, wherein the control unit executes a process of acquiring the concentration level input by the manager of the collaborative task together with the collaborative task as the preset concentration level.

7. A team task management method in which a control unit of a team task management device executes the following process: predicting, for each of a plurality of workers, the time progression of concentration corresponding to a schedule for each of the plurality of workers that includes a collaborative task to be performed collaboratively, based on a prediction model for each of the workers for predicting the time progression of concentration corresponding to a schedule including a plurality of tasks; and, if the predicted time progression of concentration corresponding to the collaborative task is less than a predetermined concentration degree, modifying the schedule for tasks other than the collaborative task included in the schedule so that the concentration degree corresponding to the collaborative task is equal to or greater than the predetermined concentration degree.

8. A program that causes a control unit of a team task management device to function to execute the following process: predict the time progression of concentration corresponding to a schedule for each of multiple workers that includes collaborative tasks performed by multiple workers, based on a prediction model for each worker for predicting the time progression of concentration corresponding to a schedule including multiple tasks; and if the concentration corresponding to the collaborative task among the predicted time progression of concentration is less than a predetermined concentration degree, modify the schedule for tasks other than the collaborative task included in the schedule so that the concentration corresponding to the collaborative task becomes equal to or greater than the predetermined concentration degree.

Images