JP6840064B2 - Data management device and data provision control method - Google Patents

Description

The present invention relates to a data management device and a data provision control method, and is suitable for application to, for example, a data management device and a data provision control method that manages each sensor data detected by each of a plurality of sensors provided in a field system. is there.

For the purpose of providing services that utilize big data, a data management system that can collectively manage site data collected from factory equipment, site equipment, sensors, etc. is provided. Such a data management system is used in a centralized monitoring system for monitoring the site by displaying the collected data on the screen of the user terminal of the operator in real time.

In recent years, with the improvement of information and communication technology, there is an increasing need for data analysis such as predictive detection of equipment abnormality from a large amount of sensor information, device information, and the like. In such data analysis, operations such as data preparation (selection of data to be analyzed), selection of analysis model, and evaluation of analysis results are performed.

In data preparation, only the sensor information to be analyzed is quickly selected from the huge amount of data. In this work, metadata is added to the accumulated data in advance, and the metadata is used to streamline the selection of sensor information to be used for analysis. Some analytical models require learning using past data, and in such cases, learning is required for each system.

On the other hand, in the field, apart from the service utilizing big data, we are working on quality improvement by our own method and adding sensors under the initiative of the field. In services that utilize big data, it is necessary to detect such system changes and handle the data required for the service appropriately. In this regard, a method capable of detecting a change in the system is disclosed (see Patent Document 1).

Japanese Unexamined Patent Publication No. 2010-206582

In the technique described in Patent Document 1, as in the case of network failure, the service affected by the system change can be identified, but for example, in the addition of a sensor for the purpose of increasing the number of measurement points, the system is affected. However, it is treated as a system change. That is, there is a problem that it is not possible to determine which of the collected data can be used because the change in the system cannot be accurately grasped.

The present invention has been made in consideration of the above points, and an object of the present invention is to propose a data management device capable of appropriately managing data.

In order to solve such a problem, in the present invention, it is a data management device that manages each sensor data detected by each of a plurality of sensors provided in the field system, can communicate with the administrator terminal, and is the field system. Indicates the dependency relationship between the interface unit that receives the configuration information change request indicating that the predetermined component of the above is changed from the administrator terminal, the configuration change request received by the interface unit, and the component related to the field system. Based on the configuration information, the sensor affected by the change of the component indicated by the configuration change request is identified, and the sensor data detected by the identified sensor and the revision information for managing the explanatory information of the sensor data are managed. The data revision information management department to update is provided.

Further, in the present invention, a data provision control method for managing and providing each sensor data detected by each of a plurality of sensors provided in the field system, the interface unit capable of communicating with the administrator terminal is provided. The first step of receiving a configuration information change request indicating that a predetermined component of the field system is changed from the administrator terminal, and a configuration change request received by the data revision information management unit by the interface unit. Based on the component information indicating the dependency of the components related to the field system, the sensor affected by the change of the component indicated by the configuration change request is identified, and the sensor data detected by the specified sensor and the above-mentioned A second step of updating the revision information for managing the explanatory information of the sensor data is provided.

According to the above configuration, it is possible to update the sensor data detected by the sensor affected by the change of the component related to the field system and the revision information for managing the explanatory information of the sensor data.

According to the present invention, it is possible to realize a data management device capable of appropriately managing data.

It is a figure which shows an example of the structure of the data management system by 1st Embodiment. It is a figure which shows an example of the hardware configuration of the data management server by 1st Embodiment. It is a figure which shows an example of the data by 1st Embodiment. It is a figure which shows the configuration example in the field system by 1st Embodiment. It is a figure which shows an example of the configuration information by 1st Embodiment. It is a figure which shows an example of the configuration information by 1st Embodiment. It is a figure which shows an example of the generation rule by 1st Embodiment. It is a figure which shows an example of the generation rule by 1st Embodiment. It is a figure which shows an example of explanatory information by 1st Embodiment. It is a figure which shows an example of explanatory information by 1st Embodiment. It is a figure which shows an example of the flowchart which concerns on the processing at the time of receiving the configuration information change request by 1st Embodiment. It is a figure which shows an example of the flowchart which concerns on the metadata automatic generation processing by 1st Embodiment. It is a figure which shows an example of the flowchart which concerns on the processing at the time of receiving a data request by 1st Embodiment.

Hereinafter, one embodiment of the present invention will be described in detail with reference to the drawings.

(1) First Embodiment In FIG. 1, 1 indicates a data management system according to the first embodiment as a whole. The data management system 1 includes a user terminal 110, an administrator terminal 120, a field system 130, and a data management server 140. The data management system 1 performs (A) data collection processing, (B) data management processing, (C) data analysis processing, (D) data provision processing, and the like, and data 140A which is sensor data transmitted from the field system 130. And the explanatory information 140B of the data 140A is appropriately managed. The details will be described below.

The user terminal 110 is communicably connected to the data management server 140 via the communication path 150, and is a terminal used by the user to use the data 140A managed by the data management server 140, the explanatory information 140B of the data 140A, and the like. Computer etc.).

The administrator terminal 120 is a terminal (computer or the like) that is communicably connected to the data management server 140 via the communication path 150 and is used by the site system administrator who manages the site system 130 to perform management work. The management work includes, for example, referencing, updating, adding, and deleting the configuration information 140C related to the field system 130 in the data management server 140, and generating information for generating the explanatory information 140B (generation rule 140D, generation program 140E). Etc.), reference, addition, update, deletion, etc.

The field system 130 includes a gateway 131 that is communicably connected to a data management server 140 via a communication path 150, a controller group 132 that controls equipment such as production line equipment and power plant equipment, and sensors built into each equipment. , A sensor group 133 having an external sensor or the like. For example, the gateway 131 aggregates on-site data such as control performance data in the controller collected by the controller group 132 and various sensor data detected by the sensor group 133, and transmits the site data to the data management server 140.

The data management server 140 is a computer, a data management device, or the like, and includes a data access I / F unit 141, a data management unit 142, a site data storage unit 143, a communication I / F unit 144, and an explanatory information access I / F unit 145. Configuration Information access I / F unit 146, data revision information management unit 147, metadata generation management I / F unit 148, and information automatic generation unit 149 are included.

Further, the data management server 140 includes data 140A, explanatory information 140B, configuration information 140C, generation rule 140D, and generation program 140E.

The data access I / F unit 141 is an interface unit (I / F unit) for accessing the data 140A, such as receiving a data request from the user terminal 110. An example of the data 140A is shown in FIG. 3 and will be described later.

When the data management unit 142 receives a data request from the data access I / F unit 141, the data management unit 142 generates response data based on the data 140A, the configuration information 140C, and the like, and sends the user terminal 110 via the data access I / F unit 141. Send.

When the field data storage unit 143 receives the packet via the communication I / F unit 144, the field data storage unit 143 stores the packet as data 140A. Further, the site data storage unit 143 transmits the data 140A to the user according to an instruction from the user (data management unit 142, automatic information generation unit 149, etc.) of the data 140A.

The communication I / F unit 144 is an I / F unit for receiving a packet transmitted from the gateway 131 of the field system 130. The communication I / F unit 144 passes the received packet to the field data storage unit 143. The packet includes on-site data, time information related to the on-site data (information indicating the time when the on-site data was acquired, the time when the on-site data was transmitted, and the like).

The explanatory information access I / F unit 145 is an I / F unit for the user terminal 110 to access the explanatory information 140B, such as receiving an explanatory information request from the user terminal 110. For example, the explanatory information access I / F unit 145 refers to, adds, updates, deletes, and the like the explanatory information 140B. The explanatory information 140B is information for explaining the data 140A (information for a person to understand the data 140A, such as an average value, a variance value, and an outlier value). An example of the explanatory information 140B is shown in FIGS. 7A and 7B, which will be described later.

The configuration information access I / F unit 146 is an I / F unit for the administrator terminal 120 to access the configuration information 140C, such as receiving a configuration information change request (configuration change request) from the administrator terminal 120. The configuration information 140C is information (system configuration information) for specifying the configuration of the field system 130. An example of the configuration information 140C is shown in FIGS. 5A and 5B, which will be described later.

When the data revision information management unit 147 receives the configuration information change request from the configuration information access I / F unit 146, the sensor is affected by the components changed in the field system 130 based on the data 140A, the configuration information 140C, and the like. Is specified, and the configuration information 140C (revision information of the specified sensor) is updated.

The metadata generation management I / F unit 148 refers to, adds, and updates the generation information (generation rule 140D, generation program 140E, etc.) for generating the explanatory information 140B via the user terminal 110 or the administrator terminal 120. This is the I / F section for deleting and the like. An example of the generation rule 140D is shown in FIGS. 6A and 6B, which will be described later.

The information automatic generation unit 149 automatically generates the explanatory information 140B based on the generation instruction, the generation information, and the like from the user terminal 110 and the like.

(A) Data collection process In the data collection process, a process for collecting site data in the site system 130 is performed at an appropriate timing. For example, the field data storage unit 143 can reconstruct the field data based on the packet received from the field system 130 via the communication I / F unit 144, use it in various data processing, or store it in the database. It is stored (stored) as data 140A in the data.

(B) Data management process In the data management process, a process of updating the configuration information 140C for managing the data 140A and the explanatory information 140B is performed. For example, the configuration information access I / F unit 146 instructs the data revision information management unit 147 to perform operations related to addition, update, deletion, etc. of the configuration information 140C in response to the configuration information change request from the administrator terminal 120. The data revision information management unit 147 changes the configuration information 140C according to the contents. Details of these series of processes will be described with reference to FIG.

(C) Data analysis process In the data analysis process, the data 140A is evaluated (the data 140A is analyzed and the explanatory information 140B is generated, etc.). For example, the information automatic generation unit 149 acquires data 140A via the site data storage unit 143 based on the generation instruction from the user terminal 110, the generation rule 140D, and the like, performs an operation according to the generation rule 140D, and results (calculation) The result) is stored as explanatory information 140B. Further, the information automatic generation unit 149 periodically performs a calculation based on the contents of the data 140A according to the generation rule 140D registered in advance, and stores the result as the explanatory information 140B. Details of these series of processes will be described with reference to FIG.

(D) Data provision process In the data provision process, data is provided from the user terminal 110 based on a data request. For example, the data management unit 142 refers to the data 140A and the configuration information 140C in response to the data request, and provides the user terminal 110 with response data configured as data that does not span revisions. Details of these series of processes will be described with reference to FIG.

Further, in the data providing process, data is provided from the user terminal 110 based on the explanatory information request. For example, the explanatory information access I / F unit 145 refers to the explanatory information 140B and the configuration information 140C in response to the explanatory information request, and provides the user terminal 110 with response data configured as data that does not span revisions.

Note that each of (A) data collection processing, (B) data management processing, (C) data analysis processing, and (D) data provision processing is basically performed asynchronously regardless of the above-mentioned order. Is.

FIG. 2 is a diagram showing an example of the hardware configuration of the data management server 140. The data management server 140 includes a CPU (Central Processing Unit) 201, a memory 202, a peripheral I / F 203, a storage device 204, a communication I / F 205, and a bus 206. The CPU 201, the memory 202, the peripheral I / F 203, the storage device 204, and the communication I / F 205 are each connected via the bus 206 and exchange information with each other.

The CPU 201 functions the data management server 140 by reading the program stored in the storage device 204 (which may be a peripheral device connected via the peripheral I / F 203) into the memory 202 and executing the program (FIG. FIG. Each part 141 to 149 shown in 1) is realized. The functions of the data management server 140 are not limited to those realized by software as described above, and some or all of the functions may be realized by hardware such as a dedicated circuit. Software and software may be combined and realized.

The memory 202 is a volatile storage device used by the CPU 201 as a working memory and a temporary buffer for input / output data when executing a program. The peripheral I / F 203 is an interface for connecting various peripheral devices such as input / output devices such as a mouse, keyboard, and monitor, and external storage such as a USB (Universal Serial Bus) memory to the data management server 140.

The storage device 204 is composed of a magnetic disk device, a flash ROM (Read Only Memory), and the like, and includes an OS (Operating System), various drivers, various application programs, and various information used in the programs (for example, an administrator or a maintainer). Information set by, data 140A, explanatory information 140B, configuration information 140C, generation rule 140D, generation program 140E, etc.) are stored. The communication I / F 205 provides an interface when the data management server 140 communicates with the user terminal 110, the administrator terminal 120, the field system 130, and the like via the communication path 150. There may be two or more communication I / F205.

Each of the user terminal 110 and the administrator terminal 120 is a computer or the like provided with a CPU, a memory, a peripheral I / F, a storage device, and a communication I / F, and is the hardware of the user terminal 110 and the administrator terminal 120. Since the configuration is the same as the hardware configuration of the data management server 140, illustration and description thereof will be omitted.

FIG. 3 is a diagram showing an example (data management table 300) of the data 140 stored in the data management server 140. The data management table 300 is a table composed of items that can uniquely identify (identify) records and items (sensor items) that store site data collected by the site system 130 for each sensor. In the data management table 300, as shown in FIG. 3, time information and site data (for example, each sensor data detected by each of the sensor group 133) are managed in association with each other.

FIG. 4 is a diagram showing a configuration example (system configuration example 400) showing the order of physical actions of site data, components, and the like in the site system 130. As shown in the system configuration example 400, in the field system 130, the sensor group 133 is installed before and after the plurality of devices. For example, with respect to "Sensor 1", "Device A", and "Sensor 2", "Sensor 1" measures on-site conditions such as temperature and humidity, and the contents are processed by "Device A", and the result is processed. It is shown to be executed in the process of measuring with "sensor 2".

5A and 5B are diagrams showing an example (configuration information management table 500A and revision management table 500B) of the configuration information 140C stored in the data management server 140.

The configuration information management table 500A stores information related to the system configuration example 400 (information indicating the dependency relationships of the components such as the device name, the collection cycle of the device, the system configuration, the parameters, and the calculation result). In the configuration information management table 500A, the source of the data is stored in "From" and the destination of the data is stored in "To" in order to handle the dependency relationship with the component existing between the sensor group 133 as metadata.

The revision management table 500B includes items that can uniquely identify records and revision information of sensors that measure field data collected by the field system 130 (corrections, revisions, etc. for managing updates of components of the field system 130). It is a table composed of items that store information). In the revision management table 500B, as shown in FIG. 5B, the time information and the revision information of each of the sensor group 133 are managed in association with each other.

Further, the revision management table 500B can be updated based on a request (configuration information change request) from the administrator terminal 120 when a sensor is added to the field system 130 or the control algorithm of the device is changed.

The revision management table 500B is composed of the same columns as the data management table 300. Further, every time data is stored in the data management table 300, the data is also stored in the revision management table 500B.

6A and 6B are diagrams showing an example (generation condition management table 600A and generation rule management table 600B) of the generation rule 140D stored in the data management server 140. The generation condition management table 600A and the generation rule management table 600B are referred to, added, updated, and deleted via the metadata generation management I / F unit 148.

The generation condition management table 600A stores information related to the automatic generation of explanatory information 140B (metadata) indicating the result of the calculation using the data 140A. More specifically, in the generation condition management table 600A, the timing for automatically generating the explanatory information 140B (setting item) and the information for determining whether or not to be the target of automatic generation (calculation execution condition) are associated with each other. Stores the obtained information (generation condition information).

For example, in "condition 1", since the setting item is "user access" and the operation execution condition is "True", the condition is satisfied at the timing when the user terminal 110 (user) accesses the explanatory information 140B. Is shown. For example, in "condition 2", the setting item is "data update" and the calculation execution condition is "100 times update", so that the data of the data management table 300 is updated a predetermined number of times (100 times in this example). Indicates that the condition is met when it occurs.

For example, in "Condition 3", the setting item is "time cycle" and the calculation execution condition is "60 minutes", so that the condition is satisfied in a specific time cycle (60 minutes time cycle in this example). Show that. For example, in "Condition 4", the setting item is "time designation" and the operation execution condition is "8:00", so that the condition is satisfied at a specific time (8:00 in this example). Shown. For example, in "condition 5", the setting item is "data value" and the calculation execution condition is "{sensor 1} <10", so that the value of the sensor information is a specific condition (sensor 1 in this example). When the sensor value of is less than 10), it indicates that the condition is satisfied.

The generation rule management table 600B has an execution No. , Target data, algorithm, parameters, and execution condition items. The target data is selected from the column names (sensor items) of the data management table 300. The algorithm is selected from the generation program 140E managed by the data management server 140. As the parameters, the parameters required for calculation by the algorithm selected from the generation program 140E are input. The execution condition is selected from the conditions set in the generation condition management table 600A.

For example, when the information automatic generation unit 149 determines that the execution condition "condition 2 and condition 4" is satisfied, the information automatic generation unit 149 calculates an average value for the sensor data of the "sensor 1".

7A and 7B are diagrams showing an example (explanatory information management tables 700A, 700B) of the explanatory information 140B stored in the data management server 140. The explanatory information management tables 700A and 700B are referenced, added, updated, and deleted by the user terminal 110 or the administrator terminal 120 via the explanatory information access I / F unit 145.

The explanatory information management table 700A is an example of assigning one explanatory information to a specific time zone. The explanatory information management table 700A is composed of a column name, a start time, an end time, a revision, explanatory items, and explanatory contents. As the column name, any of the column names of the data management table 300 is stored. The start time and end time indicate that the explanatory information is valid for the range specified in these times (time zones). The revision stores which revision the sensor specified in the column name belongs to in the range of the start time and the end time. The explanatory items and the explanatory contents indicate the explanatory information itself. Here, an example of whether or not the variance value and distribution conform to the normal distribution and the mean value is shown.

The explanatory information management table 700B is an example in which explanatory information is given to each time. In the explanation information management table 700B, the time and the explanation content are managed in association with each other for each column name, explanation item, and revision. Here, an example of whether or not it is an outlier is shown.

FIG. 8 is a diagram showing an example of a flowchart relating to the processing at the time of receiving the configuration information change request executed when the data revision information management unit 147 receives the configuration information change request via the configuration information access I / F unit 146. ..

When the data revision information management unit 147 receives the configuration information change request, the data revision information management unit 147 acquires the difference from the current configuration information management table 500A (change information such as wanting to change the device and parameters) (step S801).

The data revision information management unit 147 determines whether or not the changed From contents are included in the columns of the data table (data management table 300 or revision management table 500B) (whether or not the changed one is a sensor). Is determined (step S802). If it is determined that the data revision information management unit 147 is included (is a sensor), the process is transferred to step S804, and if it is determined that the data revision information management unit 147 is not included (not a sensor), the process is transferred to step S803.

In step S803, the data revision information management unit 147 searches the content of "To" in "From" of the configuration information management table 500A, acquires a list of affected sensors (items), and moves the process to step S804. .. For example, when the data revision information management unit 147 determines that "device A" has been changed, it searches for "device A" from "From" and "sensor 2" of "To" associated with "device A". , Then search for "Sensor 2" from "From", identify "Device C" of "To" associated with "Sensor 2", and then search for "Device C" from "From". Search for "Sensor 3" of "To" associated with "Device C", and since there is no "To" associated with "Sensor 3", "Sensor 2" and "Sensor 2" are listed as a list of sensors. Acquire "Sensor 3".

In step S804, the data revision information management unit 147 determines whether or not all the change information has been confirmed. If it is determined that the data revision information management unit 147 has been confirmed, the process is transferred to step S805, and if it is determined that the data revision information management unit 147 has not been confirmed, the process is transferred to step S801.

In step S805, the data revision information management unit 147 determines the time when the sensor is changed (the time specified by the field system administrator included in the configuration information change request, the time when the configuration information change request is received, and the like. The revision information of the sensor acquired in step S803 is updated in the revision management table 500B based on the above.

In this way, by identifying the configuration information of the field system 130 and the range of influence caused by the change and managing the information as revision information in association with the sensor, the user can use the data collected by a certain sensor. You will be able to properly determine which data is available.

FIG. 9 is a diagram showing an example of a flowchart relating to the metadata automatic generation processing executed periodically by the information automatic generation unit 149.

The information automatic generation unit 149 refers to the execution conditions of the processing target of the generation rule management table 600B (step S901).

In step S902, the information automatic generation unit 149 determines whether or not the execution condition is satisfied. When the information automatic generation unit 149 determines that the execution condition is satisfied, the process is transferred to step S903, and when it is determined that the execution condition is not satisfied, the information automatic generation unit 149 advances the processing target to the next step and shifts the process to step S901.

In step S903, the information automatic generation unit 149 refers to the revision management table 500B and acquires revision information of the time zone used for the calculation.

In step S904, the information automatic generation unit 149 performs an operation using a designated algorithm for each acquired revision information.

For example, when "execution 3" of the generation rule management table 600B is executed, "condition 3" is satisfied every "60 minutes", so that when the current time is "14:00", the "sensor" For "2", the average value from "13:00" to "14:00" is calculated. At this time, when the revision information of "Sensor 2" is changed to "13:30", the average value "50.3" of "13:00" to "13:29" and "13:30" to "13:30". The average value "51.0" of "14:00" is calculated.

In step S905, the information automatic generation unit 149 stores the calculation result in the explanatory information management tables 700A and 700B, advances the processing target to the next, and shifts the processing to step S901.

In the above-mentioned process, the case where the metadata automatic generation process is executed periodically has been described, but similarly, the case where the metadata automatic generation process is executed triggered by a user operation (user access) is also performed in steps S903 to S903. The process of step S905 is performed (illustration and description thereof are omitted).

In this way, by specifying the revision information (revision information to which the data belongs) of the time zone used for the calculation, it is possible to automatically generate explanatory information including changes in the components of the field system 130.

FIG. 10 is a diagram showing an example of a flowchart relating to data request reception processing executed when the data management unit 142 receives a data request via the data access I / F unit 141. Here, the data request is a designated section (time information) for designating the time in the data management table 300 and column information for designating the sensor group 133 (sensor identification for specifying a sensor such as "sensor 1"). Information) will be described as being configured to include.

Upon receiving the data request, the data management unit 142 acquires (selects) the revision management table 500B (step S1001).

In step S1002, the data management unit 142 acquires the revision information at the beginning of the designated section (the oldest revision information in the designated section) from the revision management table 500B.

In step S1003, the data management unit 142 selects the data management table 300 and acquires the acquired revision information data from the data management table 300 in the designated section.

In step S1004, the data management unit 142 transmits the acquired data to the request source (user terminal 110) via the data access I / F unit 141.

In this way, based on the revision information accompanying the change of the component of the field system 130, the revision information can be reconstructed into data that does not straddle and the data can be provided.

Although the case of acquiring data from the data management table 300 has been described with reference to FIG. 10, the same applies to the case of acquiring explanatory information from the explanatory information management tables 700A and 700B. That is, by using the explanatory information management tables 700A and 700B at the time of data access, it is possible to provide (manage) the explanatory content for each revision information due to the time zone and / or device change. In addition, in the past, data was searched and extracted in consideration of changes in the field such as equipment replacement and parameter changes, but according to the above configuration, it is possible to search and extract by revision information or explanation contents. Therefore, the work cost of data analysis is reduced.

According to the above configuration, for example, for a large amount of field data collected by the process control system, it is determined whether or not the control system has been changed, and information on whether or not the change of the control system has an effect is provided. , It becomes possible for higher-level services to use data without the need for reexamination in data use.

According to the present embodiment, the data collected by the field system 130 and the explanatory information of the data can be appropriately managed.

(2) Other Embodiments In the above-described embodiment, the case where the present invention is applied to the data management system 1 has been described, but the present invention is not limited to this, and various other data managements are described. It can be widely applied to systems (data provision control methods).

Further, in the above-described embodiment, in the data request reception processing, the case where the revision information at the beginning of the designated section is acquired, the revision information data is acquired, and the acquired data is transmitted to the request source has been described. The present invention is not limited to this, and all revision information of the designated section is acquired, data is acquired for each revision information, and the data is transmitted to the requester in an identifiable data format (mode) for each revision information. You may.

Further, in the above-described embodiment, the case where the revision information of each sensor is managed (stored) in the revision management table 500B every predetermined time (for example, every time data is stored in the data management table 300) has been described. However, the present invention is not limited to this, and a predetermined time may be a specified time such as 1 second, or the time when the revision information is changed can be specified in a data format (for example, for the same revision information of each sensor). May be managed in association with one time zone).

1 ... Data management system, 110 ... User terminal, 120 ... Administrator terminal, 130 ... Field system, 140 ... Data management server.

Claims (4)

It is a data management device that manages each sensor data detected by each of a plurality of sensors installed in the field system.
An interface unit that can communicate with the administrator terminal and receives a configuration information change request from the administrator terminal indicating that a predetermined component of the field system is changed.
Based on the configuration change request received by the interface unit and the configuration information indicating the dependency of the components related to the field system, the sensor affected by the component change indicated by the configuration change request is identified. , The data revision information management unit that updates the sensor data detected by the specified sensor and the revision information for managing the explanatory information of the sensor data.
A data management device characterized by comprising. The interface unit can communicate with the user terminal, and receives a data request from the user terminal for requesting the sensor data stored in the storage device that stores each sensor data.
The data request includes time information for specifying a time zone for requesting the sensor data and sensor identification information for specifying each of the plurality of sensors.
A data management unit is provided that acquires revision information of the time zone included in the data request based on the data request received by the interface unit and extracts sensor data from the storage device for each acquired revision information.
The interface unit transmits the sensor data extracted by the data management unit to the user terminal.
The data management device according to claim 1. Based on the generated information including the algorithm for calculating the explanatory information of each sensor data and the execution condition, the revision information used for the calculation in the algorithm of the generated information satisfying the execution condition is specified, and the respective sensor data. It is provided with an information automatic generation unit that reads sensor data used for calculation by the algorithm from a storage device that stores the information and calculates explanatory information of the read sensor data for each specified revision information.
The data management device according to claim 1. It is a data provision control method for managing and providing each sensor data detected by each of a plurality of sensors installed in a field system.
The first step of receiving a configuration information change request from the administrator terminal indicating that the interface unit capable of communicating with the administrator terminal changes a predetermined component of the field system, and the first step.
The data revision information management unit changes the components indicated by the configuration change request based on the configuration change request received by the interface unit and the configuration information indicating the dependency of the components related to the field system. A second step of identifying the affected sensor and updating the revision information for managing the sensor data detected by the identified sensor and the explanatory information of the sensor data.
A data provision control method comprising.

Images