Data acquisition device, program, and data acquisition method

Abstract

The data acquisition device (300) includes: a data collector (311) that collects RAW data; a primary data parser (321) that obtains data for parsing, extracts parsing records of a specified category from the data for parsing based on a data array of the data for parsing, and performs a specified parsing process on the extracted parsing records to generate result data; a database accessor (331) that converts registration data into a specified database format based on a data array of the registration data and registers it in a database (332); and an application manager (334) that controls the data flow among the data collector (311), the primary data parser (321), and the database accessor (331).

Description

Technical Field

[0001] The present disclosure relates to a data acquisition device, a program, and a data acquisition method. Background Art

[0002] In Patent Document 1, a data acquisition device is disclosed that acquires data from each device on a production line and appends the acquired data to a database. The data acquisition device includes: an acquisition unit that acquires a file containing the data and a file name from the device; an extraction unit that extracts additional information related to the data from the file name acquired by the acquisition unit; and an append unit that appends the additional information extracted by the extraction unit to the data in the file acquired by the acquisition unit and appends it to the database.

[0003] Prior Art Documents

[0004] Patent Documents

[0005] Patent Document 1: Japanese Unexamined Patent Application Publication No. 2013-225317 Summary of the Invention

[0006] Problems to be Solved by the Invention

[0007] An object of the present disclosure is to provide a data acquisition device that can effectively balance the ease of database expansion and the ease of database utilization.

[0008] Means for Solving the Problems

[0009] A data acquisition device according to one aspect of the present invention includes: one or more data collectors that acquire RAW data, the RAW data being data in which one or more RAW records related to the operation of industrial equipment are arranged in one or more categories; a data parser that acquires parsing data in which one or more parsing records are arranged in one or more categories, extracts a parsing record of a specified category from the parsing data based on the data array of the parsing data, performs a specified parsing process on the extracted parsing record to generate one or more result records, and generates result data in which one or more result records are arranged in one or more categories; a database accessor that acquires registration data in which one or more registration records are arranged in one or more categories, converts the registration data into a specified database format based on the data array of the registration data, and registers it in the database; and an application manager that controls the data flow between the data collector, the data parser, and the database accessor.

[0010] The program according to another aspect of the present invention includes: one or more data collectors that collect RAW data, where the RAW data is data formed by arranging one or more RAW records related to the operation of industrial equipment according to one or more categories; a data parser that obtains parsing data formed by arranging one or more parsing records according to one or more categories, extracts parsing records of a specified category from the parsing data based on the data array of the parsing data, performs a specified parsing process on the extracted parsing records to generate one or more result records, and generates result data formed by arranging one or more result records according to one or more categories; a database accessor that obtains registration data formed by arranging one or more registration records according to one or more categories, converts the registration data into a specified database format based on the data array of the registration data, and registers it in the database; and an application manager that controls the data flow among the data collector, the data parser, and the database accessor.

[0011] The data collection method according to still another aspect of the present invention includes: collecting RAW data from industrial equipment, where the RAW data is data formed by arranging one or more RAW records related to the operation of industrial equipment according to one or more categories; obtaining the RAW data, extracting parsing records of a specified category from the RAW data based on the data array of the RAW data, performing a specified parsing process on the extracted parsing records to generate one or more result records, and generating result data formed by arranging one or more result records according to one or more categories; and obtaining the result data, converting the result data into a specified database format based on the data array of the result data, and registering it in the database.

[0012] Advantages of the Invention

[0013] According to the present disclosure, it is possible to provide a data collection device that can effectively balance the ease of database expansion and the ease of database utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is a schematic diagram illustrating the structure of a production system.

[0015] Figure 2 It is a schematic diagram illustrating the structure of a robot.

[0016] Figure 3 It is a block diagram illustrating the structure of a data collection device.

[0017] Figure 4 It is a table illustrating array structure data.

[0018] Figure 5 It is a chart for illustrating primary parsing.

[0019] Figure 6 It is a schematic diagram illustrating tag structure data.

[0020] Figure 7 It is a diagram for illustrating secondary parsing.

[0021] Figure 8 It is a block diagram illustrating the hardware structure of the control system.

[0022] Figure 9 It is a flowchart illustrating the program registration steps.

[0023] Figure 10 It is a flowchart illustrating the primary parsing steps.

[0024] Figure 11 It is a flowchart illustrating the registration steps of RAW records.

[0025] Figure 12 It is a flowchart illustrating the secondary parsing steps.

[0026] Figure 13 It is a flowchart of a modified example of the registration steps of auxiliary RAW records. Detailed Implementation Manner

[0027] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. In the description, the same reference numerals are assigned to the same elements or elements having the same functions, and repeated descriptions are omitted.

[0028] (Production System)

[0029] Figure 1 The production system 1 (robot system) shown is a system for manufacturing workpieces. Hereinafter, in the process of manufacturing workpieces, all objects to be the operation targets are collectively referred to as "workpieces". For example, "workpieces" include the final products in the production system 1, the parts of the final products, and units formed by combining multiple parts, etc.

[0030] The production system 1 includes one or more local devices 2 and a control system 3. For example, the production system 1 includes a plurality of local devices 2, and the workpieces are manufactured through the coordinated actions of the plurality of local devices 2. Coordinated action means that the plurality of local devices act in a manner of sharing a plurality of processes for obtaining at least one of the above-mentioned final products. The plurality of local devices may act in a manner of sharing a plurality of processes for obtaining one final product in units of processes, or may act in a manner of sharing a plurality of processes for obtaining a plurality of final products in units of final products.

[0031] The plurality of local devices 2 are respectively devices that directly perform operations on the workpiece 9 at the production site of the workpiece 9. The direct operation is, for example, an operation of imparting some kind of energy such as thermal energy, kinetic energy, and potential energy to the workpiece 9.

[0032] Each of the plurality of local devices 2 is, for example, an industrial device. The plurality of local devices 2 includes at least a robot (at least one local device 2 is a robot). In addition, the plurality of local devices 2 includes an industrial device that cooperates with the robot. As a specific example of the industrial device that cooperates with the robot, in addition to other robots, an NC machine tool etc. can be cited.

[0033] Figure 1 The illustrated plurality of local devices 2 includes a transfer device 2A, robots 2B, 2C, and a mobile robot 2D, but is not limited thereto. As long as at least one robot is included, the number and types of the local devices 2 can be appropriately changed.

[0034] The transfer device 2A transfers a workpiece 9 using, for example, an electric motor etc. as a power source. As a specific example of the transfer device 2A, a belt conveyor, a roller conveyor etc. can be cited. The robots 2B, 2C, and the mobile robot 2D perform operations on the workpiece 9 transferred by the transfer device 2A. As specific examples of operations performed on the workpiece 9, the following can be cited: assembling another workpiece 9 (for example, a sub-part) to the workpiece 9 (for example, a base part) transferred by the transfer device 2A; fastening (for example, bolt fastening), joining (for example, welding) the parts of the workpiece 9 transferred by the transfer device 2A to each other; loading the workpiece 9 into an NC machine tool provided around the transfer device 2A; unloading the workpiece 9 from the NC machine tool etc.

[0035] For example, the robots 2B, 2C are 6-axis vertical articulated robots and, as Figure 2 shown, have a base 11, a rotating part 12, a first arm 13, a second arm 14, a third arm 17, a front end part 18, and actuators 41, 42, 43, 44, 45, 46. The base 11 is provided around the transfer device 2A. The rotating part 12 is provided on the base 11 so as to rotate around a vertical axis 21.

[0036] The first arm 13 is connected to the rotating part 12 in such a way that it swings around an axis 22 that intersects (e.g., is orthogonal to) the axis 21. The intersection also includes cases where the axes are in a torsional relationship like a so-called overpass. The second arm 14 is connected to the front end part of the first arm 13 in such a way that it swings around an axis 23 that is substantially parallel to the axis 22. The second arm 14 includes an arm base part 15 and an arm end part 16. The arm base part 15 is connected to the front end part of the first arm 13 and extends along an axis 24 that intersects (e.g., is orthogonal to) the axis 23. The arm end part 16 is connected to the front end part of the arm base part 15 in such a way that it rotates around the axis 24. The third arm 17 is connected to the front end part of the arm end part 16 in such a way that it swings around an axis 25 that intersects (e.g., is orthogonal to) the axis 24. The front end part 18 is connected to the front end part of the third arm 17 in such a way that it rotates around an axis 26 that intersects (e.g., is orthogonal to) the axis 25. An operating tool such as a gripper, a suction nozzle, or a torch is mounted on the front end part 18.

[0037] In this way, the robots 2B and 2C have: a joint 31 that connects the base part 11 and the rotating part 12; a joint 32 that connects the rotating part 12 and the first arm 13; a joint 33 that connects the first arm 13 and the second arm 14; a joint 34 in the second arm 14 that connects the arm base part 15 and the arm end part 16; a joint 35 that connects the arm end part 16 and the third arm 17; and a joint 36 that connects the third arm 17 and the front end part 18.

[0038] The actuators 41, 42, 43, 44, 45, and 46 include, for example, an electric motor and a speed reducer, and drive the joints 31, 32, 33, 34, 35, and 36 respectively.

[0039] For example, the actuator 41 rotates the rotating part 12 around the axis 21, the actuator 42 swings the first arm 13 around the axis 22, the actuator 43 swings the second arm 14 around the axis 23, the actuator 44 rotates the arm end part 16 around the axis 24, the actuator 45 swings the third arm 17 around the axis 25, and the actuator 46 rotates the front end part 18 around the axis 26.

[0040] In addition, the specific structure of the robots 2B and 2C can be appropriately changed. For example, the robots 2B and 2C can be 7-axis redundant robots with an additional one-axis joint added to the above-mentioned 6-axis vertical multi-joint robot, or so-called scalar multi-joint robots.

[0041] Return to Figure 1, the mobile robot 2D is a robot capable of autonomous travel. The mobile robot 2D has a robot 10 and an automated guided vehicle 50 configured in the same way as robots 2B and 2C. The automated guided vehicle 50 autonomously travels in a manner of carrying the robot 10. As a specific example of the automated guided vehicle 50, an electric so-called AGV (Automated Guided Vehicle) can be cited.

[0042] The production system 1 may also include an environmental sensor 5. The environmental sensor 5 detects the state of the working environment of the plurality of local devices 2 (hereinafter referred to as "environmental state"). As a specific example of the environmental sensor 5, for example, a camera that photographs the working environment of the plurality of local devices 2 can be cited. The environmental sensor 5 may be a sensor that detects the presence or absence of a workpiece 9 at a specified position by laser or the like, or may be a sensor that detects the dimensions of the workpiece 9 or the like. The production system 1 may also include a plurality of environmental sensors 5.

[0043] The control system 3 controls the plurality of local devices 2. Hereinafter, the structure of the control system 3 will be exemplified in detail.

[0044] (Control System)

[0045] The control system 3 causes the plurality of local devices 2 to operate based on an operation program. The control system 3 includes a plurality of local controllers 100, a host controller 200, and a data acquisition device 300. The plurality of local controllers 100 respectively control the plurality of local devices 2. For example, the plurality of local controllers 100 respectively control the corresponding local devices 2 based on a predetermined operation program. For example, the plurality of local controllers 100 include: a local controller 100A that controls the transfer device 2A; a local controller 100B that controls the robot 2B; a local controller 100C that controls the robot 2C; and a local controller 100D that controls the mobile robot 2D.

[0046] The local controller 100A controls the transfer device 2A based on an operation program for transfer control prepared in advance to transfer the workpiece 9. The local controller 100B controls the actuators 41, 42, 43, 44, 45, 46 of the robot 2B based on an operation program for robot control prepared in advance to operate the robot 2B. The local controller 100C controls the actuators 41, 42, 43, 44, 45, 46 of the robot 2C based on an operation program for robot control prepared in advance to operate the robot 2C. The local controller 100D controls the actuators 41, 42, 43, 44, 45, 46 of the automated guided vehicle 50 and the robot 10 based on an operation program for robot control prepared in advance to operate the mobile robot 2D.

[0047] The host controller 200 respectively obtains information indicating the operation states of the corresponding local devices 2 (hereinafter referred to as "operation information") from a plurality of local controllers 100, obtains the detection results of the environmental state (hereinafter referred to as "environmental information") from the environmental sensor 5, and outputs execution instructions of the operation program to the plurality of local controllers 100 respectively based on the obtained operation information and environmental information.

[0048] The host controller 200 performs synchronous communication with a plurality of local controllers 100. Synchronous communication means that in a synchronous communication cycle synchronized with a synchronous frame of a certain period, communication with the plurality of local controllers 100 is repeated. The host controller 200 repeatedly executes the following operations in synchronization with the cycle of the synchronous communication: respectively obtains operation information from the plurality of local controllers 100, obtains environmental information from the environmental sensor 5, and outputs an execution instruction to any one of the plurality of local controllers 100 as needed based on the operation information and the environmental information.

[0049] The data acquisition device 300 acquires various data obtained / generated in the control of the plurality of local devices 2 by the plurality of local controllers 100 and the host controller 200, and then stores them in a database in a database format that can be parsed. The data stored by the data acquisition device 300 can be effectively utilized for improving productivity or preventive maintenance in the production system 1. The content of the data to be stored in the database may change according to changes in the structure of the production system 1 or changes in the operation sequence of the production system 1.

[0050] In contrast, the data acquisition device 300 includes: one or more data collectors that collect RAW data formed by arranging one or more RAW records related to the operation of industrial equipment in one or more categories; a data parser that obtains parsing data formed by arranging one or more parsing records in one or more categories, extracts a parsing record of a specified category from the parsing data based on the data array of the parsing data, performs a specified parsing process on the extracted parsing record to generate one or more result records, and generates result data formed by arranging the one or more result records in one or more categories; a database accessor that obtains registration data formed by arranging one or more registration records in one or more categories, converts the registration data into a specified database format based on the data array of the registration data, and registers it in the database; and an application manager that controls the data flow between the data collector, the data parser, and the database accessor.

[0051] According to such a structure, by adding at least one of the data collector and the data parser and changing the data flow through the application manager, it is possible to maintain the database format and flexibly expand the content registered in the database. Therefore, it is possible to effectively balance the ease of expanding the database and the ease of using the database.

[0052] As Figure 3 shown, for example, the data acquisition device 300 includes a collector storage unit 310, a parser storage unit 320, a database accessor 331, a database 332, an application storage unit 333, and an application manager 334.

[0053] The collector storage unit 310 stores one or more data collectors 311. For example, the collector storage unit 310 stores a plurality of data collectors 311. The plurality of data collectors 311 are respectively libraries that collect RAW data in which one or more RAW records related to the operations of one or more local devices 2 are arranged according to one or more categories. For example, the plurality of data collectors 311 are respectively dynamic link libraries that can be dynamically combined with programs in an execution format. A RAW record is an unprocessed record on which the information processing of the data acquisition device 300 has not been performed.

[0054] Hereinafter, data in which one or more records are arranged according to one or more categories like the above-mentioned RAW data is referred to as "array structure data". Based on the array structure data, the category of the record can be determined according to the configuration of the records in the data.

[0055] As a specific example of the array structure data, comma-separated text data (CSV data), tag-separated text data, etc. can be cited. In CSV data, a data set containing a plurality of records corresponding to a plurality of categories respectively is divided by line breaks and stored. In each data set, the plurality of records are arranged in a predetermined category order, and the records are separated by commas. The category of each record can be determined according to the position from the beginning in the corresponding data set.

[0056] The array structure data may also include attribute definition data that defines attributes according to one or more categories of one or more records. An attribute refers to a property common to records belonging to the same category. As a specific example of the common property, how a physical quantity value is represented in what unit, etc. can be cited.

[0057] Figure 4 is a table illustrating the array structure data. As Figure 4 shown, the array structure data 410 includes a header 411 and record data 412. The record data 412 is data in which a plurality of records are arranged in correspondence with time according to a plurality of categories.

[0058] For example, the record data 412 includes a plurality of data sets 413 in multiple rows. Each data set 413 includes a time 415 and a plurality of records 414 corresponding to a plurality of categories respectively. As a specific example of the time 415, the acquisition time of the plurality of records 414 can be cited. In each data set 413, the plurality of records 414 are arranged in category order from left to right.

[0059] The header 411 corresponds to the above-described attribute definition data and defines attributes for each of a plurality of series. When the array structure data shown in Figure 4 is the above RAW data, the header 411 defines the attributes of the RAW records for each of a plurality of categories. The attributes of the RAW records can be control instructions for causing the local device 2 to operate, or detection values of the operation results of the local device 2. Specific examples of the attributes of the RAW records are shown below.

[0060] Example 1-1: The amount of operation (e.g., operation angle) of an actuator (e.g., actuators 41, 42, 43, 44, 45, 46) is represented by an angle [rad].

[0061] Example 1-2: The operation speed of an actuator is represented by an angular velocity [rad / s].

[0062] Example 1-3: The driving force generated by an actuator is represented by a torque [N·m].

[0063] Example 1-4: Represents the drive current [A] of an actuator.

[0064] Example 1-5: The control instructions for the local device 2 are represented by target coordinates (X [m], Y [m], Z [m]) and a target posture (θx [rad], θy [rad], θz [rad]) in a specified coordinate system.

[0065] Example 1-6: Represents the control mode (position control mode / torque control mode) of an actuator.

[0066] The attributes of the RAW records can also be environmental information based on the detection results of the environmental sensor 5.

[0067] Return to Figure 3 , a plurality of data collectors 311 can correspond to a plurality of local devices 2 respectively, or at least one of the plurality of data collectors 311 can correspond to two or more local devices 2. The plurality of data collectors 311 can respectively collect RAW data from the upper controller 200, for example, or can collect RAW data from the local controller 100 of the corresponding local device 2. When the plurality of data collectors 311 respectively collect RAW data from the upper controller 200, RAW data assigned with a time based on a unified timer can be collected.

[0068] The plurality of data collectors 311 can respectively obtain RAW data generated by the upper controller 200 or the local controller 100, or can store the RAW records collected from the upper controller 200 or the local controller 100 to generate RAW data.

[0069] The parser storage unit 320 stores one or more primary data parsers 321. For example, the parser storage unit 320 stores a plurality of primary data parsers 321.

[0070] The plurality of primary data parsers 321 are respectively the following libraries: obtaining parsing data in which one or more parsing records are arranged according to one or more categories, extracting parsing records of a specified category from the parsing data based on the data array of the parsing data, performing a specified primary parsing process on the extracted parsing records to generate one or more result records, and generating result data in which one or more result records are arranged according to one or more categories. For example, the plurality of primary data parsers 321 are respectively dynamic link libraries that can be dynamically combined with a program in an execution format. The result record is a processed record in which the information processing of the data acquisition device 300 has been implemented.

[0071] The parsing data is also array structure data in which one or more records are arranged according to one or more categories. The plurality of primary data parsers 321 respectively obtain RAW data collected by a certain one of the plurality of data collectors 311 as parsing data, and extract RAW records of a specified category from the RAW data as parsing records. When the RAW data contains the above-mentioned attribute definition data, the plurality of primary data parsers 321 may also respectively extract RAW records of a specified category based on the attribute definition data of the RAW data.

[0072] When the RAW data arranges a plurality of RAW records in correspondence with time according to one or more categories, the primary data parser 321 may also extract, as one or more result records, RAW records whose values change with respect to the previous RAW record in the time sequence from the plurality of RAW records.

[0073] Figure 5 (a) is a graph showing the time change of RAW records represented in binary as in the control mode of the actuator described above, and includes a plurality of RAW records R10. The transition TR10 of the control mode is represented by the plurality of RAW records R10.

[0074] When the primary data parser 321 extracts, as one or more result records, RAW records whose values change with respect to the previous RAW record in the time sequence from the plurality of RAW records, as Figure 5As shown in (b) of , two RAW records R11 and R12 are extracted from multiple RAW records R10. Based on the RAW records R11 and R12 and attributes such as "change points indicating control mode changes", the transition TR10 of the control mode can be represented in the same way as the content represented by the multiple RAW records R10. In this way, by thinning out records other than the change points, the amount of data required to represent the transition TR10 can be significantly reduced.

[0075] The following shows other specific examples of the primary parsing process executed by the primary data parser 321.

[0076] Example 2-1: Extract RAW records representing the operating speed of the actuator (hereinafter referred to as "speed records") and RAW records representing the driving force of the actuator (hereinafter referred to as "force records") based on the attributes of the RAW data. Generate the degradation degree of the actuator's speed reducer (an example of the result record) based on the relationship between the speed record and the force record. And generate result data, which is obtained by attaching a header that defines the attribute of one category as "degradation degree of the speed reducer" to the record data in which one or more result records are arranged corresponding to one category.

[0077] Example 2-2: Extract RAW records representing the control mode of the actuator (hereinafter referred to as "mode records") based on the attributes of the RAW data. Extract one or more mode records whose values have changed relative to the previous mode record in the chronological order as result records. And generate result data, which is obtained by attaching a header that defines the attribute of one category as "change points indicating control mode changes" to the record data in which one or more result records are arranged corresponding to one category.

[0078] The primary data parser 321 can also generate result data in which one or more result records are arranged corresponding to time according to one or more categories. The time in the result data can be the generation time of the result record or the acquisition time of the RAW record used in the generation of the result record.

[0079] The database accessor 331 is a program library that: obtains registration data in which one or more registration records are arranged according to one or more categories, converts the registration data into a specified database format based on the data array of the registration data, and registers it in the database 332. For example, the database accessor 331 is a dynamic link library that can be dynamically combined with a program in an execution format. The registration data is also array structure data in which one or more records are arranged according to one or more categories.

[0080] The database format is, for example, a tag structure format in which structured tags are attached to individual records. As a specific example of the tag structure format, the JSON (Java Script Object Notation) format can be cited.

[0081] Figure 6 It is a schematic diagram illustrating tag structure data in which array structure data is set to a tag structure format. The tag structure data includes a plurality of structured records 420. The plurality of structured records 420 each include a record value 422 and a structured tag 421 attached to the record value 422.

[0082] The database accessor 331 can also register one or more registration records in the database 332 by attaching structured tags to each of them based on the data array of the registration data. When the registration data includes the above-described attribute definition data, the database accessor 331 can also attach structured tags indicating attributes to one or more registration records based on the category of each of the one or more registration records and the attribute definition data of the registration data.

[0083] The database accessor 331 can also attach structured tags to one or more registration records that further indicate the configuration within the category. For example, when the registration data arranges a plurality of registration records in correspondence with time according to one or more categories, the database accessor 331 can attach structured tags to the plurality of registration records that further indicate time (an example of the configuration within the category).

[0084] For example, the database accessor 331 obtains the result data generated by one of the plurality of primary data parsers 321 as registration data, converts the result data into a database format based on the data array of the result data, and registers it in the database 332.

[0085] As an example, the database accessor 331 attaches structured tags to one or more result records based on the category of each of the one or more result records of the result data and the attribute definition data of the result data. For example, when the result data arranges a plurality of result records in correspondence with time for the degradation degree of the reducer, the database accessor 331 attaches structured tags indicating "degradation degree of the reducer" as an attribute and time to each of the plurality of result records.

[0086] The database accessor 331 can also obtain RAW data collected by any one of the plurality of data collectors 311 as registration data, convert the RAW data into a database format based on the data array of the RAW data, and register it in the database 332.

[0087] As an example, the database accessor 331 can also define data based on the category of each of one or more RAW records of the RAW data and the attributes of the RAW data, and attach structured tags to the one or more RAW records respectively. For example, when multiple RAW records are arranged in correspondence with time for each of "actuator movement amount", "actuator movement speed", "driving force generated by the actuator", and "driving current of the actuator" in the RAW data, the database accessor 331 attaches a structured tag indicating "actuator movement amount" as an attribute and time to each of the multiple RAW records belonging to "actuator movement amount".

[0088] In addition, the database accessor 331 attaches a structured tag indicating "actuator movement speed" as an attribute and time to each of the multiple RAW records belonging to "actuator movement speed".

[0089] In addition, the database accessor 331 attaches a structured tag indicating "driving force generated by the actuator" as an attribute and time to each of the multiple RAW records belonging to "driving force generated by the actuator". In addition, the database accessor 331 attaches a structured tag indicating "driving current of the actuator" as an attribute and time to each of the multiple RAW records belonging to "driving current of the actuator".

[0090] The application manager 334 controls the data flow among the data collector 311, the primary data parser 321, and the application storage unit 333.

[0091] For example, the application manager 334 controls the transfer of the array structure data among the data collector 311, the primary data parser 321, and the application storage unit 333 based on the application program stored in the application storage unit 333. The transfer of the array structure data includes storing the array structure data in a specified storage area and passing a reference to the storage area. The application program is, for example, a program in an execution format.

[0092] As an example, the application program can also include the following processing.

[0093] Processing 1-1: Start any one of the multiple data collectors 311 at a specified time, and store the RAW data collected by the started data collector 311 in the first storage area.

[0094] Processing 1-2: As a storage area for parsing data, while passing a reference to the first storage area, start any one of the multiple primary data parsers 321, and store the result records generated by the started primary data parser 321 in the second storage area.

[0095] Process 1-3: As a storage area for registration data, while passing a reference to the second storage area, the database accessor 331 is started, and the result data is converted into a database format by the started database accessor 331 and registered in the database 332.

[0096] In this case, the application manager 334 causes the primary data parser 321 to acquire the RAW data collected by the data collector 311 as parsing data, and causes the database accessor 331 to acquire the result data generated by the primary data parser 321 as registration data.

[0097] The application may also include the following processes.

[0098] Process 2-1: As a storage area for registration data, while passing a reference to the first storage area, the database accessor 331 is started, and the RAW record is converted into a database format by the started database accessor 331 and registered in the database 332.

[0099] In this case, the application manager 334 causes the database accessor 331 to further acquire the RAW data collected by the data collector 311 as registration data.

[0100] Whether the application manager 334 causes the database accessor 331 to acquire RAW data depends on whether the application includes Process 2-1. Therefore, the application storage unit 333 is an example of a setting storage unit, and stores a need / non-need setting for determining whether RAW data needs to be registered. In addition, the application manager 334 switches whether to cause the database accessor 331 to acquire RAW data as registration data based on the need / non-need setting in the setting storage unit.

[0101] The application may also be configured to switch whether Process 2-1 needs to be executed based on one or more result records generated by the primary data parser 321. In this case, the application manager 334 switches whether to cause the database accessor 331 to acquire RAW data as registration data based on one or more result records generated by the primary data parser 321.

[0102] As an example, the application may also be configured to: when an abnormality is confirmed in one or more result records generated by the primary data parser 321, Process 2-1 needs to be executed, and when no abnormality is confirmed in one or more result records generated by the primary data parser 321, Process 2-1 does not need to be executed.

[0103] The data acquisition device 300 may further include a database accessor 335, and the parser storage unit 320 may further store one or more secondary data parsers 322. The parser storage unit 320 may also store a plurality of secondary data parsers 322.

[0104] The database accessor 335 (second database accessor) generates secondary data in which one or more secondary records are arranged in one or more categories based on the data read from the database 332. The secondary data is also array-structured data in which one or more records are arranged in one or more categories.

[0105] For example, the database accessor 335 reads data including a plurality of structured records from the database 332, generates attribute definition data of the array-structured data based on the structured tags included in each structured record, and arranges the record values included in each structured record in one or more categories based on the attribute definition data.

[0106] The plurality of secondary data parsers 322 (second data parsers) are each a library as follows: obtaining secondary parsing data in which one or more secondary parsing records are arranged in one or more categories, extracting secondary parsing records of a specified category from the secondary parsing data based on the data array of the secondary parsing data, performing a specified secondary parsing process (second parsing process) on the extracted secondary parsing records to generate one or more secondary result records, and generating secondary result data in which one or more secondary result records are arranged in one or more categories.

[0107] For example, the plurality of secondary data parsers 322 each obtain the secondary data generated by the database accessor 335 as secondary parsing data, extract secondary parsing records of a specified category from the secondary data based on the data array of the secondary data, perform a secondary parsing process on the extracted secondary parsing records to generate one or more secondary result records, and generate secondary result data in which one or more secondary result records are arranged in one or more categories.

[0108] Hereinafter, a specific example of the secondary parsing process executed by the database accessor 335 and the secondary data parser 322 is shown.

[0109] Example 3-1: The database accessor 335 reads data containing multiple structured tags from the database 332. The data is given structured tags representing the time within a specified period and the "deterioration degree of the speed reducer" described above. The database accessor 335 generates a secondary record, which includes record data arranged by associating the records of the multiple read structured tags with the time, and attribute definition data with the category attribute set to "deterioration degree of the speed reducer". The secondary data parser 322 extracts the secondary parsing record representing the deterioration degree of the speed reducer from the secondary record. The secondary data parser 322 derives the maintenance recommendation period when the deterioration degree of the speed reducer reaches a specified level as the secondary result record based on the secondary parsing record. The secondary data parser 322 generates secondary result data, which is obtained by assigning a header with the attribute of one category defined as "maintenance recommendation period" to the record data arranged by associating one or more result records with one category.

[0110] Figure 7 It is a diagram used to schematically represent the derivation of the maintenance recommendation period. Figure 7 The horizontal axis of represents the elapsed time, and the vertical axis represents the deterioration degree of the speed reducer. The secondary data parser 322 derives the deterioration trend line TL1 based on multiple result records R20, and derives the elapsed time t1 when the threshold TV1 for recommending maintenance intersects with the deterioration trend line TL1 as the maintenance recommendation period.

[0111] When the data acquisition device 300 further includes the database accessor 335 and the parser storage unit 320 further stores the secondary data parser 322, the above application program may further include the following processes.

[0112] Process 3-1: Start the database accessor 335 at a specified time, and store the secondary data generated by the started database accessor 335 in the third storage area.

[0113] Process 3-2: As the storage area for secondary parsing data, while passing the reference of the third storage area, start any one of the multiple secondary data parsers 322, and store the secondary result record generated by the started secondary data parser 322 in the fourth storage area.

[0114] Process 3-3: As the storage area for registration data, while passing the reference of the fourth storage area, start the database accessor 331, and convert the secondary result data into a database format through the started database accessor 331 and register it in the database 332.

[0115] In this case, the application manager 334 causes the secondary data parser 322 to acquire the secondary data generated by the database accessor 335 as the secondary parsing data, and causes the database accessor 331 to acquire the secondary result data generated by the secondary data parser 322 as the registration data. The database accessor 331 further acquires the secondary result data, converts the secondary result data into a database format based on the data array of the secondary result data, and further registers it in the database.

[0116] The parser storage unit 320 may also store the identification information of the secondary data parser 322 in correspondence with the record category required for the secondary parsing process. In this case, the application manager 334 may also specify the read object read from the database 332 based on the record category corresponding to the secondary data parser 322 in the parser storage unit 320, and cause the database accessor 335 to generate secondary data.

[0117] The data acquisition device 300 may also have a program registration unit 336. The program registration unit 336 acquires a new application program created by the user and stores it in the application storage unit 333.

[0118] The data collectors 311, the primary data parser 321, the secondary data parser 322, the database accessor 331, the database accessor 335, etc. used by the application program are held by the data acquisition device 300. Therefore, an application program can be created by a simple operation of defining the combination, array structure data flow, execution time, etc. of the data collector 311, the primary data parser 321, the secondary data parser 322, the database accessor 331, and the database accessor 335.

[0119] As described above, the application program includes a need setting for determining whether RAW data needs to be registered. Therefore, the program registration unit 336 is an example of a setting acquisition unit, which acquires the need setting for determining whether RAW data needs to be registered and stores it in the setting storage unit.

[0120] The program registration unit 336 may also be configured to further execute acquiring the data collector 311 made by the user and storing it in the collector storage unit 310. In this case, the data collector 311 can be added according to the addition of the local device 2, and the RAW data to be collected can be flexibly expanded.

[0121] The program registration unit 336 may also be configured to further execute acquiring the primary data parser 321 or the secondary data parser 322 made by the user and storing them in the parser storage unit 320. In this case, the content of the primary parsing process and the secondary parsing process can be flexibly changed.

[0122] Figure 8is a block diagram illustrating the hardware configuration of the control system 3. As Figure 8 shown, the local controller 100 has a circuit 190. The circuit 190 includes one or more processors 191, a memory 192, a storage 193, a communication port 194, and a driver circuit 195. The storage 193 has a computer-readable storage medium such as a non-volatile semiconductor memory, for example. The storage 193 stores a control program for causing the local controller 100 to control the local device 2 based on an operation program.

[0123] The memory 192 temporarily stores a program loaded from the storage medium of the storage 193 and the operation results of the processor 191. The processor 191 executes the above program in cooperation with the memory 192, thereby constituting each functional block of the local controller 100. The communication port 194 communicates with the host controller 200 via the first network line NW1 according to an instruction from the processor 191. The driver circuit 195 outputs drive power to the local device 2 according to an instruction from the processor 191.

[0124] The host controller 200 has a circuit 290. The circuit 290 includes one or more processors 291, a memory 292, a storage 293, communication ports 294, 295, and an input / output port 296. The storage 293 has a computer-readable storage medium such as a non-volatile semiconductor memory, for example. The storage 293 stores a program for causing the host controller 200 to acquire action information and environmental information, and output an execution instruction of an operation program based on the action information and the environmental information.

[0125] The memory 292 temporarily stores a program loaded from the storage medium of the storage 293 and the operation results of the processor 291. The processor 291 executes the above program in cooperation with the memory 292, thereby constituting each functional block of the host controller 200. The communication port 294 communicates with the local controller 100 via the first network line NW1 according to an instruction from the processor 291. The communication port 295 communicates with the data acquisition device 300 via the second network line NW2 according to an instruction from the processor 291. The input / output port 296 inputs and outputs information to and from the environmental sensor 5 according to an instruction from the processor 291.

[0126] The data acquisition device 300 has a circuit 390. The circuit 390 includes one or more processors 391, a memory 392, a storage 393, a communication port 394, a display device 395, and an input device 396. The storage 393 has a computer-readable storage medium such as a non-volatile semiconductor memory. The storage 393, as a storage unit for programs, further includes a storage unit for the collector storage unit 310, the parser storage unit 320, the application storage unit 333, the database accessors 331 and 335, a storage unit for the basic programs (such as an operating system) for configuring the data acquisition device 300 into an application manager 334 and a program registration unit 336. In addition, the storage 393 includes a storage unit for the database 332.

[0127] The memory 392 temporarily stores the programs loaded from the storage medium of the storage 393 and the operation results of the processor 391. The processor 391 executes the above programs in cooperation with the memory 392, thereby constituting each functional block of the data acquisition device 300. The communication port 394 communicates with the upper controller 200 via the second network line NW2 according to the instructions from the processor 391. The display device 395 and the input device 396 function as user interfaces of the data acquisition device 300. The display device 395 includes, for example, a liquid crystal monitor for displaying information to the user. The input device 396 is, for example, a keyboard for obtaining input information from the user. The display device 395 and the input device 396 may also be integrated as a so-called touch panel. The display device 395 and the input device 396 may be provided in an external device connected to the data acquisition device 300 or may be assembled in the data acquisition device 300.

[0128] In addition, the circuits 190, 290, and 390 are not necessarily limited to configuring each function through programs. For example, the circuits 190, 290, and 390 may also constitute at least a part of the functions through dedicated logic circuits or ASICs (Application Specific Integrated Circuits) integrating such dedicated logic circuits.

[0129] (Data acquisition step)

[0130] Next, as an example of the data collection method, the data collection steps performed by the data collection device 300 will be illustrated in detail. These steps include: collecting RAW data from industrial equipment, where the RAW data is data formed by arranging one or more RAW records according to one or more categories; obtaining the RAW data, extracting parsing records of a specified category from the RAW data based on the data array of the RAW data, performing specified parsing processing on the extracted parsing records to generate one or more result records, and generating result data formed by arranging one or more result records according to one or more categories; and obtaining the result data, converting the result data into a specified database format based on the data array of the result data, and registering it in the database.

[0131] As an example, the data collection steps include a program registration step, a primary parsing step, a RAW data registration step, and a secondary parsing step. Hereinafter, each step will be illustrated in detail.

[0132] (Program registration step)

[0133] As Figure 9 shown, the data collection device 300 first executes steps S01 and S02. In step S01, the program registration unit 336 causes the display device 395 to display a programming screen. The programming screen includes, for example, a combination of a data collector 311, a primary data parser 321, a secondary data parser 322, a database accessor 331, and a database accessor 335; an array structure data stream; an application definition area for defining the execution time, etc.; an application registration operation unit (such as a button) for requesting registration of an application program; a collector registration operation unit (such as a button) for requesting registration of the data collector 311; and a parser registration operation unit (such as a button) for requesting registration of a primary data parser or a secondary data parser. In step S02, the program registration unit 336 confirms whether an application program is requested to be registered through the application registration operation unit.

[0134] If it is determined in step S02 that an application program is requested to be registered, the data collection device 300 executes steps S03 and S04. In step S03, the program registration unit 336 generates an application program based on the input content in the application definition area. In step S04, the program registration unit 336 stores the application program in the application storage unit 333.

[0135] If it is determined in step S02 that no application program is requested to be registered, the data collection device executes step S05. In step S05, the program registration unit 336 confirms whether the data collector 311 is requested to be registered through the collector registration operation unit.

[0136] When it is determined in step S05 that registration of the data collector 311 is requested, the data collection device executes steps S06, S07, and S08. In step S06, the program registration unit 336 causes the display device 395 to display a collector selection screen for selecting one or more pre-generated new data collectors 311. In step S07, the program registration unit 336 waits for a selection input on the collector selection screen. In step S08, the program registration unit 336 causes the collector storage unit 310 to store the one or more new data collectors 311 selected on the collector selection screen.

[0137] When it is determined in step S05 that registration of the data collector 311 is not requested, the data collection device 300 executes step S11. In step S11, the program registration unit 336 confirms whether registration of the primary data parser 321 or the secondary data parser 322 is requested through the parser registration operation unit.

[0138] When it is determined in step S11 that registration of the primary data parser 321 or the secondary data parser 322 is requested, the data collection device 300 executes steps S12, S13, and S14. In step S12, the program registration unit 336 causes the display device 395 to display a parser selection screen for selecting one or more pre-generated new primary data parsers 321 or secondary data parsers 322. In step S13, the program registration unit 336 waits for a selection input on the parser selection screen.

[0139] In step S14, the program registration unit 336 causes the parser storage unit 320 to store the one or more new primary data parsers 321 or secondary data parsers 322 selected on the parser selection screen. When storing the secondary data parser 322 in the parser storage unit 320, the program registration unit 336 may also store the identification information of the secondary data parser 322 in correspondence with the record categories required for secondary parsing processing in the parser storage unit 320.

[0140] After steps S04, S08, and S14, the data collection device 300 executes step S15. When it is determined in step S11 that registration of the primary data parser 321 and the secondary data parser 322 is not requested, the data collection device 300 also executes step S15. In step S15, the program registration unit 336 confirms whether an input for completing programming has been made in the programming screen.

[0141] When it is determined in step S15 that an input for completing programming has not been made, the data collection device 300 returns the process to step S02. When it is determined in step S15 that an input for completing programming has been made, the program registration step is completed.

[0142] (Primary Parsing Step)

[0143] As can be seen from the above description, the data acquisition device 300 can perform a variety of primary parsing processes. Figure 10 It is a flowchart illustrating the steps of performing any one of the primary parsing processes. Hereinafter, one of the primary parsing processes that is the object of the flowchart of a variety of primary parsing processes is simply referred to as "primary parsing process". Figure 10 As

[0144] As Figure 10 shown, the data acquisition device 300 first executes steps S21, S22, S23, S24, S25, S26, S27, S28. In step S21, the application manager 334 waits for the execution time of the primary parsing process.

[0145] In step S22, the application manager 334 starts one or more of the plurality of data collectors 311 for collecting RAW data required for the primary parsing process. The one or more started data collectors 311 respectively collect RAW data. In step S23, the application manager 334 uses the RAW data collected in step S22 as parsing data and starts the primary data parser 321 for primary parsing. The started primary data parser 321 obtains the specified RAW data and extracts primary parsing records from the RAW data.

[0146] In step S24, the primary data parser 321 performs a primary parsing process on the parsing records extracted in step S23, generates one or more result records, and generates result data in which the one or more result records are arranged according to one or more categories. In step S25, the application manager 334 starts the database accessor 331 using the result data generated in step S24 as registration data. The database accessor 331 obtains the specified result data and reads out the first result record from the result data.

[0147] In step S26, the database accessor 331 attaches a structured tag to the result record based on the data array of the result data to generate a structured record. In step S27, the database accessor 331 stores the structured record in the database 332. In step S28, the database accessor 331 confirms whether the registration of all the result records in the result data is completed.

[0148] When it is determined in step S28 that there are unregistered result records remaining in the result data, the data acquisition device 300 executes step S29. In step S29, the database accessor 331 reads out the next result record from the result data. After that, the data acquisition device 300 returns the process to step S26. Thereafter, the reading, structuring, and registration of result records are repeated until the registration of all result records in the result data is completed.

[0149] When it is determined in step S28 that the registration of all result records in the result data is completed, the primary parsing step is completed. The data acquisition device 300 repeatedly executes the above process.

[0150] (RAW Data Registration Step)

[0151] As can be seen from the above description, the data acquisition device 300 can acquire various types of RAW data. Figure 11 It is a flowchart illustrating the steps of registering any one of the RAW data. Hereinafter, among the various RAW data, Figure 11 a RAW data that is the object in the flowchart is simply referred to as "RAW data".

[0152] As Figure 11 shown, the data acquisition device 300 first executes steps S31, S32, S33, S34, S35, and S36. In step S31, the application manager 334 waits for the acquisition time of the RAW data. In step S32, the application manager 334 starts the data collector 311 for acquiring the RAW data. The started data collector 311 acquires the RAW data respectively.

[0153] In step S33, the application manager 334 starts the database accessor 331 with the RAW data acquired in step S32 as the registration data. The database accessor 331 acquires the specified RAW data and reads out the first RAW record from the RAW data.

[0154] In step S34, the database accessor 331 attaches a structuring tag to the RAW record based on the data array of the RAW data to generate a structured record. In step S35, the database accessor 331 stores the structured record in the database 332. In step S36, the database accessor 331 confirms whether the registration of all RAW records in the RAW data is completed.

[0155] When it is determined in step S36 that there are unregistered RAW records remaining in the RAW data, the data acquisition device 300 executes step S37. In step S37, the database accessor 331 reads out the next RAW record from the RAW data. After that, the data acquisition device 300 returns the process to step S34. After that, the reading, structuring, and registration of RAW records are repeated until the registration of all RAW records in the RAW data is completed.

[0156] When it is determined in step S36 that the registration of all RAW records in the RAW data is completed, the registration step of the RAW data is completed. The data acquisition device 300 repeatedly executes the above process.

[0157] (Secondary parsing step)

[0158] As can be seen from the above description, the data acquisition device 300 can execute various secondary parsing processes. Figure 12 It is a flowchart illustrating the steps of executing any one of the secondary parsing processes. Hereinafter, one of the secondary parsing processes that takes the flowchart of Figure 12 as an object is simply referred to as "secondary parsing process".

[0159] As Figure 12 shown, the data acquisition device 300 first executes steps S41, S42, S43, S44, S45, S46, S47, S48. In step S41, the application manager 334 waits for the execution time of the secondary parsing process.

[0160] In step S42, the application manager 334 specifies the read object to be read from the database 332 based on the record category required for the secondary parsing process, and causes the database accessor 335 to generate secondary data. For example, the application manager 334 specifies the read object from the database 332 based on the record category corresponding to the secondary data parser 322 for secondary parsing in the parser storage unit 320.

[0161] In step S43, the application manager 334 uses the secondary data generated in step S42 as secondary parsing data and starts the secondary data parser 322 for secondary parsing. The started secondary data parser 322 acquires the specified secondary data and extracts secondary parsing records from the secondary data.

[0162] In step S44, the secondary data parser 322 performs secondary parsing on the secondary parsing records extracted in step S43, generates one or more secondary result records, and generates secondary result data in which the one or more secondary result records are arranged according to one or more categories.

[0163] In step S45, the application manager 334 starts the database accessor 331 using the secondary result data generated in step S44 as registration data. The database accessor 331 acquires the specified secondary result data and reads out the first secondary result record from the secondary result data.

[0164] In step S46, the database accessor 331 generates a structured record by attaching a structured label to the secondary result record based on the data array of the secondary result data. In step S47, the database accessor 331 stores the structured record in the database 332. In step S48, the database accessor 331 confirms whether the registration of all secondary result records in the secondary result data is completed.

[0165] If it is determined in step S48 that there are unregistered secondary result records remaining in the secondary result data, the data acquisition device 300 executes step S49. In step S49, the database accessor 331 reads out the next secondary result record from the secondary result data. Thereafter, the data acquisition device 300 returns the process to step S46. Thereafter, the reading, structuring, and registration of secondary result records are repeated until the registration of all secondary result records in the secondary result data is completed.

[0166] If it is determined in step S48 that the registration of all secondary result records in the secondary result data is completed, the secondary parsing step is completed. The data acquisition device 300 repeatedly executes the above process.

[0167] (Variant example of the RAW data registration step)

[0168] As described above, the application manager 334 may also switch whether to cause the database accessor 331 to acquire RAW data as registration data based on one or more result records generated by the primary data parser 321. An example of the RAW data registration step in this case is shown.

[0169] As Figure 13 shown, the data acquisition device 300 first executes steps S51 to S59, which are the same primary parsing steps as steps S21 to S29. Thereafter, the data acquisition device 300 executes step S61. In step S61, the application manager 334 confirms whether RAW data needs to be registered based on one or more result records generated by the primary data parser 321 in the primary parsing process.

[0170] When it is determined in step S61 that registration of RAW data is required, the data acquisition device 300 executes steps S63 to S67, which are the same RAW data registration steps as steps S33 to S37. When it is determined in step S61 that RAW data registration is not required, the data acquisition device 300 omits the registration of RAW data. Thus, the RAW data registration step is completed.

[0171] (Effect of this Embodiment)

[0172] As described above, the data acquisition device 300 includes: one or more data collectors 311 that collect RAW data, where the RAW data is data formed by arranging one or more RAW records related to the operation of industrial equipment in one or more categories; a primary data parser 321 that obtains parsing data formed by arranging one or more parsing records in one or more categories, extracts parsing records of a specified category from the parsing data based on the data array of the parsing data, performs specified parsing processing on the extracted parsing records to generate one or more result records, and generates result data formed by arranging one or more result records in one or more categories; a database accessor 331 that obtains registration data formed by arranging one or more registration records in one or more categories, converts the registration data into a specified database format based on the data array of the registration data, and registers it in the database 332; and an application manager 334 that controls the data flow between the data collector 311, the primary data parser 321, and the database accessor 331.

[0173] According to this data acquisition device 300, by adding at least one of the data collector 311 and the primary data parser 321 and changing the data flow through the application manager 334, the database format can be maintained, and the content registered in the database 332 can be flexibly expanded. Therefore, the ease of expanding the database 332 and the ease of using the database 332 can be effectively balanced.

[0174] The database format is a tag structure format in which structured tags are attached to each record. The database accessor 331 can also attach structured tags to one or more registration records respectively based on the data array of the registration data and register them in the database 332. In this case, the ease of using the database 332 can be further improved through data registration in the tag structure format.

[0175] The registration data includes attribute definition data that defines attributes according to one or more categories of one or more registration records. The database accessor 331 can also attach structured tags indicating attributes to each of the one or more registration records based on each category of the one or more registration records and the attribute definition data of the registration data. In this case, it is possible to easily attach more appropriate structured tags to each record.

[0176] The database accessor 331 can also attach structured tags indicating the configuration within the category to each of the one or more registration records. In this case, it is possible to easily attach more appropriate structured tags to each record.

[0177] The application manager 334 can cause the primary data parser 321 to acquire the AW data collected by the data collector 311 as parsing data, and cause the database accessor 331 to acquire the result data generated by the primary data parser 321 as registration data. In this case, compared with the case of reading the data temporarily registered in the database 332 for parsing processing, the processing load on the database 332 can be reduced.

[0178] The RAW data can also include attribute definition data that defines attributes according to one or more categories of one or more RAW records. The primary data parser 321 extracts parsing records of a specified category based on the attribute definition data of the RAW data. In this case, it is possible to easily extract parsing records.

[0179] The application manager 334 can also cause the database accessor 331 to acquire the RAW data collected by the data collector 311 as registration data. In this case, in addition to registering the result data in the database 332, the RAW data is also registered, thereby enabling the construction of a database 332 that can flexibly adapt to various future demands.

[0180] The data collection device 300 can also have a program registration unit 336 (setting acquisition unit) that acquires a need / non - need setting for determining whether RAW data needs to be registered and stores it in the application storage unit 333 (setting storage unit). The application manager 334 can switch whether to cause the database accessor 331 to acquire the RAW data collected by the data collector 311 as registration data based on the need / non - need setting in the setting storage unit. In this case, by omitting the database registration of RAW data that the user does not need, the processing load on the database 332 can be further reduced.

[0181] The application manager 334 can also switch whether to cause the database accessor 331 to acquire the RAW data collected by the data collector 311 as registration data based on one or more result records generated by the primary data parser 321. In this case, it is possible to support more appropriate selection and rejection of the RAW data.

[0182] Alternatively, the data collection device 300 may further include: a database accessor 335 that generates secondary data in which one or more secondary records are arranged in one or more categories based on the data read from the database 332; and a secondary data parser 322 that acquires secondary parsing data in which one or more secondary parsing records are arranged in one or more categories, extracts secondary parsing records of a specified category from the secondary parsing data based on the data array of the secondary parsing data, performs a specified second parsing process on the extracted secondary parsing records to generate one or more secondary result records, and generates secondary result data in which one or more secondary result records are arranged in one or more categories. The application manager 334 causes the secondary data parser 322 to acquire the secondary data generated by the database accessor 335 as secondary parsing data, and causes the database accessor 331 to acquire the secondary result data generated by the secondary data parser 322 as registration data. In this case, it is possible to perform multi-stage data parsing corresponding to the storage state of data in the database 332, and it is possible to promote further effective use of the database 332.

[0183] The data collection device 300 further includes a parser storage unit 320 that stores the identification information of the secondary data parser 322 in correspondence with the record categories required for the second parsing process. The application manager 334 can also specify the read object read from the database 332 based on the record categories corresponding to the secondary data parser 322 in the parser storage unit 320, and cause the database accessor 335 to generate secondary data. In this case, by screening the records read from the database 332 according to the content of the secondary parsing, it is possible to further reduce the processing load on the database 332.

[0184] The data collector 311 can also collect RAW data in which a plurality of RAW records are arranged in correspondence with time in one or more categories. The primary data parser 321 extracts, as one or more result records, the RAW records whose values have changed with respect to the previous RAW record in the time sequence from the plurality of RAW records. In this case, it is possible to suppress a decrease in the amount of information contained in the plurality of RAW records, and it is easy to reduce the processing load on the database 332.

[0185] As described above, the embodiments have been described, but the present invention is not necessarily limited to the above-described embodiments, and various modifications can be made without departing from the gist thereof.

[0186] Symbol Explanation:

[0187] 2… Local device (industrial device)

[0188] 300… Data acquisition device

[0189] 311… Data collector

[0190] 320… Parser storage unit

[0191] 321… Primary data parser (data parser)

[0192] 322… Secondary data parser (second data parser)

[0193] 331… Database accessor

[0194] 332… Database

[0195] 333… Application storage unit (setting storage unit)

[0196] 334… Application manager

[0197] 335… Database accessor (second database accessor)

[0198] 336… Program registration unit (setting acquisition unit)

Claims

1. A data acquisition device, comprising: One or more data collectors that collect RAW data with an array structure from industrial equipment, where each record is identified by its position in the data array; A first data parser that obtains parsing data with the array structure, extracts parsing records from the parsing data based on the data array of the parsing data, and performs a specified first parsing process on the extracted parsing records to generate result data with the array structure; A first database accessor that obtains registration data with the array structure, converts the registration data from the array structure into a specified database format based on the data array of the registration data, and registers it in the database; and An application manager that controls the data flow among the data collector, the first data parser, and the first database accessor.

2. The data acquisition device according to claim 1, wherein, The database format is a tag structure, where each record is identified by a structured tag respectively attached to the record, The first database accessor attaches a structured tag to each of one or more registration records based on the data array of the registration data and registers the converted registration records in the database.

3. The data acquisition device according to claim 2, wherein, In the array structure, one or more records are arranged in one or more categories, The array structure contains attribute definition data that defines attributes according to the one or more categories, The first database accessor attaches a structured tag representing an attribute to each of the one or more registration records based on the category of each of the one or more registration records and the attribute definition data of the registration data.

4. The data acquisition device according to claim 3, wherein, The first database accessor attaches a structured tag to each of the one or more registration records that further represents the configuration within the category.

5. The data acquisition device according to any one of claims 1 to 4, wherein, The application manager causes the first data parser to obtain the RAW data collected by the data collector as the parsing data, and causes the first database accessor to obtain the result data generated by the first data parser as the registration data.

6. The data acquisition device according to claim 5, wherein, In the array structure, one or more records are arranged in one or more categories, The array structure contains attribute definition data that defines attributes according to the one or more categories, The first data parser extracts parsing records of the specified category based on the attribute definition data of the RAW data.

7. The data acquisition device according to claim 5, wherein, The application manager also causes the first database accessor to obtain the RAW data collected by the data collector as the registration data.

8. The data acquisition device according to claim 7, further comprising: A setting acquisition unit that acquires a need setting for determining whether to register the RAW data and stores it in a setting storage unit. The application manager switches whether to cause the first database accessor to acquire the RAW data collected by the data collector as the registration data based on the need setting in the setting storage unit.

9. The data collection device according to claim 7, wherein, The application manager switches whether to cause the first database accessor to acquire the RAW data collected by the data collector as the registration data based on the one or more result records generated by the first data parser.

10. The data collection device according to claim 5, further comprising: A second database accessor that extracts secondary records from the database and generates secondary data having an array structure by arranging the secondary records based on the database format; and A second data parser that acquires secondary parsing data having the array structure, extracts secondary parsing records from the secondary parsing data based on the data array of the secondary parsing data, and performs a prescribed second parsing process on the extracted secondary parsing records to generate secondary result data having the array structure. The application manager causes the second data parser to acquire the secondary data generated by the second database accessor as the secondary parsing data, and causes the first database accessor to acquire the secondary result data generated by the second data parser as the registration data.

11. The data collection device according to claim 10, further comprising: A parser storage unit that stores the identification information of the second data parser in correspondence with the record categories required for the second parsing process. The application manager designates a read-out object read from the database based on the record categories corresponding to the identification information of the second data parser in the parser storage unit, and causes the second database accessor to generate the secondary data.

12. The data collection device according to claim 5, wherein, The data collector collects the RAW data in which a plurality of RAW records are arranged in correspondence with time according to one or more categories. The first data parser extracts, as the one or more result records, the RAW records whose values have changed with respect to the previous RAW record in the time sequence from the plurality of RAW records.

13. A data collection device, comprising: One or more data collectors that collect RAW data having an array structure from industrial equipment, where each record is identified by a position in the data array; A first data parser that acquires the RAW data, extracts parsing records from the RAW data based on the data array of the RAW data, and performs a prescribed first parsing process on the extracted parsing records to generate result data having the array structure; and The first database accessor obtains the result data, converts the result data from the array structure into a specified database format based on the data array of the result data, and registers the converted result data into the database.

14. The data acquisition device according to claim 13, wherein, the database format is a tag structure, where each record is identified by a structured tag respectively attached to the record, the first database accessor attaches a structured tag to each record of the result data based on the data array of the result data and registers the converted result data into the database.

15. The data acquisition device according to claim 13, wherein, the first database accessor also obtains the RAW data, converts the RAW data from the array structure into the database format based on the data array of the RAW data, and further registers the converted RAW data into the database.

16. The data acquisition device according to any one of claims 13 to 15, further comprising: a second database accessor that extracts secondary records from the database and generates secondary data with an array structure by arranging the secondary records based on the database format; and a second data parser that obtains the secondary data, extracts secondary parsing records from the secondary data based on the data array of the secondary data, performs a specified second parsing process on the extracted secondary parsing records, and generates secondary result data with the array structure, the first database accessor also obtains the secondary result data, converts the secondary result data from the array structure into the database format based on the data array of the secondary result data, and further registers the converted secondary result data into the database.

17. A data acquisition method, comprising: acquiring RAW data with an array structure from industrial equipment, where each record is identified by a position in the data array; extracting parsing records from the RAW data based on the data array of the RAW data, performing a specified first parsing process on the extracted parsing records, and generating result data with the array structure; and converting the result data from the array structure into a specified database format based on the data array of the result data, and registering the converted result data into the database.

Images