Computer system and retrieval support method

Abstract

The present invention supports selection of a business flow from among a plurality of business flows. This computer system holds, for each business flow defining a procedure of a plurality of tasks, business data acquired in a business based on the business flow, manages the business flow as a directed graph having one task as one node, compares the plurality of business flows, generates an integrated node by executing at least one of a process of integrating a plurality of tasks having a different order relation between business flows on the basis of the result of comparison and a process of integrating a subject task not included in at least one business flow with at least one of a task executed before the subject task and a task executed after the subject task, and generates a directed graph, which is composed of at least one unintegrated task node and at least one integrated node, as an integrated business flow for retrieving a business flow.

Description

Computer system and search support method Incorporation by Reference

[0001] This application claims priority from Japanese Patent Application No. 2023-122839, filed on July 27, 2023, the contents of which are incorporated herein by reference.

[0002] The present invention relates to a data search technique used for analyzing work performed according to a work flow.

[0003] In the production of products or materials and in administrative procedures, some tasks are performed according to a workflow that defines the order of tasks. In order to improve the efficiency of business operations, it is important to optimize the selection of tasks to be performed and the order in which the tasks are performed.

[0004] A workflow can be represented as a directed graph with tasks as nodes. Known techniques for generating directed graphs include those described in Patent Documents 1 and 2, for example.

[0005] Patent Document 1 describes that "the directed graph creation device has an identification unit that refers to an event chain storage unit that stores a plurality of event chains and a directed graph storage unit that stores a directed graph created by integrating the plurality of event chains, and identifies, among the paths included in the directed graph, a path that does not exist in any of the plurality of event chains; a duplication unit that creates a copy of the most downstream node, excluding the endpoint node of the path, and the edge connected to that node, among the nodes to which a plurality of edges connect downstream on the identified path; and a deletion unit that deletes, from the duplicated edges, an edge such that deleting the edge does not remove from the directed graph any path included in the plurality of event chains."

[0006] Patent Document 2 states that "the information processing device 1 classifies each of the multiple events included in the multiple response histories 30 relating to the actions and states to be recorded into actions and states. The information processing device 1 generates graph information 23 by an integration process based on the contents of the multiple events included in the multiple response histories 30. The information processing device 1 determines the validity of the integration process by verifying whether each of the paths included in the generated graph information 23 that pass through the events integrated by the integration process and classified as states is included in the partial paths of the multiple response histories 30."

[0007] JP 2012-194708 A JP 2019-117442 A

[0008] In an environment where business processes are executed according to various workflows, useful information can be obtained by analyzing the results of each workflow. Conventionally, users have had to manually select the workflow to analyze. However, when there are a large number of workflows, the cost required for workflow selection becomes high.

[0009] An object of the present invention is to provide a technique for supporting the selection of a workflow from among a plurality of workflows.

[0010] A representative example of the invention disclosed in this application is as follows: That is, a computer system including a processor, a storage device connected to the processor, and a network interface connected to the processor manages, for each workflow defining the procedures of a plurality of tasks, business data acquired in tasks based on the workflow, manages the workflow as a directed graph with each task as a node, compares the plurality of workflows, and, based on the results of the comparison, generates an integrated node by executing at least one of the following: a process for integrating the plurality of tasks whose order relationships differ between the workflows, and a process for integrating at least one task not included in the workflow with at least one task executed before or after the task, and generates a directed graph consisting of at least one unintegrated task node and at least one integrated node as an integrated workflow for searching the plurality of workflows, and presents the directed graph to a user.

[0011] According to the present invention, by presenting an integrated workflow that integrates multiple workflows, it is possible to easily specify the tasks and the order of the tasks included in the workflow to be searched. Problems, configurations, and advantages other than those described above will become clear from the description of the following embodiments.

[0012] 1 is a diagram illustrating an example of a system configuration according to a first embodiment; FIG. 2 is a diagram illustrating an example of a configuration of a business data collection device according to a first embodiment; FIG. 3 is a diagram illustrating an example of a configuration of a business data management server according to a first embodiment; FIG. 4 is a diagram illustrating an example of a data structure of data stored in a business data DB according to a first embodiment; FIG. 5 is a diagram illustrating an example of a data structure of data stored in a business flow DB according to a first embodiment; FIG. 6 is a diagram illustrating an example of a data structure of data stored in a business flow DB according to a first embodiment; FIG. 7 is a diagram illustrating an example of a data structure of data stored in an integrated business flow DB according to a first embodiment; FIG. 8 is a diagram illustrating an example of a data structure of data stored in an integrated business flow DB according to a first embodiment; FIG. 9 is a diagram illustrating an example of a data structure of data stored in an integrated business flow DB according to a first embodiment; 1 is a flowchart illustrating an example of a second order determination process executed by the business data management server of Example 1. FIG. 2 is a sequence diagram illustrating the flow of a search process for business data in the system of Example 1. FIG. 3 is a diagram illustrating an example of a screen presented by the business data management server of Example 1. FIG. 4 is a diagram illustrating an example of a screen presented by the business data management server of Example 1. FIG. 5 is a flowchart illustrating an example of a business flow search process executed by the business data management server of Example 1. FIG. 6 is a diagram illustrating an example of a screen presented by the business data management server of Example 1. FIG. 7 is a diagram illustrating an example of a screen presented by the business data management server of Example 1. FIG. 8 is a flowchart illustrating an example of a business flow search process executed by the business data management server of Example 1.

[0013] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will readily understand that the specific configuration can be changed without departing from the spirit or intent of the present invention.

[0014] In the configuration of the invention described below, the same or similar configurations or functions are denoted by the same reference numerals, and redundant explanations will be omitted.

[0015] In this specification, the terms "first," "second," "third," etc. are used to identify components and do not necessarily limit the number or order.

[0016] FIG. 1 is a diagram illustrating an example of a system configuration according to a first embodiment.

[0017] The system is composed of a business data management server 100, a terminal 101, and a plurality of bases 102. The business data management server 100, the terminal 101, and the plurality of bases 102 are connected via a network 103 such as a WAN (Wide Area Network) or a LAN (Local Area Network).

[0018] At the base 102, work is performed according to a work flow. The work includes, for example, application work, manufacturing work, production work, and performance testing work. Note that the present invention is not limited to the content of the work. A work flow represents the procedure of multiple tasks. A work flow can be expressed as a directed graph with tasks as nodes.

[0019] The base 102 includes a plurality of data generation devices 111 and a business data collection device 110. The data generation device 111 is a device that generates business data related to business, such as a sensor, a camera, or a terminal operated by a worker. The business data collection device 110 is a device that collects and manages business data. The business data collection device 110 accumulates business data along with information related to business flows. The information related to business flows is, for example, a business flow identifier, etc.

[0020] The business data management server 100 acquires and stores business data from the business data collection device 110 at each base 102. The business data management server 100 also accepts requests from the terminal 101 and executes various processes.

[0021] The terminal 101 is a terminal for transmitting various requests to the business data management server 100 .

[0022] FIG. 2 is a diagram illustrating an example of the configuration of the business data collection device 110 according to the first embodiment.

[0023] The business data collection device 110 includes a processor 200, a main memory device 201, an auxiliary memory device 202, and a network interface 203. The hardware elements are connected via a bus 204.

[0024] The processor 200 is a device that performs various calculations and executes programs stored in the main memory device 201. The processor 200 executes processing in accordance with the programs, thereby operating as a functional unit (module) that realizes a specific function. In the following description, when a process is described using a functional unit as the subject, this indicates that the processor 200 is executing a program that realizes the functional unit.

[0025] The main memory device 201 is a storage device, such as a volatile or nonvolatile memory, that stores programs executed by the processor 200 and information executed by the programs. The main memory device 201 is also used as a work area. The auxiliary memory device 202 is a large-capacity storage device that permanently stores information, such as a hard disk drive (HDD) or a solid state drive (SSD). The network interface 203 communicates with other devices via a network.

[0026] The programs and information stored in the main memory device 201 may be stored in the auxiliary memory device 202. In this case, the processor 200 reads the programs and information from the auxiliary memory device 202 and loads them into the main memory device 201.

[0027] The main storage device 201 stores a program that realizes the collection unit 210 and a business data DB 220. The collection unit 210 collects business data from the data generation device 111. The business data DB 220 is a database that stores business data.

[0028] FIG. 3 is a diagram illustrating an example of the configuration of the business data management server 100 according to the first embodiment.

[0029] The business data management server 100 includes a processor 300, a main memory device 301, an auxiliary memory device 302, and a network interface 303. The hardware elements are connected via a bus 304.

[0030] The processor 300, main memory device 301, auxiliary memory device 302, network interface 303, and bus 304 are the same hardware elements as the processor 200, main memory device 201, auxiliary memory device 202, network interface 203, and bus 204, so their description will be omitted.

[0031] The main memory device 301 stores programs that implement the management unit 310 and search unit 311. The main memory device 301 also stores a business data DB 320, a business flow DB 321, and an integrated business flow DB 322.

[0032] The management unit 310 manages business data and business flows. The search unit 311 searches for business data associated with a business flow in accordance with a user request.

[0033] The business data DB 320 is a database that stores business data. The business flow DB 321 is a database that stores definition information of business flows. The integrated business flow DB 322 is a database that stores definition information of integrated business flows that are used to search for business flows.

[0034] It should be noted that with regard to each functional unit of the business data management server 100, multiple functional units may be combined into one functional unit, or one functional unit may be divided into multiple functional units for each function.

[0035] Although the business data management server 100 is implemented using a physical computer, it may be implemented using virtualization technology. Furthermore, the functions of the business data management server 100 may be implemented using a computer system consisting of multiple computers.

[0036] FIG. 4 is a diagram illustrating an example of the data structure of data stored in the business data DB 320 according to the first embodiment.

[0037] The business data DB 320 stores business data 400. The business data 400 includes a business identifier 401, a data identifier 402, and a plurality of items 403.

[0038] The task identifier 401 is a field that stores a task identifier. The data identifier 402 is a field that stores an identifier for task data. The items 403 are fields that store item values ​​that are measured or acquired during work. The number of items 403 included in the task data 400 can be set arbitrarily.

[0039] 5A and 5B are diagrams illustrating an example of the data structure of data stored in the business flow DB 321 according to the first embodiment.

[0040] The business flow DB 321 stores business flow metadata 500 and node data 510 .

[0041] The business flow metadata 500 is data for managing an overview of a business flow. The business flow DB 321 stores as many business flow metadata 500 as there are business flows. The business flow metadata 500 includes a business identifier 501, a business flow identifier 502, and a creation date and time 503.

[0042] The task identifier 501 is a field for storing the identifier of the task. The workflow identifier 502 is a field for storing the identifier of the workflow. The creation date / time 503 is a field for storing the date / time when the workflow was created.

[0043] The node data 510 is data for managing nodes corresponding to the tasks that make up a business flow. In the following explanation, a node corresponding to a task will also be referred to as a task node. For one business flow, there is as many node data 510 as there are tasks that make up the business flow. The node data 510 includes a business flow identifier 511, a node identifier 512, a previous node identifier 513, a next node identifier 514, a data identifier 515, and a registration date and time 516.

[0044] The business flow identifier 511 is a field that stores the identifier of the business flow. The node identifier 512 is a field that stores the identifier of the node. The previous node identifier 513 is a field that stores the identifier of the node that precedes the node that corresponds to the node data 510. The subsequent node identifier 514 is a field that stores the identifier of the node that follows the node that corresponds to the node data 510.

[0045] The data identifier 515 is a field for storing an identifier for specifying the task data 400 corresponding to the node. The registration date and time 516 is a field for storing the latest registration date and time of the task data 400.

[0046] A user sets the definition information of the business flow (business flow metadata 500 and node data 510 ) using, for example, the terminal 101 and registers it in the business data management server 100 .

[0047] 6A, 6B, and 6C are diagrams illustrating an example of the data structure of data stored in the integrated workflow DB 322 according to the first embodiment.

[0048] The integrated workflow DB 322 stores integrated workflow metadata 600 , node data 610 , and integrated node data 620 .

[0049] The integrated business flow metadata 600 is data for managing an overview of an integrated business flow. The integrated business flow DB 322 stores as many pieces of integrated business flow metadata 600 as there are integrated business flows. The integrated business flow metadata 600 includes a business identifier 601 and an integrated business flow identifier 602.

[0050] The task identifier 601 is a field for storing the identifier of a task. The integrated workflow identifier 602 is a field for storing the identifier of an integrated workflow.

[0051] The node data 610 is data for managing the nodes that make up an integrated workflow. For one integrated workflow, there is as many node data 610 as there are nodes that make up the integrated workflow. Note that an integrated workflow includes operation nodes and integrated nodes that integrate multiple operation nodes. In the following explanation, when there is no need to distinguish between operation nodes and integrated nodes, they will be referred to as nodes.

[0052] The node data 610 includes an integrated workflow identifier 611 , a node identifier 612 , a previous node identifier 613 , a subsequent node identifier 614 , and an existence rate 615 .

[0053] The integrated workflow identifier 611 is a field that stores the identifier of the integrated workflow. The node identifier 612 is a field that stores the identifier of the node. In the case of an operation node, the identifier of the operation node in the workflow is stored as is, and in the case of an integrated node, the identifier assigned to the integrated node is stored.

[0054] The previous node identifier 613 is a field that stores the identifier of the node that precedes the node that corresponds to the node data 610. The next node identifier 614 is a field that stores the identifier of the node that follows the node that corresponds to the node data 610. The existence rate 615 is a field that stores the percentage of the workflows that contain the operation node that corresponds to the node data 610, out of the workflows that were used to generate the integrated workflow. If the node is an integrated node, the existence rate of each operation node included in the integrated node is stored.

[0055] The integrated node data 620 is data for managing the integrated node, and includes an integrated business process identifier 621, a node identifier 622, and an operation node list 623.

[0056] The integrated workflow identifier 621 is a field that stores the identifier of the integrated workflow. The node identifier 622 is a field that stores the identifier of the integrated node. The operation node list 623 is a field that stores the identifiers of the operation nodes that make up the integrated node.

[0057] Next, we will explain the processing executed by the business data management server 100. The business data management server 100 executes processing to generate an integrated business flow and processing to search for business data using the integrated business flow. First, we will explain the processing to generate an integrated business flow.

[0058] The business data management server 100 executes the integrated business flow generation process periodically or when an execution instruction is received. Fig. 7 is a flowchart illustrating an example of the integrated business flow generation process executed by the business data management server 100 of Example 1. Here, it is assumed that a business identifier is specified.

[0059] The business data management server 100 starts a loop process of the business flow (step S101). Specifically, the business data management server 100 selects one business flow of the business corresponding to the specified identifier from the business flow DB 321. Here, the business flow is selected in ascending order of the number of nodes. At this time, the creation date of the business flow may be taken into consideration. For example, one possible method is to select the business flow in ascending order of the number of nodes and the oldest creation date.

[0060] The business data management server 100 references the integrated business flow DB 322 and determines whether or not an integrated business flow corresponding to the specified business exists (step S102). That is, it determines whether or not there exists integrated business flow metadata 600 in which the identifier of the specified business is set in the business identifier 601.

[0061] If the integrated business flow DB 322 does not contain an integrated business flow corresponding to the specified business, the business data management server 100 sets the selected business flow as the integrated business flow (step S104) and then proceeds to step S105.

[0062] Specifically, the business data management server 100 generates integrated business flow metadata 600 and generates integrated node data 620 corresponding to the node data 510 of the selected business flow.

[0063] If an integrated workflow corresponding to the specified task exists in the integrated workflow DB 322, the task data management server 100 executes an integrated workflow update process (step S103), and then proceeds to step S105. The integrated workflow update process will be described in detail later.

[0064] In step S105, the business data management server 100 determines whether or not processing has been completed for all business flows (step S105).

[0065] If processing has not been completed for all business flows, the business data management server 100 returns to step S101 and executes the same process. If processing has been completed for all business flows, the business data management server 100 ends the integrated business flow generation process.

[0066] 8A and 8B are flowcharts illustrating an example of integrated workflow update processing executed by the business data management server 100 according to the first embodiment.

[0067] The business data management server 100 starts loop processing of the nodes (step S201). Specifically, the business data management server 100 selects one node of the selected business flow. Note that the nodes are selected in the order in which the tasks are to be executed.

[0068] The business data management server 100 determines whether the selected task node is included in the integrated task flow (step S202). Specifically, the business data management server 100 determines whether there is node data 610 whose node identifier 612 value matches the node identifier 512 value, or whether there is integrated node data 620 whose task node list 623 includes the value of the node identifier 512.

[0069] If the selected task node is not included in the integrated workflow, the business data management server 100 integrates the task node with the node preceding the selected task node in the workflow (step S203), and then proceeds to step S204. Specifically, the following process is executed.

[0070] (S203-1) The business data management server 100 refers to the node data 510 of the selected operation node to identify the previous node.

[0071] (S203-2) The business data management server 100 references the integrated business flow DB 322 and determines whether or not there is node data 610 in which the identifier of the previous node is stored in the node identifier 612.

[0072] (S203-3) If there is node data 610 in which the identifier of the previous node is stored in the node identifier 612, the business data management server 100 generates integrated node data 620 that stores the identifiers of the previous node and the selected work node in the work node list 623. The business data management server 100 determines the identifier of the integrated node and stores it in the node identifier 622. The business data management server 100 rewrites the node identifier 612 of the found node data 610 with the identifier of the integrated node. Thereafter, the business data management server 100 ends the processing of step S203.

[0073] (S203-4) If there is no node data 610 in which the identifier of the previous node is stored in the node identifier 612, the business data management server 100 searches for integrated node data 620 that stores the identifier of the previous node in the work node list 623, and stores the identifier of the selected work node in the work node list 623 of the integrated node data 620. Thereafter, the business data management server 100 ends the processing of step S203.

[0074] The selected operation node may be integrated with the node following the selected operation node. In this way, an operation that is not included in at least one workflow is integrated with the preceding operation or the following operation.

[0075] In step S204, the business data management server 100 determines whether or not processing has been completed for all nodes in the selected business flow (step S204).

[0076] If processing has not been completed for all nodes in the selected business flow, the business data management server 100 returns to step S201 and executes the same process. If processing has been completed for all nodes in the selected business flow, the business data management server 100 ends the integrated business flow update process.

[0077] If it is determined in step S202 that the selected work node is included in the integrated workflow, the business data management server 100 determines whether an integrated node including the work node exists (step S205). Specifically, it determines whether the work node list 623 contains integrated node data 620 that stores the identifier of the selected work node.

[0078] If an integrated node including the selected operation node exists, the business data management server 100 proceeds to step S204.

[0079] If there is no integrated node that includes the selected operation node, the business data management server 100 determines whether both the previous node and the subsequent node of the selected operation node in the business flow are included in the integrated business flow (step S206).

[0080] Specifically, the business data management server 100 identifies the previous node and the subsequent node of the selected work node in the selected business flow based on the node data 510 of the selected work node. For each of the previous node and the subsequent node, the business data management server 100 determines whether there is node data 610 that stores the identifier of the node (previous node or subsequent node) in the node identifier 612, or whether there is integrated node data 620 that stores the identifier of the node (previous node or subsequent node) in the work node list 623.

[0081] If both the previous node and the next node of the selected task node in the business flow are included in the integrated business flow, the business data management server 100 executes a first order determination process (step S207) and then proceeds to step S204. The first order determination process will be described in detail later.

[0082] If at least one of the preceding node and succeeding node of the selected operation node in the business flow is not included in the integrated business flow, the business data management server 100 executes a second order determination process (step S208) and then proceeds to step S204. The second order determination process will be described in detail later.

[0083] FIG. 9 is a flowchart illustrating an example of a first order determination process executed by the business data management server 100 according to the first embodiment.

[0084] The business data management server 100 compares the order relationship between the selected operation node, previous node, and subsequent node in the business flow with the order relationship between the selected operation node, previous node, and subsequent node in the integrated business flow (step S301).

[0085] Specifically, the business data management server 100 identifies the order relationship between the selected operation node, previous node, and subsequent node in the integrated business flow by referencing the integrated business flow DB 322. If any of the operation node, previous node, and subsequent node is included in an integrated node, the order relationship between the integrated node and the other two operation nodes is compared with the order relationship between the selected operation node, previous node, and subsequent node in the business flow.

[0086] The business data management server 100 determines whether the order relationships match based on the comparison result (step S302).

[0087] If the order relationships match, the business data management server 100 ends the first order determination process.

[0088] If the order relationships do not match, the business data management server 100 integrates the nodes in the range (integration range) that includes the selected operation node, the previous node, and the next node of the integrated business flow (step S303).The business data management server 100 then terminates the first order determination process.Specifically, the following process is executed.

[0089] (S303-1) The business data management server 100 determines whether or not two or more integrated nodes are included in the nodes included in the integration range.

[0090] (S303-2) If two or more integrated nodes are included among the nodes included in the integration range, the business data management server 100 merges the integrated node data 620 corresponding to the integrated nodes to generate one integrated node data 620. The business data management server 100 registers the identifiers of the work nodes included in the integration range in the work node list 623 of the generated integrated node data 620.

[0091] The business data management server 100 generates node data 610 corresponding to the newly generated integrated node. The node identifier 612 is set to the value of the node identifier 622. The previous node identifier 613 is set to the value of the previous node identifier 613 of the integrated node data 620 of the node that is the earliest in order among the nodes included in the integration range. The next node identifier 614 is set to the value of the next node identifier 614 of the integrated node data 620 of the node that is the latest in order among the nodes included in the integration range.

[0092] The business data management server 100 deletes the node data 610 of the work nodes in the integration range, and then ends the process of step S303.

[0093] (S303-3) If two or more integrated nodes are not included in the nodes included in the integration range, the business data management server 100 determines whether or not one integrated node is included in the integration range.

[0094] (S303-4) When one integrated node is included among the nodes included in the integration range, the business data management server 100 registers the identifier of the work node included in the integration range in the work node list 623 of the integrated node data 620 corresponding to that integrated node. Also, the previous node identifier 613 is set to the value of the previous node identifier 613 of the node data 610 of the node that is the earliest in order among the nodes included in the integration range. The next node identifier 614 is set to the value of the next node identifier 614 of the node data 610 of the node that is the latest in order among the nodes included in the integration range.

[0095] The business data management server 100 deletes the node data 610 of the operation nodes included in the integration range, and then ends the process of step S303.

[0096] (S303-5) If the integrated node is not included among the nodes included in the integration range, the business data management server 100 generates integrated node data 620. The business data management server 100 sets an identifier in the integrated business flow identifier 621, sets the identifier of the integrated node in the node identifier 622, and sets the identifiers of the work nodes included in the integration range in the work node list 623. The business data management server 100 generates node data 610 corresponding to the integrated node. The previous node identifier 613 is set to the value of the previous node identifier 613 of the node data 610 of the work node that is the earliest in order within the integration range. The next node identifier 614 is set to the value of the next node identifier 614 of the node data 610 of the work node that is the latest in order among the nodes included in the integration range.

[0097] The business data management server 100 deletes the node data 610 of the operation nodes included in the integration range, and then ends the process of step S303.

[0098] 10A and 10B are flowcharts illustrating an example of the second order determination process executed by the business data management server 100 according to the first embodiment.

[0099] The business data management server 100 determines whether the node preceding the selected operation node in the business flow is included in the integrated business flow (step S401).

[0100] If the previous node of the selected work node in the business flow is included in the integrated business flow, the business data management server 100 compares the order relationship between the selected work node and the previous node in the business flow with the order relationship between the selected work node and the previous node in the integrated business flow (step S402).

[0101] Based on the comparison result, the business data management server 100 determines whether the order relationships match (step S403). That is, it determines whether the previous node precedes the operation node in the integrated business flow.

[0102] If the order relationships match, the business data management server 100 ends the second order determination process.

[0103] If the order relationships do not match, the business data management server 100 integrates the nodes in the range (integration range) that includes the selected operation node and the previous node in the integrated business flow (step S404). The business data management server 100 then ends the second order determination process. The process in step S404 is similar to the process in step S303, so a detailed description will be omitted.

[0104] In step S401, if the node preceding the selected work node in the business flow is not included in the integrated business flow, the business data management server 100 determines whether the node following the selected work node in the business flow is included in the integrated business flow (step S405).

[0105] If the successor node of the selected work node in the business flow is included in the integrated business flow, the business data management server 100 compares the order relationship between the selected work node and the successor node in the business flow with the order relationship between the selected work node and the successor node in the integrated business flow (step S406).

[0106] Based on the comparison result, the business data management server 100 determines whether the order relationships match (step S407). That is, it determines whether the order of the subsequent node in the integrated business flow is after the operation node.

[0107] If the order relationships match, the business data management server 100 ends the second order determination process.

[0108] If the order relationships do not match, the business data management server 100 integrates the nodes in the range (integration range) that includes the selected operation node and the subsequent node in the integrated business flow (step S408). The business data management server 100 then ends the second order determination process. The process in step S408 is similar to the process in step S303, so a detailed description will be omitted.

[0109] In step S405, if the node following the selected work node in the business flow is not included in the integrated business flow, the business data management server 100 skips the processing of the selected work node and terminates the second order determination process. The selected work node is processed again after the processing of other work nodes has been executed.

[0110] In the first order determination process and the second order determination process, task groups with different order relationships are integrated.

[0111] The above-described method for generating an integrated workflow is an example and is not intended to be limiting. Any process can be used as long as it can integrate multiple tasks that have different order relationships between workflows, and can integrate a task that is not included in at least one workflow with at least one task that is executed before that task and / or one task that is executed after that task.

[0112] Next, a process for searching business data using an integrated business flow will be described. Fig. 11 is a sequence diagram illustrating the flow of a process for searching business data in the system of the first embodiment.

[0113] A user uses the terminal 101 to access the business data management server 100 in order to search for business data (step S501).

[0114] The business data management server 100 presents a screen for accepting the designation of the integrated business flow (step S502). For example, a screen 1200 such as that shown in FIG.

[0115] The screen 1200 includes radio buttons 1201 and 1202, input fields 1203 and 1204, and an operation button 1205. The radio buttons 1201 and 1202 are used to select information used to specify an integrated business flow. The input fields 1203 and 1204 are used to input various identifiers. The operation button 1205 is used to instruct the display of an integrated business flow.

[0116] When using a business identifier, the user operates radio button 1201 and inputs the business identifier in input field 1203. When using a business flow identifier, the user operates radio button 1202 and inputs the business flow identifier in input field 1204.

[0117] When the user operates the operation button 1205, the terminal 101 transmits a display request including the identification information input by the user to the business data management server 100 (step S503).

[0118] The business data management server 100 searches for the corresponding integrated business flow and presents a screen displaying the integrated business flow (step S504).

[0119] If the display request includes a business identifier, the business data management server 100 refers to the integrated business flow DB 322 and searches for the integrated business flow metadata 600 that includes the business identifier.

[0120] If the display request includes a business flow identifier, the business data management server 100 references the business flow DB 321 to search for business flow metadata 500 that includes the business flow identifier, and acquires the business identifier from the business flow metadata 500. The business data management server 100 references the integrated business flow DB 322 to search for integrated business flow metadata 600 that includes the acquired business identifier.

[0121] The business data management server 100 presents, for example, a screen 1300 as shown in Fig. 13. The screen 1300 includes display fields 1301 and 1302.

[0122] The display field 1302 is a field that displays the business flow used when the integrated business flow was generated. The display field 1302 displays a business flow list 1320. The display field 1301 is a field that displays the integrated business flow. The display field 1301 displays a directed graph corresponding to the integrated business flow and operation buttons 1310. The operation buttons 1310 are operation buttons for setting search conditions for business flows.

[0123] When the operation button 1310 is operated, the business data management server 100 presents a screen 1400 as shown in Fig. 14. The screen 1400 includes setting fields 1401 and 1402.

[0124] The setting field 1401 is a field for selecting a node of an integrated business flow to be used in a search. The user selects a node to be used in a search by clicking on the node of the integrated business flow displayed in the setting field 1401.

[0125] The setting field 1402 is a field for setting the work nodes to be used in the search and the order of the work nodes included in the integrated node. The setting field 1402 includes an input field 1410 and operation buttons 1411 and 1412. The input field 1410 is a field for inputting the identifier of the work node to be used in the search. In this embodiment, the work nodes are set in the order of execution. The operation button 1411 is an operation button for adding to the input field 1410. The operation button 1412 is an operation button for instructing a search for a business flow.

[0126] The user can set search conditions using the screen 1400. When the user operates the operation button 1412, the terminal 101 transmits a search request including the search conditions to the business data management server 100 (step S505).

[0127] The business data management server 100 executes a business flow search process (step S506). The business flow search process will now be described. Fig. 15 is a flowchart illustrating an example of the business flow search process executed by the business data management server 100 according to the first embodiment.

[0128] The business data management server 100 identifies the business flow to be processed (step S601). Specifically, the business data management server 100 searches for business flow metadata 500 in which the value of the business identifier 601 of the integrated business flow metadata 600 is stored in the business identifier 501.

[0129] The business data management server 100 sets up a search business flow based on the search conditions (step S602). In the following description, the work nodes of the search business flow will be referred to as search work nodes.

[0130] The search workflow is generated from the operation nodes selected in the integrated workflow and the operation nodes selected in the integrated node.

[0131] The business data management server 100 starts loop processing of the business flow (step S603). Specifically, the business data management server 100 selects one business flow from the business flows identified in step S601.

[0132] The business data management server 100 determines whether the selected business flow includes all search operation nodes (step S604).

[0133] If the selected business flow does not include at least one search operation node, the business data management server 100 proceeds to step S608.

[0134] If the selected business flow includes all search work nodes, the business data management server 100 compares the order relationship of the search work nodes in the search business flow with the order relationship of the search work nodes in the selected business flow (step S605).

[0135] The business data management server 100 determines whether the order relationships match based on the comparison result (step S606).

[0136] If the order relationships do not match, the business data management server 100 proceeds to step S608.

[0137] If the order relationships match, the business data management server 100 registers the selected business flow in the list (step S607), and then proceeds to step S608.

[0138] In step S608, the business data management server 100 determines whether or not processing has been completed for all business flows identified in step S601 (step S608).

[0139] If the processing has not been completed for all the business flows identified in step S601, the business data management server 100 returns to step S603 and executes the same processing.

[0140] When processing has been completed for all the business flows identified in step S601, the business data management server 100 ends the business flow search process.

[0141] This concludes the explanation of the business flow search process. Returning to the explanation of FIG.

[0142] The business data management server 100 presents the business flows registered in the list in the business flow search process as search results (step S507). The business data management server 100 presents, for example, a screen 1600 as shown in FIG. 16. The screen 1600 includes display fields 1601 and 1602. The display field 1601 is a field for displaying the searched business flow. The display field 1602 is a field for displaying the searched business flow. The display field 1602 includes an operation button 1610. The operation button 1610 is an operation button for instructing the display of business data 400 related to the searched business flow.

[0143] When the operation button 1610 is operated, the terminal 101 transmits a business data display request including the business flow identification information. The business data management server 100 refers to the business flow DB 321 to identify business data 400 related to the business flow, retrieves the identified business data 400 from the business data DB 320, and presents it to the user.

[0144] According to the first embodiment, the business data management server 100 can present to the user an integrated workflow for searching for business flows with different orders of work nodes and different included work nodes. By using the integrated workflow, the user can easily set the conditions for the business flow to be searched (search workflow).

[0145] The business data management server 100 can also search for business flows based on the search business flow and present business data related to the business flow, thereby enabling analysis of work content and execution order for the purpose of improving business efficiency.

[0146] In the second embodiment, the method of setting the search workflow is different from that in the first embodiment. The second embodiment will be described focusing on the differences from the first embodiment.

[0147] The system configuration of the second embodiment is the same as that of the first embodiment. The configurations of the business data collection device 110 and the business data management server 100 of the second embodiment are the same as those of the first embodiment. The integrated business flow generation process of the second embodiment is the same as that of the first embodiment.

[0148] In the second embodiment, the method for setting a search workflow is different. Fig. 17 is a diagram showing an example of a screen presented by the business data management server 100 of the second embodiment. The screen 1400 of the second embodiment has some different setting items in the setting field 1402. Specifically, it includes an input field 1413 and an operation button 1414. The input field 1413 is a field for inputting the identifier of the work node to be excluded. The operation button 1414 is an operation button for adding the input field 1413.

[0149] FIG. 18 is a flowchart illustrating an example of a business flow search process executed by the business data management server 100 according to the first embodiment.

[0150] If the selected business flow includes all search operation nodes in step S604, the business data management server 100 determines whether the selected business flow includes an operation node to be excluded (step S651).

[0151] If the selected business flow includes the operation node to be excluded, the business data management server 100 proceeds to step S608.

[0152] If the selected business flow does not include the operation node to be excluded, the business data management server 100 proceeds to step S605.

[0153] The integrated node also includes an operation node that is not included in at least one workflow. Therefore, according to the second embodiment, it is possible to search for a workflow that does not include a specific operation.

[0154] The present invention is not limited to the above-described embodiments, but includes various modifications. For example, the above-described embodiments are provided to explain the present invention in detail, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, some of the configurations of each embodiment can be added to, deleted from, or replaced with other configurations.

[0155] Furthermore, some or all of the above-described configurations, functions, processing units, processing means, etc. may be implemented in hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that implements the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media for providing such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, solid-state drives (SSDs), optical disks, magneto-optical disks, CD-Rs, magnetic tape, non-volatile memory cards, and ROMs.

[0156] Furthermore, the program code that realizes the functions described in this embodiment can be implemented in a wide range of programming or scripting languages, such as assembler, C / C++, perl, Shell, PHP, Python, and Java.

[0157] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read and execute the program code stored in the storage means or the storage medium.

[0158] In the above-described embodiment, the control lines and information lines are those that are considered necessary for the explanation, and not all control lines and information lines are necessarily shown in the product. All components may be interconnected.

Claims

1. A computer system having a processor, a storage device connected to the processor, and a network interface connected to the processor, which holds, for each business flow that defines the procedures of a plurality of tasks, business data acquired in a business based on the business flow, manages the business flows as a directed graph with one task as one task node, compares the plurality of business flows, and generates an integrated node by performing at least one of the following processes based on the results of the comparison: a process of integrating the plurality of tasks having different order relationships between the business flows, and a process of integrating at least one task not included in the business flow with at least one task executed before the task and / or one task executed after the task; and generates a directed graph consisting of at least one task node and at least one integrated node that has not been integrated as an integrated business flow for searching the plurality of business flows, and presents the directed graph to a user.

2. A computer system as described in claim 1, which displays the integrated business flow and presents an interface for accepting conditions for searching the business flow, the interface including: a first setting field in which the user selects the work nodes and the integrated nodes to be used for the search from among the work nodes and the integrated nodes included in the integrated business flow; and a second setting field in which the user selects the work nodes to be used for the search from among the work nodes included in the integrated node and specifies the order of the selected work nodes, the computer system generating a search business flow consisting of search work nodes which are the work nodes selected in the first setting field and the second setting field, searching for the business flow which includes all of the search work nodes and in which the order of the search work nodes matches the order in the search business flow, presenting it to the user, and outputting the business data of the business flow specified by the user.

3. A computer system as claimed in claim 1, comprising: a first setting field in which the user selects the work nodes and the integrated nodes to be used for a search from among the work nodes and the integrated nodes included in the integrated business flow; a second setting field in which the user selects the work nodes to be used for a search from among the work nodes included in the integrated node and specifies the order of the selected work nodes; and a third setting field in which the user selects the work nodes not to be used for a search from among the work nodes included in the integrated node; said computer system generates a search work flow consisting of search work nodes which are the work nodes selected in the first setting field and the second setting field; searches for a work flow which does not include the work node selected in the third setting field, includes all of the search work nodes, and in which the order of the search work nodes matches the order in the search work flow, presents the search work flow to the user; and outputs the business data of the work flow specified by the user.

4. A search support method executed by a computer system, the computer system having a processor, a storage device connected to the processor, and a network interface connected to the processor, for each business flow defining the procedures of a plurality of tasks, retaining business data acquired in a business based on the business flow, and managing the business flows as a directed graph with one task as one task node, the search support method comprising the steps of: comparing the plurality of business flows by the computer system; generating an integrated node by the computer system executing at least one of a process of integrating the plurality of tasks having different order relationships between the business flows based on a result of the comparison and a process of integrating at least one task not included in the business flow with at least one task executed before the task and / or a task executed after the task; and generating a directed graph consisting of at least one of the unintegrated task nodes and at least one of the integrated nodes by the computer system as an integrated business flow for searching the plurality of business flows, and presenting the directed graph to a user.

5. A search support method according to claim 4, comprising: a step in which the computer system presents an interface on which the integrated business flow is displayed and which accepts conditions for searching the business flow, the interface comprising: a first setting field in which the user selects the work nodes and the integrated nodes to be used for a search from among the work nodes and the integrated nodes included in the integrated business flow; and a second setting field in which the user selects the work nodes to be used for a search from among the work nodes included in the integrated node and specifies an order of the selected work nodes, the search support method comprising: a step in which the computer system generates a search business flow consisting of search work nodes which are the work nodes selected in the first setting field and the second setting field; a step in which the computer system searches for the business flow which includes all of the search work nodes and in which the order of the search work nodes matches the order in the search business flow, and presents the search to the user; and a step in which the computer system outputs the business data of the business flow specified by the user.

6. A search support method according to claim 4, comprising: a step in which the computer system presents an interface in which the integrated workflow is displayed and which accepts conditions for searching the workflow, the interface comprising: a first setting field in which the user selects the work nodes and the integrated nodes to be used for a search from among the work nodes and the integrated nodes included in the integrated workflow; a second setting field in which the user selects the work nodes to be used for a search from among the work nodes included in the integrated node and specifies the order of the selected work nodes; and a third setting field in which the user selects the work nodes not to be used for a search from among the work nodes included in the integrated node, the search support method comprising: a step in which the computer system generates a search workflow composed of search work nodes which are the work nodes selected in the first setting field and the second setting field; a step in which the computer system searches for a workflow which does not include the work node selected in the third setting field, includes all of the search work nodes, and in which the order of the search work nodes matches the order in the search workflow, and presents the workflow to the user; a step of outputting, by the computer system, the business data of the business flow specified by the user.

Images