Task management program and task management system

Abstract

To customize a free template, and to output a flowchart showing the latest task execution status.SOLUTION: A task management program that manages a task by customizing a free template causes a computer to execute: processing (S1) of accepting input of information that identifies task contents; processing (S2) of accepting input of a required period to complete the task; processing (S3) of accepting registration of staff involved in execution of the task; processing (S4) of accepting input of information showing progress status of the task; and processing (S5) of outputting a flowchart showing the latest task execution status based on each piece of the input information.SELECTED DRAWING: Figure 7A

Description

[Technical field]

[0001] The present invention relates to a task management program and a task management system that manages tasks by customizing a free template. [Background technology]

[0002] In recent years, methods of electronically managing schedules using a PC (Personal Computer) or a PDA (Personal Digital Assistant) have become known. Patent Document 1 discloses a method of electronically managing schedules, in which a user's planned activities are registered from a terminal device such as a PC to a server device. In the method described in Patent Document 1, a planned activity input by a user is accepted and registered as provisional data, the user is notified to complete the provisional data by the scheduled time, and an accurate planned activity is accepted from the user and registered as the actual data. This makes it possible to simply, quickly, and reliably register a planned activity.

[0003] Patent Document 2 also discloses a technique that allows a user to simultaneously register related schedules without being aware of it when registering a schedule. In this technique, complementary actions that complement the actions of the main schedule registered by the registrant are stored in advance in a server device that registers the schedule. When the server device accepts registration of a main schedule from a PC via a network, the server device determines whether or not there are complementary actions that complement the actions of the main schedule. If there is complementary information, the server device generates and registers a complementary schedule related to the complementary actions. This allows a user to simply input their own schedule and register schedules that are not input by the user but are necessary for the input schedule. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2003-256384 A [Patent Document 2] JP 2011-180908 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the conventional technology, a fixed template is used, and a "free template" that can be freely determined according to the content is not used. Also, even if a task is registered or updated, the latest task execution status is not displayed.

[0006] The present invention has been made in consideration of the above circumstances, and has an object to provide a task management program and a task management system that can customize free templates and output a flowchart showing the latest task execution status. [Means for solving the problem]

[0007] (1) In order to achieve the above object, the present invention provides the following means. That is, the task management program of the present invention is a task management program that manages tasks by customizing a free template, and is characterized in that it causes a computer to execute the following processes: accepting input of information that specifies the content of a task, accepting input of a period required to complete the task, accepting registration of staff involved in the execution of the task, accepting input of information showing the progress of the task, and outputting a flowchart showing the latest execution status of the task based on each of the input information.

[0008] This configuration makes it possible to display the latest task execution status, allowing users and staff to easily grasp the progress of the tasks, thereby ensuring that the tasks are completed.

[0009] (2) The task management program of the present invention further includes a process for displaying the tasks and required periods on a calendar, and a process for displaying the flowchart and the calendar on the same screen.

[0010] This configuration makes it possible to display the registration status and progress of tasks along with the calendar.

[0011] (3) Furthermore, the task management program of the present invention is characterized by further including a process for accepting input of information identifying a case requested by a client, and a process for selecting a task required to process the case from among tasks already created or for creating a new task.

[0012] This configuration makes it possible to manage tasks related to cases requested by clients, thereby ensuring that the requested content is completed.

[0013] (4) Furthermore, the task management program of the present invention is characterized by further including a process for accepting selection of tasks to be aggregated, a process for accepting input of a starting point and period to be aggregated, a process for accepting selection of items to be shown on the horizontal axis of the graph and items to be shown on the vertical axis of the graph, a process for aggregating the progress status of the tasks to be aggregated based on the starting point and period, and the items to be shown on the horizontal axis of the graph and the items to be shown on the vertical axis of the graph, and a process for displaying the aggregated progress status of the tasks on a screen as a task dashboard.

[0014] This configuration allows the user to visualize the task completion status according to the task that the user wants to check and the settings of the graph to be displayed, so that the user can easily grasp the task progress, which makes it possible to reliably achieve task completion.

[0015] (5) Furthermore, the task management system of the present invention is a task management system that manages tasks by customizing free templates, and is characterized by having an input unit that accepts input of information identifying the content of the task, accepts input of a period required to complete the task, accepts registration of staff involved in the execution of the task, and accepts input of information indicating the progress of the task, a control unit that outputs a flowchart showing the latest task execution status based on each of the input information, and a recording unit that records each of the input information and the task.

[0016] This configuration makes it possible to display the latest task execution status, allowing users and staff to easily grasp the progress of the tasks, thereby ensuring that the tasks are completed.

[0017] (6) The task management system of the present invention further includes a display unit for displaying images, and the control unit controls the display unit to display the tasks and required time periods on a calendar and to display the flowchart and the calendar on the same screen.

[0018] This configuration makes it possible to display the registration status and progress of tasks along with the calendar.

[0019] (7) Also, in the task management system of the present invention, the input unit accepts input of information identifying a case requested by a client, and the control unit selects a task required to process the case from tasks that have already been created or creates a new one.

[0020] This configuration makes it possible to manage tasks related to cases requested by clients, thereby ensuring that the requested content is completed.

[0021] (8) Also, in the task management system of the present invention, the input unit accepts selection of tasks to be aggregated, accepts input of a starting point and period to be aggregated, and accepts selection of items to be shown on the horizontal axis of the graph and items to be shown on the vertical axis of the graph, and the control unit aggregates the completion status of the tasks to be aggregated based on the starting point and period, and the items to be shown on the horizontal axis of the graph and the items to be shown on the vertical axis of the graph, and displays the aggregated task completion status on the screen of the display unit as a task dashboard.

[0022] This configuration makes it possible to display the latest task execution status, allowing users and staff to easily grasp the progress of the tasks, thereby ensuring that the tasks are completed.

[0023] (9) In the task management system of the present invention, a folder serving as an area for storing information related to each task is added or updated, and a usage authority is given to any of the folders.

[0024] This configuration makes it possible to store, display, and use materials related to a task, making it easier to grasp the progress of the task. Effect of the Invention

[0025] According to the present invention, the latest task execution status can be displayed, so that users and staff can easily grasp the progress of the task, and as a result, it becomes possible to reliably accomplish the task. [Brief description of the drawings]

[0026] [Figure 1] 1 is a diagram illustrating an outline of a hardware configuration of a task management system 1 according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing a functional configuration of a server device 3 according to the present embodiment. [Diagram 3] 1 is a list of example case registration items. [Figure 4] 13 is an example of a display screen showing details of a registered case. [Diagram 5] 11 is a list showing an example of task template registration items. [Figure 6] 13 is an example of a display screen for a registered task template. [Figure 7A] 2 is a basic flowchart of the present embodiment. [Figure 7B] 13 is a flowchart illustrating an example of a task template creation process. [Figure 8] FIG. 11 is a diagram showing an example of a registered task list. [Figure 9] FIG. 11 illustrates an example of a client registration process. [Figure 10] 11 is a list showing an example of client registration items. [Figure 11] 13 is an example of a display screen showing details of a registered client. [Figure 12] 13 is a flowchart showing an example of a staff registration process. [Figure 13] 11 is a list showing an example of staff registration items. [Figure 14] 13 is an example of a display screen showing details of a registered staff member as a system administration account. [Figure 15] This is a list showing the types of authority to be given to staff members when they are registered. [Figure 16] 13 is a flowchart illustrating an example of a case registration process. [Figure 17] 13 is a flowchart showing a folder updating process. [Figure 18] 13 is an example of a display screen for registered folders. [Figure 19] 13 is an example of a display screen for registered folders. [Figure 20] 13 is a flowchart showing a process for posting a parent comment and notifying the user of the parent comment. [Figure 21]13 is a flowchart showing a process of replying to a child comment in response to a parent comment posted and notifying the reply. [Figure 22] 13 is an example of a display screen for a list of registered cases. [Figure 23] 13 is a flowchart showing a process when a case list is used. [Figure 24] 13 is a flowchart showing a process for updating a case status. [Diagram 25] 13 is a flowchart showing a process for using a task list. [Figure 26] 13 is a flowchart showing a process when a task dashboard is used. [Figure 27] FIG. 13 is a diagram illustrating an example of a display of a task dashboard. [Figure 28] 13 is a flowchart showing a process of updating and creating a folder and setting a folder usage authority. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] The inventors noticed that conventional standardized templates made it difficult to manage detailed tasks according to business content, and discovered that by using "free templates" that can be freely determined according to content and visualizing the status of each task, highly convenient task management could be achieved, leading to the invention.

[0028] In other words, the task management program of the present invention is a task management program that manages tasks by customizing a free template, and is characterized in that it causes a computer to execute the following processes: a process of accepting input of information that identifies the content of the task, a process of accepting input of a period required to complete the task, a process of accepting registration of staff involved in the execution of the task, a process of accepting input of information indicating the progress of the task, and a process of outputting a flowchart showing the latest execution status of the task based on each of the input information.

[0029] In this way, the inventors have made it possible to display the latest task execution status, and to allow users and staff to easily grasp the progress of the tasks. As a result, it has become possible to ensure that tasks are completed. Hereinafter, an embodiment of the present invention will be specifically described with reference to the drawings.

[0030] 1 is a diagram showing an outline of the hardware configuration of a task management system 1 according to this embodiment. The server device 3 and the terminal devices 5, 7, and 9 each include hardware such as a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a storage device, and a communication device that enables connection to a network. The CPU reads out a program prestored in the ROM into the RAM as appropriate and executes the program, and controls the operation of each of the above-mentioned hardware components. The ROM stores the program, and is, for example, a static RAM (SRAM), a dynamic RAM (DRAM), or a flash memory. The RAM temporarily stores various data generated when the CPU executes the program.

[0031] The storage device is, for example, a hard disk drive, and stores necessary data and programs. The programs may be installed in the storage device from a recording medium such as a CD-ROM (Compact Disc-ROM) or a DVD-ROM (Digital Versatile Disc-ROM), or may be downloaded from a network for use. The server device 3 and the terminal devices 5, 7, and 9 are configured to be able to communicate with each other via the network.

[0032] FIG. 2 is a block diagram showing the functional configuration of the server device 3 according to this embodiment. The main body function unit 13 has a task management function, a schedule management function, and a business management function. The task registration function unit 15 performs task template registration, client registration, and staff registration based on input from the user. The case registration function unit 17 performs registration of a case requested by a requester. At that time, it selects an existing task or creates a new task. The task list unit 19 has a function of listing and outputting the registered tasks, and extracting and displaying a specified specific task. The case list unit 21 has a function of listing and outputting the registered cases, and extracting and displaying a specified specific case. The data output unit 23 has a function of displaying the task achievement status on the screen as a task dashboard, and displaying the sales status on the screen. The folder management unit 25 performs new folder addition, deletion of existing folders, change of existing folder names, and update of information in the folder based on input from the user. The above-mentioned task registration function unit 15 and case registration function unit 17 constitute an input unit, the main body function unit 13 constitutes a control unit, the task list unit 19 and case list unit 21 constitute a recording unit, and the data output unit 23 constitutes a display unit.

[0033] FIG. 3 is a list showing an example of case registration items. FIG. 4 is an example of a display screen showing details of a registered case. FIG. 5 is a list showing an example of task template registration items. FIG. 6 is an example of a display screen showing a registered task template. FIG. 7A is a basic flowchart, and FIG. 7B is a flowchart showing an example of a task template creation process. In the task management system 1 according to this embodiment, first, input of information specifying the contents of a task is accepted (step S1), input of a period required to complete the task is accepted (step S2), registration of staff involved in the execution of the task is accepted (step S3), and input of information showing the progress of the task is accepted (step S4). Next, a flowchart showing the latest task execution status is output based on each of the input information (step S5).

[0034] In this embodiment, when a task is registered, a task template is created. That is, as shown in FIG. 7B, first, input or selection of items that specify the contents of the task is accepted (step S11). Items that specify the contents of the task include items that indicate the task contents and the planned period required for the task to be completed. More specifically, as shown in FIG. 7B, input or selection of the template title, category, task setting method (how many days in advance or after), weekend and holiday settings (whether to include them in the required period), and task name is accepted.

[0035] Here, the task management system 1 according to this embodiment is provided with items that allow free input (free description). For example, the template, category, and task name are not predetermined, but can be freely selected and input by the user (or operator). Here, it is also possible to select from items that have already been registered.

[0036] Next, in FIG. 7B, it is determined whether or not the "task addition operation" is allowed (step S12), and if the result is NO, the process transitions to step S11. In step S12, if the "task addition operation" is allowed, the task is registered (step S13). Next, it is determined whether or not the next task is added (step S14), and if the next task is added, the process transitions to step S11 and the above operations are repeated. In step S14, if the next task is not added, each item of each registered task is edited (step S15). In step S15, as shown in FIG. 7B, the task color (color displayed on the screen), the selection or new input of the status, the input of the number of days (the number of days elapsed from a specified date or the number of days required until the specified date), and the like are performed. Next, it is determined whether or not the editing of the task in step S15 is completed (step S16), and if the editing of the task is not completed, the process transitions to step S15. On the other hand, in step S16, if the editing of the task is completed, the edited task is registered (step S17), and the process ends.

[0037] As shown in Figure 6, tasks with the name "A" are registered, and the expected completion dates of each task (A to U) are displayed. This makes it easy to know how many days remain until the deadline for each task.

[0038] FIG. 8 is a diagram showing an example of a registered task list. On the right side of the page in FIG. 8, tasks (A to U) are displayed. Clicking on each task makes it possible to display the registered contents of the task. Also, on the left side of the page in FIG. 8, a calendar is displayed, in which tasks (A to U) are displayed. It is also possible to display the task registration table by clicking on a task displayed in the calendar. In this way, by linking each task with the calendar and displaying them on the same screen, it is possible to display the registration status and progress of the task along with the calendar.

[0039] FIG. 9 is a flow chart showing an example of a client registration process, and FIG. 10 is a list showing an example of client registration items. In FIG. 9, first, input of information for identifying the client and information related to settlement, such as the client's company name, telephone number, email address, address, and payment date, is accepted (step S21). For the payment date, for example, as shown in FIG. 10, information related to accounting and settlement, such as "what date is the closing date and what date is the payment date," is input. Next, in FIG. 9, it is determined whether or not the registration operation can be performed (step S22), and if NO, the process transitions to step S21. On the other hand, if it is possible to perform the registration operation in step S22, the client is registered (step S23), and the process ends.

[0040] Figure 11 is an example of a display screen for the details of a registered client. As shown in Figure 11, the registered details such as the client name, registration date, email address, telephone number, address, etc. are displayed on the screen. A client registered in this way can be linked to a task template as a requester and managed as someone involved in the case.

[0041] Fig. 12 is a flow chart showing an example of staff registration processing, and Fig. 13 is a list showing an example of staff registration items. In Fig. 12, first, input of information for identifying a staff member, such as the staff member's email address, password, name, telephone number, address, date of birth, and occupation, is accepted (step S31). Next, it is determined whether or not the registration operation is permitted (step S32), and if NO, the process transitions to step S31. On the other hand, if the registration operation is permitted in step S32, the staff member is registered (step S33), and the process ends.

[0042] Figure 14 is an example of a display screen showing details of a registered staff member as a system administrator account. As shown in Figure 14, the registered information such as the registration date, company, email address, phone number, address, date of birth, and occupation is displayed on the screen. Staff members registered in this way can be linked to task templates and managed as those involved in those tasks.

[0043] Fig. 15 is a list showing the types of authority given to staff members when they are registered. As shown in Fig. 15, the authority given to staff members includes, for example, displaying task list, displaying sales management, displaying task dashboard, displaying case list, displaying staff list, displaying contractors, displaying clients, displaying access logs, displaying attendance management, viewing all cases, managing case details, managing staff authority, managing staff memos, displaying tasks of other staff members, managing task templates, and displaying attendance data of other staff members. It is possible to set whether to give authority to staff members for each of these items.

[0044] FIG. 16 is a flow chart showing an example of the case registration process. Here, the case registration process is performed using the case registration items shown in FIG. 3. In FIG. 16, first, input of information for identifying the case is accepted (step S41), such as case name, client name, construction period, contractor, estimate (submission, submission due date, confirmation) date, estimate amount, confirmed amount, construction (request, reply due date, start, completion) date, road occupation creation (delivery date, completion) date, road occupation (application, permission, deadline) date, road use document creation (delivery date, completion) date, road use (application, permission, deadline) date, waterworks bureau document creation (delivery date, completion) date, waterworks bureau (application, permission) date, sewerage bureau document creation (delivery date, completion) date, sewerage bureau (application, permission) date, task template, etc. Next, it is judged whether or not the registration operation is allowed (step S42), and if NO, the process transitions to step S41. On the other hand, if it is allowed to perform the registration operation in step S42, the case is registered (step S43).

[0045] Next, a registered case is selected (step S44), and it is determined whether or not a task already registered will be used as a task for completing the case (step S45). If a task already registered will be used in step S45 (YES in step S45), the registered task is selected (step S46). On the other hand, if a task already registered will not be used (NO in step S45), a task is created and registered (step S47).

[0046] Next, a folder display is selected (step S48). A folder is an area for storing information related to each task, and the contents of this step S48 are processed based on the flowchart shown in FIG. 17. In FIG. 17, it is determined whether or not to add a folder display (step S91), and if the folder display is not to be added (NO in step S91), the process ends. On the other hand, if the folder display is to be added in step S91 (YES in step S91), the selection of the folder name to which the display is to be added and the click of the add button are accepted (step S92). Next, it is determined whether or not to update the folder information (step S93), and if the folder information is not to be updated (NO in step S93), the process ends. On the other hand, if the folder information is to be updated in step S93 (YES in step S93), the inside of the target folder is displayed by clicking, and the data to be added or changed by drag & drop is stored in the target folder (step S94), and the process ends. This makes it possible to update the folder information.

[0047] 18 and 19 are examples of display screens for registered folders. As shown in FIG. 18, multiple folders are registered, each with a folder name. As shown in FIG. 19, a new folder can be added (created). Also, as shown in FIG. 18, it is possible to delete an existing folder or change the name of an existing folder. When step S48 in FIG. 16 is completed, the registration contents of the case are updated (step S49), and the process is terminated.

[0048] An example of a registered project is shown in Figure 4. Three columns are displayed from the left as you face the page, with the leftmost column displaying information such as the project name, status (project progress), project number, category, client name, construction period, contractor, order recipient, estimated amount, and final amount. The second column from the left as you face the page allows you to enter any comments. The rightmost column displays tasks. These tasks are displayed in the same way as in Figure 6. In this way, the project requested by the client and all the tasks required to complete the request are displayed on the same screen.

[0049] FIG. 20 is a flow chart showing the process of posting a parent comment and notifying the user of the parent comment. The parent comment is the comment posted first, and a reply comment to the parent comment is called a child comment. First, a click on the parent comment creation button is accepted (step 111), and a parent comment creation screen is displayed (step 112). After the user creates a parent comment, the selection of the notification destination of the parent comment is accepted (step 113). Next, a click on the parent comment posting button is accepted (step 114), and the parent comment is displayed in the comment field in the second column from the left in FIG. 4, and at the same time, the member selected in step 113 is notified (step 115). As a notification method, for example, a notification list icon is displayed on the screen, and when a notification is received, a green circle is displayed next to the notification list icon. Also, when the user clicks on the notification list icon, the screen transitions to the notification list screen, and the green circle indicating a new notification disappears (step 116). Note that the notification method is not limited to this method.

[0050] FIG. 21 is a flow chart showing the process of replying to a child comment posted by a parent comment and notifying the user of the reply. First, the system accepts a click of the reply button under the parent comment to which the user wishes to reply (step 121), and displays a child comment creation screen (step 122). Next, after the user creates a child comment, the system accepts a click of the child comment posting button (step 123), and displays the child comment under the target parent comment, while notifying the member selected in step 113 of FIG. 20 (step 124). When the member confirms the new arrival notification, the display of the new arrival notification disappears (step 125). The notification method and the turning off of the display of the new arrival notification are the same as those for the notification of the parent comment. Note that a reply cannot be made to a child comment, but there is no upper limit on the number of replies by a child comment to the same parent comment. In addition, multiple child comments to the same parent comment are displayed in order from the top to the bottom in order of oldest to newest. Therefore, the notification of the new child comment is displayed at the bottom.

[0051] FIG. 22 is an example of a display screen for a list of registered cases. As shown in FIG. 22, each registered case is displayed in a list. Here, the case number (Case No.), case name, category, client name, status, amount, and storage location (Drive name or URL) are displayed. When any case is clicked in FIG. 22, the contents of each case are displayed on the screen. At this time, it is possible to display, for example, a screen such as that shown in FIG. 18.

[0052] Fig. 23 is a flow chart showing the process when using the case list. In Fig. 23, first it is determined whether or not to search for cases (step S61), and if cases are not to be searched for (NO in step S61), the process proceeds to step S64. On the other hand, if cases are to be searched for in step S61, search conditions are set and a search is performed (step S62). Here, the search conditions set are case name, date (registration date, scheduled construction completion date, estimate submission date, etc.), status (before estimate is finalized, construction in progress, application in progress, etc.), billing status (full billing completed, unbilled), and related companies (clients, contractors, etc.). It is also possible to set multiple conditions here.

[0053] Next, in step S63, the specified case is displayed. Next, a folder display is selected (step S64). A folder is an area for storing information related to each task, and the contents of this step S64 are processed based on the flowchart shown in FIG. 17. In FIG. 17, it is determined whether or not to add a folder display (step S91), and if the folder display is not added (NO in step S91), the process ends. On the other hand, in step S91, if the folder display is added (YES in step S91), the selection of the folder name to which the display is to be added and the click of the add button are accepted (step S92). Next, it is determined whether or not to update the folder information (step S93), and if the folder information is not updated (NO in step S93), the process ends. On the other hand, in step S93, if the folder information is updated (YES in step S93), the inside of the target folder is displayed by clicking, and the data to be added or changed by drag & drop is stored in the target folder (step S94), and the process ends. This makes it possible to update the folder information.

[0054] In Fig. 23, after step S64, the status of the item is updated as necessary (step S65). The contents of this step S65 are processed based on the flowchart shown in Fig. 24. That is, in Fig. 24, each item is selected from the list of items, and the status, the processed check of registered tasks (setting, canceling, etc.), addition or deletion of tasks, information on payment from the client (date, amount), information on payment to the contractor (date, amount), etc. are changed (step S81), and then the information on the item is updated (step S82), and the process ends (it also ends in Fig. 23).

[0055] Figure 25 is a flowchart showing the process when using a task list. In Figure 25, first, it is determined whether or not to narrow down the cases or tasks (step S71), and if the cases or tasks are not to be narrowed down (NO in step S71), the process proceeds to step S74. On the other hand, if the cases or tasks are to be narrowed down in step S71, the case or task conditions are set (step S72). Here, color (narrowing down status by color), color set (narrowing down by color set items), status (narrowing down by completed, incomplete, all items), date selection, calendar date, etc. are set.

[0056] Next, the screen is displayed based on the selection conditions set in step S72 (step S73), and the task or case is selected from the list of tasks selected in the above step S74. Next, a folder display is selected (step S75). The contents of step S75 are processed based on the flowchart shown in FIG. 17. In FIG. 17, it is determined whether or not to add a folder display (step S91), and if the folder display is not added (NO in step S91), the process ends. On the other hand, if the folder display is added in step S91 (YES in step S91), a click of the add button corresponding to the folder name to which the display is to be added is accepted (step S92). Next, it is determined whether or not to update the folder information (step S93), and if the folder information is not updated (NO in step S93), the process ends. On the other hand, if the folder information is updated in step S93 (YES in step S93), the inside of the target folder is displayed by clicking, and the data to be added or changed by drag & drop is stored in the target folder (step S94), and the process ends. This makes it possible to update the folder information.

[0057] Next, the status of the item is updated (step S76). The contents of this step S76 are processed based on the flowchart shown in Fig. 24. That is, in Fig. 24, each item is selected from the list of items, and the status, the processed check of registered tasks (setting, canceling, etc.), the addition or deletion of tasks, the information on payment from the client (date, amount), the information on payment to the contractor (date, amount), etc. are changed (step S81), and then the information on the item is updated (step S82), and the process ends (it also ends in Fig. 25).

[0058] Fig. 26 is a flowchart showing the process when using the task dashboard. In Fig. 26, first, the task to be counted is selected (step S51). Here, the task name (the name of the task being used in the task template) is specified (road use application in progress, billed, waiting for payment, etc.), the task color (the color of the task being used in the task color) is specified (person in charge only, estimate being submitted, under construction, etc.), and the task to be counted is selected. Next, the count start date is selected (step S52). Here, either the deadline date or the completion date is selected. Next, the count start date is selected (step S53). Here, the year and month are selected, such as "** year ** month to ** year ** month."

[0059] Next, the x-axis item of the graph is selected (step S54). Here, the period is selected (year / month). , weekly, daily), client, status, category, etc., are selected all or according to conditions. Next, the y-axis item of the graph is selected (step S55). Here, the number of tasks, estimated amount, invoice amount, etc. are selected all or according to conditions. Next, the operation of the data aggregation button (a button displayed on the screen or a mechanical button) is accepted (step S56), and the data is displayed (step S57).

[0060] Next, it is determined whether or not to set breakdown conditions (step S58), and if breakdown conditions are not to be set (NO in step S58), the process ends. On the other hand, if breakdown conditions are to be set in step S58, the breakdown conditions are selected (step S59). Here, a selection is made according to all or certain conditions, such as no breakdown, by client, by contractor, by staff, etc. Then, the process proceeds to step S57.

[0061] Fig. 27 is a diagram showing an example of a task dashboard display. Here, the aggregation tasks to be aggregated, the start point of aggregation, the period, the x-axis of the graph representing days, and the y-axis representing the number of tasks are specified. The figure shows the task dashboard without the breakdown.

[0062] In this way, the task completion status can be visualized according to the task that the user wants to check and the settings of the graph to be displayed, so the user can easily grasp the task progress, which makes it possible to reliably achieve task completion.

[0063] FIG. 28 is a flow chart showing the process of updating and creating a folder and setting a folder use authority. In FIG. 28, first, it is determined whether to add or change a folder (step S101). In step S101, if a folder is not added or changed, the process ends. However, if a folder is added or changed, the name of the folder to be added is input and added, or the folder to be changed is selected and the folder name is changed (step S102). Next, it is determined whether to grant a use authority for the folder (step S103). In step S103, if the use authority for the folder is not granted, the process ends. On the other hand, if the use authority for the folder is granted, a staff member to whom the use authority for the folder is granted is selected, the use permission is set (step S104), and the process ends. This makes it possible to flexibly update or add a folder, and further to flexibly set the use authority for each folder. [Explanation of symbols]

[0064] 1. Task Management System 3. Server equipment 5, 7, 9 Terminal Equipment 13 Main body function section 15 Task registration function 17 Case registration function section 19 Task List Section 21 Case List Section 23 Data output section 25 Folder Management Section

Claims

1. A task management program for managing tasks by customizing free templates, A process of accepting input of information identifying the content of a task; receiving an input of a time required to complete the task; A process of accepting registration of staff involved in the execution of the task; A process of accepting an input of information indicating a progress status of the task; and outputting a flowchart showing the latest task execution status based on the input information.

2. displaying the tasks and durations on a calendar; 2. The task management program according to claim 1, further comprising a process for displaying the flowchart and the calendar on the same screen.

3. A process of accepting input of information identifying a case requested by a requester; 3. The task management program according to claim 1, further comprising a process of selecting a task required for processing the case from among tasks already created, or creating a new task.

4. A process of accepting a selection of tasks to be aggregated; A process for accepting input of the start point and period to be aggregated; A process of accepting a selection of an item to be shown on the horizontal axis of the graph and an item to be shown on the vertical axis of the graph; a process of aggregating the progress status of the tasks to be aggregated based on the starting point and period, the items shown on the horizontal axis of the graph, and the items shown on the vertical axis of the graph; and displaying the aggregated task progress status on a screen as a task dashboard.

5. A task management system that manages tasks by customizing free templates, an input unit that receives input of information that identifies the content of a task, receives input of a period required to complete the task, receives registration of staff involved in the execution of the task, and receives input of information indicating a progress status of the task; a control unit that outputs a flowchart showing the latest task execution status based on each of the input information; a recording unit that records the input information and the tasks.

6. Further comprising a display unit for displaying an image, 6. The task management system according to claim 5, wherein the control unit controls the display unit to display the tasks and required periods on a calendar, and to display the flowchart and the calendar on the same screen.

7. The input unit receives an input of information identifying a case requested by a client, 7. The task management system according to claim 5, wherein the control unit selects a task required for processing the case from among tasks that have already been created, or creates a new task.

8. The input unit receives a selection of a task to be tabulated, receives an input of a start point and a period to be tabulated, receives a selection of an item to be shown on the horizontal axis of the graph and an item to be shown on the vertical axis of the graph, and The task management system according to claim 5, characterized in that the control unit tally up the progress status of the tasks to be tallyed based on the starting point and period, as well as the items shown on the horizontal axis of the graph and the items shown on the vertical axis of the graph, and displays the tally up progress status of the tasks as a task dashboard on the screen of the display unit.

9. 6. The task management system according to claim 5, further comprising: adding or updating a folder as an area for storing information related to each task; and granting a usage right to any of the folders.

Images