KPI evaluation system and method

Abstract

Provided is a technology that is capable of analyzing business KPIs and that is capable of obtaining a plurality of solutions that are harmonized as a whole while taking feasibility into consideration. A KPI evaluation system 100 is a system for evaluating business key performance indicators (KPIs) for a stakeholder, wherein a computer provided with at least a processor 101, a memory 102, and a storage device 103 defines relationships between issues for each of two or more stakeholders including the abovementioned stakeholder, and associates KPI settings of stakeholders other than the abovementioned stakeholder with the issues of each stakeholder on the basis of the defined relationships between the issues.

Description

System and method for evaluating KPIs

[0001] The present invention relates to a technique for evaluating KPIs in business.

[0002] In recent years, in response to the diversification of end-user needs and corporate services, fundamentally reviewing traditional business operations and structures has become one of the key factors in becoming a company that customers choose.

[0003] Traditionally, companies have set business KPIs (Key Performance Indicators) and implemented measures to improve them in order to achieve their management goals. However, in today's world where needs and services are diversifying, it is important to evaluate KPIs across the entire business, focusing not only on the company's KPIs but also on the customer's KPIs (see, for example, Patent Documents 1 and 2).

[0004] JP 2021-144700 A JP 2014-095952 A

[0005] The technology of Patent Document 1 applies KPIs defined for each grouped target and can create a report of the analysis results, but there is a problem in that it results in individual optimization for each group.

[0006] The technology of Patent Document 2 can optimize the entire business process by using a synthesis formula for multiple task KPIs, but there is a problem in that it results in a specific solution whose feasibility is unclear.

[0007] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a technology that enables analysis of business KPIs that can yield multiple solutions that are harmonious overall while taking feasibility into consideration.

[0008] The KPI evaluation system according to the present invention is a system for evaluating a stakeholder's business KPIs (Key Performance Indicators), in which a computer having at least a processor, memory, and storage device defines the relationships between the issues of each stakeholder for two or more stakeholders including the stakeholder in question, and associates the KPI settings of stakeholders different from the stakeholder in question with the issues of each stakeholder based on the defined relationships between the issues.

[0009] Other problems and solutions disclosed in the present application will be made clear in the detailed description and drawings.

[0010] According to the present invention, it is possible to analyze business KPIs in a way that provides multiple solutions that are harmonious as a whole while taking feasibility into consideration.

[0011] 1 is a diagram showing an example of the overall system configuration of a business KPI evaluation system according to Examples 1 and 2. FIG. 2 is a diagram showing an example of the function blocks of a business KPI evaluation system according to Example 1. FIG. 3 is a diagram showing an example of the configuration of each table stored in a customer information database. FIG. 4 is a diagram showing an example of the configuration of each table stored in a relationship database. FIG. 5 is a flowchart showing an example of the flow of a graph definition process. FIG. 6 is a flowchart showing an example of the flow of a KPI relationship definition process. FIG. 7 is a flowchart showing an example of the flow of an issue relationship definition process. FIG. 8 is a flowchart showing an example of the flow of an issue selection process. FIG. 9 is a flowchart showing an example of the flow of a KPI calculation process. FIG. 10 is a diagram showing an example of the function blocks of a business KPI evaluation system according to Example 2. FIG. 11 is a diagram showing an example of the configuration of each table stored in a relationship database. FIG. 12 is a flowchart showing an example of the flow of a KPI calculation accumulation process. FIG. 13 is a flowchart showing an example of the flow of a UI control process. FIG. 14 is a diagram showing an example of the configuration of a KPI evaluation confirmation screen. FIG. 15 is a flowchart showing an example of the flow of an accumulation reference process.

[0012] In the following description, an "interface unit" refers to one or more interface devices. The one or more interfaces may be one or more interface devices of the same type (for example, one or more NICs (Network Interface Cards)) or two or more interface devices of different types (for example, a NIC and an HBA (Host Bus Adapter)).

[0013] In the following description, a "storage unit" refers to one or more memories. At least one memory may be a volatile memory or a non-volatile memory. The storage unit may include one or more PDEVs in addition to one or more memories. A "PDEV" refers to a physical storage device, and may typically be a non-volatile storage device (e.g., an auxiliary storage device). A PDEV may be, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

[0014] In the following description, a "processor unit" refers to one or more processors. At least one processor is typically a CPU (Central Processing Unit). The processor may include a hardware circuit that performs some or all of the processing.

[0015] In the following description, functions are sometimes described using the term "kkk unit" (excluding the interface unit, storage unit, and processor unit). However, the functions may be implemented by one or more computer programs executed by the processor unit, or by one or more hardware circuits (e.g., a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)). When a function is implemented by a program executed by the processor unit, the specified processing is performed using the storage unit and / or the interface unit, as appropriate, and therefore the function may be considered to be at least a part of the processor unit. Processing described using a function as the subject may be processing performed by the processor unit or a device having the processor unit. A program may be installed from a program source. The program source may be, for example, a program distribution computer or a computer-readable recording medium (e.g., a non-transitory recording medium). The description of each function is merely an example; multiple functions may be combined into one function, or one function may be divided into multiple functions.

[0016] In the following description, information may be described using expressions such as "xxx table," but the information may be expressed in any data structure. In other words, to indicate that the information does not depend on the data structure, an "xxx table" may be referred to as "xxx information." In the following description, the structure of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0017] In the following description, "time" is expressed in units of year, month, day, hour, minute, and second, but the time unit may be coarser or finer than that, or may be a different unit.

[0018] In the following description, a "dataset" refers to data (a logical block of electronic data) consisting of one or more data elements, and may be, for example, any of a record, a file, a key-value pair, and a tuple.

[0019] In the following description, a process may be described using a "program" as the subject, but the process described using a program as the subject may also be a process performed by a processor or a device having that processor. Two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0020] Furthermore, in the following description, the "KPI evaluation system" may be a system configured with one or more physical computers, or may include a system (e.g., a cloud computing system) implemented on a group of physical computing resources (e.g., a cloud infrastructure). When the KPI evaluation system "displays" the display information, it may mean that the display information is displayed on a display device possessed by the computer, or that the computer transmits the display information to a display computer (in the latter case, the display information is displayed by the display computer).

[0021] Hereinafter, several embodiments will be described in detail with reference to the drawings.

[0022] In the following description, the same or similar components will be designated by common reference numerals, and redundant description may be omitted.

[0023] Furthermore, when there are multiple elements having the same or similar functions, the multiple elements may be described by using the same reference numeral with different subscripts to distinguish between them. On the other hand, when there is no need to distinguish between the multiple elements, the subscripts may be omitted.

[0024] <Configuration Example of KPI Evaluation System 100> First, a configuration example of the KPI evaluation system 100 according to the embodiment will be described with reference to Figures 1 and 2. Figure 1 is a diagram showing an example of the overall system configuration of the KPI evaluation system 100 according to Examples 1 and 2. Also, Figure 2 is a diagram showing an example of functional blocks of the KPI evaluation system 100 according to Example 1.

[0025] (Example of Overall System Configuration) The KPI evaluation system 100 of this embodiment is a computer system capable of evaluating KPIs, and is realized by a computer device or a server device having the components described below.

[0026] The KPI evaluation system 100 is connected to user terminals 110a, 110b, 110c, ... 110n (hereinafter, collectively referred to as "user terminals 110" when referring to them collectively or when no particular distinction is made) such as laptop PCs, tablets, smartphones, etc. owned by users of the KPI evaluation system 100, so that data can be communicated between them via an appropriate communication network 120 such as the Internet or a dedicated line. The KPI evaluation system 100 and the communication network 120 are connected via a wired connection via well-known communication equipment (not shown), but may also be connected wirelessly. Each user terminal 110 and the communication network 120 are connected wirelessly, but may also be connected via a wired connection.

[0027] Furthermore, for example, other computer devices, server devices, etc. (hereinafter also referred to as "other devices") may be connected to the KPI evaluation system 100 so as to be able to communicate data with each other via the communication network 120. In this case, the other devices and the communication network 120 may be connected by wire or wirelessly via well-known communication equipment (not shown).

[0028] In the present embodiment, the KPI evaluation system 100 is described as being composed of one device. However, for example, the KPI evaluation system 100 may be composed of a plurality of devices.

[0029] In addition, in the present embodiment, the KPI evaluation system 100 and the user terminal 110 or other devices have been described as being separate devices. However, the KPI evaluation system 100 and the user terminal 110 or other devices may be configured as the same device. In this case, the KPI evaluation system may be configured as a system including, for example, the user terminal 110 or other devices. Furthermore, for example, the KPI evaluation system may be configured to include some or all of the functions performed by the user terminal 110 or other devices.

[0030] (Example of Hardware Configuration of KPI Evaluation System 100) Next, an example of the hardware configuration of the KPI evaluation system 100 will be described with reference to FIG.

[0031] The KPI evaluation system 100 of this embodiment is realized by a single general-purpose computer device, as shown in Fig. 1. The following description will be given assuming that the KPI evaluation system 100 is realized by a single general-purpose computer device including one or more processors 101, one or more memories 102, one or more storage devices 103, one or more network interfaces 104, one or more input devices 105, and a wired or wireless communication line 107 connecting them.

[0032] That is, the KPI evaluation system 100 has a storage device including a memory 102 and a storage device 103, an interface device including a network interface 104 and an input device 105, and a processor 101 connected thereto.

[0033] The storage device 103 is an auxiliary storage device made up of a nonvolatile storage element such as a flash memory. Specific examples of the storage device 103 include a solid state drive (SSD) and a hard disk drive (HDD). The storage device 103 stores at least a KPI evaluation program. The KPI evaluation program is a computer program for implementing the functions required for the KPI evaluation system 100.

[0034] In other words, when the KPI evaluation program is executed by the processor 101, various processes are performed, including processes related to graph definition (hereinafter referred to as "graph definition process"), processes related to KPI relationship definition (hereinafter referred to as "KPI relationship definition process"), processes related to issue relationship definition (hereinafter referred to as "issue relationship definition process"), processes related to issue selection (hereinafter referred to as "issue selection process"), processes related to KPI calculation (hereinafter referred to as "KPI calculation process"), processes related to KPI calculation and accumulation (hereinafter referred to as "KPI calculation and accumulation process"), processes related to UI control (hereinafter referred to as "UI control process"), and processes related to accumulation reference (hereinafter referred to as "accumulation reference process"), which will be described later in relation to Figures 5 to 9 and Figures 12 to 14, respectively.

[0035] The KPI evaluation program may be installed from a program source. The program source may be, for example, a program distribution computer or a computer-readable recording medium. The KPI evaluation program may also be composed of a device driver, an operating system, various application programs located at higher levels than these, and a library that provides common functions to these programs. Furthermore, two or more programs may be realized as one KPI evaluation program, and one KPI evaluation program may be realized as two or more programs.

[0036] The memory 102 is a primary storage device mainly composed of volatile memory elements such as RAM (Random Access Memory). The memory 102 temporarily stores data representing various information read from the storage device 103 and various data acquired via the network interface 104 and / or the input device 105.

[0037] The processor 101 is a processor device such as a CPU (Central Processing Unit) and various co-processors. The processor 101 loads a KPI evaluation program into the memory 102 and executes it, thereby performing overall control of the KPI evaluation system 100 itself and also managing a control unit (not shown) that performs various processes such as calculation processing and judgment processing.

[0038] The interface devices include a network interface 104 that connects to a communication network 120 to communicate with a user terminal 110 or other devices, and an input device 105 .

[0039] (Example of Hardware Configuration of User Terminal 110) Next, an example of the hardware configuration of the user terminal 110 will be described with reference to FIG.

[0040] The user terminal 110 of this embodiment is realized by a single general-purpose computer device, as shown in Fig. 1. The following description will be given assuming that the user terminal 110 is realized by a single general-purpose computer device including one or more processors 111, one or more memories 112, one or more storage devices 113, one or more network interfaces 114, one or more input devices 115, one or more output devices 116, and a wired or wireless communication line 117 connecting them.

[0041] That is, the user terminal 110 has a storage device including a memory 112 and a storage device 113, an interface device including a network interface 114, an input device 115 and an output device 116, and a processor 111 connected thereto.

[0042] The storage device 113 is an auxiliary storage device made up of a non-volatile storage element such as a flash memory. Specific examples of the storage device 113 include a solid state drive (SSD) and a hard disk drive (HDD). The storage device 113 stores various computer programs, including programs for implementing functions required by the user terminal 110.

[0043] The program may be installed from a program source. The program source may be, for example, a program distribution computer or a computer-readable recording medium. The program may also be composed of a device driver, an operating system, various application programs located at higher levels than these, and a library that provides common functions to these programs. Furthermore, two or more programs may be realized as a single program, or one program may be realized as two or more programs.

[0044] The memory 112 is a primary storage device mainly composed of volatile memory elements such as RAM (Random Access Memory). The memory 112 temporarily stores data representing various information read from the storage device 113 and various data acquired via the network interface 114 and / or the input device 115.

[0045] The processor 111 is a processor device such as a CPU (Central Processing Unit) and various co-processors. The processor 111 loads the above programs into the memory 112 and executes them, thereby performing overall control of the user terminal 110 itself and also managing a control unit that performs various processes such as calculation processing and determination processing.

[0046] The interface device includes a network interface 114 that connects to a communication network 120 to communicate with the KPI evaluation system 100 and other devices, and an I / O (Input / Output) interface consisting of an input device 115 and an output device 116.

[0047] (Example of Functional Blocks of KPI Evaluation System 100 According to Example 1) Next, an example of blocks of various functions provided in the KPI evaluation system 100 according to Example 1 will be described with reference to Fig. 2. Note that each block described below does not represent a hardware-based configuration, but represents a functional-based block.

[0048] The KPI evaluation system 100 is configured to include the following functional blocks: a control unit, a storage unit, a communication unit, and a user interface unit consisting of an input unit and an output unit (none of which are shown).

[0049] The control unit executes various data processing based on the programs and data stored in the storage unit and the data acquired by the communication unit. The control unit also executes various processes such as the graph definition process (described in detail below with reference to FIG. 5), KPI relationship definition process (described in detail below with reference to FIG. 6), issue relationship definition process (described in detail below with reference to FIG. 7), issue selection process (described in detail below with reference to FIG. 8), and KPI calculation process (described in detail below with reference to FIG. 9). The control unit also functions as an interface between the storage unit and the communication unit.

[0050] As shown in FIG. 2, the control unit has the functional blocks of a definition unit 210 and an evaluation unit 220 .

[0051] The definition unit 210 includes the following functional blocks: a graph definition unit 211 , a KPI definition unit 212 , and an issue relationship definition unit 213 .

[0052] The graph definition unit 211 executes graph definition processing (described in detail below with reference to FIG. 5).

[0053] The KPI definition unit 212 executes a KPI relationship definition process (described in detail below with reference to FIG. 6).

[0054] The task relationship definition unit 213 executes task relationship definition processing (described in detail below with reference to FIG. 7).

[0055] The evaluation unit 220 includes the functional blocks of a task selection unit 221 and a KPI calculation unit 222 .

[0056] The task selection unit 221 executes a task selection process (described in detail below with reference to FIG. 8).

[0057] The KPI calculation unit 222 executes a KPI calculation process (described in detail later with reference to FIG. 9).

[0058] The control unit is configured using the processor 101, and can realize these functional blocks by executing a predetermined KPI evaluation program. Note that the control unit may be configured using a logic circuit such as an FPGA (Field Programmable Gate Array) instead of the processor 101. The control unit may also be configured by combining the processor 101 and a logic circuit.

[0059] The memory unit is configured using a storage device consisting of, for example, a storage device 103 and a memory 102, and stores programs that supply various processing instructions to the control unit, and data representing various information used in the processing executed by the control unit.

[0060] The storage unit stores at least a customer information database 230 including a stakeholder table 231 , an issue table 232 and a process table 233 , and a relationship database 240 including a KPI relationship table 241 and an issue relationship table 242 , for example.

[0061] As shown in FIG. 3, the customer information database 230 includes a stakeholder table 231, an issue table 232, and a process table 233.

[0062] The stakeholder table 231 is a table for managing information about stakeholders. The stakeholder table 231 has a record for each stakeholder. The record represents, for example, the name of the stakeholder, the names of the stakeholders connected to the stakeholder, and the relationship between them. In other words, the stakeholder table 231 manages stakeholder connections for each stakeholder by linking and recording the stakeholder name, the names of the stakeholders connected to the stakeholder, and the relationship between them for each record. In the example shown in FIG. 3, the stakeholder table 231 records that a "data analysis company" is connected to a "general company" through an "analysis service."

[0063] The issue table 232 is a table for managing information about issues faced by stakeholders. The issue table 232 has a record for each stakeholder. The record represents, for example, the name of the stakeholder, the higher-level issue for that stakeholder, and the lower-level issue for that stakeholder. In other words, the issue table 232 manages the issues faced by each stakeholder by linking and recording the stakeholder name with the higher-level issue and the lower-level issue for that stakeholder for each record. In the example shown in FIG. 3, the issue table 232 records that the higher-level issue for the "data analysis company" is "improving profit margins" and the lower-level issue is "improving processing efficiency."

[0064] The process table 233 is a table for managing information about the business processes of stakeholders. The process table 233 has a record for each stakeholder. The record represents, for example, the name of the stakeholder, the upstream process for the stakeholder, the downstream process for the stakeholder, and the related data for these processes. That is, the process table 233 manages information about the business processes of each stakeholder by linking and recording the stakeholder name with the upstream process, downstream process, and the related data for these processes for each record. In the example shown in FIG. 3 , the process table 233 records that for a "data analysis company," the upstream process is "design," the downstream process is "development," and the related data for these processes is "design data."

[0065] As shown in FIG. 4, the relationship database 240 includes a KPI relationship table 241 and an issue relationship table 242 .

[0066] The KPI relationship table 241 is a table for managing information about KPIs of stakeholders. The KPI relationship table 241 has a record for each stakeholder. The record represents, for example, the name of the stakeholder, the issue for the stakeholder, the KPI for the stakeholder, and the value of the KPI. That is, the KPI relationship table 241 manages information about the KPIs of the stakeholders for each stakeholder by linking and recording the stakeholder name, the issue for the stakeholder, the KPI for the stakeholder, and the value of the KPI for the stakeholder. In the example shown in FIG. 4, the KPI relationship table 241 records that the issue for the "data analysis company" is "processing efficiency," the KPI is "development man-hours," and the KPI value is "X."

[0067] The issue relationship table 242 is a table for managing information about issue relationships. The issue relationship table 242 has a record for each source stakeholder (hereinafter referred to as the "source stakeholder"). Each record represents, for example, the name of the source stakeholder, the issue for the source stakeholder (hereinafter referred to as the "source issue"), the name of the destination stakeholder for the source stakeholder (hereinafter referred to as the "destination stakeholder"), the issue for the destination stakeholder (hereinafter referred to as the "destination issue"), and the degree of influence. In other words, the issue relationship table 242 manages issue relationships for each source stakeholder by linking and recording the name of the source stakeholder, the source issue, the destination stakeholder name, the destination issue, and its degree of influence for each record. In the example shown in Figure 4, the issue relationship table 242 records that the source issue of the source stakeholder "data analysis company" is "processing efficiency improvement," and the destination issue of the destination stakeholder "general company" is "workload reduction," with an impact level of "1."

[0068] By reading and writing this information to the memory unit, the control unit can execute various processes such as the aforementioned graph definition process (described in detail below in relation to Figure 5), KPI relationship definition process (described in detail below in relation to Figure 6), issue relationship definition process (described in detail below in relation to Figure 7), issue selection process (described in detail below in relation to Figure 8), and KPI calculation process (described in detail below in relation to Figure 9).

[0069] The communication unit is responsible for communication processing with the user terminal 110 and other devices via the Internet (an example of the communication network 120). The communication unit is configured using, for example, a NIC (Network Interface Card) or an HBA (Host Bus Adapter).

[0070] The user interface section is configured to include functional blocks of an input section and an output section.

[0071] The input unit is responsible for input-related processing, such as accepting input operations from the user, among other processes related to the user interface. The input unit is configured using an input device 105, such as a keyboard, pointing device, or touch panel, and detects various operations from the user.

[0072] The output unit is responsible for output-related processes such as displaying various screens on a display device, outputting audio, etc. The output unit is configured using an output device (not shown) such as a liquid crystal display or a touch screen, for example.

[0073] That is, each component of the KPI evaluation system 100 is realized by hardware including a processor 101, storage devices such as memory 102 and storage device 103, wired or wireless communication lines 107 and interface devices (104, 105) that connect them, and software stored in the storage device 103 that supplies processing instructions to the computing unit.

[0074] In this embodiment, the functions of the KPI evaluation system 100 have been described as being implemented integrally by a single computer. However, these functions may be implemented by multiple interconnected computers or server devices. Furthermore, the KPI evaluation system 100 may be configured to include a general-purpose computer such as a laptop PC and a web browser installed thereon, or may be configured to include a web server and various portable devices.

[0075] Furthermore, the KPI evaluation system 100 may have other functions in addition to the various functions described above.

[0076] <Example of Processing Flow> Next, each process executed in the KPI evaluation system 100 according to the first embodiment will be described with reference to FIGS.

[0077] (Graph Definition Processing) FIG. 5 is a flowchart showing an example of the flow of graph definition processing executed by the KPI evaluation system 100 according to this embodiment.

[0078] 5, the control unit of the KPI evaluation system 100 repeatedly executes the processes of steps S501 to S508 by the graph definition unit 211 until all input is complete. As a result, the processes of steps S501 to S508 are repeatedly executed until all input is complete. When the control unit of the KPI evaluation system 100 completes the process in step S501, it proceeds to step S502.

[0079] In step S502, the control unit of the KPI evaluation system 100 executes a process in which the graph definition unit 211 receives an input operation for a graph definition via the input unit or the communication unit. This allows the input of a graph definition to be received. Note that this graph definition may receive an input operation for a portion thereof, and the entire graph definition may be inferred from similar structures in the past. When the process in step S502 is completed, the control unit of the KPI evaluation system 100 proceeds to step S503.

[0080] In step S503, the control unit of the KPI evaluation system 100 executes a process to determine whether or not a stakeholder has been defined by the graph definition unit 211. If it is determined that a stakeholder has been defined (step S503: Yes), the process proceeds to step S504 to store the defined content in the stakeholder table 231. If it is determined that a stakeholder has not been defined (step S503: No), the process proceeds directly to step S505.

[0081] In step S504, the control unit of the KPI evaluation system 100 executes processing in which the graph definition unit 211 stores the defined content in the stakeholder column, connected stakeholder column, and relation column of the stakeholder table 231. As a result, the defined content is stored in the stakeholder column, connected stakeholder column, and relation column of the stakeholder table 231. When the control unit of the KPI evaluation system 100 completes the processing in step S504, it proceeds to step S505.

[0082] In step S505, the control unit of the KPI evaluation system 100 executes a process of determining whether or not a task has been defined by the graph definition unit 211. If it is determined that a task has been defined (step S505: Yes), the process proceeds to step S506 to store the defined content in the task table 232, and if it is determined that a task has not been defined (step S505: No), the process proceeds directly to step S507.

[0083] In step S506, the control unit of the KPI evaluation system 100 executes processing in which the graph definition unit 211 stores the defined content in the stakeholder column, upper-level task column, and lower-level task column of the task table 232. As a result, the defined content is stored in the stakeholder column, upper-level task column, and lower-level task column of the task table 232. When the processing in step S506 is completed, the control unit of the KPI evaluation system 100 proceeds to step S507.

[0084] In step S507, the control unit of the KPI evaluation system 100 executes processing to determine whether or not a process has been defined by the graph definition unit 211. If it is determined that a process has been defined (step S507: Yes), the process proceeds to step S508 to store the defined content in the process table 233. If it is determined that a process has not been defined (step S507: No), the process returns to step S501 again to continue executing the graph definition processing shown in the flowchart of FIG.

[0085] In step S508, the control unit of the KPI evaluation system 100 causes the graph definition unit 211 to execute processing to store the defined content in the stakeholder column, upstream process column, downstream process column, and related data column of the process table 233. As a result, the defined content is stored in the stakeholder column, upstream process column, downstream process column, and related data column of the process table 233.

[0086] When the control unit of the KPI evaluation system 100 completes the processing in step S507 or step S508, the control unit returns to step S501 again to continue executing the graph definition processing shown in the flowchart of Fig. 5. After that, when the processing in steps S501 to S508 is repeatedly executed until all inputs are completed, the control unit of the KPI evaluation system 100 proceeds to step S509.

[0087] In step S509, the control unit of the KPI evaluation system 100 executes processing to call the KPI definition unit 212 using the graph definition unit 211. This calls the KPI definition unit 212, and following the graph definition processing shown in the flowchart of Fig. 5, it is possible to execute the KPI relationship definition processing shown in the flowchart of Fig. 6. When the processing in step S509 is completed, the control unit of the KPI evaluation system 100 ends the graph definition processing shown in the flowchart of Fig. 5.

[0088] (KPI Relationship Definition Processing) FIG. 6 is a flowchart showing an example of the flow of KPI relationship definition processing executed by the KPI evaluation system 100 according to this embodiment.

[0089] 6, the control unit of the KPI evaluation system 100 repeatedly executes the processes of steps S601 to S607 by the KPI definition unit 212 until all input is completed. As a result, the processes of steps S601 to S607 are repeatedly executed until all input is completed. When the control unit of the KPI evaluation system 100 completes the process in step S601, it proceeds to step S602.

[0090] In step S602, the control unit of the KPI evaluation system 100 executes a process in which the KPI definition unit 212 receives an input operation for the KPI relationship definition via the input unit or the communication unit. This allows the input of the KPI relationship definition to be received. Note that this KPI relationship definition may receive an input operation for a portion thereof, and the entire definition may be inferred from past similar structures. When the process in step S602 is completed, the control unit of the KPI evaluation system 100 proceeds to step S603.

[0091] In step S603, the control unit of the KPI evaluation system 100 executes a process of retaining the stakeholders, issues, and KPIs using the KPI definition unit 212. As a result, the stakeholders, issues, and KPIs are retained. Upon completing the process in step S603, the control unit of the KPI evaluation system 100 proceeds to step S604.

[0092] 6, the control unit of the KPI evaluation system 100 repeatedly executes the processes of steps S604 to S606 by the KPI definition unit 212 until the processes are completed for all of the process tables 233. As a result, the processes of steps S604 to S606 are repeatedly executed until the processes are completed for all of the process tables 233. When the control unit of the KPI evaluation system 100 completes the process in step S604, it proceeds to step S605.

[0093] In step S605, the control unit of the KPI evaluation system 100 causes the KPI definition unit 212 to execute processing to acquire the upstream process, downstream process, and related data from the record with the matching stakeholder in the process table 233. As a result, the upstream process, downstream process, and related data are acquired from the record with the matching stakeholder in the process table 233. When the control unit of the KPI evaluation system 100 completes the processing in step S605, it proceeds to step S606.

[0094] In step S606, the control unit of the KPI evaluation system 100 executes a process of calculating a KPI value based on the process connections and related data using the KPI definition unit 212. As a result, the KPI value is calculated based on the process connections and related data. Note that the KPI may be extracted from the process using 1DCAE, TOC, or the like. Also, the method of calculating the KPI may be defined in advance. When the process in step S606 is completed, the control unit of the KPI evaluation system 100 proceeds to step S607.

[0095] When the control unit of the KPI evaluation system 100 completes the process in step S606, the control unit returns to step S604 again to continue executing the process. After that, when the processes in steps S604 to S606 are repeatedly executed until the processes are completed for all of the process tables 233, the control unit of the KPI evaluation system 100 proceeds to step S607.

[0096] In step S607, the control unit of the KPI evaluation system 100 causes the KPI definition unit 212 to execute processing to store the results of the processing up to step S606 in the stakeholder column, issue column, KPI column, and KPI value column of the KPI relationship table 241. As a result, the results of the processing up to step S606 are stored in the stakeholder column, issue column, KPI column, and KPI value column of the KPI relationship table 241.

[0097] When the control unit of the KPI evaluation system 100 completes the process in step S607, the process returns to step S601 again to continue executing the KPI relationship definition process shown in the flowchart of Fig. 6. After that, the processes in steps S601 to S607 are repeatedly executed until all inputs are completed, and then the control unit of the KPI evaluation system 100 proceeds to step S608.

[0098] In step S608, the control unit of the KPI evaluation system 100 executes processing to call the issue relationship definition unit 213 via the KPI definition unit 212. This calls the issue relationship definition unit 213, and following the KPI relationship definition processing shown in the flowchart of Fig. 6, it is possible to execute the issue relationship definition processing shown in the flowchart of Fig. 7. When the processing in step S608 is completed, the control unit of the KPI evaluation system 100 ends the KPI relationship definition processing shown in the flowchart of Fig. 6.

[0099] (Task Relationship Definition Processing) FIG. 7 is a flowchart showing an example of the flow of task relationship definition processing executed by the KPI evaluation system 100 according to this embodiment.

[0100] 7, the control unit of the KPI evaluation system 100 repeatedly executes the processing of steps S701 to S703 by the issue relationship definition unit 213 until all input is complete. As a result, the processing of steps S701 to S703 is repeatedly executed until all input is complete. When the control unit of the KPI evaluation system 100 completes the processing in step S701, it proceeds to step S702.

[0101] In step S702, the control unit of the KPI evaluation system 100 executes a process in which the issue relationship definition unit 213 receives an input operation for the issue relationship definition via the input unit or communication unit. This allows the input of the issue relationship definition to be received. Note that this issue relationship definition may receive an input operation for a portion thereof, and the entire definition may be inferred from similar structures in the past. When the process in step S702 is completed, the control unit of the KPI evaluation system 100 proceeds to step S703.

[0102] In step S703, the control unit of the KPI evaluation system 100 causes the issue relationship definition unit 213 to execute a process of storing the content of the input operation received in step S702 in the related source stakeholder column, related source issue column, related destination stakeholder column, related destination issue column, and impact column of the issue relationship table 242. As a result, the content of the input operation is stored in the related source stakeholder column, related source issue column, related destination stakeholder column, related destination issue column, and impact column of the issue relationship table 242.

[0103] When the control unit of the KPI evaluation system 100 completes the processing in step S703, the control unit returns to step S701 again to continue executing the task relationship definition processing shown in the flowchart of Fig. 7. After that, when the processing in steps S701 to S703 is repeatedly executed until all inputs are completed, the control unit of the KPI evaluation system 100 ends the task relationship definition processing shown in the flowchart of Fig. 7.

[0104] (Issue Selection Process) FIG. 8 is a flowchart showing an example of the flow of the issue selection process executed by the KPI evaluation system 100 according to this embodiment.

[0105] In step S801, the control unit of the KPI evaluation system 100 executes a process of accepting a selection operation of a stakeholder and an issue by the issue selection unit 221. This allows the selection of a stakeholder and an issue to be accepted. When the control unit of the KPI evaluation system 100 completes the process in step S801, the process proceeds to step S802.

[0106] 8, the control unit of the KPI evaluation system 100 causes the issue selection unit 221 to repeatedly execute the processes of steps S802 to S804 until the processes are completed for all records in the issue relationship table 242. As a result, the processes of steps S802 to S804 are repeatedly executed until the processes are completed for all records in the issue relationship table 242. When the control unit of the KPI evaluation system 100 completes the process in step S802, it proceeds to step S803.

[0107] In step S803, the control unit of the KPI evaluation system 100 executes a process to acquire a related stakeholder and a related destination issue from records in which the stakeholder and the related source stakeholder, and the issue and the related source issue match, respectively, using the issue selection unit 221. As a result, the related destination stakeholder and the related destination issue are acquired from records in which the stakeholder and the related source stakeholder, and the issue and the related source issue match, respectively. When the control unit of the KPI evaluation system 100 completes the process in step S803, it proceeds to step S804.

[0108] In step S804, the control unit of the KPI evaluation system 100 executes a process of retaining the related stakeholder as a stakeholder and the related issue as an issue using the issue selection unit 221. As a result, the related stakeholder is retained as a stakeholder and the related issue is retained as an issue. When the control unit of the KPI evaluation system 100 completes the process in step S804, it proceeds to step S805.

[0109] When the control unit of the KPI evaluation system 100 completes the process in step S804, the control unit returns to step S802 again to continue executing the process. After that, when the processes in steps S802 to S804 are repeatedly executed until the processes are completed for all of the issue relationship tables 242, the control unit of the KPI evaluation system 100 proceeds to step S805.

[0110] 8, the control unit of the KPI evaluation system 100 causes the issue selection unit 221 to repeatedly execute the processes of steps S805 to S807 until the process is completed for all records in the issue table 232. As a result, the processes of steps S805 to S807 are repeatedly executed until the process is completed for all records in the issue table 232. When the process in step S805 is completed, the control unit of the KPI evaluation system 100 proceeds to step S806.

[0111] In step S806, the control unit of the KPI evaluation system 100 causes the issue selection unit 221 to execute a process of acquiring lower-level issues from records in which the stakeholder and the stakeholder, and the issue and the higher-level issue, respectively, match. As a result, lower-level issues are acquired from records in which the stakeholder and the stakeholder, and the issue and the higher-level issue, respectively, match. When the control unit of the KPI evaluation system 100 completes the process in step S806, it proceeds to step S807.

[0112] In step S807, the control unit of the KPI evaluation system 100 executes a process of retaining the stakeholder as a stakeholder and the sub-task as a task by the task selection unit 221. As a result, the stakeholder is retained as a stakeholder and the sub-task is retained as a task.

[0113] When the control unit of the KPI evaluation system 100 completes the process in step S807, the control unit returns to step S805 again to continue executing the process. After that, the processes in steps S805 to S807 are repeatedly executed until the process is completed for all of the issue tables 232, and then the control unit of the KPI evaluation system 100 proceeds to step S808.

[0114] In step S808, the control unit of the KPI evaluation system 100 executes processing in which the issue selection unit 221 calls the KPI calculation unit 222 using the held list of stakeholders and issues as arguments. As a result, the KPI calculation unit 222 is called using the held list of stakeholders and issues as arguments, and the KPI calculation processing shown in the flowchart of Fig. 9 can be executed following the issue selection processing shown in the flowchart of Fig. 8. When the processing in step S808 is completed, the control unit of the KPI evaluation system 100 ends the issue selection processing shown in the flowchart of Fig. 8.

[0115] (KPI Calculation Process) FIG. 9 is a flowchart showing an example of the flow of the KPI calculation process executed by the KPI evaluation system 100 according to this embodiment.

[0116] In step S901, the control unit of the KPI evaluation system 100 causes the KPI calculation unit 222 to execute processing to receive a list of stakeholders and issues from the issue selection unit 221. This allows the control unit of the KPI evaluation system 100 to receive a list of stakeholders and issues from the issue selection unit 221. When the processing in step S901 is completed, the control unit of the KPI evaluation system 100 proceeds to step S902.

[0117] 9, the control unit of the KPI evaluation system 100 repeatedly executes the processes of steps S902 to S903 by the KPI calculation unit 222 until the processes are completed for all lists. As a result, the processes of steps S902 to S903 are repeatedly executed until the processes are completed for all lists. When the control unit of the KPI evaluation system 100 completes the process in step S902, it proceeds to step S903.

[0118] In step S903, the control unit of the KPI evaluation system 100 causes the KPI calculation unit 222 to execute a process of acquiring KPIs and KPI values ​​from records in the KPI relationship table 241 in which the stakeholder and issue match. As a result, KPIs and KPI values ​​are acquired from records in the KPI relationship table 241 in which the stakeholder and issue match.

[0119] When the control unit of the KPI evaluation system 100 completes the process in step S903, the control unit returns to step S902 again to continue executing the process. After that, when the processes in steps S902 to S903 are repeatedly executed until the processes are completed for all lists, the control unit of the KPI evaluation system 100 proceeds to step S904.

[0120] In step S904, the control unit of the KPI evaluation system 100 executes a process of outputting KPIs and KPI values ​​for each stakeholder using the KPI calculation unit 222. As a result, KPIs and KPI values ​​are output for each stakeholder. Upon completing the process in step S904, the control unit of the KPI evaluation system 100 ends the KPI calculation process shown in the flowchart of FIG.

[0121] <Configuration Example of KPI Evaluation System 100> Next, a configuration example of the KPI evaluation system 100 according to the second embodiment will be described with reference to FIGS. 1 and 10. FIG.

[0122] (Example of overall system configuration) The overall system configuration of the KPI evaluation system 100 according to Example 2 is similar to the example of the overall system configuration of the KPI evaluation system 100 according to Example 1 described above with reference to Figure 1, so a description thereof will be omitted.

[0123] (Example of hardware configuration of KPI evaluation system 100 and user terminal 110) Furthermore, the hardware configuration of the KPI evaluation system 100 and user terminal 110 according to Example 2 is similar to the example of the hardware configuration of the KPI evaluation system 100 and user terminal 110 according to Example 1 described above with reference to Figure 1, and therefore a description thereof will be omitted.

[0124] (Example of Functional Blocks of KPI Evaluation System 100 According to Example 2) Next, an example of functional blocks included in the KPI evaluation system 100 according to Example 2 will be described with reference to Fig. 10. Note that each block described below does not represent a hardware-based configuration, but represents a functional block.

[0125] 10 , the KPI evaluation system 100 according to the second embodiment has the following differences in the configuration of each functional block of the control unit and the storage unit compared to the KPI evaluation system 100 according to the first embodiment. As the other configurations of the KPI evaluation system 100 according to the second embodiment are the same as those of the KPI evaluation system 100 according to the first embodiment, only the differences will be described here.

[0126] 10 , the evaluation unit 220 of the control unit includes the function blocks of a task selection unit 221, a KPI calculation and storage unit 223, a UI control unit 224, and an accumulation reference unit 225. That is, compared to the evaluation unit 220 of the KPI evaluation system 100 of the first embodiment, the evaluation unit 220 of the KPI evaluation system 100 of the second embodiment does not include the KPI calculation unit 222, but instead includes the KPI calculation and storage unit 223, the UI control unit 224, and the accumulation reference unit 225.

[0127] The KPI calculation accumulation unit 223 executes a KPI calculation accumulation process (described in detail later with reference to FIG. 12).

[0128] The UI control unit 224 executes a UI control process (described in detail below with reference to FIG. 13).

[0129] The storage reference unit 225 executes a storage reference process (described in detail later with reference to FIG. 15).

[0130] 10 , in the KPI evaluation system 100 according to the second embodiment, the relationship database 240 stored in the storage unit includes a KPI relationship table 241, an assignment relationship table 242, and a KPI evaluation table 243. That is, the relationship database 240 included in the KPI evaluation system 100 according to the second embodiment further includes a KPI evaluation table 243, as compared with the relationship database 240 included in the KPI evaluation system 100 according to the first embodiment.

[0131] The KPI evaluation table 243 is a table for managing information about stakeholder evaluations of KPIs (hereinafter referred to as "KPI evaluations"). The KPI evaluation table 243 has a record for each stakeholder. The record represents, for example, the stakeholder's selected issue, an evaluation value of the KPI for the selected issue by a data analysis company, and an evaluation value of the KPI by a general company. In other words, the KPI evaluation table 243 manages information about KPI evaluations for each stakeholder by linking and recording, for each record, the stakeholder's name, the stakeholder's selected issue, the evaluation value of the KPI for the selected issue by a data analysis company, and the evaluation value of the KPI by a general company. In the example shown in FIG. 4, the KPI evaluation table 243 records that the selected issue for the "data analysis company" is "improving processing efficiency," that the evaluation value of the KPI for the selected issue by the data analysis company is "α=X, β=Y," and that the evaluation value of the KPI by the general company is "γ=Z."

[0132] <Example of Processing Flow> Next, each process executed by the KPI evaluation system 100 according to the second embodiment will be described with reference to FIGS.

[0133] (KPI Calculation and Accumulation Processing) FIG. 12 is a flowchart showing an example of the flow of KPI calculation and accumulation processing executed by the KPI evaluation system 100 according to this embodiment.

[0134] In step S1201, the control unit of the KPI evaluation system 100 executes processing to receive a list of stakeholders and issues from the issue selection unit 221 using the KPI calculation and accumulation unit 223. This allows the control unit of the KPI evaluation system 100 to receive a list of stakeholders and issues from the issue selection unit 221. When the processing in step S1201 is completed, the control unit of the KPI evaluation system 100 proceeds to step S1202.

[0135] 12, the control unit of the KPI evaluation system 100 repeatedly executes the processes of steps S1202 to S1203 by the KPI calculation and accumulation unit 223 until the processes are completed for all lists. As a result, the processes of steps S1202 to S1203 are repeatedly executed until the processes are completed for all lists. When the control unit of the KPI evaluation system 100 completes the process in step S1202, it proceeds to step S1203.

[0136] In step S1203, the control unit of the KPI evaluation system 100 causes the KPI calculation and accumulation unit 223 to execute a process of acquiring KPIs and KPI values ​​from records in the KPI relationship table 241 in which the stakeholder and issue match. As a result, KPIs and KPI values ​​are acquired from records in the KPI relationship table 241 in which the stakeholder and issue match.

[0137] When the control unit of the KPI evaluation system 100 completes the process in step S1203, the control unit returns to step S1202 again to continue executing the process. After that, when the processes in steps S1202 to S1203 are repeatedly executed until the processes are completed for all lists, the control unit of the KPI evaluation system 100 proceeds to step S1204.

[0138] In step S1204, the control unit of the KPI evaluation system 100 executes a process in which the KPI calculation and accumulation unit 223 stores the issues as an array in the selected issue column and stores KPI=KPI values ​​as an array in the column corresponding to the stakeholder name in the KPI evaluation table 243. As a result, in the KPI evaluation table 243, the issues are stored as an array in the selected issue column and KPI=KPI values ​​are stored as an array in the column corresponding to the stakeholder name. When the process in step S1204 is completed, the control unit of the KPI evaluation system 100 proceeds to step S1205.

[0139] In step S1205, the control unit of the KPI evaluation system 100 executes a process of outputting KPIs and KPI values ​​for each stakeholder using the KPI calculation and accumulation unit 223. As a result, KPIs and KPI values ​​are output for each stakeholder. Upon completing the process in step S1205, the control unit of the KPI evaluation system 100 ends the KPI calculation and accumulation process shown in the flowchart of FIG.

[0140] (UI Control Processing) FIG. 13 is a flowchart showing an example of the flow of UI control processing executed by the KPI evaluation system 100 according to this embodiment.

[0141] In step S1301, the control unit of the KPI evaluation system 100 causes the UI control unit 224 to execute processing for referencing the stakeholder table 231, the issue table 232, and the process table 233. This causes reference to the stakeholder table 231, the issue table 232, and the process table 233. Upon completing the processing in step S1301, the control unit of the KPI evaluation system 100 proceeds to step S1302.

[0142] In step S1302, the control unit of the KPI evaluation system 100 causes the UI control unit 224 to execute processing for referencing the issue relationship table 242 and the KPI relationship table 241. This causes reference to the issue relationship table 242 and the KPI relationship table 241. Upon completing the processing in step S1302, the control unit of the KPI evaluation system 100 proceeds to step S1303.

[0143] In step S1303, the control unit of the KPI evaluation system 100 executes processing to display the reference result on the KPI evaluation screen D1400 illustrated in Fig. 14 by the UI control unit 224. As a result, the reference result is displayed on the KPI evaluation screen D1400 illustrated in Fig. 14. When the processing in step S1303 is completed, the control unit of the KPI evaluation system 100 proceeds to step S1304.

[0144] In step S1304, the control unit of the KPI evaluation system 100 executes a process of determining whether or not to select an issue using the UI control unit 224. If it is determined that an issue is to be selected (step S1304: Yes), the process proceeds to step S1305 to select an issue, and if it is determined that an issue is not to be selected (step S1304: No), the process proceeds directly to step S1306.

[0145] In step S1305, the control unit of the KPI evaluation system 100 executes processing to call the issue selection unit 221 by the UI control unit 224. As a result, the issue selection unit 221 is called and processing to select an issue is executed. When the processing in step S1305 is completed, the control unit of the KPI evaluation system 100 proceeds to step S1306.

[0146] In step S1306, the control unit of the KPI evaluation system 100 executes a process of determining whether or not to set a target value by the UI control unit 224. If it is determined that a target value is to be set (step S1306: Yes), the process proceeds to step S1307 to set the target value, and if it is determined that a target value is not to be set (step S1306: No), the process proceeds directly to step S1310.

[0147] In step S1307, the control unit of the KPI evaluation system 100 executes processing to call the accumulation reference unit 225 using the stakeholder, KPI, and KPI value as arguments through the UI control unit 224. As a result, the accumulation reference unit 225 is called using the stakeholder, KPI, and KPI value as arguments. Upon completing the processing in step S1307, the control unit of the KPI evaluation system 100 proceeds to step S1308.

[0148] In step S1308, the control unit of the KPI evaluation system 100 causes the UI control unit 224 to execute processing to receive the list of stakeholders and issues from the accumulation reference unit 225. This allows the list of stakeholders and issues to be received from the accumulation reference unit 225. Upon completing the processing in step S1308, the control unit of the KPI evaluation system 100 proceeds to step S1309.

[0149] In step S1309, the control unit of the KPI evaluation system 100 executes processing for displaying the processing results on the KPI evaluation screen D1400 illustrated in Fig. 14 by the UI control unit 224. As a result, the processing results are displayed on the KPI evaluation screen D1400 illustrated in Fig. 14. When the processing in step S1309 is completed, the control unit of the KPI evaluation system 100 proceeds to step S1310.

[0150] In step S1310, the control unit of the KPI evaluation system 100 executes a process of determining whether or not to close the KPI evaluation screen D1400 using the UI control unit 224. If it is determined that the KPI evaluation screen D1400 should be closed (step S1310: Yes), the UI control process shown in the flowchart of Fig. 13 is terminated. On the other hand, if it is determined that the KPI evaluation screen D1400 should not be closed (step S1310: No), the process returns to step S1304 again to continue the UI control process.

[0151] (Storage Reference Process) FIG. 15 is a flowchart showing an example of the flow of the storage reference process executed by the KPI evaluation system 100 according to this embodiment.

[0152] In step S1501, the control unit of the KPI evaluation system 100 executes processing to acquire the stakeholders, KPIs, and KPI values ​​from the UI control unit 224 using the storage reference unit 225. As a result, the stakeholders, KPIs, and KPI values ​​are acquired from the UI control unit 224. Upon completing the processing in step S1501, the control unit of the KPI evaluation system 100 proceeds to step S1502.

[0153] 15, the control unit of the KPI evaluation system 100 repeatedly executes the processes of steps S1502 to S1505 by the accumulation reference unit 225 until the processes are completed for all of the KPI evaluation tables 243. As a result, the processes of steps S1502 to S1505 are repeatedly executed until the processes are completed for all of the KPI evaluation tables 243. When the control unit of the KPI evaluation system 100 completes the process in step S1502, it proceeds to step S1503.

[0154] In step S1503, the control unit of the KPI evaluation system 100 executes a process of acquiring records containing an array in which KPIs match columns containing matching stakeholders, using the storage reference unit 225. This acquires records containing an array in which KPIs match columns containing matching stakeholders. When the process in step S1503 is completed, the control unit of the KPI evaluation system 100 proceeds to step S1504.

[0155] In step S1504, the control unit of the KPI evaluation system 100 executes a process of calculating the similarity between the target value and the KPI value of the record using the accumulation reference unit 225. This calculates the similarity between the target value and the KPI value of the record. Note that this similarity may be evaluated using a method such as cosine distance, or may be evaluated as a small difference or ratio. Upon completing the process in step S1504, the control unit of the KPI evaluation system 100 proceeds to step S1505.

[0156] In step S1505, the control unit of the KPI evaluation system 100 executes a process of storing a record with a higher similarity if the record with a higher similarity is found, by the storage reference unit 225. As a result, if a record with a higher similarity is found, the record is stored.

[0157] When the control unit of the KPI evaluation system 100 completes the process in step S1505, the process returns to step S1502 again to continue executing the storage reference process shown in the flowchart of Fig. 15. After that, the processes of steps S1502 to S1505 are repeatedly executed until the process is completed for all of the KPI evaluation tables 243, and then the control unit of the KPI evaluation system 100 proceeds to step S1506.

[0158] In step S1506, the control unit of the KPI evaluation system 100 returns the list of stakeholders and issues of the retained records through the accumulation reference unit 225. As a result, the list of stakeholders and issues of the retained records is returned. Upon completing the processing in step S1506, the control unit of the KPI evaluation system 100 ends the accumulation reference processing shown in the flowchart of FIG.

[0159] The above-described embodiment of the present invention can be summarized as follows.

[0160] (1) The KPI evaluation system 100 is a system for evaluating a stakeholder's business KPIs (Key Performance Indicators). A computer including at least a processor 101, a memory 102, and a storage device 103 defines relationships between issues for two or more stakeholders, including the stakeholder, and associates KPI settings for other stakeholders with each stakeholder's issues based on the defined relationships between the issues. In this manner, the KPI evaluation system 100 can define KPI relationships between stakeholders based on issues and express interrelationships. As a result, a user of the KPI evaluation system 100 can obtain multiple solutions that are harmonious overall while taking feasibility into consideration. This allows the user to analyze business KPIs, determine the scope and prioritization of issues while grasping the overall KPI, and derive measures that are harmonious overall from the perspective of both the company and the customer's value.

[0161] (2) A task is defined as a task tree represented in tree format.

[0162] (3) Define issues related to multiple KPIs from the business and behavioral processes of the relevant stakeholders.

[0163] (4) When a part of a definition is input, the entire definition is inferred from similar past structures.

[0164] (5) Calculate the changes in multiple KPIs for each stakeholder according to the selection of the issue tree.

[0165] (6) The range of selection for the issue tree toward the target value is suggested based on the change in KPI of each stakeholder.

[0166] The present invention is not limited to the above-described embodiment, and can be implemented using any components without departing from the spirit of the present invention.

[0167] The above-described embodiments, examples, and modifications are merely examples, and the present invention is not limited to these details as long as the features of the invention are not impaired. Furthermore, although various embodiments, examples, and modifications have been described above, the present invention is not limited to these details. Other aspects that can be considered within the scope of the technical idea of ​​the present invention are also included within the scope of the present invention.

[0168] In the above figures, the control lines and information lines shown are those that are considered necessary for explanation, and do not necessarily show all the control lines and information lines that are actually implemented. For example, it can be considered that almost all components are actually connected to each other.

[0169] The above-described layout of the functional units of the KPI evaluation system 100 is merely an example. The layout of the functional units can be changed to an optimal layout in terms of the performance, processing efficiency, communication efficiency, etc. of the hardware and software included in the KPI evaluation system 100.

[0170] 100: KPI evaluation system

Claims

1. A KPI evaluation system for evaluating a stakeholder's business KPIs (Key Performance Indicators), comprising: a computer having at least a processor, memory, and a storage device; defining relationships between issues of each stakeholder for two or more stakeholders including the stakeholder; and associating KPI settings of a stakeholder other than the stakeholder with the issues of each stakeholder based on the defined relationships between the issues.

2. The KPI evaluation system according to claim 1, wherein the issues are defined as an issue tree represented in a tree format.

3. The KPI evaluation system according to claim 1, further comprising: defining issues related to a plurality of KPIs from the business / behavioral processes of said stakeholders.

4. A KPI evaluation system according to any one of claims 1 to 3, wherein when a portion of the definition is input, the entire definition is inferred from similar structures in the past.

5. The KPI evaluation system according to claim 2, further comprising: a step of calculating changes in multiple KPIs for each stakeholder in response to the selection of the issue tree.

6. The KPI evaluation system according to claim 2, wherein a selection range of an issue tree toward the target value is suggested from the KPI changes of each stakeholder.

7. A KPI evaluation method for evaluating a stakeholder's business KPIs (Key Performance Indicators), comprising: a computer having at least a processor, a memory, and a storage device; defining relationships between issues of each stakeholder for two or more stakeholders including the stakeholder; and associating KPI settings of a stakeholder different from the stakeholder to the issues of each stakeholder based on the defined relationships between the issues.

Images