Business support systems, business support methods, and programs

Abstract

This system efficiently assists in identifying the cause of errors that occur in data linked between business systems. [Solution] The business support system comprises an error information collection unit that collects linked data when an error occurs in linked data which is linked data between multiple business systems, each of which performs business processing, and to which data identification information, trace tag information including data source information and destination information, and error-related information are attached; and an error estimation unit that estimates the linkage path and error location where the linkage error occurred, indicating an error related to the linked data, based on the trace tag information contained in the linked data collected by the error information collection unit.

Description

Technical Field

[0001] The present disclosure relates to a business support system, a business support method, and a program.

Background Art

[0002] In recent years, in systems related to power transmission services and the like, cooperation data is transmitted between a plurality of business systems, and processing is carried out in cooperation between the plurality of business systems. Further, a technique for efficiently supporting such a system is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the conventional technology as described above, for example, when an error occurs in cooperation data, it has been difficult to identify which business system is the cause.

[0005] The present disclosure has been made to solve the above problems, and an object thereof is to provide a business support system, a business support method, and a program that can efficiently support the identification of the cause when an error occurs in cooperation data between business systems.

Means for Solving the Problems

[0006] To solve the above problem, one aspect of the present disclosure is a business support system comprising: an error information collection unit that collects linked data when an error occurs in linked data which is linked data between multiple business systems, each of which performs business processing, and to which data identification information, trace tag information including data source information and destination information, and error-related information are attached; and an error estimation unit that estimates the linkage path and error location where a linkage error occurred, indicating an error related to the linked data, based on the trace tag information contained in the linked data collected by the error information collection unit.

[0007] Furthermore, one aspect of this disclosure is a business support method in which an error information collection unit collects linked data between multiple business systems, each of which performs business processing, when an error occurs in the linked data to which data identification information, trace tag information including data source information and destination information, and error-related information are attached, and an error estimation unit estimates the linked path and error location where the linked error occurred, indicating an error related to the linked data, based on the trace tag information contained in the linked data collected by the error information collection unit.

[0008] Furthermore, one aspect of this disclosure is a program that causes a computer to perform the following steps when an error occurs in the linked data between multiple business systems, each of which performs business processing, and to which data identification information, trace tag information including data source information and destination information, and error-related information are attached: an error information collection step which collects the linked data; and an error estimation step which estimates the linkage path and error location where the linkage error occurred, indicating an error related to the linked data, based on the trace tag information contained in the linked data collected by the error information collection step. [Effects of the Invention]

[0009] According to this disclosure, it is possible to efficiently support the identification of the cause when an error occurs in the linked data between business systems. [Brief explanation of the drawing]

[0010] [Figure 1] This is a diagram showing an example of a business support system according to this embodiment. [Figure 2] This figure shows an example of a data object for linked data in this embodiment. [Figure 3] This figure shows an example of the process for adding trace tag information to the business support system according to this embodiment. [Figure 4] This flowchart shows an example of the process for estimating the cause of a linkage error in the business support system according to this embodiment. [Figure 5] This figure shows an example of the output processing of output information of the business support system according to this embodiment. [Figure 6] This flowchart shows an example of the visualization process for statistical processing information of collaboration errors in the business support server in this embodiment. [Figure 7] This figure shows an example of how statistical processing information for linkage errors in the business support system according to this embodiment is displayed. [Figure 8] This flowchart shows an example of the visualization process for the business support server's interconnection path analysis information in this embodiment. [Figure 9] This figure shows an example of how the business support system according to this embodiment displays the integration path analysis information. [Figure 10] This flowchart shows a modified example of the process for estimating the cause of a linkage error in the business support system according to this embodiment. [Figure 11] This diagram illustrates an example of the hardware configuration of the server device described herein. [Figure 12] This diagram illustrates an example of the hardware configuration of the terminal device described herein. [Modes for carrying out the invention]

[0011] A business support system and a business support method according to one embodiment of this disclosure will be described below with reference to the drawings.

[0012] Figure 1 is a schematic block diagram showing the business support system 1 according to the present embodiment. As shown in Figure 1, the business support system 1 includes a business support server 10, a cooperation management server 20, a plurality of business systems 30, and an administrator terminal 40.

[0013] Note that the business support system 1 according to the present embodiment monitors a cooperation error indicating an error in cooperation data between a plurality of business systems 30 executed within, for example, the power transmission and distribution company 2, and when a cooperation error occurs, estimates the cooperation path and error location where the cooperation error occurred to support identifying the cause of the cooperation error.

[0014] Also, in the example shown in Figure 1, the plurality of business systems 30 include a business A system 31, a business B system 32, a business C system 33, and a CIS (Customer Information System) 34. Transmission of cooperation data is performed in the order of business A system 31 → business B system 32 → business C system 33 → CIS 34, and business processing is executed in each business system 30.

[0015] The business A system 31 is an external business system 30 of the power transmission and distribution company 2, and can be connected to the business support system 1 via a network NW2 which is an external network such as a WAN (Wide Area Network). The business A system 31 is composed of, for example, a server device and executes the business processing of "business A". The business A system 31 transmits the execution result of the business processing of "business A" as cooperation data to the business B system 32 via the cooperation management server 20.

[0016] The Business B System 32, the Business C System 33, and the CIS 34 are the internal business systems 30 of the power transmission and distribution operator 2. The Business B System 32, the Business C System 33, and the CIS 34 can be connected to the Business Support Server 10 and the Linkage Management Server 20 via a network NW1 which is a network within the enterprise of the power transmission and distribution operator 2 (for example, an enterprise internal LAN (Local Area Network)).

[0017] The Business B System 32 is composed of, for example, server devices and executes the business processes of "Business B". The Business B System 32 transmits the execution results of the business processes of "Business B" as linkage data to the Business C System 33 via the Linkage Management Server 20.

[0018] The Business C System 33 is composed of, for example, server devices and executes the business processes of "Business C". The Business C System 33 transmits the execution results of the business processes of "Business C" as linkage data to the CIS 34 via the Linkage Management Server 20.

[0019] The CIS 34 is composed of, for example, server devices and executes the business processes of "Customer Information Management" of the power transmission and distribution operator 2. The CIS 34 transmits the execution results of the business processes of "Customer Information Management" to an external system (not shown).

[0020] The administrator terminal 40 is a terminal device owned by the power transmission and distribution operator 2 and is the terminal device of an administrator who manages the business support system 1. The administrator terminal 40 is, for example, a personal computer, a tablet terminal, etc. The administrator terminal 40 can communicate with the business support server 10 via the network NW1. The administrator terminal 40 receives the output information (for example, the estimated results of linkage errors, or the statistical information of linkage errors, etc.) generated by the business support server 10 via the network NW1 and displays it on the display unit 43. The administrator terminal 40 includes a NW (Network) communication unit 41, an input unit 42, a display unit 43, a terminal control unit 44, and a terminal storage unit 45.

[0021] The NW communication unit 41 is a functional unit implemented by a communication device such as a network adapter. The NW communication unit 41 connects to the network NW1 and communicates with the business support server 10.

[0022] The input unit 42 is, for example, an input device such as a keyboard, mouse, or touch panel, and receives various information in response to the administrator's operation. The input unit 42 outputs the received information to the terminal control unit 44.

[0023] The display unit 43 is a display device such as a liquid crystal display, and displays various output information generated by the business support server 10 (for example, estimated causes of linkage errors, statistical information on linkage data, etc.). The terminal storage unit 45 stores various information used by the administrator terminal 40.

[0024] The terminal control unit 44 is a functional unit that is implemented, for example, by having a processor including a CPU (Central Processing Unit) execute a program stored in the terminal storage unit 45, and comprehensively controls the administrator terminal 40. The terminal control unit 44 connects to the business support server 10 via the network communication unit 41 and transmits the information received by the input unit 42 to the business support server 10. The terminal control unit 44 also displays the output information received from the business support server 10 via the network communication unit 41 on the display unit 43.

[0025] The integration management server 20 is a server device that manages integration data between multiple business systems 30 (business system A 31, business system B 32, business system C 33, and CIS 34). The collaborative management server 20 comprises a network communication unit 21, a server storage unit 22, and a server control unit 23.

[0026] The NW communication unit 21 is a functional unit implemented by a communication device such as a network adapter. The NW communication unit 21 connects to network NW1 and communicates with business system B 32, business system C 33, CIS 34, and business support server 10. The NW communication unit 21 also connects to network NW2 and communicates with business system A 31.

[0027] The server storage unit 22 stores various information used by the collaboration management server 20. The server storage unit 22 includes a collaboration history storage unit 221.

[0028] The linkage history storage unit 221 stores linkage history information of the linkage data managed by the business support system 1 as object-format data, as described later. For example, the linkage history storage unit 221 stores data identification information, which is uniquely assigned to object-format data, as linkage history information for the linkage data. The linkage history information is used to determine whether or not the linkage data has already been registered in the business support system 1 (data identification information has been assigned).

[0029] The server control unit 23 is a functional unit that is realized, for example, by causing a processor including a CPU to execute a program stored in the server storage unit 22. The server control unit 23 executes various processes of the cooperative management server 20. The server control unit 23 includes a cooperative management unit 231.

[0030] The integration management unit 231 checks the integration history information in the integration history storage unit 221 for integration data received from each business system 30. If it is new integration data, it assigns data identification information and registers it in the integration history storage unit 221. In addition, if the integration data is already registered, the integration management unit 231 updates the integration history information stored in the integration history storage unit 221.

[0031] Furthermore, the integration management unit 231 adds data identification information and trace tag information including data source information and destination information to the integration data, converts it into object-format data (hereinafter sometimes referred to as data object), and sends it to the destination (next stage) business system 30.

[0032] The Link Management Unit 231, for example, receives data in data object format sent from the source business system 30, adds source information corresponding to the source business system 30 and destination information corresponding to the next business system 30 that will execute the business process to the trace tag information, and sends the data in data object format with the added source and destination information to the destination business system 30.

[0033] Now, with reference to Figure 2, the objects of the linked data in this embodiment will be described. Figure 2 shows an example of a data object for linked data in this embodiment.

[0034] As shown in Figure 2, the data object of linked data includes data identification information, trace tag information, error-related information, and linked data information. The data object of linked data uses, for example, the JSON (JavaScript Object Notation) format, which can be described in the data structure.

[0035] Data identification information is identification information that identifies linked data and is uniquely assigned within the business support system 1. For example, data identification information is information obtained by assigning a serial number to a code (e.g., a two-character code) that indicates the source of the linked data. Data identification information may also include date and time information.

[0036] Furthermore, trace tag information is tag information used to trace the path (transmission path) through which the linked data was transmitted. Trace tag information includes source and destination information of the linked data that has passed through so far.

[0037] Furthermore, error-related information is information added by each business system 30 when a linkage error occurs during business processing in each business system 30. Error-related information includes, for example, the source system indicating the business system 30 from which the information was obtained, the location where the linkage error occurred (for example, on a module basis), the error code, the cause of the error, the date and time of the error, and the linkage data at the time the error occurred.

[0038] Furthermore, the linked data information includes the contents of the linked data output by each business system 30.

[0039] In the example shown in Figure 2, the data object of the linked data includes data identification information, trace tag information TG1, error-related information ER1, and linked data information. In this linked data data object, the data identification information is "XXXXXXXXX", and the trace tag information TG1 indicates that the source information, "Source 1", is "Business System A", "Source 2" is "Business System B", and "Source 3" is "Business System C".

[0040] Furthermore, the trace tag information TG1 indicates that the destination information, "Link 1," is "Business System B," "Link 2" is "Business System C," and "Link 3" is "CIS." Furthermore, it indicates that a linkage error has occurred, and error-related information ER1 has been added.

[0041] Returning to the explanation in Figure 1, for example, the linkage management unit 231, via the network communication unit 21, adds new data identification information to the linkage data received from business system A 31, and further generates a data object by adding business system A 31 to the source information and business system B 32 to the destination information. The linkage management unit 231 also stores the new data identification information, trace tag information, and linkage data in the linkage history storage unit 221. The linkage management unit 231 then transmits the generated linkage data object to the destination business system B 32 via the network communication unit 21.

[0042] Furthermore, for example, the Link Management Unit 231 adds the source information of the data object of the Link Data received from the Business System B 32 via the Network Communication Unit 21, and adds the destination information of the Business System C 33. The Link Management Unit 231 also updates the Link History Information in the Link History Storage Unit 221 corresponding to the said data identification information. Finally, the Link Management Unit 231 transmits the data object of the Link Data to the destination Business System C 33 via the Network Communication Unit 21.

[0043] Furthermore, for example, the Link Management Unit 231 adds the business system C 33 to the source information and the CIS 34 to the destination information of the data object of the linked data received from the business system C 33 via the NW communication unit 21. The Link Management Unit 231 also updates the link history information in the link history storage unit 221 corresponding to the data identification information. Finally, the Link Management Unit 231 transmits the data object of the linked data to the destination CIS 34 via the NW communication unit 21.

[0044] The business support server 10 is a server device that monitors linked data between multiple business systems 30 and, in the event of a linkage error, estimates the linkage path and location where the error occurred, or the cause of the linkage error. The business support server 10 comprises a network communication unit 11, a server storage unit 12, and a server control unit 13.

[0045] The NW communication unit 11 is a functional unit implemented by a communication device such as a network adapter. The NW communication unit 11 connects to network NW1 and communicates with business system B 32, business system C 33, CIS 34, the integration management server 20, and the administrator terminal 40. The NW communication unit 11 also connects to network NW2 and communicates with business system A 31.

[0046] The server storage unit 12 stores various types of information used by the business support server 10. The server storage unit 12 includes a module business-related information storage unit 121, a collaboration error history storage unit 122, an error statistics information storage unit 123, an estimated result storage unit 124, and an output information storage unit 125.

[0047] The module business-related information storage unit 121 stores information about the modules that execute business processes in each business system 30. The information stored in the module business-related information storage unit 121 is used when estimating the cooperation path and error location where a cooperation error occurred, or the cause of the cooperation error, as described later.

[0048] The linkage error history storage unit 122 stores the linkage data collected by the error information collection unit 131 (described later) as a history of linkage errors. For example, the linkage error history storage unit 122 stores the data objects of the linkage data collected by the error information collection unit 131 from each business system 30 when a linkage error occurred, as a history of linkage errors.

[0049] The error statistics information storage unit 123 stores error statistics information, which is the result of statistical processing based on the linked error history by the error statistics processing unit 133, described later. Details of the error statistics information will be described later.

[0050] The estimation result storage unit 124 stores the estimation results estimated by the error estimation unit 132, which will be described later. The estimation results include, for example, the communication path and location where the communication error occurred, or the cause of the communication error.

[0051] The output information storage unit 125 stores the output information generated by the output control unit 134, which will be described later. The output information is, for example, display information to be displayed on the display unit 43 of the administrator terminal 40, and may include, for example, the estimated result of a linkage error, or image information that visualizes error statistics.

[0052] The server control unit 13 is a functional unit that is realized, for example, by causing a processor including a CPU to execute a program stored in the server storage unit 12. The server control unit 13 executes various processes of the business support server 10. The server control unit 13 includes an error information collection unit 131, an error estimation unit 132, an error statistics processing unit 133, and an output control unit 134.

[0053] The error information collection unit 131 collects linked data when an error occurs in linked data between multiple business systems 30, each of which performs business processing, and which has data identification information, trace tag information including data source information and destination information, and error-related information attached to the linked data. The error information collection unit 131 monitors the linked data (data objects) of each business system 30 via the network communication unit 11 and collects the data objects in which the linked error occurred. The error information collection unit 131 stores the collected data objects in which the linked error occurred in the linked error history storage unit 122.

[0054] The error estimation unit 132 estimates the linkage path and error location where a linkage error occurred, based on the trace tag information included in the linkage data collected by the error information collection unit 131. The error estimation unit 132 estimates the linkage path and error location where the linkage error occurred, or the cause of the linkage error, based, for example, the data objects of the linkage data stored in the linkage error history storage unit 122 and the information stored in the module business-related information storage unit 121.

[0055] The error estimation unit 132 estimates the linkage path and error location (the business system 30 (module) where the linkage error occurred) based on the trace tag information and error-related information contained in the data object of the linked data, and the information about the module of the business system 30 stored in the module business-related information storage unit 121.

[0056] Furthermore, the error estimation unit 132 may estimate the cause of the linkage error based on the error-related information and information about the modules of the business system 30. The error estimation unit 132 stores the estimated result in the estimation result storage unit 124.

[0057] The error statistics processing unit 133 statistically processes the history of linkage errors stored in the linkage error history storage unit 122 to generate error statistics information (an example of statistical information) related to linkage errors. For example, the error statistics processing unit 133 generates an aggregated result as error statistics information, which is the number of linkage errors aggregated for each time period.

[0058] Furthermore, the error statistics processing unit 133 generates, for example, an aggregated result of the number of linked errors for each type of error, as error statistics information. The error statistics processing unit 133 stores the generated error statistics information (statistics information) in the error statistics information storage unit 123.

[0059] The output control unit 134 generates output information that visualizes the error statistics information generated by the error statistics processing unit 133. For example, the output control unit 134 generates output information that visualizes the aggregated results of the number of coordination errors for each time period (for example, a graph showing the number of coordination errors for each time period).

[0060] Furthermore, the output control unit 134 generates output information (for example, a pie chart) that visualizes the aggregated results, such as the number of linked errors for each type of error. Furthermore, the output control unit 134 generates output information that visualizes the communication path and error location where the communication error estimated by the error estimation unit 132 occurred.

[0061] Furthermore, the output control unit 134 may, for example, generate output information that visualizes detailed information of a collaboration error, including trace tag information and error-related information, in response to a request from the administrator terminal 40 (external terminal device) for visualization of detailed information of the collaboration error.

[0062] The output control unit 134 stores the generated output information in the output information storage unit 125. The output control unit 134 also transmits the generated output information (the output information stored in the output information storage unit 125) to, for example, the administrator terminal 40 via the NW communication unit 11, causing the administrator terminal 40 to display the output information on its display unit 43.

[0063] Next, the operation of the business support system 1 according to this embodiment will be described with reference to the drawings. Figure 3 shows an example of the process for adding trace tag information to the business support system 1 according to this embodiment.

[0064] As shown in Figure 3, first, business system A 31 sends the integration data to the integration management server 20 (step S101). Business system A 31 then sends the integration data to business system B 32, for example, to the integration management server 20.

[0065] Next, the integration management unit 231 of the integration management server 20 adds data identification information to the integration data and initially registers the data object (step S102). The integration management unit 231 adds data identification information to the integration data received from the business A system 31 via the NW communication unit 21 and stores it in the integration history storage unit 221 as new integration data.

[0066] Next, the Link Management Unit 231 adds source information and destination information to the data object (step S103). The Link Management Unit 231 generates a data object to which trace tag information is added, indicating that the source information is business system A 31 and the destination information is business system B 32.

[0067] Next, the integration management unit 231 sends the data object to the business system B 32 (step S104). The integration management unit 231 sends the data object of the integration data to the business system B 32 via the network communication unit 21.

[0068] Next, the business system B 32 executes the business process (step S105). The business system B 32 executes the business process for business B based on the linked data received from the business system A 31.

[0069] Next, business system B 32 sends the data object and destination information to the integration management server 20 (step S106). Business system B 32 sends the data object of the integration data destined for business system C 33 and destination information indicating business system C 33 to the integration management server 20.

[0070] Next, the integration management unit 231 adds source information and destination information to the data object (step S107). The integration management unit 231 receives the data object of the integration data from business system B 32 via the network communication unit 21 and generates a data object with trace tag information indicating that the source information is business system B 32 and the destination information is business system C 33.

[0071] The linkage management unit 231 determines whether the data identification information contained in the data object of the received linkage data is stored in the linkage history storage unit 221. If it is not stored, it registers the data identification information of the linkage data in the linkage history storage unit 221. If the data identification information of the linkage data is already registered, the linkage management unit 231 updates the linkage history corresponding to the linkage data.

[0072] Next, the integration management unit 231 sends the data object to the business C system 33 (step S108). The integration management unit 231 sends the data object of the integration data to the business C system 33 via the NW communication unit 21.

[0073] Next, the business system C 33 executes the business process (step S109). The business system C 33 executes the business process of business C based on the linked data received from the business system B 32.

[0074] Next, business system C 33 sends the data object and destination information to the integration management server 20 (step S110). Business system C 33 sends the data object of the integration data destined for CIS 34 and destination information indicating CIS 34 to the integration management server 20.

[0075] Next, the integration management unit 231 adds source information and destination information to the data object (step S111). The integration management unit 231 receives the data object of the integration data from the business C system 33 via the NW communication unit 21 and generates a data object to which trace tag information is added, indicating that the source information is the business C system 33 and the destination information is CIS 34.

[0076] The linkage management unit 231 determines whether the data identification information contained in the data object of the received linkage data is stored in the linkage history storage unit 221. If it is not stored, it registers the data identification information of the linkage data in the linkage history storage unit 221. If the data identification information of the linkage data is already registered, the linkage management unit 231 updates the linkage history corresponding to the linkage data.

[0077] Next, the integration management unit 231 sends the data object to the CIS 34 (step S112). The integration management unit 231 sends the data object of the integration data to the CIS 34 via the NW communication unit 21.

[0078] Next, CIS34 executes the business process (step S113). Based on the linked data received from business system C33, CIS executes the customer information management business process.

[0079] In this manner, the Link Management Unit 231 receives data in data object format sent from the source business system 30, adds source information corresponding to the source business system 30 and destination information corresponding to the next business system 30 that will execute the business process, to the trace tag information, and sends the data in data object format with the added source and destination information to the destination business system 30.

[0080] Furthermore, if a linkage error occurs, each business system 30 adds error-related information to the data object and sends it to the next business system 30 that will execute the next business process. In addition, each business system 30 stores the data object of the linked data used in the business process as linked data history information.

[0081] Next, with reference to Figure 4, the process for estimating the cause of the linkage error in the business support system 1 according to this embodiment will be described. Figure 4 is a flowchart showing an example of the process for estimating the cause of a linkage error in the business support system 1 according to this embodiment.

[0082] As shown in Figure 4, the business support server 10 of the business support system 1 first collects data objects of linked data from each business system 30 (step S201). The error information collection unit 131 of the business support server 10 collects data objects of linked data from each business system 30 (for example, business system B 32, business system C 33, and CIS 34, etc.) via the network communication unit 11.

[0083] Next, the error information collection unit 131 determines whether or not the error object contains error-related information (step S202). The error information collection unit 131 determines whether or not the data object of the collected linked data contains error-related information. If the error object contains error-related information (step S202: YES), the error information collection unit 131 proceeds to step S203. If the error object does not contain error-related information (step S202: NO), the error information collection unit 131 terminates the process.

[0084] In step S203, the error information collection unit 131 stores a data object containing error-related information in the linked error history storage unit 122.

[0085] Next, the error estimation unit 132 estimates the error path and error location based on the data object (step S204). The error estimation unit 132 estimates the error path and error location based on the data object containing error-related information stored in the linked error history storage unit 122 (the linked error data object). For example, the error estimation unit 132 estimates the error path and error location from the source information and destination information included in the trace tag information.

[0086] The error estimation unit 132 may also estimate the cause of the coordination error based on error-related information and information about each business system 30 module stored in the module business-related information storage unit 121.

[0087] Next, the error estimation unit 132 stores the estimation result in the estimation result storage unit 124 (step S205). After the processing in step S205, the error estimation unit 132 terminates the process of estimating the cause of the linkage error.

[0088] The processes described above from steps S201 to S205 are executed, for example, periodically or in response to a request from the administrator terminal 40.

[0089] Next, with reference to Figure 5, the output processing of output information of the business support system 1 according to this embodiment will be described. Figure 5 shows an example of the output processing of output information of the business support system 1 according to this embodiment.

[0090] As shown in Figure 5, the administrator terminal 40 of the business support system 1 sends an output request for output information to the business support server 10 (step S301). The terminal control unit 44 of the administrator terminal 40 sends an output request corresponding to the input information received from the administrator by the input unit 42 to the business support server 10 via the network communication unit 41.

[0091] Next, the business support server 10 generates output information in response to the output request (step S302). The output control unit 134 of the business support server 10 generates output information in response to the received output request via the NW communication unit 11. The output control unit 134 stores the generated output information in the output information storage unit 125.

[0092] Next, the output control unit 134 transmits the output information to the administrator terminal 40 (step S303). The output control unit 134 transmits, for example, the output information corresponding to the output request stored in the output information storage unit 125 to the administrator terminal 40 via the NW communication unit 11.

[0093] Next, the terminal control unit 44 displays the output information on the display unit 43 (step S304). The terminal control unit 44 displays the output information received from the business support server 10 via the NW communication unit 41 on the display unit 43.

[0094] Next, with reference to Figures 6-9, we will explain specific examples of the output processing (visualization processing) of the output information described above. Figure 6 is a flowchart showing an example of the visualization process for statistical processing information of collaboration errors in the business support server 10 in this embodiment. Figure 7 shows an example of the display of statistical processing information for linkage errors in the business support system 1 according to this embodiment.

[0095] As shown in Figure 6, the output control unit 134 of the business support server 10 determines whether or not it has received a request to output error statistics information (step S401). The output control unit 134 determines whether or not it has received a request to output error statistics information (for example, the number of coordination errors that occurred at each time) from the administrator terminal 40 via the NW communication unit 11. If the output control unit 134 has received a request to output error statistics information (step S401: YES), it proceeds to step S402. If the output control unit 134 has not received a request to output error statistics information (step S401: NO), it proceeds to step S404.

[0096] In step S402, the error statistics processing unit 133 of the business support server 10 generates error statistics information (referred to as "cooperation error statistics information" in Figure 6) from the information stored in the cooperation error history storage unit 122. The error statistics processing unit 133 statistically processes the history of cooperation errors stored in the cooperation error history storage unit 122 to generate cooperation error statistics information related to cooperation errors (for example, statistical information such as the number of cooperation errors occurring at each time). The error statistics processing unit 133 stores the generated cooperation error statistics information in the error statistics information storage unit 123.

[0097] Next, the output control unit 134 sends the output information, which visualizes the linkage error statistics, to the administrator terminal 40 for display (step S403). Based on the linkage error statistics stored in the error statistics storage unit 123, the output control unit 134 generates an image G1, for example, as shown in Figure 7(a), and sends it to the administrator terminal 40 via the NW communication unit 11.

[0098] Next, in step S404, the output control unit 134 determines whether or not it has received an additional output request. The output control unit 134 determines, via the NW communication unit 11, whether or not it has received an additional output request from the administrator terminal 40, for example, for the output of detailed error statistics information. If the output control unit 134 has received an additional output request (step S404: YES), it proceeds to step S405. If the output control unit 134 has not received an additional output request (step S404: NO), it returns to step S401.

[0099] In step S405, the output control unit 134 generates additional output information. The output control unit 134 generates, for example, an image G2 as shown in Figure 7(b), or an image G3 as shown in Figure 7(c).

[0100] Next, the output control unit 134 sends additional output information to the administrator terminal 40 for display (step S406). The output control unit 134 sends additional output information (such as image G2 in Figure 7(b) or image G3 in Figure 7(c)) to the administrator terminal 40 via the NW communication unit 11 for display on the display unit 43. After processing in step S406, the output control unit 134 returns to processing in step S401.

[0101] Here, we will explain an example of how error statistics information is displayed, referring to Figure 7. The example shown in Figure 7(a) is a graph illustrating the number of synchronization errors against a given time, as an example of displaying visualized error statistics.

[0102] The graph in image G1 shown in Figure 7(a) has time on the horizontal axis and the number of coordination errors on the vertical axis. Waveform W1 shows the relationship between the number of coordination errors and time.

[0103] In image G1 of Figure 7(a), when the administrator specifies point P1 as an additional output request via the input unit 42 of the administrator terminal 40, the output control unit 134 outputs image G2 as shown in Figure 7(b) and displays it on the display unit 43 of the administrator terminal 40.

[0104] As shown in image G2 of Figure 7(b), the output control unit 134 displays a pie chart GR1 classifying the coordination errors at point P1 on the display unit 43 as additional output information.

[0105] Furthermore, in image G2 of Figure 7(b), if the administrator specifies "Task A" as an additional output request via the input unit 42 of the administrator terminal 40, the output control unit 134 outputs image G3 as shown in Figure 7(c) and displays it on the display unit 43 of the administrator terminal 40.

[0106] As shown in image G3 of Figure 7(c), the output control unit 134 displays detailed information about the linkage error in "Task A" as additional output information on the display unit 43. Here, the detailed information about the linkage error includes, for example, the source system, the location of occurrence (per module), the error code, the cause of the occurrence, the date and time of occurrence, and the linkage data at the time the error occurred.

[0107] Figure 8 is a flowchart showing an example of the visualization process of the collaboration path analysis information of the business support server 10 in this embodiment. Figure 9 shows an example of the display of the linkage path analysis information of the business support system 1 according to this embodiment.

[0108] As shown in Figure 8, the output control unit 134 of the business support server 10 determines whether or not it has received an output request for linkage route analysis (step S501). The output control unit 134 determines whether or not it has received an output request for linkage route analysis (for example, the route of the linkage data and the estimated location of the linkage error) from the administrator terminal 40 via the NW communication unit 11. If the output control unit 134 has received an output request for linkage route analysis (step S501: YES), it proceeds to step S502. If the output control unit 134 has not received an output request for linkage route analysis (step S501: NO), it proceeds to step S504.

[0109] In step S502, the output control unit 134 generates collaborative path analysis information from the estimation results stored in the estimation result storage unit 124. For example, the output control unit 134 generates an image G4 as shown in Figure 9(a) as collaborative path analysis information. Alternatively, the output control unit 134 may generate collaborative path analysis information using the estimation results, the trace tag information of the collaborative error history, and the error-related information.

[0110] Next, the output control unit 134 transmits the coordinated route analysis information to the administrator terminal 40 for display (step S503). The output control unit 134 transmits an image G4, as shown in Figure 9(a), to the administrator terminal 40 via the NW communication unit 11.

[0111] Next, in step S504, the output control unit 134 determines whether or not it has received an additional output request. The output control unit 134 determines whether or not it has received an additional output request from the administrator terminal 40 via the NW communication unit 11, for example, an output of detailed information on the cooperation route. If the output control unit 134 has received an additional output request (step S504: YES), it proceeds to step S505. If the output control unit 134 has not received an additional output request (step S504: NO), it returns to step S501.

[0112] In step S505, the output control unit 134 generates additional output information. The output control unit 134 generates, for example, an image G5 as shown in Figure 9(b).

[0113] Next, the output control unit 134 sends additional output information to the administrator terminal 40 for display (step S506). The output control unit 134 sends additional output information (such as image G5 in Figure 9(b)) to the administrator terminal 40 via the NW communication unit 11 for display on the display unit 43. After processing in step S506, the output control unit 134 returns to processing in step S501.

[0114] Here, we will explain an example of how to display the interconnection route analysis information, referring to Figure 9. The display example of image G4 shown in Figure 9(a) shows the display example of visualized linkage path analysis information, including the linkage path of the linked data where a linkage error occurred and the estimated error locations (EP1, RP2). The output control unit 134 makes it possible to visually identify the estimated error locations EP1 of "CIS" and EP2 of "Business C System" as estimated error locations, for example, by hatching, coloring, etc.

[0115] Furthermore, in image G4 of Figure 9(a), if the administrator specifies "CIS" for error estimation location EP1 as an additional output request via the input unit 42 of the administrator terminal 40, the output control unit 134 outputs image G5 as shown in Figure 9(b) and displays it on the display unit 43 of the administrator terminal 40. If "Business C System" for error estimation location EP2 is specified, the output control unit 134 similarly outputs detailed information about "Business C System" as output information.

[0116] As shown in image G5 of Figure 9(b), the output control unit 134 displays detailed information about the linkage error in "CIS" as additional output information on the display unit 43. Here, the detailed information about the linkage error includes, for example, the source system, the location of occurrence (per module), the error code, the cause of the occurrence, the date and time of occurrence, and the linkage data at the time the error occurred.

[0117] Next, with reference to Figure 10, a modified example of the process for estimating the cause of a linkage error in the business support system 1 according to this embodiment will be described. Figure 10 is a flowchart showing a modified example of the process for estimating the cause of a linkage error in the business support system 1 according to this embodiment.

[0118] As shown in Figure 10, the business support server 10 of the business support system 1 first collects data objects of linked data from each business system 30 (step S601). The error information collection unit 131 of the business support server 10 collects data objects of linked data from each business system 30 (for example, business system B 32, business system C 33, and CIS 34, etc.) via the network communication unit 11.

[0119] Next, the error information collection unit 131 determines whether or not the error object contains error-related information (step S602). The error information collection unit 131 determines whether or not the data object of the collected linked data contains error-related information. If the error object contains error-related information (step S602: YES), the error information collection unit 131 proceeds to step S603. If the error object does not contain error-related information (step S602: NO), the error information collection unit 131 terminates the process.

[0120] In step S603, the error information collection unit 131 stores a data object containing error-related information in the linked error history storage unit 122.

[0121] Next, the error estimation unit 132 estimates the cause of the error based on the data object containing error-related information and a similar normal data object (step S604). The error estimation unit 132 obtains a similar normal data object from the relevant business system 30 via the NW communication unit 11. The error estimation unit 132 compares the similar normal data object with the data object containing error-related information to estimate the cause of the error.

[0122] Next, the error estimation unit 132 stores the estimation result in the estimation result storage unit 124 (step S605). After the processing in step S605, the error estimation unit 132 terminates the process of estimating the cause of the coordination error.

[0123] The processes described above from steps S601 to S605 are executed, for example, periodically or in response to a request from the administrator terminal 40.

[0124] As described above, the business support system 1 according to this embodiment comprises an error information collection unit 131 and an error estimation unit 132. The error information collection unit 131 collects linked data when an error occurs in linked data which is linked data between multiple business systems 30, each of which performs business processing, and to which data identification information, trace tag information including data source information and destination information, and error-related information are attached. The error estimation unit 132 estimates the linked path and error location where the linked error occurred, indicating an error in the linked data, based on the trace tag information contained in the linked data collected by the error information collection unit 131.

[0125] As a result, the business support system 1 according to this embodiment uses trace tag information, including data source and destination information, to estimate the linkage path and error location where the linkage error occurred. Therefore, when an error occurs in the linked data between business systems 30, it can efficiently help identify the cause.

[0126] Furthermore, the business support system 1 according to this embodiment includes a linkage error history storage unit 122, an error statistics processing unit 133, and an output control unit 134. The linkage error history storage unit 122 stores the linkage data collected by the error information collection unit 131 as a history of linkage errors. The error statistics processing unit 133 statistically processes the history of linkage errors stored in the linkage error history storage unit 122 to generate statistical information (error statistics information) related to linkage errors. The output control unit 134 generates output information that visualizes the statistical information generated by the error statistics processing unit 133.

[0127] As a result, the business support system 1 according to this embodiment visualizes statistical information (error statistics), making it easier to accurately grasp the status of collaboration errors and to more efficiently support the identification of the causes.

[0128] In this embodiment, the error statistics processing unit 133 generates an aggregated result as statistical information, which is the number of coordination errors aggregated for each time period. The output control unit 134 generates output information that visualizes the aggregated result of the number of coordination errors aggregated for each time period (see, for example, image G1 in Figure 7(a)).

[0129] As a result, the business support system 1 according to this embodiment visualizes the aggregated results of the number of linkage errors for each time period, making it easier to grasp the status of linkage errors more accurately and enabling more efficient support for identifying the causes.

[0130] In this embodiment, the error statistics processing unit 133 generates aggregated results as statistical information, which aggregate the number of linked errors for each type of error. The output control unit 134 generates output information (see, for example, image G2 in Figure 7(b)) that visualizes the aggregated results of the number of linked errors for each type of error.

[0131] As a result, the business support system 1 according to this embodiment visualizes the aggregated results of the number of linkage errors for each type of error, making it easier to accurately grasp the status of linkage errors and to more efficiently support the identification of the causes.

[0132] Furthermore, the business support system 1 according to this embodiment includes an output control unit 134 that generates output information (for example, see image G4 in Figure 9(a)) that visualizes the collaboration path and error location where the collaboration error estimated by the error estimation unit 132 occurred.

[0133] As a result, the business support system 1 according to this embodiment visualizes the collaboration path and error location where the collaboration error estimated by the error estimation unit 132 occurred, making it easier to grasp the situation of the collaboration error more accurately and enabling more efficient support for identifying the cause.

[0134] Furthermore, in this embodiment, the output control unit 134 generates output information (for example, image G3 in Figure 7(c) or image 5 in Figure 9(b)) that visualizes detailed information of the linkage error, including trace tag information and error-related information, in response to a request from the administrator terminal 40 (external terminal device) for visualization of detailed information of the linkage error.

[0135] As a result, the business support system 1 according to this embodiment visualizes detailed information about linkage errors, including race tag information and error-related information, making it easier to accurately grasp the status of linkage errors and to more efficiently support the identification of the cause.

[0136] In this embodiment, the linked data is transmitted between multiple business systems 30 as data object format data (for example, JSON format data) to which data identification information, trace tag information, and error-related information are attached to identify the linked data. The business support system 1 also includes a linkage management unit 231. The linkage management unit 231 receives the data object format data transmitted from the source business system 30, adds source information corresponding to the source business system 30 and destination information corresponding to the next business system 30 that will execute the business process to the trace tag information, and transmits the data object format data with the added source and destination information to the destination business system 30.

[0137] As a result, the business support system 1 according to this embodiment can easily add source information and destination information to trace tag information by using data in data object format, and can easily grasp the linkage path of linked data. Furthermore, the business support system 1 according to this embodiment includes a linkage management unit 231, which makes it easy to manage linked data using data in data object format that includes trace tag information.

[0138] Furthermore, in this embodiment, the error estimation unit 132 estimates the cause of the linkage error based on data in a data object format corresponding to the linkage error and data in a data object format that is similar to the linkage error and has completed successfully.

[0139] As a result, the business support system 1 according to this embodiment can easily detect abnormalities by using data in a data object format corresponding to a linkage error and data in a data object format that is similar to the linkage error but completed successfully.

[0140] Furthermore, the business support method according to this embodiment includes an error information collection step and an error estimation step. In the error information collection step, the error information collection unit 131 collects linked data between multiple business systems 30, each of which performs business processing, when an error occurs in the linked data to which data identification information, trace tag information including data source information and destination information, and error-related information are attached. In the error estimation step, the error estimation unit 132 estimates the linked path and error location where the linked error occurred, indicating an error in the linked data, based on the trace tag information included in the linked data collected by the error information collection unit 131.

[0141] As a result, the business support method according to this embodiment has the same effects as the business support system 1 described above, and can efficiently help identify the cause when an error occurs in the linked data between business systems 30.

[0142] Figure 11 is a diagram illustrating the hardware configuration of the server device in this disclosure. Figure 11 shows the hardware configuration of each server device in business support system 1 (business support server 10, integration management server 20, and server devices for each business system 30).

[0143] As shown in Figure 11, each server device of the business support system 1 (business support server 10, collaboration management server 20, and the server devices of each business system 30) is equipped with a communication device H11, memory H12, and processor H13.

[0144] Communication device H11 is a communication device that can connect to networks NW1 and NW2, such as a LAN card. Memory H12 is a storage device such as RAM, flash memory, or HDD, and stores various information and programs used by each server device (business support server 10, collaboration management server 20, and server devices of each business system 30).

[0145] Processor H13 is a processing circuit that includes, for example, a CPU. Processor H13 executes various processes for each server device (business support server 10, collaboration management server 20, and server devices for each business system 30) by executing programs stored in memory H12.

[0146] Figure 12 is a diagram illustrating an example of the hardware configuration of the terminal device in this disclosure. The terminal devices shown in Figure 12 represent the hardware configuration of each terminal device (administrator terminal 40) of the business support system 1.

[0147] As shown in Figure 12, each terminal device (administrator terminal 40) of the business support system 1 is equipped with a communication device H11, memory H12, processor H13, input device H14, and display H15.

[0148] Communication device H11 is a communication device that can connect to network NW1, such as a LAN card. Memory H12 is a storage device such as RAM, flash memory, or HDD, and stores various information and programs used by each terminal device (administrator terminal 40).

[0149] Processor H13 is a processing circuit that includes, for example, a CPU. Processor H13 executes various processes on each terminal device (administrator terminal 40) by running programs stored in memory H12.

[0150] The input device H14 is, for example, an input device such as a keyboard, mouse, or touch sensor, and accepts various inputs from each terminal device (administrator terminal 40).

[0151] Display H15 is a display device such as a liquid crystal display or an organic EL (Electro-Luminescence) display, and displays various output information from each terminal device (administrator terminal 40).

[0152] This disclosure is not limited to the embodiments described above and may be modified without departing from the spirit of this disclosure. For example, in the above embodiment, the business support server 10 and the collaboration management server 20 were described as being implemented as one server device each, but the system is not limited to this, and may be implemented as multiple devices, such as multiple server devices.

[0153] Furthermore, although the above embodiment describes an example in which the business support server 10 and the collaboration management server 20 are implemented as separate server devices, the invention is not limited to this. For example, the collaboration management server 20 may be included in the business support server 10, or some functions of the collaboration management server 20 or the business support server 10 may be implemented in other server devices.

[0154] Furthermore, in the above embodiment, an example of using JSON format data as an example of data object format for linked data was described, but it is not limited to this, and other data structure formats such as XML (Extensible Markup Language), YAML (Yet Another Markup Language), or CSV (Comma Separated Values) format may also be used.

[0155] Furthermore, while the above embodiment describes an example in which the error estimation unit 132 estimates the linkage path and location where the linkage error occurred, or the cause of the linkage error, it is not limited to this. The error estimation unit 132 may also estimate other items, such as suggesting countermeasures for the linkage error and suggestions for improving the business system based on past performance.

[0156] Furthermore, in the above embodiment, the statistical information generated by the error statistics processing unit is not limited to the examples described in the above embodiment, and other statistical information may be generated. Furthermore, in the above embodiment, the output information generated by the output control unit 134 is not limited to the example described in the above embodiment, and other output information may be generated.

[0157] Furthermore, although the above embodiment describes an example in which each business system 30 stores historical information of data objects of linked data, it is not limited to this, and the linked management server 20 may store and manage the historical information of data objects of linked data collectively. In this case, the error estimation unit 132 may use the historical information of data objects of linked data stored by the linked management server 20 to estimate the cause of the linked error.

[0158] Furthermore, each component of the aforementioned business support system 1 contains an internal computer system. The processing in each component of the aforementioned business support system 1 may be performed by recording a program for realizing the functions of each component onto a computer-readable recording medium, loading the program recorded on this recording medium into the computer system, and executing it. Here, "loading the program recorded on the recording medium into the computer system and executing it" includes installing the program into the computer system. Here, "computer system" includes the OS and hardware such as peripheral devices.

[0159] Furthermore, "computer system" may include multiple computer devices connected via a network, including communication lines such as the Internet, WAN, LAN, and dedicated lines. Also, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into the computer system. Thus, the recording medium storing the program may also be a non-transient recording medium such as a CD-ROM.

[0160] Furthermore, the recording medium includes internal or external recording media accessible from the distribution server for distributing the program. The program may be divided into multiple parts, downloaded at different times, and then combined in each configuration provided by the business support system 1, or each of the divided programs may be distributed by a different distribution server. Additionally, "computer-readable recording media" includes volatile memory (RAM) within a computer system that acts as a server or client when the program is transmitted over a network, which retains the program for a certain period of time. Moreover, the program may be intended to implement only a part of the functions described above. Furthermore, the program may be a so-called differential file (differential program) that can implement the functions described above in combination with a program already recorded in the computer system. [Explanation of Symbols]

[0161] 1...Business support system, 2...Power transmission and distribution company, 10...Business support server, 11,21,41...Network communication unit, 12,22...Server storage unit, 13,23...Server control unit, 30...Business system, 31...Business A system, 32...Business B system, 33...Business C system, 34...CIS, 40...Administrator terminal, 42...Input unit, 43...Display unit, 44...Terminal control unit, 45...Terminal storage unit, 121...Module business-related information storage unit, 122...Linkage error history storage unit, 123...Error statistics information storage unit, 124...Estimated result storage unit, 125...Output information storage unit, 131...Error information collection unit, 132...Error estimation unit, 133...Error statistics processing unit, 134...Output control unit, 221...Linkage history storage unit, 231...Linkage management unit, NW1,NW2...Network

Claims

1. An error information collection unit collects the linked data when an error occurs in the linked data, which is linked data between multiple business systems, each of which performs business processing, and to which data identification information, trace tag information including data source information and destination information, and error-related information is attached. Based on the trace tag information included in the linked data collected by the error information collection unit, an error estimation unit estimates the linked path and error location where a linked error occurred, indicating an error related to the linked data. A business support system equipped with the following features.

2. A linkage error history storage unit stores the linkage data collected by the error information collection unit as a history of the linkage errors, An error statistics processing unit statistically processes the history of the linkage errors stored in the linkage error history storage unit to generate statistical information related to the linkage errors, The output control unit generates output information that visualizes the statistical information generated by the error statistics processing unit. The business support system according to claim 1, comprising:

3. The error statistics processing unit generates an aggregated result as statistical information, which is the number of the linkage errors aggregated for each time period. The output control unit generates output information that visualizes the aggregated results obtained by aggregating the number of coordination errors for each time period. The business support system according to claim 2.

4. The error statistics processing unit generates an aggregated result as statistical information, which is the number of linked errors for each type of error. The output control unit generates output information that visualizes the aggregated results, which are obtained by aggregating the number of linked errors for each type of error. The business support system according to claim 2.

5. The output control unit generates output information that visualizes the communication path where the communication error estimated by the error estimation unit occurred and the location of the error. The business support system according to claim 1, comprising:

6. The output control unit generates output information that visualizes the detailed information of the linkage error, including the trace tag information and the error-related information, in response to a request from an external terminal device for visualization of the detailed information of the linkage error. A business support system according to any one of claims 2 to 5.

7. The linked data is transmitted between multiple business systems as data object format data to which data identification information, trace tag information, and error-related information are attached to identify the linked data. The system includes a linkage management unit that receives the data object format data sent from the source business system, adds the source information corresponding to the source business system and the destination information corresponding to the destination business system that will next execute the business process to the trace tag information, and sends the data object format data with the added source and destination information to the destination business system. A business support system according to any one of claims 1 to 5.

8. The error estimation unit estimates the cause of the linkage error based on the data in the data object format corresponding to the linkage error and the data in the data object format that is similar to the linkage error and has completed successfully. The business support system according to claim 7.

9. The error information collection unit collects linked data when an error occurs in linked data between multiple business systems, each of which performs business processing, and which includes data identification information, trace tag information including data source information and destination information, and error-related information. The error estimation unit estimates the collaboration path and error location where a collaboration error occurred, which indicates an error related to the collaboration data, based on the trace tag information included in the collaboration data collected by the error information collection unit. Business support methods.

10. On the computer, An error information collection step is performed when an error occurs in linked data between multiple business systems, each of which performs business processing, and the linked data includes data identification information, trace tag information including data source information and destination information, and error-related information. Based on the trace tag information included in the linked data collected by the error information collection step, an error estimation step is performed to estimate the linked path and error location where a linked error occurred, indicating an error related to the linked data. A program to execute.

Images