Information processing device and program

Abstract

To provide an information processing device and a program capable of assisting a KPI tree designing.SOLUTION: An information processing device includes: storing means for storing tree data in which a relation among a first node representing a management goal, a second node representing a task to achieve the goal, and a third node representing a scheme to address the task is set step by step in a tree structure; setting means for setting a status in accordance with a correspondent situation to the task of the second node in association with the second node; tabulating means for classifying the number of second nodes included in the respective pieces of tree data stored in the storing means by a unit of a subject of the task represented by the second node to perform tabulation; and outputting means for outputting information based on the tabulated number by the tabulating means.SELECTED DRAWING: Figure 14

Description

[Technical Field]

[0001] An embodiment of the present invention relates to an information processing device and a program. [Background technology]

[0002] Various business services (hereinafter referred to as "services") are provided at stores and other workplaces. In such workplaces, the processing procedures for each element involved in the implementation of the service are sometimes designed as a business flow using techniques such as the KPI (Key Performance Indicator) tree method or BPMN (Business Process Model and Notation).

[0003] The KPI tree method described above is used to analyze customer issues and consider services that will solve those issues. It can also be used to analyze issues in the industry in which a service is provided, and to plan and design new services.

[0004] However, when analyzing issues for an entire industry using a KPI tree, the issues will be diverse. Therefore, when developing a service with limited resources, it is necessary to narrow down the issues to focus on.

[0005] Typically, market research is conducted separately, and issues are analyzed from the results of the research before the KPI tree is designed and the service is planned. However, designing a KPI tree requires knowledge and know-how, and it is not easy to correlate the results of the issue analysis with the KPI tree. For this reason, there is a need for technology that can support the design of KPI trees. Summary of the Invention [Problem to be solved by the invention]

[0006] The problem to be solved by the present invention is to provide an information processing device and a program capable of supporting the design of a KPI tree. [Means for solving the problem]

[0007] The information processing device of the embodiment comprises a storage means for storing tree data in which the relationship between a first node indicating a management goal, a second node indicating a challenge to achieve the goal, and a third node indicating a measure to resolve the challenge is set in a step-by-step tree structure; a setting means for setting a status corresponding to the response status of the challenge of the second node in association with the second node; a counting means for classifying and counting the number of the second nodes included in each of the tree data stored in the storage means by the title of the challenge indicated by the second node; and an output means for outputting information based on the number counted by the counting means. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a business support system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a terminal device according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of a server device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the data configuration of the KPI tree DB according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a visualized KPI tree according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a data configuration of the business flow DB according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a visualized business flow according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a data configuration of the customer master according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a data configuration of the name identification master according to the embodiment. [Figure 10]FIG. 10 is a diagram illustrating an example of a data configuration of the provided service DB according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of the data configuration of the assignment number DB according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of the functional configuration of the terminal device and the server device according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a screen provided by the server device according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of a screen provided by the server device according to the embodiment. [Figure 15] FIG. 15 is a flowchart illustrating an example of processing executed by the server device according to the embodiment. [Figure 16] FIG. 16 is a flowchart illustrating an example of processing executed by the server device according to the embodiment. [Figure 17] FIG. 17 is a flowchart illustrating an example of processing executed by the server device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiments described below.

[0010] Fig. 1 is a diagram showing an example of the configuration of a business support system according to this embodiment. As shown in Fig. 1, the business support system 1 includes a terminal device 10 and a server device 20. The terminal device 10 and the server device 20 are communicably connected via a network N such as a LAN (Local Area network).

[0011] The terminal device 10 is a terminal device used by a user of the business support system 1. The terminal device 10 executes various processes in response to user operations. For example, the user operates the terminal device 10 to access the server device 20, thereby utilizing various functions provided by the server device 20. The terminal device 10 can be realized by a stationary terminal device such as a PC (Personal Computer), or a portable terminal device such as a notebook PC, tablet terminal, or smartphone.

[0012] The server device 20 is an example of an information processing device. The server device 20 provides various functions to the terminal device 10. For example, the server device 20 provides functions for creating and viewing a KPI tree, a business flow, and the like, which will be described later.

[0013] In this embodiment, an example in which the server device 20 is realized by a single information processing device will be described, but this is not limiting. For example, the server device 20 may be realized by multiple information processing devices using technology such as cloud computing.

[0014] Next, the configurations of the terminal device 10 and the server device 20 will be described.

[0015] Fig. 2 is a diagram illustrating an example of a hardware configuration of the terminal device 10. As illustrated in Fig. 2, the terminal device 10 includes a computer configuration including a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, and a RAM (Random Access Memory) 13.

[0016] The CPU 11 is an example of a processor, and performs overall control of each unit of the terminal device 10. The ROM 12 stores various programs. The RAM 13 is a workspace where programs and various data are developed.

[0017] The terminal device 10 also includes a display unit 14 , an operation unit 15 , a storage unit 16 , and a communication unit 17 .

[0018] The display unit 14 is composed of a display device such as an LCD (Liquid Crystal Display). The display unit 14 displays various information under the control of the CPU 11. The operation unit 15 has a keyboard, a pointing device, etc. The operation unit 15 outputs the operation content received from the user to the CPU 11. The operation unit 15 may be a touch panel provided on the display screen of the display unit 14.

[0019] The storage unit 16 is configured with a storage medium such as a hard disk drive (HDD) or flash memory, and maintains its stored contents even when the power is turned off. The storage unit 16 stores programs that can be executed by the CPU 11 and various setting information. For example, the storage unit 16 stores application programs such as a web browser that can utilize various functions provided by the server device 20.

[0020] The CPU 11 executes various processes by operating in accordance with programs stored in the ROM 12 or the storage unit 16 and expanded in the RAM 13 .

[0021] The communication unit 17 is a communication interface that can be connected to the network N. The communication unit 17 communicates with external devices such as the server device 20 via the network N.

[0022] Fig. 3 is a diagram showing an example of the hardware configuration of the server device 20. As shown in Fig. 3, the server device 20 includes a computer configuration including a CPU 21, a ROM 22, and a RAM 23.

[0023] The CPU 21 is an example of a processor, and performs overall control of each unit of the server device 20. The ROM 22 stores various programs. The RAM 23 is a workspace where programs and various data are developed.

[0024] The server device 20 also includes a display unit 24 , an operation unit 25 , a storage unit 26 , and a communication unit 27 .

[0025] The display unit 24 is composed of a display device such as an LCD. The display unit 24 displays various information under the control of the CPU 21. The operation unit 25 has a keyboard, a pointing device, etc. The operation unit 25 outputs the operation content received from the user to the CPU 11. The operation unit 25 may be a touch panel provided on the display screen of the display unit 24.

[0026] The storage unit 26 is configured with a storage medium such as a HDD or flash memory, and maintains its stored contents even when the power is turned off. The storage unit 26 stores programs that the CPU 21 can execute and various setting information. For example, the storage unit 26 stores web application programs that can provide various functions to the terminal device 10. The CPU 21 executes various processes by operating in accordance with the programs stored in the ROM 22 or the storage unit 26 and loaded into the RAM 23.

[0027] The storage unit 26 also stores a KPI tree DB 261, a business flow DB 262, a customer master 263, a name identification master 264, a provided service DB 265, a number of issues DB 266, and the like.

[0028] The KPI tree DB 261 is an example of a storage means. The KPI tree DB 261 is a table or database for storing and managing KPI trees. Here, a KPI tree is tree data with a tree structure in which the relationship between the management goals of an organization or company and the measures for achieving those goals is set in a hierarchical manner using nodes. Alternatively, a KPI tree can be described as tree data in which the relationship between the management issues of an organization or company and the measures for addressing those issues is set in a hierarchical manner using nodes. In this embodiment, the KPI tree is described as defining the relationship between goals and measures, but it may also be defined as defining the relationship between issues and measures.

[0029] Fig. 4 is a diagram showing an example of the data configuration of the KPI tree DB 261. As shown in Fig. 4, the KPI tree DB 261 stores customer IDs, KPI trees, etc., by associating the KPI trees with tree IDs that can identify them.

[0030] The Customer ID field is used to register information that can identify the customer to whom the KPI tree is applied. The KPI Tree field is used to register the actual data of the KPI tree (hereinafter also referred to as the data file) or the address of the storage location of the data file.

[0031] The KPI tree is created using a method such as KPI (Key Performance Indicator), etc. The KPI tree can be visualized as shown in FIG.

[0032] Fig. 5 is a diagram showing an example of a visualized KPI tree. Fig. 5 shows a visualized KPI tree applied to the customer with customer ID "12345678" (customer name "ABC Supermarket") shown in Fig. 4.

[0033] As shown in Figure 5, the KPI tree is made up of multiple nodes connected in a tree structure. Here, the final goal node A, which is the top-level root node, is a node for setting a goal to be achieved and is an example of a first node. The final goal node A corresponds to, for example, a KGI (Key Goal Indicator). For example, if the final goal is to increase store sales, a node name such as "Sales" indicating the target content is set in the final goal node A.

[0034] One or more intermediate goal nodes B are connected to the final goal node A. One or more intermediate goal nodes B can also be connected to the intermediate goal node B. A node name indicating an intermediate goal for achieving the goal (final goal or intermediate goal) set in the node immediately above is set in the intermediate goal node B. The intermediate goal node B corresponds to, for example, KPI (Key Performance Indicators).

[0035] 5 shows an example in which intermediate goal node Ba, whose target content is to increase the number of customers visiting the store, and intermediate goal node Bb, whose target content is to increase the average customer spending, are placed below final goal node A. Also shown is an example in which intermediate goal node Bc, whose target content is to increase the number of sales points, and intermediate goal node Bd, whose target content is to increase the unit price of an item, are placed below intermediate goal node Bb.

[0036] Furthermore, in the KPI tree, it is possible to place a factor node C representing a factor for achieving the intermediate goal set in the intermediate goal node B below the intermediate goal node B. The factor node C corresponds to, for example, a KSF (Key Success Factor) and is an example of a second node. Here, the factor for achieving the intermediate goal can also be rephrased as the challenge for achieving the intermediate goal. A node name representing the challenge is set in the factor node C. Hereinafter, the node name set in the factor node C is also referred to as the "title" of the challenge.

[0037] FIG. 5 shows an example in which factor nodes Ca to Cd, with the node names "Improved Quality," "Product Assortment," "Sales Floor," and "Advertising" set as challenges to increase the number of customers, are placed under intermediate goal node Ba. Also, an example is shown in which factor nodes Ce and Cf, with the node names "Sales Promotion" and "Impulse Buying" set as challenges to increase the number of sales, are placed under intermediate goal node Bc. Also, an example is shown in which factor node Cg, with the node name "Improved Customer Understanding" set as a challenge to increase the average customer spending, is placed under intermediate goal node Bb.

[0038] In addition, in the KPI tree, it is possible to place a solution node D below a factor node C, which represents a solution to achieve (solve) the problem set in the factor node C immediately above it.

[0039] Figure 5 shows an example in which solution nodes Da and Db, with node names set to represent solutions for "store information visualization" and "product assortment optimization," are placed below factor nodes Ca to Cc. Also, an example is shown in which solution nodes Dc to De, with node names set to represent solutions for "coupon issuance," "points management," and "POP creation," are placed below factor node Ce. Also, an example is shown in which solution node Df, with a node name set to represent a solution for "CRM (Customer Relationship Management)," is placed below factor node Cg.

[0040] Furthermore, in the KPI tree, it is possible to place a service node E, which represents a specific service for realizing the cause or solution set in the node immediately above, below the solution node D. Here, the service node E is an example of a third node, is located at the end of the tree structure, and is a specific measure for realizing the solution set in the node immediately above.

[0041] FIG. 5 shows an example in which a service node Ea, to which a node name indicating a measure for a "coupon issuing service" is set, is placed below a solution node Dc.

[0042] Each node making up the KPI tree is assigned a node ID for identifying it. Information about the corresponding node is stored in association with the node ID. For example, property information indicating the name (node ​​name) and category (KPI, etc.) of the corresponding node is stored in association with the node ID. Information according to the node category is stored in association with the property information.

[0043] For example, factor node C stores information (hereinafter also referred to as status) according to the response status of the issue of the node in association with it. Specifically, the status of factor node C can be "not yet addressed," "in response," "resolved," etc. Here, "not yet addressed" indicates a state in which the issue is recognized as an issue but has not yet been addressed. "in response" indicates a state in which a service or initiative is being implemented to resolve the issue. "resolved" indicates a state in which the issue was once an issue but is no longer an issue.

[0044] The status of the factor node C can be changed automatically or manually. When changing the status automatically, for example, the CPU 21 of the server device 20 (the status change unit 215 described later) sets the status of the factor node C to "not supported" on the condition that the factor node C has been created. The CPU 21 of the server device 20 (the status change unit 215 described later) may also set the status of the factor node C to "supported" on the condition that a service node E has been created below the factor node C.

[0045] Furthermore, when changing the status manually, for example, a user who plans or designs a service changes the status to a desired one by performing an operation to instruct the factor node C to change the status. In this case, the CPU 21 of the server device 20 (a status change unit 215, described later) changes the status of the factor node C in response to the user operation.

[0046] Furthermore, for example, a business flow related to the provision of a service, information indicating whether or not the service is provided, etc. are stored in association with the service node E. For example, information indicating the date on which the service corresponding to the service node E was provided (implemented) is stored in association with the service node E.

[0047] The KPI tree described above is saved in, for example, JSON (JavaScript Object Notation) format. Note that the format for saving the KPI tree is not limited to JSON, and it may be saved in other data formats such as XML (Extensible Markup Language).

[0048] Returning to Fig. 3, the business flow DB 262 is a table or database for storing and managing business flows. A business flow is a data file in which each element involved in the performance of a business and the execution content executed by that element are described as a series of procedures. Specifically, the business flow describes, for each element involved in the provision of a service, the execution content and procedure executed by that element.

[0049] Fig. 6 is a diagram showing an example of the data configuration of the business flow DB 262. As shown in Fig. 6, the business flow DB 262 stores a target service, a flow ID, a business flow name, and a data file in association with each other.

[0050] The target service field is where information specifying the service corresponding to the business process that is the subject of the business flow description is registered. Specifically, the node ID of the service node E specified as the target service, the tree ID of the KPI tree to which the service node E belongs, etc. are registered. Note that the method of specifying the target service is not limited to this.

[0051] The flow ID field is where a flow ID that can identify the business flow is registered. The business flow name field is where information indicating the name of the business flow is registered. For example, the business flow name is set to the name of the service implemented by the business flow (the node name of service node E). Furthermore, the data file field is where the data file of the business flow or the address indicating the storage location of the data file is registered.

[0052] Business flows are created using techniques such as flowcharts and BPMN (Business Process Modeling Notation). Business flows are created according to the service content, but if the service content is common or similar, it is possible to use the same business flow even if the KPI trees are different. Figure 6 shows an example in which a business flow with flow ID "F01" is used in service node Ea, which is included in the KPI tree with tree ID T01. Figure 6 also shows an example in which a business flow with flow ID "F02" is used in service node Ex, which is included in the KPI tree with tree ID T02.

[0053] A business flow is created using techniques such as a flowchart or BPMN (Business Process Modeling Notation). A business flow can be visualized, for example, as shown in Figure 7.

[0054] 7 is a diagram showing an example of a visualized business flow. Note that FIG. 7 shows an example of a business flow related to the service node Ea (coupon issuing service) in the KPI tree shown in FIG.

[0055] As shown in Figure 7, in the business flow, between the start event ST and the end event EN, a series of operations (or processing) related to the implementation (hereinafter also referred to as provision) of a coupon issuing service is described for each element that performs the operation. The business flow in Figure 7 shows an example in which the elements described are a "customer" who visits a store, a "surveillance camera" and a "payment system" installed in the store, and a "store clerk" who works in the store.

[0056] Here, "surveillance cameras" are an example of hardware resources, and are installed in multiple locations in a store, for example. A "payment system" is an example of software resources, and is realized through the collaboration of multiple PCs (Personal Computers) such as POSs and applications installed on those PCs. For example, additional services provided in conjunction with payment (e.g., point services) may also be included in the business flow. Hereinafter, the hardware resources, software resources, and additional services related to the implementation of the target service are collectively referred to as "elements."

[0057] The business flow in Figure 7 first describes the flow of a "customer" entering a store (Step Qa), selecting a product to purchase (Step Qb), and proceeding to the cash register (Step Qc). The flow of a "surveillance camera" installed in the store describes how the camera photographs the "customer" as he or she approaches the cash register (Step Qd) and transmits the photographed data to a payment system installed in the store (Step Qe). The flow of the "payment system" describes how the camera receives photographed data from the "surveillance camera" (Step Qf), and displays customer information, such as the "customer's" attributes, derived from the photographed data on a display device (Step Qg).

[0058] The flow also describes the "clerk" operating the cash register, in which the "payment system" checks the customer information displayed (step Qh) and performs the cash register operation for the items brought in by the "customer" (step Qi). It also describes that the "payment system" executes "payment processing" (step Qj) in conjunction with the "clerk" performing the cash register operation.

[0059] It also describes that the "customer" pays for the product according to the "payment processing" of the "payment system" (step Qk) and leaves the store (step Ql). It also describes that the "payment system" saves data showing the details of this transaction upon payment (step Qm).

[0060] For example, the payment system may issue coupons for discounts or reductions based on the amount of the product or payment purchased in the payment process, and may store the number of issued coupons on a daily basis. Furthermore, for example, the payment system may apply discounts or reductions to the product price based on the coupons presented during the payment process, and may store the number of used coupons on a daily basis.

[0061] When a point service is implemented, for example, the payment system identifies the membership number of the "customer" shown in the photographed data by comparing the photographed data received in step Qf with the facial images of each member registered in advance. The payment system then accumulatively stores points issued according to the purchase amount in association with the identified membership number.

[0062] The above-described business flow is saved in, for example, JSON format. Note that the format for saving the business flow is not limited to JSON, and it may be saved in other data formats such as XML.

[0063] Furthermore, in this embodiment, the KPI tree and the business flow may be created in advance, or may be created via the terminal device 10 or the like by the server device 20 providing creation support (design support). In the latter case, for example, the server device 20 provides the terminal device 10 with a screen (GUI (Graphical User Interface)) for supporting the viewing, creation, and editing of the KPI tree and the business flow.

[0064] Specifically, the server device 20 provides the terminal device 10 with a screen on which the KPI tree can be created and edited in a state in which various nodes and the relationships between the nodes are visualized. Then, upon completing the creation or editing of the KPI tree, the server device 20 stores the KPI tree in the KPI tree DB 261.

[0065] Furthermore, when any of the service nodes E included in the KPI tree is selected, the server device 20 provides a screen on which a business flow and a checklist can be created and edited for the service corresponding to the service node E. Then, when either the business flow or the checklist is created, the server device 20 associates it with the node ID and tree ID of the service node E and stores it in the corresponding DB.

[0066] Returning to FIG. 3, the customer master 263 is a table or database for storing and managing information about customers to which the KPI tree is applied.

[0067] Fig. 8 is a diagram showing an example of the data configuration of the customer master 263. As shown in Fig. 8, the customer master 263 stores customer names, customer attributes, etc. in association with customer IDs. Here, the customer ID is identification information for identifying each customer. The customer names correspond to the customer names registered in the KPI tree 261 of Fig. 4.

[0068] In the customer attribute field, information indicating customer attributes classified according to predetermined criteria is registered. The criteria for classifying attributes can be set arbitrarily, and for example, classification can be based on industry, etc. Figure 8 shows an example in which industry, which is a customer attribute, is classified into three levels: major classification, medium classification, and minor classification. However, classification of customer attributes is not limited to this. For example, classification can also be based on sales, number of employees, region, number of stores, etc.

[0069] Returning to Fig. 3, the name matching master 264 is a table or database for storing and managing the correspondence between the node names of the name matching source and the node names of the name matching destination. The name matching master 264 is used, for example, in a process of eliminating variations in the notation of node names and consolidating them into a common node name (hereinafter also referred to as "name matching"). The name matching master 264 has, for example, the data configuration shown in Fig. 9.

[0070] Fig. 9 is a diagram showing an example of the data configuration of the name identification master 264. As shown in Fig. 9, the name identification master 264 stores node names, node types, reference node names, data creation dates, etc. in association with each other.

[0071] The node name of the source node is registered as the node name. The reference node name of the destination node is registered as the reference node name. The node type is registered as the node type to be matched. The data creation date stores data indicating the date registered in the match master 264.

[0072] Here, the set of node name, node type, and reference node name functions as name matching information that defines the name matching rule. Specifically, the name matching information defines that the source node name should be matched (hereinafter also referred to as conversion) with the target reference node name under the condition of the specified node type.

[0073] Figure 9 shows an example in which a node with a node type of "Factor" and a node name of "Attractive Product Assortment" is converted to the node name "Product Assortment", and a node with a node type of "Factor" and a node name of "Rich Product Assortment" is converted to the node name "Product Assortment". This allows, for example, factor nodes C with the node names "Attractive Product Assortment" and "Rich Product Assortment" to be treated as factor node C with the node name "Product Assortment". In other words, it is possible to group together topics with common issues. Note that the source node name and the target reference node name are assumed to represent the same issue.

[0074] Furthermore, the name matching information is not limited to a one-way conversion from the source to the target, but may also specify a reverse conversion of node names from the target to the source. In this case, for example, a node with a node type of "Factor" and a node name of "product lineup" is reverse converted to the node names "attractive product lineup" and "rich product lineup." In other words, factor nodes C with the node names "product lineup," "attractive product lineup," and "rich product lineup" can be treated as factor nodes C with the same node name.

[0075] The content of the name identification information settings is not limited to the above example. The name identification information may be set manually, or the server device 20 may be configured to assist in the setting. In the latter case, for example, when a node other than the combination of node name and node type registered in the name identification master 264 is set in the KPI tree, the CPU 21 of the server device 20 may extract and display the node name of the node and prompt the user to set the name identification information.

[0076] Specifically, the CPU 21 of the server device 20 presents, as candidates for the name identification target, reference node names that correspond to the node type of the node set in the KPI tree, among the reference node names registered in the name identification master 264. Then, when one reference node name is selected from the candidates, the CPU 21 of the server device 20 registers, in the name identification master 264, name identification information based on the node name of the node set in the KPI tree and the selected reference node name. Furthermore, when a reference node name is not selected from the candidates, the CPU 21 of the server device 20 may store the node set in the KPI tree as name identification information of the name identification target in the name identification master 264 (or a separate table). This allows the CPU 21 of the server device 20 to present the nodes set in the KPI tree as candidates for the name identification target in subsequent registration assistance.

[0077] 3, the provided service DB 265 is a table or database for storing and managing service nodes E for which provision of a service has begun, among the service nodes E set in each KPI tree in the KPI tree DB 261. The provided service DB 265 has, for example, the data configuration shown in FIG.

[0078] Fig. 10 is a diagram showing an example of the data configuration of the provided service DB 265. As shown in Fig. 10, the provided service DB 265 stores a customer ID, a service ID, an introduction date, a data update date, and the like in association with each other.

[0079] The customer ID field is used to register identification information for the customer for whom the provision of the service has begun. For example, the customer ID field may register a customer ID or a customer name. Alternatively, the customer ID field may be used to register the tree ID of the KPI tree for the customer for whom the provision of the service has begun.

[0080] The service ID field stores information that can identify the service node E of the service that has started to be provided. For example, the service ID field stores the node ID of the service node E and the tree ID of the KPI tree that includes the service node E. The implementation date field stores data indicating the date on which the service started to be provided. The data update date field stores data indicating the date on which the service was registered in the provided service DB 265 and the date on which the update was performed.

[0081] It should be noted that data is registered in the provided service DB 265 in response to a user operation. For example, when an operation is performed on the display screen of the KPI tree to instruct that provision of a service has started for any one of the service nodes E, the CPU 21 of the server device 20 may be configured to register data in the provided service DB 265 based on the service node E that is the target of the operation.

[0082] Specifically, the CPU 21 of the server device 20 identifies the node ID of the service node E that is the target of the operation from the KPI tree, and identifies the customer ID corresponding to the KPI tree from the customer master 263. Then, the CPU 21 of the server device 20 associates the identified customer ID and node ID with the current date (data update date) and registers them in the provided service DB 265.

[0083] The server device 20 may be configured to automatically register data in the provided service DB 265. In this case, for example, the CPU 21 of the server device 20 may register the node ID, customer ID, etc. related to the service node E in the provided service DB 265 on the condition that the service node E is set in the KPI tree.

[0084] 3, the issue count DB 266 is a table or database for storing and managing the results of counting the number of issues for each status for factor node C set in each KPI tree in the KPI tree DB 261. The provided service DB 265 has, for example, the data configuration shown in FIG.

[0085] Fig. 11 is a diagram showing an example of the data configuration of the issue number DB 266. As shown in Fig. 11, the issue number DB 266 stores, in association with each other, issues, statuses, major industry classifications, medium industry classifications, minor industry classifications, the number of cases, and data update dates. Specifically, the issue number DB 266 stores, in association with each other, the number of cases, data update dates, etc. for each combination of issue, status, and customer attributes (major industry classifications, medium industry classifications, minor industry classifications, etc.).

[0086] The issues for each factor node C set in the KPI tree are registered in the Issues column. Specifically, the node name of factor node C, whose spelling variations have been resolved through name matching, in other words, the unified issue title, is registered in the Issues column. The Status column is registered with "Not yet addressed," "In progress," or "Resolved."

[0087] The major industry classification field, the medium industry classification field, and the small industry classification field are used to register the major, medium, and small classifications of customer attributes. If the customer attributes include other items (for example, size, etc.), the issue number DB 266 may have a field for registering the other items.

[0088] The number of occurrences column registers the number of factor nodes C that correspond to the conditions of issue, status, and customer attribute among the factor nodes C set in each KPI tree. In other words, the issue number DB 266 registers the number of occurrences of each factor node C that has common issue, status, and customer attribute among the factor nodes C set in the KPI tree of each customer.

[0089] The data update date stores data indicating the date when the item was registered in the issue number DB 266 or the date when the item was updated.

[0090] 3, the communication unit 27 is a communication interface connectable to the network N. The communication unit 27 communicates with external devices such as the terminal device 10 via the network N.

[0091] Next, the functional configuration of the terminal device 10 and the server device 20 will be described with reference to Fig. 12. Fig. 12 is a diagram showing an example of the functional configuration of the terminal device 10 and the server device 20.

[0092] As shown in FIG. 12, the terminal device 10 includes a display control unit 111 and an operation reception unit 112 as functional units.

[0093] Some or all of the functional units of the terminal device 10 may be software configured to be realized by cooperation between a processor (e.g., CPU 11) of the terminal device 10 and a program stored in a memory (e.g., ROM 12, storage unit 16). Also, some or all of the functional units of the terminal device 10 may be hardware configured to be realized by a dedicated circuit or the like mounted on the terminal device 10.

[0094] The display control unit 111 of the terminal device 10 controls the display unit 14 to display various screens on the display unit 14. For example, the display control unit 111 displays various operation screens on the display unit 14 based on information provided from the server device 20.

[0095] The operation accepting unit 112 of the terminal device 10 accepts a user operation via the operation unit 15. For example, when the operation accepting unit 112 accepts an operation on a screen displayed on the display unit 14, the operation accepting unit 112 notifies the server device 20 of the content of the operation.

[0096] On the other hand, the server device 20 includes a GUI providing unit 211, a design support unit 212, a display control unit 213, an operation receiving unit 214, a status changing unit 215, and a tallying unit 216 as functional units.

[0097] Some or all of the functional units of the server device 20 may be configured as software implemented by cooperation between a processor (e.g., CPU 21) of the server device 20 and a program stored in a memory (e.g., ROM 22, storage unit 26). Alternatively, some or all of the functional units of the server device 20 may be configured as hardware implemented by a dedicated circuit or the like mounted on the server device 20.

[0098] The GUI providing unit 211 is an example of an output means. The GUI providing unit 211 cooperates with other functional units to provide the terminal device 10 with information capable of displaying various operation screens (hereinafter also simply referred to as screens). Herein, the GUI providing unit 211 may provide data representing the screens, or may provide various content data related to the display of the screens. Hereinafter, the provision of information related to the display of the screens by the GUI providing unit 211 to the terminal device 10 will also be expressed as "providing" the screen, or "displaying," "presenting," or "outputting" the screen.

[0099] The design support unit 212 cooperates with the GUI provision unit 211 to provide a screen for supporting the creation (design) of a KPI tree and a business flow.

[0100] For example, the design support unit 212 provides a screen on which a KPI tree can be created by arranging various nodes, edges, and the like as drawing parts. On such a screen, a user can create or edit a tree-shaped KPI tree by arranging various nodes on the screen and arranging links that connect the nodes. When a KPI tree is created or edited, the design support unit 212 generates a data file representing the KPI tree and stores it in the KPI tree DB 261.

[0101] Furthermore, the design support unit 212 provides a screen on which a KPI tree to be viewed or edited can be selected based on the KPI tree DB 261. When a KPI tree is selected, the design support unit 212 reads the data file of that KPI tree from the KPI tree DB 261 and provides a screen on which the KPI tree is visualized.

[0102] The design support unit 212 also provides a screen on which a business flow can be created, with drawing parts and the like arranged in accordance with the BPMN notation rules. For example, when the design support unit 212 receives an operation to instruct the generation of a business flow (flow ID) for service node E included in the KPI tree, it provides a screen for creating the business flow. Then, when the design support unit 212 receives an operation to complete the creation or editing of the business flow, it generates a data file representing the business flow, associates it with the target service, and stores it in the business flow DB 262.

[0103] Furthermore, the design support unit 212 displays a business flow in response to a user operation. For example, when a service node E in the KPI tree is selected, the design support unit 212 visualizes the data file associated with the service node E, thereby displaying the business flow.

[0104] The display control unit 213 controls the display unit 24 to display various screens on the display unit 24. For example, the display control unit 213 causes the display unit 24 to display various screens provided by the GUI providing unit 211.

[0105] The operation receiving unit 214 receives user operations via the operation unit 25. For example, when the operation receiving unit 214 receives an operation on one of various operation support screens displayed on the display unit 24, the operation receiving unit 214 outputs the operation content to the CPU 21.

[0106] The status change unit 215 is an example of a setting unit. The status change unit 215 executes a process of changing the setting of the status associated with a factor node C included in the KPI tree, depending on the response status of the issue of the factor node C.

[0107] For example, when a factor node C is created in the KPI tree, the status change unit 215 sets the status of the factor node C to "not handled." Furthermore, when a service node E is created below the factor node C, the status change unit 215 changes the status of the factor node C from "not handled" to "being handled."

[0108] The conditions for changing to "in progress" are not limited to the above example. For example, in the design stage of the KPI tree, even if a service node E is created, the service corresponding to that service node E may not actually be provided (implemented). Therefore, the status change unit 215 may keep the status of factor node C as "not in progress" even if service node E is created.

[0109] Furthermore, for example, the status change unit 215 may perform processing to change the status of the corresponding factor node C to "in progress" based on a data entry registered in the provided service DB 265. Specifically, for each data entry registered in the provided service DB 265, the status change unit 215 identifies the tree ID of the KPI tree corresponding to the customer ID included in the data entry. After identifying the tree ID, the status change unit 215 identifies the node corresponding to the service ID included in the data entry, that is, the service node E, from the node IDs included in the tree data of the tree ID. Next, the status change unit 215 identifies the corresponding factor node C by tracing upstream from the identified service node E. Then, the status change unit 215 changes the status of the identified factor node C to "in progress".

[0110] When changing the status using the provided service DB 265, the status change unit 215 may change the status of the factor node C related to a new data entry to "in progress" every time the provided service DB 265 is updated. The status change unit 215 may also refer to the provided service DB 265 at a predetermined time interval, and change the status of the corresponding factor node C to "in progress" for each data entry registered during that time interval. For example, the status change unit 215 may be configured to refer to the provided service DB 265 at a timing such as once a day.

[0111] In addition, the status change unit 215 may work in cooperation with the GUI provision unit 211 to provide the user with a screen to assist in changing the status of a factor node C included in the KPI tree, and change the status of the factor node C depending on the content of the change operation.

[0112] For example, when a factor node C is selected from a KPI tree on a screen that visualizes the KPI tree, the GUI providing unit 211 displays a screen (hereinafter referred to as the property screen) on which the property information of the selected node can be confirmed and changed.

[0113] 13 is a diagram showing an example of a screen provided by the server device 20, and shows an example of a property screen. For example, as shown in Fig. 13, the property screen 30 is displayed superimposed on a screen that visualizes the KPI tree. Note that Fig. 13 shows the property screen 30 when factor node C with the node name "product lineup" included in the KPI tree shown in Fig. 5 is selected.

[0114] The property screen 30 has a name field 31, a category field 32, a status field 33, and a comment field 34. The name field 31 displays the node name of the selected factor node C. The category field 32 displays the category of the selected factor node C. The status field 33 displays the current status of the selected factor node C.

[0115] Here, the status column 33 has a pull-down menu 331. The pull-down menu 331 has each status of the factor node C ("Not Handled," "In Handled," and "Resolved") as options, and is an operator that can select one of the statuses. For example, when a user operating the KPI tree wants to change the status of a selected factor node C, the user operates the pull-down menu 331 to change the status to the desired one.

[0116] When the status change unit 215 receives an operation to change the status via the pull-down menu 331, it updates the status of the selected factor node C to the changed status. For example, when the user performs an operation to change the status to "resolved", the status change unit 215 changes the status of the selected factor node C to "resolved".

[0117] Any character string can be entered in the comment field 34. For example, if there is something to be passed on to another user regarding the selected factor node C, the information to be passed on can be entered in the comment field 34. When a character string is entered or edited in the comment field 34, the status change unit 215 stores information about the character string entered in the comment field 34 (hereinafter, comment information) as part of the property information of the selected factor node C.

[0118] Of the items included in the property screen 30, the status field 33 and the comment field 34 are configured to be editable, but this is not limiting, and the name field 31 and the category field 32 may also be configured to be editable.

[0119] In addition, in Figure 13, the property screen 30 and the aggregate value setting screen 40 described later are configured to be switchable by switching between the property tab Ta and the aggregate value tab Tb, but the display form is not limited to this, and it is also possible to display only the property screen 30.

[0120] 12, the tallying unit 216 is an example of a tallying means and a name matching means. The tallying unit 216 classifies and tally the number of factor nodes C included in the KPI tree stored in the KPI tree DB 261 (the number of occurrences) by unit such as the title of the task indicated by the factor node C or the status of the factor node C.

[0121] For example, the aggregation processing unit 216 makes it possible to handle factor nodes C with common issues as a group by merging the node names of factor nodes C set in the KPI tree of each customer based on the name merging master 264. Hereinafter, the factor nodes C grouped together by name merging are also referred to as a group of issue-common factor nodes.

[0122] Furthermore, the aggregation processing unit 216 aggregates the number of factor nodes C belonging to each task common factor node group in a predetermined unit. For example, the aggregation processing unit 216 aggregates the number of factor nodes C for each status condition (type). Furthermore, the aggregation processing unit 216 refers to the customer master 263 to identify customer attributes of the KPI tree that includes factor nodes C, and aggregates the number of factor nodes C for each condition of the identified customer attributes. As an example, the aggregation processing unit 216 aggregates the number of factor nodes C for each combination of status, major industry classification, medium industry classification, and minor industry classification.

[0123] Then, the aggregation processing unit 216 registers the number of factor nodes C aggregated for each task common factor node group in the task number DB 266, associating it with the tasks and aggregation conditions (status, customer attributes) common to the task common factor node group.

[0124] Generally, issues of factor nodes C set in the same KPI tree do not overlap, so the number of factor nodes C tallied by the aggregation processing unit 216 corresponds to the number of KPI trees in which the issue of that factor node C is set. Furthermore, when one KPI tree is designed for each customer, the number of factor nodes C tallied by the aggregation processing unit 216 corresponds to the number of customers with a common issue. Therefore, the number tallied by the aggregation processing unit 216 can also be referred to as the "number of trees" or "number of customers."

[0125] The timing for executing the tallying process is not particularly limited and can be set arbitrarily. For example, the tallying processor 216 may tally the number of events related to factor node C each time the status of the factor node C is changed. The tallying processor 216 may also perform tallying for each KPI tree stored in the KPI tree DB 261 by batch processing, such as once a day. For example, the tallying processor 216 may also perform tallying for each KPI tree stored in the KPI tree DB 261 in response to an instruction from a user.

[0126] Furthermore, the tallying unit 216 provides a screen showing the results of the tallying process by working in cooperation with the GUI providing unit 211 and the like. For example, when an instruction to display the results of the tallying process is given on a screen that visualizes a KPI tree, the GUI providing unit 211 visualizes and displays the tallying results related to the issues of factor node C, in association with factor node C included in the visualized KPI tree. An example of displaying the tallying results will be described below.

[0127] 14 is a diagram showing an example of a screen provided by the server device 20, illustrating an example of an aggregation result screen. For example, as shown in FIG. 14, the GUI providing unit 211 displays an aggregation value setting screen 40 for setting aggregation conditions for the aggregation results to be displayed, superimposed on a screen that visualizes the KPI tree.

[0128] Here, it is preferable that the KPI tree to be displayed is, for example, a KPI tree for a customer in the planning and design stage, when the service is still to be formulated. Note that Figure 14 shows an example of a KPI tree for a customer in the planning and design stage, different from the customer name "ABC Supermarket" shown in Figure 13.

[0129] When the GUI providing unit 211 receives an operation to select a factor node C or an operation to instruct display of the aggregation results, it displays the aggregation value setting screen 40 shown in Fig. 14 superimposed on the KPI tree. Specifically, when it receives an operation to select the aggregation value tab Tb out of the property tab Ta and the aggregation value tab Tb, the GUI providing unit 211 displays the aggregation value setting screen 40 for displaying the aggregation results.

[0130] The tally value setting screen 40 has a hide / show operator 41. The hide / show operator 41 is an operator for switching between displaying and hiding the tally results. When display is selected with the hide / show operator 41, the GUI providing unit 211 enables the display of the tally results and displays the tally results. Furthermore, when hide is selected with the hide / show operator 41, the GUI providing unit 211 disables the display of the tally results and hides the tally results.

[0131] The tally value setting screen 40 also has controls that allow the user to specify tally conditions for the tally results. Specifically, the tally value setting screen 40 has pull-down menus 421 to 424 for narrowing down the status and customer attributes.

[0132] Here, the pull-down menu 421 is an operator that has the status of the factor node C as options and can select one of the statuses. Note that the options selectable in the pull-down menu 421 include "Not Handled," "In Handled," and "Resolved," as well as "No Designation," which means that no status is specified.

[0133] Pull-down menu 422 has major industry classifications as options and is an operator that allows the selection of any one of the major industry classifications. Pull-down menu 423 has medium industry classifications as options and is an operator that allows the selection of any one of the medium industry classifications. Pull-down menu 424 has minor industry classifications as options and is an operator that allows the selection of any one of the minor industry classifications. Note that the options that can be selected from pull-down menus 422 to 424 include "No specification," which means that no industry classification is specified.

[0134] When the tallying conditions are specified using the pull-down menus 421 to 424, the GUI providing unit 211 reads out the tallying results (number of cases) of each task corresponding to the specified tallying conditions from the task number DB 266. For example, as shown in Fig. 14, when the status "unspecified", the major industry category "retail", the medium industry category "mass retailer", and the minor industry category "supermarket" are specified, the tallying processing unit 216 adds up the number of cases of each status that meets the specified industry condition among the numbers of each task, and reads out the sum as the tallying result.

[0135] The tallying unit 216 then displays the tallying results for each task read from the task number DB 266 in association with the factor node C included in the visualized KPI tree. For example, in the case of the KPI tree shown in Fig. 14, seven tasks (titles) - "Quality Display," "Product Assortment," "Sales Floor," "Advertising," "Sales Promotion," "Impulse Buying," and "Improved Customer Understanding" - are set in the factor node C. In this case, the tallying value setting screen 40 reads the tallying results for each of these tasks from the task number DB 266 and displays them in association with the corresponding factor node C.

[0136] Specifically, in Fig. 14, the number displayed above factor node C corresponds to the number of items, which is the count result. For example, factor node C with the title "Product Assortment" is associated with "987" items.

[0137] This allows users viewing the KPI tree to easily check the number of trees and customers that have issues similar to factor node C, as well as the status of each customer's response to the issues, by looking at the number of items displayed in association with factor node C in the KPI tree.

[0138] Furthermore, for example, when proposing a service by referring to KPI trees created for other clients or past KPI trees, the number of items displayed in association with factor node C in the KPI tree can be used as information for service design, such as the priority of the problem to be solved (factor node C) and the application status of existing services. Therefore, the server device 20 can effectively utilize existing KPI trees to support the design of a new KPI tree.

[0139] The tallying unit 216 may start tallying when tallying conditions are specified on the tally value setting screen 40. Specifically, the tallying unit 216 performs tallying processing of the number of cases according to the specified tallying conditions. Furthermore, the tallying unit 216 may narrow down the tallying processing to issues of factor nodes C included in the visualized KPI tree, among the factor nodes C included in the KPI tree that meet the tallying conditions.

[0140] Furthermore, the display format of the tally results is not limited to the example in Fig. 14 and may be displayed in other formats. For example, the GUI providing unit 211 may display the number and percentage of issues in the statuses of "Not Handled," "In Handled," and "Resolved" for the issues of factor node C in a manner that allows comparison. Furthermore, when one of the statuses "Not Handled," "In Handled," and "Resolved" is selected in the pull-down menu 421, the tallying unit 216 may display the number of issues in the selected status and the total value obtained by adding up the numbers of issues in each status in a manner that allows comparison.

[0141] An example of the operation of the above-mentioned server device 20 will be described below with reference to Fig. 15 to Fig. 17. Fig. 15 to Fig. 17 are flowcharts showing an example of the processing executed by the server device 20.

[0142] 15, an example of a process in which the status change unit 215 changes the status of the factor node C based on the provided service DB 265 will be described. Note that in this process, an example of a process in which the status is changed daily will be described.

[0143] First, the status change unit 215 reads one data entry whose implementation date is today (or the day before) from the data entries stored in the provided service DB 265 (step S11).

[0144] Next, based on the customer ID included in the read data entry, the status change unit 215 acquires the KPI tree stored in association with the customer ID from the KPI tree DB 261 (step S12).

[0145] The status change unit 215 identifies a factor node C related to the service ID included in the data entry in the acquired KPI tree (step S13). The status change unit 215 changes the status of the identified factor node C to "in progress" (step S14).

[0146] Next, the status change unit 215 determines whether or not there is an unprocessed data entry among the data entries stored in the provided service DB 265 whose installation date is today (or the previous day) (step S15).

[0147] If it is determined that an unprocessed data entry exists (step S15; Yes), the status change unit 215 returns the process to step S11, and reads out the unprocessed data entry from the provided service DB 265.

[0148] Moreover, if it is determined that there is no unprocessed data entry (step S15; No), the status change unit 215 ends this process.

[0149] By the process of FIG. 15, the status of the factor node C related to the service node E to which the service was provided is automatically changed to "in progress."

[0150] Following the processing of step S15, the tallying unit 216 may update the assignment number DB 266 by adding 1 to the number of assignments of factor node C whose status has been changed and whose status is "in progress."

[0151] Next, an example of the tallying process performed by the tallying processor 216 will be described with reference to FIG.

[0152] First, the aggregation processing unit 216 merges the node names of the factor nodes C set in each KPI tree in the KPI tree DB 261, thereby making it possible to handle factor nodes C with a common issue as a group (step S21).

[0153] Next, the tallying unit 216 tally up, for each task common factor node group, the number of factor nodes C belonging to the task common factor node group in a predetermined classification unit such as status or customer attribute (step S22).

[0154] Next, the aggregation processing unit 216 associates the number of factor nodes C aggregated for each task common factor node group with the tasks and aggregation conditions (status, customer attributes), etc. common to the task common factor node group, and registers them in the task number DB 266 (step S23).

[0155] This allows you to quantitatively grasp the status of service provision for all customers (or the entire KPI tree) by, for example, aggregating the number of issues for each status for factor node C set in each customer's KPI tree.

[0156] Next, an example of processing for superimposing and displaying the aggregation results of the aggregation processing unit 216 on a visualized KPI tree will be described with reference to Fig. 17. Note that in this processing, the aggregation results of the aggregation processing unit 216 will be described as having been registered in advance in the issue number DB 266.

[0157] First, the GUI providing unit 211 cooperates with the design support unit 212 to display a screen that visualizes the KPI tree (step S31). When the GUI providing unit 211 receives an operation to instruct the display of the aggregation results of the aggregation processing unit 216 (step S32), the GUI providing unit 211 displays an aggregation value setting screen 40 (see FIG. 14) that specifies aggregation conditions for the aggregation results (step S33).

[0158] When the specification of the aggregation conditions is accepted via the aggregation value setting screen 40 (step S34), the GUI providing unit 211 reads out the number of items that meet the specified aggregation conditions and correspond to the issues of factor node C of the visualized KPI tree from the issue number DB 266 (step S35).

[0159] Then, the GUI providing unit 211 displays the total number of issues for the factor node C in association with the factor node C of the visualized KPI tree (step S36), and ends this process.

[0160] This allows users viewing the KPI tree to easily see the number of customers who have issues similar to those of factor node C and the status of each customer's response to the issues by looking at the number of items displayed in association with factor node C in the KPI tree.

[0161] As described above, the server device 20 sets a status according to the response status of the issue of a factor node C included in a KPI tree in association with the factor node C. The server device 20 also classifies and tallies the number of factor nodes C included in each KPI tree stored in the KPI tree DB 261 by the title of the issue indicated by the factor node C. The server device 20 then outputs information based on the tallied number.

[0162] This allows a user creating a KPI tree to easily check the number of trees and customers with similar issues, and the status of each customer's response to the issues, based on the information output by the server device 20. Therefore, the server device 20 can provide support for designing a KPI tree.

[0163] Furthermore, the server device 20 further classifies and tallies the number of factor nodes C included in each KPI tree in units of the status set for the factor nodes C.

[0164] This allows the user to easily check the priority of the problem to be solved (factor node C), the application status of existing services, etc., based on the information output by the server device 20. Therefore, the server device 20 can provide support for designing a KPI tree.

[0165] Furthermore, the server device 20 classifies and counts the number of factor nodes C included in each KPI tree by the unit of customer attribute related to the KPI tree.

[0166] This allows the user creating a KPI tree to check the number of trees and customers with similar issues, and the status of each customer's response to issues, based on the aggregate results of KPI trees created for other customers with similar customer attributes as the customer to whom the KPI tree being created will be applied, thereby enabling efficient creation of a KPI tree.As a result, the server device 20 can provide support for designing a KPI tree.

[0167] Furthermore, the server device 20 visualizes and outputs the KPI tree, and visualizes and outputs the aggregation results related to the issue of the factor node C in association with the factor node C included in the KPI tree.

[0168] This allows a user creating a KPI tree to easily check the priority of the problem to be solved (factor node C), the application status of existing services, etc., by looking at the number of items displayed in association with factor node C of the KPI tree to be created, for example. Therefore, the server device 20 can provide support for designing a new KPI tree.

[0169] The above-described embodiment can be modified as needed by changing some of the configurations or functions of the above-described devices. Therefore, the following describes modifications of the above-described embodiment as other embodiments. The following mainly describes differences from the above-described embodiment, and omits detailed descriptions of commonalities with the content already described. The modifications described below may be implemented individually or in appropriate combination.

[0170] (Variation 1) In the above-described embodiment, an example is shown in which the terminal device 10 and the server device 20 work together to display various screens provided by the server device 20 on the terminal device 10, but this is not limited to this, and the terminal device 10 may display the screens on its own.

[0171] In this case, the terminal device 10 can display various screens by including functional units such as the above-mentioned GUI providing unit 211 and design support unit 212. It is assumed that the terminal device 10 is in a state where it can read and write various DBs held by the server device.

[0172] In this case, part or all of the DB held by the server device may be held by the terminal device 10, or may be held by another device (or cloud) accessible by the terminal device 10.

[0173] (Variation 2) In the above-described embodiment, information based on the aggregation results is displayed in association with factor node C of the KPI tree to be displayed, but this is not limited to this. For example, information based on the aggregation results may be displayed in a KPI tree other than the KPI tree to be displayed.

[0174] For example, the GUI providing unit 211 may extract a common tree structure or a representative KPI tree from the KPI trees of each customer that meets the customer attribute (e.g., industry) conditions specified in the aggregation conditions, and display information based on the aggregation results in association with factor node C included in the extracted tree structure or KPI tree.

[0175] This allows the user to check the tree structure common to KPI trees for the industry specified in the aggregation conditions, as well as a representative KPI tree, and also to easily check the number of customers with similar issues and the status of each customer's response to the issues using the KPI tree. Therefore, the server device 20 can effectively utilize existing KPI trees to support the design of new KPI trees.

[0176] The programs executed by each device in the above-described embodiments are provided in a state where they are pre-installed in a ROM, a storage unit, etc. The programs executed by each device in the above-described embodiments may be provided by being recorded in an installable or executable format on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD).

[0177] Furthermore, the programs executed by each device in the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by each device in the above-described embodiments may be provided or distributed via a network such as the Internet.

[0178] Although the embodiments of the present invention have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments and their modifications can be embodied in various other forms, and various omissions, substitutions, changes, and combinations can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0179] 1. Business support system 10 Terminal Equipment 20 Server device 111 Display control unit 112 Operation reception section 211 GUI provision department 212 Design Support Department 213 Display control unit 214 Operation reception section 215 Status Change Section 216 Aggregation Processing Unit 261 KPI Tree DB 262 Business Flow DB 263 Customer Master 264 Name Matching Master 265 Service DB 266 Issue Number DB [Prior art documents] [Patent documents]

[0180] [Patent Document 1] Patent Publication No. 2021-117846

Claims

1. a storage means for storing tree data in which the relationship between a first node indicating a business goal, a second node indicating a problem to be solved in order to achieve the goal, and a third node indicating a measure to solve the problem is set in a tree structure in a stepwise manner; a counting means for classifying and counting the number of second nodes included in each tree data stored in the storage means by the title of the assignment indicated by the second node; an output means for outputting information based on the number of cases counted by the counting means; An information processing device comprising:

2. the storage means stores a status according to a response status of the second node to the issue in association with the second node; the counting means further classifies and counts the number of the second nodes included in each of the tree data stored in the storage means by a status unit set for the second node; The information processing device according to claim 1 .

3. the storage means stores the tree data in association with customer attributes of customers to which the tree data is applied; the counting means further classifies and counts the number of the second nodes included in each piece of tree data stored in the storage means by a customer attribute unit related to the tree data, 3. The information processing device according to claim 1 or 2.

4. the output means visualizes and outputs the tree data, and visualizes and outputs information based on the number of cases totaled by the totaling means for the issue indicated by the second node, in association with the second node included in the tree data. The information processing device according to claim 1 .

5. The method further comprises a name matching means for grouping common subject titles together by matching the subject titles indicated by the second nodes included in each of the tree data, the counting means counts the number of items based on the titles of the second nodes grouped by the name identification means; The information processing device according to claim 1 .

6. a setting unit that sets a status corresponding to a response status of the second node to the problem in association with the second node; the setting means, when the second node is created in the tree data, associates and sets a status indicating that the second node is not supported with the second node, and when the third node is created below the second node, associates and sets a status indicating that the second node is supported with the third node; The information processing device according to claim 1 .

7. The computer of the information processing device, a storage means for storing tree data in which the relationship between a first node indicating a business goal, a second node indicating a problem to be solved in order to achieve the goal, and a third node indicating a measure to solve the problem is set in a tree structure in a stepwise manner; a counting means for classifying and counting the number of second nodes included in each tree data stored in the storage means by the title of the assignment indicated by the second node; an output means for outputting information based on the number of cases counted by the counting means; A program to make it function as such.

Images