Data cooperation system, data cooperation method, and data cooperation program

Abstract

To obtain a data cooperation system that can flexibly change whether to permit an operation for cooperated data according to a customer.SOLUTION: A data cooperation system comprises: a data acquisition unit 10 that acquires pieces of data from a plurality of systems that output data; and a cooperation data management unit 12 that, on the basis of cooperation data attribute information indicating the authority of an operation performed by a customer for cooperation data in which the pieces of data from the plurality of systems are cooperated with each other, determines whether to permit the operation for the cooperation data performed by the customer who is a request source of the operation.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to a data linkage system, a data linkage method, and a data linkage program for linking data. [Background technology]

[0002] Multi-tenant services are known, which allow multiple customers to use a common system. Multi-tenant services eliminate the need for each customer to build a system that achieves the same functionality as the system in question. They also eliminate the need for the customer to operate and manage the system.

[0003] Also known is a data linkage system that acquires data from a plurality of systems that output data and links the acquired data.

[0004] Patent Document 1 discloses a multi-tenant database system in which data in a database is shared among multiple customers, and the data can be accessed instantly without copying the data. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] International Publication No. 2018 / 132478 Summary of the Invention [Problem to be solved by the invention]

[0006] In the database system of Patent Document 1, when data in the databases is linked, the linked data can be provided to each of multiple customers. According to the technology of Patent Document 1, the linked data can be provided by a multi-tenant service, but there is a demand for more flexible data control according to customer needs.

[0007] The present disclosure has been made in consideration of the above, and aims to provide a data linkage system that allows flexible switching depending on the customer as to whether or not to permit operations on linked data. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the objectives, the data integration system disclosed herein comprises a data acquisition unit that acquires data from each of a plurality of systems that output data, and an integrated data management unit that determines whether or not to allow a customer, who is the source of the operation, to operate on the integrated data based on integrated data attribute information that indicates the customer's authority to operate on the integrated data that is created by linking data from each of the plurality of systems. [Effects of the Invention]

[0009] The data linkage system according to the present disclosure has the advantage of being able to flexibly switch whether or not to permit operations on linked data depending on the customer. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 shows a data linkage system according to a first embodiment. [Figure 2] FIG. 1 is a diagram showing an example of the configuration of a data linkage device that realizes a data linkage system according to a first embodiment. [Figure 3] FIG. 1 is a diagram showing an example of link source data acquired by a data linkage device according to the first embodiment; [Figure 4] FIG. 10 is a diagram showing an example of data attribute information created by the data linkage apparatus according to the first embodiment; [Figure 5] FIG. 10 is a diagram showing an example of linkage definition information created by the data linkage apparatus according to the first embodiment; [Figure 6] FIG. 10 is a diagram showing an example of linked data attribute information created by the data linkage device according to the first embodiment; [Figure 7]10 is a flowchart showing an example of an operation procedure performed by a linked data management unit of the data linkage device according to the first embodiment; [Figure 8] FIG. 10 is a diagram showing an example of a time condition included in data attribute information in a data linkage device according to a second embodiment. [Figure 9] FIG. 10 is a diagram showing an example of a time condition included in linked data attribute information in a data linkage device according to a second embodiment. [Figure 10] FIG. 10 is a diagram showing a configuration example of a data linkage device that realizes a data linkage system according to a third embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a logical expression representing linked data attribute information in a data linkage device according to a third embodiment. [Figure 12] 10 is a flowchart showing an example of an operation procedure performed by a linked data management unit of a data linkage device according to a third embodiment. [Figure 13] FIG. 1 is a diagram showing an example of a hardware configuration for realizing a data linkage device according to first to third embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0011] A data linkage system, a data linkage method, and a data linkage program according to an embodiment will be described in detail below with reference to the accompanying drawings.

[0012] Embodiment 1 FIG. 1 is a diagram showing a data linkage system 1 according to a first embodiment. The data linkage system 1 acquires data from each of a plurality of systems that output data, and outputs linked data that links the acquired data. The monitoring and control system 2 and the inspection support system 3 shown in FIG. 1 are each an example of a system that outputs data. The monitoring and control system 2 monitors and controls equipment installed in a certain facility. The inspection support system 3 supports the inspection of the equipment installed in the facility. In the first embodiment, the facility is, for example, a factory, a plant, a water purification plant, a sewage treatment plant, a power plant, a river management facility, or a road management facility.

[0013] The monitoring and control system 2 monitors the equipment by periodically acquiring various data indicating the status of the equipment. The monitoring and control system 2 transmits monitoring data, which is data acquired for monitoring the equipment, to the data linkage system 1. The monitoring data includes values ​​detected by sensors installed in the equipment or values ​​indicating the electrical status of devices that make up the equipment.

[0014] The inspection support system 3 acquires various data collected by workers during equipment inspection work. The inspection support system 3 transmits inspection data, which is data acquired during inspection work, to the data linkage system 1. The inspection data includes values ​​obtained by workers visually inspecting instruments, results of workers determining the status of equipment on-site, and images taken by workers on-site. The inspection data may also include data acquired by processing images taken by workers on-site.

[0015] The data linkage system 1 receives monitoring data from the monitoring control system 2 and inspection data from the inspection support system 3. The data linkage system 1 creates linked data by linking the monitoring data and the inspection data with each other. The data linkage system 1 may also create linked data by processing the monitoring data and the inspection data. The data linkage system 1 provides the linked data to the inspection support service 4. In the first embodiment, linking data with each other means associating data with each other, aggregating data with each other, or processing data with each other.

[0016] The inspection support service 4 is a multi-tenant service that uses a system operated by a service provider to support the inspection work of facilities and the like for multiple customers. The customer is, for example, a business operator that operates a facility. As part of the support, the inspection support service 4 provides linked data to multiple customers. The service provider may also be a provider of a service that supports the maintenance and preservation of facilities and the like for customers. The inspection support service 4 may also be part of a service that supports the maintenance and preservation of facilities and the like.

[0017] In the above description, the data linkage system 1 acquires data from each of the individual systems, the monitoring and control system 2 and the inspection support system 3, and links the data. That is, the data linkage system 1 links data from each of the two individual systems. The data linkage system 1 may link data from each of three or more individual systems. The data linkage system 1 may link data from each of multiple individual systems, and the number of individual systems is arbitrary.

[0018] Furthermore, the individual system is not limited to the monitoring and control system 2 or the inspection support system 3. The individual system may be any system that outputs data, and is not limited to being installed in the above-mentioned facilities. The individual system may be, for example, a system that measures and analyzes the three-dimensional shape of a structure, or a system that supports the maintenance and preservation of a structure.

[0019] The data linkage system 1 may acquire open data such as weather data. The data linkage system 1 may link the open data with data acquired from individual systems. In this case, the provider of the open data is considered to be one of the multiple individual systems.

[0020] 2 is a diagram showing a configuration example of a data linkage device 5 that realizes the data linkage system 1 according to the first embodiment. Here, it is assumed that the data linkage system 1 shown in FIG. 1 is realized by a single device, the data linkage device 5.

[0021] Device 6 shown in Fig. 2 is a device included in monitoring control system 2 shown in Fig. 1. Device 7 shown in Fig. 2 is a device included in inspection support system 3 shown in Fig. 1. Device 8 shown in Fig. 2 is a device that constitutes a system for providing inspection support service 4 shown in Fig. 1. Each of devices 6, 7, and 8 is communicatively connected to data linkage device 5 via a network. The network is, for example, a WAN (Wide Area Network) such as the Internet. The network may also be a LAN (Local Area Network).

[0022] The data linkage device 5 includes a data acquisition unit 10 that acquires data from each of a plurality of systems that output data, a data storage unit 11 that stores the data, a linked data management unit 12 that manages linked data, a request receiving unit 13 that receives data requests, and a linked data transmission unit 14 that transmits linked data to the outside of the data linkage device 5. The data linkage device 5 also includes a linkage definition creation unit 15 that creates linkage definition information, a linkage definition information storage unit 16 that stores the linkage definition information, a data attribute information creation unit 17 that creates data attribute information, a data attribute information storage unit 18 that stores the data attribute information, a linked data attribute information creation unit 19 that creates linked data attribute information, and a linked data attribute information storage unit 20 that stores the linked data attribute information. Details of the linkage definition information, data attribute information, and linked data attribute information will be described later.

[0023] Device 6 transmits monitoring data to data linkage device 5. Device 7 transmits inspection data to data linkage device 5. Data acquisition unit 10 receives the monitoring data transmitted from device 6 and the inspection data transmitted from device 7. That is, data acquisition unit 10 acquires monitoring data output from monitoring control system 2 and inspection data output from inspection support system 3. Data acquisition unit 10 stores the acquired monitoring data and acquired inspection data in data storage unit 11. In the following description, the linkage source device refers to each of device 6 and device 7. Linkage source data is data acquired from the linkage source device and refers to each of the monitoring data and inspection data.

[0024] In the first embodiment, a customer is a party that receives the inspection support service 4. The customer can request the inspection support service 4 to perform operations on the linked data. Operations on the linked data refer to viewing the linked data or editing the linked data managed by the inspection support service 4. Editing the linked data refers to rewriting the linked data or deleting the linked data.

[0025] When a customer requests to view linked data, the customer notifies device 8 of the linked data that the customer requests to view. When a customer requests to edit linked data, the customer notifies device 8 of the linked data that the customer requests to edit. When a request is made to view linked data, device 8 transmits data request information indicating that viewing of linked data has been requested to data linkage device 5. When a request is made to edit linked data, device 8 transmits data request information indicating that editing of linked data has been requested to data linkage device 5. Device 8 also transmits information indicating the linked data that has been requested to be viewed or edited, and customer information indicating the customer who made the request, to data linkage device 5. The customer information is information for identifying each of multiple customers in data linkage device 5, and is, for example, a customer name or number.

[0026] The request receiving unit 13 receives data request information sent from the device 8. The request receiving unit 13 receives information indicating the linked data requested to be viewed or edited, and customer information indicating the customer who made the request. The request receiving unit 13 outputs the received information to the linked data management unit 12.

[0027] The linkage definition information is information that indicates the linkage mode when linking source data. Linkage definition information can also be said to be information that indicates the definition of linked data. Linkage definition information includes information that indicates the linkage source data to be linked together. Furthermore, linkage definition information for linked data created by processing the linkage source data includes processing information that indicates the content of the processing.

[0028] The linkage definition creation unit 15 has a GUI (Graphical User Interface) function. The linkage definition creation unit 15 accepts edits of the linkage definition information. The user edits the linkage definition information on the screen. The user is a person who uses the data linkage device 5. The linkage definition creation unit 15 creates the linkage definition information according to the edits made by the user. The linkage definition creation unit 15 stores the created linkage definition information in the linkage definition information storage unit 16. The linkage definition creation unit 15 may also modify the linkage definition information stored in the linkage definition information storage unit 16 through editing by the user.

[0029] Data attribute information indicates the customer's authorization to operate on data from each of multiple individual systems. An operation on the linked source data refers to viewing the linked source data or editing the linked source data. Editing the linked source data refers to rewriting the linked source data or deleting the linked source data.

[0030] The data attribute information creation unit 17 has a GUI function. The data attribute information creation unit 17 accepts editing of the data attribute information. The user edits the data attribute information on the screen. The data attribute information creation unit 17 creates data attribute information according to the editing by the user. The data attribute information creation unit 17 stores the created data attribute information in the data attribute information storage unit 18. The data attribute information storage unit 18 stores data attribute information for each of a plurality of customers. The data attribute information creation unit 17 may also modify the data attribute information stored in the data attribute information storage unit 18 through editing by the user.

[0031] The linked data attribute information indicates the customer's authorization to operate on linked data that is created by linking data from multiple individual systems. An operation on linked data refers to viewing or editing the linked data. Editing the linked data refers to rewriting or deleting the linked data.

[0032] The linked data attribute information creation unit 19 has a GUI function. The linked data attribute information creation unit 19 reads out data attribute information from the data attribute information storage unit 18 and displays the data attribute information on the screen. The linked data attribute information creation unit 19 presents the data attribute information on the screen and accepts editing of the linked data attribute information. The user refers to the displayed data attribute information and edits the linked data attribute information on the screen. The linked data attribute information creation unit 19 creates linked data attribute information in accordance with the editing by the user. The linked data attribute information creation unit 19 stores the created linked data attribute information in the linked data attribute information storage unit 20. The linked data attribute information storage unit 20 stores the linked data attribute information for each of the multiple customers.

[0033] The linked data attribute information creation unit 19 may create the linked data attribute information based on the data attribute information read from the data attribute information storage unit 18. The user may edit the linked data attribute information created based on the data attribute information to correct it. The linked data attribute information creation unit 19 stores the linked data attribute information corrected by the user's editing in the linked data attribute information storage unit 20. The linked data attribute information creation unit 19 may also correct the linked data attribute information stored in the linked data attribute information storage unit 20 through editing by the user.

[0034] Data request information is input to linked data management unit 12 from request receiving unit 13. Here, as an example, it is assumed that data request information indicating that a request to view linked data has been made is input to linked data management unit 12. Linked data management unit 12 also receives information indicating the linked data requested to be viewed and customer information indicating the customer who has requested the viewing.

[0035] Based on the customer information, the linked data management unit 12 reads linked data attribute information for the customer who requested the viewing from the linked data attribute information storage unit 20. Based on the linked data attribute information, the linked data management unit 12 determines whether or not to permit the customer who requested the operation to operate on the linked data. Here, the linked data management unit 12 determines whether or not to permit the customer who requested the viewing to view the linked data based on the linked data attribute information.

[0036] If the linked data attribute information indicates that the requested linked data can be operated on, the linked data management unit 12 determines to permit the client who requested the viewing to view the linked data. In this case, the linked data management unit 12 reads link definition information for the linked data requested to be viewed from the link definition information storage unit 16 based on the information indicating the linked data requested to be viewed. The linked data management unit 12 reads the link source data indicated in the link definition information from the data storage unit 11. The linked data management unit 12 creates linked data by linking the link source data. If the link definition information includes processing information, the linked data management unit 12 creates linked data by processing the read link source data. The linked data management unit 12 outputs the created linked data to the linked data transmission unit 14.

[0037] The linked data transmission unit 14 transmits the linked data created by the linked data management unit 12 to the device 8. The device 8 transmits the linked data to the customer who has requested the viewing.

[0038] On the other hand, if the linked data attribute information indicates that the requested linked data cannot be operated on, linked data management unit 12 outputs information indicating that viewing is not possible to linked data transmission unit 14. Linked data transmission unit 14 transmits information indicating that viewing is not possible to device 8. Device 8 notifies the customer who requested viewing that viewing is not possible.

[0039] When data request information indicating that editing of linked data has been requested is input to linked data management unit 12, information indicating the linked data for which editing has been requested and customer information indicating the customer who requested the editing are also input to linked data management unit 12. Based on the customer information, linked data management unit 12 reads linked data attribute information for the customer who requested the editing from linked data attribute information storage unit 20. Based on the linked data attribute information, linked data management unit 12 determines whether to permit editing of the linked data by the customer who requested the editing.

[0040] If the linked data attribute information indicates that the requested linked data can be operated on, the linked data management unit 12 decides to permit the client who requested the editing to edit the linked data. The linked data management unit 12 outputs information indicating that editing of the linked data is permitted to the linked data transmission unit 14. The linked data transmission unit 14 transmits information indicating that editing of the linked data is permitted to the device 8. The device 8 notifies the client who requested the editing that editing of the linked data is permitted. Thereafter, the device 8 transmits an instruction to edit the linked data to the data linkage device 5 in accordance with the instruction from the client. The request receiving unit 13 receives the editing instruction transmitted from the device 8. The request receiving unit 13 outputs the received editing instruction to the linked data management unit 12. The linked data management unit 12 edits the linked source data stored in the data storage unit 11 in accordance with the editing instruction. The data linkage device 5 edits the linked data by editing the linked source data in the linked data management unit 12 in accordance with the editing instruction.

[0041] On the other hand, if the linked data attribute information indicates that the requested linked data cannot be operated on, linked data management unit 12 outputs information indicating that editing is not possible to linked data transmission unit 14. Linked data transmission unit 14 transmits information indicating that editing is not possible to device 8. Device 8 notifies the client who requested the editing that editing is not possible.

[0042] Next, the details of the link source data will be explained. Fig. 3 is a diagram showing an example of link source data acquired by the data linkage device 5 according to the first embodiment. The link source data is data acquired from each of a plurality of individual systems, and is, for example, each of monitoring data and inspection data. "Data x", "Data y", "Data z", and "Data w" are each the data names of the link source data. The data names of the link source data are names used to identify each of the plurality of link source data in the data linkage device 5.

[0043] As shown in FIG. 3, in the coordination source data, the data name of the coordination source data is linked to the value of the coordination source data and the name of the coordination source device that output the coordination source data. "Device A" and "Device B" are names that represent the coordination source devices. "Device A" is the name of device 6. "Device B" is the name of device 7. In the example shown in FIG. 3, the value "3.2V" of "data x" and the value "10W" of "data y" are monitoring data acquired from device 6. In the example shown in FIG. 3, the value "OK" of "data z" and the value "NG" of "data w" are inspection data acquired from device 7.

[0044] Next, details of the data attribute information will be described. Fig. 4 is a diagram showing an example of data attribute information created by the data linkage device 5 according to the first embodiment. The data attribute information is information indicating the operation authority of a customer for the link source data. The data attribute information can also be said to be information defining the operation authority for data from individual systems. "Customer A," "Customer B," "Customer C," and "Customer D" are each the name of a customer. Fig. 4 shows an example of data attribute information for each of four customers.

[0045] As shown in FIG. 4, in the data attribute information, either "allowed" or "not allowed" information is linked to the data name of the linked source data. "Allowed" in FIG. 4 indicates that the customer can operate on the linked source data. "Not allowed" in FIG. 4 indicates that the customer cannot operate on the linked source data. In the example shown in FIG. 4, the data attribute information for "Customer A" indicates that operations on "Data x" are allowed, but operations on "Data y," "Data z," and "Data w" are not allowed.

[0046] In the data attribute information, either "OK" or "NO" is associated with all of the source data acquired from the multiple individual systems. The data linkage device 5 stores such data attribute information for all customers who receive the inspection support service 4 in the data attribute information storage unit 18.

[0047] The data attribute information may be such that "allowed" or "not allowed" is associated with each operation by a customer. The data attribute information may include information on "allowed" or "not allowed" regarding viewing of the linked source data and information on "allowed" or "not allowed" regarding editing of the linked source data. Furthermore, the information on editing of the linked source data in the data attribute information may include information on "allowed" or "not allowed" regarding rewriting of the linked source data and information on "allowed" or "not allowed" regarding deleting of the linked source data.

[0048] Data attribute information for a customer who is using the inspection support service 4 for the first time is added when the customer obtains an account for using the service. In addition, if a customer who has been using the inspection support service 4 deletes their account, the data attribute information for that customer is deleted.

[0049] Next, the details of the linkage definition information will be explained. Fig. 5 is a diagram showing an example of linkage definition information created by the data linkage device 5 according to the first embodiment. The linkage definition information is information indicating the manner in which data from multiple individual systems are linked together. The linkage definition information can also be said to be information that defines a method for linking source data. "Data a" and "data b" are each the data names of linked data. The data names of linked data are names used to identify each of the multiple linked data in the data linkage device 5.

[0050] As shown in Fig. 5, in the linkage definition information, the data name of the linked data is linked to each data name of the linked source data. In the example shown in Fig. 5, "data a" represents linked data in which "data x" and "data z" are linked together. "data b" represents linked data in which "data y" and "data w" are linked together.

[0051] In addition, in the linkage definition information for linked data created by processing the linkage source data, processing information is linked to the data name of the linked data. In the example shown in FIG. 5, "data b" represents linked data that has been processed by multiplying "data y" and "data w" together. The linkage definition information for "data b" includes the information "(data y) × (data w)" as processing information that indicates the content of the processing. In the example shown in FIG. 5, no processing information is linked to "data a." In other words, "data a" is linked data that simply aggregates "data x" and "data z," and "data x" and "data z" are not processed. Data linkage device 5 stores such linkage definition information for all linked data that may be subject to customer operations in linkage definition information storage unit 16.

[0052] Next, the linked data attribute information will be described in detail. Fig. 6 is a diagram showing an example of linked data attribute information created by the data linkage device 5 according to the first embodiment. The linked data attribute information is information indicating the authority of a customer to operate on the linked data. The linked data attribute information can also be said to be information that defines the operation authority for the linked data. Fig. 6 shows examples of linked data attribute information for each of "Customer A," "Customer B," "Customer C," and "Customer D."

[0053] As shown in FIG. 6, in the linked data attribute information, either "allowed" or "not allowed" information is associated with the data name of the linked data. "allowed" in FIG. 6 indicates that the customer can operate on the linked data. "not allowed" in FIG. 6 indicates that the customer cannot operate on the linked data. In the example shown in FIG. 6, the linked data attribute information for "Customer A" indicates that operations on each of the linked data "Data a" and "Data b" are allowed.

[0054] In the linked data attribute information, either "OK" or "NO" is associated with all linked data that can be operated by a customer. The data linkage device 5 stores such linked data attribute information for all customers who receive the inspection support service 4 in the linked data attribute information storage unit 20.

[0055] The linked data attribute information may be such that "Yes" or "No" is associated with each operation by a customer. The linked data attribute information may include information on "Yes" or "No" regarding viewing of linked data and information on "Yes" or "No" regarding editing of linked data. Furthermore, the information on editing of linked data in the linked data attribute information may include information on "Yes" or "No" regarding rewriting of linked data and information on "Yes" or "No" regarding deleting linked data.

[0056] The linked data attribute information for a customer who is using the inspection support service 4 for the first time is added when the customer obtains an account for using the service. In addition, if a customer who has been using the inspection support service 4 deletes their account, the linked data attribute information for the customer is deleted.

[0057] The linked data attribute information can be rewritten as needed by the user of the data linkage device 5. For example, conditions for allowing a customer to operate the linked data may be set in advance, and if the conditions are met, the operation of the linked data may be "allowed," and if the conditions are not met, the operation of the linked data may be "not allowed." An example of a condition is payment of a fee. Furthermore, when a customer pays a fee, the linked data attribute information for that customer may be added, and when the customer no longer pays the fee, the linked data attribute information for that customer may be deleted.

[0058] Next, an operation procedure performed by the data linkage device 5 will be described. Here, the operation procedure performed by the linked data management unit 12 will be mainly described. Fig. 7 is a flowchart showing an example of an operation procedure performed by the linked data management unit 12 of the data linkage device 5 according to the first embodiment.

[0059] Prior to the operation of the linked data management unit 12 according to the procedure shown in FIG. 7, the data acquisition unit 10 shown in FIG. 2 acquires linkage source data from each of the devices 6 and 7. That is, the data acquisition unit 10 acquires data from each of the multiple systems that output data. The data storage unit 11 stores the linkage source data acquired by the data acquisition unit 10. The linkage definition creation unit 15 creates linkage definition information. The linkage definition information storage unit 16 stores the linkage definition information created by the linkage definition creation unit 15. The data attribute information creation unit 17 creates data attribute information. The data attribute information storage unit 18 stores the data attribute information created by the data attribute information creation unit 17. The linked data attribute information creation unit 19 creates linked data attribute information. The linked data attribute information storage unit 20 stores the linked data attribute information created by the linked data attribute information creation unit 19.

[0060] When request receiving unit 13 receives data request information transmitted from device 8, it outputs the data request information to linked data management unit 12. As a result, in step S1, linked data management unit 12 acquires the data request information. Here, as an example, it is assumed that data request information indicating that viewing of linked data has been requested has been acquired.

[0061] When request receiving unit 13 receives information indicating the requested linked data and customer information indicating the requesting customer, transmitted from device 8, it outputs the information indicating the requested linked data and the customer information indicating the requesting customer to linked data management unit 12. As a result, in step S2, linked data management unit 12 acquires the information indicating the requested linked data and the customer information indicating the requesting customer.

[0062] In step S3, the linked data management unit 12 reads the linked data attribute information of the customer indicated in the customer information acquired in step S2 from the linked data attribute information storage unit 20. In step S4, the linked data management unit 12 determines whether the customer has the authority to view the requested linked data based on the linked data attribute information read in step S3.

[0063] If the customer has the authority to view the requested linked data (step S4, Yes), the linked data management unit 12 proceeds to step S5. On the other hand, if the customer does not have the authority to view the requested linked data (step S4, No), the linked data management unit 12 proceeds to step S10.

[0064] In step S5, the linked data management unit 12 reads out the linkage definition information of the requested linked data from the linkage definition information storage unit 16. In step S6, the linked data management unit 12 reads out from the data storage unit 11 the linkage source data whose data name is indicated in the linkage definition information read out in step S5.

[0065] In step S7, the linked data management unit 12 determines whether or not the linkage definition information read in step S5 includes processing information. If the linkage definition information includes processing information (step S7, Yes), the linked data management unit 12 proceeds to step S8. On the other hand, if the linkage definition information does not include processing information (step S7, No), the linked data management unit 12 proceeds to step S11.

[0066] In step S8, the linked data management unit 12 processes the link source data in accordance with the processing information. Then, in step S9, the linked data management unit 12 outputs the linked data, which is the data generated by the processing in step S8, to the linked data transmission unit 14. That is, the linked data management unit 12 outputs the data generated by processing the link source data as linked data.

[0067] In step S11, the linked data management unit 12 outputs linked data, which is a combination of link source data, to the linked data transmission unit 14. That is, the linked data management unit 12 outputs the combination of link source data as linked data.

[0068] The linked data transmission unit 14 acquires the linked data output from the linked data management unit 12 in step S9 or step S11. The linked data transmission unit 14 transmits the acquired linked data to the device 8. As a result, the data linkage device 5 transmits the linked data to the device 8 if the customer has the authority to view the requested linked data.

[0069] In step S10, the linked data management unit 12 outputs information indicating that viewing is not permitted to the linked data transmission unit 14. The linked data transmission unit 14 transmits the information indicating that viewing is not permitted to the device 8. As a result, if the customer does not have the authority to view the requested linked data, the data linkage device 5 transmits information indicating that viewing is not permitted to the device 8.

[0070] According to the first embodiment, the data linkage system 1 includes a data acquisition unit 10 that acquires data from each of a plurality of systems that output data, and a linked data management unit 12 that determines whether to permit a customer, who is requesting the operation, to operate on the linked data, based on linked data attribute information that indicates the customer's authorization to operate on the linked data obtained by linking data from each of the plurality of systems. The data linkage system 1 can flexibly switch whether to permit an operation on the linked data based on the linked data attribute information. This allows the data linkage system 1 to flexibly switch whether to permit an operation on the linked data depending on the customer.

[0071] The data linkage system 1 also includes a linked data attribute information creation unit 19 that creates linked data attribute information. This allows the data linkage system 1 to determine whether or not to permit a customer to operate on the linked data, based on the linked data attribute information created by the linked data attribute information creation unit 19.

[0072] In addition, the linked data attribute information creation unit 19 presents data attribute information indicating the customer's authorization to operate on data from each of the multiple systems, and accepts editing of the linked data attribute information. This allows the data linkage system 1 to determine whether to permit the customer to operate on the linked data, based on the linked data attribute information edited by referring to the data attribute information.

[0073] Embodiment 2 In the second embodiment, an example will be described in which the data linkage system 1 determines whether to permit an operation on the linked data depending on the date and time when the request for the operation on the linked data from the requesting customer is received. The data linkage system 1 according to the second embodiment is realized by a configuration similar to that of the data linkage device 5 shown in FIG.

[0074] In the second embodiment, the linked data attribute information includes a time condition, which is a date and time condition for when a customer is permitted to perform an operation on the linked data. For example, a user of the data linkage device 5 inputs the time condition to the linked data attribute information creation unit 19. As a result, the linked data attribute information creation unit 19 creates linked data attribute information including the time condition.

[0075] The linked data management unit 12 permits the operation by the requester when the date and time when the request for operation on the linked data by the requesting client is accepted satisfies the time condition included in the linked data attribute information.

[0076] The time condition may be included in the data attribute information. In this case, the time condition, which is the condition on the date and time when a customer is permitted to operate on data from each of the multiple individual systems, is included in the data attribute information. For example, a user inputs the time condition to the data attribute information creation unit 17. As a result, the data attribute information creation unit 17 creates data attribute information including the time condition.

[0077] In this case, the linked data attribute information creation unit 19 reads out the data attribute information including the timing conditions from the data attribute information storage unit 18 and displays the data attribute information including the timing conditions on the screen. Hereinafter, the timing conditions for the linked source data refer to the timing conditions included in the data attribute information. The timing conditions displayed on the screen are the timing conditions for the linked source data.

[0078] The user refers to the timing conditions for the linked source data and inputs the contents of the timing conditions to be included in the linked data attribute information to linked data attribute information creation unit 19. In this way, linked data attribute information creation unit 19 presents the timing conditions for the linked source data and accepts editing of the linked data attribute information. As a result, linked data attribute information creation unit 19 creates linked data attribute information including the timing conditions.

[0079] Next, the details of the time conditions included in the data attribute information will be described. Fig. 8 is a diagram showing an example of the time conditions included in the data attribute information in the data linkage device 5 according to the second embodiment. Fig. 8 shows an example of the time conditions included in the data attribute information for "Customer A."

[0080] In the example shown in FIG. 8, the data attribute information for "data x" includes information indicating a time condition, "24 / 01 / 01~30 / 12 / 31." This indicates that the period during which "customer A" is permitted to operate on "data x" is from January 1, 2024 to December 31, 2030. Furthermore, in the example shown in FIG. 8, the data attribute information for "data y," "data z," and "data w" does not include a time condition.

[0081] The data attribute information may consist of, for example, only a time condition, or may be a combination of a time condition and "OK" or "NG" information as shown in FIG.

[0082] Next, the details of the timing conditions included in the linked data attribute information will be described. Fig. 9 is a diagram showing examples of timing conditions included in the linked data attribute information in the data linkage device 5 according to embodiment 2. Fig. 9 shows examples of timing conditions included in the linked data attribute information for "Customer A."

[0083] In the example shown in FIG. 9, the linked data attribute information for "data a" includes information "24 / 01 / 01~28 / 12 / 31" indicating a time condition. This indicates that the period during which "customer A" is permitted to operate on "data a" is from January 1, 2024 to December 31, 2028. In addition, in the example shown in FIG. 9, the linked data attribute information for "data b" includes information "Monday and Tuesday" indicating a time condition. This indicates that the days during which "customer A" is permitted to operate on "data b" are Monday and Tuesday.

[0084] The linked data attribute information may consist of, for example, only a time condition. Alternatively, the linked data attribute information may be a combination of a time condition and "OK" or "NG" information as shown in FIG. 6.

[0085] The manner in which the time condition included in the data attribute information or the linked data attribute information is specified is not limited to the above example and may be any. The time condition may be specified, for example, by a time period within a day. By setting different time periods for each customer as the time condition, the data linkage device 5 may distribute access to the data linkage device 5 in response to requests from customers.

[0086] Next, a procedure of operations performed by the data linkage system 1 according to the second embodiment will be described. Here, the operations performed by the linked data management unit 12 that are different from those in the first embodiment will be mainly described. Also, the flowchart in FIG. 7 will be referred to as appropriate.

[0087] The linked data management unit 12 performs the same operations as steps S1 and S2 shown in FIG. 7, and then proceeds to step S3. In step S3, the linked data management unit 12 reads out the linked data attribute information of the customer indicated in the customer information acquired in step S2 from the linked data attribute information storage unit 20. The linked data attribute information includes a time condition. Here, the linked data attribute information consists only of a time condition.

[0088] In step S4, the linked data management unit 12 determines whether the customer has the authority to view the requested linked data based on the linked data attribute information read in step S3. The linked data management unit 12 determines whether the date and time when the request to view the linked data from the requesting customer is received satisfies the time condition included in the linked data attribute information.

[0089] If the date and time when the viewing request was received satisfies the time condition, the linked data management unit 12 determines that the customer has the authority to view the requested linked data (step S4, Yes). In this case, the linked data management unit 12 proceeds to step S5. On the other hand, if the date and time when the viewing request was received does not satisfy the time condition, the linked data management unit 12 determines that the customer does not have the authority to view the requested linked data (step S4, No). In this case, the linked data management unit 12 proceeds to step S10. In the second embodiment, the linked data management unit 12 performs the same operations as steps S5 to S11 shown in FIG. 7.

[0090] According to the second embodiment, the linked data attribute information includes a time condition, which is a date and time condition for when a customer is permitted to operate on the linked data. The linked data management unit 12 permits the requester to perform the operation if the date and time at which the requester's request to operate on the linked data is accepted satisfies the time condition. This allows the data linkage system 1 to determine whether to permit the operation on the linked data depending on the date and time at which the requester's request to operate on the linked data is accepted.

[0091] Embodiment 3 In the third embodiment, an example will be described in which the data linkage system 1 determines whether or not to permit an operation on linked data by citing the operation authority of the linkage source data. FIG. 10 is a diagram showing an example of the configuration of a data linkage device 5A that realizes the data linkage system 1 according to the third embodiment. Here, it is assumed that the data linkage system 1 according to the third embodiment is realized by a single device, the data linkage device 5A. In the third embodiment, the same components as those in the first or second embodiment are denoted by the same reference numerals, and the configuration that differs from the first or second embodiment will be mainly described.

[0092] The data linkage device 5A has the same components as the data linkage device 5 shown in Fig. 2. The data linkage device 5A differs from the data linkage device 5 shown in Fig. 2 in that the data attribute information held in the data attribute information holding unit 18 is read by the linked data management unit 12.

[0093] In the third embodiment, the linked data attribute information is represented by a logical expression including a variable representing the presence or absence of an operation authority for the linked source data. That is, the linked data attribute information is represented by an expression including a variable representing the presence or absence of an operation authority for data from each of a plurality of systems. For example, a user of the data linkage device 5A inputs the logical expression to the linked data attribute information creation unit 19. As a result, the linked data attribute information creation unit 19 creates the linked data attribute information represented by the logical expression.

[0094] Based on the customer information, the linked data management unit 12 reads from the linked data attribute information storage unit 20 a logical formula that represents the linked data attribute information for the customer who requested the operation. The variables included in the logical formula represent whether or not the user has permission to perform an operation on the linked source data, and are associated with the data name of the linked source data. The linked data management unit 12 reads from the data attribute information storage unit 18 data attribute information that corresponds to the data name of the linked source data indicated by the variables in the logical formula. The linked data management unit 12 calculates the logical formula by substituting the read data attribute information for the variables in the logical formula. The linked data management unit 12 determines whether or not to permit the operation by the requester based on the result of calculating the logical formula. In this way, the linked data management unit 12 determines whether or not to permit the operation by the requester by calculating the logical formula included in the linked data attribute information.

[0095] Next, details of the logical formula representing the linked data attribute information will be described. Fig. 11 is a diagram showing an example of a logical formula representing the linked data attribute information in the data linkage device 5A according to embodiment 3. Fig. 11 shows examples of logical formulas for each of "Customer A," "Customer B," "Customer C," and "Customer D."

[0096] In the example shown in FIG. 11, the logical formula representing the linked data attribute information for "data a" is the formula "(variable X) × (variable Z)". "Variable X" is a variable representing whether or not there is authority to operate on "data x", which is the source data to be linked. "Variable Z" is a variable representing whether or not there is authority to operate on "data z", which is the source data to be linked. In other words, the logical formula is the logical product of information indicating whether or not there is authority to operate on "data x" and information indicating whether or not there is authority to operate on "data z". In the example shown in FIG. 11, the logical formula is common to all of "Customer A", "Customer B", "Customer C", and "Customer D".

[0097] In the example shown in FIG. 11, the logical formula representing the linked data attribute information for "data b" is the formula "(variable Y) + (variable W)". "Variable Y" is a variable representing whether or not there is authority to operate on "data y", which is the source data to be linked. "Variable W" is a variable representing whether or not there is authority to operate on "data w", which is the source data to be linked. In other words, the logical formula is the logical sum of information indicating whether or not there is authority to operate on "data y" and information indicating whether or not there is authority to operate on "data w". In the example shown in FIG. 11, the logical formula is common to all of "Customer A", "Customer B", "Customer C", and "Customer D".

[0098] For example, when "Customer A" requests to view "Data a," which is linked data, the linked data management unit 12 reads the formula "(Variable X) × (Variable Z)" representing the linked data attribute information for "Data a" of "Customer A" from the linked data attribute information storage unit 20. The linked data management unit 12 also reads, for "Customer A," from the data attribute information storage unit 18 the data attribute information for "Data x" and "Data z," which are indicated by "Variable X" and "Variable Z," which are variables in the logical formula.

[0099] For example, as shown in Figure 4, assume that for "Customer A," the data attribute information of "Data x" is "OK" and the data attribute information of "Data z" is "NO." The linked data management unit 12 assigns "OK" to "Variable X" of "(Variable X) x (Variable Z)" and "NO" to "Variable Z," thereby obtaining the calculation result of the logical formula, "NO." In this case, the linked data management unit 12 determines that "Customer A" is not permitted to view "Data a."

[0100] Furthermore, for example, when "Customer B" requests to view "Data b," which is linked data, the linked data management unit 12 reads the formula "(Variable Y)+(Variable W)" representing the linked data attribute information for "Data b" of "Customer B" from the linked data attribute information storage unit 20. The linked data management unit 12 also reads, for "Customer B," from the data attribute information storage unit 18 the data attribute information for "Data y" and data attribute information for "Data w," which are indicated by "Variable Y" and "Variable W," which are variables in the logical formula.

[0101] For example, as shown in Figure 4, assume that for "Customer B," the data attribute information of "Data y" is "OK" and the data attribute information of "Data w" is "NO." The linked data management unit 12 assigns "OK" to "Variable Y" of "(Variable Y) + (Variable W)" and "NO" to "Variable W," thereby obtaining the calculation result of the logical formula, "OK." In this case, the linked data management unit 12 determines that "Customer B" is permitted to view "Data b."

[0102] In the above, the operation authority for multiple customers is defined by a common logical formula in each linked data, but the operation authority for each customer may be defined by a different logical formula. Also, in the third embodiment, the formula representing the linked data attribute information is not limited to the logical formula described here and may be any formula.

[0103] Next, an operation procedure of the data linkage system 1 according to the third embodiment will be described. Here, the operation of the linked data management unit 12 that is different from that of the first embodiment will be mainly described. Fig. 12 is a flowchart showing an example of an operation procedure of the linked data management unit 12 of the data linkage device 5A according to the third embodiment.

[0104] Steps S1 and S2 shown in Fig. 12 are the same as steps S1 and S2 shown in Fig. 7. Here, as an example, it is assumed that data request information indicating a request to view linked data is acquired in step S1. The procedure shown in Fig. 12 includes steps S21 to S23 instead of step S3 shown in Fig. 7.

[0105] In step S21, the linked data management unit 12 reads a logical formula, which is linked data attribute information of the customer indicated in the customer information acquired in step S2, from the linked data attribute information storage unit 20. In step S22, the linked data management unit 12 reads data attribute information of the linked source data indicated in the logical formula read in step S21 from the data attribute information storage unit 18. That is, the linked data management unit 12 reads data attribute information corresponding to the data name of the linked source data indicated by the variable of the logical formula from the data attribute information storage unit 18.

[0106] In step S23, the linked data management unit 12 calculates the logical formula read out in step S21. The linked data management unit 12 calculates the logical formula by substituting the information indicating whether or not the operation has authority, which is the data attribute information read out in step S22, into the logical formula.

[0107] In step S4, the linked data management unit 12 determines whether the customer has the authority to view the requested linked data. If the calculation result in step S23 is "Yes," the linked data management unit 12 determines that the customer has the authority to view the requested linked data. On the other hand, if the calculation result in step S23 is "No," the linked data management unit 12 determines that the customer does not have the authority to view the requested linked data. Steps S5 to S11 shown in FIG. 12 are the same as steps S5 to S11 shown in FIG. 7.

[0108] According to the third embodiment, the linked data attribute information is expressed by an equation including variables that indicate whether each of the multiple systems has permission to operate on the data. The linked data management unit 12 calculates the equation to determine whether to permit the operation by the requester. This allows the data linkage system 1 to determine whether to permit the operation on the linked data by citing the operation permission of the linked source data.

[0109] Next, a hardware configuration for realizing the data linkage apparatus 5, 5A according to the first to third embodiments will be described. Fig. 13 is a diagram showing an example of a hardware configuration for realizing the data linkage apparatus 5, 5A according to the first to third embodiments. The data linkage apparatus 5, 5A is realized by a computer system including a processing circuit 30, a communication device 31, an input device 34, and a display device 35. The processing circuit 30 includes a processor 32 and a memory 33. The processing circuit 30 is a circuit on which the processor 32 executes software.

[0110] The processing functions of each of the data acquisition unit 10, linked data management unit 12, request receiving unit 13, linked data transmission unit 14, linked definition creation unit 15, data attribute information creation unit 17, and linked data attribute information creation unit 19 shown in Figure 2 or Figure 10 are realized by software, firmware, or a combination of software and firmware.

[0111] The software or firmware is written as a program and stored in memory 33. In the processing circuit 30, the processor 32 reads and executes the program stored in memory 33, thereby realizing the above-mentioned processing functions of the data linkage apparatus 5, 5A. That is, the processing circuit 30 includes memory 33 for storing a data linkage program, which is a program that results in the processing of the data linkage apparatus 5, 5A being executed. In addition, the data linkage program stored in memory 33 can also be said to cause a computer to execute the procedures and methods of the data linkage apparatus 5, 5A.

[0112] The processor 32 is a CPU (Central Processing Unit), a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, a processor, or a DSP (Digital Signal Processor). The memory 33 is, for example, a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory), a magnetic disk, a flexible disk, an optical disk, a compact disk, a minidisk, or a DVD (Digital Versatile Disc). The data storage unit 11, the linkage definition information storage unit 16, the data attribute information storage unit 18, and the linked data attribute information storage unit 20 are each realized by the memory 33.

[0113] The communication device 31 communicates with devices external to the data linkage devices 5 and 5 A. The communication functions of the data acquisition unit 10, the request reception unit 13, and the linkage data transmission unit 14 are realized by the communication device 31.

[0114] The input device 34 is a device operated by a user of the data linkage device 5, 5A to input information. The input device 34 includes, for example, a keyboard, a mouse, a keypad, or a touch panel. The display device 35 is a device that displays information. The display device 35 is, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display. The GUI functions of each of the linkage definition creation unit 15, the data attribute information creation unit 17, and the linked data attribute information creation unit 19 are realized by the input device 34 and the display device 35.

[0115] The data linkage devices 5, 5A may include integrated circuits such as ASICs (Application Specific Integrated Circuits) or FPGAs (Field Programmable Gate Arrays). The data linkage programs according to the first to third embodiments may be stored in a recording medium such as a CD (Compact Disc)-ROM or a DVD-ROM and provided. The data linkage programs according to the first to third embodiments may be stored in a computer connected to a network such as the Internet and provided by being downloaded via the network such as the Internet. The data linkage programs according to the first to third embodiments may be provided or distributed via a network such as the Internet.

[0116] In the first to third embodiments, the data linkage system 1 is realized by a single device, the data linkage device 5, 5A. However, the data linkage system 1 may be realized using two or more devices. That is, the data linkage system 1 may be configured by two or more devices. The two or more devices are connected to each other so that they can communicate with each other. Each of the two or more devices has, for example, the same configuration as the processing circuit 30 and the communication device 31. The two or more devices may include a device having the same configuration as the input device 34 and the display device 35. The two or more devices may include a cloud server. The cloud server is a server built in a cloud environment that includes computer resources provided by a cloud service platform.

[0117] The configurations shown in the above embodiments are examples of the contents of the present disclosure. The configurations of each embodiment can be combined with other known technologies. The configurations of each embodiment can also be combined as appropriate. Part of the configuration of each embodiment can be omitted or modified without departing from the gist of the present disclosure. [Explanation of symbols]

[0118] 1 data linkage system, 2 monitoring and control system, 3 inspection support system, 4 inspection support service, 5, 5A data linkage device, 6, 7, 8 device, 10 data acquisition unit, 11 data storage unit, 12 linked data management unit, 13 request receiving unit, 14 linked data transmission unit, 15 linkage definition creation unit, 16 linkage definition information storage unit, 17 data attribute information creation unit, 18 data attribute information storage unit, 19 linked data attribute information creation unit, 20 linked data attribute information storage unit, 30 processing circuit, 31 communication device, 32 processor, 33 memory, 34 input device, 35 display device.

Claims

1. a data acquisition unit that acquires data from each of a plurality of systems that output data; and a linked data management unit that determines whether or not to permit an operation on the linked data by the client who is a requester of the operation, based on linked data attribute information that indicates the client's authorization to operate on the linked data obtained by linking the data from each of the plurality of systems. A data linkage system characterized by:

2. a linked data attribute information creation unit that creates the linked data attribute information; 2. The data linkage system according to claim 1.

3. The linked data attribute information creation unit presents data attribute information indicating the authorization of the customer to operate the data from each of the plurality of systems, and accepts editing of the linked data attribute information.

3. The data linkage system according to claim 2.

4. the linked data attribute information includes a time condition that is a date and time condition for when the customer is permitted to perform an operation on the linked data; The linked data management unit permits the operation by the request source when a date and time at which the request source's request for the operation on the linked data is accepted satisfies the time condition.

3. The data linkage system according to claim 1 or 2.

5. the linked data attribute information is expressed by an equation including a variable representing whether or not each of the plurality of systems has an operation authority for the data; The linked data management unit calculates the formula to determine whether or not to permit the operation by the request source.

3. The data linkage system according to claim 1 or 2.

6. acquiring data from each of a plurality of systems that output said data; and determining whether or not to permit the client, who is a requester of the operation, to operate on the linked data, based on linked data attribute information indicating the client's authorization to operate on the linked data, which is obtained by linking the data from each of the plurality of systems. A data linking method characterized by:

7. The method further includes the step of creating the linked data attribute information. The data linking method according to claim 6 .

8. In the step of creating the linked data attribute information, data attribute information indicating the authorization of the customer to operate the data from each of the plurality of systems is presented, and editing of the linked data attribute information is accepted. The data linking method according to claim 7 .

9. the linked data attribute information includes a time condition that is a date and time condition for when the customer is permitted to perform an operation on the linked data; In the step of determining whether to permit the request source to operate on the linked data, the operation by the request source is permitted if the date and time at which the request source to operate on the linked data is accepted satisfies the time condition.

8. The data linking method according to claim 6 or 7.

10. the linked data attribute information is expressed by an equation including a variable representing whether or not each of the plurality of systems has an operation authority for the data; In the step of determining whether to permit the request source to perform an operation on the linked data, the formula is calculated to determine whether to permit the request source to perform the operation.

8. The data linking method according to claim 6 or 7.

11. acquiring data from each of a plurality of systems that output said data; and determining whether or not to permit the client, who is a requester of the operation, to operate on the linked data, which is obtained by linking the data from each of the plurality of systems, based on linked data attribute information indicating the client's authorization to operate on the linked data. A data linkage program characterized by:

Images