Information processing device and program
The information processing apparatus and program address the inconvenience in setting service verification specifications by utilizing tree data to extract and visualize verification items, improving the efficiency and accuracy of service design processes.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- TOSHIBA TEC KK
- Filing Date
- 2023-07-03
- Publication Date
- 2026-07-01
Smart Images
Figure 0007883469000001 
Figure 0007883469000002 
Figure 0007883469000003
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to an information processing apparatus and a program.
Background Art
[0002] At a site such as a store, various business services (hereinafter also referred to as services) are carried out. In such a site, by using methods such as the KPI (Key Performance Indicator) tree method and BPMN (Business Process Model and Notation), the processing procedures of each element related to the implementation of the service may be designed as a business flow. For example, conventionally, a technique has been proposed that can automatically create a business flow so that the input / output relationship between adjacent operations is continuous.
[0003] By the way, in the above-described service design process, it is important to define (hereinafter also referred to as setting) the specifications related to the effect verification of the service based on the target contents set as the final goal and intermediate goals. However, in the conventional technology, no consideration has been given to the setting of the specifications related to the effect verification of the service, and there has been room for improvement in terms of convenience.
Summary of the Invention
Problems to be Solved by the Invention
[0004] The problem to be solved by the present invention is to provide an information processing apparatus and a program capable of supporting the setting work of the specifications related to the effect verification of the service.
Means for Solving the Problems
[0005] The information processing apparatus according to the embodiment is based on tree data in which the relationship between a target node indicating a management target and a service node indicating the service content for realizing the target is set step by step in a tree structure, and a first reception unit that receives a selection operation of the service node, and the selected service node An extraction means for extracting items related to the target content set for each of the target nodes from the target nodes located between the selected service node and the root node in the tree data to which the service belongs, as verification items for verifying the effectiveness of the service content, the extraction means extraction The system includes a means for providing a screen that allows setting specifications related to the effectiveness verification of each of the aforementioned verification items. [Brief explanation of the drawing]
[0006] [Figure 1] Figure 1 is a diagram showing an example configuration of a business support system according to an embodiment. [Figure 2] Figure 2 shows an example of the hardware configuration of a terminal device according to this embodiment. [Figure 3] Figure 3 shows an example of the hardware configuration of a server device according to this embodiment. [Figure 4] Figure 4 shows an example of the data structure of the KPI tree database according to the embodiment. [Figure 5] Figure 5 shows an example of a visualized KPI tree according to the embodiment. [Figure 6] Figure 6 shows an example of the data structure of the business flow database according to the embodiment. [Figure 7] Figure 7 shows an example of a visualized business flow according to the embodiment. [Figure 8] Figure 8 shows an example of the data structure of the service definition DB according to the embodiment. [Figure 9] Figure 9 shows an example of the functional configuration of a terminal device and a server device according to an embodiment. [Figure 10] Figure 10 shows an example of a screen provided by the design support unit of the embodiment. [Figure 11] Figure 11 shows an example of a screen provided by the design support unit of the embodiment. [Figure 12] Figure 12 is a flowchart showing an example of the processing performed by the server device of the embodiment. [Modes for carrying out the invention]
[0007] The embodiments will be described in detail below with reference to the drawings. However, the invention is not limited to the embodiments described below.
[0008] Figure 1 shows an example configuration of a business support system according to an embodiment. As shown in Figure 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 connected to each other via a network N such as a LAN (Local Area Network).
[0009] Terminal device 10 is a terminal device used by users of the business support system 1. Terminal device 10 performs various processes in response to user operations. For example, a user can use various functions provided by server device 20 by operating terminal device 10 to access server device 20. Terminal device 10 can be implemented as a stationary terminal device such as a PC (Personal Computer), or a portable terminal device such as a notebook PC, tablet, or smartphone.
[0010] 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 KPI trees and business flows, which will be described later.
[0011] In this embodiment, an example is described in which the server device 20 is implemented by a single information processing device, but this is not the only example. For example, the server device 20 may be implemented by multiple information processing devices using technologies such as cloud computing.
[0012] Next, the configurations of the terminal device 10 and server device 20 described above will be explained.
[0013] FIG. 2 is a diagram showing an example of the hardware configuration of the terminal device 10. As shown in FIG. 2, the terminal device 10 includes computer components such as a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, and a RAM (Random Access Memory) 13.
[0014] The CPU 11 is an example of a processor and comprehensively controls each part of the terminal device 10. The ROM 12 stores various programs. The RAM 13 is a workspace for developing programs and various data.
[0015] The terminal device 10 further includes a display unit 14, an operation unit 15, a storage unit 16, and a communication unit 17.
[0016] 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. Note that the operation unit 15 may be a touch panel provided on the display screen of the display unit 14.
[0017] The storage unit 16 is composed of a storage medium such as an HDD (Hard Disk Drive) or a flash memory, and maintains the stored content 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.
[0018] The CPU 11 operates according to the programs stored in the ROM 12 and the storage unit 16 and developed in the RAM 13, thereby executing various processes.
[0019] 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.
[0020] Figure 3 shows an example of the hardware configuration of the server device 20. As shown in Figure 3, the server device 20 includes a computer configuration such as a CPU 21, ROM 22, and RAM 23.
[0021] The CPU 21 is an example of a processor that comprehensively controls all parts of the server device 20. The ROM 22 stores various programs. The RAM 23 is a workspace for displaying programs and various data.
[0022] The server device 20 also includes a display unit 24, an operation unit 25, a storage unit 26, and a communication unit 27.
[0023] 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.
[0024] The memory unit 26 is composed of a storage medium such as an HDD or flash memory, and retains its contents even when the power is cut off. The memory unit 26 stores programs that the CPU 21 can execute and various setting information. For example, the memory unit 26 stores web application programs that can provide various functions to the terminal device 10. The CPU 21 executes various processes by operating according to programs stored in the ROM 22 and the memory unit 26 and loaded into the RAM 23.
[0025] Furthermore, the memory unit 26 stores KPI tree DB 261, business flow DB 262, service definition DB 263, and the like.
[0026] The KPI Tree DB261 is a table or database for storing and managing KPI trees. Here, a KPI tree is tree data in a tree structure where the relationship between an organization's or company's management goals (the final goal described later) and the measures to achieve those goals (intermediate goals, factors, solutions, services, etc. described later) is set stepwise by nodes.
[0027] Figure 4 shows an example of the data structure of the KPI tree DB261. As shown in Figure 4, the KPI tree DB261 stores customer names, KPI trees, etc., associating each KPI tree with an identifiable tree ID.
[0028] The "Customer Name" field contains information that identifies the customer to whom the KPI tree applies. The "KPI Tree" field contains the actual data for the KPI tree (hereinafter also referred to as the data file) or an address indicating the location where the data file is stored.
[0029] A KPI tree is created using methods such as KPIs (Key Performance Indicators). A KPI tree can be represented in a visualized form, as shown in Figure 5, for example.
[0030] Figure 5 shows an example of a visualized KPI tree. Specifically, Figure 5 shows the visualized KPI tree applied to the customer "ABC Supermarket" shown in Figure 4.
[0031] As shown in Figure 5, a KPI tree consists of multiple nodes connected in a tree structure. Here, the root node, Final Goal Node A, is the node for setting the achievement goal. Final Goal Node A corresponds to, for example, a KGI (Key Goal Indicator). For example, if the ultimate goal is to increase store sales, then Final Goal Node A would be set to something like "Sales," which indicates the content of the goal.
[0032] The final target node A is connected to one or more intermediate target nodes B. It is also possible to connect one or more intermediate target nodes B to each intermediate target node B. Intermediate target nodes B are set with intermediate goals to achieve the goals (final or intermediate goals) set in the node directly above them. Intermediate target nodes B correspond to, for example, KPIs (Key Performance Indicators).
[0033] Figure 5 shows an example where, below the final target node A, intermediate target node Ba has an objective of increasing the number of customers, and intermediate target node Bb has an objective of increasing the average customer spending. Furthermore, below intermediate target node Bb, an example is shown where intermediate target node Bc has an objective of increasing the number of stores, and intermediate target node Bd has an objective of increasing the average price per item.
[0034] Furthermore, in the KPI tree, it is possible to place factor nodes C below the intermediate goal node B, which represent the factors necessary to achieve the intermediate goal set in intermediate goal node B. Factor node C corresponds to, for example, a KSF (Key Success Factor).
[0035] Figure 5 shows an example where, under the intermediate target node Ba, factor nodes Ca to Cd are placed, each representing a factor for increasing the number of customers visiting the store: "Quality Improvement," "Product Assortment," "Sales Floor," and "Advertising." It also shows an example where, under the intermediate target node Bc, factor nodes Ce and Cf are placed, each representing a factor for increasing the number of items sold: "Sales Promotion" and "Impulse Buying." Furthermore, it shows an example where, under the intermediate target node Bb, factor node Cg is placed, each representing a factor for increasing the average customer spending: "Improved Customer Understanding."
[0036] Furthermore, in the KPI tree, it is possible to place a Solution Node D below the Intermediate Target Node B or Factor Node C, which represents a solution that achieves (resolves) the intermediate objective or factor set in the node directly above it.
[0037] Figure 5 shows an example where solution nodes Da and Db, each configured for "store information visualization" and "product assortment optimization," are placed under factor nodes Ca to Cc. It also shows an example where solution nodes Dc to De, each configured for "coupon issuance," "point management," and "POP creation," are placed under factor node Ce. Furthermore, it shows an example where solution node Df, configured for "CRM (Customer Relationship Management)," is placed under factor node Cg.
[0038] Furthermore, in the KPI tree, it is possible to place a service node E under a factor node C or solution node D, which represents a specific service for realizing the factor or solution set in the node directly above it. Here, service node E is located at the end of the tree structure and represents a specific measure for realizing the factor or solution set in the node directly above it.
[0039] Figure 5 shows an example where a service node Ea, configured with "Service A," is placed under the solution node Dd.
[0040] Each node in the KPI tree is assigned a node ID to identify it. Furthermore, information about the corresponding node is stored in association with the node ID. For example, service node E is associated with the business flow related to service implementation and verification items related to service effectiveness evaluation.
[0041] The KPI tree described above can be saved, for example, in JSON (JavaScript Object Notation) format. However, the KPI tree is not limited to JSON; it may also be saved in other data formats such as XML (Extensible Markup Language).
[0042] Returning to Figure 3, the business flow DB262 is a table or database for storing and managing business flows. A business flow is a data file that describes each element involved in the execution of a business and the execution content performed by that element as a series of procedures. Specifically, a business flow describes the execution content and procedures performed by each element involved in the implementation of a service.
[0043] Figure 6 shows an example of the data structure of the business flow DB262. As shown in Figure 6, the business flow DB262 stores the target service, flow ID, business flow name, and data file in association with each other.
[0044] The "Target Services" field registers information specifying the service corresponding to the business process described in the business flow. Specifically, it registers the node ID of the service node E designated as the target service, the tree ID of the KPI tree to which the service node E belongs, etc. However, this is not the only way to specify the target service.
[0045] The Flow ID field registers a Flow ID that identifies the business flow. The Business Flow Name field registers information indicating the name of the business flow. For example, the Business Flow Name may be the name of the service performed by the business flow (the node name of service node E). The Data File field registers the data file of the business flow or an address indicating the location where the data file is stored.
[0046] Business flows are created using methods such as flowcharts and BPMN (Business Process Modeling Notation). Business flows should be created according to the service content, but if the service content is common or similar, the same business flow can be used even if the KPI trees are different. Figure 6 shows an example in which the business flow with flow ID "F01" is used in service node Ea, which is included in the KPI trees with tree IDs T01 and T02, respectively.
[0047] Business processes are created using methods such as flowcharts and BPMN (Business Process Modeling Notation). Business processes can be represented in a visualized form, for example, as shown in Figure 7.
[0048] Figure 7 shows an example of a visualized business process flow. Note that Figure 7 is an example of the business process flow related to service node Ea (Service A) in the KPI tree shown in Figure 5.
[0049] As shown in Figure 7, in the business flow, the sequence of actions (or processes) related to the implementation of service A is described for each element that performs the action between the start event ST and the end event EN. The business flow in Figure 7 shows an example where the elements are described as "customers" visiting the store, "surveillance cameras" and "payment systems" installed in the store, and "store employees" working in the store.
[0050] Here, "surveillance cameras" are an example of hardware resources, and are installed, for example, at multiple locations within a store. Similarly, "payment systems" are an example of software resources, and are implemented through the collaboration of multiple PCs (Personal Computers), such as POS systems, and applications installed on those PCs. Furthermore, additional services provided in conjunction with payment (e.g., point services) may also be included in the business flow. Hereafter, the hardware resources, software resources, and additional services related to the implementation of the target services will be collectively referred to as "elements."
[0051] In the business flow diagram in Figure 7, the "customer" flow is first described as entering the store (step Qa), selecting the products to be purchased (step Qb), and proceeding to the cash register (step Qc). The "surveillance camera" flow installed in the store is described as taking a picture of the "customer" heading to the cash register (step Qd) and transmitting the captured image data to the payment system installed in the store (step Qe). The "payment system" flow is described as receiving the image data from the "surveillance camera" (step Qf) and displaying customer information such as the "customer's" attributes derived from the image data on a display device (step Qg).
[0052] Furthermore, the workflow for a "store clerk" operating the register is described as follows: confirming customer information displayed by the "payment system" (step Qh), and performing register operations for the items brought in by the "customer" (step Qi). In addition, it is described that the "payment system" executes the "payment processing" in conjunction with the "store clerk's" register operations (step Qj).
[0053] Furthermore, it is described that the "customer" pays for the goods (step Qk) in accordance with the "payment processing" of the "payment system" and leaves the store (step Ql). It is also described that the "payment system" stores data showing the details of this transaction upon payment (step Qm).
[0054] Furthermore, when implementing a coupon service, for example, the payment system may issue coupons that offer discounts or reductions based on the purchased goods or the amount of the payment, and store the number of coupons issued on a daily basis. In addition, for example, the payment system may apply discounts or reductions to the price of goods based on the coupons presented during the payment process, and store the number of coupons used on a daily basis.
[0055] Furthermore, when implementing a points service, for example, the payment system identifies the member number of the "customer" represented in the photographic data by comparing the photographic data received in step Qf with the facial image of each member that has been registered in advance. The payment system then accumulates and stores the points issued according to the purchase amount, associating them with the identified member number.
[0056] The business process flow described above is saved, for example, in JSON format. However, the business process flow is not limited to JSON; it may also be saved in other data formats such as XML.
[0057] Returning to Figure 3, the service definition DB263 is a table or database for storing and managing definition data that contains specifications related to the effectiveness verification of the service defined in service node E. Here, effectiveness verification means verifying the effect that the service has had on verification items such as sales. Note that the definition data is an example of configuration information.
[0058] Figure 8 shows an example of the data structure of the service definition DB263. As shown in Figure 8, the service definition DB263 stores the target service, the validation item ID, the item name, and the data file in association.
[0059] The "Target Service" field registers information that identifies the target service. For example, the "Target Service" field may register the node ID of service node E, the tree ID of the KPI tree to which service node E belongs, etc. The "Verification Item ID" and "Item Name" fields indicate the ID and item name of the verification item related to the effectiveness verification. The "Data File" field registers the actual definition data in which the specifications related to the effectiveness verification of the verification item are defined (hereinafter also referred to as "settings"), or an address indicating the storage location of said definition data, etc.
[0060] In this embodiment, the KPI tree and business flow may be pre-created, or they may be created via the terminal device 10 or the like with assistance from the server device 20. In the latter case, for example, the server device 20 provides the terminal device 10 with a screen (GUI (Graphical User Interface)) to assist in viewing, creating, and editing the KPI tree and business flow.
[0061] Specifically, the server device 20 provides the terminal device 10 with a screen that allows creation and editing of various nodes and the relationships between nodes in a visualized state. Then, once the creation or editing of the KPI tree is complete, the server device 20 stores the KPI tree in the KPI tree DB 261.
[0062] Furthermore, when any service node E included in the KPI tree is selected, the server device 20 provides a screen that allows the creation (editing) of business flows and definition data for the service corresponding to that service node E. Then, when either a business flow or definition data is created, the server device 20 stores it in the corresponding database, associating it with the node ID and tree ID of the service node E.
[0063] Returning to Figure 3, the communication unit 27 is a communication interface that can connect to the network N. The communication unit 27 communicates with external devices such as the terminal device 10 via the network N.
[0064] Next, the functional configurations of the terminal device 10 and the server device 20 will be described with reference to Figure 9. Figure 9 is a diagram showing an example of the functional configurations of the terminal device 10 and the server device 20.
[0065] As shown in Figure 9, the terminal device 10 includes a display control unit 111 and an operation reception unit 112 as functional units.
[0066] Some or all of the functional components of the terminal device 10 may be implemented as software through the cooperation of the terminal device 10's processor (e.g., CPU 11) and a program stored in its memory (e.g., ROM 12, storage unit 16). Alternatively, some or all of the functional components of the terminal device 10 may be implemented as hardware through dedicated circuits or the like mounted on the terminal device 10.
[0067] 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 by the server device 20.
[0068] The operation reception unit 112 of the terminal device 10 receives user operations via the operation unit 15. For example, when the operation reception unit 112 receives an operation on the screen displayed on the display unit 14, it notifies the server device 20 of the details of that operation.
[0069] On the other hand, the server device 20 includes a GUI provisioning unit 211, a design support unit 212, a display control unit 213, and an operation reception unit 214 as functional units.
[0070] Some or all of the functional components of the server device 20 may be implemented as software through the cooperation of the server device 20's processor (e.g., CPU 21) and a program stored in its memory (e.g., ROM 22, storage unit 26). Alternatively, some or all of the functional components of the server device 20 may be implemented as hardware through dedicated circuits or the like mounted on the server device 20.
[0071] The GUI provider unit 211, in cooperation with other functional units, provides the terminal device 10 with information that enables the display of various operation screens (hereinafter also simply referred to as "screens"). Here, the GUI provider unit 211 may provide data representing a screen, or it may provide various content data related to the display of a screen. Hereinafter, the provision of information related to the display of a screen by the GUI provider unit 211 to the terminal device 10 will be referred to as "providing" a screen or "displaying" a screen.
[0072] The design support unit 212 is an example of a first receiving means, an identification means, a provisioning means, a second receiving means, an editing means, a generation means, and a storage means. The design support unit 212 works in cooperation with the GUI provisioning unit 211 to provide screens to support the creation of KPI trees and business flows, and the setting of specifications for service effectiveness verification.
[0073] For example, the design support unit 212 provides a screen that allows the creation of a KPI tree by arranging various nodes, edges, etc., as drawing parts. Here, the design support unit 212 displays the visualized KPI tree in response to user operations. The design support unit 212 can also associate a business flow (flow ID) with the service node E of the KPI tree in response to user operations. When the design support unit 212 receives confirmation that the creation or editing of the KPI tree is complete, it generates a data file representing the KPI tree and stores it in the KPI tree DB 261.
[0074] Furthermore, the design support unit 212 provides a screen that allows the user to select a KPI tree to be viewed or edited based on the KPI tree DB 261. When a KPI tree is selected, the design support unit 212 reads that KPI tree from the KPI tree DB 261 and provides a screen that visualizes the KPI tree.
[0075] Furthermore, the design support unit 212 provides a screen that allows the creation of a business flow by arranging drawing parts and the like that correspond to the BPMN notation rules. Here, the design support unit 212 displays a visualized business flow in response to user operations. When the design support unit 212 receives confirmation that the business flow has been created or edited, it generates a data file representing the business flow and stores it in the business flow DB 262, associating it with the target service.
[0076] Furthermore, the design support unit 212, in cooperation with the GUI provision unit 211, provides a screen that allows for the setting and confirmation of specifications related to the effectiveness verification of the service. For example, when the design support unit 212 receives a selection of a target service from among the services registered in the KPI tree in response to a user's operation, it provides a screen that allows for the setting and confirmation of specifications related to the effectiveness verification of the selected service.
[0077] Specifically, when the design support unit 212 receives a selection operation for service node E registered in the KPI tree, it displays a screen showing the verification items related to effectiveness verification for the selected service node E. For example, when service node Ea (service A) is selected from the KPI tree shown in Figure 5, the design support unit 212 displays a screen showing the verification items for effectiveness verification for the selected service A.
[0078] Here, Figure 10 shows an example of a screen provided by the design support unit 212. As shown in Figure 10, the settings screen 30 has tabs TA to TD and a display area 31. Tabs TA to TD indicate the type of settings related to the selected service node E (service A).
[0079] The tab TA corresponding to "BPMN" is an operator used to set up (create) and check business workflows. When tab TA is selected, for example, the design support unit 212 displays a screen (for example, Figure 7) in the display area 31 that allows the creation and viewing of business workflows, with drawing parts and other elements corresponding to the BPMN notation rules placed on it.
[0080] The tab TB corresponding to "Cost Modeling" is an operator for setting and confirming the costs related to the service implementation of the selected service node E. When tab TB is selected, for example, the design support unit 212 displays a screen (not shown) in the display area 31 on which the costs related to service implementation can be set and viewed. On this screen, for example, it is possible to set the costs required at the time of introduction and the costs required during operation after implementation for elements registered in the business flow (e.g., surveillance cameras, payment systems, etc.).
[0081] Tab TC, which corresponds to "Serviceability Check," is an operator for setting and confirming the requirements for the service implementation of the selected service node E. When tab TB is selected, for example, the design support unit 212 displays a screen (not shown) in the display area 31 on which check items for checking the requirements for service implementation can be set and viewed.
[0082] The tab TD corresponding to "KPI" is an operator used to edit and confirm the verification items related to the effectiveness verification of the selected service node E. Figure 10 shows the state when tab TD is selected, and a screen displaying a list of verification items (hereinafter also referred to as the verification item screen) is displayed in the display area 31.
[0083] As shown in Figure 10, the verification item screen has an item list 311 and an item addition button 312. The item list 311 has an "ID", "item name", and "definition", and each verification item to be defined is displayed in a list. The "ID" is an ID used to identify each verification item. The "item name" displays the name of each verification item. The "definition" displays information indicating whether it is defined or undefined.
[0084] Here, the design support unit 212 extracts verification items related to the selected service node E from the KPI tree and displays the extracted verification items in the item list 311. For example, the design support unit 212 extracts verification items related to the effectiveness verification of the service of service node E based on the target content of the target nodes related to service node E (final target node A and intermediate target node B) by traversing the nodes from the selected service node E toward the final target node A. Next, the design support unit 212 displays the extracted verification items in the item list 311 in order from the higher-level node.
[0085] For example, in the KPI tree in Figure 5, when service node Ea (Service A) is selected, the design support unit 212 extracts "Sales" from the final target node A, "Average Customer Spending" from the intermediate target node Bb, and "Number of Items Sold" from the intermediate target node Bc as verification items. The design support unit 212 then displays the extracted verification items in the item list 311 in order from the highest-level node (see Figure 10). Note that IDs 1 to 3 correspond to the verification items extracted from the final target node A and the intermediate target nodes Bb and Bc.
[0086] In this way, when a service node E is selected, the design support unit 212 extracts the target content of the KPI and KGI nodes related to the selected service node E as verification items. The design support unit 212 then displays the extracted verification items in the item list 311 as targets for specification setting. This allows the user to easily set and confirm specifications related to effectiveness verification for the service of the service node E selected from the KPI tree, while checking the target content of the higher-level nodes related to that service node E.
[0087] The item addition button 312 is an operator used to add a verification item. When the design support unit 212 receives an operation on the item addition button 312, it adds an ID to the item list 311 and accepts input for the verification item to be defined.
[0088] In Figure 10, ID 4, "Number of Coupons Issued," and ID 5, "Coupon Usage Rate," indicate the item names of the additional verification items. There are no specific restrictions on the item names of the additional verification items, and they can be set arbitrarily. However, candidate verification items may be suggested based on the settings of Factor Node C and Solution Node D, which are located above Service Node E.
[0089] For example, if service node Ea is selected, verification items related to "coupon issuance" set in the higher-level solution node Dc may be presented as candidates. In this case, by preparing candidate verification items in advance, for example, by associating them with key words such as "coupon," verification items corresponding to the settings of factor node C and solution node D can be presented. The design support unit 212 may also display verification items selected based on the contents of factor node C and solution node D, along with the verification items extracted from the target node, in the item list 311.
[0090] Furthermore, when a user sets specifications related to a verification item, they perform an operation to instruct the editing of the specifications for the target verification item displayed in the item list 311. For example, when an operation such as right-clicking is performed on a verification item displayed in the item list 311, the design support unit 212 displays an operation menu 313 as shown in Figure 10. Then, when "Edit" is instructed from the operation menu 313, the design support unit 212 displays a screen (hereinafter also referred to as the definition screen) on which the specifications related to the effectiveness verification of the target verification item can be edited. If "Delete" is instructed from the operation menu 313, the design support unit 212 deletes the target verification item from the item list 311.
[0091] Figure 11 shows an example of a screen provided by the design support unit 212. Figure 11 is an example of the display of the definition screen 40 for the verification item ID 5, item name "Coupon Usage Rate," which is displayed in the item list 311 of Figure 10.
[0092] As shown in Figure 11, the definition screen 40 has a definition area 41 and an image diagram area 42. The definition area 41 displays each item to be set in the specifications (hereinafter also referred to as a definition item) and an input area for defining the specifications. Definition items include, for example, "item name," "display unit," "number of decimal places of the numerical value," "definition or calculation formula of the numerical value," "whether or not it can be acquired," "aggregation period," "closing date," "aggregation unit 1," "aggregation unit 2," and "display format."
[0093] Here, "Item Name" corresponds to the item name of the verification item selected from the item list 311 on the settings screen 30, and indicates the verification content. If "Item Name" has already been set, that item name will be displayed in the input area. Note that the item name in the input area is editable, and if it is edited, the edited item name will also be reflected in the item list 311 on the settings screen 30.
[0094] The "Display Unit" defines the unit used to display the value of the "Item Name." For example, by entering a unit such as "%" in the corresponding input area, you can define the unit used to display the item corresponding to the "Item Name." Figure 11 shows an example where "%" is defined as the display unit for "Coupon Usage Rate."
[0095] The "Number of decimal places" setting defines the number of decimal places displayed when the value of the "Item Name" is shown. For example, you can define the number of decimal places to display by entering a number such as "0" in the corresponding input area. Figure 11 shows an example where the number of decimal places for "Coupon Usage Rate" is set to "0".
[0096] "Definitions and calculation formulas for numerical values" define the elements and calculation formulas used to derive the values of the "item names." Figure 11 shows an example where the number of coupons used is divided by the number of coupons issued in order to derive the "coupon usage rate."
[0097] "Availability of Acquisition" defines whether the element used to derive the value of "Item Name" is available for acquisition in the current system configuration. For example, if the element can be acquired in the current system configuration, information such as "available" is entered in the corresponding input area. Alternatively, if the element cannot be acquired in the current system configuration, information such as "development required to acquire the element" can be entered in the corresponding input area. Figure 11 shows an example where "development required" is entered to indicate that acquisition is not possible. Note that while Figure 11 shows a form in which information indicating availability of acquisition can be selectively entered, this is not the only option.
[0098] The "aggregation period" defines the aggregation period used to derive the value of the "item name," that is, the period for collecting the elements involved in the derivation. For example, the "aggregation period" can be set to a period such as daily, monthly, or yearly. Figure 11 shows an example where monthly is entered. Note that while Figure 11 shows a form in which the aggregation period can be selected, this is not the only option.
[0099] The "closing date" defines the closing date for the "aggregation period." For example, any date can be defined as the "closing date." Figure 11 shows an example where "25th" is entered as the closing date for the "monthly" period.
[0100] "Aggregation Unit 1" and "Aggregation Unit 2" define the display units for axis elements and graphs when displaying the values of "Item Name" in a graph. For example, "Aggregation Unit 1" defines the display unit for the horizontal axis of a dual-axis graph, in which case the vertical axis will be set to the value of "Item Name". Also, for example, "Aggregation Unit 2" is used to define the aggregation unit of the graph displayed in a dual-axis graph.
[0101] Figure 11 shows an example where "Aggregation Unit 1" uses each month from April 2022 to September 2022 as the aggregation unit. It also shows an example where "Aggregation Unit 2" uses each of the POS1 to POS3 devices as the aggregation unit. Here, POS1 to POS3 are, for example, three product sales data processing devices included in the payment system configured in the business flow shown in Figure 7, and it is assumed that the coupon usage rate will be displayed graphically for each product sales data processing device.
[0102] The "Display Format" setting defines the display format for the graph when displaying the values of the "Item Name." For example, you can input graph types such as bar graphs and line graphs in the "Display Format" field. Figure 11 shows an example where a line graph is entered. Note that while Figure 11 shows a form where the display format can be selected, this is not the only option.
[0103] Meanwhile, the image area 42 displays an image of a graph based on the definitions entered (set) in the definition area 41. Specifically, the design support unit 212 generates an image of a graph to represent the verification results based on the specifications of each definition item, and displays the generated image in the image area 42.
[0104] Here, the graph diagram is not a graph based on actual data, i.e., it does not show the measured value of the item name "Coupon Usage Rate," but rather a sample to confirm the style and form of the graph generated under the specifications set in definition area 41. Figure 11 shows an example of a graph diagram of the coupon usage rate, based on each specification set in definition area 41, with the vertical axis representing the "Display Unit" in % and the horizontal axis representing each month from 2022 / 04 to 2022 / 09 of "Aggregation Unit 1." In this diagram, the graphs of POS1 to POS3 defined in "Aggregation Unit 2" are represented by changing the line type.
[0105] The method for generating the image diagram is not particularly limited. For example, the design support unit 212 may generate the image diagram using pre-prepared sample data, or it may generate the image diagram using random data. Furthermore, for example, if there is a service node E defined under similar conditions in another customer's KPI tree, and actual service values exist for that service node E, the design support unit 212 may generate the image diagram using that actual data. In this case, it is preferable to perform processing such as removing outliers from the actual values. Alternatively, the design support unit 212 may generate an image diagram based on actual values by randomly setting values within the range of the maximum and minimum values of the actual values.
[0106] Furthermore, the graph types that can be entered in "Display Format" are not limited to graph types for plotting data values of item names, but may also be graphs for displaying a single point of statistical representativeness. In this case, the design support unit 212 may, for example, calculate representative values such as the mean or median from actual values of other services defined under similar conditions, and generate a graph representing the calculated representative value as an image diagram.
[0107] In this way, when various definitions are entered into the definition area 41, the design support unit 212 displays a graphical image in the image area 42 that schematically represents the verification results (aggregated results) of the verification items based on the entered definitions. This allows the user to check the display format of the definitions entered into the definition area 41 and to confirm the validity of the entered definitions by looking at the image. Therefore, the design support unit 212 can support the setting work of definitions related to the verification of the effectiveness of the services provided.
[0108] When the design support unit 212 receives an operation to instruct the completion of editing, it generates definition data in which the contents of various definition items defined in the definition area 41 are set. The design support unit 212 associates the generated definition data with the ID (verification item ID) and item name of the corresponding verification item, and stores it in the service definition DB 263, associating it with the target service of the selected service node E.
[0109] Furthermore, the design support unit 212 displays "Completed" in the "Definition" column for verification items whose definition data is stored in the service definition DB 263 among the verification items displayed in the item list 311. Also, the design support unit 212 displays "Undefined" in the "Definition" column for verification items whose definition data is not stored in the service definition DB 263 among the verification items displayed in the item list 311.
[0110] In the example above, we explained the definition screen 40 related to the verification item "coupon usage rate," but similar definition screens 40 containing the same definition items will be displayed for other verification items as well. However, it is not necessary to set all of the definition items displayed on the definition screen 40; only some of the definition items may be set. Furthermore, the definition screen 40 may have different configurable definition items depending on the characteristics of the verification item, and it may also be possible to edit the definition items by adding or deleting them.
[0111] Furthermore, when checking (viewing) the specifications of the verification items, the definition screen 40 may be used, or the definition screen 40 may be used with the specification editing disabled. In the latter case, the design support unit 212 may, for example, display an option in the operation menu 313 to instruct the user to view the specifications, and when this option is selected, display the definition screen 40 with editing disabled.
[0112] Returning to Figure 9, the display control unit 213 of the server device 20 controls the display unit 24 to display various screens on the display unit 24. For example, the display control unit 213 displays various screens provided by the GUI provider unit 211 on the display unit 24.
[0113] The operation reception unit 214 of the server device 20 receives user operations via the operation unit 25. For example, when the operation reception unit 214 receives an operation on one of the various operation support screens displayed on the display unit 24, it outputs the details of that operation to the CPU 21.
[0114] The following describes an example of the operation of the server device 20 described above. Figure 12 is a flowchart showing an example of the processing performed by the server device 20. In this processing, the server device 20 described above has a function for setting specifications related to service effectiveness verification. explain.
[0115] First, the design support unit 212 accepts the selection of the KPI tree to be displayed from the KPI tree DB 261 (step S11). Next, the design support unit 212 visualizes and displays the selected KPI tree (step S12).
[0116] Next, the design support unit 212 accepts the selection of the service node E to be configured from the displayed KPI tree (step S13). Once a service node E is selected, the design support unit 212 determines whether or not the definition data related to the selected service node E exists in the service definition DB 263 (step S14).
[0117] If definition data exists in the service definition DB263 (step S14; Yes), the design support unit 212 reads the definition data from the service definition DB263 (step S15) and displays the verification items set in the definition data on the verification item screen (step S17).
[0118] Furthermore, if the definition data does not exist in the service definition DB263 (step S14; No), the design support unit 212 identifies the target nodes related to service node E (final target node A, intermediate target node B) by traversing from the selected service node E to the final target node A. Then, the design support unit 212 extracts verification items based on the target content of the identified target nodes (step S16). Next, the design support unit 212 displays a verification item screen representing the extracted verification items (step S17).
[0119] Next, the design support unit 212 determines whether or not an editing operation (addition, deletion, renaming, etc.) has been performed on the verification items (step S18). If an editing operation has been performed on the verification items (step S18; Yes), the design support unit 212 adds or deletes verification items according to the edited content (step S19) and proceeds to step S20. If no editing operation has been performed on the verification items (step S18; No), the process also proceeds to step S20. The design support unit 212 may also store or update the definition data at the timing of step S15 or S19.
[0120] In the following step S20, the design support unit 212 determines whether any verification item has been selected for editing or confirming the specifications (step S20). If a verification item has been selected (step S20; Yes), the design support unit 212 displays a definition screen 40 in which the specifications related to the effectiveness verification can be set for the selected verification item (step S21). If definition data for the verification item that has been instructed to be edited (or viewed) exists in the service definition DB 263, the design support unit 212 displays the specifications set in the definition data on the definition screen 40.
[0121] Here, the user can edit the specifications of each definition item (new input, modification, deletion, etc.) by operating the definition screen 40. The design support unit 212 generates an image diagram that schematically represents the verification results related to the effectiveness verification of the verification items based on the specifications set for each definition item, and displays this image on the definition screen 40.
[0122] Next, the design support unit 212 determines whether or not the operation of the definition screen 40 has been instructed to end (step S22). If the operation of the definition screen 40 has not been instructed to end (step S22; No), the design support unit 212 continues to display the definition screen 40 by proceeding to step S21.
[0123] If the user is instructed to finish operations on the definition screen 40 (step S22; Yes), the design support unit 212 determines whether or not the specifications of the definition items have been edited (step S23). If no editing has been done (step S23; No), the design support unit 212 proceeds to step S17 and displays the verification items screen. If the specifications have been edited (step S23; Yes), the design support unit 212 stores the edited specifications in the definition data (step S24), then proceeds to step S17 and displays the verification items screen.
[0124] Furthermore, if it is determined in step S20 that editing (or viewing) the specifications is not instructed (step S20; No), the design support unit 212 determines whether or not the operation on the verification item screen has been terminated (step S25).
[0125] If the user is not instructed to end operations on the verification item screen (step S25; No), the design support unit 212 continues to display the verification item screen by proceeding to step S17. On the other hand, if the user is instructed to end operations on the verification item screen (step S25; Yes), the design support unit 212 terminates this process.
[0126] In this process, definition data is stored (or updated) each time a specification setting for a verification item is performed, but this is not limited to this. For example, the design support unit 212 may store the definition data related to the verification item for which the specification editing operation was performed all at once when the operation on the verification item screen is instructed to end.
[0127] As described above, when a service node E is selected from the KPI tree, the server device 20 of this embodiment extracts verification items related to service effectiveness verification based on the target content of the target node related to the service node E. The server device 20 then provides the user with a screen in which they can set the specifications related to effectiveness verification for the extracted verification items.
[0128] This allows the server device 20 to perform the specification setting work related to effectiveness verification while making the user aware of and confirming the target content of the higher-level target node that should serve as a benchmark for the service of the service node E that is the target of the configuration. Therefore, the server device 20 can support the specification setting work related to the effectiveness verification of the service.
[0129] Furthermore, the server device 20 stores the configured specifications in association with the service node E and the verification items, and when the service node E is selected, it provides the user with a screen displaying the specifications set for the verification items. This allows the server device 20 to share the definition of the specifications related to the verification of the service's effectiveness among all parties involved in the design.
[0130] Furthermore, the server device 20 accepts the selection of a service to be configured or viewed based on the selection operation of the service node E set in the KPI tree. This allows the server device 20 to improve user convenience regarding service selection.
[0131] The embodiments described above can also be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above. Therefore, several modifications of the embodiments described above will be described below as other embodiments. In the following, we will mainly describe the differences from the embodiments described above, and will omit detailed explanations of points that are common with what has already been described. Furthermore, the modifications described below may be implemented individually or in combination as appropriate.
[0132] (Variation 1) In the above embodiment, an example was shown in which the terminal device 10 and the server device 20 cooperate to display various screens provided by the server device 20 on the terminal device 10. However, the embodiment is not limited to this, and the terminal device 10 may also display the information on its own.
[0133] In this case, the terminal device 10 can display various screens related to editing and confirming definitions for verifying the effectiveness of the service node E, for example, by including functional units such as the GUI provision unit 211 and the design support unit 212 described above. The terminal device 10 is assumed to be in a state where it can read and write to various databases held by the server device 20.
[0134] In this case, some or all of the KPI tree DB261, business flow DB262, and service definition DB263 may be held by the terminal device 10, or by another device (or cloud) that the terminal device 10 can access.
[0135] (Modification 2) In the embodiment described above, the server device 20 stores and manages the business flow in association with the service node E of the KPI tree. However, it is not limited to this configuration, and the business flow may be stored and managed independently without being associated with the service node E.
[0136] The programs executed in each of the above-described embodiments are provided pre-installed in ROM, storage units, etc. Alternatively, the programs executed in each of the above-described embodiments may be provided as installable or executable files recorded on a computer-readable recording medium such as a CD-ROM, flexible disk (FD), CD-R, or DVD (Digital Versatile Disk).
[0137] Furthermore, the programs executed by each of 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. Alternatively, the programs executed by each of the above-described embodiments may be provided or distributed via a network such as the Internet.
[0138] Although 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 variations can be implemented in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. [Explanation of Symbols]
[0139] 1. Business support system 10 Terminal devices 20 Server Devices 111 Display Control Unit 112 Operation Reception Unit 211 GUI provision department 212 Design Support Department 213 Display Control Unit 214 Operation Reception Section 261 KPI Tree DB 262 Business Flow Database 263 Service Definition DB [Prior art documents] [Patent Documents]
[0140] [Patent Document 1] Japanese Patent Publication No. 2014-235470
Claims
1. A first receiving means accepts a service node selection operation based on tree data in which the relationship between target nodes, which indicate management objectives, and service nodes, which indicate the service content to achieve those objectives, is set in a stepwise tree structure. An extraction means for extracting items related to the target content set for each of the target nodes from the tree data to which the selected service node belongs, from the target nodes that exist between the selected service node and the root node, as verification items for verifying the effectiveness of the service content, A providing means that provides a screen on which it is possible to set specifications related to the effectiveness verification of each of the verification items extracted by the extraction means, An information processing device equipped with the following features.
2. A second receiving means for receiving editing operations for the aforementioned verification items, An editing means that adds or deletes the verification items in response to the editing operation received by the second receiving means, The information processing apparatus according to claim 1, further comprising:
3. The system further comprises a generation means for generating an image diagram that schematically represents the verification results related to the effectiveness verification of the verification items, based on the specifications set based on the aforementioned screen. The providing means provides the image diagram generated by the generating means by including it on the screen. The information processing apparatus according to claim 1 or 2.
4. The system further includes a storage means for storing the specifications set based on the aforementioned screen as configuration information, associated with the selected service node and the verification item. The information processing apparatus according to claim 1.
5. The providing means, if the configuration information is stored in association with the selected service node, provides a screen representing the specifications set for the verification item based on the configuration information. The information processing apparatus according to claim 4.
6. The computer of the information processing device, A first receiving means accepts a service node selection operation based on tree data in which the relationship between target nodes, which indicate management objectives, and service nodes, which indicate the service content to achieve those objectives, is set in a stepwise tree structure. An extraction means for extracting items related to the target content set for each of the target nodes from the tree data to which the selected service node belongs, from the target nodes that exist between the selected service node and the root node, as verification items for verifying the effectiveness of the service content, A providing means that provides a screen on which it is possible to set specifications related to the effectiveness verification of each of the verification items extracted by the extraction means, A program to make it work.