Task support system and task support method

Abstract

To support objective determination for the degree of necessity in the execution of each task or each process thereof.SOLUTION: A task support system 1 comprises: a memory unit for memorizing the deadline of each process which makes up a task; and an arithmetic unit for executing task risk evaluation value calculation processing which acquires information on the implementation stage of each process, and calculates each task risk evaluation value as a parameter expressing the size of risk that each process will delay the completion of each task about each process based on the acquired information on each implementation stage and the deadline of each process, process risk evaluation value calculation processing which calculates each process risk evaluation value as a parameter expressing the size of the risk of delaying the completion of each task based on the calculated each task risk evaluation value, and output processing which outputs information on each calculated process risk evaluation value to an output unit.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a business support system and a business support method.

Background Art

[0002] In recent years, the number of operations performed by companies has increased, and the number of steps in each operation has also increased. In addition, the content of each operation or step also varies widely. Along with this, it has become more difficult to determine the priority of each operation or step.

[0003] As a technology that contributes to the determination of the start of operations, for example, in Patent Document 1, there is provided a business process creation unit that determines the business process of each project and plans process information (start date, end date, person in charge, related persons), and a business process that monitors and manages the process information created by the business process creation unit during the execution of the business process. In the support system, there is provided means for calculating the difference between the scheduled start date and the actual start date among the business process information executed in the past. When executing the created business process, the transmission date is determined based on the scheduled start date and the calculated value, and a business process support system that transmits to the user terminal that the operation should be started is disclosed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, the specific content of each step (task) that constitutes an operation may vary greatly depending on the operation or step. In this regard, Patent Document 1 may make it difficult to objectively determine the start of an operation unless the specific content of the operation step (task) is managed.

[0006] The present invention has been made in view of such a background, and an object thereof is to provide a business support system and a business support method capable of assisting in objectively determining the degree of necessity for implementing a business or its processes.

Means for Solving the Problems

[0007] One aspect of the present invention for solving the above problems includes a storage device that stores deadlines for each process constituting a business, and acquires information on the implementation stage of the process. Based on the acquired implementation stage information and the deadline of the process, a task risk evaluation value calculation process that calculates, for each process, a parameter representing the magnitude of the risk that the process delays the completion of the business, a process risk evaluation value calculation process that calculates a parameter representing the magnitude of the risk that the completion of the business is delayed based on the calculated task risk evaluation values, and an arithmetic device that executes an output process of outputting information on the calculated process risk evaluation value to an output device.

Effects of the Invention

[0008] According to the present invention, it is possible to assist in objectively determining the degree of necessity for implementing a business or its processes.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Best Mode for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0011] FIG. 1 is a diagram showing an example of the configuration of an operation support system 1 according to the present embodiment. The operation support system 1 is an information processing system that manages the progress status of operations composed of a plurality of tasks (processes). The operation support system 1 includes a user terminal 100 managed by one or a plurality of users involved in the operation, and a progress management system 200 that objectively evaluates the progress status of each task of the operation and provides information such as the priority of each task to the user. The operation support system 1 manages a plurality of different operations.

[0012] Between the user terminal 100 and the progress management system 200, they are connected by a wired or wireless communication network 5 such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or a dedicated line.

[0013] FIG. 2 is a block diagram showing an example of the functions provided by the progress management system 200. First, the progress management system 200 includes an arithmetic unit 91 (processor) such as a CPU (Central Processing Unit), a storage device 92 such as a RAM (Random Access Memory), a ROM (Read Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive), an input device 93 composed of a keyboard, a mouse, a touch panel, etc., an output device 94 for performing screen display composed of a monitor (display), etc., and a communication device 95 composed of a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, or a serial communication module. Note that the user terminal 100 also has the same hardware.

[0014] Then, the progress management system 200 stores a task management table 700 that manages information such as the attributes of tasks in each business, the current implementation stage of the tasks, and the risk evaluation values of the tasks (details will be described later), and a task management table 700 that manages information on the risk evaluation values of each business (details will be described later).

[0015] In addition, the progress management system 200 stores information on the urgency of each task (deadline information management table). The urgency is a parameter indicating to what extent a task should be completed promptly in relation to the period from the start time (e.g., the present) to the deadline of the task and the implementation stage of the task.

[0016] Specifically, the deadline information management table stores a pre - deadline information management table 300 that manages the urgency of a task when the deadline of the task has not arrived yet, a within - deadline information management table 400 that manages the urgency of a task when the deadline of the task is currently within the deadline, and a past - deadline information management table 500 that manages the urgency of a task when the deadline of the task has passed.

[0017] In addition, in the present embodiment, for the implementation stage of a task, one of the following statuses is set in relation to the status of other tasks: "Pending", which is a status objectively impossible to start in the business process; "Open", which is a status where it is possible to start but has simply not been started; "Processing", which is a status of being in progress (underway); and "Completed", which is a completed status. "Pending", for example, is a situation where, when performing a task using a certain facility, the task of installing the facility must be completed first before starting.

[0018] The information on these implementation stages is information that can be commonly set for each task of each business. That is, the information on these implementation stages represents implementation stages that can identify the objective progress status regardless of the specific content of the business and tasks, such as before, during, or after the implementation of the task. Therefore, as long as it is information that can identify the objective progress status regardless of the specific content of the business and tasks, setting other types of information is not hindered.

[0019] (Information Management Table before Deadline) FIG. 3 is a diagram showing an example of the information management table 300 before the deadline. The information management table 300 before the deadline stores data for each task, including its item number 301, the urgency level 302 when the deadline has not yet arrived and the implementation stage is "Pending", the urgency level 303 when the deadline has not yet arrived and the implementation stage is "Open", the urgency level 304 when the deadline has not yet arrived and the implementation stage is "Processing", and the urgency level 305 when the deadline has not yet arrived and the implementation stage is "Completed".

[0020] The data in the information management table 300 before the deadline may be set by the user in advance, for example, or may be automatically set by the progress management system 200. For example, since it is before the deadline, a minimum value (e.g., 0) is set for all urgency levels.

[0021] Note that in the following, when the implementation stage is "pending", the urgency level 302 is referred to as the pending urgency level; when the implementation stage is "open", the urgency level 303 is referred to as the open urgency level; when the implementation stage is "in progress", the urgency level 304 is referred to as the in - progress urgency level; and when the implementation stage is "completed", the urgency level 305 is referred to as the completed urgency level.

[0022] (Information Management Table within Deadline) FIG. 4 is a diagram showing an example of an information management table 400 within a deadline. The information management table 400 within a deadline stores, for each task, its item number 401, the pending urgency level 402 when the deadline has arrived (for example, currently) and the implementation stage is "pending", the open urgency level 403 when the deadline has arrived and the implementation stage is "open", the in - progress urgency level 404 when the deadline has arrived and the implementation stage is "in progress", and the completed urgency level 405 when the deadline has arrived and the implementation stage is "completed".

[0023] The data in the information management table 400 within a deadline may be set by the user in advance, for example, or may be automatically set by the progress management system 200. For example, since the deadline has currently arrived, a value larger than the urgency level in the pre - deadline information management table 300 is set for each urgency level.

[0024] (Information Management Table after Deadline) FIG. 5 is a diagram showing an example of an information management table 500 after a deadline. The information management table 500 after a deadline stores, for each task, its item number 501, the pending urgency level 502 when the deadline has passed (for example, currently) and the implementation stage is "pending", the open urgency level 503 when the deadline has passed and the implementation stage is "open", the in - progress urgency level 504 when the deadline has passed and the implementation stage is "in progress", and the completed urgency level 505 when the deadline has passed and the implementation stage is "completed".

[0025] The data in the expiration date overdue information management table 500 may be set by the user in advance, for example, or may be automatically set by the progress management system 200. For example, since the expiration date has passed, a value larger than the urgency level in the expiration date within information management table 400 is set for each urgency level.

[0026] Next, as shown in FIG. 2, the progress management system 200 stores each functional unit (program) of an expiration date information acquisition unit 210, a risk evaluation value calculation unit 220, and an output unit 230.

[0027] The expiration date information acquisition unit 210 acquires an expiration date information management table.

[0028] The risk evaluation value calculation unit 220 includes a task risk evaluation value calculation unit 221 and a process risk evaluation value calculation unit 222.

[0029] The task risk evaluation value calculation unit 221 acquires information on the execution stage of a task from the task management table 700, and based on the acquired execution stage information ("pending", "open", "processing", "completed") and the expiration date of the task (scheduled start date, scheduled end date), calculates a task risk evaluation value, which is a parameter representing the magnitude of the risk that the task will delay the completion of the business, for each task.

[0030] Specifically, the task risk evaluation value calculation unit 221 refers to the expiration date information management table and calculates the task risk evaluation value based on the urgency level of the task according to the period from the start time (current date) to the expiration date of the task and the information on the execution stage of the task.

[0031] Note that the task risk evaluation value calculation unit 221 further calculates the task risk evaluation value based on the information on the importance level of the task, as will be described later.

[0032] Next, the process risk evaluation value calculation unit 222 calculates a process risk evaluation value, which is a parameter representing the magnitude of the risk that the completion of the business will be delayed, based on each task risk evaluation value calculated by the task risk evaluation value calculation unit 221.

[0033] Note that the process risk evaluation value calculation unit 222 calculates a process risk evaluation value for each of a plurality of different operations.

[0034] The output unit 230 outputs the information on the process risk evaluation value calculated by the process risk evaluation value calculation unit 222 to an output device.

[0035] In addition, the output unit 230 totals the number of tasks constituting each operation for each of the plurality of operations at the current implementation stage, and outputs a graph (bubble chart) representing the relationship between the process risk evaluation value of each operation and the number of processes related to each implementation stage of the tasks of each operation to an output device.

[0036] The functions of the progress management system 200 described above are realized by the hardware of the progress management system 200, or by the arithmetic unit 91 of the progress management system 200 reading and executing each program stored in the storage device 92. These programs are stored in a storage device such as a secondary storage device, a non-volatile semiconductor memory, a hard disk drive, an SSD, etc., or a recording medium readable by the progress management system 200 such as an IC card, an SD card, a DVD, etc. Note that the progress management system 200 may be realized using virtual information processing resources provided using virtualization technology, process space separation technology, etc., such as a virtual server provided by a cloud system. Also, all or part of the functions provided by these devices may be realized by a service provided by a cloud system via an API (Application Programming Interface) or the like. Next, the processing performed in the business support system 1 will be described.

[0037] FIG. 6 is a flowchart for explaining an example of business support processing performed in the business support system 1. The business support processing is started, for example, when a predetermined input is received from the user terminal 100 when each user formulates a business plan.

[0038] The progress management system 200 creates prototype data of the process management table 800 for managing the operations in which the user is involved, for each operation (s101).

[0039] Also, the progress management system 200 creates prototype data of the task management table 700 for managing the tasks in the operations in which the user is involved, for each task (s102).

[0040] The progress management system 200 sets information on the scheduled start date, scheduled end date, importance level, and current implementation stage of each task in each task management table 700 created in s102 (s103).

[0041] (Task Management Table) Here, FIG. 7 is a diagram showing an example of the task management table 700. The task management table 700 stores each data including the item number 701 of each task, the importance level of each task (task importance level 702), the scheduled start date 703 of each task, the scheduled end date 704 of each task, the current implementation stage 705 of each task, and the task risk evaluation value 706 of each task.

[0042] The task importance level is set based on the business importance of the task in the operation (for example, the importance from a technical perspective, the importance from a profitability perspective), or the degree of requirement for compliance with the deadline of the task (the degree to which the deadline should be observed). The task importance level may be set by the user, or may be automatically set based on the information of the tasks registered in a predetermined operation management system.

[0043] Any one of "pending", "open", "processing", and "completed" is set for the implementation stage 705. The implementation stage 705 is set by the user or automatically set by a predetermined operation management system that manages the implementation stages of the operations and tasks. When s103 is executed for the first time, "open" is set for the implementation stage 705.

[0044] The task risk evaluation value 706 is automatically set by the process described later.

[0045] (Process management table) FIG. 8 is a diagram showing an example of a process management table 800. The process management table 800 is data that stores each data including the item number 801 of each business and the process risk evaluation value 802 of each business. The process management table 800 is created for each business, for example. The process risk evaluation value 802 is automatically set by the process described later.

[0046] After the process management table 800 and the task management table 700 are set by s101 to s103, as shown in FIG. 6, the progress management system 200 monitors whether the information on the execution stage, the planned start date, or the planned end date of any task in the task management table 700 has been changed (s104).

[0047] When the information of any task is changed, the progress management system 200 updates the task risk evaluation value of that task (hereinafter referred to as this task) and the process risk evaluation value of the business (hereinafter referred to as this business) to which that task belongs based on the planned start date, the planned end date, and the execution stage of that task (s105 - s108). When the information of a plurality of tasks is changed, the progress management system 200 executes the processes of s105 - s108 for each of those tasks.

[0048] Specifically, first, when the execution stage of this task is changed, the progress management system 200 acquires the information of the current date (time), and also specifies the relationship (period) between the planned start date or the planned end date of this task and the current date (s105).

[0049] That is, when the current date is before the planned start date of this task (s105: before the deadline), the progress management system 200 executes the process of s106.

[0050] If the current date is after the scheduled start date and before the end date of this task (s105: within the deadline), the progress management system 200 executes the process of s107.

[0051] If the current date is after the start and end date of this task (s105: deadline exceeded), the progress management system 200 executes the process of s108.

[0052] In s106, the progress management system 200 identifies the current urgency of this task based on the pre - deadline information management table 300, and calculates the task risk assessment value of this task based on the identified urgency.

[0053] Specifically, first, the progress management system 200 identifies the current (changed) implementation stage of this task ("on hold", "open", "in progress", "completed"), and obtains the urgency related to the above - identified implementation stage from the pre - deadline information management table 300 related to this task. For example, if the changed implementation stage of this task is "in progress", "0" is obtained as the in - progress urgency.

[0054] Then, the progress management system 200 calculates the task risk assessment value of this task by multiplying the obtained urgency by the task importance of this task obtained from the task management table 700. The progress management system 200 sets the calculated task risk assessment value in the task management table 700 related to this task. Then, the process of s109 is performed.

[0055] In s107, the progress management system 200 identifies the current urgency of this task based on the within - deadline information management table 400, and calculates the task risk assessment value of this task based on the identified urgency.

[0056] Specifically, first, the progress management system 200 identifies the current (changed) implementation stage of this task ("pending", "open", "processing", "completed"), and obtains the urgency level corresponding to the identified implementation stage from the deadline information management table 400 related to this task. For example, if the changed implementation stage of this task is "processing", "2" is obtained as the urgency level during processing.

[0057] Then, the progress management system 200 calculates the task risk evaluation value of this task by multiplying the obtained urgency level by the task importance level of this task obtained from the task management table 700. The progress management system 200 sets the calculated task risk evaluation value in the task management table 700 related to this task. After that, the process of s109 is performed.

[0058] In s108, the progress management system 200 identifies the current urgency level of this task based on the deadline overdue information management table 500, and calculates the task risk evaluation value of this task based on the identified urgency level.

[0059] Specifically, first, the progress management system 200 identifies the current (changed) implementation stage of this task ("pending", "open", "processing", "completed"), and obtains the urgency level corresponding to the identified implementation stage from the deadline overdue information management table 500 related to this task. For example, if the changed implementation stage of this task is "processing", "5" is obtained as the urgency level during processing.

[0060] Then, the progress management system 200 calculates the task risk evaluation value of this task by multiplying the obtained urgency level by the task importance level of this task obtained from the task management table 700. The progress management system 200 sets the calculated task risk evaluation value in the task management table 700 related to this task. After that, the process of s109 is performed.

[0061] In S109, the progress management system 200 calculates the process risk evaluation value by summing up the task risk evaluation values of each task in the main business calculated in S106 to S108.

[0062] Note that the calculation method of this process risk evaluation value is just an example. For example, the process risk evaluation value may be calculated using parameters such as the weight value for each task and the weight value determined by the relationship with other businesses.

[0063] Then, the progress management system 200 displays the information of each risk evaluation value and the process evaluation value on the screen of the user terminal 100 or the progress management system 200 (S110). After that, the process of S104 is repeated. The following describes the displayed screen.

[0064] (Process Management Screen) FIG. 9 is a diagram showing an example of a process management screen 900 that displays information on each business. The process management screen 900 is a screen that displays the ID 901 of each business, the name 902 of each business, the implementation stage 903 of each task in each business, and the process risk evaluation value 904 of each business.

[0065] The figure 905 representing the implementation stage 903 of each task is a different figure depending on the implementation stage. Also, each figure 905 is displayed in an orderly manner according to the standard order in which each task should be performed.

[0066] (Task Management Screen) FIG. 10 is a diagram showing an example of a task management screen 1000 that displays information on each task. It has a process selection part 1001 for selecting the business that displays the information of the task, and a task display part 1002 for displaying the information of each task in the selected business.

[0067] The task display section 1002 displays the ID 1003 of each task, the name 1004 of each task, the current execution stage 1005 of each task, the scheduled start date 1006 of each task, the scheduled end date 1007 of each task, the start date 1008 of each task (displayed when the task is started), the end date 1009 of each task (displayed when the task is completed), and the task risk evaluation value 1010 of each task respectively.

[0068] (Task Risk Ranking Screen) FIG. 11 is a diagram showing an example of a task risk ranking screen 1100. The task risk ranking screen 1100 includes a process selection section 1101 for selecting an operation to display task information, and a task display section 1102 for displaying a list of each task in the selected operation.

[0069] In the task display section 1102, each selected task is displayed in ascending order of its task risk evaluation value. In the task display section 1102, the same various types of information as the task display section 1002 of the task management screen 1000 are displayed.

[0070] Note that the task risk ranking screen 1100 may display the information of each task according to a predetermined rule corresponding to a descending order or other task risk evaluation values instead of the ascending order of the task risk evaluation values.

[0071] (Process Risk Ranking Screen) FIG. 12 is a diagram showing an example of a process risk ranking screen 1200. In the process risk ranking screen 1200, the information of each operation is displayed in ascending order of its process risk evaluation value 1201. In the process risk ranking screen 1200, the same information of each operation as the process management screen 900 is displayed.

[0072] Note that the process risk ranking screen 1200 may display the information of each operation according to a predetermined rule corresponding to a descending order or other process risk evaluation values instead of the ascending order of the process risk evaluation values.

[0073] (Business Risk Assessment Screen) FIG. 13 is a diagram showing an example of a business risk assessment screen 1300. The business risk assessment screen 1300 is a screen that displays a graph 1301 representing the three-way relationship among the process risk assessment values of each business, each implementation stage of each task of each business, and the number of tasks currently belonging to each implementation stage.

[0074] This graph 1301 is in the form of a bubble chart, and is a bubble chart with the increasing direction of the process risk assessment value in the direction of the horizontal axis 1302 and the implementation stages of the tasks ("open", "processing", "completed") in the direction of the vertical axis 1303.

[0075] The progress management system 200 identifies the current implementation stages of each task of a plurality of each business by means of a task management table 700, and totals the number of tasks belonging to each implementation stage for each business. Then, a graphic 1304 representing the totaled number of tasks is displayed at the corresponding positions (business process risk assessment value, implementation stage) on the horizontal and vertical axes of the bubble chart. This graphic 1304 is a graphic with a size corresponding to the magnitude of the number of tasks.

[0076] When the user designates this graphic 1304, the corresponding information 1305 (business ID or name, number of tasks, process risk assessment value) is displayed.

[0077] In this embodiment, the above three-way relationship is displayed in a bubble chart, but it may also be displayed in other forms of graphs (such as a three-dimensional bar graph).

[0078] By referring to the distribution of the graphics 1304 in the graph 1301 of the business risk assessment screen 1300, the user can confirm whether a large number of existing businesses are progressing smoothly at a more specific task level.

[0079] As described above, the business support system 1 of the present embodiment calculates, for each process, a task risk evaluation value, which is a parameter representing the magnitude of the risk that a task delays the completion of a business, based on the information on the implementation stage of the task (task management table 700) and the deadline of the task (deadline information management table), and calculates, based on the calculated task risk evaluation values, a process risk evaluation value, which is a parameter representing the magnitude of the risk that the completion of the business is delayed, and outputs the process risk evaluation value to an output device.

[0080] That is, the business support system 1 can estimate the risk of a business arising in relation to the deadline by calculating a risk evaluation value related to the task and an evaluation value related to the business, respectively, based on the objective implementation stage of each task and the deadline of the task.

[0081] Thus, according to the business support system 1 of the present embodiment, it is possible to support objectively judging the degree of necessity for implementing a business or its process.

[0082] In addition, the business support system 1 of the present embodiment calculates a task risk evaluation value based on the period from the start time (current) to the deadline of the task and the urgency of the task corresponding to the implementation stage of the task.

[0083] Thus, by calculating the task risk evaluation value using the objective urgency of the task with respect to the deadline and the urgency corresponding to the implementation stage of the task, the risk of the business can be estimated more accurately.

[0084] In addition, the business support system 1 of the present embodiment acquires, as information on the implementation stage of the task, which one of "on hold", "open", "in progress", and "completed" it is, and calculates a task risk evaluation value based on the period until the deadline of the task and the urgency of the task corresponding to the implementation stage.

[0085] In this way, by specifying the execution stage of a task as either "pending", "open", or "completed", the execution stage of the task can be objectively specified regardless of the type of business, and the task risk evaluation value can be calculated, enabling a more objective estimation of the business risk. For example, even if there are multiple businesses with different specific task contents, the relative priority of business completion among them can be easily specified.

[0086] In addition, the business support system 1 of this embodiment calculates the task risk evaluation value using the importance of the task.

[0087] This enables a highly accurate risk evaluation based not only on the task deadline but also on the objective importance of the business.

[0088] In addition, the business support system 1 of this embodiment displays on the screen each figure indicating the execution stage of each task constituting the business in association with the process risk evaluation value of the business (process management screen 900).

[0089] This allows the user to easily grasp the specific execution stage at the task level of the business.

[0090] In addition, the business support system 1 of this embodiment displays on the screen the figure indicating the execution stage of the task in association with the task risk evaluation value (task management screen 1000).

[0091] This allows the user to easily grasp the execution stage of each task and its risk.

[0092] In addition, the business support system 1 of this embodiment displays on the screen each of the plurality of process risk evaluation values in an order (ascending order, descending order, etc.) according to the magnitude of the process risk evaluation value (process risk ranking screen 1200).

[0093] This allows the user to easily identify the business that should be executed preferentially among the multiple existing businesses.

[0094] In addition, the business support system 1 of this embodiment totals the number of steps in each process for each of a plurality of operations for each implementation stage, and displays on the screen a graph (such as a bubble chart) representing the relationship between the process risk evaluation value of each operation, the implementation stage of the process in the operation, and the number of tasks belonging to each implementation stage of each operation (business risk evaluation screen 1300).

[0095] Thereby, the user can easily determine, for a plurality of operations, which operation should be preferentially completed in view of the implementation stage of its constituent tasks, regardless of the specific content of the operation.

[0096] The above description of the embodiment is for facilitating the understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from its gist, and equivalents thereof are included in the present invention.

[0097] For example, a part of the hardware provided in each device of this embodiment may be provided in other devices.

[0098] Also, each program of each device may be provided in other devices, a certain program may be composed of a plurality of programs, or a plurality of programs may be integrated into one program.

Description of Reference Numerals

[0099] 1 Business support system, 100 User terminal, 200 Progress management system

Claims

1. A storage device that stores deadlines for each process constituting a business, and a task risk evaluation value calculation process that acquires information on the implementation stage of the process and calculates, for each process, a task risk evaluation value that is a parameter representing the magnitude of the risk that the process will delay the completion of the business based on the acquired implementation stage information and the deadline of the process, a process risk evaluation value calculation process that calculates a process risk evaluation value that is a parameter representing the magnitude of the risk that the completion of the business will be delayed based on the calculated task risk evaluation values for each process, and an arithmetic device that executes an output process of outputting information on the calculated process risk evaluation value to an output device A business support system comprising:

2. The storage device further stores the urgency of the process according to the period from the specified start time to the deadline of the process and the implementation stage of the process, The arithmetic device In the task risk evaluation value calculation process, acquires the start time, and calculates the task risk evaluation value based on the period specified by the acquired start time and the urgency of the process corresponding to the acquired implementation stage information of the process. The business support system according to claim 1.

3. The storage device further stores the urgency of the process according to the period from the specified start time to the deadline of the process and whether the implementation stage of the process is impossible to start, possible to start but not yet started, or already completed, The arithmetic device In the task risk evaluation value calculation process, As information on the implementation stage of the process, acquires information indicating whether the process is impossible to start, possible to start but not yet started, or already completed, And calculates the task risk evaluation value based on the period specified by the acquired start time and the urgency of the process corresponding to the acquired implementation stage information of the process. The business support system according to claim 2.

4. The storage device further stores information on the importance of each process, The arithmetic device In the task risk evaluation value calculation process, calculates the task risk evaluation value based on the acquired implementation stage information, the deadline of the process, and the information on the importance of the process. The business support system according to claim 1.

5. The arithmetic device In the output process, outputs, to the output device, each figure indicating the implementation stage of each process constituting the business, in association with the process risk evaluation value of the business. The business support system according to claim 1.

6. The arithmetic unit In the output process, a graphic indicating the implementation stage of the process is output to an output device in association with the task risk evaluation value of the process. The business support system according to claim 1.

7. The arithmetic unit In the task risk evaluation value calculation process, for each of a plurality of operations, calculate the task risk evaluation value of each process of the operation. In the process risk evaluation value calculation process, based on the calculated task risk evaluation value, calculate the process risk evaluation value for each of the plurality of operations. In the output process, each of the calculated plurality of process risk evaluation values is output to an output device in an order according to the magnitude of the process risk evaluation value. The business support system according to claim 1.

8. The arithmetic unit In the task risk evaluation value calculation process, for each of a plurality of operations, calculate the task risk evaluation value of each process of the operation. In the process risk evaluation value calculation process, based on the calculated task risk evaluation value, calculate the process risk evaluation value for each of the plurality of operations. In the output process For each of the plurality of operations, total the number of processes in the operation for each implementation stage, and output to an output device a graph representing the relationship between the process risk evaluation value of the operation, the implementation stage of the process of the operation, and the number of processes belonging to each implementation stage. The business support system according to claim 1.

9. A business support method by an information processing device including a storage device that stores the deadlines of each process constituting a business and an arithmetic unit, wherein the arithmetic unit acquires information on the implementation stage of the process, and based on the acquired implementation stage information and the deadline of the process, performs a task risk evaluation value calculation process for calculating, for each process, a task risk evaluation value that is a parameter representing the magnitude of the risk that the process delays the completion of the business; a process risk evaluation value calculation process for calculating a process risk evaluation value that is a parameter representing the magnitude of the risk that the completion of the business is delayed based on the calculated task risk evaluation values; and an output process for outputting information on the calculated process risk evaluation value to an output device. Business support method.

Images