Information processing apparatus and program

Abstract

To provide an information processor and a program for supporting the design of a service.SOLUTION: The information processing apparatus includes a first storage unit that stores, in association with customer information on a customer, at least one of tree information in which a relation between a business objective of the customer and a service executed to achieve the business objective is represented by a tree structure and relevant information relevant to execution of the service, an extraction unit that extracts, from an information group including the customer information and at least one of the tree information and the relevant information, character strings representing a feature of the information group, and a second storage unit that stores each of the character strings extracted by the extraction unit as a search index in association with specific information capable of specifying the information group.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 above-mentioned methods are used to analyze customer issues and consider services that will solve those issues. By using the above-mentioned methods, it is also possible to analyze issues in the industry in which the service is provided and to design new services.

[0004] However, analyzing customer issues and creating business processes using the above-mentioned methods requires knowledge and know-how. Furthermore, in recent years, a variety of services have been offered in a variety of industries, and the systems involved in implementing these services have become increasingly complex. Given this situation, it is effective to refer to the design information of existing services, for example, in order to efficiently design services for new customers.

[0005] However, with conventional technology, it is not easy to find design information that meets desired conditions from among the design information of existing services, and there is room for improvement in terms of convenience. 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 that can support the design of a service. [Means for solving the problem]

[0007] An information processing device according to an embodiment includes a first storage means for storing, in association with customer information relating to a customer, at least one of tree information in which the relationship between the customer's business goals and the services implemented to achieve the business goals is expressed in a tree structure and related information related to the implementation of the services; an extraction means for extracting character strings representing characteristics of an information group including the customer information and at least one of the tree information and the related information; and a second storage means for using each of the character strings extracted by the extraction means as a search index and storing the information group in association with specific information that can identify the information group. [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 a cost information DB according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of visualized cost information according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a data configuration of the customer master according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a data configuration of the name identification master according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of a data configuration of the service design information DB according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a data configuration of the disclosure range setting DB according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of the functional configuration of the terminal device and the server device according to the embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of a screen provided by the server device according to the embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of a screen provided by the server device according to the embodiment. [Figure 17] FIG. 17 is a flowchart illustrating an example of a disclosure range setting process executed by the server device according to the embodiment. [Figure 18] FIG. 18 is a flowchart illustrating an example of a search support process 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. In this embodiment, the user of the business support system 1 refers to a person in charge of designing and creating service design information such as a KPI tree, business flow, and cost information, a person (e.g., a salesperson) who proposes services to customers based on the KPI tree, and the like.

[0012] 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, a tablet terminal, or a smartphone.

[0013] 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 and a business flow, which will be described later.

[0014] 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.

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

[0016] Fig. 2 is a diagram illustrating an example of a hardware configuration of the terminal device 10 according to the embodiment. 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.

[0017] 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.

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

[0019] 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.

[0020] 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.

[0021] 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 .

[0022] 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.

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

[0024] 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.

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

[0026] 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.

[0027] 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.

[0028] The storage unit 26 also stores a KPI tree DB 261, a business flow DB 262, a cost information DB 263, a customer master 264, a name identification master 265, a service design information DB 266, a disclosure range setting DB 267, etc. Here, the KPI tree DB 261, the business flow DB 262, the cost information DB 263, and the customer master 264 are examples of a first storage means. The service design information DB 266 is an example of a second storage means.

[0029] 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.

[0030] 4 is a diagram showing an example of the data configuration of the KPI tree DB 261 according to the embodiment. As shown in Fig. 4, the KPI tree DB 261 associates KPI trees with identifiable tree IDs and stores customer IDs, KPI tree data files, and the like.

[0031] The customer ID field stores information that can identify the customer to whom the KPI tree is applied. The data file field stores the actual data of the KPI tree or the address of the storage location of the data file. The KPI tree is saved in JSON (JavaScript Object Notation) format, for example. Note that the KPI tree may be saved in other data formats, such as XML (Extensible Markup Language), and is not limited to JSON.

[0032] 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.

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

[0034] 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 goals to be achieved. 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 final goal node A.

[0035] 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).

[0036] 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.

[0037] Furthermore, in the KPI tree, it is possible to place a factor node C representing the factors 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). Here, the factors for achieving the intermediate goal can also be rephrased as the challenges 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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 located at the end of the tree structure and is a specific measure for realizing the solution set in the node immediately above.

[0042] 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.

[0043] 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.

[0044] For example, service node E stores associated information related to the implementation of the service, such as a business flow that specifies the processing procedures for each element involved in the implementation of the service, and cost information that specifies the cost of each resource required to implement the service.

[0045] 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.

[0046] 6 is a diagram showing an example of the data configuration of the business flow DB 262 according to the embodiment. 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] A business flow is created using techniques such as a flowchart or BPMN (Business Process Modeling Notation) and saved in JSON format. The business flow may be saved in any other data format, such as XML, and is not limited to JSON. The business flow can also be visualized as shown in Figure 7.

[0051] Fig. 7 is a diagram showing an example of a visualized business flow according to the embodiment. Fig. 7 shows an example of a business flow related to the service node Ea (coupon issuing service) of the KPI tree shown in Fig. 5. Fig. 7 shows a form in which a screen visualizing the business flow (hereinafter also referred to as a business flow screen) can be displayed by switching between tabs Ta and Tb. Here, the business flow is displayed when tab Ta is selected.

[0052] As shown in Figure 7, on the business flow screen, between the start event ST indicated by a circle and the end event EN, the content of a series of processes or operations (also referred to as tasks) related to the implementation (hereinafter also referred to as provision) of a coupon ticket issuing service is described for each element that performs the operation. The business flow in Figure 7 shows an example in which a store Pa and a coupon issuing service Pb are described as elements (hereinafter also referred to as pools) related to the implementation of a coupon ticket issuing service. However, the classification of elements described as pools is not limited to this.

[0053] Store Pa refers to the store that serves as the implementation environment for the coupon issuing service, and includes as elements customers who visit the store (hereinafter also referred to as store customers) and store staff (POS), which are resources possessed by the store. Here, store staff (POS) refers to store staff, which are human resources, and POS terminals, which are hardware resources. Coupon issuing service Pb refers to the service to be implemented and the implementation environment for that service.

[0054] The workflow screen in Figure 7 shows the flow for a "store customer" who visits store Pa, selecting the product to purchase (step Qa) and paying for the selected product (step Qb). Next, the flow for a store clerk (POS) is shown, where the payment for the product is processed (step Qc).

[0055] Next, the flow of the coupon issuing service Pb describes receiving data generated by the checkout process (data indicating the details of the transaction, checkout process, etc.) from the POS of store Pa (step Qd). Next, it is described that based on the contents of the received data, it is determined whether or not there is a coupon to be issued (step Qe). For example, the coupon issuing service Pb determines whether or not to issue a coupon based on pre-set conditions for coupon issuance. As an example, the coupon issuing service Pb stores coupon information in which discount or discount amounts are set in association with conditions such as product codes and the price range of the price paid in the checkout process, and determines that the corresponding coupon information (coupon) exists if the contents of the data satisfy the conditions.

[0056] If the coupon issuing service Pb determines that a corresponding coupon exists (step Qe; Yes), it extracts coupon information that matches the conditions of the data content (step Qf) and proceeds to step Qh. If the coupon issuing service Pb determines that a corresponding coupon does not exist (step Qe; No), it generates no-coupon information indicating that no coupon to be issued exists (step Qg) and proceeds to step Qh. Then, in step Qh, the coupon issuing service Pb sends the coupon information extracted in step Qf or the no-coupon information generated in step Qg to the POS terminal of store Pa (step Qh).

[0057] Next, at store Pa, when the store clerk (POS) receives the information transmitted from coupon issuing service Pb, the store clerk (POS) issues a coupon based on the information (step Qi), and the series of operations ends. For example, when the store clerk (POS) receives coupon information, it issues a coupon indicating the discount or discount amount set in the coupon information. Also, for example, when the store clerk (POS) receives information that does not include a coupon, it ends the process without issuing a coupon.

[0058] Returning to FIG. 3, the cost information DB 263 is a table or database for storing and managing cost information indicating the estimated cost required to implement a service.

[0059] 8 is a diagram illustrating an example of a data configuration of the cost information DB 263 according to the embodiment. As illustrated in Fig. 8, the cost information DB 263 stores target services, cost information, etc. in association with cost IDs for identifying each piece of cost information.

[0060] Information specifying the service for which costs are to be calculated is registered in the target service. Specifically, the node ID of the service node E specified in the target service, the tree ID of the KPI tree to which the service node E belongs, etc. are registered. Figure 8 shows an example of cost information with a cost ID of "C01" set for service node Ea included in the KPI tree with a tree ID of T01.

[0061] Cost information includes items such as ID, target, classification, quantity, implementation cost, and operating cost. The ID is an identifier that identifies each target. The target field contains the name of the resource for which costs are to be calculated (hereinafter also referred to as the cost calculation target). Specifically, the target field contains the names of each resource related to the implementation of the target service. Figure 8 shows an example in which "POS," "store system," "coupon issuance service," and "initial setup work" are registered in the target field as resources related to the implementation of the coupon issuance service described in the business flow of Figure 7.

[0062] Here, "POS" corresponds to the POS terminal used in store Pa shown in FIG. 7. "Store system" corresponds to the store system of store Pa shown in FIG. 7. The store system includes network devices that connect each POS terminal to a network, and server devices such as a store server. "Coupon issuing service" corresponds to applications and the like related to the implementation of the coupon issuing service implemented by coupon issuing service Pb. "Initial setting work" corresponds to work related to the initial setting of "POS," "store system," and "coupon issuing service" to implement the coupon issuing service.

[0063] The classification registers information indicating the type of resource for which costs are to be calculated. For example, "POS" and "store system" are realized by hardware (HW) resources, so "HW" is registered as their classification. Also, "coupon issuing service" is realized by software (SW) resources, so "SW" is registered as its classification. Also, "initial setup work" is realized by human resources, so "personnel" is registered as its classification.

[0064] Information indicating the quantity of the item for which cost calculation is performed is registered in the quantity field. Figure 8 shows an example in which the quantity of "POS" is "3," the quantity of "Store System" is "1," the quantity of "Coupon Issuance Service" is "1," and the quantity of "Initial Setup Work" is "1."

[0065] The installation cost field contains information indicating the estimated cost required to install the item being calculated. Figure 8 shows an example where 200,000 yen has been registered as the installation cost for three POS units. It also shows an example where 50,000 yen has been registered as the installation cost for the store system. It also shows an example where 100,000 yen has been registered as the installation cost for the initial setup work.

[0066] The operating cost field contains information indicating the estimated cost required for the operation of the target service. Here, "operation" refers to the operating cost for a specified period, such as the operating cost per month. Figure 8 shows an example in which "150,000 yen" has been registered as the monthly operating cost for the "coupon issuing service."

[0067] It should be noted that the cost information DB 263 is not limited to the data configuration shown in Fig. 8. For example, the cost information DB 263 may store, in association with the cost information, the user ID of the user who input (or updated) the cost information, and date and time information indicating the input (or update) date. Furthermore, the cost information can be displayed in a visualized state, for example, as shown in Fig. 9.

[0068] Fig. 9 is a diagram showing an example of visualized cost information according to the embodiment. Fig. 9 shows an example of cost information related to the service node Ea (coupon issuing service) of the KPI tree shown in Fig. 5. Note that Fig. 9 shows a form in which a screen that visualizes cost information (hereinafter also referred to as a cost information screen) can be displayed by switching between tabs Ta and Tb. Here, the cost information is displayed when tab Tb is selected.

[0069] As shown in Fig. 9, the cost information screen displays the contents registered in the cost information DB 263. For example, Fig. 9 shows an example in which cost information related to the cost ID "C01" shown in Fig. 8 is displayed. Note that the cost information may be displayed in an uneditable state or in an editable state.

[0070] The cost information screen also displays "implementation costs" and "operation costs" as cost estimates. Here, "implementation costs" indicates the total amount of implementation costs. "Operation costs" indicates the total amount of operation costs. For example, in Figure 9, "350,000 yen," which is the total implementation costs for "POS," "store system," and "initial setup work," is displayed as "implementation costs." Also, "150,000 yen," the operation cost for "coupon issuance service," is displayed as "operation costs."

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

[0072] 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.

[0073] Furthermore, when any of the service nodes E included in the KPI tree is selected, the server device 20 provides a screen on which it is possible to create and edit the business flow and cost information for the service corresponding to the service node E. Then, when either the business flow or the cost information 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.

[0074] 3, the customer master 264 is a table or database for storing and managing information about customers to which the KPI tree is applied. In this embodiment, a customer refers to an organization such as a company or enterprise, but is not limited to this and may also refer to an individual such as a representative of an organization.

[0075] Fig. 10 is a diagram showing an example of the data configuration of the customer master 264 according to the embodiment. As shown in Fig. 10, the customer master 264 stores customer information, creation date, etc. in association with a customer ID. The customer ID is identification information for identifying each customer, and corresponds to the customer ID registered in the KPI tree DB 261 of Fig. 4. The creation date indicates the date on which the customer information was registered or updated.

[0076] Customer information is information about customers, and includes items such as customer name, address, telephone number, industry classification (major classification, medium classification, minor classification), sales, number of employees, number of stores, management department, implementation costs, and operating costs. Customer name indicates the trade name, business name, or company name of the customer corresponding to the customer ID. Address and telephone number indicate the customer's contact information, and for example, the head office address and telephone number are registered, respectively.

[0077] The business classification registers information indicating the business type to which the customer belongs, classified according to predetermined criteria. Attribute classifications can be set arbitrarily. Figure 10 shows an example in which the classification is divided into three levels: major classification, medium classification, and minor classification. However, the number of business classification divisions is not limited to this. Sales indicates the total sales of the customer's organization over a predetermined period (e.g., one year). Number of employees indicates the number of employees employed by the customer's organization. Number of stores indicates the number of stores owned by the customer's organization. Here, business classification, sales, number of employees, and number of stores can be rephrased as attribute information that indicates the customer's attributes. In addition, the location (prefecture, etc.) that can be identified based on the address or telephone number may also be included in the customer's attribute information.

[0078] The customer information also has items such as management department and person in charge. The management department indicates the name of the organization, such as the business office or department of the user in charge of supporting the customer's business. The person in charge registers the user ID and user name of the user in charge of supporting the customer's business. Note that the number of organizations and users that can be registered in the management department and person in charge items is not limited to one, and may be multiple.

[0079] Returning to Fig. 3, the name matching master 265 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 target. The name matching master 265 is used, for example, to resolve variations in the notation of node names in the KPI tree and to consolidate them into common node names (hereinafter also referred to as "name matching"). The name matching master 265 has, for example, the data configuration shown in Fig. 11.

[0080] 11 is a diagram illustrating an example of the data configuration of the name identification master 265 according to the embodiment. As illustrated in FIG. 11, the name identification master 265 stores the node name, type, reference node name, data creation date, etc. in association with each other.

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

[0082] 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.

[0083] In the example of FIG. 11, it is set that a node whose node type is "KGI" and whose node name is "Sales" is converted to the node name "Sales." It is also set that a node whose node type is "KPI" and whose node name is "Average Customer Spend" is converted to the node name "Customer Spend." It is also set that a node whose node type is "Factor" and whose node name is "Attractive Product Assortment" is converted to the node name "Product Assortment." It is also set that a node whose node type is "KGI" and whose node name is "Sales" is converted to the node name "Sales." This allows, for example, a final goal node A whose node name is "Sales" or "Sales" to be treated as a final goal node A whose node name is "Sales." In other words, nodes with a common title can be grouped together. Note that the node name of the source and the reference node name of the target have the same meaning.

[0084] Furthermore, the name matching information is not limited to one-way conversion from the source to the target, but may also specify reverse conversion of node names from the target to the source. In this case, for example, a node with a node type of "KGI" and a node name of "Sales" is reverse converted to the node names "Sales" and "Sales". In other words, final target nodes A with node names of "Sales", "Sales", and "Sales" can be treated as final target nodes A with the same node name.

[0085] The setting contents of the name identification information are 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 265 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.

[0086] 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 265. 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 265, 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 265 (or a separate table). This allows the CPU 21 of the server device 20 to present the node set in the KPI tree as a candidate for the name identification target in subsequent registration assistance.

[0087] 3, the service design information DB 266 is a table or database for storing and managing character strings (hereinafter also referred to as tags) that serve as search indexes extracted from information groups such as each customer's customer information, KPI tree, business flow, cost information, etc. The service design information DB 266 has, for example, the data configuration shown in FIG.

[0088] 12 is a diagram showing an example of the data configuration of the service design information DB 266 according to the embodiment. As shown in Fig. 12, the service design information DB 266 stores a customer ID, a service design information address, a name, a tag, a data creation date, etc. in association with each other.

[0089] The customer ID corresponds to the customer ID registered in the customer master 264, and the customer ID of the customer from whom the tag was extracted is registered. The service design information address registers address information indicating the storage location of the service design information of the customer corresponding to the customer ID. Here, the service design information includes any or all of the KPI tree, business flow, and cost information, and includes at least the KPI tree. The service design information may also include customer information corresponding to the customer ID. For example, the service design information address stores address information indicating the storage location of the KPI tree.

[0090] The name indicates the name of the service design information stored in the service design information address (hereinafter also referred to as the service design name). Here, the service design information address, or the combination of the customer ID and the service design name, is an example of specific information that can identify the service design information. Note that if multiple KPI trees with different KGIs are created for the same customer (customer ID), a different service design name will be set for each KPI tree.

[0091] The tags are registered with character strings extracted from the customer information, KPI tree, business flow, cost information, etc. of the customer corresponding to the customer ID. Fig. 12 shows an example in which character strings such as "Tokyo," "mass retailer," and "A branch office" are registered as tags for a customer with a customer ID of "12345678." Note that the data creation date stores data indicating the date of registration in the service design information DB 266.

[0092] Here, the character string registered in the tag is used as an index when searching for service design information that meets desired conditions from the service design information (KPI tree, etc.) stored in the KPI tree DB 261, etc. The process of tag extraction and search will be described later.

[0093] Returning to Fig. 3, the disclosure range setting DB 267 is a table or database for storing and managing the customer IDs of customers for which the disclosure range has been set on the disclosure setting screen described below, in association with the disclosure range of the service design information related to the customer IDs. The disclosure range setting DB 267 has, for example, the data configuration shown in Fig. 13. Here, the disclosure range specifies the disclosure range for personnel who use existing service design information to design KPI trees and propose services.

[0094] 13 is a diagram showing an example of a data configuration of the disclosure range setting DB 267 according to the embodiment. As shown in Fig. 13, the disclosure range setting DB 267 stores a customer ID, a name, a disclosure range, a data creation date, and the like in association with each other.

[0095] The customer ID corresponds to the customer ID registered in the customer master 264, and the customer ID of the customer for whom the disclosure range is set is registered. The name is the name (service design name) given when the disclosure range is set. The disclosure range is a condition that specifies the disclosure range of the service design information related to the customer ID. The disclosure range may be, for example, "All," which allows disclosure to all personnel, or the user ID of a specific management department or a specific user. If a specific management department is registered in the disclosure range, disclosure is not permitted to organizations other than the registered management department. Furthermore, if a specific user ID is registered in the disclosure range, disclosure is not permitted to anyone other than the registered user ID. The data creation date stores data indicating the date of registration in the disclosure range setting DB 267.

[0096] The data stored in the storage unit 26 is not limited to the above, and other data may be stored. For example, the storage unit 26 may store a table or database (hereinafter also referred to as a user management DB) that stores information about users. In this case, the user management DB stores user information (or user attributes) such as name, organization, position, and title in association with a user ID that can identify each user. In this embodiment, the user management DB is used, for example, to determine the conditions for the disclosure range. Furthermore, the user management DB may be used for user authentication of users who use the terminal device 10 by storing authentication information such as a password in association with the user ID.

[0097] 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.

[0098] Next, the functional configurations of the terminal device 10 and the server device 20 will be described with reference to Fig. 14. Fig. 14 is a diagram showing an example of the functional configurations of the terminal device 10 and the server device 20 according to the embodiment.

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

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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 tag extraction unit 215, a disclosure range setting unit 216, and a search processing unit 217 as functional units.

[0104] 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.

[0105] 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 simply referred to as screens). Here, 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 screens, or "displaying," "presenting," or "outputting" the screens.

[0106] 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, a business flow, cost information, and the like.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] Furthermore, the design support unit 212 displays the 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.

[0111] Furthermore, the design support unit 212 provides a screen on which cost information can be created. For example, when the design support unit 212 receives an operation to instruct creation of cost information for a service node E included in the KPI tree or a business flow corresponding to the service node E, the design support unit 212 provides a screen for creating cost information. Then, when the design support unit 212 receives an operation to complete the creation or editing of the cost information, the design support unit 212 stores the created or edited cost information in the cost information DB 263 in association with the target service.

[0112] 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.

[0113] 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.

[0114] The tag extraction unit 215 is an example of an extraction unit, and executes a process for extracting tags from the service design information of each customer.

[0115] For example, the tag extraction unit 215 extracts tags from customer information stored in the customer master 264. Specifically, the tag extraction unit 215 extracts, as tags, names of prefectures or other areas based on the customer's address (or telephone number) included in the customer information. The tag extraction unit 215 also extracts, as tags, names of the customer's business based on the business classification included in the customer information. The tag extraction unit 215 also extracts, as tags, names that indicate the size of the customer based on sales, number of employees, number of stores, and the like included in the customer information. The tag extraction unit 215 also extracts, as tags, names of organizations or users that provide business support to the customer based on information such as management departments and personnel included in the customer information.

[0116] Furthermore, for example, the tag extraction unit 215 extracts tags from the KPI tree stored in the KPI tree DB 261. Specifically, when a service node E is set in the KPI tree, the tag extraction unit 215 traces from the service node E to the upstream nodes to extract the node names of the solution node D, factor node C, intermediate goal node B (KPI), and final goal node A (KGI) as tags. For example, in the case of the KPI tree of Fig. 3, the tag extraction unit 215 traces from the service node Ea to the KGI to extract "coupon issuance" from the solution node Dc, "sales promotion" from the factor node Ce, "sales points" from the intermediate goal node Bc, "average customer price" from the intermediate goal node Bb, and "sales" from the final goal node A.

[0117] After extracting the node names, the tag extraction unit 215 uses the name identification master 265 to standardize node names that share common issues or objectives, and extracts the standardized node names as tags. Specifically, the tag extraction unit 215 refers to the name identification master 265 and determines whether a node name corresponding to a pair of the extracted node name and its node type is registered as a node name in the name identification master 265. If it is determined that the node name is registered in the name identification master 265, the tag extraction unit 215 converts the extracted node name into a corresponding reference node name, and uses the converted node name as a tag. For example, since the "average customer price" of the intermediate goal node Bb described above is registered as a node name in the name identification master 265, the tag extraction unit 215 extracts the reference node name "customer price" as a tag.

[0118] In this way, the tag extraction unit 215 standardizes node names with common issues or purposes into a single tag, thereby preventing the number of tags with common issues or purposes from increasing inadvertently, thereby improving the efficiency of searches using tags.

[0119] Also, for example, the tag extraction unit 215 extracts tags from the business flows stored in the business flow DB 262. Specifically, the tag extraction unit 215 extracts the names of pools set in the business flows as tags. Here, the pools of business flows indicate the main target ranges (e.g., processes) in business management, so the names of the pools succinctly represent the characteristics of the business flows.

[0120] In addition to the names of pools, the names (labels) of events and tasks set in pools may also be extracted as tags. However, when event or task names are used as tags, names that do not represent the characteristics of business management (services) will be included, such as step Qa "Product Selection" in Figure 7. Therefore, when using event or task names as tags, it is preferable to perform processing to remove names that do not represent the characteristics of business management (services). For example, the tag extraction unit 215 may use publicly known techniques such as TF-IDF to calculate the importance of each event or task name within the business flow, and extract names whose importance is above a threshold, i.e., names that are characteristic words within the business flow, as tags.

[0121] Further, for example, the tag extraction unit 215 extracts tags from the cost information stored in the cost information DB 263. Specifically, the tag extraction unit 215 extracts, as tags, the names of resources for which costs set in the cost information are to be calculated. Furthermore, the tag extraction unit 215 may extract, as tags, the names of resources in a predetermined category based on the classification of each resource. As an example, the tag extraction unit 215 may extract, as tags, the names of resources classified as "HW" and "SW." For example, in the case of the cost information shown in FIG. 8, the tag extraction unit 215 extracts, as tags, "POS" and "store system" classified as "HW" and "coupon issuing service" classified as "SW." Note that the reason why resources classified as "Personnel" are not used as tags is because the resources represent human work performed regardless of the content of the service and do not represent the characteristics of business management (service).

[0122] In this way, the tag extraction unit 215 extracts, as tags, character strings that represent the characteristics of each piece of service design information (customer information, KPI tree, business flow, and cost information).

[0123] Incidentally, there is a possibility that tags extracted from each piece of service design information (customer information, KPI tree, business flow, and cost information) may overlap. Therefore, it is preferable that the tag extraction unit 215 deletes overlapping tags after extracting tags from each piece of service design information. Specifically, when there are multiple tags with the same name, the tag extraction unit 215 keeps one tag from among these multiple tags and deletes the others. This allows the tag extraction unit 215 to prevent the number of tags with overlapping names from increasing inadvertently, thereby improving the efficiency of searches using tags.

[0124] The timing at which the tag extractor 215 extracts tags is not particularly important, and tag extraction can be performed at any timing.

[0125] For example, the tag extraction unit 215 may automatically extract tags from the service design information of each customer ID registered in the customer master 264 at predetermined time intervals. Furthermore, for example, the tag extraction unit 215 may automatically extract tags when a KPI tree, a business flow, or cost information is created or updated. When automatically extracting tags, the tag extraction unit 215 associates the tags extracted from the service design information with the customer ID, address, etc. related to the service design information, and registers them in the service design information DB 266.

[0126] The tag extraction unit 215 may also be configured to extract tags in response to an instruction from a user. For example, the tag extraction unit 215 may be configured to extract tags when a user instructs to set the disclosure range of service design information, by cooperating with the disclosure range setting unit 216, etc. Note that the tags extracted by the tag extraction unit 215 may also be called "tag candidates" because they are selected and discarded on a disclosure range setting screen (see FIG. 15) described later.

[0127] The disclosure range setting unit 216 performs processing to support setting of the disclosure range of the service design information. Specifically, the disclosure range setting unit 216 cooperates with the GUI providing unit 211 to provide the user with a screen for setting the disclosure range (disclosure range setting screen).

[0128] For example, when the disclosure range setting unit 216 receives an operation to instruct setting of the disclosure range on the KPI tree screen shown in Fig. 5, it provides a disclosure range setting screen. Here, the operation method for instructing setting of the disclosure range is not particularly limited. For example, the disclosure range setting unit 216 may display an operation menu including an operator for instructing setting of the disclosure range in response to an operation of a hamburger button displayed in the upper left of the KPI tree screen. Then, when the operator for instructing setting of the disclosure range is selected, the disclosure range setting unit 216 provides a disclosure range setting screen.

[0129] 15 is a diagram showing an example of a screen provided by the server device 20 according to the embodiment, illustrating an example of a disclosure range setting screen. Here, Fig. 15 shows the disclosure range setting screen when the operator "Public" that instructs setting of the disclosure range is selected from the operation menu of the hamburger button on the KPI tree screen shown in Fig. 5.

[0130] As shown in FIG. 15, the disclosure range setting screen 30 has a name field 31, a disclosure range field 32, a tag display field 33, an add tag button , a cancel button 35, and a publish button .

[0131] The name of the service design information (service design name) related to the KPI tree displayed on the KPI tree screen can be input in the name field 31. The service design name may be input by the user himself or automatically by the disclosure range setting unit 216. In the latter case, for example, the disclosure range setting unit 216 displays (inputs) in the name field 31 a name that combines the customer name of the customer related to the KPI tree being displayed and the node name of the solution node D that is located above the service node E.

[0132] In addition, if the disclosure range setting unit 216 determines that the corresponding service design name is registered in the service design information DB 266 based on the customer ID of the customer related to the KPI tree displayed on the KPI tree screen or the address of the KPI tree, it may display the service design name in the name column 31.

[0133] In the disclosure range field 32, it is possible to input conditions that define the disclosure range of the service design information. In the disclosure range field 32, it is possible to input "All," which allows disclosure to all personnel, the name of a specific management department, the user ID of a specific personnel, etc. FIG. 15 shows a form in which the disclosure range conditions can be input using a pull-down menu. In this case, the pull-down menu has various disclosure range conditions as options, and when one option is selected, the selected condition is input into the disclosure range field 32.

[0134] In addition, if the disclosure range setting unit 216 determines, based on the customer ID of the customer related to the KPI tree displayed on the KPI tree screen or the address of the KPI tree, that the corresponding disclosure range conditions are registered in the service design information DB 266, it may display the disclosure range conditions in the disclosure range column 32.

[0135] The tag display field 33 displays each of the tags (tag candidates) extracted by the tag extraction unit 215. For example, the disclosure range setting unit 216 determines whether or not the corresponding tag is registered in the service design information DB 266 based on the customer ID of the customer related to the KPI tree displayed on the KPI tree screen and the address of the KPI tree.

[0136] If tags are registered in the service design information DB 266, the disclosure range setting unit 216 reads each of the tags from the service design information DB 266 and displays them in the tag display field 33. If tags are not registered in the service design information DB 266, the disclosure range setting unit 216 controls the tag extraction unit 215 to extract tags from the customer's service design information related to the KPI tree displayed on the KPI tree screen. Then, the disclosure range setting unit 216 displays each of the tags extracted by the tag extraction unit 215 in the tag display field 33. Note that FIG. 15 shows an example in which nine tags, such as "Tokyo" and "mass retailer," are displayed in the tag display field 33.

[0137] The add tag button 34 is an operator for instructing the addition of a tag. When the add tag button 34 is operated, the disclosure range setting unit 216 displays an input screen (not shown) on which any character string can be input. The disclosure range setting unit 216 adds and displays the character string input on the input screen as a new tag in the tag display field 33.

[0138] In addition to adding new tags, the disclosure range setting screen 30 also allows for deleting tags displayed in the tag display field 33. There is no particular restriction on the operating method for deleting tags, and various methods can be adopted. As one example, when any tag displayed in the tag display field 33 is pressed and held, the disclosure range setting unit 216 may display a delete operator in the upper right or upper left corner of the tag, and delete (erase) the tag on the condition that the operator is operated.

[0139] For example, the user checks the tags displayed in the tag display field 33 and determines whether they represent the characteristics of the service design information to be made public. The user can then delete unnecessary tags or add new tags to determine the tags to be used as search indexes. In other words, the server device 20 can support the task of assigning search indexes (tags) to service design information.

[0140] The cancel button 35 is an operator for instructing to cancel the setting of the disclosure range. When the disclosure range setting unit 216 receives an operation of the cancel button 35, it erases the disclosure range setting screen 30 and displays the previous screen (KPI tree screen).

[0141] The disclosure button 36 is an operator for instructing application of the disclosure range setting. When the disclosure range setting unit 216 accepts operation of the disclosure button 36, it associates each of the tags displayed in the tag display field 33 with the customer ID of the customer related to the KPI tree displayed on the KPI tree screen, the address of the KPI tree, etc., and registers them in the service design information DB 266. In addition, the disclosure range setting unit 216 associates the name entered in the name field 31 and the disclosure range entered in the disclosure range field 32 with the customer ID of the customer related to the KPI tree displayed on the KPI tree screen, etc., and registers them in the disclosure range setting DB 267.

[0142] While FIG. 15 shows an example in which the disclosure range setting screen 30 is displayed from the KPI tree screen, the disclosure range setting screen 30 can also be displayed from the business flow screen (FIG. 7) or the cost information screen (FIG. 9). Specifically, an operation menu including an operator for instructing the setting of the disclosure range can be displayed in response to an operation of the hamburger button displayed in the upper left of the business flow screen or the cost information screen. Then, the disclosure range setting unit 216 provides the disclosure range setting screen when an operator for instructing the setting of the disclosure range is selected.

[0143] Returning to Fig. 14, the search processing unit 217 is an example of a receiving means and a searching means. The search processing unit 217 receives input of search keywords from the user and executes processing for searching for service design information based on tags corresponding to the keywords. Specifically, the search processing unit 217 cooperates with the GUI providing unit 211 to provide the user with a screen for searching for service design information (hereinafter also referred to as a search screen). For example, the search processing unit 217 provides the search screen shown in Fig. 16. In providing the search screen, the search processing unit 217 receives input of the user ID, department, etc. of the operator (user) from the terminal device 10, etc.

[0144] 16 is a diagram showing an example of a screen provided by the server device 20 according to the embodiment, illustrating an example of a search screen. As shown in FIG. 16, a search screen 40 has a keyword input field 41 and a search result display field 42.

[0145] The keyword input field 41 allows the user to input keywords that will be used as search keys. For example, the user inputs a string of characters that represents the industry or issues of the client that the user is responsible for as a keyword into the keyword input field 41. Note that by inputting multiple keywords into the keyword input field 41, it is also possible to perform searches using AND / OR, etc. For example, an OR search can be performed by inserting a space between multiple keywords. Also, for example, an AND search can be performed by inserting a "+" between multiple keywords.

[0146] When a keyword is input in the keyword input field 41, the search processing unit 217 searches the service design information DB 266 for a customer ID and name (service design name) associated with the tag corresponding to the keyword.

[0147] 16, when "mass retailer store" is entered in the keyword input field 41, the search processing unit 217 performs an OR search to search for customer IDs and service design names associated with the tags "mass retailer" or "store" from the service design information DB 266. Also, when "mass retailer + store" is entered in the keyword input field 41, the search processing unit 217 performs an AND search to search for customer IDs and service design names associated with both the tags "mass retailer" and "store" from the service design information DB 266.

[0148] Furthermore, if the search processing unit 217 is able to search the service design information DB 266, it refers to the disclosure range setting DB 267 and determines whether the user satisfies the disclosure range conditions for the searched combination of customer ID and service design name. Specifically, the search processing unit 217 determines whether the user satisfies the disclosure range conditions by comparing the disclosure range conditions with the user's attributes (user ID or department). For example, if "All" is set as the disclosure range, the search processing unit 217 determines that the disclosure range conditions are met regardless of the user's attributes. Furthermore, if a specific user ID or department is set as the disclosure range, the search processing unit 217 determines that the disclosure range conditions are met if the user's attributes (user ID or department) match the set conditions. Then, the search processing unit 217 displays the search results for the keyword entered in the keyword input field 41 in the search result display field 42 based on the combination of customer ID and service design name that is determined to satisfy the disclosure range conditions.

[0149] The search result display field 42 is an area for displaying the search results for the keywords entered in the keyword input field 41. For example, based on a pair of a customer ID and a service design name that is determined to satisfy the conditions for the disclosure range, the search processing unit 217 associates the customer name corresponding to the customer ID, the service design name, and the data creation date, and displays them in the search result display field 42. Here, the customer name can be identified based on the customer ID and the customer master 264. Furthermore, the data creation date can be identified based on the pair of the customer ID and the service design name and the service design information DB 266.

[0150] 16 shows an example in which seven search results are displayed in the search result display field 42 in response to the input of the keyword "mass retailer store." Here, the search results displayed in the search result display field 42 all relate to service design information associated with the tag "mass retailer" or "store." Therefore, by referring to the service design information of the customer name or service design name displayed in the search result display field 42, the user can efficiently use past service design information related to the input keyword.

[0151] Furthermore, when a search result displayed in the search result display field 42 is selected, the search processing unit 217 may cooperate with the GUI providing unit 211, etc. to display service design information related to the selected search result. Specifically, when one of the search results is selected, the search processing unit 217 identifies the service design information address associated with the service design name of the selected search result from the service design information DB 266. Then, the search processing unit 217 reads out service design information (e.g., a KPI tree) from the identified service design information address and displays a screen (e.g., a KPI tree screen) showing the service design information.

[0152] This allows users to easily find existing service design information related to the entered keywords, allowing them to efficiently design services for new customers while effectively utilizing existing service design information.

[0153] In this embodiment, the conditions for the disclosure range are determined based on the user's department and user ID, but the disclosure range conditions may be determined based on other factors. For example, the conditions for the disclosure range may be determined based on the user's job title or rank. Also, the disclosure range may be configured to be accessible to all users without setting any conditions for the disclosure range.

[0154] An example of the operation of the server device 20 will be described below with reference to Fig. 17 and Fig. 18. First, an example of processing related to tag extraction will be described with reference to Fig. 17. Note that this processing describes an example of processing when tags are extracted in conjunction with setting the disclosure range.

[0155] 17 is a flowchart showing an example of a disclosure range setting process executed by the server device 20 according to the embodiment. First, the disclosure range setting unit 216 accepts an operation to instruct setting of a disclosure range from a screen, such as a KPI tree screen, on which the customer ID of the customer and the address of the service design information can be identified (step S11). Next, the disclosure range setting unit 216 refers to the service design information DB 266 and the disclosure range setting DB 267, and determines whether or not an existing setting associated with a combination of the customer ID and the address of the service design information has been registered (step S12).

[0156] If it is determined that an existing setting has been registered (step S12; Yes), the disclosure range setting unit 216 reads out the existing service design name and tag from the service design information DB 266, and also reads out the existing disclosure range from the disclosure range setting DB (step S13). Next, the disclosure range setting unit 216 displays a disclosure range setting screen that reflects the existing service design name, tag, and disclosure range (step S19), and proceeds to step S20.

[0157] On the other hand, if it is determined in step S12 that the service design name is not registered (step S12; No), the disclosure range setting unit 216 inputs the customer ID and the address of the service design information into the tag extraction unit 215, causing the tag extraction unit 215 to extract tags.

[0158] The tag extraction unit 215 reads customer information corresponding to the customer ID from the customer master 264 and extracts tags from the customer information (step S14). Next, the tag extraction unit 215 reads a KPI tree from the KPI tree DB 261 based on the address of the service design information, and extracts tags from the KPI tree (step S15). Next, the tag extraction unit 215 reads a business flow from the business flow DB 262 based on the address of the service design information, and extracts tags from the business flow (step S16). Next, the tag extraction unit 215 reads cost information from the cost information DB 263 based on the address of the service design information, and extracts tags from the cost information (step S17). Next, the tag extraction unit 215 deletes duplicate tags from the extracted tags (step S18).

[0159] Next, the disclosure range setting unit 216 displays a disclosure range setting screen that reflects the tags extracted by the tag extraction unit 215 (step S19), and the process proceeds to step S20.

[0160] In the next step S20, the disclosure range setting unit 216 accepts editing operations on the disclosure range setting screen (step S20). For example, the disclosure range setting unit 216 accepts tag editing (addition, deletion) operations, input or editing operations of service design names, and setting or editing operations of disclosure ranges.

[0161] Next, when the disclosure range setting unit 216 receives an operation to confirm the disclosure range via a disclosure button or the like (step S21), it registers each of the service design name and tag displayed on the disclosure range setting screen in the service design information DB 266 in association with the customer ID and the address of the service design information (step S22). Also, the disclosure range setting unit 216 registers the disclosure range displayed on the disclosure range setting screen in the disclosure range setting DB 267 in association with the customer ID and the address of the service design information (step S23), and ends the process.

[0162] In steps S22 and S23, the disclosure range setting unit 216 may simply reflect the difference data updated by the editing operation in step S20 in the service design information DB 266 and the disclosure range setting DB 267.

[0163] Next, an example of processing related to a search for service design information will be described with reference to Fig. 18. Fig. 18 is a flowchart showing an example of search support processing executed by the server device 20 of the embodiment. First, upon receiving access from a user, the search processing unit 217 acquires information (e.g., a user ID) that can identify the user attributes of the user (step S31).

[0164] Next, the search processor 217 displays a search screen (step S32) and waits until a search keyword is entered. When a search keyword is entered (step S33), the search processor 217 searches the service design information DB 266 for a pair of a customer ID and a service design name associated with a tag corresponding to the keyword (step S34).

[0165] Next, the search processing unit 217 refers to the disclosure range setting DB 267, compares the disclosure range conditions for the pair of customer ID and service design name searched from the service design information DB 266 with the attributes of the accessing user, and determines whether the user satisfies the disclosure range conditions (step S35). Here, for a pair of customer ID and service design name that satisfies the disclosure range conditions (step S35; Yes), the search processing unit 217 displays the search results based on the pair of customer ID and service design name on the search screen (step S36), and proceeds to step S37. On the other hand, for a pair of customer ID and service design name that does not satisfy the disclosure range conditions (step S35; No), the search processing unit 217 proceeds to step S37 without displaying the search results.

[0166] Next, the search processing unit 217 determines whether the keyword has been changed (step S37). For example, if a keyword has been added or deleted, the search processing unit 217 determines that the keyword has been changed (step S37; Yes) and returns the process to step S33. On the other hand, if the search processing unit 217 determines that the keyword has not been changed (step S37; No), the process proceeds to step S38.

[0167] The search processing unit 217 determines whether or not one search result has been selected from the search results displayed on the search screen (step S38). When a selection operation of a search result has been received (step S38; Yes), the search processing unit 217 identifies the address of the service design information corresponding to the selected search result from the service design information DB 266, and displays a screen (e.g., a KPI tree screen) showing the service design information stored at that address (step S39). On such a screen, for example, it is also possible to display a screen of the business flow associated with service node E from the KPI tree screen, or a screen of cost information.

[0168] Next, the search processing unit 217 determines whether an instruction to end the display of the screen representing the service design information has been given by an operation such as closing the screen (step S40). If an instruction to end the display has not been given (step S40; No), the search processing unit 217 returns the process to step S39, thereby continuing to display the screen representing the service design information. On the other hand, if an instruction to end the display has been given (step S40; Yes), the search processing unit 217 closes the screen representing the service design information and then returns the process to step S37.

[0169] On the other hand, if a selection operation of a search result is not accepted in step S38 (step S38; No), the search processing unit 217 proceeds to step S41. In step S41, the search processing unit 217 determines whether or not an instruction to end the search has been given (step S41). If an instruction to end the search has not been given (step S41; No), the search processing unit 217 returns the process to step S37 to continue the search process. If an instruction to end the search has been given (step S41; Yes), the search processing unit 217 closes the search screen and ends this process.

[0170] As described above, the server device 20 associates and stores customer information about a customer, a KPI tree that represents the relationship between the customer's business goals and the services implemented to achieve those business goals in a tree structure, and related information related to the implementation of the service (workflow, cost information). The server device 20 also extracts tags that serve as search indexes representing the characteristics of the service design information from the customer information, KPI tree, and service design information of the related information related to the same customer. The server device 20 then associates each of the extracted tags with specific information that can identify the service design information and stores the tags.

[0171] This allows the user to easily find existing service design information related to desired conditions based on the tags stored in association with the service design information, and thus allows the user to design services for new customers while utilizing existing service design information, etc. Therefore, the server device 20 can support the design of services.

[0172] Furthermore, the server device 20 extracts, as tags, character strings representing customer characteristics contained in the customer information. This allows the user to easily find existing service design information related to desired conditions for the customer, enabling the user to design services for new customers while utilizing existing service design information, etc. Therefore, the server device 20 can support the design of services.

[0173] Furthermore, the server device 20 traces the upstream nodes from the service node E included in the KPI tree to extract the node name set for each node as a tag. This allows the user to easily find existing service design information related to the desired business goals and problem conditions, and thus allows the user to design services for new customers while utilizing existing service design information, etc. Therefore, the server device 20 can support the design of services.

[0174] Furthermore, if there are duplicate tags extracted from the service design information, the server device 20 deletes the duplicate tags. This allows the server device 20 to prevent the number of tags with duplicate names from increasing inadvertently, thereby improving the efficiency of searches using tags.

[0175] The server device 20 also accepts input of keywords that serve as search keys and outputs specific information associated with tags corresponding to the keywords as search results. This allows a user to easily find existing service design information related to a keyword by inputting the keyword, thereby enabling the user to design services for new customers while utilizing existing service design information, etc. Therefore, the server device 20 can support service design.

[0176] 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.

[0177] (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.

[0178] In this case, the terminal device 10 can display various screens, extract tags, and search for service design information by including functional units such as the above-mentioned GUI providing unit 211, design support unit 212, tag extraction unit 215, disclosure range setting unit 216, and search processing unit 217. Note that the terminal device 10 is assumed to be in a state where it can read and write various DBs held by the server device.

[0179] 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.

[0180] (Variation 2) In the above embodiment, the KPI tree and related information (workflow, cost information) are stored in association with the customer information of the customer, and tags representing the characteristics of the information are extracted from all of this information. However, this is not limited to this, and tags may be extracted from only a portion of the information. For example, the tag extraction unit 215 may extract tags representing the characteristics of an information group including customer information and a KPI tree or related information. The related information includes at least one of business flow and cost information.

[0181] The server device 20 may also store at least one of a KPI tree and related information in association with the customer information of the customer. In this case, the tag extraction unit 215 extracts tags that represent characteristics of an information group including the customer information, the KPI tree, and / or the related information stored in the server device 20. The related information includes at least one of business flow and cost information.

[0182] In the above embodiment, the business flow and cost information are stored in association with the service node (target service) of the KPI tree, but this is not limiting, and related information may be stored in a form independent of the KPI tree. For example, an identifier (e.g., service ID or service design name) of the service to be implemented to achieve the business goal of each customer may be set, and the service node of the KPI tree and related information may be stored in association with the identifier.

[0183] This makes it possible to extract tags from an information group that includes customer information and at least one of a KPI tree and related information, thereby achieving the same effects as those of the above-described embodiment.

[0184] 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).

[0185] 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.

[0186] 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]

[0187] 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 Tag Extraction Unit 216 Public Range Setting Section 217 Search processing unit 261 KPI Tree DB 262 Business Flow DB 263 Cost Information DB 264 Customer Master 265 Name Master 266 Service Design Information DB 267 Public Scope Setting DB [Prior art documents] [Patent documents]

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

Claims

1. a first storage means for storing at least one of tree information representing, in a tree structure, the relationship between the business goals of a customer and the services to be implemented to achieve the business goals, in association with customer information relating to the customer, and related information relating to the implementation of the services; extraction means for extracting a character string representing a characteristic of an information group including the customer information and at least one of the tree information and the related information; a second storage means for storing each of the character strings extracted by the extraction means as an index for search, in association with specific information that can identify the information group; An information processing device comprising:

2. the extraction means extracts a character string representing a characteristic of the customer included in the customer information; The information processing device according to claim 1 .

3. the extraction means extracts, as the character string, a node name set to each node by tracing upstream nodes from a service node related to the implementation of the service included in the tree information; The information processing device according to claim 1 .

4. the extraction means extracts the character string from the information group at predetermined time intervals. The information processing device according to claim 1 .

5. the extraction means extracts the character string from the information group when the information group is updated. The information processing device according to claim 1 .

6. the extraction means extracts the character string from the information group in response to a user operation. The information processing device according to claim 1 .

7. If the character strings extracted from the information group are duplicated, the extraction means deletes the duplicated character strings.

7. The information processing device according to claim 1.

8. an accepting means for accepting an input of a character string to be a search key; a search means for outputting, as a search result, the specific information associated with an index corresponding to the character string received by the receiving means; The information processing device according to claim 1 , further comprising:

9. The computer of the information processing device, a first storage means for storing at least one of tree information representing, in a tree structure, the relationship between the business goals of a customer and the services to be implemented to achieve the business goals, in association with customer information relating to the customer, and related information relating to the implementation of the services; extraction means for extracting a character string representing a characteristic of an information group including the customer information and at least one of the tree information and the related information; a second storage means for storing each of the character strings extracted by the extraction means as an index for search, in association with specific information that can identify the information group; A program to make it function as such.

Images