Business support device and program

Abstract

To provide a work support apparatus and program allowing for work support based on a workflow.SOLUTION: A work support apparatus includes: extraction means which extracts each of elements related to execution of a work, from a workflow including the elements and contents to be executed by the elements, which are described as a series of procedures; read means which reads, from a storage unit which stores additional information related to the elements in association with each type of the elements, the additional information related to the elements extracted by the extraction means; and output means which outputs the additional information related to the elements read by the read means.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to a business support device and a program. [Background technology]

[0002] Various services are provided at stores and other locations. In these locations, methods such as BPMN (Business Process Model and Notation) are often used to create workflows that describe the processing procedures for each element involved in providing the service. For example, technologies have been proposed that can automatically create workflows that ensure continuity between input and output relationships between adjacent tasks.

[0003] By using the above-mentioned business flow, it is possible to check the processing procedures of each element and the relationships between elements. However, there are limits to what can be checked from the business flow, and there is room for further improvement from the perspective of business support. For example, it is difficult to check additional items such as requirements and costs for the elements described in the business flow based on the business flow. Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a business support device and a program that are capable of providing business support based on a business flow. [Means for solving the problem]

[0005] The business support device of the embodiment includes an extracting means, a reading means, and an output means. The extracting means extracts each of the elements from a business flow in which each element related to the performance of a business and the execution contents executed by the element are described as a series of procedures. The reading means extracts each of the elements from the business flow in which each element related to the performance of a business and the execution contents executed by the element are described as a series of procedures. everyThe additional information about the element extracted by the extraction means is read from a storage unit that stores the additional information about the element in association with the additional information about the element. The output means outputs the additional information about the element read by the read means. In addition, the storage unit stores a checklist in which confirmation items related to the element are set as the additional information, and the output means outputs the checklist related to the element extracted by the extraction means in association with the element. [Brief explanation of the drawings]

[0006] [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 a data configuration of the business flow DB according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a visualized business flow according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a data configuration of the checklist DB according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a data configuration of the cost DB according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the data configuration of the confirmation result DB according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the functional configuration of the terminal device and the server device according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a creation support screen according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a check screen according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of a quote screen according to the embodiment. [Figure 13] FIG. 13 is a flowchart illustrating an example of a process for creating a checklist executed by the server device according to the embodiment. [Figure 14]FIG. 14 is a flowchart illustrating an example of a process related to checking a business flow executed by the server device according to the embodiment. [Figure 15] FIG. 15 is a flowchart illustrating an example of a process related to business flow estimation executed by the server device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0008] Fig. 1 is a diagram showing an example of the configuration of a business support system according to an 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).

[0009] The terminal device 10 is a terminal device used by a user of the business support system 1. The terminal device 10 executes various processes in response to user operations. For example, the terminal device 10 cooperates with the server device 20 to support the creation of business flows and checklists, which will be described later, and to display business flows and checklists. The terminal device 10 can be realized by, for example, a stationary information processing device such as a PC (Personal Computer), or a portable information processing device such as a notebook PC, tablet terminal, or smartphone.

[0010] The server device 20 is an example of a business support device. The server device 20 supports the creation and viewing of business flows. The server device 20 also provides the user with additional information related to elements described in the business flows.

[0011] Specifically, the server device 20 provides the terminal device 10 with a GUI (Graphical User Interface) for creating a business flow and creating or executing a checklist, which will be described later. The server device 20 also stores and manages checklists and cost information related to the business flow as additional information, and provides the additional information to the terminal device 10 according to the business flow selected by the user of the terminal device 10.

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

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

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

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

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

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

[0018] 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 an application program such as a web browser that can access the server device 20 and display and operate various operation support screens provided by the server device 20.

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

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

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

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

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

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

[0025] The storage unit 26 is an example of a storage device. The storage unit 26 is configured with a storage medium such as a HDD or flash memory, and retains 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 and the like. The CPU 21 executes various processes by operating in accordance with programs stored in the ROM 22 or the storage unit 26 and loaded into the RAM 23.

[0026] The storage unit 26 also stores a business flow DB 261, a checklist DB 262, a cost DB 263, and a confirmation result DB 264.

[0027] The business flow DB 261 is a database for storing and managing business flows. Here, a business flow is a data file in which each element related to the performance of a business and the execution content executed by that element are described as a series of procedures. For example, a business flow describes, for each element related to the business of a store, the execution content and procedure executed by that element.

[0028] Fig. 4 is a diagram showing an example of the data configuration of the business flow DB 261. As shown in Fig. 4, the business flow DB 261 stores business flow names, data files, etc. in association with flow IDs. Here, a flow ID is an identifier assigned to uniquely identify each business flow.

[0029] The business flow name stores a name that identifies the business flow. The data file stores the business flow data file or the address that indicates where the data file is stored. Business flows are created using techniques such as flowcharts or BPMN (Business Process Modeling Notation), and can be visualized as shown in Figure 5.

[0030] Fig. 5 is a diagram showing an example of a visualized business flow. Fig. 5 shows an example of a business flow related to "payment business" stored in the business flow DB 261 of Fig. 4.

[0031] As shown in Figure 5, in a business flow, between a start event ST and an end event EN, a series of operations (or processes) related to the execution of a payment transaction are described for each element that performs the operation. The business flow in Figure 5 shows an example in which the elements described are a "customer" who visits a store, a "surveillance camera" and a "payment system" installed in the store, and a "store clerk" who works in the store. Note that there is no particular restriction on what can be described as an element. For example, a business flow may exclude human elements.

[0032] The business flow in Figure 5 first describes the flow of a "customer" entering a store (Step Qa), selecting a product to purchase (Step Qb), and proceeding to the cash register (Step Qc). The flow of a "surveillance camera" installed in the store is described as taking a picture of the "customer" approaching the cash register (Step Qd) and transmitting the captured image data to a payment system installed in the store (Step Qe). The flow of the "payment system" is described as receiving the captured image data from the "surveillance camera" (Step Qf) and displaying customer information, such as the "customer's" attributes, derived from the captured image data on a display device such as a cash register (Step Qg).

[0033] Also, the flow of the "clerk" operating the cash register is described as checking the customer information displayed by the "payment system" (step Qh) and performing the cash register operation for the items brought in by the "customer" (step Qi). Also, it is described that the "payment system" executes "payment processing" (step Qj) in conjunction with the cash register operation of the "clerk".

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

[0035] The above-described business flow is saved in, for example, XML format. Note that the format for saving the business flow does not necessarily have to be XML, and it may be saved in another structured format such as JSON format.

[0036] 3, the checklist DB 262 is a database for storing and managing checklists for checking business flows. Note that checklists are an example of additional information.

[0037] Fig. 6 is a diagram showing an example of the data configuration of the checklist DB 262. As shown in Fig. 6, the checklist DB 262 stores information related to items such as target, classification, checklist name, and default flag.

[0038] Here, an identifier indicating the element to be checked by this checklist is registered in the target item. Specifically, the names of the hardware or software elements described in the business flow are registered. For example, in the case of the business flow described in Figure 5, "surveillance cameras" and "payment system" are registered as target items. Note that the target of the check is not limited to individual elements described in the business flow, but the entire business flow may also be the target of the check. Figure 6 shows an example in which "common" is registered as the identifier for checking the business flow. A checklist with a target of "common" is applied to all business flows, regardless of the content of the business flow.

[0039] The classification item registers information indicating the classification of the check target element registered in the target item. For example, if the target is a "surveillance camera," hardware (HW) is registered as the classification. Also, if the target is a "payment system," software (SW) is registered as the classification. For "common" targets, the classification is "entire service," which indicates that the target applies to the entire business flow.

[0040] The checklist name field contains the identifier of the checklist. The identifier may be, for example, the data name of the checklist or an address indicating the storage location of the checklist. A checklist is created in advance for each target, and one or more check items (confirmation items) are set according to the target. It is also preferable that the check items in the checklist include check items for non-functional requirements. Here, "non-functional requirements" refer to requirements other than the function of the target element, and include, for example, requirements such as the target's performance, availability, and security.

[0041] The number of checklists registered for one object is not limited to one, and multiple checklists may be registered, for example, as in the case of "surveillance camera" in Fig. 5. In this case, for example, as will be described later, a customized edited checklist created by editing a template checklist can be registered in association with the same object as the unedited checklist.

[0042] The default flag is flag information for setting the checklist to be displayed by default on the checklist editing screen or confirmation screen described below. For example, the flag information is binary information representing on or off, and is controlled so that the checklist set to on is displayed by default. In Figure 6, "1" indicates the on state and "0" indicates the off state, and the checklist set to "1" is displayed by default.

[0043] It is preferable to exclusively control the default flag to be in the ON state so that it is set in a maximum of one checklist among the checklists associated with the same object. Also, when one checklist is registered for one object, the checklist in question may be configured to be treated as in the ON state.

[0044] It should be noted that the checklist DB 262 is not limited to the data configuration shown in Fig. 6. For example, the checklist DB 262 may store, in association with a checklist registered in a list name, the user ID of the user who created (or edited) the checklist and date and time information indicating the date and time of creation (or editing).

[0045] The cost DB 263 is a database for storing and managing cost information indicating the cost required for introducing or operating each element described in the business flow. Note that the cost information is an example of additional information.

[0046] Fig. 7 is a diagram showing an example of the data configuration of the cost DB 263. As shown in Fig. 7, the cost DB 263 stores information relating to items such as target, classification, cost, and unit.

[0047] Here, the target item is registered with an identifier indicating the element for which the cost is to be calculated. Specifically, the target item is registered with the names of elements described in the business flow, as in the checklist DB 262. Note that FIG. 7 shows an example in which the "surveillance camera" and "payment system" described in the business flow of FIG. 5 are registered as targets.

[0048] The classification item is registered with information indicating the classification of the calculation target registered in the target item. Figure 7 shows an example where hardware (HW) is registered as a classification for the target "surveillance camera." Also, it shows an example where software (SW) is registered as a classification for the target "payment system."

[0049] The cost and unit fields correspond to cost information. The cost and unit fields register information indicating the cost required to install or operate the element registered in the target field and the unit of the cost. Figure 7 illustrates an example in which the installation of the target "surveillance camera" costs 6,000 yen, and the maintenance cost of the target "payment system" costs 7,000 yen per month. Figure 7 also illustrates an example in which the installation of the target "PC," which is classified as hardware, costs 300,000 yen. Here, the target "PC" is, for example, the hardware configuration required to realize the "payment system." The cost required to install the target "PC" may be configured to be included when calculating the cost of the "payment system." Hereinafter, calculating costs is also referred to as "estimation."

[0050] It should be noted that the cost DB 263 is not limited to the data configuration shown in Fig. 7. For example, the cost DB 263 may store, in association with the target or cost, the user ID of the user who input (or updated) the cost, or date and time information indicating the date and time of input (or update).

[0051] The check result DB 264 is a database for storing and managing the check results of the above-mentioned checklist and the cost calculation results in association with the business flow.

[0052] Fig. 8 is a diagram showing an example of the data configuration of the check result DB 264. As shown in Fig. 8, the check result DB 264 stores checklist names, check results, estimate results, etc. in association with flow IDs. Here, the flow IDs are identifiers assigned to uniquely identify each business flow, and correspond to the flow IDs in the business flow DB 261.

[0053] The checklist name field stores the identifier of the checklist used to check the workflow. This identifier corresponds to the checklist name in the checklist DB 262. The check result field stores information indicating the check results performed on each check item included in the checklist with the checklist name. The check result may be, for example, the file name of the check result data file, or the address indicating the storage location of the check result data file.

[0054] The calculation result field contains information indicating the cost calculation results for the business flow. Specifically, the calculation result field contains the cost calculation results for the elements included in the business flow of the flow ID.

[0055] It should be noted that the check result DB 264 is not limited to the data configuration of Fig. 8. For example, the check result DB 264 may store, in association with the check result, the user ID of the user who performed the check and date and time information indicating the date and time when the check was performed. Furthermore, the check result DB 264 may store, in association with the calculation result, the user ID of the user who calculated the cost and date and time information indicating the date and time when the cost was calculated.

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

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

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

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

[0060] 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 causes the display unit 14 to display various operation support screens provided by the server device 20.

[0061] 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 the operation assistance screen displayed on the display unit 14, the operation accepting unit 112 notifies the server device 20 of the content of the operation.

[0062] On the other hand, as shown in FIG. 9, the server device 20 has, as functional units, a GUI providing unit 211, a business flow creation support unit 212, a checklist creation support unit 213, a check support unit 214, a cost calculation unit 215, a display control unit 216, and an operation reception unit 217.

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

[0064] The GUI providing unit 211 of the server device 20 is an example of an output means. The GUI providing unit 211 provides (outputs) various operation assistance screens so that they can be displayed. Here, the operation assistance screens may be image data representing the operation assistance screens, or various content data for displaying the operation assistance screens at the destination.

[0065] For example, the GUI providing unit 211 provides an operation support screen related to the creation of a checklist or a check operation using the checklist to the terminal device 10 that has accessed the server device 20. Also, for example, when the server device 20 creates a checklist or performs a check operation on its own device, the server device 20 provides various operation support screens to the display control unit 216. Note that in this embodiment, a form will be described in which the server device 20 provides various operation support screens to the terminal device 10.

[0066] The business flow creation support unit 212 of the server device 20 cooperates with the GUI providing unit 211 to provide an operation support screen for supporting the creation (or editing) and viewing of a business flow.

[0067] For example, the workflow creation support unit 212 provides an operation support screen on which drawing parts and the like corresponding to the notation rules of BPMN are arranged. Furthermore, when the workflow creation support unit 212 receives an operation to create a workflow via the operation support screen, it creates a data file representing the workflow according to the operation content and stores it in the workflow DB 261.

[0068] Furthermore, when a business flow to be displayed or edited is specified from among the business flows stored in the business flow DB 261, the business flow creation support unit 212 reads out the specified business flow and displays the flow diagram of the business flow in a visualized state.

[0069] The method for selecting a workflow is not particularly limited. For example, the flow names of the workflows stored in the workflow DB 261 may be displayed as a list, and a workflow may be selected from the displayed list. Alternatively, for example, the flow diagrams represented by the workflows stored in the workflow DB 261 may be displayed as a list using thumbnails, and a workflow may be selected from the displayed list.

[0070] The checklist creation support unit 213 of the server device 20 cooperates with the GUI providing unit 211 to provide an operation support screen (hereinafter also referred to as a creation support screen) for supporting the creation (or editing) of a checklist.

[0071] For example, the checklist creation support unit 213 provides a creation support screen on which various check items related to non-functional requirements can be set. Furthermore, when the checklist creation support unit 213 receives an operation to set a check item via the creation support screen, it creates (generates) a checklist including the set check items.

[0072] Here, Fig. 10 is a diagram showing an example of the creation support screen 30. As shown in Fig. 10, the creation support screen 30 has a first input area 31 for inputting basic information and a second input area 32 in which various check items can be input.

[0073] The first input area 31 has areas 311 to 313 for inputting the list name, category, and target of the checklist to be created. Here, the input list name, category, and target correspond to the list name, category, and target items in the checklist DB 262 described above. Note that the category and target may be configured to be selectable from preset candidates. In this case, the target candidates may be extracted from the business flow elements stored in the business flow DB 261.

[0074] The second input area 32 is provided with an area 321 where check items can be input. Any character string can be input into the area 321. The user sets the check items by inputting into the area 321, for example, a character string representing a check item for confirming a non-functional requirement for the target element input into the area 313.

[0075] It is preferable that the second input area 32 be divided according to, for example, the category of non-functional requirements. Fig. 10 shows an example in which the second input area 32 is divided into operation-related and maintenance-related categories. However, the division method of the second input area 32 is not limited to the example of Fig. 10.

[0076] After information is input into the first input area 31 and the second input area 32, when the checklist creation support unit 213 receives an operation instructing registration, the checklist creation support unit 213 generates a checklist based on the input information and registers it in the checklist DB 262. Specifically, the checklist creation support unit 213 generates a checklist that includes, as check items, the content input into area 321 of the second input area 32. Furthermore, the checklist creation support unit 213 associates the generated checklist with the list name, category, and target input into the first input area 31, and newly registers it in the checklist DB 262.

[0077] Furthermore, the checklist creation support unit 213 is not limited to the registration of new checklists, but can also support the editing of existing checklists.

[0078] For example, when a user instructs the checklist to be edited, the checklist creation support unit 213 provides a selection screen for selecting a checklist to be edited based on the checklists registered in the checklist DB 262. Note that the method for selecting a checklist to be edited is not limited to the above example. For example, a configuration may be adopted in which an operator that can select the checklist as the checklist to be edited is provided on a checklist execution screen described later, and when the operator is operated, the checklist displayed on the execution screen is selected as the checklist to be edited.

[0079] When a checklist to be edited is selected, the checklist creation support unit 213 reads out the selected checklist and displays the list name, category, and target set in the checklist in the first input area 31, and also displays each check item set in the checklist in an editable state in the second input area 32. In this case, the user can edit the check items (for example, correct character strings, add or delete check items) via the creation support screen 30. Then, after the check items have been edited, the checklist creation support unit 213 receives an operation to instruct registration, and updates the corresponding checklist stored in the checklist DB 262 based on the information input in the second input area 32.

[0080] In this way, on the creation support screen 30, a checklist including check items such as non-functional requirements can be arbitrarily created for the elements described in the business flow.

[0081] The checklist may be stored in advance in the checklist DB 262. For example, the checklist DB 262 may store in advance a checklist (template list) that includes check items to be checked as templates for each type of object.

[0082] Furthermore, in the above example, the first input area 31 is not editable, but the first input area 31 may be displayed in an editable state together with the second input area 32. In this case, when the first input area 31 is edited, the checklist creation support unit 213 registers the edited first input area 31 as a new checklist in the checklist DB 262 based on the edited first input area 31. This allows the user to easily create a checklist with customized check items based on a template list.

[0083] 9, the check support unit 214 of the server device 20 is an example of an extracting means and a reading means. The check support unit 214 provides an operation support screen (hereinafter also referred to as a check screen) for supporting the check of the business flow by working together with the GUI providing unit 211. In other words, the check support unit 214 also functions as an example of an output means.

[0084] For example, when a business flow to be checked is selected from the business flows stored in the business flow DB 261, the check support unit 214 provides a check screen for checking the business flow.

[0085] Specifically, the check support unit 214 extracts each of the elements described in the business flow to be checked from the business flow. The check support unit 214 also reads out checklists related to each of the extracted elements from the checklist DB 262.

[0086] More specifically, the check support unit 214 reads out checklists for which the default flag is set to ON from among the checklists for which the extracted element is set as the target. Furthermore, if there is a checklist for which the target is set to "common," the check support unit 214 reads out checklists for which the default flag is set to ON from among those checklists.

[0087] Then, the check support unit 214 generates a check screen for checking the business flow to be checked based on the checklist read out from the checklist DB 262.

[0088] Here, Fig. 11 is a diagram showing an example of the check screen. As shown in Fig. 11, the check screen 40 allows the contents to be displayed to be switched using tabs TA to TC.

[0089] Specifically, the check support unit 214 generates a tab for each checklist read from the checklist DB 262, and generates a check screen that can be switched using the tab. The screen that is displayed by switching the tab displays the check items of the checklist that corresponds to the tab. In other words, the checklist can be switched by switching the tab.

[0090] 11, the tab TA corresponds to the checklist whose target is "common," the tab TB corresponds to the checklist whose target is "surveillance cameras," and the tab TC corresponds to the checklist whose target is "payment services." In other words, the checklists are output in association with the corresponding elements.

[0091] 11 shows the state in which the tab TA is selected, and the check items set for each of the operation-related and maintenance-related items are displayed. Each check item is associated with four options: "Not done," "Pending," "OK," and "NG," and the system is configured so that one of the options can be selected.

[0092] This allows the user to check each check item, including non-functional requirements, for the target selected using tabs TA to TC by selecting the appropriate option while checking the contents of the check item.

[0093] In Fig. 11, there are four options for the check items, but the number and types of options are not limited to this. Also, answers to the check items may be entered as characters. In either case, it is possible to set the answer method for the check items at the checklist creation stage.

[0094] The check screen 40 also has a change button 41. The change button 41 is an operator for instructing a change to the checklist. When the check support unit 214 receives an operation of the change button 41, it executes a process for changing the checklist displayed on the check screen 40.

[0095] Specifically, when the check support unit 214 receives an operation of the change button 41, it identifies the target (element) of the tab selected at the time the operation is received. The check support unit 214 displays a selection screen from which a checklist related to the identified target can be selected from among the checklists stored in the checklist DB 262. At this time, the check support unit 214 may display the remaining checklists on the selection screen, excluding the checklist displayed on the selected tab. Then, when a checklist is selected from the selection screen, the check support unit 214 reads out the selected checklist and updates the check screen based on the selected checklist.

[0096] This allows the user to check non-functional requirements and the like using a desired checklist from among multiple checklists, for example, when multiple checklists exist for the same object.

[0097] Furthermore, when the check support unit 214 receives an instruction to complete the check, it registers the content of the options entered (selected) for each check item in the check result DB 264 as the check results for the business flow that was checked.

[0098] Specifically, the check support unit 214 associates the content of the options entered for the check items on each tab with the list name of the checklist used to display that tab, and stores the result as a check.The check support unit 214 then associates the flow ID of the business flow that was checked with the check results for each checklist that it previously stored, and registers them in the check result DB 264.As a result, the check result DB 264 stores, for each business flow, the check results for each element described in that business flow.

[0099] When an instruction is given to display or edit a business flow, the business flow creation support unit 212 may read the check results associated with the flow ID of the specified business flow from the check result DB 264 based on the flow ID of the specified business flow, and display them together with the business flow.

[0100] In addition, when a business flow to be checked is selected, the business flow creation support unit 212 may visualize and display the selected business flow on the same screen as the above-mentioned check screen or in a state that can be compared with the check screen.

[0101] 9, the cost calculation unit 215 of the server device 20 is an example of an extracting means and a reading means. The cost calculation unit 215 cooperates with the GUI providing unit 211 to provide an operation support screen (hereinafter also referred to as an estimate screen) that estimates the cost required to realize a configuration related to the business flow. In other words, the cost calculation unit 215 also functions as an example of an output means.

[0102] For example, when a business flow to be estimated is selected from the business flows stored in the business flow DB 261, the cost calculation unit 215 provides an estimate screen that estimates the cost required to realize the business flow.

[0103] Specifically, the cost calculation unit 215 extracts each of the elements described in the business flow to be estimated from the business flow. The cost calculation unit 215 also reads cost information related to each of the extracted elements from the cost DB 263. The cost calculation unit 215 also calculates the cost of each element based on the cost information read for each element, or adds up the costs of all elements. Then, based on the calculation results, the cost calculation unit 215 generates an estimate screen that displays the costs required to realize the business flow to be estimated.

[0104] 12 is a diagram showing an example of the quotation screen. As shown in Fig. 12, the quotation screen 50 has a first display area 51 that displays the cost for each element and a second display area 52 that displays the estimated cost for all elements.

[0105] The first display area 51 displays the cost for each element. Specifically, the first display area 51 displays the cost of each element using items such as target, classification, quantity, implementation cost, and operating cost. The target and classification correspond to the identifier and classification of the element described in the business flow that is the subject of the estimate. The quantity refers to the number of elements that are planned to be implemented. Furthermore, the implementation cost refers to the cost required for implementation, and the operating cost refers to the cost required for operation per unit period (for example, per month).

[0106] Here, the installation cost and operation cost are derived based on cost information read from the cost DB 263. For example, in the cost DB 263 of Fig. 7, the cost required to install one surveillance camera is 6,000 (yen), and therefore, as shown in the first display area 51, the cost required to install five surveillance cameras is 6,000 multiplied by 5, which is 30,000 (yen). In addition, in the cost DB 263 of Fig. 7, the cost required to operate the payment system is 7,000 (yen), and therefore, as shown in the first display area 51, the cost required to operate the payment system is 7,000 (yen). Furthermore, in the estimate for the payment system, 300,000 (yen) is recorded as the cost required to install a PC.

[0107] The quantity of an element may be automatically recognized from the business flow or may be input by the user. In the latter case, a numerical value may be directly input into the quantity field in the first display area 51.

[0108] The second display area 52 displays the total result of adding up the costs of the elements displayed in the first display area 51. Specifically, the second display area 52 displays the total result of the costs, separated into installation costs and operating costs.

[0109] This allows the user to easily check the cost of each element of the business flow for which an estimate is being made, as well as the cost required for the entire business flow, by referring to the estimate screen 50.

[0110] Furthermore, when the cost calculation unit 215 receives an instruction to complete confirmation of the estimated amount, it registers the content displayed on the estimate screen 50 in the confirmation result DB 264 as the estimate result for the business flow that was the subject of the estimate.

[0111] Specifically, the cost calculation unit 215 associates the flow ID of the business flow that is the subject of the estimate with the estimate result displayed on the estimate screen 50, and registers this in the confirmation result DB 264. As a result, the confirmation result DB 264 stores, for each business flow, the estimate result required to realize that business flow.

[0112] When an instruction is given to display or edit a business flow, the business flow creation support unit 212 may read the estimation results associated with the flow ID of the instructed business flow from the confirmation result DB 264 based on the flow ID of the instructed business flow, and control the display of the results together with the business flow.

[0113] In addition, when a business flow to be estimated is selected, the business flow creation support unit 212 may visualize and display the selected business flow on the same screen as the estimation screen described above, or in a state that can be compared with the estimation screen.

[0114] 9, the display control unit 216 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 216 causes the display unit 24 to display various operation support screens provided by the GUI providing unit 211.

[0115] The operation accepting unit 217 of the server device 20 accepts user operations via the operation unit 25. For example, when the operation accepting unit 217 accepts an operation on one of various operation support screens displayed on the display unit 24, the operation accepting unit 217 outputs the content of the operation to the CPU 21.

[0116] An example of the operation of the business support system 1 will be described below.

[0117] First, an example of an operation related to creating a checklist will be described. Fig. 13 is a flowchart showing an example of a process related to creating a checklist executed by the server device 20.

[0118] When the checklist creation support unit 213 receives an instruction to create a checklist from the terminal device 10 that has accessed the checklist creation support unit 213, the checklist creation support unit 213 displays a creation support screen on the display unit 14 of the terminal device 10 (step S11).

[0119] In addition, when an instruction is given to edit an existing checklist, the checklist creation support unit 213 reads the requested checklist from the checklist DB 262 and displays a creation support screen based on the requested checklist on the display unit 14 of the terminal device 10.

[0120] Next, the checklist creation support unit 213 waits until check items and the like are input (step S12; No). Here, when a registration instruction is received from the terminal device 10, the checklist creation support unit 213 determines that input has been made (step S12; Yes).

[0121] Next, the checklist creation support unit 213 generates a checklist based on the information input on the creation support screen (step S13), and registers it in the checklist DB 262 (step S14).

[0122] When an instruction is given to edit an existing checklist and there are no changes to the basic information, the checklist creation support unit 213 updates the checklist based on the contents of the changed check items. When an instruction is given to edit an existing checklist and there are edits to the basic information, the checklist creation support unit 213 registers a new checklist based on the contents of the changed check items.

[0123] Next, an example of an operation related to checking a business flow will be described. Fig. 14 is a flowchart showing an example of processing related to checking a business flow executed by the server device 20.

[0124] First, when the check support unit 214 receives an instruction from the terminal device 10 that has accessed the unit to specify the business flow to be checked, the check support unit 214 reads out the checklists with the default flag turned on from among the checklists with the target being "common" stored in the checklist DB 262 (step S21).

[0125] Next, the check support unit 214 initializes an index i, which counts the number of elements, to 0 (step S22). Next, the check support unit 214 extracts each of the elements described in the business flow to be checked from the business flow (step S23). Next, the check support unit 214 assigns an ascending number, starting from 0, to each of the extracted elements, and sets the number of extracted elements to "a" (step S24).

[0126] Next, the check support unit 214 determines whether or not the index i is less than the number of elements a (step S25). If the index i is less than the number of elements a (step S25; Yes), the check support unit 214 determines whether or not a checklist corresponding to the i-th element is stored in the checklist DB 262 (step S26). Here, if the check support unit 214 determines that a checklist corresponding to the i-th element is not stored (step S26; No), the process proceeds to step S29.

[0127] Furthermore, if the check support unit 214 determines that a checklist corresponding to the i-th element is stored (step S26; Yes), it determines whether or not any of the stored checklists has a default flag in an on state (step S27).Here, if the check support unit 214 determines that no checklist has a default flag in an on state (step S27; No), it proceeds to step S29.

[0128] Furthermore, if the check support unit 214 determines that there is a checklist whose default flag is on (step S27; Yes), it reads out the corresponding checklist from the checklist DB 262 (step S28) and proceeds to step S29.

[0129] In step S29, the check support unit 214 increments the index i by 1 and returns the process to step S25 (step S29). That is, the check support unit 214 sequentially executes the processes of steps S25 to S29 for all the extracted elements.

[0130] On the other hand, if the index i is equal to or greater than the number of elements a in step S25 (step S25; No), the check support unit 214 generates a check screen based on the checklist that has been read so far (step S30). Then, the check support unit 214 displays the generated check screen on the display unit 14 of the accessing terminal device 10 (step S31). Note that if an instruction to change the checklist is given via the above-mentioned change button 41, the check support unit 214 changes the checklist based on the instruction and updates the check screen.

[0131] Next, the check support unit 214 waits until an answer to the check item displayed on the check screen is input (step S32; No). Here, when an instruction to complete the check is given from the terminal device 10, the checklist creation support unit 213 determines that an answer has been input (step S32; Yes).

[0132] Then, the checklist creation support unit 213 registers the content of the answers entered for each check item in the check result DB 264 as the check results for the business flow that was the subject of the check (step S33).

[0133] Next, an example of an operation related to cost estimation of a business flow will be described. Fig. 15 is a flowchart showing an example of processing related to cost estimation of a business flow executed by the server device 20.

[0134] First, when the business flow to be estimated is specified by the terminal device 10 that has accessed the cost calculation unit 215, the cost calculation unit 215 initializes the index i that counts the number of elements to 0 (step S41).

[0135] Next, the cost calculation unit 215 extracts each of the elements described in the business flow to be estimated from the business flow (step S42). Next, the cost calculation unit 215 assigns an ascending number starting from 0 to each of the extracted elements, and sets the number of extracted elements to "a" (step S43).

[0136] Next, the cost calculation unit 215 determines whether or not the index i is less than the number of elements a (step S44). If the index i is less than the number of elements a (step S44; Yes), the cost calculation unit 215 determines whether or not cost information corresponding to the i-th element is stored in the cost DB 263 (step S45). Here, if the cost calculation unit 215 determines that cost information corresponding to the i-th element is not stored (step S45; No), the process proceeds to step S47.

[0137] Furthermore, if the cost calculation unit 215 determines that cost information corresponding to the i-th element is stored (step S45; Yes), it reads out the corresponding cost information from the cost DB 263 (step S46), and proceeds to step S47.

[0138] In step S47, the cost calculation unit 215 increments the index i by 1 and returns the process to step S44 (step S47). That is, the cost calculation unit 215 sequentially executes the processes of steps S44 to S47 for all the extracted elements.

[0139] On the other hand, if the index i is equal to or greater than the number of elements a in step S44 (step S44; No), the cost calculation unit 215 generates an estimate screen showing the cost required to realize the business flow based on the cost information that has been read up to that point (step S48). Then, the cost calculation unit 215 displays the generated estimate screen on the display unit 14 of the accessing terminal device 10 (step S49). Note that if the quantity of elements is changed, the cost calculation unit 215 recalculates the cost based on the changed quantity and updates the estimate screen.

[0140] Next, the cost calculation unit 215 waits until confirmation of the estimate screen is completed (step S50; No). Here, when confirmation completion is instructed from the terminal device 10, the cost calculation unit 215 determines that confirmation of the estimate screen is completed (step S50; Yes).

[0141] Then, the cost calculation unit 215 registers the content displayed on the estimate screen as the estimate result of the business flow that is the subject of the estimate in the confirmation result DB 264 (step S51).

[0142] As described above, the server device 20 of this embodiment extracts each element from a business flow that describes a series of steps consisting of each element related to the performance of a business and the execution content to be executed by that element, reads out additional information related to the extracted element from the memory unit 26 that stores additional information related to the element in association with each type of element, and outputs the additional information to the terminal device 10 to which the information is to be provided.

[0143] As a result, when there are items to be checked for elements described in a business flow, for example, at the stage of creating or checking the business flow, the server device 20 can use the additional information for checking. Therefore, the server device 20 can provide business support based on the business flow.

[0144] The server device 20 also stores, as additional information, a checklist in which check items related to the elements are set, and outputs the checklist related to the elements extracted from the business flow to the destination terminal device 10. This allows the server device 20 to present to the user a checklist containing check items to be confirmed for the elements described in the business flow, thereby urging the user to check the check items. Therefore, the server device 20 can provide business support based on the business flow.

[0145] The server device 20 also stores cost information, which sets the cost required to introduce or operate an element, as additional information, and outputs the cost information related to the element extracted from the business flow to the destination terminal device 10. This allows the server device 20 to present the cost required to introduce or operate the element described in the business flow to the user, thereby prompting the user to check the cost required to realize the business flow. Therefore, the server device 20 can provide business support based on the business flow.

[0146] The above-described embodiment can be modified as needed by partially changing the configuration or functions of each of the above-described devices. Therefore, several modifications of the above-described embodiment will be described below as other embodiments. The following mainly focuses on differences from the above-described embodiment, and detailed descriptions of commonalities with the content already described will be omitted. The modifications described below may be implemented individually or in appropriate combination.

[0147] (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 operation support 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.

[0148] In this case, the terminal device 10 may function as a business support device by including functional units such as the GUI providing unit 211, the business flow creation support unit 212, the checklist creation support unit 213, the check support unit 214, and the cost calculation unit 215 described above, and may display various operation support screens on the terminal device 10 itself. Note that the terminal device 10 is assumed to be in a state in which it can read and write various DBs held by the server device 20.

[0149] In this case, the terminal device 10 may store some or all of the business flow DB261, checklist DB262, cost DB263, and confirmation result DB264, or they may be stored in another device (or cloud) that the terminal device 10 can access.

[0150] (Variation 2) In the above-described embodiment, the cost information is stored in advance in the cost DB 263, but this is not limiting, and the cost information for each element may be created in a manner similar to a checklist, etc. In this case, the server device 20 may be configured to provide the terminal device 10 with an operation support screen for creating and editing the cost information.

[0151] The creation and editing of cost information may be performed by an existing functional unit such as the GUI providing unit 211, or a dedicated functional unit may be newly provided.

[0152] (Variation 3) In the above embodiment, a form in which one business flow is the subject of checking or estimation is described, but this is not limited to this. If multiple business flows are selected at once, each of the business flows may be the subject of checking or estimation.

[0153] For example, when multiple business flows are selected, the check support unit 214 may generate a check screen (tab) for each selected business flow that displays the check items for each element. In this case, a check screen based on a "common" checklist may be generated individually for each business flow, or a single check screen common to all business flows may be generated.

[0154] Furthermore, for example, when multiple business flows are selected, the cost calculation unit 215 may generate an estimate screen for each selected business flow that shows the costs required for that business flow, or may generate an estimate screen that adds up the costs required for all business flows.

[0155] (Variation 4) In the above embodiment, a form has been described in which a business flow to be checked or estimated is selected by displaying a list of business flows stored in the business flow DB 261. However, the method of selecting a business flow is not limited to this, and other methods may also be used.

[0156] For example, a management policy tree has been known in the past that visualizes the relationship between management goals and the measures to achieve those goals, and represents the relationship between goals and measures in a tree structure. Such a management policy tree is created using techniques such as KPI (Key Performance Indicator) and is composed of multiple nodes connected in a tree structure.

[0157] Specifically, in a management policy tree, intermediate goal nodes for setting intermediate goals corresponding to KPIs (Key Performance Indicators) are placed below the root node, which is a node for setting goals to be achieved. Furthermore, factor nodes representing factors for achieving intermediate goals corresponding to KSFs (Key Success Factors) are placed below the intermediate goal nodes. Furthermore, in a management policy tree, solution nodes representing methods for achieving (solving) the intermediate objectives or factors set in the node immediately above can be placed below the intermediate goal or factor nodes. Furthermore, in a management policy tree, service nodes representing specific services that achieve the factors or solutions set in the node immediately above can be placed below the factor or solution nodes.

[0158] Furthermore, in the management policy tree, it is possible to describe specific services that realize the cause or solution set in the node immediately above it, below the factor node or solution node, i.e., in the terminal node (hereinafter also referred to as the service node). Here, since the service node corresponds to the service provided at the field level such as a store, for example, it is conceivable to associate, store, and manage each service node with a business flow that describes the process of realizing the service corresponding to that service node.

[0159] When managing workflows using the management policy tree configured as described above, the configuration may be such that, for example, a workflow to be checked or estimated is selected by selecting a service node. Also, the configuration may be such that, by selecting a higher-level node of a service node, the workflow corresponding to one or more service nodes connected to the higher-level node is selected as the target for checking or estimation.

[0160] When this modified example is adopted, the GUI providing unit 211 or the business flow creation support unit 212 may be responsible for the function of displaying the management policy tree in a visualized state, or the configuration may be such that a separate functional unit specialized in creating and visualizing the management policy tree is provided.

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

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

[0163] 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, and modifications 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]

[0164] 1. Business support system 10 Terminal Equipment 20 Server device 111 Display control unit 112 Operation reception section 211 GUI provision department 212 Business Flow Creation Support Department 213 Checklist Creation Support Department 214 Check Support Department 215 Cost Calculation Department 216 Display control unit 217 Operation reception section 261 Business Flow DB 262 Checklist DB 263 Cost DB 264 Confirmation Results DB [Prior art documents] [Patent documents]

[0165] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-235470

Claims

1. An extraction means for extracting each of the elements from a workflow in which each element relating to the performance of a business and the execution contents executed by the element are described as a series of procedures; a reading means for reading the additional information regarding the element extracted by the extracting means from a storage unit in which additional information regarding each element is stored in association with the element; an output means for outputting the additional information regarding the element read by the reading means; Equipped with the storage unit stores, as the additional information, a checklist in which check items related to the element are set; The output means outputs the checklist related to the element extracted by the extraction means in association with the element.

2. A receiving means for receiving a node selection from a management policy tree composed of a plurality of nodes; an extraction means for extracting each of the elements from a workflow corresponding to the selected node, the workflow being described as a series of steps consisting of elements related to the performance of a business and the execution contents executed by the elements; a reading means for reading, from a storage unit that stores, as additional information, at least one of a checklist in which confirmation items related to each element are set and cost information indicating the cost required for introducing or operating the element; and an output means for outputting the additional information regarding the element read by the reading means in association with the element extracted by the extraction means; A business support device comprising:

3. The storage unit stores the checklist including at least confirmation items related to non-functional requirements of the element. The business support device according to claim 1 or 2.

4. the storage unit stores, as the additional information, cost information indicating a cost required for introducing or operating the element; the output means outputs the cost information related to the element extracted by the extraction means in association with the element. The business support device according to claim 1 .

5. the output means outputs a total amount of costs required for introducing or operating the elements based on the cost information related to each of the elements extracted by the extraction means. The business support device according to claim 2 or 4.

6. Computers for business support devices, An extraction means for extracting each of the elements from a workflow in which each element relating to the performance of a business and the execution contents executed by the element are described as a series of procedures; a reading means for reading the additional information regarding the element extracted by the extracting means from a storage unit in which additional information regarding each element is stored in association with the element; an output means for outputting the additional information regarding the element read by the reading means; and make it work, the storage unit stores, as the additional information, a checklist in which check items related to the element are set; The output means outputs the checklist related to the element extracted by the extraction means in association with the element.

7. A computer of a business support device, a receiving means for receiving a node selection from a management policy tree composed of a plurality of nodes; an extraction means for extracting each of the elements from a workflow corresponding to the selected node, the workflow being described as a series of steps consisting of elements related to the performance of a business and the execution contents executed by the elements; a reading means for reading, from a storage unit that stores, as additional information, at least one of a checklist in which confirmation items related to each element are set and cost information indicating the cost required for introducing or operating the element; and an output means for outputting the additional information regarding the element read by the reading means in association with the element extracted by the extraction means; A program to make it function as such.

Images