Data conversion device, system, and method

Abstract

To enable data to be converted quickly and flexibly.SOLUTION: A data conversion device includes: a storage unit for storing monitoring target management information in which a monitoring target and a controller type representing the type of a controller controlling the monitoring target are associated with each other, and data conversion rule information in which a controller-type-specific data set, which defines a conversion rule indicating a data conversion method, is registered for each controller type; and a computation unit capable of executing a software program that uses the stored information to implement data conversion. The computation unit deploys the data conversion rule information in a cache memory, identifies, from data received from an edge device, a monitoring target corresponding to the data, identifies a controller type corresponding to the identified monitoring target by referring to the monitoring target management information, reads the conversion rule corresponding to the identified controller type from the cache memory, and uses the conversion rule to carry out the data conversion.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to processing IoT data collected from monitored objects such as industrial equipment. [Background technology]

[0002] In recent years, it has become increasingly important to utilize IoT (Internet of Things) data generated by industrial equipment (hereinafter referred to as "assets") equipped with a variety of sensors in combination with cutting-edge IT (Information Technology) such as machine learning and AI (Artificial Intelligence).

[0003] When monitoring failures in assets using IoT data, speed is required for detecting failures and for predictive diagnosis, which monitors for signs of failure.

[0004] Usually, IoT data is not used as raw data, but is converted according to predetermined conversion rules before use (see Patent Document 1). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2020-126533 A Summary of the Invention [Problem to be solved by the invention]

[0006] To achieve rapid utilization of IoT data, rapid conversion of IoT data is also desirable.

[0007] In addition, the conversion rules for IoT data are created by data scientists and are often updated according to changing trends. Usually, updating the conversion rules requires system modification and deployment. However, in cases where the conversion rules need to be changed frequently, it is desirable to be able to flexibly change the conversion rules without modifying or deploying them.

[0008] One objective of the present disclosure is to provide techniques that enable rapid and flexible transformation of data. [Means for solving the problem]

[0009] A data conversion device according to one aspect of the present disclosure is a data conversion device that converts data acquired by an edge device associated with a monitoring target, and has a memory unit that stores monitoring target management information that associates the monitoring target with a controller type that indicates a type of controller that controls the monitoring target, and data conversion rule information in which a data set for each controller type that defines a conversion rule that indicates a data conversion method for each controller type is registered, and a calculation unit that has a cache memory and is capable of executing a software program that realizes data conversion using the information stored in the storage unit, wherein the calculation unit expands the data conversion rule information in the cache memory, identifies a monitoring target corresponding to the data from data received from the edge device, identifies a controller type corresponding to the identified monitoring target by referring to the monitoring target management information, reads a conversion rule corresponding to the identified controller type from the cache memory, and converts the data using the conversion rule. Effect of the Invention

[0010] According to one aspect of the present disclosure, conversion rules can be flexibly updated in units of data sets, and data can be converted quickly. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram of a data processing system. [Diagram 2] FIG. 2 is a block diagram showing a functional configuration of the data conversion device. [Diagram 3] FIG. 2 is a block diagram showing a hardware configuration of the data conversion device. [Figure 4] 13 is a flowchart of a process executed by a data conversion unit. [Diagram 5] 11 is a diagram showing an example of raw data input to a data conversion unit; FIG. [Figure 6] 13 is a flowchart showing detailed processing of step S105. [Figure 7] 1 is a table illustrating data conversion. [Figure 8] FIG. 13 is a conceptual diagram illustrating how the data conversion rule is updated. [Figure 9] FIG. 13 is a diagram showing an example of a conversion rule creation screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0013] FIG. 1 is a block diagram of a data processing system.

[0014] The data processing system includes an edge device 13 and a data conversion device 15 .

[0015] The asset 11 is an industrial device or the like to be monitored. There may be multiple assets 11. The asset 11 has a controller 12. The controller 12 is a device for monitoring and controlling the asset 11. The controller 12 acquires data from various sensors (not shown) of the asset 11, etc. The data transmitted from the controller 12 is raw data collected by the asset 11 and not processed.

[0016] The edge device 13 is installed in the asset 11, acquires data from the controller 12, and transmits the data as raw data to the data conversion device 15. The raw data from the edge device 13 is received by the data conversion device 15 via the gateway 14. The gateway 14 is provided on the cloud, and transfers the data from the edge device 13 to the data conversion device 15.

[0017] The data conversion device 15 has a management database 16, a data conversion unit 17, and a data lake 18. The management database 16 is a database (also called "DB") that stores various management data. The data conversion unit 17 is a data conversion engine that converts raw data received from the edge device 13 based on the various management data in the management database 16. The converted data converted by the data conversion unit 17 is transmitted to an external device 19 and a message queue 20.

[0018] Although there is no particular limitation on how the data conversion device 15 converts the data, in this embodiment, the data is converted into contextualized and meaningful data. The raw data received by the data conversion device 15 and the converted data converted by the data conversion device 15 are also stored in the data lake 18.

[0019] The external device 19 receives the converted data from the data conversion device 15 and uses it for processing various applications. Hereinafter, the application may be abbreviated to an app. Although there is no particular limitation on the way in which the converted data is used by the app, the app of the external device 19 may be, for example, a threshold monitoring app, a DTC monitoring app, a location information display app, an advanced analysis app, a machine learning and AI app, etc.

[0020] The threshold monitoring application compares the value of the converted data with a predetermined threshold and detects a change in state, such as a failure or a sign of a failure of the asset 11. The DTC monitoring application detects an abnormality in the asset 11 based on an error message converted from a DTC (Diagnostic Trouble Code). The location information display application uses location information converted from GPS data. The advanced analysis application is an application that performs advanced analysis on the converted data, for example, by accumulating the converted data in a time series and analyzing the converted data in a time series. The machine learning and AI application is an application that learns the learning data to generate a predictive model and makes predictions using the predictive model, and the converted data is used as learning data or input data for the predictive model. Various applications can appropriately acquire and use the management data registered in the management database 16 and the data accumulated in the data lake 18.

[0021] Furthermore, the converted data may not only be used by an app, but also be used directly by a person. For example, the converted data may be a message including a phrase or sentence that can be read and understood by a person, and may be registered in the message queue 20. The converted data registered in the message queue 20 may be sequentially retrieved by the external device 21 and displayed on the display device 22. The user can read the message displayed on the display device 22 and perform some appropriate action.

[0022] Fig. 2 is a block diagram showing the functional configuration of data conversion device 15. Fig. 3 is a block diagram showing the hardware configuration of data conversion device 15.

[0023] 2, the data conversion device 15 has, in addition to the management database 16, the data conversion unit 17, and the data lake 18, an asset management GUI unit 31, a device management GUI unit 32, an event management GUI unit 33, and a conversion rule creation GUI unit 34. Referring to Fig. 3, the data conversion device 15 has, as hardware, a calculation unit 51, a storage unit 52, and a communication unit 53.

[0024] The storage unit 52 is a storage device that stores data in a writable and readable manner, and the management database 16 and the data lake 18 shown in FIG. 2 are constructed on the storage unit 52. The storage unit 52 also stores software programs that realize various processes of the data conversion device 15. The calculation unit 51 is a processor that executes the processes of the software programs stored in the storage unit 52, and executes desired processes using various data on the storage unit 52. The asset management GUI unit 31, the device management GUI unit 32, the event management GUI unit 33, the conversion rule creation GUI unit 34, and the data conversion unit 17 shown in FIG. 2 are realized by the calculation unit 51 executing the software programs. The calculation unit 51 includes a cache memory (not shown) and uses it for data conversion processing. The communication unit 53 is a communication device that receives data used for processing by the calculation unit 51 via wired or wireless communication and transmits data processed by the calculation unit 51 via wired or wireless communication.

[0025] The management database 16 includes an asset management DB 35, a device management DB 36, an event management DB 37, and a data conversion rule DB 38. The data conversion unit 17 includes a first process unit 39 and a second process unit 40.

[0026] The asset management GUI unit 31 provides a GUI (Graphical user interface) for the user to register asset management data for managing each asset 11 to be monitored. The asset management data registered by the user is stored in the asset management DB 35. The asset management data includes information for associating an asset serial number for identifying the asset 11 with a control type indicating the type of the controller 12 of the asset 11. The device management GUI unit 32 provides a GUI for the user to register device management data for managing the edge device 13 provided in each asset 11. The device management data registered by the user is stored in the device management DB 36. The event management GUI unit 33 provides a GUI for the user to register event management data related to an event. The event management data is, for example, a threshold value for determining the occurrence of an event from data. The event management data registered by the user is stored in the event management DB 37. The conversion rule creation GUI unit 34 provides a GUI for the user to register a data conversion rule. The data conversion rule registered by the user is stored in the data conversion rule DB 38. The data conversion rule includes information that associates the controller type of the controller 12 with the data conversion rule used to convert raw data acquired from the asset 11 that corresponds to that controller type.

[0027] FIG. 4 is a flowchart of the process executed by the data conversion unit 17.

[0028] Before starting the process of Fig. 4, the data conversion unit 17 expands the data conversion rules stored in the data conversion rule DB 38 in a cache memory as a data conversion rule cache 61. The format of the data conversion rules is, for example, JSON (JavaScript Object Notation (JavaScript is a registered trademark)) format. After that, unclassified raw data is input to the data conversion unit 17. The raw data is, for example, an MQTT (Message Queue Telemetry Transport) message in JSON format.

[0029] This raw data is transformed in real time by the process described below.

[0030] In step S101, in the data conversion unit 17, the first process unit 39 stores the input raw data in the data lake 18. FIG. 5 is a diagram showing an example of raw data input to the data conversion unit 17. The raw data 101 includes a data body 102 and an asset serial number 105. The data body 102 includes a key 103 and a value 104. The asset serial number 105 is a serial number that identifies the asset 11 from which the raw data 101 was obtained. The key 103 included in the data body 102 indicates a data item, and the value 104 indicates the value of the data item.

[0031] In step S102, the second process unit 40 checks the asset serial number 105 in the raw data 101 received from the edge device 13. In step S103, the second process unit 40 refers to the asset management data and checks the controller type of the controller 12 corresponding to the asset serial number.

[0032] In step S104, the second process unit 40 obtains from the data conversion rule cache 61 a data conversion rule used to convert data obtained from the asset 11 in which the controller 12 of the controller type is installed.

[0033] In step S105, the second process unit 40 converts the raw data into a context by using the data conversion rule. The converted data is in JSON format, for example.

[0034] In this way, data conversion is performed using the data conversion rules in the data conversion rule cache 61, making it possible to perform conversion quickly in real time.

[0035] FIG. 6 is a flowchart showing detailed processing of step S105.

[0036] In step S201, the second process unit 40 converts the key 103 included in the data body 102 of the raw data 101 in accordance with the data conversion rule. Next, in step S202, the second process unit 40 converts the value 104 included in the data body 102 in accordance with the data conversion rule. The converted data in which the key 103 and / or the value 104 is converted is output as rich context data.

[0037] FIG. 7 is a table illustrating data conversion.

[0038] Various transformations are shown in table 201. In the example of Figure 7, the types of transformations include: (1) adjusting the resolution, (2) mapping a key, (3) adding a unit of measurement, (4) converting a unit of measurement, and (5) decoding a DTC.

[0039] (1) Adjust resolution is a data transformation that adjusts the resolution of value 104. (2) Mapping a key is a data transformation that converts key 103 into a human-readable phrase. (3) Add unit of measure is a data transformation that adds a unit to value 104. (4) Convert unit of measure is a data transformation that converts the unit of value 104. (5) Decode DTC is a data transformation that decodes a DTC and converts key 103 and value 104 into a human-readable message.

[0040] 8 is a conceptual diagram showing how the data conversion rules are updated. The data conversion rules are updated online without modifying or deploying the data conversion device 15.

[0041] As described above, asset management data registered by the user from the asset management GUI unit 31 is stored in the asset management DB 35, and data conversion rules registered by the user from the conversion rule creation GUI unit 34 are stored in the data conversion rule DB 38. The data conversion unit 17 expands the data conversion rules stored in the data conversion rule DB 38 as a data conversion rule cache in a cache memory. Then, the data conversion unit 17 converts the input raw data using the asset management data stored in the asset management DB 35 and the data conversion rule cache 61, and outputs the converted data.

[0042] In this state, when the user changes the data conversion rules in the data conversion rule DB 38 from the conversion rule creation GUI unit 34 , the data conversion rule DB 38 reflects the contents of the changed part in the data conversion rule cache 61 .

[0043] In this way, changes to the data conversion rules in the data conversion rule DB 38 and their reflection in the data conversion rule cache 61 are executed without modifying or deploying the data conversion device 15 .

[0044] In this embodiment, the data conversion rules registered in the data conversion rule DB 38 are data sets that combine multiple policy modules that can be created individually and that define data conversion methods. The conversion rule creation GUI unit 34 displays multiple policy modules on a screen so that the user can select them, combines the policy modules selected by the user from the screen to create a data set, and registers the data set in the data conversion rule DB 38.

[0045] 9 is a diagram showing an example of a conversion rule creation screen. The conversion rule creation screen 62 includes a first screen 63 that displays a plurality of policy modules that are components of the data conversion rule, and a second screen 64 that creates a data conversion rule by combining the components. A data conversion rule is created by selecting a policy module displayed on the first screen 63 and arranging it on the second screen 64. For example, a user can create a data conversion rule on the second screen 64 by dragging and dropping a policy module displayed on the first screen 63 onto the second screen 64 with a cursor 65.

[0046] In addition, in the above-described embodiment, the policy module may prescribe the operation of data conversion. For example, functions and programs may be included in the policy of data conversion. In that case, an operation using multiple items of data may be prescribe. A data scientist can check trends in accumulated data and set flexible conversion rules so that new value can be created from data to be received in the future. For example, when a data scientist creates a data conversion operation in a familiar programming language (such as Python), the program can be immediately used as one policy module without modifying or deploying the data conversion device 15. As a result, a new data conversion rule can be immediately applied to the system at any time.

[0047] In addition, in this embodiment, the data conversion device 15 identifies the asset 11 from which the data received from the edge device 13 was obtained, and identifies the controller type corresponding to that asset 11, but other configurations are also possible.

[0048] The edge device 13 may store in advance information indicating a controller type that indicates the type of the controller 12 that controls the asset 11 from which the data received by the edge device 13 is obtained, and transmit the information to the data conversion device 15. The data conversion device 15 may receive the controller type information and data from the edge device 13, read a conversion rule corresponding to the received controller type from a cache memory, and convert the data using the conversion rule. Since the data conversion device 15 uses the controller type received from the edge device 13, it becomes unnecessary to refer to the management database 16 to specify the controller type, and thus it becomes possible to convert data at a higher speed.

[0049] In addition, in the present embodiment, the data conversion device 15 sends the converted data to the external devices 19 and 21, and the external devices 19 and 21 use the converted data. However, the present invention is not limited to this.

[0050] As another configuration, data conversion device 15 itself may be the one that uses the converted data. For example, data conversion device 15 may be provided with various applications provided in external device 19 in this embodiment and execute the processing of those applications. Furthermore, data conversion device 15 itself may be provided with a display device and display the converted data.

[0051] Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and these embodiments may be used in combination or some of the configurations may be changed within the scope of the technical concept of the present invention.

[0052] Furthermore, the present embodiment and / or its modified examples include the following items. However, the items included in the present embodiment and / or its modified examples are not limited to only those items described below.

[0053] (Item 1) A data conversion device that converts data acquired by an edge device associated with a monitoring target, a storage unit for storing monitoring target management information that associates the monitoring targets with controller types that indicate the types of controllers that control the monitoring targets, and data conversion rule information in which data sets are registered for each controller type that prescribes conversion rules that indicate a data conversion method for each controller type; A calculation unit including a cache memory and capable of executing a software program for implementing data conversion using information stored in the storage unit, the calculation unit expands the data conversion rule information in the cache memory, identifies a monitoring target corresponding to the data from the data received from the edge device, identifies a controller type corresponding to the identified monitoring target by referring to the monitoring target management information, reads a conversion rule corresponding to the identified controller type from the cache memory, and converts the data using the conversion rule. Data conversion device.

[0054] This allows conversion rules that indicate how to convert data to be registered as a data set for each controller type, making it possible to flexibly update the conversion rules for each data set. In addition, the conversion rules are deployed in a cache memory, and the conversion rules in the cache memory are used to convert data, making it possible to convert data quickly.

[0055] (Item 2) The data includes a key indicating an item and a value of the item; The data transformation rule specifies that at least one of the key and the value is to be transformed. 2. A data conversion device according to item 1.

[0056] (Item 3) The data conversion rules stipulate that the keys are converted into human understandable phrases or sentences. 3. A data conversion device according to item 2.

[0057] This allows the user to read the message and take appropriate action as soon as possible.

[0058] (Item 4) The data conversion rules are defined to convert the values ​​into human understandable words or sentences. 3. A data conversion device according to item 2.

[0059] This allows the user to read the message and take appropriate action as soon as possible.

[0060] (Item 5) The data conversion rules include at least one of adjusting resolution, adding units, converting units, and converting codes into words or sentences; 5. A data conversion device according to item 4.

[0061] (Item 6) The data conversion rule information is a data set that combines one or more individually creatable policy modules that define a method of converting data. 2. The data conversion device according to claim 1. ⇒By flexibly combining multiple policy modules, it is possible to create conversion rules that correspond to various assets 11. In addition, new conversion rules can be easily created with minor modifications to existing policy modules or conversion rules.

[0062] (Item 7) the calculation unit displays a plurality of policy modules selectable by a user, and provides a user interface for creating a conversion rule that combines selected policy modules to create the data set; 7. A data conversion device according to item 6.

[0063] (Item 8) An edge device that is provided in a monitoring target and acquires and transmits data related to the monitoring target; a data conversion device that receives the data from the edge device and converts the data; having The data conversion device includes: a storage unit for storing data conversion rule information in which a data set for each controller type is registered, the data conversion rule defining a conversion rule indicating a data conversion method for each controller type; A calculation unit including a cache memory and capable of executing a software program for implementing data conversion using information stored in the storage unit, The edge device further transmits a controller type indicating a type of a controller that controls the monitoring target; the calculation unit expands the data conversion rule information in the cache memory, receives the controller type and the data from the edge device, reads a conversion rule corresponding to the received controller type from the cache memory, and converts the data using the conversion rule. Data conversion system.

[0064] According to this, the data conversion device uses the controller type received from the edge device, so there is no need to obtain controller type information from the asset identification information, enabling even faster data conversion.

[0065] (Item 9) the edge device transmits the controller type in the same message as the data; the data conversion device reads from the cache memory a conversion rule corresponding to the controller type included in the message, and converts the data using the conversion rule. Item 9. A data conversion system according to item 8.

[0066] According to this, the data conversion device does not need to hold information that associates the monitoring target with the controller type, since the controller type is received in the same message as the data. [Explanation of symbols]

[0067] 11...asset, 12...controller, 13...edge device, 14...gateway, 15...data conversion device, 16...management database, 17...data conversion unit, 18...data lake, 19...external device, 20...message queue, 21...external device, 22...display device, 31...asset management GUI unit, 32...device management GUI unit, 33...event management GUI unit, 34...conversion rule creation GUI unit, 35...asset management DB, 36...device management DB, 37...event management DB, 38...data conversion rule DB, 39...process unit, 40...process unit, 51...calculation unit, 52...storage unit, 53...communication unit, 61...data conversion rule cache, 62...conversion rule creation screen, 63...first screen, 64...second screen

Claims

1. A data conversion device that converts data acquired by an edge device associated with a monitoring target, a storage unit for storing monitoring target management information that associates the monitoring targets with controller types that indicate the types of controllers that control the monitoring targets, and data conversion rule information in which data sets are registered for each controller type that prescribes conversion rules that indicate a data conversion method for each controller type; A calculation unit including a cache memory and capable of executing a software program for implementing data conversion using information stored in the storage unit, the calculation unit expands the data conversion rule information in the cache memory, identifies a monitoring target corresponding to the data from the data received from the edge device, identifies a controller type corresponding to the identified monitoring target by referring to the monitoring target management information, reads a conversion rule corresponding to the identified controller type from the cache memory, and converts the data using the conversion rule. Data conversion device.

2. The data includes a key indicating an item and a value of the item; The data transformation rule specifies that at least one of the key and the value is to be transformed.

2. The data conversion device according to claim 1.

3. The data conversion rules stipulate that the keys are converted into human understandable phrases or sentences.

3. The data conversion device according to claim 2.

4. The data conversion rules are defined to convert the values ​​into human understandable words or sentences.

3. The data conversion device according to claim 2.

5. The data conversion rules include at least one of adjusting resolution, adding units, converting units, and converting codes into words or sentences.

5. The data conversion device according to claim 4.

6. The data conversion rule information is a data set that combines one or more individually creatable policy modules that define a data conversion method.

2. The data conversion device according to claim 1.

7. the calculation unit displays a plurality of policy modules selectable by a user, and provides a user interface for creating a conversion rule that combines selected policy modules to create the data set; 7. The data conversion device according to claim 6.

8. An edge device that is provided in a monitoring target and acquires and transmits data related to the monitoring target; a data conversion device that receives the data from the edge device and converts the data; having The data conversion device includes: a storage unit for storing data conversion rule information in which a data set for each controller type is registered, the data conversion rule defining a conversion rule indicating a data conversion method for each controller type; A calculation unit including a cache memory and capable of executing a software program for implementing data conversion using information stored in the storage unit, The edge device further transmits a controller type indicating a type of a controller that controls the monitoring target; the calculation unit expands the data conversion rule information in the cache memory, receives the controller type and the data from the edge device, reads a conversion rule corresponding to the received controller type from the cache memory, and converts the data using the conversion rule. Data conversion system.

9. the edge device transmits the controller type in the same message as the data; the data conversion device reads from the cache memory a conversion rule corresponding to the controller type included in the message, and converts the data using the conversion rule. The data conversion system according to claim 8.

10. A data conversion method for converting data acquired by an edge device associated with a monitoring target, comprising: A computer having a storage device and an arithmetic unit having a cache memory, storing in the storage device monitoring target management information associating the monitoring target with a controller type indicating a type of controller controlling the monitoring target, and data conversion rule information in which a data set for each controller type is registered, the data conversion rule defining a data conversion method for each controller type; expanding the data conversion rule information in the cache memory, identifying a monitoring target corresponding to the data from the data received from the edge device, identifying a controller type corresponding to the identified monitoring target by referring to the monitoring target management information, reading a conversion rule corresponding to the identified controller type from the cache memory, and converting the data using the conversion rule; Data conversion methods.

Images