Causal loop diagram processing system, causal loop diagram processing method, and causal loop diagram processing program

Abstract

To easily and appropriately calculate the importance of KPIs that constitute a causal loop diagram.SOLUTION: A CVD processing apparatus 100 for processing a causal loop diagram having a plurality of KPIs as elements, comprises at least one processor 131. The processor 131 is configured to accept, from one or more users, evaluation values relating to the importance of the KPIs in the causal loop diagram, and calculate the importance of each KPI in the causal loop diagram based on the accepted evaluation values. The processor 131 may calculate the weight of each KPI in the causal loop diagram based on the accepted evaluation value and the connection relations of the plurality of KPIs configuring the causal loop diagram.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a technique for processing a causal loop diagram (CLD) having elements such as KPIs, for example city KPIs. [Background technology]

[0002] A configuration is known for finding the most reliable correlation of causal relationships by integrating expert knowledge and data (see, for example, Patent Document 1). In the technology of Patent Document 1, experimental data, planner's knowledge, etc. are used to support the user when the user formulates a planning policy. Also, in the technology of Patent Document 1, knowledge on causal relationships from both experts and actual data can be input to the system, and the computing device outputs causal inferences that are displayed by a design support system including an output device. This is mainly related to business support, but can also be generalized.

[0003] So there are two sets of causal relationships, and the system uses both of these pieces to build the CLD. And finally, the correlations between insights and actionable data are integrated, either complementary or by correction. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2021-144481 A Summary of the Invention [Problem to be solved by the invention]

[0005] For example, there is a demand to make local government decision-making easier and more efficient. A CLD, which is rich in variables, is not easy to use, understand and adapt to the specific needs of every user. If the structure of the CLD is too generalized, it becomes too complex for practical use and it becomes difficult to understand which issues have priority.

[0006] Therefore, there is no way to focus on one high-priority perspective at a time to facilitate specific policy making. Furthermore, there is no value in using a static CLD system with unchanging variables in a dynamically changing context like a city, since there is no way to record and reuse common patterns that emerge from the discussions (e.g., the need for new urban variables to be considered, changing priorities, etc.).

[0007] There is a need for a way for urban planners to dynamically visualize urban dynamics based on their changing priorities and needs, facilitating targeted policy creation.

[0008] The present invention has been made in consideration of the above circumstances, and has an object to provide a technique that can easily and appropriately calculate the importance of KPIs (Key Performance Indicators) that make up a causal loop diagram. [Means for solving the problem]

[0009] In order to achieve the above-mentioned object, a causal loop diagram processing device according to one aspect is a causal loop diagram processing device that processes a causal loop diagram having a plurality of KPIs as elements, and is equipped with at least one processor, and the processor receives evaluation values ​​regarding the importance of KPIs in the causal loop diagram from one or more users, and calculates the importance of each KPI in the causal loop diagram based on the received evaluation values. Effect of the Invention

[0010] According to the present invention, it is possible to easily and appropriately calculate the importance of KPIs that constitute a causal loop diagram. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a computer system according to an embodiment. [Diagram 2] FIG. 2 is a configuration diagram of a common KPI table according to an embodiment. [Diagram 3] FIG. 3 is a configuration diagram of a tag table according to an embodiment. [Figure 4] FIG. 4 is a diagram showing the structure of a subtag table according to an embodiment. [Diagram 5] FIG. 5 is a configuration diagram of a KPI detail table according to an embodiment. [Figure 6] FIG. 6 is a configuration diagram of a KPI connection link table according to an embodiment. [Figure 7] FIG. 7 is a sequence diagram of an initial KPI network configuration process according to an embodiment. [Figure 8] FIG. 8 is a sequence diagram of a CLD display process according to an embodiment. [Figure 9] FIG. 9 is a flowchart of a weight calculation process during initial processing according to an embodiment. [Figure 10] FIG. 10 is a flowchart of a weight calculation process when a KPI evaluation is changed according to an embodiment. [Figure 11] FIG. 11 is a flowchart of a weight calculation process when a KPI is added according to an embodiment. [Figure 12] FIG. 12 is a diagram illustrating a specific example of the weight calculation process according to an embodiment. [Figure 13] FIG. 13 is a diagram showing the configuration of a first CLD display screen according to an embodiment. [Figure 14] FIG. 14 is a diagram showing the configuration of a second CLD display screen according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] The following embodiments will be described with reference to the drawings. Note that the following embodiments do not limit the scope of the invention, and not all of the elements and combinations thereof described in the embodiments are necessarily essential to the solution of the invention.

[0013] In the following description, information may be described using the expression "AAA table", but the information may be expressed in any data structure. In other words, to show that the information does not depend on the data structure, the "AAA table" may be called "AAA information".

[0014] In addition, in the following description, the processing may be described with a "program" as the operating subject, but since the program is executed by a processor to perform a defined processing while appropriately using at least one of the storage resource and the interface unit, the operating subject of the processing may be the processor (or a computer (device) having a processor, or a computer system). The program may be installed on the computer from a program source. The program source may be, for example, a program distribution server or a recording medium readable by a computer. In the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs. Furthermore, at least a part of the processing realized by executing a program may be realized by a hardware circuit (for example, an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array)).

[0015] FIG. 1 is a diagram showing the overall configuration of a computer system according to an embodiment.

[0016] The computer system 10 includes a CLD processing device 100 as an example of a causal loop diagram processing system, and one or more terminals 150. The CLD processing device 100 and the terminals 150 are connected via a network 140 such as the Internet.

[0017] The terminal 150 is a device used by an administrator who manages the CLD processing device 100 or a user who uses the CLD processing device 100 to refer to a CL, and accepts various information input from the administrator or user, transmits it to the CLD processing device 100, and displays information (various screens, etc.) transmitted from the CLD processing device 100. The terminal 150 may be, for example, a PC (Personal Computer), a smartphone, a public I / F (for example, a touch panel at a WS (workshop) venue), or other devices.

[0018] The CLD processing device 100 includes a memory 110, a storage unit 120 as an example of a storage resource, an I / F (interface) device 130, a processor 131, and an input / output device 132.

[0019] The I / F device 130 mediates data exchange between the processor 131 and the input / output device 132 , and communication between the processor 131 and the terminal 150 via the network 140 .

[0020] The processor 131 executes various processes according to programs stored in the memory 110 and / or the storage unit 120. The processor 131 is, for example, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (Field Programmable Gate Array), or other semiconductor devices capable of performing calculations.

[0021] The memory 110 is, for example, a RAM (RANDOM ACCESS MEMORY), and stores programs executed by the processor 131 and necessary information. In this embodiment, the memory 110 stores a weight calculation program 111 and a KPI network / CLD generation program 112. In this embodiment, the weight calculation program 111 and the KPI network / CLD generation program 112 correspond to the causal loop diagram processing program.

[0022] The storage unit 120 is, for example, a hard disk or a flash memory, and stores programs executed by the processor 131 and data used by the processor 131. In this embodiment, the storage unit 120 stores a common KPI DB (database) 121, a tag DB 122, and a KPI network DB 123.

[0023] The common KPI DB 121 stores a common KPI table 200 (see FIG. 2). The tag DB 122 stores a tag table 300 (see FIG. 3) and a subtag table 310 (see FIG. 4). The KPI network DB 123 stores a KPI detail table 400 (see FIG. 5) and a KPI connection link table 410 (see FIG. 6).

[0024] The input / output device 132 includes, for example, an input device such as a mouse or a keyboard that accepts input of various types of information, and an output device such as a display that outputs various types of information.

[0025] Next, the common KPI table 200 will be described.

[0026] FIG. 2 is a configuration diagram of a common KPI table according to an embodiment.

[0027] The common KPI table 200 stores an entry for each KPI corresponding to an element (node) of the CLD. The entry of the common KPI table 200 includes fields of KPI_ID 201, KPI name 202, and tag-subtag ID 203.

[0028] KPI_ID 201 stores the ID (KPI_ID) of the KPI corresponding to the entry. KPI name 202 stores the name of the KPI corresponding to the entry (KPI name). Tag-subtag ID 203 stores the IDs (tag ID, subtag ID) of the tag to which the KPI corresponding to the entry belongs (main tag: category to which the KPI belongs) and the subtag which is a lower category of the main tag. Note that a KPI is associated with at least one tag ID. Also, a KPI may be associated with multiple subtag IDs.

[0029] Next, the tag table 300 will be described.

[0030] FIG. 3 is a configuration diagram of a tag table according to an embodiment.

[0031] The tag table 300 stores an entry for each tag (main tag). The entry in the tag table 300 includes fields for a tag ID 301 and a tag name 302.

[0032] The tag ID of the tag corresponding to the entry is stored in the tag ID 301. The tag name 302 stores the tag name of the tag corresponding to the entry.

[0033] Next, the subtag table 310 will be described.

[0034] FIG. 4 is a diagram showing the structure of a subtag table according to an embodiment.

[0035] Subtag table 310 stores an entry for each subtag. An entry in subtag table 310 includes fields for subtag ID 311, subtag name 312, and tag ID 313.

[0036] Subtag ID 311 stores the subtag ID of the subtag corresponding to the entry. Subtag name 312 stores the subtag name of the subtag corresponding to the entry. Tag ID 313 stores the tag ID of the tag to which the subtag corresponding to the entry belongs. Note that a subtag can belong to one or more tags, and when a subtag belongs to multiple tags, tag ID 313 stores multiple tag IDs.

[0037] Next, the KPI detail table 400 will be described.

[0038] FIG. 5 is a configuration diagram of a KPI detail table according to an embodiment.

[0039] The KPI details table 400 stores an entry for each KPI. The entry in the KPI details table 400 includes fields for a KPI_ID 401, a KPI name 402, a tag-subtag ID 403, and a weight 404.

[0040] KPI_ID 401 stores the KPI_ID of the KPI corresponding to the entry. KPI name 402 stores the KPI name of the KPI corresponding to the entry. Tag-subtag ID 403 stores the IDs of the tag and subtag (tag ID, subtag ID) to which the KPI corresponding to the entry belongs. Weight 404 stores the weight (importance) of the KPI corresponding to the entry.

[0041] Next, the KPI connection link table 410 will be described.

[0042] FIG. 6 is a configuration diagram of a KPI connection link table according to an embodiment.

[0043] The KPI connection link table 410 stores an entry for each link that connects KPIs. The entry in the KPI connection link table 410 includes fields for a link ID 411, a connection source Kpi_ID 412, a connection destination Kpi_ID 413, and a relationship 414.

[0044] Link ID 411 stores the ID of the link (link ID) corresponding to the entry. Source Kpi_ID 412 stores the ID of the KPI that is the source of the link corresponding to the entry. Destination Kpi_ID 413 stores the ID of the KPI that is the destination of the link corresponding to the entry. Relationship 414 stores the type of relationship between KPIs connected by the link corresponding to the entry (for example, an increasing relationship (+) or a decreasing relationship (-)).

[0045] Next, the initial KPI network configuration process will be described.

[0046] FIG. 7 is a sequence diagram of an initial KPI network configuration process according to an embodiment.

[0047] The initial KPI network configuration process is a process in which an administrator forms an initial KPI network frame using the CLD processing device 100 before stakeholders meet at a site (eg, a workshop).

[0048] First, the terminal 150 accepts an operation from the administrator to create a list (common KPI list) of KPIs (city KPIs) for common cities that may be useful to stakeholders, and transmits the created common KPI list to the KPI network / CLD generation program 112 of the CLD processing device 100 (more precisely, the processor 131 that executes the KPI network / CLD generation program 112) (S200). Here, the common KPI list includes the KPI names, KPI connection relationships (source KPI and destination KPI; this connection relationship is represented by an arrow between KPIs in CLD), the type of relationship between KPIs, tags and subtags for each KPI, etc.

[0049] The KPI network / CLD generation program 112 of the CLD processing device 100 (more precisely, the processor 131 that executes this program) stores information of the common KPI list in the common KPI table 200 of the common KPI DB 121 (S201), and stores tag and subtag information of the common KPI list in the tag table 300 and subtag table 310 of the tag DB 122 (S202).

[0050] Furthermore, the KPI network / CLD generation program 112 of the CLD processing device 100 stores initial KPI network information (information other than the weights in the KPI detail table 400) in the KPI detail table 400 and KPI connection link table 410 of the KPI network DB 123 based on the common KPI list (S203).

[0051] The weight calculation program 111 receives the initial KPI network information from the KPI detail table 400 and the KPI connection link table 410, performs weight calculation processing to calculate the weight of each KPI based on the KPI connection relationships, and passes the processing result (KPI network information including the calculated weights) to the KPI network / CLD generation program 112 (S204). The weight calculation processing will be described later.

[0052] When the KPI network / CLD generation program 112 receives the KPI network information from the weight calculation program 111, it stores a weight in the weight 404 of the entry corresponding to each KPI in the KPI detail table 400 based on the KPI network information, and terminates the process (S205). According to this process, the weight calculated based on the connection relationships of the KPIs is stored in the weight 404 of the entry corresponding to each KPI in the KPI detail table 400.

[0053] Next, the CLD display process will be described.

[0054] FIG. 8 is a sequence diagram of a CLD display process according to an embodiment.

[0055] The CLD display process is a process in which, after one or more stakeholders have participated in a workshop, the stakeholders cause the CLD processing device 100 to display the CLD.

[0056] When the terminal 150 accepts a processing start instruction by an operation of the stakeholder, it transmits the processing start instruction to the KPI network / CLD generation program 112 of the CLD processing device 100 (more precisely, the processor 131 executing this program). If it is the first workshop, the KPI network / CLD generation program 112 generates an ID (SH ID) of the stakeholder's group and an ID (WS ID) of the workshop, and causes the KPI network DB 123 to prepare a KPI detail table 400 and a KPI connection link table 410 corresponding to the SH ID and WS ID (S301), and acquires KPI network information (KPI network frame information, tags, etc.) from these tables (S302). On the other hand, if it is not the first workshop, it identifies the WS ID of the last workshop in which the stakeholder's group participated, identifies the KPI detail table 400 and the KPI connection link table 410 corresponding to the SH ID and WS ID from the KPI network DB 123 (S301), and acquires this KPI network information (S302).

[0057] The KPI network / CLD generation program 112 creates a screen including a CLD (CLD display screens 500, 600: see Figs. 13 and 14) based on the acquired KPI network information, and displays it on the terminal 150 via the I / F device 130 (S303). Here, for example, the node of the KPI associated with the highest weight is highlighted on the screen.

[0058] Here, in the screen (CLD display screen 500) that is displayed first when the workshop is the first time, the nodes are highlighted according to the weight calculated based on the connection relationships. The connection relationships indicate how the nodes affect each other, and are therefore relatively important for establishing the priority order of the KPI nodes. For example, when a certain KPI node (here, [kpi]) is connected to many KPI nodes and many KPI nodes affect [kpi], it can be said that [kpi] has a large effect on the dynamic relationship between the nodes of the CLD. However, the stakeholder, who is an expert, has a detailed understanding of which KPI has the highest priority for a specific KPI. Therefore, in this embodiment, the displayed screen (CLD display screen 500) is configured to prompt each stakeholder to evaluate each KPI node based on the priority order. Note that when the workshop is not the first time, the KPIs may be re-evaluated on the screen. In addition, in this case, the tag may be selected, and only the KPIs belonging to the tag in the CLD may be displayed. Also, the screen may be configured to allow a new KPI to be added by specifying a tag, and an evaluation may be input for the added KPI node.

[0059] Next, the KPI network / CLD generation program 112 accepts various inputs (addition of KPIs, selection of specific tags, KPI evaluation values) from the stakeholders to the screen of the terminal 150 via the I / F device 130 (S304). For example, when a new tag or subtag is accepted, the KPI network / CLD generation program 112 stores the new tag or subtag in the tag DB 122 (S305).

[0060] In step S304, when addition of a KPI, selection of a specific tag, or a KPI evaluation value is received, the KPI network / CLD generation program 112 passes the received information to the weight calculation program 111 (S306). The weight calculation program 111 recalculates the weight of each KPI based on the received information and passes it to the KPI network / CLD generation program 112 (S307). The weight calculation program 111 also checks whether the new weight of the calculated KPI exceeds a predetermined threshold, and passes the result to the KPI network / CLD generation program 112 (S308).

[0061] As a result, if the KPI network / CLD generation program 112 receives a result indicating that the new weight exceeds the threshold value, it stores the new KPI together with the attached tag and subtag in the common KPI DB 121 (S309), and stores the KPI network information at that time, the calculated weight, and the tag in the KPI network DB 123 in association with the WS ID and SH ID (S310).

[0062] Next, the KPI network / CLD generation program 112 acquires the updated information from the KPI network DB 123, and displays a screen including the updated CLD on the terminal 150 via the I / F device 130 (S311). For example, if a tag is selected by the stakeholder in step S304, only the KPI nodes belonging to the selected tag are displayed in the CLD on the screen. This allows the stakeholder to easily identify the KPIs to be considered and the priority order of the KPIs, and based on this, can easily and appropriately create a policy to be pursued.

[0063] Next, the weight calculation process will be described in detail.

[0064] First, the weight calculation process (for example, step S204 in FIG. 7) for calculating the weight of each KPI based only on the connection relationships of the KPIs during the initial process will be described.

[0065] FIG. 9 is a flowchart of a weight calculation process during initial processing according to an embodiment.

[0066] First, the weight calculation program 111 checks (verifies) the number of edges directly connected to the KPI nodes (number of directly connected edges) for all KPI nodes in the CLD based on the KPI network information (S401). Here, the KPI node under consideration is referred to as the considered KPI node. Next, the weight calculation program 111 checks the maximum chain depth (maximum chain depth) connected to the considered KPI node (S402). Here, the chain depth is the number of edges from the farthest KPI node in a unidirectional chain to the considered KPI node.

[0067] Next, the weight calculation program 111 calculates the weight of the considered KPI node based on the number of directly connected edges for the considered KPI node and the maximum chain depth, and updates the weight in the KPI network DB 123 (S403). For example, the weight calculation program 111 calculates the weight by adding the number of directly connected edges for the considered KPI node and the maximum chain depth.

[0068] Next, the weight calculation process when the evaluation value of the KPI is changed will be described.

[0069] FIG. 10 is a flowchart of a weight calculation process when a KPI evaluation is changed according to an embodiment.

[0070] First, the weight calculation program 111 determines whether or not the stakeholder has evaluated the KPI (S411). As a result, if the stakeholder has not evaluated the KPI (S411: NO), the weight calculation program 111 ends the process.

[0071] On the other hand, if a stakeholder has evaluated a KPI (S411: YES), the weight calculation program 111 checks the average value (average evaluation value) of the evaluation values ​​by one or more stakeholders for the evaluated KPI node (considered KPI node) (S412). Next, the weight calculation program 111 checks the average evaluation values ​​of the KPI nodes adjacent to the considered KPI node, and extracts a value (adjacent influence evaluation value) that is a predetermined percentage (for example, 20%) of these average evaluation values ​​(S413).

[0072] Next, the weight calculation program 111 calculates the weight of the considered KPI node based on the average value value of the considered KPI and the total value of the adjacent influence evaluation values, and updates the weight in the KPI network DB 123 (S414). Specifically, in this embodiment, the weight W[kpi] of the considered KPI node kpi is calculated by the following formula (1).

[0073] W[kpi] = (number of directly connected edges of kpi) + (maximum chain depth of kpi) + (average evaluation value of kpi) + (sum of adjacent influence evaluation values ​​of kpi) (1)

[0074] Here, the reason why the sum of adjacent influence evaluation values ​​is taken into consideration in the weighting of the considered KPI node is that the importance of the considered KPI node is influenced by the importance of the KPIs adjacent to the considered KPI.

[0075] This weight calculation process makes it possible to calculate the weight of the KPI in which the evaluation value by the stakeholder is appropriately reflected.

[0076] Next, the weight calculation process when a KPI is added will be described.

[0077] FIG. 11 is a flowchart of a weight calculation process when a KPI is added according to an embodiment.

[0078] The weight calculation program 111 determines whether or not the stakeholder has added a new KPI (S421). As a result, if the stakeholder has not added a new KPI (S421: NO), the weight calculation program 111 ends the process.

[0079] On the other hand, if a stakeholder adds a new KPI (S421: YES), the weight calculation program 111 takes into consideration all KPI nodes in the CLD, including the new KPI, and checks the number of edges directly connected to the KPI node (number of directly connected edges) and the maximum chain depth for the KPI node under consideration, and updates the weight of each KPI node based on the number of directly connected edges and the maximum chain depth (S422).

[0080] Next, the weight calculation program 111 checks the average evaluation value of each KPI node adjacent to the considered KPI node, extracts a predetermined percentage (e.g., 20%) of these average evaluation values ​​(adjacent impact evaluation value), calculates a weight based on the total value of the adjacent impact evaluation values, and updates the weight in the KPI network DB 123 (S423).

[0081] According to this weight calculation process, when a new KPI is added, the weight of each KPI can be appropriately calculated.

[0082] In this embodiment, when there is a change in the KPI network frame (when a new KPI is added) or when a stakeholder's evaluation of a KPI node is input, the weight calculation program 111 automatically recalculates the weights through the weight calculation process shown in Figures 10 and 11.

[0083] Next, the weight calculation process will be specifically described.

[0084] FIG. 12 is a diagram illustrating a specific example of the weight calculation process according to an embodiment.

[0085] Here, a weight calculation process will be described in which a weight is calculated for the KPI node "Public Health" (in the following description, the KPI node is represented by "") in the KPI network frame shown in FIG. 12 as a considered KPI node.

[0086] First, we check the number of edges directly connected to "Public Health." Since "Public Health" has three edges connected to it - "Pollution", "Walking", and "Promotion of Healthy Eating / Products" - the number of edges is three.

[0087] Next, we check the maximum chain depth of "Sanitation". There are five chains that lead to "public health", Chains 1 to 5 below. Chain 1: “Population” → “Vehicle Travel” → “Pollution” → “Environmental Disease” → “GMO Restriction Policy” → “Research and Development of Alternative Products” → “Promotion of Healthy Diets / Products” → “Public Health” Chain 2: “Population” → “Car Travel” → “Pollution” → “Sanitation” Chain 3: "Green space" → "Walking" → "Public health" Chain 4: “GOV Funds for Industrial Health Products” → “Research and Development of Alternative Products” → “Promotion of Healthy Eating / Products” → “Public Health” Chain 5: “GOV funds for industrial health products” → “Promotion of healthy eating / products” → “Public health” Among chains 1 to 5, chain 1 has seven one-way edges and is the largest chain, so the maximum chain depth for "Public Health" is seven.

[0088] Next, check the average stakeholder evaluation score for "Public Health." Here, the average evaluation value for "public health" is 9.5, as shown in Figure 12. Note that the evaluation values ​​by each stakeholder may be stored, and the average value may be calculated from these evaluation values.

[0089] Next, check the total adjacent impact assessment value for "Public Health." The three KPIs adjacent to "Public Generation" are "Pollution," "Walking," and "Promoting Healthy Eating / Products." The average assessment value for "Pollution" is 10, and if the specified percentage is 20%, the adjacent impact assessment value will be 2. The average rating for "walking" is 6, and assuming a predetermined percentage of 20%, the adjacent impact rating is 1.2. The average rating for "promoting healthy eating / products" is 5, and the adjacent impact rating is 1, assuming a given percentage of 20%. Therefore, the total adjacent impact assessment value is 2 + 1.2 + 1 = 4.2.

[0090] Next, the weight W[Public Health] is calculated according to formula (1): W[Public Health] = 3 + 7 + 9.5 + 4.2 = 23.7.

[0091] Next, a display screen displayed on the terminal 150 by the CLD processing device 100 will be described.

[0092] 13 is a configuration diagram of a first CLD display screen according to an embodiment. A first CLD display screen 500 is a screen that is displayed on the terminal 150 in step S303 at the first time of the workshop.

[0093] The CLD display screen 500 includes a CLD display area 510 and a KPI evaluation input area 520. In the CLD display area 510, a CLD including all KPI nodes corresponding to KPIs included in a list of common KPIs provided by an administrator is displayed. In this embodiment, the KPI nodes in the CLD are displayed in a display mode according to the weight calculated based only on the connection relationship of the KPIs calculated in step S403. For example, the KPI nodes are highlighted such that the thickness of the circular line indicating the node increases as the weight increases. Note that a list of CLDs may be displayed instead of the CLD display area 510 at the user's instruction.

[0094] The KPI evaluation input area 520 is an area for inputting the stakeholder's evaluation of the KPI. The KPI evaluation input area 520 includes a plurality of individual evaluation input areas 521 for inputting evaluations of each KPI. In the individual evaluation input area 521, a slider 522 is disposed which allows the evaluation of the KPI corresponding to that area to be selected in the range of 0.0 to 10.0. When the stakeholder's evaluation of the KPI is input in the KPI evaluation input area 520, the weight calculation program 111 calculates an average evaluation value which is the average value of the stakeholder's evaluations of each KPI.

[0095] Next, a second CLD display screen 600 that is displayed after a KPI evaluation value is input to the CLD display screen 500 will be described.

[0096] FIG. 14 is a diagram showing the configuration of a second CLD display screen according to an embodiment.

[0097] The CLD display screen 600 includes a CLD display area 610 and a KPI addition area 620. In the CLD display area 610, a CLD similar to that in the CLD display area 510 is displayed. However, the KPI nodes in the CLD are displayed in a display mode according to the weight calculated in step S414. This CLD allows the user to grasp the weight of the KPI that reflects the evaluation value of the KPI by the stakeholder. The CLD display area 610 includes a tag display designation area 611. By operating the tag display designation area 611, the user can select and designate a tag (or a subtag) that is a category of the KPI to be included in the CLD to be displayed in the CLD display area 610. When a tag is designated in this tag display designation area 611, the KPI network / CLD generation program 112 displays in the CLD display area 610 a CLD of only the KPIs that belong to the designated tag. This allows the user to refer to the CLD by narrowing down to the required KPIs.

[0098] The KPI adding area 620 is an area for inputting information about a KPI to be added to the CLD. In the KPI adding area 620, the name of the KPI to be added, the source KPI, the destination KPI, the relationship with the KPI, the tag and subtag to which the KPI belongs, the evaluation value for the KPI, etc. can be input. When information about the KPI to be added is input in the KPI adding area 620, the weight for each KPI is calculated and updated by the weight calculation process shown in Fig. 11. When the weight of the KPI is updated, the updated CLD is displayed in the CLD display area 610.

[0099] The present invention is not limited to the above-described embodiment, and can be modified as appropriate without departing from the spirit of the present invention. [Explanation of symbols]

[0100] 10... computer system, 100... CLD processing device, 110... memory, 120... storage unit, 130... I / F device, 131... processor, 132... input / output device, 150... terminal

Claims

1. A causal loop diagram processing system for processing a causal loop diagram having a plurality of KPIs as elements, At least one processor; The processor, receiving an evaluation value regarding the importance of the KPI in the causal loop diagram from one or more users; Calculating the importance of each KPI in the causal loop diagram based on the received evaluation value. Causal loop diagram processing system.

2. In the causal loop diagram processing system according to claim 1, Equipped with memory resources, The storage resource stores a connection relationship between a plurality of KPIs constituting the causal loop diagram, The processor, Calculating a weight for each KPI in the causal loop diagram based on the received evaluation value and a connection relationship between the KPIs constituting the causal loop diagram. Causal loop diagram processing system.

3. 3. The causal loop diagram processing system according to claim 2, The processor, Calculate a weight for each KPI in the causal loop diagram based on the evaluation value, the connection relationship between the KPIs constituting the causal loop diagram, and the evaluation value for the KPI adjacent to the KPI. Causal loop diagram processing system.

4. 4. The causal loop diagram processing system according to claim 3, The connection relationship is as follows: Includes the number of edges directly connected to the KPI and the chain depth of the largest KPI connected to the KPI Causal loop diagram processing system.

5. In the causal loop diagram processing system according to claim 1, The processor, Accept the addition of KPIs to the causal loop diagram; Calculate the weight of each KPI in the modified causal loop diagram that includes the KPI Causal loop diagram processing system.

6. In the causal loop diagram processing system according to claim 1, The processor, The causal loop diagram is displayed so that the importance of the KPI can be recognized. Causal loop diagram processing system.

7. In the causal loop diagram processing system according to claim 1, The processor, receiving a tag indicating a category of a KPI to be displayed in the causal loop diagram; Display a causal loop diagram of only the KPIs in the category indicated by the received tag Causal loop diagram processing system.

8. A causal loop diagram processing method for a causal loop diagram processing system that processes a causal loop diagram having a plurality of KPIs as elements, comprising: The causal loop diagram processing system comprises: receiving an evaluation value regarding the importance of the KPI in the causal loop diagram from one or more users; Calculating the importance of each KPI in the causal loop diagram based on the received evaluation value. Causal loop diagram processing method.

9. 9. The method for processing a causal loop diagram according to claim 8, Calculating a weight for each KPI in the causal loop diagram based on the received evaluation value and a connection relationship between the KPIs constituting the causal loop diagram. Causal loop diagram processing method.

10. A causal loop diagram processing program for causing a system to execute the method according to claim 8 or 9.

Images