Related data extraction device, related data extraction system, related data extraction method, and related data extraction program

Abstract

To provide metadata flexibly in accordance with an application.SOLUTION: A related data extraction apparatus for extracting related data related to data collected from a target system, and to be added to the data includes: a configuration data accumulation unit which manages configuration information of the target system; a configuration data input unit which receives an input of registration or update of the configuration information; an application association unit which receives, by an application for analyzing the data, a request for the related data to be added to the data; and a related data extraction unit which extracts the related data from the configuration information on the basis of the request.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a related data extraction device, a related data extraction system, a related data extraction method, and a related data extraction program. [Background technology]

[0002] With the development of IoT (Internet of Things), services that provide value-added solutions by analyzing data collected from devices such as sensors are emerging. When applying IoT to factories, sensor data is collected from sensors attached to manufacturing equipment and workers in the factory, and the status and efficiency of the factory's manufacturing processes are visualized and analyzed to detect abnormalities in the manufacturing site, improve production plans and manufacturing processes, and enhance workers' production skills.

[0003] A specific example of a solution that applies IoT to factories is a solution that correlates sensor data collected from equipment in the factory with configuration data of the production line to analyze the status and efficiency of the factory's production line. The configuration data of the production line includes the order in which the equipment installed on the production line is connected, the type of equipment used, the products being produced, etc. When correlating sensor data with configuration data of the production line, it is necessary to be able to provide data that is suitable for the application that performs the analysis.

[0004] For example, Patent Document 1 below discloses a data flow control device comprising: device-side metadata acquisition means for acquiring, for each of a plurality of devices, device-side metadata including items indicating specifications of data that the device can provide; application-side metadata acquisition means for acquiring, for an application that uses data provided by the device, application-side metadata including items indicating specifications of data required by the application; storage means for storing the device-side metadata and the application-side metadata; matching means for matching the application-side metadata with the device-side metadata to extract combinations of the application and devices that can provide data that meets the specifications required by the application; and data flow control means for generating a data flow control command that identifies the device and the application extracted by the matching means, wherein the matching means extracts the combinations based on whether or not items to be matched match among the items included in the device-side metadata and the application-side metadata, and, if there is an item where a mismatch occurs, acquires information indicating whether the item where the mismatch occurs can be changed, and changes the item where the mismatch occurs based on the information. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-167748 Summary of the Invention [Problem to be solved by the invention]

[0006] However, the technology described in Patent Document 1 aims to match application-side metadata with device-side metadata, and does not disclose a mechanism for adding metadata or changing the metadata to be assigned in response to a request from the application side. Therefore, there is room for improvement in the flexibility of providing metadata to applications.

[0007] The present invention has been made in view of the above-mentioned problems, and has as its object to provide metadata flexibly according to the application. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems, one aspect of the present invention is a related data extraction device that extracts related data related to data collected from a target system and is to be assigned to the data, and is characterized by having a configuration data storage unit that manages configuration information of the target system, a configuration data input unit that accepts input for registering or updating the configuration information, an application collaboration unit that accepts a request for the related data to be assigned to the data by an application that analyzes the data, and a related data extraction unit that extracts the related data from the configuration information based on the request. [Effects of the Invention]

[0009] According to the present invention, for example, it is possible to provide metadata flexibly according to the application. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a related data extraction system including a related data extraction device. [Figure 2] FIG. 2 is a diagram illustrating an example of the hardware configuration of a related data extraction device. [Figure 3] FIG. 4 is an explanatory diagram showing an example of configuration data. [Figure 4] FIG. 10 is an explanatory diagram showing an example of a supplementary data management table. [Figure 5] FIG. 10 is an explanatory diagram showing an example of a related data request screen displayed on a screen display unit. [Figure 6] FIG. 10 is an explanatory diagram showing an example of a related data request screen displayed on a screen display unit. [Figure 7] FIG. 4 is an explanatory diagram showing an example of a configuration management screen displayed on a screen display unit. [Figure 8] FIG. 10 is an explanatory diagram showing an example of a data extraction rule. [Figure 9] FIG. 10 is an explanatory diagram showing an example of a related data combination table. [Figure 10] 10 is a sequence diagram illustrating an example of related data acquisition between a related data extraction device and a data processing platform. [Figure 11] 10 is a flowchart showing a related data extraction process of the related data extraction device. [Figure 12] FIG. 10 is an explanatory diagram showing an example in which related data is added to data collected by the data processing platform. [Figure 13] FIG. 10 is an explanatory diagram showing an example of version management of the related data extraction device. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will readily understand that the specific configuration can be modified (for example, by combining at least a part of one embodiment with another embodiment) without departing from the spirit or intent of the present invention.

[0012] In the following description, the same or similar components or functions are denoted by the same reference numerals, and redundant descriptions are omitted. Furthermore, even when different sub-reference numerals are assigned to the same reference numerals, the reference numerals without sub-reference numerals are used when no distinction is required.

[0013] In the following description, the following embodiments will be described focusing on the differences from the previously described embodiments, and descriptions of overlapping portions will be omitted.

[0014] In the following explanation, various data and information such as "configuration data 3," "supplementary data management table 4," "data extraction rule 8," "related data binding table 9," and "collected data 155" are assumed to be stored in a predetermined storage area. Furthermore, even if simply written as "configuration data 3," "supplementary data management table 4," "data extraction rule 8," "related data binding table 9," "collected data 155," etc., they may refer to a storage unit that stores the corresponding data.

[0015] In the following description, information is illustrated in a table format, but the information may be expressed in a format other than a table.

[0016] <Overall structure> 1 is a diagram showing an example of the configuration of an associated data extraction system 1 including an associated data extraction device 110. The associated data extraction system 1 includes associated data extraction device 110, first system configuration information 121-1 to N-th system configuration information 121-N (N is any natural number equal to or greater than 2), first device 132-1 to N-th device 132-N, first sensor 131-1 to N-th sensor 131-N, first relay device 141-1 to N-th relay device 141-N, and a data processing infrastructure 150. Hereinafter, the first system configuration information 121-1 to N-th system configuration information 121-N will be collectively referred to as "system configuration information 121." Furthermore, first sensor 131-1 to Nth sensor 131-N are collectively referred to as "sensor 131," first device 132-1 to Nth device 132-N are collectively referred to as "device 132," and first relay device 141-1 to Nth relay device 141-N are collectively referred to as "relay device 141."

[0017] The sensor 131 measures the temperature, humidity, vibration, current, position, etc. of the device 132 and outputs the measurement results as sensor data. The device 132 is, for example, a manufacturing device installed on a production line, and is connected to a programmable logic controller (PLC) (not shown) or the like, and the device status, execution results, etc. are acquired by the sensor 131. The device 132 may have the sensor 131 built in. The sensor 131 and the device 132 are connected to a relay device 141 via an in-factory network including a PLC or the like, and collected data such as sensor data, device status, execution results, etc. is transferred to the data processing platform 150. A plurality of sensors 131 and devices 132 may be configured.

[0018] The system configuration information 121 includes information such as the types of devices 132 and sensors 131 used, detailed information about each device, the connection order, and information about the products to be manufactured. The j-th sensor 131-j, the j-th device 132-j, and the j-th relay device 141-j may be considered to constitute one intra-factory network (j-th intra-factory network), which is managed by the j-th system configuration information 121-j (j is an integer equal to or greater than 1). The j-th intra-factory network is a target system for acquiring sensor data, and is configured to include one or more j-th sensors 131-j, one or more j-th devices 132-j, and one or more j-th relay devices 141-j.

[0019] The data processing infrastructure 150 includes a data collection unit 151, a data processing unit 152, a collected data storage unit 153, and a data analysis unit 154. The data collection unit 151 collects data transferred from the relay device 141. The data collected by the data collection unit 151 is called collected data. The data processing unit 152 formats the collected data. The formatted collected data is stored as collected data 155 in the collected data storage unit 153 and is used for analysis by the data analysis unit 154. The data processing infrastructure 150 manages the collected data transferred from the relay device 141 as a series of flows. For example, the collected data acquired from the first sensor 131-1 or the first device 132-1, which is managed in the first system configuration information 121-1, may be managed as a first flow.

[0020] The related data extraction device 110 is provided, for example, as an enhanced function of the related data extraction system 1. The related data extraction device 110 includes a configuration data input unit 111, a configuration data storage unit 112, a related data extraction unit 113, and an application linkage unit 114.

[0021] The configuration data input unit 111 takes in the system configuration information 121 and stores it in the configuration data storage unit 112. In this embodiment, device information such as the type of device 132 and system configuration information indicating the connection order and connection configuration of the devices 132 and sensors 131 are managed in the configuration data 3, and detailed information on each device of the sensors 131 and the devices 132 is managed in the supplementary data management table 4.

[0022] The application collaboration unit 114 includes a screen display unit 5 and receives a request for related data (i.e., metadata) to be extracted. The related data extraction unit 113 extracts related data in accordance with the request received by the application collaboration unit 114. The related data extraction unit 113 includes data extraction rules 8 and stores related data corresponding to the request received by the application collaboration unit 114 in a related data combination table 9 from the information stored in the configuration data 3 and the supplementary data management table 4.

[0023] When the related data extraction device 110 receives a request from the data analysis unit 154 for related data to be added for analysis, it extracts the relevant related data and outputs it to the data processing unit 152. The collected data to which the related data has been added in the data processing unit 152 is accumulated in collected data 155 and used for analysis by the data analysis unit 154.

[0024] <Hardware configuration of related data extraction device> 2 is a diagram showing an example of the hardware configuration of the related data extraction device 110. The related data extraction device 110 has a processor 201, a storage device 202, an input device 203, an output device 204, and a communication interface (communication IF) 205. The processor 201, the storage device 202, the input device 203, the output device 204, and the communication IF 205 are connected by a bus 206. The processor 201 controls the related data extraction device 110.

[0025] The storage device 202 serves as a working area for the processor 201. The storage device 202 is a non-transitory or temporary recording medium that stores various programs and data. Examples of the storage device 202 include a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), and a flash memory. The input device 203 inputs data. Examples of the input device 203 include a keyboard, a mouse, a touch panel, a numeric keypad, and a scanner. The output device 204 outputs data. Examples of the output device 204 include a display and a printer. The communication IF 205 connects to a network and transmits and receives data.

[0026] Each of the hardware components of the related data extraction device 110, namely the processor 201, the storage device 202, the input device 203, the output device 204, and the communication IF 205, may be composed of multiple devices.

[0027] <Configuration data> 3 is an explanatory diagram showing an example of configuration data 3. The configuration data 3 is expressed, for example, as a table having time 301 and graph-format database ID 302 as fields. Time 301 is a predetermined time when graph-format database ID 302 is saved. Time 301 may be the time when the configuration is changed, or may be the time when registered information is changed. The graph-format database ID 302, i.e., the system configuration information 121, is registered periodically or irregularly.

[0028] The graph format database ID 302 is an identifier of a graph format database that indicates the types and connection order of the sensors 131 and devices 132 to be used in the system configuration information 121. Each time the related data extraction device 110 creates or updates the configuration data 3 in response to input of the system configuration information 121, an entry is added to the table of the configuration data 3. For example, it may be considered that the input of the first system configuration information 121-1 described in FIG. 1 is triggered by the addition of an entry with the graph format database ID 302 being GDB0001.

[0029] Furthermore, by referencing the graph format database ID 302 of the configuration data 3, it is possible to confirm the contents of the system configuration information 121, as shown in reference example 300. In reference example 300, the graph format database ID 302 indicates an example of the entry contents of GDB0001. In the graph format, an IoT GW (Gateway), GW, PLC, Asset, and process are each managed as a node surrounded by a circle, and the relationship between the nodes is expressed by connecting them with arrows. Assets are sensors 131 and devices 132, and the IoT GW and GW correspond to relay devices 141. For example, solid arrows connecting the IoT GW, GW, PLC, and Asset indicate physical connection relationships. Dash-dotted arrows connecting Assets and processes indicate logical relationships indicating Assets corresponding to one process, and dashed arrows connecting processes indicate logical relationships of the process order for each product ID.

[0030] <Supplementary data management table> 4 is an explanatory diagram showing an example of the supplementary data management table 4. The supplementary data management table 4 stores detailed information of each device of the sensors 131 and equipment 132 used in the system configuration information 121.

[0031] The supplementary data management table 4 is expressed as a table having, for example, fields of a graph format database ID 401, node information 402, supplementary data 403, and update time 404. The graph format database ID 401 corresponds to the graph format database ID 302 of the configuration data 3 shown in FIG. 3 and indicates the correspondence between the supplementary data management table 4 and the configuration data 3. The node information 402 registers IDs of various nodes such as IoT GW, GW, PLC, and Asset. The supplementary data 403 may register detailed information of each device of the sensor 131 and the equipment 132, or may register a reference destination for the detailed information. The update time 404 is a predetermined time when the supplementary data 403 was registered or updated.

[0032] Figure 4 shows an example in which, in a database with a graph format database ID 401 of GDB0001, A01 inspection processing implementation data 40311 and A01 inspection result validity range data 40312 are registered as supplementary data 403 in an Asset with an ID of A01, and A02 inspection processing implementation data 40321 and A02 inspection result validity range data 40322 are registered as supplementary data 403 in an Asset with an ID of A02.

[0033] The A01 inspection process execution data 40311 shows an example of information indicating whether four inspections, Inspection 1 to Inspection 4, performed by an Asset with an ID of A01 are to be performed for each product ID, such as S01 to S03. The A01 inspection result validity range data 40312 shows an example of information indicating the validity range of the inspection results for the four inspections, Inspection 1 to Inspection 4, performed by an Asset with an ID of A01. The A02 inspection process execution data 40321 shows an example of information indicating whether two inspections, Inspection 1 to Inspection 2, performed by an Asset with an ID of A02 are to be performed for each product ID, such as S01 to S03. The A02 inspection result validity range data 40322 shows an example of information indicating the validity range of the inspection results for the two inspections, Inspection 1 to Inspection 2, performed by an Asset with an ID of A02. Although not shown in FIG. 4, it is also possible to consider that similar supplementary data 403 is registered for Assets with IDs of A03 to A08.

[0034] In this embodiment, the system configuration information 121 is stored in two storage units, divided into two data types, configuration data and supplementary data, like the configuration data 3 and supplementary data management table 4. However, this is not limiting, and there may be n data types (n is an integer of 3 or more), and the data may be stored in n storage units divided into data types.

[0035] <Related data request screen> 5 and 6 are explanatory diagrams showing examples of related data request screens (51-1 and 51-2) displayed on the screen display unit 5. Hereinafter, the related data request screens 51-1 and 51-2 will be collectively referred to as the "related data request screens 51." On the related data request screen 51, it is possible to input information such as which data related information is being requested, what the search sort key is, and what the output requirements are for each flow managed by the data processing platform 150.

[0036] 5 has a first input field 511-1 to a fifth input field 515-1 and a request button 516-1. Identification information for the flow to be managed can be entered in the first input field 511-1. Information regarding which data related information is to be requested can be entered in the second input field 512-1. When an Asset node is selected, the second input field 512-1 can be used to select whether to acquire inspection process execution data and inspection result validity range data.

[0037] The third input field 513-1 can be used to input search sort key information when obtaining the information requested in the second input field 512-1. The fourth input field 514-1 can also be used to input search sort key information, and may be used in combination with the third input field 513-1 to refine the search sort key. The fifth input field 515-1 can be used to input output requests, such as the order of the information requested in the second input field 512-1 in a keyword search.

[0038] 5 shows an example in which "F001" is entered in the first input field 511-1, "Asset ID" in the second input field 512-1, "Product ID" in the third input field 513-1, and "Order" in the fifth input field 515-1. When the request button 516-1 is pressed, the application cooperation unit 114 notifies the related data extraction unit 113 of a request to extract related data, specifying "F001" as the management flow, "Product ID" as the search sort key, "Asset ID" as the output information, and "Order" as the additional request at the time of output.

[0039] 6 has a first input field 511-2 to a fifth input field 515-2 and a request button 516-2. The same information as that in the first input field 511-1 to the fifth input field 515-1 shown in FIG. 5 can be entered in the first input field 511-2 to the fifth input field 515-2.

[0040] 6 shows an example in which "F001" is entered in the first input field 511-2, "Asset inspection process" in the second input field 512-2, "Asset ID" in the third input field 513-2, and "Product ID" in the fourth input field 514-2. When the request button 516-2 is pressed, the application cooperation unit 114 notifies the related data extraction unit 113 of a request to extract related data, specifying "F001" as the management flow, "Asset ID & Product ID" as the search sort key, "Inspection process" (inspection process implementation data and inspection result valid range data) as the output information, and "None (may be left blank, etc.)" as the additional request at the time of output. For "Inspection process" in the output information, the inspection process implementation data and inspection result valid range data may be individually selectable.

[0041] <Configuration management screen> 7 is an explanatory diagram showing an example of the configuration management screen 52 displayed on the screen display unit 5. The configuration management screen 52 has an input field 521 and first to third display fields 522 to 524.

[0042] The input field 521 allows the user to input identification information for the flow to be managed. The first display field 522 allows the user to confirm the contents of the system configuration information 121, as shown in the reference example 300 of FIG. 3. The second display field 523 allows the user to confirm the contents of each node information configured in the first display field 522. The second display field 523 can display node information corresponding to the node identification information entered in the node selection field, such as supplementary data listed in the supplementary data management table 4 (e.g., A01 inspection processing execution data 40311 and A01 inspection result validity range data 40312 when A01 is entered in the node selection field). The third display field 524 allows the user to display, as event information, information on a related data request received from the related data request screen 51. FIG. 7 shows an example in which the information requested from the related data request screen 51-1 shown in FIG. 5, in which the search sort key is "product ID," the output information is "asset ID," and the additional request at the time of output is "order," is displayed as text. 7, the content of the entry in the second line of the data extraction rule 8 in Fig. 8, which will be described later, is displayed. The third display field 524 may display other information such as log information.

[0043] <Data extraction rules> FIG. 8 is an explanatory diagram showing an example of a data extraction rule 8. The data extraction rule 8 stores the related data request details for each application. The data extraction rule 8 is expressed as a table having the following fields: management flow ID 801, output information 802, search sort key 803, addition request 804, and rule ID 805. The management flow ID 801 to addition request 804 each hold information corresponding to the management flow ID, output information, search sort key, and addition request notified from the application cooperation unit 114 as data extraction requirements. The rule ID 805 is an identifier of the rule that extracts related data based on the data extraction requirements.

[0044] The data extraction rules 8 also include a rule search table 82, which manages rules for extracting related data. The rule search table 82 is expressed as a table having the following fields: rule ID 821, data search target 822, data acquisition condition 823, related data binding table ID 824, and composition time 825. The rule ID 821 is an identifier for the rule that extracts related data, and corresponds to the rule ID 805. The data search target 822 holds information about the database or table to be searched for the corresponding rule ID 821, i.e., information such as the composition data 3, supplementary data management table 4, and graph-format database ID (302 or 401). The data acquisition condition 823 defines a method for acquiring data from the corresponding data search target 822.

[0045] The related data linkage table ID 824 is an identifier for the related data linkage table 9, which is expressed as a table that combines information on the data acquired according to the corresponding data acquisition condition 823. Details of the related data linkage table 9 will be described later using Fig. 9. The creation time 825 is a predetermined time when the related data linkage table 9 corresponding to the related data linkage table ID 824 is registered or updated.

[0046] In the example shown in Figure 8, two rules are defined. The first rule, R001, is a rule for extracting related data corresponding to a request registered from the related data request screen 51-2 shown in Figure 6, where the management flow is "F001," the output information is "inspection processing," the search sort key is "Asset ID & product ID," and the additional requirements at output are "none." The data search target 822 is "Graph format database ID: GDB0001, supplementary data management table," and the data acquisition condition 823 is "obtain inspection processing execution data and inspection result validity range data held by Asset." This condition indicates that the related data binding table ID 824, "T001," was registered or updated at the configuration time 825, "2021 / 2 / 7 08:03:00.000." The configuration time 825 reflects the update time of the A02 inspection result validity range data 40322, which is the most recent update time among the update times 404 shown in Figure 4.

[0047] The second rule, R002, is used to extract related data corresponding to a request registered on the related data request screen 51-1 shown in Figure 5, where the management flow is "F001," the output information is "Asset ID," the search sort key is "Product ID," and the additional requirement at output is "Order." The data search target 822 is "Graph format database ID: GDB0001, configuration data." The data acquisition condition 823 is "Acquire information on nodes and connections identified by the product ID (search sort key) and the Asset ID (output information). If no matching order connection is found, trace the order from the upper and lower connections." This condition indicates that the related data binding table ID 824, "T002," was registered or updated at the configuration time 825, "2021 / 2 / 7 09:10:00.000." The configuration time 825 reflects the time 301 shown in Figure 3.

[0048] <Related data join table> Fig. 9 is an explanatory diagram showing an example of the related data linkage table 9. The related data linkage table 9 is a general term for a group of tables configured based on the data extraction rules shown in Fig. 8. Fig. 9 explains an example of a related data linkage table 91 with a related data linkage ID of T001 and a related data linkage table 92 with a related data linkage ID of T002.

[0049] The related data binding table 91 holds information on the related data binding table ID 911, management flow ID 912, and configuration time 913, and based on data extraction rule 8, the information held is "T001", "F001", and "2021 / 2 / 7 08:03:00.000".

[0050] The related data binding table 91 is expressed as a table having the fields Asset ID 914, product ID 915, "Inspection: performed / not performed" 916, and "Inspection value: valid range" 917. Asset ID 914 and product ID 915 are search sort keys, and are provided based on the search sort key 803 of data extraction rule 8. "Inspection: performed / not performed" 916 and "Inspection value: valid range" 917 are extracted values, and are fields that are acquired and combined based on the conditions indicated in the data search target 822 and data acquisition condition 823 of data extraction rule 8.

[0051] In the example of FIG. 9, A01 inspection process execution data 40311 and A01 inspection result validity range data 40312 are acquired for Asset with ID A01, and are combined according to Asset ID 914 and product ID 915, which are search sort keys.

[0052] Although not shown in FIG. 9, the A02 inspection process execution data 40321 and the A02 inspection result valid range data 40322 may also be acquired from the Asset with ID A02 and combined with the related data combination table 91.

[0053] The related data binding table 92 holds information on the related data binding table ID 921, management flow ID 922, and configuration time 923, and based on data extraction rule 8, the information held is "T002", "F001", and "2021 / 2 / 7 09:10:00.000".

[0054] The related data linkage table 92 is expressed as a table having fields such as product ID 924 and "Asset ID: order" 925. The product ID 924 is a search sort key and is provided based on the search sort key 803 of data extraction rule 8. The "Asset ID: order" 925 is an extracted value and is a field obtained and created based on the conditions indicated in the data search target 822 and data acquisition condition 823 of data extraction rule 8. In the example of FIG. 9, the Asset ID information for each product ID 924 is arranged in order to match the logical relationship of the process order indicated by the dotted line in the reference example 300 of FIG. 3. Although not shown in FIGS. 9 and 3, data with a product ID such as S03 may also be obtained in a similar manner and linked to the related data linkage table 92.

[0055] <Example of sequence for obtaining related data> Fig. 10 is a sequence diagram showing an example of related data acquisition between the related data extraction device 110 and the data processing infrastructure 150. Fig. 10 shows an example in which the data analysis unit 154 requests and receives related data from, for example, the registration of information in the configuration data 3 and the supplementary data management table 4.

[0056] (Data registration process for configuration data 3 and supplementary data management table 4) First, in step S1001, when the configuration data accumulation unit 112 detects that information has been registered in the configuration data 3 or the supplementary data management table 4, it notifies the related data extraction unit 113 that the data has been registered. Next, in step S1002, the related data extraction unit 113 searches for data in the configuration data 3 and the supplementary data management table 4 based on the data extraction rules 8, and updates the related data combination table 9. Next, in step S1003, the configuration data accumulation unit 112 notifies the application collaboration unit 114 that the update has been completed. Next, in step S1004, upon receiving the update completion notification, the application collaboration unit 114 begins accepting requests to the related data request screen 51 for the corresponding management flow ID.

[0057] Next, in step S1005, data processing unit 152 formats the data collected by data collection unit 151 and stores it as collected data 155 in collected data storage unit 153. Next, in step S1006, data analysis unit 154 reads out the collected data stored in collected data 155.

[0058] Next, in step S1007, the data analysis unit 154 analyzes the data read from the collected data 155 and determines whether or not related data needs to be added. In step S1008, if related data needs to be added, the data analysis unit 154 requests information to be added as related data from the application cooperation unit 114 via the screen display unit 5 or the like. Next, in step S1009, the application cooperation unit 114 analyzes the information request received from the data analysis unit 154. Next, in step S1010, the application cooperation unit 114 notifies the related data extraction unit 113 of a request to extract related data, including information such as the management flow, search sort key, output information, and additional requests at the time of output, in accordance with the analysis result of the information request received from the data analysis unit 154.

[0059] Next, in step S1011, upon receiving an extraction request from the application cooperation unit 114, the related data extraction unit 113 extracts related data by referring to the data extraction rules 8 and the related data association table 9. Next, in step S1012, the related data extraction unit 113 notifies the data processing unit 152 of the extracted related data as added related data. A detailed example of the processing by the related data extraction unit 113 will be described later with reference to FIG. 11.

[0060] Next, in step S1013, upon receiving the additional related data from the related data extraction unit 113, the data processing unit 152 updates the processed data to add the additional related data, and adds the additional related data when formatting the data collected by the data collection unit 151. Next, in step S1014, the data processing unit 152 stores the processed data to which the additional related data has been added in collected data 155 of the collected data storage unit 153. Next, in step S1015, the data analysis unit 154 reads out the processed data to which the additional related data has been added, which is stored in collected data 155 of the collected data storage unit 153. Next, in step S1016, the data analysis unit 154 confirms that the related data has been added when analyzing the processed data read out in step S1015.

[0061] (Configuration data 3, supplementary data management table 4 update processing) After step S1016, in step S1017, when the configuration data accumulation unit 112 detects an update to the information in the configuration data 3 or the supplementary data management table 4, it notifies the related data extraction unit 113 that the data has been updated. Next, in step S1018, when the related data extraction unit 113 is notified of the update to the configuration data 3 or the supplementary data management table 4 from the configuration data accumulation unit 112, it searches for data in the configuration data 3 and the supplementary data management table 4 based on the data extraction rule 8 and updates the related data combination table 9. Next, in step S1019, in response to the extraction request received in S1010, the related data extraction unit 113 notifies the data processing unit 152 of the update information in the related data combination table 9 as updated related data. Next, in step S1020, the data processing unit 152 updates the processed data by adding the updated related data received from the related data extraction unit 113.

[0062] <Example of processing flowchart> Fig. 11 is a flowchart showing the details of the processing of related data extraction device 110. The example of Fig. 11 shows an overview of the processing from when related data extraction device 110 receives a request for related data to be added for analysis from data analysis unit 154, to when it extracts the relevant related data, and when it outputs the data to data processing unit 152. When related data extraction device 110 receives a request for related data, it executes the processing shown in the following flowchart.

[0063] First, in step S1101, related data extracting device 110 analyzes the received related data request and acquires the search sort key, output information, and additional request information. This corresponds to steps S1008 to S1009 of application cooperation unit 114 shown in FIG. 10.

[0064] Next, in step S1102, the related data extraction device 110 refers to the data extraction rule 8 based on the acquired information to determine the corresponding rule ID 805 (or 821), and acquires the related data combination table ID 824 based on the rule ID 805.

[0065] Next, in step S1103, the related data extraction device 110 determines whether or not there is data being updated in the data search target 822 for the relevant rule ID 805 determined in step S1102. If the related data extraction device 110 determines that there is data being updated, it proceeds to step S1104, and if it determines that there is no data being updated, it proceeds to step S1106.

[0066] In step S1104, the related data extracting device 110 waits for an update of the related data corresponding to the relevant rule ID 805 in the related data merge table ID 824. Next, in step S1105, the related data extracting device 110 determines whether the update it waited for in step S1104 has completed. If the related data extracting device 110 determines that the update has completed, it proceeds to step S1106. In FIG. 11, step S1105 is repeated until it is determined that the update has completed, but if the update is not completed, the process shown in FIG. 11 may be terminated by a timeout or the like.

[0067] In step S1106, the associated data extracting device 110 acquires information on the associated data from the associated data linking table 9 based on the associated data linking table ID 824, and outputs the information to the data processing unit 152. The processing of steps S1102 to S1106 corresponds to steps S1010 to S1012 of the associated data extracting unit 113 shown in Fig. 10. After step S1106, the processing shown in Fig. 11 ends.

[0068] <Example of adding related data> FIG. 12 is an explanatory diagram showing an example in which the data processing infrastructure 150 adds related data to collected data.

[0069] Data 1200-1, data 1200-2, and data 1200-3 are collected data before associated data is added, and are collected data shaped by data processing unit 152 in step S1005 shown in FIG. 10. Hereinafter, data 1200-1 to data 1200-3 are collectively referred to as "data 1200." Data 1200 shows an example of collected data acquired from sensor 131 or device 132 with Asset ID A01, and includes information on the results of each inspection performed in A01 for each product ID. Specifically, data 1200-1 includes information on Asset ID: A01, product ID: S01, inspection 1 result: 10, inspection 2 result: 20, inspection 3 result: 15, and inspection 4 result: 30.

[0070] Data 1201-1, data 1201-2, and data 1201-3 are collected data after the related data extracted based on the rule ID R001 shown in Fig. 8 has been assigned to data 1200-1, data 1200-2, and data 1200-3, respectively, and are an example of collected data shaped together with the related data by data processing unit 152 in step S1014 shown in Fig. 10. Hereinafter, data 1201-1 to data 1201-3 will be collectively referred to as "data 1201."

[0071] In data 1201, information on whether each test was performed or not and the valid range of each test value is added to each data item in data 1200. Specifically, in data 1201-1, the following information is added to the data in data 1200-1: Test 1 performed: 1 (test executed (same below)), Test 2 performed: 1, Test 3 performed: 1, Test 4 performed: 1, Test 1 range: 0-20, Test 2 range: 0-50, Test 3 range: 10-100, Test 4 range: 20-90.

[0072] By collecting data 1201, the data analysis unit 154 can determine whether the results of each test performed in A01 need to be used as data. For example, data 1200-2 includes information such as "Test 2 result: 0" (test not performed (same below)), but it may be difficult to determine whether test 2 was not performed on the product in S02, whether the value is correct, or whether the data is usable. Data 1201-2 includes information such as "Test 2 performed: 0," so it may be determined that test 2 was not performed. Furthermore, data 1200-3 includes information such as "Test 3 result: -5," so it may be difficult to determine whether test 3 was performed correctly on the product in S03 or whether the value is abnormal. Data 1201-3 includes information such as "Test 3 performed: 1" and "Test 3 range: 10-100," so it may be determined that test 3 was performed but the value was outside the valid range (an outlier or invalid value), resulting in an abnormal result.

[0073] Data 1202-1 and data 1202-2 are data after the associated data extracted based on the rule ID R002 shown in FIG. 8 has been added to data 1200-1 and data 1200-2, respectively, and are another example of collected data shaped together with the associated data by data processing unit 152 in step S1014 shown in FIG. 10. Hereinafter, data 1202-1 to data 1202-2 will be collectively referred to as "data 1202." In data 1202, information on passing devices has been added to each piece of data in data 1200. Specifically, in data 1202-1, information on passing devices: "A01, A02, A03, A04, A05, A06, A07, A08" has been added to the data in data 1200-1.

[0074] By collecting data 1202, the data analysis unit 154 can determine all of the Assets passed through for each product ID and their order. For example, while data 1200 allows for determination that a product with each product ID was processed by the device with Asset ID: A01, it may be difficult to determine how the product was processed overall. Data 1202-1 includes information on passed devices: "A01, A02, A03, A04, A05, A06, A07, A08," and it may be determined that the product with product ID: S01 passes through each of the Assets A01 to A08 before being processed. Data 1202-2 also includes information on passed devices: "A01, A02, A04, A05, A06, A08," and it may be determined that the product with product ID: S02 does not pass through Assets A03 and A07.

[0075] <Example of version control> 13 is an explanatory diagram showing an example of version management of the related data extraction device 110. The related data extraction device 110 may manage the history of generated related data using a version management table 1300 having, for example, fields such as extraction rule 1301, version 1302, creation time 1303, generated data 1304, and configuration time 1305.

[0076] Extraction rule 1301 is an identifier of a rule for extracting related data, and corresponds to rule ID 805 shown in FIG. 8. Version 1302 is a name indicating the history, such as version information, of the related data to be generated. Creation time 1303 is the time when the relevant related data was generated, and is the time when the related data extraction unit 113 obtained the related data information from the related data combination table 9. Generated data 1304 holds the contents of the related data combination table 9 as of creation time 1303. Composition time 1305 is a predetermined time when the related data combination table 9 is registered or updated, and corresponds to composition time 825 shown in FIG. 8.

[0077] Figure 13 shows an example in which Version 1302 of the related data created by extraction rule 1301 of R001 has been updated from "Version 1" to "Version 2," with information about the updated portion shown in bold. In the example of Figure 13, it is assumed that, in the A01 inspection result validity range data 40312, information indicating the validity range of the inspection results for two inspections, Inspection 2 and Inspection 3, performed by Asset A01, has been updated. The update time 404 of the supplementary data management table 4 is updated from "2021 / 2 / 7 08:01:00.000" to "2021 / 2 / 9 15:01:00.000," and the configuration time 825 of the rule search table 82 is also updated in the same way. The version management table 1300 shows that the related data for "Ver 2" was generated on "2021 / 2 / 9 15:01:30.000", and the data generated at that time is information from the related data binding table ID: T001, which was updated on "2021 / 2 / 9 15:01:00.000".

[0078] As described above, according to this embodiment, the related data extraction device 110 can extract related data in response to a request from the data analysis unit 154. Therefore, metadata can be provided flexibly according to the application. Furthermore, according to this embodiment, by providing the data extraction rules 8 and configuring the related data linkage table 9 in advance, it is possible to flexibly respond to a variety of system configuration information 121 and shorten the time required to provide related data.

[0079] According to the above-described embodiment, the following advantageous effects can be obtained.

[0080] (1) The related data extraction device 110 includes a configuration data storage unit 112 that manages system configuration information 121, a configuration data input unit 111 that accepts input such as updates and changes to the system configuration information 121, an application collaboration unit 114 that accepts information that the data analysis unit 154 requests to be added as related data, and a related data extraction unit 113 that creates related data by referencing data managed by the configuration data storage unit 112 based on the information accepted by the application collaboration unit 114. Therefore, related data can be provided in response to a request from the data analysis unit 154. The requested content differs depending on, for example, the type of application performing the analysis. In this embodiment, the application collaboration unit 114 creates related data by referencing data managed by the configuration data storage unit 112 based on the information accepted by the application collaboration unit 114, so that related data, i.e., metadata, can be provided flexibly.

[0081] (2) The information received by the application collaboration unit 114 includes information requesting the overall device configuration and order. The application collaboration unit 114 requests the related data extraction unit 113 to extract related data, for example, using a search sort key of "product ID," output information of "asset ID," and an additional request at the time of output of "order." The related data extraction unit 113 then creates the relevant related data from the configuration data 3 managed by the configuration data accumulation unit 112.

[0082] (3) The information received by the application collaboration unit 114 includes information requesting a decision on whether or not to use the data, such as the presence or absence of outliers or invalid values. The application collaboration unit 114 requests the related data extraction unit 113 to extract related data, for example, by setting the search sort key to "Asset ID & Product ID," the output information to "Inspection process," and the additional request at the time of output to "None." The related data extraction unit 113 then creates the relevant related data from the supplementary data management table 4 managed by the configuration data accumulation unit 112.

[0083] (4) The configuration data storage unit 112 manages the system configuration information 121 by dividing it into multiple parts, such as the configuration data 3 and the supplementary data management table 4. Therefore, the application cooperation unit 114 selects a range (storage unit) to be referenced depending on the information received, and extracts related data from the selected range. This allows for load balancing of the storage area, and enables rapid extraction of related data.

[0084] (5) The related data extraction unit 113 is provided with data extraction rules 8 and has previously constructed a related data linkage table 9. When the application cooperation unit 114 receives a new request, the related data extraction unit 113 extracts related data corresponding to the request from the related data linkage table 9. This reduces the time required to provide related data created from data stored in multiple storage units.

[0085] (6) The configuration data 3 and the supplementary data management table 4 each have time information for updating the data in the system configuration information 121, and the data extraction rules 8 and the related data linkage table 9 also have this time information. Furthermore, when the application cooperation unit 114 accepts a new request, the related data extraction device 110 stores the time at which the related data corresponding to the new request was created. This allows for generational management of the system configuration information 121, the data extraction rules 8, the related data linkage table 9, and the related data based on these.

[0086] (7) The related data extraction system 1 includes a related data extraction device 110 and a data processing infrastructure 150. The data processing infrastructure 150 can request the related data extraction device 110 to provide related data and obtain the requested related data from the related data extraction device 110.

[0087] (Variation 1) In the above-described embodiment, the related data extraction device 110 determines whether or not there is data being updated in the data search target 822 for the relevant rule ID 805 in FIG. 11, and if it determines that there is data being updated, it waits for the related data linkage table ID 824 to be updated. However, it is also possible to output the related data before and after the update to the data processing unit 152 without waiting for the update.

[0088] (Variation 2) In the embodiment described above, after the associated data extraction device 110 creates the associated data combination table 9 in steps S1001 to S1004 of FIG. 10 , the application cooperation unit 114 starts accepting requests to the associated data request screen 51 for the corresponding management flow ID. However, creation of the corresponding associated data combination table 9 may start after accepting a request. In this case, before creation of the corresponding associated data combination table 9 is complete, the results acquired from the data search target 822 and the data acquisition condition 823 may be output as associated data to the data processing unit 152. Furthermore, in this case, after creation of the corresponding associated data combination table 9 is complete, associated data obtained by combining the results acquired from the data search target 822 and the data acquisition condition 823 may be output to the data processing unit 152.

[0089] (Variation 3) In the above-described embodiment, the related data extraction device 110 outputs the related data to the data processing unit 152, but it may also output the related data to another functional block of the data processing platform 150. For example, it may output the related data to the data analysis unit 154. In this case, the collected data and the related data may be linked and processed in the data analysis unit 154.

[0090] (Variation 4) In the above-described embodiment, the supplementary data is selected from the data managed by the related data extraction system 1 in the supplementary data management table 4. However, this is not limiting, and it is also possible to determine whether data found in a search based on a keyword entered by the user exists in the supplementary data management table 4, and use the data found in the search as supplementary data. This improves the flexibility in selecting and changing supplementary data.

[0091] (Variation 5) In the above-described embodiment, the granularity of supplementary data may be set more finely on the related data request screen (FIGS. 5 and 6). For example, in the "Test Process Enable / Disable" of the second input fields 512-1 and 512-2, the test process data and test result valid range data may be individually selectable, or each item may be individually selectable.

[0092] (Variation 6) The data extraction requirements (FIG. 8) may have an additional column for requirement IDs to distinguish between records. In this case, the supplementary data in FIG. 12 may be listed for each requirement ID. For example, if supplementary data for requirement IDs 1 and 2 are assigned to data 1200-1, data 1201-1 lists the supplementary data for requirement ID 1, followed by the supplementary data for requirement ID 2.

[0093] In the above-described embodiment and modified examples, the functional block configurations are merely examples. Several functional configurations shown as separate functional blocks may be configured as an integrated unit, or a configuration shown in a single functional block diagram may be divided into two or more functions. Also, some of the functions of each functional block may be provided in other functional blocks. Furthermore, the screen display method is also merely an example. The screen layout, wording, and design may be changed.

[0094] The present invention is not limited to the above-described embodiments and includes various modifications and equivalent configurations within the spirit and scope of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to configurations including all of the described configurations. Furthermore, part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, part of the configuration of each embodiment may be added, deleted, or replaced with other configurations. Furthermore, various processing functions may be integrated and distributed as appropriate for processing efficiency and implementation efficiency. Similarly, memory areas for storing various data may be integrated and distributed as appropriate for processing efficiency and implementation efficiency.

[0095] As mentioned above, each of the configurations, functions, processing units, processing means, etc. described above may be realized in part or in whole in hardware, for example by designing them as integrated circuits, or may be realized in software by having a processor interpret and execute a program that realizes each function.

[0096] Information such as programs, tables, and files that implement each function of the related data extraction device or related data extraction system can be stored in a storage device such as a memory, a hard disk, or a solid-state drive (SSD), or in a recording medium such as an integrated circuit (IC) card, an SD card, or a digital versatile disc (DVD). Alternatively, information such as programs, tables, and files that implement each function may be obtained from an external computer equipped with a non-transitory storage device via communication via the communication IF 205. Alternatively, information such as programs, tables, and files that implement each function may be recorded on a non-transitory recording medium and read by a medium reading device.

[0097] In addition, the control lines and information lines shown are those that are considered necessary for explanation, and do not necessarily represent all the control lines and information lines that are necessary for implementation. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0098] 1: Related data extraction system, 5: Screen display unit, 8: Data extraction rules, 9: Related data combination table, 110: Related data extraction device, 111: Configuration data input unit, 112: Configuration data storage unit, 113: Related data extraction unit, 114: Application linkage unit, 121: System configuration information, 150: Data processing platform, 151: Data collection unit, 152: Data processing unit, 153: Collected data storage unit, 154: Data analysis unit

Claims

1. A related data extraction device that extracts related data related to data collected from a target system and assigns the related data to the data, comprising: a configuration data storage unit that manages configuration information of the target system; a configuration data input unit that accepts input for registering or updating the configuration information; an application cooperation unit that receives a request for the related data that is to be added to the data by an application that analyzes the data; a related data extraction unit that extracts the related data from the configuration information based on the request; and the request includes a request for supplemental data related to the data analyzed by the application; The related data extraction unit The data analyzed by the application is used to reference the configuration information, and the relevant data corresponding to the request is extracted. A related data extraction device characterized by:

2. 2. The related data extraction device according to claim 1, The request includes a request for configuration data including a layout configuration or a layout order of devices in the target system. A related data extraction device characterized by:

3. 2. The related data extraction device according to claim 1, The request includes a request for information that is the basis for determining whether or not the application needs to use the data. A related data extraction device characterized by:

4. A related data extraction device that extracts related data related to data collected from a target system and assigns the related data to the data, comprising: a configuration data storage unit that manages configuration information of the target system; a configuration data input unit that accepts input for registering or updating the configuration information; an application cooperation unit that receives a request for the related data that is to be added to the data by an application that analyzes the data; a related data extraction unit that extracts the related data from the configuration information based on the request; and the configuration data storage unit manages the configuration information in a plurality of storage units; The related data extraction unit In response to the request, the configuration data storage unit selects a storage unit from the plurality of storage units and refers to the configuration information managed in the selected storage unit. A related data extraction device characterized by:

5. 5. The related data extraction device according to claim 4, The related data extraction unit A combination of the request and the associated data created by reading the configuration information stored in each of the storage units based on the request is configured in advance and stored as associated data combination information, and when the application cooperation unit receives a new request, the associated data corresponding to the new request is created from the associated data combination information. A related data extraction device characterized by:

6. 6. The related data extraction device according to claim 5, the plurality of storage units store time information when each of the pieces of configuration information stored in each of the storage units was registered or updated; The related data extraction unit The time information is stored when a combination of the associated data created from each of the configuration information stored in the plurality of storage units is configured in advance, and when the application cooperation unit receives a new request, the time when the associated data corresponding to the new request was created is stored. A related data extraction device characterized by:

7. 6. The related data extraction device according to claim 5, The related data extraction unit Parsing the request to obtain information on a search sort key, output information, and additional requests; Identifying the relevant data of the related data combination information based on each of the acquired information, If the identified data of the related data combination information is not being updated, the related data corresponding to the request is created from the related data combination information, and if the data is being updated, the related data corresponding to the request is created from the related data combination information after the update of the data is completed. A related data extraction device characterized by:

8. A system comprising: a related data extraction device that extracts related data related to data collected from a target system and that is to be assigned to the data; and a data processing platform that collects the data from the target system; The related data extraction device includes: a configuration data storage unit that manages configuration information of the target system; a configuration data input unit that accepts input for registering or updating the configuration information; an application cooperation unit that receives a request for the related data that is to be added to the data by an application that analyzes the data; a related data extraction unit that extracts the related data from the configuration information based on the request, The data processing platform includes an application for analyzing the collected data, requests the related data to be added to the data from the related data extraction device, obtains the related data from the related data extraction device, and adds the related data to the data. A related data extraction system.

9. The related data extraction device according to any one of claims 1 to 7, a data processing platform that collects the data from the target system; The data processing platform includes an application for analyzing the collected data, requests the related data to be added to the data from the related data extraction device, obtains the related data from the related data extraction device, and adds the related data to the data. A related data extraction system.

10. A related data extraction method executed by a related data extraction device that extracts related data related to data to be assigned to the data collected from a target system, comprising: Manage the configuration information of the target system in a configuration data storage unit; Accepting input for registering or updating the configuration information; an application analyzing the data receives a request for the associated data to be attached to the data; Extracting the relevant data from the configuration information based on the request. Each process has the request includes a request for supplemental data related to the data analyzed by the application; The data analyzed by the application is used to reference the configuration information, and the relevant data corresponding to the request is extracted. A related data extraction method comprising:

11. A related data extraction method executed by a related data extraction device that extracts related data related to data collected from a target system and assigns the related data to the data, comprising: Manage the configuration information of the target system in a configuration data storage unit; Accepting input for registering or updating the configuration information; an application analyzing the data receives a request for the associated data to be attached to the data; Extracting the relevant data from the configuration information based on the request. Each process has the configuration data storage unit manages the configuration information in a plurality of storage units; In response to the request, the configuration data storage unit selects a storage unit from the plurality of storage units and refers to the configuration information managed in the selected storage unit. A related data extraction method comprising:

12. A related data extraction program for causing a computer to function as the related data extraction device or related data extraction system according to any one of claims 1 to 9.

Images