Data management system and method thereof

Abstract

To manage change description data by discriminating data in synonymous relation from data in homonymous relation.SOLUTION: A data management system 1 comprises: a data storage unit which stores inspection data in time series obtained by inspecting an inspection object by an inspection device; a change description storage unit which stores data in synonymous relation or homonymous relation indicating that one of inspection specifications, inspection items and inspection objects is changed; a data extraction unit which extracts data from respective storage units; and a data extraction indication unit which outputs an extraction request including an object item to be extracted and time. The data extraction unit is configured to: extract, on receiving the extraction request, inspection data belonging to the time specified by the extraction request and corresponding to the object item to be extracted from the data storage unit; extract change description data including change contents of change time corresponding to the time specified by the extraction request from the change description storage unit; determine whether or not data in synonymous relation or homonymous relation is present in the extracted change description data; and normalize and output inspection data extracted based upon the determination result.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a data management system and method for managing inspection data. [Background technology]

[0002] When inspecting various manufactured products on each production line at a manufacturing site in a factory, the inspection results for each process are collected as inspection data, and the collected inspection data is analyzed. When analyzing data, for example, there is a technique for determining whether multiple columns that have similar attributes or store similar data are synonymous columns (columns that store the same information of the same management target) (see Patent Document 1). There is also a technique that makes it possible to absorb differences in the format of data generated by production equipment (see Patent Document 2). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2011-232879 A [Patent Document 2] JP 2020-57089 A Summary of the Invention [Problem to be solved by the invention]

[0004] When collecting inspection result data from each process, even for the same process, if the inspection specifications change over time, the meaning of the inspection result data will change. Also, data with the same meaning may be stored in different inspection items (data items). For example, if the processing of multiple inspection devices is distributed, the inspection results of inspection devices with different inspection specifications may become data with the same meaning depending on the processing method of each inspection device. For this reason, simply recording the change in the process in the inspection results makes it impossible to distinguish whether the inspection results are for the same inspection specifications or different inspection specifications, and unrelated data may be mixed in the inspection result data for each process, resulting in a lack of necessary data for the inspection results of each process.

[0005] An object of the present invention is to manage change description data by distinguishing between synonymous data and heterosynonymous data. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, the present invention provides a data storage unit that stores time-series inspection data obtained by an inspection device inspecting an inspection target, a change description storage unit that stores, in association with the inspection data, change description data that is data in a synonymous or heterosynonymous relationship indicating that at least one of the inspection specifications, the inspection items, or the inspection target of the inspection device has been changed, the change description data including the time of the change and the content of the change, a data extraction unit that uses the data storage unit and the change description storage unit as search targets and extracts data from the search target, and a data extraction instruction unit that outputs an extraction request including the extraction target item and the time to the data extraction unit. When the data extraction unit receives the extraction request, it searches for the search target based on the received extraction request, extracts from the data storage unit the inspection data that belongs to the time specified in the extraction request and corresponds to the extraction target item specified in the extraction request, extracts from the change description storage unit the change description data including the change content at the change time corresponding to the time specified in the extraction request, determines whether or not data of the synonymous relationship or the heterosynonymous relationship is present in the extracted change description data, and normalizes and outputs the extracted inspection data based on the determination result. Effect of the Invention

[0007] According to the present invention, change description data can be managed by distinguishing between synonymous data and heterosynonymous data. [Brief description of the drawings]

[0008] [Figure 1] 1 is a configuration diagram showing an example of the configuration of a data management system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a configuration diagram showing a display example of the display device according to the first embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram showing an example of the configuration of change description data according to the first embodiment of the present invention. [Figure 4] FIG. 11 is a configuration diagram showing another configuration example of change description data according to the first embodiment of the present invention. [Diagram 5]11 is a flowchart illustrating an example of pre-processing of a data extraction unit according to the first embodiment of the present invention. [Figure 6] 11 is a flowchart showing an example of a change description data extraction process of the data extraction unit according to the first embodiment of the present invention. [Figure 7] 5 is a flowchart showing an example of a data normalization process of the data extraction unit according to the first embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. EXAMPLES

[0010] Fig. 1 is a configuration diagram showing a configuration example of a data management system according to a first embodiment of the present invention. In Fig. 1, the data management system 1 is composed of a computer (not shown) including, for example, a processor, a main storage device, an auxiliary storage device, an input device, an output device, and a communication device, and is installed in a factory having a production line for manufacturing various products.

[0011] The processor is configured using, for example, a CPU (Central Processing Unit) and an MPU (Micro Processing Unit).

[0012] The main memory device is a device that stores computer programs and data, and is, for example, a Read Only Memory (ROM), a Random Access Memory (RAM), or a non-volatile semiconductor memory.

[0013] The auxiliary storage device is, for example, a hard disk drive, a solid state drive (SSD), an optical storage medium (i.e., a compact disc (CD) and a digital versatile disc (DVD)), a storage system, an integrated circuit card (IC card), a secure digital (SD) memory card, and other storage medium read / write devices, as well as a storage area of ​​a cloud server, etc. Computer programs and data stored in the auxiliary storage device are loaded into the main storage device as needed.

[0014] Examples of the input device include a keyboard, a mouse, a touch panel, a card reader, an audio input device, etc. The output device (display device) is a user interface that provides the user with various information such as the progress and results of processing. Examples of the output device include a screen display device (i.e., a liquid crystal monitor, LCD (Liquid Crystal Display), or a graphics card), an audio output device (i.e., a speaker, etc.), or a printing device, etc.

[0015] The communication device is a wired or wireless communication interface that realizes communication with other devices via a communication means such as a LAN, the Internet, etc. The communication device is, for example, a network interface card (NIC), a wireless communication module, a universal serial bus (USB) module, or a serial communication module.

[0016] The data management system 1 includes, as software resources, a change input unit 10, a change description registration unit 12, a change description storage unit 14, a data generation unit 16, a data registration unit 18, a data storage unit 20, a data extraction unit 22, a data extraction instruction unit 24, and an extracted data storage unit 26.

[0017] The change input unit 10 inputs information according to the operation of the change inputter as information from an operation terminal operated by the change inputter, such as a keyboard or mouse. For example, the change input unit 10 inputs information indicating the time (change time) when at least one of the inspection specifications, inspection items, and inspection devices in each process of the production line was changed and the change content (change content). The change description registration unit 12 registers the input information, which is information input from the change input unit 10 and includes the change time and the change description, in the change description storage unit 14. At this time, if information related to the change description belonging to the input information already exists in the change description storage unit 14, the change description registration unit 12 updates the already existing information with the input information and registers it. The change description data belonging to the input information stored in the change description storage unit 14 is data of synonymous or heterosynonymous relationship, and is stored in the storage area sequentially as time-series data.

[0018] Here, the synonymous data means, for example, that the performance or function of a plurality of inspection devices is the same. The different synonymous data means, for example, that the inspection specifications for one of the plurality of inspection devices are different from the inspection specifications for the other inspection device. In addition, when the time, for example, the change time (change time) is t1, t2, t3, ..., t(n-1), tn, the change description data at each change time t1 to tn is stored in the storage area of ​​the change description storage unit 14 in sequence for each change time. At this time, the data extraction unit 22, which will be described later, manages the change description data stored in the change description storage unit 14 by setting the time period between the change time t1 and the change time t2 as phase 1, the time period between the change time t2 and the change time t3 as phase 2, ..., and the time period between the change time t(n-1) and the change time tn as phase (n-1).

[0019] The data generation unit 16 imports data from an inspection device or the like at the production site, such as product inspection data, generates data in which information such as the inspection time and the work target is added to the imported inspection data, and transfers the generated data to the data registration unit 18. When the data registration unit 18 receives inspection data transferred from the data generation unit 164, it registers the received inspection data in the data storage unit 20. At this time, when the received inspection data is in CSV (Comma Separated Value) format, the data registration unit 18 converts the CSV format inspection data into, for example, JSON (javaScript (registered trademark) Object Notation) format inspection data, and registers the converted inspection data in the data storage unit 20.

[0020] When data such as test data is stored in the data storage unit 20, each data is stored in a storage area in sequence as time-series data. Here, if the time stamps indicating the time of the test or the time of data collection are t1, t2, t3, . . . , t(n-1), tn, the data at each time stamp t1 to tn is stored in the storage area of ​​the data storage unit 20 in sequence for each time stamp. In this case, the data extraction unit 22, which will be described later, manages the data stored in the data storage unit 20 by setting the time period between the time stamp t1 and the time stamp t2 as phase 1, the time period between the time stamp t2 and the time stamp t3 as phase 2, . . . , and the time period between the time stamp t(n-1) and the time stamp tn as phase (n-1). In this embodiment, for convenience of explanation, the time stamps t1 to tn of the data stored in the data storage unit 20 and the change times t1 to tn of the change description data stored in the change description storage unit 14 are set to the same time.

[0021] When an extraction request including an item to be extracted (data item) and time (change time) is input from data extraction instruction unit 24 operated by a data extraction supporter, data extraction unit 22 searches change description storage unit 14 and data storage unit 20 as search targets based on the extraction request, extracts change description data from change description storage unit 14 and test data from data storage unit 20 as data for the time specified in the extraction request, normalizes the test data extracted from data storage unit 20 by the contents of the change description data specified by the test data with the time specified in the extraction request (change time) as the reference time, and stores the normalized data in extracted data storage unit 26.

[0022] In the software resources of the data management system 1, the processor reads and executes the computer programs stored in the main memory device, thereby realizing various functions of the change input unit 10, the change description registration unit 12, the change description storage unit 14, the data generation unit 16, the data registration unit 18, the data storage unit 20, the data extraction unit 22, the data extraction instruction unit 24, and the extracted data storage unit 26.

[0023] FIG. 2 is a configuration diagram showing a display example of the display device according to the first embodiment of the present invention. In FIG. 2, the display screen 100 of the display device is a screen for a change input person to operate an operation terminal to input information into the data management system 1, and is composed of a change time column 101, a change form column 102, an equivalent device ID column 103, an added device ID column 104, and a line configuration diagram display area 105. When the change input person performs an operation to change the time when the data such as the inspection specification is changed to, for example, "January 12, 2021, 8:12:43", the change time column 101 displays information of "2021-01-12T08:12:43+0900". When the change input person performs an operation to add an equivalent device as an inspection device, for example, the change form column 102 displays information of "equivalent device added". When the change input person performs an operation to specify an inspection device (equivalent device) that is connected in parallel to the added inspection device (additional device) and has the same performance as the added device, the equivalent device ID column 103 displays information such as "E12" as a device identifier that uniquely identifies the equivalent device. When the change input person performs an operation to specify the added inspection device (additional device), the added device ID column 104 displays information such as "E13" as a device identifier that uniquely identifies the added device. The line configuration display area 105 displays device identifiers ("E01", "E11", "E12", "E21", "E31") that uniquely identify each inspection device (device) belonging to the line configuration of the production line E, and information on connection lines that indicate the connection relationship between each device. In this case, the added device with device identifier E13 is added to the production line E in a state of being connected in parallel to the equivalent device with device identifier E12. As a result, in the manufacturing line E, after the change time, the inspection result data of the equivalent device (E12) and the inspection result data of the additional device (E13) are managed as the same data.

[0024] The display screen 200 of the display device is a screen for the change input person to operate the operation terminal to input information into the data management system 1, and is composed of a change time column 201, a change form column 202, an old item ID column 203, a new item ID column 204, a conversion rule column 205, and a line configuration diagram display area 206. When the change input person performs an operation to change the time when the data such as the inspection specifications related to the inspection device (E21) was changed to, for example, "January 12, 2021, 8:12:43", the change time column 201 displays the information "2021-01-12T08:12:43+0900". When the change input person performs an operation to change the inspection specifications of the inspection device (E21) in the production line E, for example, the change form column 202 displays the information "inspection specification change". When the change input person performs an operation to identify an item before the change in the inspection specifications of the inspection device (E21) in production line E, information such as "E21-a" is displayed in the old item ID column 203 as the inspection item identifier that identifies the old item in the inspection specifications. When the change input person performs an operation to identify an item after the change in the inspection specifications of the inspection device (E21) in production line E, information such as "E21-a'" is displayed in the new item ID column 204 as the inspection item identifier that identifies the new item in the inspection specifications.

[0025] When the change input user performs an operation to convert the inspection specifications of the old conversion rule to those of the new conversion rule, for example, information of "E21-a'=E21-a*0.01" is displayed in the conversion rule column 205 as the conversion rule for converting the inspection specifications of the old conversion rule to those of the new conversion rule. This means that the scale for data belonging to data item E21-a after the change time "January 12, 2021, 8:12:43" is 1 / 100, and in order to align the scale of the data of each phase for calculation, the data before the change time is multiplied by 0.01 for comparison.

[0026] The line configuration display area 206, like the line configuration display area 105, displays equipment identifiers ("E01", "E11", "E12", "E21", "E31") that uniquely identify each piece of equipment that makes up the production line E, and information indicating the connection relationships between each piece of equipment.

[0027] Fig. 3 is a configuration diagram showing an example of the configuration of change description data according to the first embodiment of the present invention. In Fig. 3, the change description storage unit 14 stores change description data 300 including, for example, change descriptions of synonymous relationships. The change description data 300 is data written in a JSON data format, and is an example of a description of data of synonymous relationships. In the change description data 300, for example, when equipment E13 (equipment having a synonymous relationship with equipment E12) having the same performance as equipment E12, which is an inspection device, is added to production line E at the time "January 12, 2021, 8:12:43", the data "2021-01-12T08:12:43+0900" is recorded as the value ("rdf:value") of the change time (change time) identified by "cd:from", the data of "E12" is recorded as the value ("line:name") of the equivalent equipment, which is the value identified by "cd:object", and the data of "E13" is recorded as the value ("cd:addedSame") of the added equipment.

[0028] At this time, it can be determined that the change description data 300 is composed of synonymous data from the data identifying the added device ("cd:addedSame") and its value ("E13"), and the data identifying the equivalent device ("line:name") and its value ("E13"). In other words, it can be determined that device E12 and device E13 are devices having a synonymous relationship with each other. After this data is stored, if a change occurs that cancels the stored data, an operation is executed to add the time when the data to be canceled became invalid, using "cd:expiredAt" as a key, in the same format as "cd:from".

[0029] FIG. 4 is a configuration diagram showing another configuration example of the change description data according to the first embodiment of the present invention. In FIG. 4, the change description storage unit 14 stores, for example, change description data 400 including a change description of a synonymous relationship. The change description data 400 is data described in a JSON data format, and is an example of a description of data of a synonymous relationship. In this change description data 400, for example, when the inspection specifications of an inspection device are changed and the inspection item is changed from the old item to the new item at 8:12:43 on January 12, 2021, the data of "2021-01-12T08:12:43+0900" is recorded as the value "rdf:value" of the change time (change time) specified by "cd:from". In addition, in the change description data 400, the data "E21-a" is recorded as the value of the old item "cd:fromItem" (item name) identified by "cd:object", the data "E21-a'" is recorded as the value of the new item "cd:toItem", and the data "E21-a'=E21-a*0.01" is recorded as the value of the conversion rule "cd:convEq".

[0030] At this time, it can be determined that the change description data 400 is composed of data with a synonymous relationship from the data specifying the old item ("cd:fromItem") and its item name data ("E21-a"), the data specifying the new item ("cd:toItem") and its item name data ("E21-a'"), and the data specifying the conversion rule ("cd:convEq"). In other words, since the old item (test item) and the new item (search item) have different test specifications and are synonymous with each other, it can be determined that a conversion rule has been specified.

[0031] The changed conversion rule means that after the change time, the data of the old item is multiplied by the constant "0.01" so that the scale when calculating the data is 1 / 100. If a change occurs that cancels the stored data after this data is stored, an operation is executed to add the time when the data to be canceled became invalid, in the same format as "cd:from", with "cd:expiredAt" as the key.

[0032] Fig. 5 is a flow chart showing an example of pre-processing of the data extraction unit according to the first embodiment of the present invention. In Fig. 5, the data extraction unit 22 searches the change description data 300, 400 stored in the change description storage unit 14 as the search target, and extracts the time (change time) at which some change occurred from the change description data stored in the change description storage unit 14, for example, the change description data 300, 400 (S11). At this time, for example, if change times (change times) t1, t2, t3, ..., tn exist in the change description data 300, 400 stored in the change description storage unit 14, these change times t1 to tn are extracted.

[0033] Next, the data extraction unit 22 extracts one or more change times (change times) that are included in the period during which each change description is valid from each change description data stored in the change description storage unit 14, and divides each change description by the extracted change times (one or more change times) (S21). For example, if the valid period of a certain change description A is from change time a to change time b, and a change time that belongs to the valid period of change time a to change time b is t3 (change time a < change time t3 < change time b), then change description A is divided into change description A1 that belongs to change time a to change time t3, and change description A2 that belongs to change time t3 to change time b. Here, the valid period means that change time a to change time b is within the valid period of change description A when the change time of the change content that has a change time later than change time a of change description A and is closest to change description A among the change contents that overwrite the change contents included in change description A (for example, a change description that says that device E12 and device E13 no longer have the same meaning appears after a change description that adds device E13, which has the same meaning as device E12), is change time b.

[0034] Fig. 6 is a flow chart showing an example of a change description data extraction process of the data extraction unit according to the first embodiment of the present invention. In Fig. 6, when an extraction request is input from a data extraction instructing person via the data extraction instruction unit 24 with an instruction to "extract data item i_q at time t_q", the data extraction unit 22 searches for change description data in the change description storage unit 14 based on the time t_q, identifies a phase (time period) that includes the change time t_q among the change description data, and sets the identified phase as phase p_q (S21). In the following, t means time, i means item, p means phase, q means a number such as time and phase, and conv means convert.

[0035] Next, the data extraction unit 22 collects data (synonymous relationship description data) indicating descriptions of synonymous relationships included in the identified phase p_q from the change description data from the change description storage unit 14, extracts data items synonymous with the data item i_q instructed by the data extraction instructor from the collected synonymous relationship description data, and updates the data item i_q with the extracted data item (S22). For example, from the change description data 300 in Fig. 3, if the data item i_q instructed by the data extraction instructor is "line:name": "E12", "cd:addedSame": "E13" is extracted as a data item synonymous with this data item.

[0036] Next, the data extraction unit 22 initializes the initial value of the variable c with the value of q used in the phase p_q (S23).

[0037] Next, the data extraction unit 22 collects data (opposite synonym description data) showing the change description of the opposite synonym relationship targeting the data item i_c from among the change description data stored in the change description storage unit 14, and creates a conversion rule set conv_c-1_c for the data of phase p_c-1 based on the collected opposite synonym description data (S24). For example, as a change description of the opposite synonym relationship targeting the data item i_c, one that includes the data item i_c in "cd:toItem" in FIG. 4 (E21-a) is collected, and based on the collected data, a conversion rule set conv_c-1_c for the data of phase p_c-1 (data of the change description having the change time included in phase p_c-1) is created. Specifically, a change description having a time in phase p_c-1 as the change time, for example, information "E21-a'=E21-a*0.01" of the conversion rule "cd:convEq" in FIG. 4 is created as the conversion rule set conv_c-1_c. In this case, this means that data item E21-a' after the change time: 8:12:43 on January 12, 2021 will have the same value as 1 / 100 of the value of data item E21-a before that. Therefore, by dividing the value of the data item before the above change time by 1 / 100, the value of the data item before the above change time can be compared on the same basis as the value of the data item belonging to phase p_c of the above change time.

[0038] Next, the data extraction unit 22 extracts, from each change description data stored in the change description storage unit 14, change description data belonging to the phase p_c-1 immediately before the phase p_c and having a synonymous relationship (S25). For example, from the change description data 300 shown in FIG. 3, information on "@type:cd:addEquipment" ("E13") is extracted as change description data specifying an added device. In addition, in step S25, the data extraction unit 22 extracts, from each change description data stored in the change description storage unit 14, a data item synonymous with the data item appearing in "line:name" among the synonymous relationships in the phase p_c, and sets the extracted data item as data item i_c-1. For example, from the change description data 300 shown in FIG. 3, as a data item synonymous with the data item E12 appearing in "line:name", the data item "cd:addedSame": "E13" indicating that equipment E13 equivalent to E12 has been added is set as data item i_c-1.

[0039] Next, the data extraction unit 22 sets the variable c to c-1 (S26), and determines whether or not the variable c is greater than 0 (S27). If the variable c is greater than 0, the process returns to step S24, and repeats the processes of steps S24 to S27 to collect data before the change time t_q until the variable c becomes 0. If the variable c is less than 0, the process proceeds to step S28, and the variable c is set to q again.

[0040] Next, the data extraction unit 22 collects change description data that indicates a change description of a different meaning relationship belonging to phase p_c+1 and targets the data item i_c from among the change description data stored in the change description storage unit 14, and creates a conversion rule set conv_c+1_c for data belonging to phase p_c+1 based on the collected change description data (S29). For example, as change description data of a different meaning relationship belonging to phase p_c+1 and targets the data item i_c, from the change description data 400 in FIG. 4, data that includes information (E12) of the data item i_c in "cd:from:Item" is collected. At this time, the conversion rule set conv_c+1_c for data belonging to phase p_c+1 is, for example, information ("E21-a'=E21-a*0.01") specified by "cd:convEq" in FIG. 4 among the change description data that has a time in phase p_c+1 as the change time. This means that the data of data item E21-a' from the change time (change time): 8:12:43 on January 12, 2021 onwards will be 1 / 100th the value of the data of data item E21-a prior to that time. For this reason, by applying the inverse function conversion rules to data items after the above change time and multiplying the data values ​​of data items after the above change time by 100, the data values ​​of data items after the above change time can be compared on the same basis as the data values ​​of data items belonging to phase p_c of the above change time.

[0041] Next, in step S30, the data extraction unit 22 extracts, from each change description data stored in the change description storage unit 14, change description data in a synonymous relationship that belongs to the phase p_c+1 that follows the phase p_c. For example, from the change description data 300 shown in FIG. 3, information on "@type:cd:addEquipment" ("E13") is extracted as change description data that specifies an added device. Next, in step S30, the data extraction unit 22 deletes the data item that appears in "cd:addedSame" of the change description data in phase p_c+1 from the data item i_c to be extracted in phase p_c. For example, it deletes "E13", which is information on the data item specified by "cd:addedSame". This is because the data item specified by "cd:addedSame" among the change description data in phase p_c+1 does not become a change description in a synonymous relationship after phase p_c+1.

[0042] After that, in step S30, the data extraction unit 22 creates an initial value i_c+1 of the data item i_c to be extracted, from which the data item specified by "cd:addedSame" has been deleted, extracts data items synonymous with the initial value i_c+1 from each change description data stored in the change description storage unit 14, and updates the initial value i_c+1 with the extracted data items. At this time, the data items from which the data item i_c to be extracted in phase p_c has been deleted from the group of synonymous data items are set as the group of synonymous data items in phase p_c+1. Also, if information (E12) of a data item appearing in "line:name" in FIG. 3 is included in the initial value i_c+1 in the change description data of phase p_c+1, information (E13) of the data item specified by "cd:addedSame" corresponding to "line:name" is extracted as a data item synonymous with the initial value i_c+1, and the extracted information is added to the initial value i_c+1.

[0043] Next, the data extraction unit 22 sets the variable c to c+1 (S31), and then determines whether the variable c is smaller than n (n: an integer indicating the number of change times) (S32). If the variable c is smaller than n, the process returns to step S29, and the processes of steps S29 to S32 are repeated to collect data after the change time tq until the variable c becomes larger than n. If the variable c is larger than n, the process ends, assuming that all processes have been completed.

[0044] 7 is a flowchart showing an example of data normalization processing of the data extraction unit according to the first embodiment of the present invention. In FIG. 7, the data extraction unit 22 sets a variable k corresponding to a phase p to 1 (S41), and extracts a data item having a timestamp in the phase p_k and included in the extraction target item i_k from the data storage unit 20 (S42). For example, when "timestamp:2021-01-10T08:12:12+0900" is stored as timestamp information in the data storage unit 20, and "E12-a:10" and "E13-z:20" are stored as data item information, these pieces of information are extracted from the data storage unit 20.

[0045] Next, the data extraction unit 22 converts the meaning of the data item extracted from the data storage unit 20 using the conversion rule conv_pk_pk+1 (S43). For example, when the same conversion rule as the conversion rule set conv_c-1_c created in step S24 of Fig. 6 is used as the conversion rule conv_pk_pk+1, the meaning of the data item is converted using the conversion rule "E21-a'=E21-a*0.01". At this time, if the data item extracted from the data storage unit 20 contains information of "E21", the process of multiplying the value by "0.01" is executed.

[0046] Next, the data extraction unit 22 treats the data belonging to phase p_k, among the data collected from the data storage unit 20, as data of phase p_k+1 thereafter (S44). That is, the data of phase p_k is converted to data of phase p_k+1 using the conversion rule for phase p_k+1, and therefore, after conversion, it is processed as data of phase p_k+1.

[0047] Next, data extraction unit 22 sets the value of variable k to k+1 (S45), and then determines whether variable k is smaller than phase number q (S46). If variable k is smaller than phase number q, it returns to step S42 and repeats the processes of steps S42 to S46 until variable k becomes larger than phase number q. If variable k is larger than phase number q, it sets variable k to n-1 and initializes variable k to the last phase number (n-1) (S47).

[0048] Next, the data extraction unit 22 extracts data items that have a timestamp in the phase p_k and are included in the extraction target item i_k from the data storage unit (S48). For example, if the data storage unit 20 stores "timestamp:2021-01-10T08:12:12+0900" as the timestamp information and "E12-a:10" and "E13-z:20" as the data item information, these pieces of information are extracted from the data storage unit 20.

[0049] Next, the data extraction unit 22 converts the meaning of the data item extracted from the data storage unit 20 using the conversion rule conv_pk_pk-1 (S49). For example, when using an inverse function conversion rule as the conversion rule conv_pk_pk-1, which is the same conversion rule as the conversion rule group conv_c-1_c created in step S29 of Fig. 6, the conversion rule "E21-a'=E21-a*0.01" is used to convert the meaning of the data item. At this time, if the data item extracted from the data storage unit 20 contains information of "E21", the process of multiplying the value by "100" is executed according to the inverse function conversion rule.

[0050] Next, the data extraction unit 22 handles the data collected from the data storage unit 20 as data belonging to phase p_k as data of phase p_k-1 thereafter (S50). That is, the data of phase p_k is converted to data of phase p_k-1 using the conversion rule for phase p_k-1, and therefore, after conversion, it is processed as data of phase p_k-1.

[0051] Next, the data extraction unit 22 sets the value of variable k to k-1 (S51), and then determines whether variable k is greater than phase number q (S52).If variable k is greater than phase number q, the process returns to step S48 and repeats the processing of steps S48 to S52 until variable k becomes smaller than phase number q.If variable k is smaller than phase number q, the process proceeds to step S53.

[0052] In step S53, the data extraction unit 22 stores all data including the data converted in step S43 and the data converted in step S49 as data of phase p_q in the extracted data storage unit 20, notifies the data extraction supporter via the data extraction instruction unit 24 that data storage has been completed, and then ends the processing in this routine. At this time, the data of phase p_q means data obtained by normalizing the data of phases p_1 to p_n-1 at the point of change time t_q.

[0053] In this embodiment, when the data extraction unit 22 receives an extraction request, it extracts from the data storage unit 20 the test data that belongs to the time specified in the extraction request and corresponds to the extraction target item specified in the extraction request, extracts from the change description storage unit 14 the change description data at the change time that belongs to the time specified in the extraction request, judges whether or not there is synonymous or different synonymous data in the extracted change description data, and normalizes and outputs the extracted test data based on the judgment result. That is, when a change occurs in the data, the content of the change and the change time are recorded in the change description data as synonymous or different synonymous data, so that even if the content of the change is synonymous or different synonymous, the test data of the extraction target item specified in the extraction request can be extracted by normalizing it according to the content of the test data at the reference time based on the time specified in the extraction request, and as a result, it is possible to extract test data based on any point (time) instructed in the extraction request.

[0054] Furthermore, when extracting the test data, the data extraction unit 22 can extract the test data that belongs to a time period before the reference time indicating the time specified in the extraction request and corresponds to the extraction target item specified in the extraction request from the data storage unit 20 as the test data that belongs to a time period before the reference time. Furthermore, when determining the change description data, the data extraction unit 22 can determine whether or not there is data with a synonymous or different synonymous relationship in the change description data that belongs to a time period before the reference time, and can normalize the test data that belongs to a time period before the reference time according to the change content corresponding to the test data at the reference time based on the determination result. That is, even if there is a change in the data in the time period before the reference time, if the content of the change and the change time are recorded in the change description data as data with a synonymous or different synonymous relationship, even if the content of the change in the data in the time period before the reference time is synonymous or different synonymous, the test data of the extraction target item specified in the extraction request and in the time period before the reference time can be extracted by normalizing it according to the change content corresponding to the test data at the time based on the time specified in the extraction request.

[0055] Furthermore, when extracting the test data, the data extraction unit 22 can extract the test data belonging to a time period after the reference time indicating the time specified in the extraction request and corresponding to the extraction target item specified in the extraction request from the data storage unit 20 as the test data belonging to a time period after the reference time. Furthermore, when determining the change description data, the data extraction unit 22 can determine whether or not there is data of synonymous or different synonymous relationship in the change description data belonging to a time period after the reference time, and normalize the test data belonging to a time period after the reference time according to the change content corresponding to the test data at the reference time based on the determination result. That is, even if there is a change in the data in the time period after the reference time, if the content of the change and the change time are recorded in the change description data as data of synonymous or different synonymous relationship, even if the content of the change in the data in the time period after the reference time is synonymous or different synonymous relationship, the test data of the extraction target item specified in the extraction request and in the time period after the reference time can be extracted by normalizing it according to the change content corresponding to the test data at the time based on the time specified in the extraction request.

[0056] In addition, when the data extraction unit 22 determines that synonymous data exists in the change description data belonging to a time period earlier than the reference time, it converts the test data belonging to a time period earlier than the reference time based on the synonymous data in the change description data, and normalizes the test data belonging to a time period earlier than the reference time that has been converted using the synonymous data to match the change content corresponding to the test data at the reference time; when the data extraction unit 22 determines that opposite-synonymous data exists in the change description data belonging to a time period earlier than the reference time, it creates opposite-synonym conversion rules based on the data, converts the test data belonging to a time period earlier than the reference time based on the created opposite-synonym conversion rules, and normalizes the test data belonging to a time period earlier than the reference time that has been converted using the opposite-synonym conversion rules to match the change content corresponding to the test data at the reference time.

[0057] For example, when data belonging to the change description data 300 exists as synonymous data in the change description data belonging to a time period before the reference time, the check data specified by these data are normalized according to the change content corresponding to the check data at the reference time, so that the synonymous check data belonging to the time period before the reference time can be handled on the same scale as the check data at the reference time. When data belonging to the change description data 400 exists as different synonymous data in the change description data belonging to a time period before the reference time, the check data specified by these data are converted by the conversion rule generated by the change description data 400, and the converted check data is normalized according to the change content corresponding to the check data at the reference time, so that the different synonymous check data belonging to the time period before the reference time can be handled on the same scale as the check data at the reference time.

[0058] In addition, when the data extraction unit 22 determines that synonymous data exists in the change description data belonging to a time period after the reference time, it converts the test data belonging to a time period after the reference time based on the synonymous data in the change description data, and normalizes the test data belonging to a time period after the reference time that has been converted using the synonymous data to match the change content corresponding to the test data at the reference time; when the data extraction unit 22 determines that opposite-synonymous data exists in the change description data belonging to a time period after the reference time, it creates opposite-synonym conversion rules based on the data, converts the test data belonging to a time period after the reference time based on the created opposite-synonym conversion rules, and normalizes the test data belonging to a time period after the reference time that has been converted using the opposite-synonym conversion rules to match the change content corresponding to the test data at the reference time.

[0059] For example, when data belonging to the change description data 300 exists as synonymous data in the change description data belonging to a time period after the reference time, the check data specified by these data are normalized according to the change content corresponding to the check data at the reference time, so that the synonymous check data belonging to a time period after the reference time can be handled on the same scale as the check data at the reference time. When data belonging to the change description data 400 exists as different synonymous data in the change description data belonging to a time period after the reference time, the check data specified by these data are converted by the conversion rule generated by the change description data 400, and the converted check data is normalized according to the change content corresponding to the check data at the reference time, so that the different synonymous check data belonging to a time period after the reference time can be handled on the same scale as the check data at the reference time.

[0060] Furthermore, the change description registration unit 12 can register change description data different from the change description data stored in the change description storage unit 14, for example new change description data, based on the operation of the person inputting the change. This makes it possible to efficiently follow changes in the field, even if there is a new change in the inspection specifications, etc., on the production line at the field, to distinguish between synonymous data and non-synonymous data and manage the change description data by simply adding the content of the new change to the change description data without rewriting the information and procedures required for normalizing the inspection data.

[0061] According to this embodiment, it is possible to distinguish between synonymous data and non-synonymous data and manage change description data, and as a result, it is possible to extract inspection data based on any point (time) specified in the extraction request.

[0062] The present invention is not limited to the above-described embodiment, but includes various modifications and equivalent configurations within the spirit of the appended claims. For example, the change description storage unit 14 and the data storage unit 20 can be integrated as a database or a memory unit. The above-described embodiment has been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to one having all of the described configurations.

[0063] In addition, each of the configurations, functions, etc. described above may be realized in hardware, for example by designing some or all of them as an integrated circuit, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0064] Information such as programs, tables, files, etc. that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC (Integrated Circuit) card, an SD card, or a DVD (Digital Versatile Disc). [Explanation of symbols]

[0065] 1 data management system, 10 change input section, 12 change description registration section, 14 change description storage section, 16 data generation section, 18 data registration section, 20 data storage section, 22 data extraction section, 24 data extraction instruction section, 26 extracted data storage section

Claims

1. a data storage unit for storing time-series inspection data obtained by the inspection device inspecting the inspection object; a change description storage unit for storing change description data, which is data of a synonymous or heterosynonymous relationship indicating that at least one of the inspection specifications, the inspection items, or the inspection target of the inspection device has been changed, the change description data including the time of the change and the content of the change, in association with the inspection data; a data extraction unit that searches the data storage unit and the change description storage unit to extract data from the search target; a data extraction instruction unit that outputs an extraction request including an extraction target item and a time to the data extraction unit, The data extraction unit includes: a data management system characterized in that, when the extraction request is received, the search target is searched based on the received extraction request, the inspection data belonging to the time specified in the extraction request and corresponding to the extraction target item specified in the extraction request is extracted from the data storage unit, the change description data including the change content at the change time corresponding to the time specified in the extraction request is extracted from the change description storage unit, whether or not data of the synonymous relationship or the heterosynonymous relationship is present in the extracted change description data, and the extracted inspection data is normalized and output based on the result of the determination.

2. 2. The data management system according to claim 1, The data extraction unit includes: A data management system characterized in that the test data which belongs to a time period before a reference time indicating the time specified in the extraction request and corresponds to the extraction target item specified in the extraction request is extracted from the data storage unit as test data belonging to a time period before the reference time, the data management system determines whether or not the synonymous or heterologous data exists in the extracted change description data which belongs to a time period before the reference time, and based on the determination result, normalizes the test data which belongs to a time period before the reference time to the change content corresponding to the test data at the reference time.

3. 2. The data management system according to claim 1, The data extraction unit includes: A data management system characterized in that the test data which belongs to a time period later than a reference time indicating the time specified in the extraction request and corresponds to the extraction target item specified in the extraction request is extracted from the data storage unit as test data belonging to a time period later than the reference time, the data management system determines whether or not the synonymous or heterologous data exists in the extracted change description data which belongs to a time period later than the reference time, and normalizes the test data which belongs to a time period later than the reference time based on the result of the determination to match the change content corresponding to the test data at the reference time.

4. 3. The data management system according to claim 2, The data extraction unit includes: a data management system comprising: when it is determined that synonymous data exists in the change description data belonging to a time period earlier than the reference time, the system converts inspection data belonging to a time period earlier than the reference time based on the synonymous data in the change description data, and normalizes the inspection data belonging to a time period earlier than the reference time that has been converted using the synonymous data to match the change content corresponding to the inspection data at the reference time; and when it is determined that opposite synonymous data exists in the change description data belonging to a time period earlier than the reference time, the system creates opposite synonymous data conversion rules based on the opposite synonymous data, converts inspection data belonging to a time period earlier than the reference time based on the created opposite synonymous conversion rules, and normalizes the inspection data belonging to a time period earlier than the reference time that has been converted using the opposite synonymous conversion rules to match the change content corresponding to the inspection data at the reference time.

5. 4. The data management system according to claim 3, The data extraction unit includes: a data management system comprising: when it is determined that synonymous data exists in the change description data belonging to a time period later than the reference time, the system converts inspection data belonging to a time period later than the reference time based on the synonymous data in the change description data, and normalizes the inspection data belonging to a time period later than the reference time that has been converted using the synonymous data to match the change content corresponding to the inspection data at the reference time; and when it is determined that opposite synonymous data exists in the change description data belonging to a time period later than the reference time, the system creates opposite synonymous data conversion rules based on the opposite synonymous data, converts inspection data belonging to a time period later than the reference time based on the created opposite synonymous conversion rules, and normalizes the inspection data belonging to a time period later than the reference time that has been converted using the opposite synonymous conversion rules to match the change content corresponding to the inspection data at the reference time.

6. 2. The data management system according to claim 1, 2. A data management system further comprising a change description registration section for registering change description data different from the change description data stored in the change description storage section.

7. A method for managing data in a database using a computer, comprising: a data storage step in which the computer stores in the database time-series inspection data obtained by the inspection device inspecting the inspection object; a change description storage step in which the computer stores in the database, in association with the inspection data, change description data which is synonymous or heterosynonymous data indicating that at least one of the inspection specifications, the inspection items, or the inspection targets of the inspection device has been changed, the change description data including the time of the change and the content of the change; a data extraction step in which the computer searches the database and extracts data from the search target; a data extraction instruction step of outputting an extraction request including an extraction target item and a time, The computer includes: In the data extraction step, A data management method characterized in that, when the extraction request is received, the search target is searched based on the received extraction request, the inspection data belonging to the time specified in the extraction request and corresponding to the extraction target item specified in the extraction request is extracted from the database, the change description data including the change content at the change time corresponding to the time specified in the extraction request is extracted from the database, whether or not the synonymous or heterosynonymous data is present in the extracted change description data, and the extracted inspection data is normalized and output based on the result of the determination.

8. 8. The data management method according to claim 7, The computer includes: In the data extraction step, A data management method characterized by extracting from the database the test data that belongs to a time period earlier than a reference time indicating the time specified in the extraction request and that corresponds to the extraction target item specified in the extraction request as test data belonging to a time period earlier than the reference time, determining whether or not the synonymous or heterologous data exists in the extracted change description data that belongs to a time period earlier than the reference time, and normalizing the test data that belongs to a time period earlier than the reference time based on the determination result to match the change content corresponding to the test data at the reference time.

9. 8. The data management method according to claim 7, The computer includes: In the data extraction step, A data management method characterized by: extracting from the database the test data that belongs to a time period after a reference time indicating the time specified in the extraction request and that corresponds to the extraction target item specified in the extraction request as test data belonging to a time period after the reference time; determining whether or not the synonymous or heterologous data exists in the extracted change description data that belongs to a time period after the reference time; and normalizing the test data that belongs to a time period after the reference time based on the result of the determination to match the change content corresponding to the test data at the reference time.

10. 9. The data management method according to claim 8, The computer includes: In the data extraction step, a data management method comprising: when it is determined that synonymous data exists in the change description data belonging to a time period earlier than the reference time, converting inspection data belonging to a time period earlier than the reference time based on the synonymous data in the change description data, and normalizing the inspection data belonging to a time period earlier than the reference time that has been converted using the synonymous data to match the change content corresponding to the inspection data at the reference time; when it is determined that opposite synonymous data exists in the change description data belonging to a time period earlier than the reference time, creating an opposite synonymous data conversion rule based on the opposite synonymous data, converting the inspection data belonging to a time period earlier than the reference time based on the created opposite synonymous conversion rule, and normalizing the inspection data belonging to a time period earlier than the reference time that has been converted using the opposite synonymous conversion rule to match the change content corresponding to the inspection data at the reference time.

11. 10. The data management method according to claim 9, The computer includes: In the data extraction step, a data management method comprising: when it is determined that synonymous data exists in the change description data belonging to a time period later than the reference time, converting inspection data belonging to a time period later than the reference time based on the synonymous data in the change description data, and normalizing the inspection data belonging to a time period later than the reference time that has been converted using the synonymous data to match the change content corresponding to the inspection data at the reference time; when it is determined that opposite synonymous data exists in the change description data belonging to a time period later than the reference time, creating an opposite synonymous data conversion rule based on the opposite synonymous data, converting inspection data belonging to a time period later than the reference time based on the created opposite synonymous conversion rule, and normalizing the inspection data belonging to a time period later than the reference time that has been converted using the opposite synonymous conversion rule to match the change content corresponding to the inspection data at the reference time.

12. 8. The data management method according to claim 7, A data management method further comprising a change description registration step in which the computer registers in the database change description data different from the change description data stored in the database.

Images