JP2020009350A - System, method and program for supporting task management - Google Patents

Abstract

To provide a task management support system, a task management support method, and a task management support program for efficiently and accurately carrying out task management in a project.SOLUTION: A control part 21 of a management server 20 acquires schedule information of a task from a plurality of user terminals 10, records the information in a schedule information storage part 24, creates a time chart containing a schedule line based on the start time and a duration in association with the plurality of tasks recorded in the schedule information storage part 24, by using preceding/subsequent relevant information recorded in a basic information storage part 22, and outputs the time chart containing other tasks associated by the preceding/subsequent relevant information recorded in the basic information storage part 22, for the tasks selected for the time chart, to a management terminal 30.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a task management support system, a task management support method, and a task management support program for supporting management of a project including a plurality of tasks.

  In a project consisting of a plurality of tasks, it is important to manage the schedule and progress of each task. For this reason, a progress input support system that supports a progress input by using a tool is being studied (for example, see Patent Document 1). In this technique, the schedule data input in the progress input format activated in the person in charge terminal is transmitted to the management server. Further, the person in charge terminal displays the task list received from the management server, and highlights a critical task whose system activation date is a work day in the task list. The schedule information received from the management server is displayed in a Gantt chart, and the displayed critical path and the delayed work are highlighted.

  Also, a PJ management support device that supports a project manager to grasp the effects of a change in the execution plan of a task on a project in which a plurality of tasks are to be performed has been studied (for example, see Patent Document 2). . In this technique, the PJ management support apparatus stores data before and after a Gantt chart in which a period and a man-hour of each task of a project are determined. The PJ management support apparatus calculates a difference between the man-hour of each task in the Gantt chart before the change and the man-hour of each task in the Gantt chart after the change for a predetermined unit period, and outputs data indicating the difference.

JP 2010-21593 A JP 2010-224889 A

  In task management in a project, progress management is performed based on comparison with a schedule. However, a large project has many tasks that make up the project. In this case, since the department in charge of the task creates the task schedule individually, it takes time to integrate the tasks performed by the administrator. Also, it is difficult for the project manager alone to evaluate the effects of integrating all tasks and changes after integration. When the same project is repeatedly executed, it is necessary to create a schedule for each task in consideration of the results of past projects.

  A task management support system that solves the above-described problem includes a basic information storage unit that records preceding and succeeding relationship information for preceding and succeeding tasks, and a schedule information storage that records schedule information including a start time and a required time for each task. And a control unit connected to the plurality of user terminals and the management terminal. Then, the control unit acquires task schedule information from the plurality of user terminals, records the task schedule information in the schedule information storage unit, and uses the preceding / succeeding relationship information recorded in the basic information storage unit to execute the task schedule. A plurality of tasks recorded in the information storage unit are associated, a time chart including a scheduled line based on the start time and the required time is created, and the task selected in the time chart is recorded in the basic information storage unit. And outputting to the user terminal a time chart including other tasks associated with the associated preceding and succeeding relationship information.

  According to the present invention, task management in a project can be supported efficiently and accurately.

FIG. 1 is an explanatory diagram of a task management support system according to the embodiment. FIG. 2 is an explanatory diagram of a hardware configuration according to the embodiment. It is explanatory drawing of the file used by this embodiment, (a) is an explanatory view of a work item list file, (b) is an explanatory view of a result input file. It is explanatory drawing of the data recorded on the storage part of this embodiment, (a) is a basic information storage part, (b) is a work item information storage part, (c) is a schedule information storage part, (d) is FIG. 4 is an explanatory diagram of a result information storage unit. FIG. 4 is an explanatory diagram of a processing procedure according to the embodiment. FIG. 4 is an explanatory diagram of a processing procedure according to the embodiment. It is explanatory drawing of the processing procedure of this embodiment, (a) is a situation confirmation process, (b) is an acquisition process of result information, (c) is an explanatory diagram of the monitoring process on the day. It is explanatory drawing of the processing procedure of this embodiment, (a) is explanatory drawing of a performance link search process, (b) is a diagram of a chain delay prediction process. It is explanatory drawing of other embodiment, (a) is a task management support system, (b) is explanatory drawing of the processing procedure of a learning process. It is explanatory drawing of the processing procedure of other embodiment, (a) is explanatory drawing of a prediction process, (b) is explanatory drawing of an evaluation process.

(1st Embodiment)
An embodiment that embodies a task management support system, a task management support method, and a task management support program will be described with reference to FIGS. In the present embodiment, a plurality of tasks (operations) are performed to execute a project. When the scale of the project is large, the system used for each task, the person in charge of each task and the department in charge are different. Therefore, it is assumed that the entire project is managed by acquiring task execution schedule information and progress status (actual information) from the person in charge of each task and integrating them. Further, in the present embodiment, it is assumed that the execution of the project is repeated. Therefore, a new schedule is adjusted and progress management on the day is performed based on a comparison between the schedule and the actual result in the past project execution.

As shown in FIG. 1, in the present embodiment, a user terminal 10, a management server 20, and a management terminal 30 are used.
(Hardware configuration)
The hardware configuration of the information processing device H10 configuring the user terminal 10, the management server 20, and the management terminal 30 will be described with reference to FIG. The information processing device H10 includes a communication interface H11, an input device H12, a display device H13, a storage unit H14, and a processor H15. Note that this hardware configuration is an example, and can be realized by other hardware.

  The communication interface H11 is an interface that establishes a communication path with another device to transmit and receive data, and is, for example, a network interface card or a wireless interface.

The input device H12 is a device that receives an input from an operator or the like, and is, for example, a mouse or a keyboard. The display device H13 is a display or the like that displays various information.
The storage unit H14 is a storage device for storing data and various programs for executing various functions of the user terminal 10, the management server 20, and the management terminal 30. Examples of the storage unit H14 include a ROM, a RAM, and a hard disk.

  The processor H15 controls each process in the user terminal 10, the management server 20, and the management terminal 30 using programs and data stored in the storage unit H14. Examples of the processor H15 include, for example, a CPU and an MPU. The processor H15 expands a program stored in a ROM or the like into a RAM and executes various processes for each service.

(System configuration)
Next, the functions of the user terminal 10, the management server 20, and the management terminal 30 will be described with reference to FIGS.

  The user terminal 10 and the management terminal 30 are computer terminals used by a person in charge of each task and a project manager. The person in charge of each task uses the user terminal 10 to transmit scheduled information and actual information on the task in charge to the management server 20. The project manager uses the management terminal 30 to adjust the schedule of each task constituting the project and manage the progress of each task.

The user terminal 10 includes a control unit 11. The control unit 11 includes a spreadsheet unit 111, a result input unit 112, and a storage unit 113.
The table calculation unit 111 executes a process of generating a work item list file 121 relating to the schedule of each task.

The result input unit 112 executes a process of generating a result input file 122 relating to the progress (result) of each task.
The storage unit 113 executes a process of transmitting the generated work item list file 121 and the result input file 122 to the management server 20.

  As shown in FIG. 3A, the work item list file 121 includes data on a management number, a system ID, a task ID, a reference start date and time, a reference end date and time, a required period, and work preconditions. The work item list file 121 is created by the person in charge of each task using the spreadsheet unit 111 of the user terminal 10 before executing the project.

In the management number data area, data relating to an identifier for specifying each work item list file is recorded.
In the system ID data area, data relating to an identifier for specifying a system that executes each task is recorded.

In the task ID data area, data relating to an identifier for specifying each task is recorded.
In the reference start date / time data area, data relating to the scheduled start date and time of the task assumed by the person in charge of the task is recorded. This reference start date and time is recorded as a start date and time corresponding to the date and time (evaluation reference date and time) provided by the system timer at the time of delay. Here, the evaluation reference date and time are used as the relative date and time used for the evaluation, but the current date and time can also be used.

  In the reference end date / time data area, data on the scheduled end date and time of the task assumed by the person in charge of the task is recorded. This reference end date and time is recorded as the end date and time corresponding to the date and time (evaluation reference date and time) provided by the system timer when the delay occurs. Here, the evaluation reference date and time are used as the relative date and time used for the evaluation, but the current date and time can also be used.

In the required period data area, data relating to the time required for task execution assumed by the person in charge of the task is recorded. In this required period, a surplus time buffer is provided to include information on the time that can be reduced (expected reduction time).
In addition, the person in charge of the task has two cases: "when the reference start date and time and the required period are set, and the reference end date and time are not set"; is there.
In addition, the estimated reducible time may be provided in a surplus time buffer in a predetermined unit instead of for each task.

  In the work precondition data area, data on conditions for starting this task is recorded. In this embodiment, any one of the event constraint, the time constraint, and the individual constraint is used. In the event constraint (event driven), a task is started based on the end of a preceding task. In the time constraint (timer driven), a task is started at a predetermined start time. In the individual constraint, a task is started under a condition set by a method other than the event driven and the timer driven.

  As shown in FIG. 3B, the result input file 122 includes data relating to a management number, a system ID, a task ID, a start date and time, and an end date and time. The result input file 122 is created by a person in charge of each task at the time of executing a project using the result input unit 112 of the user terminal 10.

In the management number data area, data relating to an identifier for specifying each performance input file is recorded.
In the system ID data area, data relating to an identifier for specifying a system that executes each task is recorded.

In the task ID data area, data relating to an identifier for specifying each task is recorded.
In the start date and time data area, data on the date and time when this task was started is recorded.
In the end date and time data area, data relating to the date and time when this task was ended is recorded.

  The management server 20 shown in FIG. 1 is a computer system that manages a project composed of a plurality of tasks. The management server 20 includes a control unit 21, a basic information storage unit 22, a work item information storage unit 23, a schedule information storage unit 24, and a result information storage unit 25.

  The control unit 21 executes processing for supporting creation of a schedule for the entire project and management of the progress of each task based on the schedule and results of each task. Then, the control unit 21 performs processing described later (processing including an information acquisition stage, a database management stage, a project management stage, and the like). By executing the task management support program for this purpose, the control unit 21 functions as the information acquisition unit 211, the database management unit 212, and the project management unit 213.

The information acquisition unit 211 acquires a file transmitted from the user terminal 10 and records the file in each information storage unit.
The database management unit 212 executes a process of managing schedule information and result information based on the file acquired from the user terminal 10. Further, the database management unit 212 executes a process of monitoring the progress of the task.
The project management unit 213 executes a process of generating a time chart (Gantt chart) based on the schedule information and the performance information generated by the database management unit 212.

  As shown in FIG. 4A, the basic information storage unit 22 stores basic management data relating to tasks constituting a project. In the basic information storage unit 22, a large item management record 221, a medium item management record 222, and a task management record 223 are recorded. In the present embodiment, a hierarchical structure of a large item (upper layer) to a task (lower layer) is used.

  The large item management record 221 is data for managing large items that are classified into large projects. The large item management record 221 records a large item ID and data related to the preceding / succeeding relationship.

In the large item ID data area, data on an identifier for specifying each large item is recorded.
In the preceding / succeeding relationship data area, data relating to an identifier (large item ID) for specifying the leading large item and the following large item of this large item is recorded.

  The medium item management record 222 is data for managing medium items obtained by subdividing large items. The middle item management record 222 records a middle item ID and data related to the preceding / succeeding relationship.

In the medium item ID data area, data on an identifier for specifying each medium item included in the large item is recorded.
In the preceding / succeeding relation data area, data relating to an identifier (medium item ID) for specifying the preceding / subsequent item of the middle item is recorded.

  The task management record 223 is data for managing a task. The task management record 223 records data relating to a task ID, a system ID, a responsible unit ID, a category, an action, and a preceding / succeeding relationship.

In the task ID data area, data relating to an identifier for identifying each task included in the middle item is recorded.
In the system ID data area, data relating to an identifier for specifying a system that executes this task is recorded.

  In the assigned department ID data area, data relating to an identifier for specifying a department assigned to this task is recorded. The contact address of the person in charge can be specified by this department ID.

  A flag for specifying the importance of the task set by the project manager is recorded in the section data area. In the present embodiment, flags indicating “slight”, “general”, “important”, “most important”, “alert” and the like are recorded.

In the action data area, data for specifying a response when a delay or an incident occurs in this task is recorded. This action is determined according to the task classification (importance) and the delay width of a checkpoint (a sign monitoring target described later). As the action, for example, there is an alarm notification to a related part, output of report material, and the like. For this reason, information for specifying a contact to which an alarm is to be transmitted, a type of report material to be output, an output method, and the like are recorded. Note that a telephone number, a mail address, a department ID, and the like can be used as the contact information.
In the preceding / succeeding relationship data area, data on an identifier (task ID) for specifying a preceding task and a succeeding task of this task is recorded.

  As shown in FIG. 4B, the work item information storage unit 23 records a work item management record 230 generated based on the work item list file 121.

  In the work item management record 230, similarly to the work item list file 121, data on a management number, a system ID, a task ID, a reference start date and time, a reference end date and time, a required period, and work preconditions are recorded.

  As shown in FIG. 4C, a schedule management record 240 for the work is recorded in the schedule information storage unit 24. The schedule management record 240 includes data relating to a management number, a system ID, a task ID, a large item ID, a medium item ID, a scheduled start date and time, a scheduled end date and time, a required period, a division, an action, whether or not sign monitoring is necessary, and work preconditions. Be recorded.

In the management number data area, data relating to an identifier for specifying the schedule management record 240 is recorded.
In the system ID data area, data relating to an identifier for specifying a system on which this task is executed is recorded.

In the task ID data area, data relating to an identifier for specifying each task is recorded.
In the large item ID data area, data relating to an identifier for specifying the large item to which this task belongs is recorded.
In the middle item ID data area, data on an identifier for specifying the middle item to which this task belongs is recorded.

In the scheduled start date / time data area, data on the date and time when the task is scheduled to start is recorded.
In the scheduled end date / time data area, data relating to the scheduled end date and time of this task is recorded.

In the required period data area, data on the required time required to execute this task is recorded.
A flag for specifying the importance of the task set by the project manager is recorded in the section data area.

In the action data area, information for specifying a response when a delay or an incident occurs in this task is recorded.
In the sign monitoring necessity data area, a flag for determining whether sign monitoring is necessary or not is recorded. In the present embodiment, a task (checkpoint) that has a large effect on a subsequent task in a critical path or the like is set as a sign monitoring target.
In the work precondition data area, data on conditions for starting this task is recorded. In this embodiment, any one of the event constraint, the time constraint, and the individual constraint is used.

  As shown in FIG. 4D, a performance management record 250 for the work is recorded in the performance information storage unit 25. This performance management record 250 is registered before executing the task. The performance management record 250 records data relating to the management number, system ID, task ID, capture date and time, start date and time, end date and time, state before capture, state after capture, elapsed time, weight evaluation result, and action. You. The capture date / time-action data area is left blank as an initial value.

In the management number data area, data relating to an identifier for specifying the performance management record 250 is recorded.
In the system ID data area, data relating to an identifier for specifying a system on which this task is executed is recorded.

  In the task ID data area, data relating to an identifier for specifying each task is recorded.

In the import date / time data area, data relating to the date and time when the result input file 122 relating to this task was acquired is recorded.
In the start date and time data area, data on the date and time when this task was started is recorded.

In the end date and time data area, data relating to the date and time when this task was ended is recorded.
In the pre-import state data area, data relating to the state before the import of the results input file 122 is recorded. In the present embodiment, the initial value is blank, and flags indicating “delay”, “waiting for report”, “monitoring”, and the like are recorded for the start and end of the task depending on the situation.

  In the post-acquisition status data area, data on the status of the results input file 122 after the import is recorded. In the present embodiment, the initial value is blank, and a flag for specifying “delay” or the like is recorded for the start and end of the task according to the situation.

In the elapsed time data area, data relating to the elapsed time from the scheduled date and time for the start and end of the task is recorded.
In the weight evaluation result data area, a flag for specifying an evaluation result for weighting the progress of the start and end of the task is recorded. In the present embodiment, the initial value is blank, and a flag for specifying “incident” and “delay” is recorded according to the situation.
In the action data area, data on an action performed according to the result of the weight evaluation regarding the start and end of the task is recorded.

(Schedule creation process)
The schedule creation processing will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes a process of acquiring schedule information (Step S1-1). Specifically, the person in charge of each task creates the work item list file 121 using the spreadsheet unit 111 of the user terminal 10. Then, when the creation of the work item list file 121 is completed, the work item list file 121 is transmitted to the management server 20 using the storage unit 113. In this case, the information acquisition unit 211 of the control unit 21 acquires the work item list file 121 transmitted from the user terminal 10.

  Next, the control unit 21 of the management server 20 executes a consistency check process (Step S1-2). Specifically, the information acquisition unit 211 of the control unit 21 uses the basic information storage unit 22 to store the task management record 223 in which the system ID and the task ID of the work item list file 121 acquired from the user terminal 10 are recorded. Search for. Here, if the information acquisition unit 211 can identify the task management record 223 in which the system ID and the task ID are recorded, the information confirmation unit 211 completes the consistency check processing. On the other hand, when the task management record 223 in which the system ID and the task ID are recorded cannot be specified, the information acquisition unit 211 determines that there is no consistency, and returns an error message to the user terminal 10. If the consistency can be confirmed, the information acquisition unit 211 generates a work item management record 230 based on the work item list file 121 and records it in the work item information storage unit 23.

  Next, the control unit 21 of the management server 20 executes an integration process (Step S1-3). Specifically, the database management unit 212 of the control unit 21 stores the work item management record 230 recorded in the work item information storage unit 23 in the order of the large item, the medium item, and the task recorded in the basic information storage unit 22. Create an integrated file listed in. Here, using the large item management record 221, a matrix in which large items are arranged in each row in the column direction is created. Furthermore, the middle item belonging to the large item is inserted between the rows of the large item in the column direction using the middle item management record 222. Further, the task belonging to the middle item is inserted between the rows of the middle item in the column direction using the preceding / succeeding relationship of the task management record 223. Then, an integrated file in which the contents of the work item management record 230 are arranged in each task line is created.

  Next, the control unit 21 of the management server 20 executes a process of generating Gantt chart drawing data (Step S1-4). Specifically, the database management unit 212 of the control unit 21 converts the created integrated file into drawing data for creating a Gantt chart in the project management unit 213.

  Next, the control unit 21 of the management server 20 executes a Gantt chart combining process (Step S1-5). Specifically, the project management unit 213 of the control unit 21 uses the Gantt chart drawing data to arrange each task in a column and create a Gantt chart provided with a time axis for indicating an execution time zone of each task. I do.

  Next, the project management unit 213 generates, on the time axis, a scheduled line in which the reference start date and time and the reference end date and time are automatically calculated according to the context between tasks. For example, in event driven, a reference start date and time of a task is set based on the end of a preceding task. In the timer driven, the reference start date and time set by the person in charge of the task is used. Then, the project management unit 213 outputs to the management terminal 30 the Gantt chart integrated by the task combination.

  Next, the control unit 21 of the management server 20 executes an adjustment process (Step S1-6). Specifically, the administrator checks the Gantt chart displayed on the management terminal 30. Then, the execution time zone of each task in the Gantt chart is adjusted using the management terminal 30. Here, the expected reduction time is corrected in consideration of the completion deadlines of all tasks. In this case, the adjustment is made according to the work preconditions (event constraints, time constraints, individual constraints) of the work item management record 230 recorded in the work item information storage unit 23. For example, in the case of an event constraint, the scheduled start date and time of each task can be changed according to the scheduled end date and time of the preceding task. On the other hand, in the case of a time constraint, the scheduled start date and time of each task cannot be changed. Further, a surplus time buffer for each task is defined, and the surplus time buffer is added to or subtracted from the scheduled line of the Gantt chart. In this case, the project management unit 213 of the control unit 21 changes the arrangement and length of the planned line of the Gantt chart in the management terminal 30 based on the operation of adjusting the date and time of each task.

  Next, the control unit 21 of the management server 20 executes a determination process as to whether or not the creation is completed (Step S1-7). Specifically, when the administrator has completed the creation of the scheduled line, the administrator inputs a completion input to the management terminal 30. When the completion input is not performed and the creation is not completed (“NO” in step S1-7), the control unit 21 of the management server 20 continues the adjustment processing (step S1-6).

  On the other hand, when the completion input is performed and it is determined that the creation is completed (in the case of “YES” in step S1-7), control unit 21 of management server 20 executes a schedule information registration process (step S1-8). ). Specifically, the database management unit 212 of the control unit 21 specifies the scheduled start date and time and the scheduled end date and time based on the adjusted arrangement of the planned lines on the time axis. Then, the database management unit 212 generates a schedule management record 240 including the management number, the task ID of the work item management record 230, the classification of the task management record 223, and the action, and records it in the schedule information storage unit 24. In the schedule management record 240, the scheduled start date and time and the scheduled end date and time specified using the scheduled line adjusted in step S1-6 are recorded.

  Next, the control unit 21 of the management server 20 executes a checkpoint registration process (step S1-9). Specifically, the project management unit 213 of the control unit 21 specifies a critical path on the scheduled line (Gantt chart). Next, the project management unit 213 specifies a task candidate serving as a checkpoint on the critical path. For example, in the tasks included in the specified critical path, the project management unit 213 specifies task candidates to be checkpoints according to predetermined time intervals and task divisions, and displays them on the display of the management terminal 30. Then, the administrator uses the management terminal 30 to check task candidates and designate a predetermined task as a checkpoint. In this case, the database management unit 212 of the control unit 21 records a monitoring flag in the sign monitoring necessity data area of the schedule management record 240 for the task at the specified checkpoint.

(Related task search processing)
Next, the related task search processing will be described with reference to FIG. In this search processing, a connection between tasks is searched.

  First, the control unit 21 of the management server 20 executes a process for specifying a selected task (Step S2-1). Specifically, the administrator specifies a task line desired to be searched in the tasks on the Gantt chart displayed on the display of the management terminal 30. Here, when a search for a plurality of tasks is desired, a plurality of lines are specified at the same time. In this case, the project management unit 213 of the control unit 21 specifies the task ID of the selected row.

  Next, the control unit 21 of the management server 20 executes a process of specifying the number of layers (step S2-2). Specifically, the project management unit 213 of the control unit 21 displays a hierarchy designation field on the display of the management terminal 30. In this hierarchy designation column, “100 hierarchy” is set as an initial value. The administrator changes the desired number of hierarchies as necessary. Then, the project management unit 213 obtains the number of layers input in the layer specification field.

  Next, the control unit 21 of the management server 20 executes a search method specifying process (step S2-3). Specifically, the project management unit 213 of the control unit 21 displays a search method designation field on the display of the management terminal 30. In the search method designation field, one of backward search, forward search, and compound search is selected. Here, in the backward search, for the selected task, a task whose succession relationship is recorded in the task management record 223 is searched. In the forward search, a task in which the preceding relation is recorded in the task management record 223 is searched for the selected task. In the compound search, a backward search and a forward search are performed for the selected task.

  Next, the control unit 21 of the management server 20 executes a process of specifying a related task (Step S2-4). Specifically, the database management unit 212 of the control unit 21 uses the preceding and succeeding relationships recorded in the task management record 223, the medium item management record 222, and the large item management record 221 of the basic information storage unit 22 to search for Identify related tasks related to the task. In the first search, the selected task is used as a search target task. Note that the medium item management record 222 and the large item management record 221 respectively specify the large item to which the middle item belongs and the preceding and succeeding Used to identify a certain other large item. In this case, “1” is added to the number of repetitions according to the searched hierarchy.

  Next, the control unit 21 of the management server 20 executes a determination process as to whether or not all the related tasks have been extracted (Step S2-5). Specifically, when a subsequent task cannot be detected in the backward search, the database management unit 212 determines that all related tasks have been extracted. In the forward search, if no preceding task can be detected, it is determined that all related tasks have been extracted. In the compound search, the determinations in the backward search and the forward search are used together.

When it is determined that all the related tasks have been extracted (in the case of “YES” in step S2-5), the control unit 21 of the management server 20 ends the process for the selected task.
On the other hand, when it is determined that all the related tasks have not been extracted (in the case of “NO” in step S2-5), the control unit 21 of the management server 20 executes a determination process on whether or not the number of layers has been reached. (Step S2-6). Specifically, the database management unit 212 determines whether the number of repetitions of the related task specifying process (step S2-4) has reached the number of layers.

  When it is determined that the number of layers has not been reached (in the case of “NO” in step S2-6), the control unit 21 of the management server 20 repeats the related task specifying process (step S2-4). In this case, the preceding or succeeding related task is repeatedly specified using the preceding and succeeding relationship recorded in the basic information storage unit 22 with the previously specified related task as a search target task. When a plurality of preceding or succeeding related tasks exist in one search target task, the specification of the related task is repeated with each related task as a search target task.

On the other hand, when it is determined that the number of layers has been reached (in the case of “YES” in step S2-6), the control unit 21 of the management server 20 ends the process for the selected task. Then, the above processing is repeated until all the selected tasks are completed.
Next, the control unit 21 of the management server 20 executes a display process of a range including the specified task (Step S2-7). Specifically, the project management unit 213 of the control unit 21 outputs a Gantt chart of the related task specified for the selected task to the display of the management terminal 30.

(Status confirmation processing)
Next, a situation confirmation process for monitoring on the day of execution of a task will be described with reference to FIG. In this monitoring process, the task execution status is monitored while performing the status confirmation process, the acquisition process of the result information, and the monitoring process on the day.

First, the status confirmation processing of an incomplete task will be described with reference to FIG.
Here, the control unit 21 of the management server 20 executes a process of specifying an incomplete task (Step S3-1). Specifically, the database management unit 212 of the control unit 21 extracts, in the result information storage unit 25, the result management record 250 in which the end date and time are not recorded. Then, the database management unit 212 specifies the incomplete task using the extracted performance management record 250.

Next, the control unit 21 of the management server 20 executes the following processing for each of the specified incomplete tasks.
Here, the control unit 21 of the management server 20 executes a process of specifying the scheduled date and time (step S3-2). Specifically, the database management unit 212 of the control unit 21 acquires the schedule management record 240 from the schedule information storage unit 24 using the task ID of the result management record 250 of the incomplete task. Then, the database management unit 212 acquires the scheduled start date and time and the scheduled end date and time recorded in the schedule management record 240.

  Next, the control unit 21 of the management server 20 executes a determination process as to whether or not it is a delay (step S3-3). Specifically, the database management unit 212 of the control unit 21 acquires the evaluation reference date and time from the system timer, and compares it with the scheduled start date and time and the scheduled end date and time. Here, in the result management record 250 of the uncompleted task, when the start date and time are not recorded and the evaluation reference date and time have passed the scheduled start date and time, it is determined that the task start is delayed. Further, in the result management record 250 of the uncompleted task, if the end date and time are not recorded and the evaluation reference date and time have passed the scheduled end date and time, it is determined that the task end is delayed.

If it is determined that the delay has occurred (“YES” in step S3-3), the control unit 21 of the management server 20 executes a state recording process (step S3-4). Specifically, when the database management unit 212 of the control unit 21 determines that the start date and time is not recorded, the database management unit 212 records the delay flag in the pre-import state data area of the performance management record 250. If it is determined that the start date and time are recorded, a delay flag is recorded in the post-acquisition state data area of the performance management record 250. When an incident report is received from the person in charge of the task, the database management unit 212 records an incident flag. Note that a reference time for determining a large delay, which should be determined as an incident, may be set in advance. In this case, if the delay width from the reference start date and time or the reference end date and time is longer than the reference time, it is determined to be an incident, and the incident flag is recorded.
On the other hand, when it is determined that it is not a delay (in the case of “NO” in step S3-3), the control unit 21 of the management server 20 skips the state recording process (step S3-4).

(Acquisition process of result information)
Next, with reference to FIG. 7B, a description will be given of a process of acquiring the result information when registering the result information.
The person in charge of each task uses the result input unit 112 of the user terminal 10 to input a start date and time when each task is started, and to input an end date and time when each task is ended. In this case, the result input unit 112 generates the result input file 122. Then, the storage unit 113 transmits the generated result input file 122 to the management server 20.

  In this case, the control unit 21 of the management server 20 executes a process of acquiring the result information (step S4-1). Specifically, the information acquisition unit 211 of the control unit 21 acquires the result input file 122 transmitted from the user terminal 10.

  Next, the control unit 21 of the management server 20 executes a recording process (Step S4-2). Specifically, the information acquisition unit 211 of the control unit 21 acquires the evaluation reference date and time from the system timer. Then, the information acquisition unit 211 extracts from the result information storage unit 25 a result management record 250 in which the management number, task ID, and system ID of the obtained result input file 122 are recorded. The information acquisition unit 211 records the evaluation reference date and time in the capture date and time data area of the extracted performance management record 250.

  Next, the database management unit 212 records the start date and time and the end date and time recorded in the result input file 122 in each data area of the result management record 250. Here, when only the start date and time is recorded in the result input file 122, the end date and time data area of the result management record 250 is blank. On the other hand, when the end date and time are recorded in the result input file 122, the end date and time are recorded in the result management record 250, and the elapsed time is calculated based on the difference from the start date and time. Record.

  Next, the database management unit 212 extracts the schedule management record 240 in which the management number, the task ID, and the system ID are recorded from the schedule information storage unit 24 based on the result management record 250 to be processed. When the end date and time are recorded in the performance management record 250, the database management unit 212 compares the scheduled end date and time of the schedule management record 240 with the end date and time. If the end date and time is later than the scheduled end date and time, a delay flag is recorded in the post-acquisition state data area. On the other hand, when the end date and time are not recorded in the performance management record 250, the database management unit 212 compares the scheduled start date and time of the schedule management record 240 with the start date and time. If the start date and time is later than the scheduled start date and time, a delay flag is recorded in the pre-import state data area. Also, when an incident report is received from the person in charge of the task, an incident flag is recorded.

(Monitoring process on the day)
Next, the monitoring process on the day will be described with reference to FIG.
Here, the control unit 21 of the management server 20 executes a prediction process of a future situation (Step S5-1). Specifically, the project management unit 213 of the control unit 21 executes a performance-linked search process and a chain delay prediction process, as described later.

Next, the control unit 21 of the management server 20 executes a progress monitoring process (step S5-2). Specifically, the database management unit 212 of the control unit 21 performs delay monitoring, incident monitoring, and checkpoint monitoring.
In the delay monitoring, the task in which the delay flag is recorded in the status data area before capture or the status data area after capture of the performance management record 250 is specified.
In the incident monitoring, the task in which the incident flag is recorded in the weight evaluation result data area of the performance management record 250 is specified, and the content supplementally input by the person in charge of the task is specified.
In the checkpoint monitoring, among the succeeding tasks specified by the related task search processing, the delay in which the monitoring flag is recorded in the sign monitoring necessity data area of the schedule management record 240 is predicted by the performance linked search processing. .

  Next, the control unit 21 of the management server 20 executes an action process (Step S5-3). Specifically, the database management unit 212 of the control unit 21 stores a checkpoint (task), a task that has detected a delay or an incident, in the schedule management record 240 of the schedule information storage unit 24 based on the monitoring result of the progress. Identify recorded actions. Here, the action according to the delay width and the classification (importance of the task) recorded in the schedule management record 240 is specified. Then, the database management unit 212 transmits an alarm and outputs report data based on the specified action. In this case, the database management unit 212 records information for specifying an action in the action data area of the performance management record 250 of the performance information storage unit 25.

(Actual linked search processing)
Next, with reference to FIG. 8A, the result-linked search processing will be described. In the performance-linked search processing, a process of rewriting the scheduled line is performed according to the performance.

  First, the control unit 21 of the management server 20 executes a process of specifying a delayed task (Step S6-1). Specifically, the database management unit 212 of the control unit 21 extracts, in the result information storage unit 25, the result management record 250 in which the delay flag is recorded in the post-acquisition state data area. The processing target is not limited to the record management record 250 in which the delay flag is recorded, but may be a record management record 250 in which the monitoring flag and the incident flag are recorded.

  Next, the control unit 21 of the management server 20 executes a process of selecting a monitoring target (Step S6-2). Specifically, the database management unit 212 of the control unit 21 outputs a monitoring screen listing the tasks of the performance management record 250 extracted from the performance information storage unit 25 to the display of the management terminal 30. In this case, the administrator selects a task desired to be searched on the monitoring screen. Here, a plurality of tasks can be selected. Then, the database management unit 212 specifies the task ID of the task selected on the monitoring screen.

Next, the control unit 21 of the management server 20 executes the following processing for each selected task.
Here, the control unit 21 of the management server 20 executes a backward search process (Step S6-3). Specifically, the database management unit 212 of the control unit 21 executes a backward search process in the related task search process (FIG. 6).

  Next, the control unit 21 of the management server 20 executes a scheduled line rewriting process according to the actual result (step S6-4). Specifically, the database management unit 212 of the control unit 21 calculates the delay width of the selected task. Here, when the end date and time are recorded, the delay width is calculated by subtracting the scheduled end date and time from the end date and time. On the other hand, when the end date and time are not recorded, the delay width is calculated by subtracting the scheduled start date and time from the start date and time. Next, the database management unit 212 extracts the result management record 250 of the related task specified by the backward search processing, and specifies the related task in which the state data area before capture is blank. Then, the database management unit 212 calculates the scheduled result reflection time by adding the delay width to the scheduled start date and time of the schedule management record 240 of the related task. Then, the database management unit 212 passes the scheduled result reflection time to the project management unit 213. In this case, the project management unit 213 generates a Gantt chart in which the planned lines reflecting the results are displayed in parallel with the planned lines, and outputs the Gantt chart to the display of the management terminal 30.

(Chain delay prediction processing)
Next, the chain delay prediction processing will be described with reference to FIG. In the chain delay prediction process, a future state that is assumed to be delayed by a predetermined period (for example, one hour or seven days) is predicted. As the predetermined period, a predetermined time or a time arbitrarily set by an administrator can be used. Further, the predetermined period may be calculated according to the task status.

  First, similarly to steps S6-1 and S6-2, the control unit 21 of the management server 20 executes a process of specifying a delayed task (step S7-1) and a process of selecting a monitoring target (step S7-2).

Next, the control unit 21 of the management server 20 executes the following processing for each selected task.
Here, the control unit 21 of the management server 20 executes a backward search process as in step S6-3 (step S7-3).

  Next, the control unit 21 of the management server 20 executes a scheduled line rewriting process according to the assumption (step S7-4). Specifically, the database management unit 212 of the control unit 21 extracts the result management record 250 of the related task specified by the backward search process, and specifies the related task whose blank state data area is blank. Then, the database management unit 212 calculates the assumption reflection scheduled date and time by adding a predetermined period to the scheduled start date and time of the schedule management record 240 of the related task. Then, the database management unit 212 transfers the assumption reflection scheduled date and time to the project management unit 213. In this case, the project management unit 213 generates a Gantt chart in which planned lines reflecting assumptions are displayed in parallel with the original planned lines, and outputs the generated Gantt chart to the display of the management terminal 30.

As described above, according to the present embodiment, the following effects can be obtained.
(1-1) In the present embodiment, the control unit 21 of the management server 20 performs the schedule information acquisition process (step S1-1), the consistency check process (step S1-2), and the integration process (step S1-3). Execute Thus, by integrating the schedule information acquired from the person in charge of each task, it is possible to create management information for creating a time chart for the entire project. Then, the department in charge of the task individually creates a task schedule, and the project manager can evaluate the effects of the task integration and the changes after the integration.

  (1-2) In the present embodiment, the control unit 21 of the management server 20 performs the Gantt chart synthesis processing (Step S1-5), the adjustment processing (Step S1-6), and the schedule information registration processing (Step S1-8). Execute Thereby, the execution time of each task can be adjusted using the scheduled line of the Gantt chart in which the schedule information of each task is integrated.

  (1-3) In the present embodiment, the control unit 21 of the management server 20 executes a checkpoint registration process (Step S1-9). As a result, a controlled checkpoint can be set in a project including a plurality of tasks.

  (1-4) In the present embodiment, the control unit 21 of the management server 20 performs the process of specifying the selected task (Step S2-1), the process of specifying the related task (Step S2-4), and the range including the specified task. Is executed (step S2-7). Thereby, the time chart of the preceding task and the succeeding task related to the selected task can be confirmed.

  (1-5) In the present embodiment, the control unit 21 of the management server 20 executes a process of specifying the number of layers (step S2-2). When it is determined that the number of layers has not been reached (in the case of “NO” in step S2-6), the control unit 21 of the management server 20 repeats the related task specifying process (step S2-4). Thereby, related tasks can be displayed in a desired number of layers.

  (1-6) In the present embodiment, the control unit 21 of the management server 20 executes a search method specifying process (step S2-3). Here, one of backward search, forward search, and compound search is selected in the search method designation field. As a result, the preceding task, the succeeding task, or both can be displayed according to the user's request.

  (1-7) In the present embodiment, the control unit 21 of the management server 20 executes a status confirmation process of an incomplete task. Here, when it is determined that it is a delay (in the case of “YES” in step S3-3), the control unit 21 of the management server 20 executes a state recording process (step S3-4). As a result, it is possible to specify a task that is delayed for a task for which actual information has not been acquired.

  (1-8) In the present embodiment, the control unit 21 of the management server 20 executes a process of importing performance information. In this case, if the start date and time and the end date and time are later than the scheduled start date and time and the scheduled end date and time, a delay flag is recorded in the post-acquisition state data area. This makes it possible to specify a delayed task based on the performance information.

  (1-9) In the present embodiment, the control unit 21 of the management server 20 executes a day monitoring process. Here, the control unit 21 of the management server 20 executes a process of monitoring the progress (step S5-2). Then, delay monitoring, incident monitoring, and checkpoint monitoring are performed. Then, the control unit 21 of the management server 20 executes an action process (Step S5-3). Thereby, an action can be efficiently executed in response to a delay or an incident.

  (1-10) In the present embodiment, the control unit 21 of the management server 20 executes a result-linked search process. This makes it possible to predict the delay of the succeeding task based on the delay situation in the result information of the preceding task.

  (1-11) In the present embodiment, the control unit 21 of the management server 20 executes a chain delay prediction process. Thus, even when the delay status of the preceding task is not determined, the delay of the succeeding task can be predicted.

(Second embodiment)
Next, a task management support system according to a second embodiment of the present invention will be described with reference to FIGS. Note that the second embodiment employs a configuration using machine learning in the work management method of the first embodiment, and a detailed description of similar parts will be omitted. Here, a plurality of incidents that have occurred in actual results are grouped by machine learning. Further, the evaluation of new schedule information and the prediction of the result are predicted by machine learning using a data set including schedule information and result information as teacher data.

As shown in FIG. 9A, the management server 20 further includes an incident information storage unit 26 and a model information storage unit 27.
The control unit 21 further includes a learning unit 215, a prediction unit 216, and an evaluation unit 217.
The learning unit 215 executes a process of generating a prediction model for predicting an output layer from an input layer by machine learning using teacher data.

The prediction unit 216 performs a process of predicting an output layer from an input layer using the prediction model generated by the learning unit 215.
The evaluation unit 217 performs a process of evaluating the prediction result based on the performance.

  The incident information storage unit 26 records an incident report on the task in which the incident has occurred. The incident report includes information on the system in which the task in which the incident occurred was executed, the major items to which the task belongs, and the incident occurrence event. Further, in the incident report, detailed information (such as supplementary explanation) on the incident is input by the person in charge of the task.

  The prediction model generated by the learning unit 215 is recorded in the model information storage unit 27. In the present embodiment, an incident event prediction model, an actual line prediction model, and an incident prediction model are recorded. The incident event prediction model is a model for grouping similar incident events from a plurality of incident events. The performance line prediction model is a model that predicts the performance line based on the prediction line. The incident prediction model is a model that predicts an incident that may occur based on a prediction line.

(Learning process)
The learning process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes an incident event input process (Step S8-1). Specifically, the learning unit 215 of the control unit 21 acquires an incident report from the incident information storage unit 26.

  Next, the control unit 21 of the management server 20 executes a process of specifying a similar event (Step S8-2). Specifically, the learning unit 215 of the control unit 21 outputs a learning screen to the display of the management terminal 30. This learning screen includes a list of the acquired incident reports. Then, the administrator assigns the same group ID to the mutually similar incidents in this list. In this case, the learning unit 215 specifies an incident report for each group ID divided into groups.

  Next, the control unit 21 of the management server 20 executes a machine learning process (Step S8-3). Specifically, the learning unit 215 of the control unit 21 uses the teacher data set in which the incident report and the group ID are combined to predict the group ID (output layer) from the incident report (input layer). Create an incident event prediction model.

  Next, the control unit 21 of the management server 20 executes a process of acquiring schedule information and actual information (step S8-4). Specifically, the learning unit 215 of the control unit 21 acquires the already executed schedule management record 240 from the schedule information storage unit 24. Further, the learning unit 215 acquires the result management record 250 corresponding to the schedule management record 240 from the result information storage unit 25. Then, the learning unit 215 uses the performance management record 250 to specify the performance line, the critical path, and the incident.

  Next, the control unit 21 of the management server 20 executes a process of creating teacher data (Step S8-5). Specifically, the learning unit 215 of the control unit 21 generates a teacher data set for a performance line by combining the planned line and the performance line. Further, an incident teacher data set is generated by combining the schedule line and the incident. For the incidents in the incident training data set, similar predicted incidents are grouped using an incident event prediction model.

  Next, the control unit 21 of the management server 20 executes a machine learning process (Step S8-6). Specifically, the learning unit 215 of the control unit 21 creates a performance line prediction model for predicting a performance line (output layer) from a planned line (input layer) using the performance line teacher data set. Further, the learning unit 215 creates an incident prediction model for predicting an incident (output layer) from a scheduled line (input layer) using the teacher data set for incident.

  Next, the control unit 21 of the management server 20 executes a prediction model registration process (Step S8-7). Specifically, the learning unit 215 of the control unit 21 records each generated prediction model in the model information storage unit 27.

(Forecast processing)
The prediction process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes a process of acquiring new schedule information (Step S9-1). Specifically, the prediction unit 216 of the control unit 21 acquires a new schedule management record 240 registered in the schedule information storage unit 24.

  Next, the control unit 21 of the management server 20 executes a process of predicting the performance line and the incident (Step S9-2). Specifically, the prediction unit 216 of the control unit 21 creates a scheduled line using the acquired schedule management record 240. Next, the prediction unit 216 calculates a predicted actual line in the output layer using an actual line prediction model using the planned line in the input layer. Further, the prediction unit 216 calculates a predicted incident in the output layer using an incident prediction model using the planned line in the input layer.

  Next, the control unit 21 of the management server 20 executes a process of calculating the critical path and the forecast / actual difference (Step S9-3). Specifically, the prediction unit 216 of the control unit 21 calculates a predicted / actual difference by comparing the planned line used for the input layer with the predicted actual line of the output layer. Next, the prediction unit 216 specifies a critical path in the predicted performance line of the output layer. Further, the prediction unit 216 specifies a checkpoint for a task included in the specified critical path. For example, a task serving as a checkpoint is specified according to a predetermined time interval or a task division.

  Next, the control unit 21 of the management server 20 executes a process of evaluating the validity of the prediction result (Step S9-4). Specifically, the prediction unit 216 of the control unit 21 outputs a Gantt chart including the planned line and the predicted result line on the display of the management terminal 30. Then, the administrator checks the performance line of the Gantt chart and determines the validity of the planned line.

(Evaluation process)
Next, the evaluation process will be described with reference to FIG. This evaluation process is executed after the implementation of the project.

  First, the control unit 21 of the management server 20 executes a process of acquiring performance information in which a performance line is predicted based on a planned line (step S10-1). Specifically, the evaluation unit 217 of the control unit 21 acquires the result management record 250 from the result information storage unit 25.

  Next, the control unit 21 of the management server 20 performs a comparison process with the prediction result (Step S10-2). Specifically, the evaluation unit 217 of the control unit 21 creates a performance line on the Gantt chart using the performance management record 250. Further, the evaluation unit 217 arranges the performance line created based on the scheduled line and the predicted performance line on the Gantt chart. In this case, the evaluation unit 217 specifies a critical path on the performance line and the predicted performance line of the Gantt chart.

  Further, the evaluation unit 217 acquires an incident report from the incident information storage unit 26, and specifies an incident that has actually occurred. Then, the evaluation unit 217 creates a comparison table between the predicted incident and the occurred incident.

  Next, the control unit 21 of the management server 20 executes a comparison result output process (Step S10-3). Specifically, the evaluation unit 217 of the control unit 21 outputs the comparison result to the display of the management terminal 30. In this case, the administrator checks the comparison result and evaluates the validity of the prediction. Specifically, when it is determined that the difference between the prediction result and the actual result is small, the prediction model is determined to be valid. On the other hand, if it is determined that the deviation of the prediction result from the actual result is large, the learning process is executed again to reconstruct the prediction model.

As described above, according to the present embodiment, the following effects can be obtained.
(2-1) In the present embodiment, the control unit 21 of the management server 20 performs the incident event input process (Step S8-1), the similar event designation process (Step S8-2), and the machine learning process (Step S8-). Execute 3). Thereby, a similar incident can be specified efficiently.

  (2-2) In the present embodiment, the control unit 21 of the management server 20 acquires the schedule information and the result information (step S8-4), creates the teacher data (step S8-5), and executes the machine learning process (step S8-5). Step S8-6) is executed. Here, an actual line prediction model and an incident prediction model are created. As a result, it is possible to predict a performance line or an incident that may occur based on the planned line.

  (2-3) In the present embodiment, the control unit 21 of the management server 20 executes a process of acquiring new schedule information (step S9-1) and a process of predicting an actual line and an incident (step S9-2). Thus, the validity of the required time can be determined based on the predicted performance line. Further, it is possible to predict a task in which an incident may occur.

  (2-4) In the present embodiment, the control unit 21 of the management server 20 executes a process of calculating the critical path and the difference between the forecast and the actual (step S9-3). This makes it possible to predict a critical path and a forecast-real difference based on the predicted performance line.

  (2-5) In the present embodiment, the control unit 21 of the management server 20 acquires the performance information that predicted the performance line based on the planned line (step S10-1), and compares the result with the prediction result (step S10). -2), a comparison result output process (step S10-3) is executed. Thereby, the validity of the prediction model can be determined. Then, the prediction model can be re-learned as necessary.

This embodiment can be implemented with the following modifications. The present embodiment and the following modifications can be implemented in combination with each other within a technically consistent range.
In the above embodiments, the user terminal 10, the management server 20, and the management terminal 30 are used. The hardware configuration is not limited to this. For example, they may be configured integrally. Further, the project management unit 213 may be provided in the management terminal 30.
In the above embodiments, the basic information storage unit 22 records basic management data relating to the tasks that make up the project. In the basic information storage unit 22, a large item management record 221, a medium item management record 222, and a task management record 223 are recorded. If the hierarchy from the large item to the task can be specified, the method of configuring the record is not limited to the large item management record to the task management record. For example, each ID of the medium item and the large item to which each task belongs may be recorded in the task management record. Further, the hierarchy is not limited to three layers.

  In each of the above embodiments, the control unit 21 of the management server 20 executes a scheduled line creation process (step S1-6). Here, if there is a conflicting task in which resources are duplicated when the scheduled line is created, the required period may be adjusted as necessary. In this case, the basic information storage unit 22 stores system capacity, man-hour information, team personnel number information (human resources) in association with the system ID, and information on the task load in association with the task ID. Then, the control unit 21 uses the schedule information storage unit 24 to search the schedule management record 240 of the competing task in which the same system ID is recorded and executed at the same time. When such a plurality of competing tasks are extracted, the control unit 21 acquires information about the system capability, task load, and human resources from the basic information storage unit 22. Then, when the control unit 21 determines that the task load is large with respect to the system capacity and the human resources, the control unit 21 adjusts the required period to be long.

  Further, the scheduled start date and time may be changed so that the task of the same period is not executed. In this case, a backward search is performed to delay the scheduled start date and time of the competing task that has little effect on other tasks.

  In the above embodiments, the schedule information storage unit 24 records the schedule management record 240 for the work. The schedule management record 240 records data relating to the action. Here, the control unit 21 of the management server 20 may machine-learn the transmission range of the alarm as an action. For example, the range of influence when a delay or an incident occurs is extracted by backward search. Then, the extracted task may be specified by a person in charge or a department in charge. Further, for an incident, machine learning may be performed using an actual action recorded in the performance information storage unit 25 as an output layer.

  In each of the above embodiments, the control unit 21 of the management server 20 executes the process of specifying the selected task (Step S2-1). Specifically, the administrator specifies a task line desired to be searched in the tasks on the Gantt chart displayed on the display of the management terminal 30. The method for specifying the selected task is not limited to this. For example, the task ID may be directly input.

  DESCRIPTION OF SYMBOLS 10 ... User terminal, 11 ... Control part, 111 ... Spreadsheet part, 112 ... Result input part, 113 ... Storage part, 121 ... Work item list file, 122 ... Result input file, 20 ... Management server, 21 ... Control part, 211 ... information acquisition unit, 212 ... database management unit, 213 ... project management unit, 215 ... learning unit, 216 ... prediction unit, 217 ... evaluation unit, 22 ... basic information storage unit, 23 ... work item information storage unit, 24 ... Schedule information storage unit, 25: Actual information storage unit, 26: Incident information storage unit, 27: Model information storage unit, 30: Management terminal, H10: Information processing device, H11: Communication interface, H12: Input device, H13: Display Device, H14: storage unit, H15: processor.

Claims (12)

A basic information storage unit that records preceding and succeeding relationship information for preceding and succeeding tasks,
A schedule information storage unit for recording schedule information including a start time and a required time for each task;
A task management support system including a plurality of user terminals and a control unit connected to the management terminal,
The control unit includes:
From the plurality of user terminals, obtain schedule information of a task, record in the schedule information storage unit,
Using the preceding and succeeding relationship information recorded in the basic information storage unit, associating a plurality of tasks recorded in the schedule information storage unit and creating a time chart including a schedule line based on the start time and the required time And
Outputting a time chart including other tasks associated with the preceding / succeeding relationship information recorded in the basic information storage unit to the user terminal for the task selected in the time chart, wherein the task management support is provided. system. For each task, further comprising a result information storage unit that records result information including the start time and the end time,
The control unit includes:
From the user terminal, obtain task information including task identification information, the start time and the end time, and record the result information in the result information storage unit,
Using the preceding and succeeding relationship information recorded in the basic information storage unit, associating a plurality of tasks recorded in the performance information storage unit, based on the start time and the end time, in the time chart, 2. The task management support system according to claim 1, wherein a performance line corresponding to the scheduled line is output. The control unit includes:
If the time included in the performance information is later than the time included in the time chart, the subsequent task is specified using the preceding and succeeding relationship information recorded in the basic information storage unit,
The task management support system according to claim 2, wherein the schedule line of the subsequent task is changed based on the delay. The control unit includes:
If the time included in the performance information is later than the time included in the time chart, the subsequent task is specified using the preceding and succeeding relationship information recorded in the basic information storage unit,
The task management support system according to claim 2, wherein the subsequent task is changed to a scheduled line delayed by a predetermined period. In the schedule information storage unit, a task serving as a checkpoint for checking the work status is recorded,
The method according to claim 1, wherein, when acquiring the delay information of the task, the control unit specifies a checkpoint subsequent to the task, and performs an action according to a delay status of the checkpoint. The task management support system according to claim 1. The schedule information storage unit records information for specifying importance for each task,
The said control part specifies the importance of the said task, and acquires the delay of a task, and performs the action according to the said importance, The Claim 1 characterized by the above-mentioned. Task management support system. The control unit includes:
Using a scheduled line in the time chart for the input layer, generating a performance line prediction model by performing machine learning using teacher data set in the output layer the performance line of each task for the planned line,
The task management support according to any one of claims 1 to 6, wherein when a time chart including a new scheduled line is acquired, a predicted actual line is calculated using the actual line prediction model. system.   The task management support system according to claim 7, wherein the control unit specifies a critical path using the predicted performance line, and sets a checkpoint for checking a work status in the critical path. The control unit includes:
Based on the content of the incident that has occurred, generate an incident event model by performing machine learning using teacher data set to classify similar incidents in the output layer,
The task management according to any one of claims 1 to 8, wherein when the content of occurrence of a newly generated incident is acquired, a classification of similar incidents is predicted using the incident event model. Support system. The control unit includes:
Generates an incident prediction model by performing machine learning using the time chart including the planned line in the input layer and performing training using the incident information generated in the results of the planned line and similar incidents in the output layer. And
The task management support system according to any one of claims 1 to 9, wherein when a time chart including a new scheduled line is acquired, a similar incident is predicted using the incident prediction model. . A basic information storage unit that records preceding and succeeding relationship information for preceding and succeeding tasks,
A schedule information storage unit for recording schedule information including a start time and a required time for each task;
A method for performing task management support using a task management support system including a plurality of user terminals and a control unit connected to the management terminal,
The control unit includes:
From the plurality of user terminals, obtain schedule information of a task, record in the schedule information storage unit,
Using the preceding and succeeding relationship information recorded in the basic information storage unit, associating a plurality of tasks recorded in the schedule information storage unit and creating a time chart including a schedule line based on the start time and the required time And
Outputting a time chart including other tasks associated with the preceding / succeeding relationship information recorded in the basic information storage unit to the user terminal for the task selected in the time chart, wherein the task management support is provided. Method. A basic information storage unit that records preceding and succeeding relationship information for preceding and succeeding tasks,
A schedule information storage unit for recording schedule information including a start time and a required time for each task;
A program for performing task management support using a task management support system including a plurality of user terminals and a control unit connected to the management terminal,
The control unit,
From the plurality of user terminals, obtain schedule information of a task, record in the schedule information storage unit,
Using the preceding and succeeding relationship information recorded in the basic information storage unit, associating a plurality of tasks recorded in the schedule information storage unit and creating a time chart including a schedule line based on the start time and the required time And
For the task selected in the time chart, a function to output to the user terminal a time chart including other tasks associated with the preceding and succeeding relationship information recorded in the basic information storage unit, Task management support program to do.

Images