Management device, management method, and management program

Abstract

An acquisition unit (15a) acquires task information that indicates a task in work for each person in charge and a period for which the person in charge is responsible. A completion unit (15b) uses incomplete date information which is included in the acquired task information and the period for which the person is responsible to complete the date information of each piece of the task information.

Description

[Technical Field]

[0001] The present invention relates to a management device, a management method, and a management program. [Background technology]

[0002] Conventionally, a list-type task management tool using a spreadsheet is known for handing over business knowledge (see Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] “How to manage tasks in Excel and how to create a management sheet,” [online], 2019, Jooto, [Retrieved January 31, 2022], Internet<URL:https: / / www.jooto.com / contents / excel-task-management / > Summary of the Invention [Problem to be solved by the invention]

[0004] However, with conventional technology, it can be difficult to transfer tasks between multiple generations of people. For example, conventional technology assumes a one-to-one task handover from the original to the new one. Therefore, for example, if a person two generations into the future wants to understand the tasks of the person two generations before as knowledge, it is necessary to manage a separate spreadsheet, which is an issue.

[0005] Furthermore, because it is difficult to systematically process information about task dates, the frequency of tasks that are useful for creating handover information must be manually identified and estimated. Furthermore, in the case of spreadsheets, task management is assumed to be done manually, so depending on the workload and the status of the task, there is a possibility that some entries may be omitted. This makes it particularly difficult to accumulate knowledge about "when tasks will occur."

[0006] The present invention has been made in view of the above, and has as its object to easily enable the handover of work between people in charge across multiple generations. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the objectives, the management device of the present invention is characterized by having an acquisition unit that acquires task information representing the business work of each person in charge and the period of responsibility of each person in charge, and a completion unit that uses the date information and the period of responsibility contained in the acquired task information to complete incomplete date information in each task information. [Effects of the Invention]

[0008] According to the present invention, it is possible to easily transfer work between people in charge across multiple generations. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram for explaining an overview of a management device according to this embodiment. [Figure 2] FIG. 2 is a diagram for explaining an overview of the management device of this embodiment. [Figure 3] FIG. 3 is a diagram for explaining an overview of the management device of this embodiment. [Figure 4] FIG. 4 is a schematic diagram illustrating a schematic configuration of the management device. [Figure 5] FIG. 5 is a diagram illustrating an example of the data configuration of the person-in-charge table. [Figure 6] FIG. 6 is a diagram illustrating an example of the data configuration of the task management table. [Figure 7] FIG. 7 is a diagram illustrating an example of the data configuration of the task frequency table. [Figure 8] FIG. 8 is a diagram for explaining the task management sheet. [Figure 9] FIG. 9 is a diagram for explaining the processing of the search unit. [Figure 10] FIG. 10 is a flowchart showing the management processing procedure. [Figure 11] FIG. 11 is a flowchart showing the management processing procedure. [Figure 12] FIG. 12 is a flowchart showing the management processing procedure. [Figure 13] FIG. 13 is a flowchart showing the management processing procedure. [Figure 14] FIG. 14 is a diagram illustrating an example of a computer that executes a management program. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment. In addition, in the description of the drawings, the same parts are designated by the same reference numerals.

[0011] [Overview of management device] 1 to 3 are diagrams for explaining an overview of the management device of this embodiment. First, as shown in FIG. 1, in management device 10, each person in charge creates a task management sheet that lists tasks for each job, and stores the sheet in knowledge DB (DataBase) 14. Management device 10 supplements the data of the start and end dates of tasks in knowledge DB 14 based on the date information in the task management sheet. Furthermore, management device 10 estimates the frequency of execution of each task based on the task name and occurrence date of each task in the task management sheet.

[0012] Furthermore, the management device 10 searches for and presents related tasks from the knowledge DB 14 using the time of task execution, the person in charge, etc. as a query. In particular, the management device 10 extracts the incomplete tasks of the predecessor and outputs them to the successor as handover items. This enables the management device 10 to mediate task management sheets that represent business knowledge between multiple generations of people in charge.

[0013] Specifically, as shown in Figure 2, each person in charge can easily create handover materials such as a list of the tasks they are responsible for, a list of uncompleted items, future annual plans, work attitudes, related contact information, and details of each task, based on the task information stored in the knowledge database 14.

[0014] Furthermore, as illustrated in FIG. 3, the management device 10 manages multiple tasks of a team in the knowledge DB 14, thereby enabling a smooth handover even when the division of roles of the successor is different from that of the predecessor and multiple people take over.

[0015] [Configuration of management device] 4 is a schematic diagram illustrating the overall configuration of a management device. As illustrated in FIG. 1, the management device 10 of this embodiment is realized by a general-purpose computer such as a personal computer, and includes an input unit 11, an output unit 12, a communication control unit 13, a storage unit 14, and a control unit 15.

[0016] The input unit 11 is realized using input devices such as a keyboard and a mouse, and inputs various instruction information such as a command to start processing to the control unit 15 in response to input operations by an operator. The output unit 12 is realized by a display device such as a liquid crystal display, a printing device such as a printer, etc. For example, the output unit 12 displays the results of the management processing described below.

[0017] The communication control unit 13 is realized by a NIC (Network Interface Card) or the like, and controls communication between the control unit 15 and external devices via telecommunication lines such as a LAN (Local Area Network) or the Internet. For example, the communication control unit 13 controls communication between the control unit 15 and an information terminal operated by a person in charge of a task, a server that manages information about the person in charge, or the like.

[0018] The storage unit 14 is realized by a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 14 stores in advance the processing programs that operate the management device 10 and data used during the execution of the processing programs, or temporarily stores them each time processing is performed. The storage unit 14 may be configured to communicate with the control unit 15 via the communication control unit 13.

[0019] In this embodiment, the storage unit 14 stores, as the knowledge DB, a person in charge table 14a, a task management table 14b, and a task frequency table 14c.

[0020] 5 is a diagram illustrating an example of the data configuration of the person in charge table 14a. As illustrated in the example of Fig. 5, the person in charge table 14a includes the name of the person in charge of the work, the start date of the work, and the end date of the work, with the person in charge label as key information.

[0021] The person in charge label is information that identifies the person in charge. The start date and end date indicate the period during which the person in charge is responsible for the work. Figure 5 shows an example of a person in charge label "T001", name "Yamada Taro", start date "2014 / 7 / 1", and end date "2017 / 6 / 30".

[0022] In this embodiment, the person in charge table 14a is acquired in advance of the management process described below from an information terminal operated by the person in charge of the work, a server that manages information about the person in charge, or the like, and is stored in the storage unit 14. Note that this information terminal may be implemented in the same hardware as the management device 10.

[0023] Furthermore, the person in charge table 14a does not necessarily have to be stored in the storage unit 14, but may be collected, for example, when a management process described later is executed. In this case, for example, the acquiring unit 15a described later may collect information for the person in charge table 14a from an information terminal of the person in charge, a server that manages information about the person in charge, or the like, prior to the process.

[0024] 6 is a diagram illustrating an example of the data configuration of a task management table. Task management table 14b is generated in a management process described below. As illustrated in FIG. 6, task management table 14b includes task information such as task name, category, start date, deadline, status, and details, similar to a task management sheet described below. Task management table 14b also includes a responsible person label.

[0025] 7 is a diagram illustrating an example of the data configuration of the task frequency table 14c. As illustrated in FIG. 7, the task frequency table 14c includes information on task name, category, occurrence date, and frequency. The task frequency table 14c is generated in a management process described later.

[0026] Returning to the explanation of FIG. 4, the control unit 15 is realized using a CPU (Central Processing Unit) or the like, and executes a processing program stored in memory. As a result, the control unit 15 functions as an acquisition unit 15a, a complementation unit 15b, an estimation unit 15c, and a search unit 15d, as exemplified in FIG. 4, to execute the management process. Note that these functional units may be implemented individually or in part in different hardware. For example, the search unit 15d may be implemented in a search device or the like that is different from the other functional units. The control unit 15 may also include other functional units.

[0027] That is, the management device 10 may be in a standalone format implemented by a single computer, an on-premise format implemented by two or more on-premise computers, or a cloud format implemented by two or more computers including one or more off-premise computers.

[0028] The acquisition unit 15a acquires task information representing the business work of each person in charge and the period of responsibility of each person in charge. Specifically, the acquisition unit 15a acquires a task management sheet, which is task information showing a list of tasks for each person in charge, via the input unit 11 or from the information terminal of each person in charge via the communication control unit 13. The acquisition unit 15a may acquire the task management sheet via the communication control unit 13 from a server or the like that has collected the task management sheets from the information terminals of the people in charge. The acquisition unit 15a accumulates the task information included in the acquired task management sheet for each person in charge as the task management table 14b.

[0029] Here, Fig. 8 is a diagram for explaining the task management sheet. As shown in Fig. 8, the task management sheet includes task information such as task name, category, start date, deadline, status, and details.

[0030] The task name is text information indicating the name of the task. The category is text information indicating the classification of the task. Figure 8 shows an example of the task name "2019 Network Maintenance Contract" and the category "Network Maintenance."

[0031] The start date is information in date format that indicates the estimated date by which the task should be started, and the deadline is information in date format that indicates the date by which the task should be completed. Figure 8 shows examples of start date "2 / 19" and deadline date "2 / 25".

[0032] The status is information that indicates the degree of progress of the task, such as "Complete," "In progress," "As needed," "Not required," "On hold," "Scheduled," or "Waiting for a response," and is updated by the person in charge according to the state of the task. Details are detailed text-based information about the task, such as notes on the progress of the task, points to be devised, or matters to be handed over, and can be freely written by the person in charge.

[0033] Each time a task for his / her work arises, the person in charge adds the task to the task management sheet of the information terminal in chronological order. The acquisition unit 15a then collects the task management sheets filled out by each person in charge. The acquisition unit 15a also acquires the period of responsibility for each person, consisting of the start date and end date of the responsibility, from the person in charge table 14a.

[0034] Returning to the explanation of Fig. 4, the completion unit 15b completes incomplete date information for each piece of task information by using date information included in the acquired task information and the period of responsibility of each person in charge. Specifically, the completion unit 15b completes the date information to be set in the task management table 14b by using the task management sheet shown in Fig. 8 and the period of responsibility of each person in charge acquired from the person in charge table 14a shown in Fig. 5.

[0035] For example, the completion unit 15b completes the year for the start date and deadline in the month-date format in the task management sheet for the person in charge shown in Fig. 6 so that they correspond to the period of responsibility of the person in charge and registers them in the task management table 14b. For example, in the task management sheet illustrated in Fig. 8, the start date and deadline are in month-date format. Meanwhile, in the task management table 14b illustrated in Fig. 6, for the task information of the person in charge label "T003," the start date and deadline are completed with the year "2019 / " and set in year-month-day format, taking into consideration the period from the start date "2 / 1 / 2019" to the end date "4 / 30 / 2021," which is the period of responsibility of this person in charge, and the chronological order of each task.

[0036] Furthermore, the complementing unit 15b sets null to both the start date and the deadline for task information that does not require a specific period for task execution, such as when the status is "unnecessary" or "on hold."

[0037] Furthermore, for task information whose status is "as needed," the completion unit 15b sets the start date of the task as the start date and the end date of the task as the deadline, since the task is occurring continuously during the period of the person in charge. Furthermore, if the deadline is not written on the task management sheet, the completion unit 15b provisionally sets a date one year from today (processing date) or the like.

[0038] Furthermore, the deadline of the task information is information that is set based on the content of the task, regardless of the order in which the tasks are entered, and may be set beyond the period of responsibility of the person in charge. Therefore, the complementing unit 15b does not complement deadlines that are not written in the task management sheet.

[0039] Returning to the description of FIG. 4, the estimation unit 15c estimates the execution frequency of each task using the task name and occurrence date included in the task information. For example, the estimation unit 15c extracts a noun set from the task name of each piece of task information in the task management table 14b through morphological analysis. Then, the estimation unit 15c calculates the similarity between the noun sets included in each task name. For example, the estimation unit 15c calculates the similarity between the noun sets using a Simpson coefficient, which is an index of the strength of the frequency of nouns co-occurring in a document.

[0040] The estimation unit 15c classifies task information whose calculated similarity is equal to or greater than a predetermined threshold as the same task. Furthermore, the estimation unit 15c estimates that the noun with the highest appearance frequency among the task information classified into the same task is the task name of the classification.

[0041] The estimation unit 15c also arranges task information classified into the same task in chronological order and estimates the execution frequency. Specifically, the estimation unit 15c calculates the average and variation of the difference between the execution dates (execution intervals) by using, for example, the occurrence date, i.e., the start date, of each task information as the execution date of each task.

[0042] If the variation in the calculated difference for a day is less than a predetermined threshold, the estimation unit 15c estimates that there is periodicity for the day, and sets the frequency of the task in the task frequency table 14c shown in Fig. 7. For example, the estimation unit 15c sets the date of occurrence of the first task in the task frequency table 14c, and sets the average of the difference as the frequency.

[0043] On the other hand, if the variance in the calculated differences for each day is equal to or greater than a predetermined threshold, the estimation unit 15c checks for monthly periodicity. That is, if the variance in the calculated differences for each month is less than a predetermined threshold, the estimation unit 15c estimates that there is monthly periodicity and sets the frequency of the task in the task frequency table 14c. For example, the estimation unit 15c sets the year and month of the first task to the occurrence date in the task frequency table 14c, and sets the average difference to the frequency.

[0044] On the other hand, if the variance in the calculated differences for each month is equal to or greater than a predetermined threshold, the estimation unit 15c checks for yearly periodicity. That is, if the variance in the calculated differences for each year is less than a predetermined threshold, the estimation unit 15c estimates that there is yearly periodicity and sets the frequency of the task in the task frequency table 14c. For example, the estimation unit 15c sets the year of the first task to the occurrence date in the task frequency table 14c, and sets the average difference to the frequency.

[0045] On the other hand, if the variation in the calculated difference for a year is equal to or greater than a predetermined threshold, the estimation unit 15c estimates that the task is not performed regularly and sets the frequency in the task frequency table 14c to "irregular."

[0046] Note that the estimation of the frequency of a task by the estimation unit 15c is not limited to the case where the task name is used. For example, the estimation unit 15c may estimate the frequency of a task by performing the same process as described above on a category instead of a task name.

[0047] The search unit 15d searches for task information including the specified task or person in charge from the supplemented task information. Specifically, the search unit 15d searches the task management table 14b using the task execution time, task category, person in charge, etc. as a query. This enables the successor to extract tasks related to his or her own work.

[0048] The search unit 15d extracts tasks that have not been completed by the previous person in charge. For example, the search unit 15d extracts incomplete tasks whose status in the task management table 14b is “in progress,” “planned,” “on hold,” etc., and outputs the extracted tasks to the successor.

[0049] Here, Fig. 9 is a diagram for explaining the processing of the search unit. As illustrated in Fig. 9, the search unit 15d can output the uncompleted tasks of a predecessor to a successor. In the example illustrated in Fig. 9, the extracted uncompleted tasks are output in the format of the task management sheet illustrated in Fig. 8. This makes it easy to hand over the tasks to the successor.

[0050] [Administrative Processing] Next, the management process by the management device 10 according to this embodiment will be described with reference to Fig. 10 to Fig. 13. Fig. 10 to Fig. 13 are flowcharts showing the management process procedure. First, the flowchart in Fig. 10 starts, for example, when the user performs an operation input to instruct the start of the process.

[0051] First, the acquisition unit 15a acquires a task management sheet for each person in charge and information about each person in charge, including the period of responsibility of each person in charge (step S1).

[0052] Next, the complementing unit 15b complements the incomplete date information of each task information by using the date information included in the acquired task information and the period of each person in charge (step S2). Also, the estimation unit 15c estimates the execution frequency of each task by using the task name and occurrence date included in the task information (step S3).

[0053] The acquiring unit 15a also generates a task management table 14b and stores the information of the acquired task management sheet. The acquiring unit 15a also generates the person in charge table 14a using the information of the person in charge. The complementing unit 15b then updates the task management table 14b with the complemented date information. The estimating unit 15c also generates a task frequency table 14c and sets the estimated execution frequency of each task (step S4). This completes the series of management processes.

[0054] Next, Fig. 11 shows the processing procedure of step S2 shown in Fig. 10. First, the complementing unit 15b sets y1 to the assignment start year and d1 to the assignment start date for i=1 of the ith (1≦i≦m) task information in the task management sheet for each person in charge (step S11). Also, if the assignment end date of this person in charge is null (step S12, Yes), the assignment end date is temporarily set to, for example, today's date one year in the future (step S13).

[0055] On the other hand, if the end date of the work for this person in charge is not null (No at Step S12) and i is less than m (Yes at Step S14), the complementing unit 15b checks the status (Step S15).

[0056] If the status is "in progress," "scheduled," "waiting for response," or "completed," and the start date is not null (No in step S18), the complementing unit 15b sets d1 as the start date (step S19) and proceeds to step S21. On the other hand, if the start date is null (Yes in step S18), the complementing unit 15b sets d1 as the start date (step S20) and proceeds to step S21.

[0057] Next, if the start date is within the responsible period of the person in charge (Yes at Step S21), the complementing unit 15b sets y1 as the year of the start date (Step S22) and proceeds to Step S24. On the other hand, if the start date is not within the responsible period of the person in charge (No at Step S21), the complementing unit 15b sets y1 as the year of the start date and proceeds to Step S24.

[0058] If the status is either "unnecessary" or "suspended," the complementing unit 15b sets the start date and deadline to null (step S16), and the process proceeds to step S24.

[0059] If the status is "as needed," the complementing unit 15b sets the start date as the in-charge start date and the deadline as the in-charge end date (step S17), and proceeds to step S24.

[0060] In the process of step S24, i is set to i+1, and the process returns to step S14. If i=m (step S14, No), the complementing unit 15b ends the series of processes.

[0061] 12 shows the processing procedure of step S3 shown in FIG. 10. First, the estimation unit 15c extracts a noun set by morphological analysis for the task name of each piece of task information in the task management table 14b (step S31). Then, the estimation unit 15c calculates the similarity between the noun sets held by each task name (step S32). For example, the estimation unit 15c calculates the similarity between the noun sets using a Simpson coefficient, which is an index of the strength of the frequency of nouns co-occurring in a document.

[0062] The estimation unit 15c classifies task information whose calculated similarity is equal to or greater than a predetermined threshold as the same task (step S33). Furthermore, the estimation unit 15c estimates that the noun with the highest appearance frequency among the task information classified into the same task is the task name of the classification (step S34).

[0063] The estimation unit 15c also arranges the task information classified into the same task in chronological order and estimates the execution frequency. For example, the estimation unit 15c calculates the average and variation of the difference between the execution dates (execution intervals) by using the occurrence date (start date) of each piece of task information as the execution date of each task (step S35).

[0064] If the variation in the calculated difference for a day is less than a predetermined threshold (No in step S36), the estimation unit 15c estimates that there is periodicity with respect to the day, and sets the task frequency in the task frequency table 14c, such as every xx days from year x month △ day (step S37). For example, the estimation unit 15c sets the year, month, and date of the first task to the occurrence date in the task frequency table 14c, and sets the average difference to the frequency. This completes the series of processes.

[0065] On the other hand, if the variance in the calculated difference for each day is equal to or greater than a predetermined threshold (step S36, Yes), the estimation unit 15c checks the periodicity for each month. That is, if the variance in the calculated difference for each month is less than a predetermined threshold (step S38, No), the estimation unit 15c estimates that there is periodicity for each month, and sets the task frequency in the task frequency table 14c, for example, every x months, based on year x month (step S39). For example, the estimation unit 15c sets the year and month of the first task to the occurrence date in the task frequency table 14c, and sets the average difference to the frequency. This completes the process.

[0066] On the other hand, if the variation in the calculated difference for each month is equal to or greater than a predetermined threshold (step S38, Yes), the estimation unit 15c checks for periodicity for each year. That is, if the variation in the calculated difference for each year is less than a predetermined threshold (step S40, No), the estimation unit 15c estimates that there is periodicity for each year and sets the frequency of the task in the task frequency table 14c, such as every x years starting from x year, △ month (step S41). For example, the estimation unit 15c sets the year of the first task to the occurrence date in the task frequency table 14c, and sets the average difference as the frequency. This completes the series of processes.

[0067] On the other hand, if the variation in the calculated difference for a year is equal to or greater than the predetermined threshold (Yes in step S40), the estimation unit 15c estimates that the task is not performed regularly, and sets the frequency in the task frequency table 14c to "irregular" (step S42). This completes the series of processes.

[0068] 13 shows the processing procedure of the search unit 15d. The search unit 15d searches the complemented task information for task information that includes the specified task or person in charge. For example, the search unit 15d extracts task information that corresponds to the specified person in charge, such as a predecessor, and the category from the task management table 14b (step S51).

[0069] Furthermore, the search unit 15d extracts incomplete task information with a status such as "in progress," "scheduled," "waiting for a response," or "as needed" from the extracted task information (step S52).

[0070] Then, the search unit 15d outputs the extracted task information to the successor in the form of a task management sheet (step S53), thereby completing the series of processes.

[0071] [effect] As described above, in the management device 10 of this embodiment, the acquisition unit 15a acquires task information representing work performed by each person in charge and the period of responsibility of each person in charge. Furthermore, the complementation unit 15b complements incomplete date information in each piece of task information by using the date information and the period of responsibility included in the acquired task information.

[0072] This allows the management device 10 to estimate and supplement the time when task information has been omitted, enabling the chronological management of task information for multiple personnel. Therefore, even when multiple successors have different roles than their predecessors, the handover can be carried out smoothly. In this way, business knowledge can be managed between multiple generations of personnel, making it easy to hand over tasks.

[0073] Furthermore, the estimation unit 15c estimates the frequency of execution of each task using the task name and occurrence date included in the task information, which makes it easy to grasp the occurrence frequency of the task that the successor will take over.

[0074] Furthermore, the search unit 15d searches for task information including the specified task or person in charge from the supplemented task information, which allows the successor to easily extract tasks related to his or her own work.

[0075] The search unit 15d extracts tasks that have not been completed by the previous person in charge, which makes it easier for the successor to take over the work.

[0076] [program] A program written in a computer-executable language may be created to execute the processes executed by the management device 10 according to the above embodiment. In one embodiment, the management device 10 can be implemented by installing a management program that executes the above management processes as package software or online software on a desired computer. For example, by executing the above management program on an information processing device, the information processing device can function as the management device 10. The information processing device referred to here includes desktop and notebook personal computers. Other examples of information processing devices include mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone Systems), as well as slate terminals such as PDAs (Personal Digital Assistants). The functions of the management device 10 may also be implemented on a cloud server.

[0077] 14 is a diagram showing an example of a computer that executes a management program. The computer 1000 includes, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These components are connected by a bus 1080.

[0078] The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012. The ROM 1011 stores, for example, a boot program such as a BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to a hard disk drive 1031. The disk drive interface 1040 is connected to a disk drive 1041. A removable storage medium such as a magnetic disk or optical disk is inserted into the disk drive 1041. The serial port interface 1050 is connected to, for example, a mouse 1051 and a keyboard 1052. The video adapter 1060 is connected to, for example, a display 1061.

[0079] Here, the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. Each piece of information described in the above embodiment is stored in the hard disk drive 1031 or memory 1010, for example.

[0080] The management program is stored in the hard disk drive 1031 as, for example, a program module 1093 in which commands to be executed by the computer 1000 are written. Specifically, the program module 1093 in which each process executed by the management device 10 described in the above embodiment is written is stored in the hard disk drive 1031.

[0081] Furthermore, data used for information processing by the management program is stored as program data 1094, for example, in the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and program data 1094 stored in the hard disk drive 1031 into the RAM 1012 as necessary, and executes each of the above-described procedures.

[0082] The program module 1093 and program data 1094 related to the management program are not limited to being stored in the hard disk drive 1031, but may be stored in a removable storage medium, for example, and read by the CPU 1020 via the disk drive 1041 or the like. Alternatively, the program module 1093 and program data 1094 related to the management program may be stored in another computer connected via a network such as a LAN or a WAN (Wide Area Network), and read by the CPU 1020 via the network interface 1070.

[0083] Although the present invention has been described above as an embodiment, the present invention is not limited to the description and drawings that form part of the disclosure of the present invention. In other words, other embodiments, examples, and operational techniques that can be made by those skilled in the art based on the present invention are all included in the scope of the present invention. [Explanation of symbols]

[0084] 10 Management device 11 Input section 12 Output section 13 Communication control section 14 Memory section (knowledge DB) 14a Personnel Table 14b Task Management Table 14c Task Frequency Table 15 Control Unit 15a Acquisition part 15b Complement part 15c Estimation part 15d Search Section

Claims

1. an acquisition unit that acquires task information representing the business work of each person in charge and the period of responsibility of each person in charge; a completion unit that completes incomplete date information of each task information by using date information and the assigned period included in the acquired task information; an estimation unit that uses the task names and occurrence dates included in the task information with the dates supplemented to estimate identical tasks using similarities between noun sets extracted from each task name, determines whether the identical tasks are performed regularly using variations in the intervals between the tasks, and estimates the frequency of each task performed by using an average of the intervals between the tasks for tasks that are determined to be periodically performed; A management device comprising:

2. 2. The management device according to claim 1, further comprising a search unit that searches the supplemented task information for task information that includes a specified task or person in charge.

3. The management device according to claim 2 , wherein the search unit extracts tasks that have not been completed by past responsible parties.

4. A management method executed by a management device, an acquisition step of acquiring task information representing the work performed by each person in charge and the period of responsibility of each person in charge; a supplementing step of supplementing incomplete date information of each piece of task information using date information and the assigned period included in the acquired task information; an estimation step of estimating identical tasks using the similarity between noun sets extracted from each task name using the task names and occurrence dates included in the task information with the dates supplemented, determining whether the identical tasks are performed regularly using the variance in the intervals between the tasks, and estimating the frequency of each task performed by using the average interval between the tasks for tasks determined to be periodically performed; A management method comprising:

5. an acquisition step of acquiring task information representing the business work of each person in charge and the period of responsibility of each person in charge; a supplementation step of supplementing incomplete date information of each task information by using date information and the assigned period included in the acquired task information; an estimation step of estimating identical tasks using the task names and occurrence dates included in the task information with the dates supplemented and the similarity between noun sets extracted from each task name, determining whether the identical tasks are performed regularly using the variation in the intervals between the tasks, and estimating the frequency of each task performed by using the average interval between the tasks for tasks determined to be periodically performed; A management program that allows a computer to execute the following.

Images