JP6917939B2 - Data provider - Google Patents

Description

The present invention relates to a data providing device and a data providing method.

In recent years, for the purpose of providing services utilizing so-called big data, a data processing device capable of collectively managing and providing on-site data collected from factory equipment and on-site equipment has been proposed.

The site data is used in a service that visualizes the amount of electric energy measured in the factory and obtains the operating rate from the number of products produced for each line (hereinafter, this is simply referred to as "service"). However, since each site data has different types and characteristics, in order to use the site data in a service, it is necessary to appropriately preprocess each site data and provide it in a format in which the service can be used.

Therefore, Patent Document 1 discloses a technique for generating integrated time-series data by combining data acquired at a plurality of different cycles and interpolating the shortage value of the combined data. In Patent Document 2, in the above-mentioned interpolation processing, a technique is developed in which the interpolation processing is selected according to the property of the desired data series value, and the acquired time series data is integrated to generate the time series data at an arbitrary time. Has been done.

Japanese Unexamined Patent Publication No. 2003-44518 Japanese Unexamined Patent Publication No. 2013-239013

By the way, on-site data collected from factory equipment and the like have different characteristics such as acquisition cycle, time accuracy, and presence / absence of missing values. For this reason, if the data is integrated using only the time of each site data, it becomes integrated data including insufficient values and irregular values, and it may be difficult to use it in the service.

Furthermore, since the characteristics of the data required by the service vary, the service user needs to format the data for each site system so that the service can appropriately handle the site data of a plurality of site systems.

However, in the techniques disclosed in Patent Documents 1 and 2, the service user fully understands the meaning of the site data acquired by the site system, and the site data itself is appropriately preprocessed. Is assumed. The meaning of the field data includes, for example, a difference in the time accuracy of the field system, a definition when an abnormal value is recorded, and the like. However, the service user does not always fully understand the meaning of the site data and use the service. If the service user does not fully understand the meaning of the site data, preprocessing is required to understand the meaning of the site data and format the data into a format that can be used by the service.

The present invention has been made in view of the above problems, and an object of the present invention is to provide a data providing device and a data providing method capable of efficiently providing data corresponding to data processing.

In order to solve the above problems, the data providing device according to the present invention is a data providing device that provides data in response to a request from the data processing device, and is a data acquisition unit that acquires data from a field device and a data processing device. Based on the specification description information indicating the specifications of the predetermined data used in, a predetermined table corresponding to the data processing executed by the data processing device is generated, and the data acquired from the data acquisition unit or based on the data. It is provided with a data generation unit that generates predetermined data by setting any of the generated data in a predetermined table and provides the generated predetermined data to a data processing apparatus.

According to the present invention, a predetermined table corresponding to data processing executed by a data processing device is generated, and by setting data in the predetermined table, predetermined data used in the data processing device is generated. be able to.

It is explanatory drawing which shows the outline of the data integration system including the data providing apparatus. It is a functional block diagram which shows the whole structure of the data integration system including a data providing apparatus. It is a hardware block diagram of the data providing apparatus. It is a block diagram which shows the internal structure of the service data generation part. Explanation of service table It is explanatory drawing which shows the structure of the information management table. It is explanatory drawing which shows the structure of the service data series explanatory information management table. It is explanatory drawing which shows the structure of the service table explanatory information registration screen. It is explanatory drawing which shows the structure of the service data series explanatory information registration screen. It is a flowchart which shows the service data provision process. It is a flowchart which shows the service data generation processing. It is a flowchart which shows the on-site data shortage value determination processing. It is a flowchart which shows the service data series value determination processing. It is a flowchart which shows the service data series shortage value determination processing. It is a flowchart which shows the service table explanation information registration process. It is a flowchart which shows the service data series explanation information registration process. It is explanatory drawing which shows the example of the site data and the generated service data, (1) shows the comparative example, and (2) shows the case of this Example.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. The data providing device 1 of the present embodiment prepares a data set (predetermined data) corresponding to the data processing 200 so that the data processing device 2 can easily execute the data processing 200. The data providing device 1 first defines a predetermined data configuration (which may also be called a specification or format) based on the request of the data processing device 2, and then the data acquired from the field device 3. To fit the given data structure. That is, in the present embodiment, the site data is adjusted according to the format (configuration, specifications) required by the data providing destination.

FIG. 1 is an explanatory diagram showing an overall outline of a data integration system including the data providing device 1 according to the present embodiment. The data providing device 1 can be applied to various sites 4 such as a power plant, a chemical plant, a steel mill, and a mechanical farm.

The data providing device 1 acquires the data acquired from the site device 3 in the site 4 in response to the request from the data processing device 2, and provides the acquired data in a form according to the request of the data processing device 2. do. The data providing device 1 includes, for example, a data generation unit 11, a specification explanation information management unit 12, and a data acquisition unit 13.

The data generation unit 11 is a function of generating data in the format required by the data processing device 2 and supplying the data to the data processing device 2. The data generation unit 11 sets either the site data 42 acquired from the site device 3 or the data generated from the site data 42 in a predetermined table 41 having a format (specification) corresponding to the data processing 200. As a result, the data generation unit 11 generates predetermined data (data set) required by the data processing device 2 and provides it to the data processing device 2.

The data generation unit 11 has data based on the site data 42 or the site data 42 with respect to the table generation unit F10 that generates a predetermined table 41 and the blanks in the table 41 or the blanks in the intermediate stage table used to generate the table 41. The setting units F11 to F13 for setting any of the above are provided.

The first setting unit F11 sets a shortage value of the site data 42 acquired from the site device 3 by the data acquisition unit 13. The second setting unit F12 uses reference data for the site data 42 for which the shortage value has been set by the first setting unit F11 so as to correspond to each value of a data series (reference data series) that serves as a reference for predetermined data. Set the data of another data series associated with the series. The third setting unit F13 sets a shortage value that could not be set by the second setting unit F12.

Specification explanation information management unit 12 as an "information management unit" is a function of managing specification explanation information that defines specifications (formats) of predetermined data used in the data processing device 2. The specification explanation information management unit 12 stores and manages information input from, for example, a service user as specification explanation information.

The data acquisition unit 13 is a function of acquiring data (site data) from the site device 3 in response to an instruction from the data generation unit 11.

The data processing device 2 is a calculator that executes data processing 200. The data processing 200 includes, for example, data analysis processing such as abnormality sign diagnosis processing, failure determination processing, life prediction processing, operating state prediction processing, and process monitoring processing. The data processing 200 may perform processing other than these illustrated processes.

The field device 3 is arranged at the field 4. The field device 3 includes various types such as time, temperature, humidity, flow rate, pressure, color, hardness, liquid level, rotation speed, voltage, current, frequency, illuminance, atmospheric pressure, length, pH, and loudness. A physical quantity (which may include a psychophysical quantity) is detected and transmitted to the data providing device 1. The physical quantities detected by the field device 3 can also be called detection targets, sensor data, and parameters. Each site device 3 records site data 42 according to its characteristics (acquisition cycle, time accuracy, presence / absence of missing values, etc.), and transmits the recorded site data 42 to the data acquisition unit 13.

The site device 3 may transmit the site data 42 in response to a request from the data providing device 1, or may transmit the site data 42 at a predetermined cycle or when a predetermined event occurs. Site devices 3 having different transmission methods may be mixed in the same site 4.

Note that FIG. 1 shows a case where one data providing device 1 is associated with one or more field devices 3 in one site 4, but the present invention is not limited to this, and one data providing device 1 is not limited to this. It may be associated with a plurality of field devices 3 distributed in 4.

As described above, the data providing device 1 shown in FIG. 1 uses the field data 42 acquired from the field device 3 and the specification explanation information of the data provided to the data processing 200, and determines the predetermined data according to the request of the data processing 200. Generate the data of.

The data providing device 1 of the present embodiment determines a reference data series that serves as a reference for predetermined data and its values based on the specification explanation information of the data used in the data processing 200, and further associates the reference data series with the reference data series. Select the data series of. As a result, a predetermined table for generating predetermined data is created.

The data providing device 1 determines the value of another data series so as to correspond to each value of the reference data series. When there is no missing value or a value (data) directly corresponding to the value of the reference data series, the setting units F11 to F13 set the missing value or the nonexistent value. As a result, a predetermined table is created.

Therefore, according to the present embodiment, the service user who uses the data processing 200 of the data processing device 2 can obtain necessary data from the data providing device 1 without depending on the data characteristics of each field device 3. can. According to this embodiment, it is possible to reduce the man-hours for shaping the site data so as to correspond to the data processing 200 (information processing service), and it is possible to realize a data providing device with high usability and work efficiency.

The first embodiment will be described with reference to FIGS. 2 to 16. FIG. 2 shows the overall configuration of the data integration system including the data providing device 1.

The data integration system includes, for example, a service terminal 20, an explanatory information setting terminal 21, a data providing device 10, and a field system 30. The correspondence with FIG. 1 will be described. The data providing device 10 corresponds to the data providing device 1, the service terminal 20 corresponds to the service terminal 2, and the field system 30 corresponds to the field device 3. The data generation unit 11 corresponds to the data generation instruction unit 112 and the service data generation unit 113, and the specification explanation information management unit 12 corresponds to the explanation information registration unit 122, the management screen generation unit 123, and the explanation information management unit 124. The data acquisition unit 13 corresponds to the query generation unit 114, the query execution control unit 115, and the data reception unit 116. The information processing service 200 is a paraphrase of the data processing 200 of FIG.

Next, the configuration of the communication connection will be described. Each service terminal 20 and the data providing device 10 are connected by a communication path CN1 and can communicate data with each other. The explanatory information setting terminal 21 and the data providing device 10 are connected to each other by a communication path CN2 so as to be capable of bidirectional communication. The data providing device 10 and the field system 30 are connected to each other via a communication path CN3 so as to be capable of bidirectional communication.

As the communication path CN, for example, a local area network (LAN) in the organization, the Internet, or the like may be used. A dedicated line may be used. The communication path CN may be either wired communication or wireless communication. Any one or all of the communication paths CN1 to CN3 may be configured as a common communication path.

The service terminal 20, which is an example of the "data processing device", executes the information processing service 200 as "data processing". Hereinafter, the information processing service is abbreviated as a service. As described above, the service 200 includes data analysis processing such as predictive diagnosis processing, failure determination processing, life prediction processing, operating state prediction processing, and process monitoring processing. Each service terminal 20 can execute at least one service 200. A plurality of different services 200 may be executed by one service terminal 20. Alternatively, the same service 200 may be executed on a plurality of service terminals 20.

The service terminal 20 transmits a data acquisition request to the data providing device 10 via the communication path CN1, and acquires the data required for the service 200 from the data providing device 10. The detailed processing flow of data acquisition will be described later in FIG. The service terminal 20 can be configured for each service such as "service A" and "service B", for example. In the figure, the service terminal 20 capable of providing the service A to the end user (service user) is displayed as "service terminal A". Similarly, the service terminal 20 capable of providing the service B to the end user is displayed as "service terminal B".

The explanatory information setting terminal 21 is a terminal that operates on the service table explanatory information and the service data series explanatory information as "specification explanatory information" registered in the data providing device 10. Operations include, for example, registering, editing, and deleting. The explanatory information setting terminal 21 may be shared with the service terminal 20. That is, one computer terminal may be used as the service terminal 20 and the explanatory information setting terminal 21.

The service table explanation information is information for explaining the service data (hereinafter, referred to as "service table") requested by the service terminal 20 from the data providing device 10, and is, for example, a data series that is used as a reference when generating service data. Includes information, data granularity, etc.

The service data series explanatory information is information for explaining a data series (hereinafter, referred to as "service data series") constituting the service data. The service data series explanation information includes, for example, information that associates service data with field data that is the source of the service data, interpolation rules for data interpolation processing such as pre-value interpolation and linear interpolation, and data such as average value and correlation value. Includes rules for determining series values in the series creation process. The service data corresponds to "predetermined data", and the service table corresponds to "predetermined table".

When the data providing device 10 receives the data acquisition request (service data acquisition request) from the service terminal 20, the data providing device 10 acquires the on-site data necessary for generating the service data from the on-site system 30, and provides the service table explanation information and the service data series explanation information. Service data is generated by data conversion based on. Then, the data providing device 10 transmits the generated service data to the service terminal 20 of the data request source.

The data providing device 10 includes, for example, a data access interface (the interface is abbreviated as I / F in the figure) 111, a data generation instruction unit 112, a service data generation unit 113, a query generation unit 114, and a query execution control unit. 115, data receiving unit 116, communication interface 117, explanatory information access interface 121, explanatory information registration unit 122, management screen generation unit 123, explanatory information management unit 124, service table explanatory information management table 125. , Service data series explanatory information management table 126 and the like.

The data access interface 111 realizes both an interface for receiving a data acquisition request from the service terminal 20 and an interface for providing data to the service terminal 20. As the data access interface 111, for example, REST of WebAPI (Web Application Programming Interface) can be used.

The data generation instruction unit 112 is a functional block that generates the service data requested by the service terminal 20. The data generation instruction unit 112 uses, for example, the service table explanation information management table 125 and the service data series explanation information management table 126 (hereinafter, these two management tables are referred to as “each explanation information management table” via the explanation information management unit 124. Refer to the information in). The data generation instruction unit 112 requests the query generation unit 114 to generate a query in order to acquire necessary site data from the site system 30 based on the referenced information. Then, the data generation instruction unit 112 acquires the site data from the site system 30 via the data reception unit 116, and instructs the service data generation unit 113 to perform data conversion processing on the acquired site data. These detailed processing flows will be described with reference to FIG.

The service data generation unit 113 is a functional block that converts data according to a data conversion request from the data generation instruction unit 112. Details of this functional block will be described with reference to FIG.

The query generation unit 114 generates a query for acquiring the site data from the site system 30 in accordance with the query generation request from the data generation instruction unit 112, and instructs the query execution control unit 115 to execute the generated query. It is a functional block.

The query execution control unit 115 is a functional block that issues a query to the field system 30 via the communication interface 117 in accordance with a query execution instruction from the query generation unit 114.

The data receiving unit 116 is a functional block that receives field data, which is a response from the field system 30 to the query, via the communication interface 117 and passes it to the data generation instruction unit 112.

The communication interface 117 provides an interface for communicating with the field system 30 via the communication channel CN3.

The explanatory information access interface 121 realizes an interface for receiving a data acquisition request from the explanatory information setting terminal 21 and an interface for providing data to the explanatory information setting terminal 21. The explanatory information access interface 121 includes, for example, REST of WebAPI.

The explanatory information registration unit 122 is a functional block that registers / changes / deletes information in the explanatory information management tables 125 and 126 in response to a registration / change / deletion request of various explanatory information received from the explanatory information setting terminal 21. be.

The management screen generation unit 123 is a functional block that acquires the information of the explanation information management tables 125 and 126 in response to the explanation information management screen request from the explanation information setting terminal 21 and generates the explanation information management screen.

The explanatory information management unit 124 is a functional block that manages the explanatory information management tables 125 and 126. The explanatory information management unit 124 registers / changes / deletes data in the explanatory information management tables 125 and 126 in response to a request from the data generation instruction unit 112 and the explanatory information registration unit 122.

The service table explanation information management table 125 is a table that manages the service table explanation information. A detailed table configuration will be described with reference to FIG.

The service data series explanation information management table 126 is a table for managing the service data series explanation information. A detailed table configuration will be described with reference to FIG.

The field system 30 as the “field device” transmits the field data requested from the data providing device 10 to the data providing device 10 via the communication path CN3. The field system 30 is, for example, a gateway 311 that connects the data providing device 10 and the field system 30, a sensor group 313, a controller 312 that controls these sensors 313, and field data that accumulates field data sensed by the sensor 313. It is provided with a storage unit 314.

The hardware configuration of the data providing device 10 will be described with reference to FIG. The data providing device 10 includes, for example, a host CPU (Central Processing Unit) 101 that performs various processes, a host memory 102, a storage device 103, a communication interface 104, a peripheral interface 105, and a bus 106. The host CPU 101, the host memory 102, the storage device 103, the communication interface 104, and the peripheral interface 105 are connected via the bus 106 so that information can be exchanged with each other.

The host CPU 101 is an arithmetic unit that executes a predetermined computer program held in the storage device 103. When the host CPU 101 executes a predetermined computer program, each function of the data providing device 10 described in FIG. 2 is realized.

The host memory 102 is a volatile storage device used as a working memory and a temporary buffer for input / output data when the host CPU 101 executes the above-mentioned computer program.

The storage device 103 is composed of, for example, a magnetic disk device, a flash ROM (Read Only Memory), and the like, and includes computer programs such as an OS (operating system), various drivers, and various application programs, and various information used in these computer programs. (For example, information set by an administrator or a maintainer, etc.) is stored.

The communication interface 104 provides an interface for the data providing device 10 to communicate with the service terminal 20, the explanatory information setting terminal 21, and the field system 30 via the communication paths CN1 to CN3. There may be two or more communication interfaces 104.

The peripheral interface 105 is an interface for connecting the peripheral device to the data providing device 10. Peripheral devices include, for example, input / output devices such as a mouse, keyboard, monitor display, and printer, and external storage such as a USB (Universal Serial Bus) memory.

FIG. 4 is a block diagram of the internal configuration of the service data generation unit 113. The service data generation unit 113 includes, for example, a reference data series determination unit 1131, a site data shortage value determination unit 1132, a service data series value determination unit 1133, and a service data series shortage value determination unit 1134.

The reference data sequence determination unit 1131 is a functional block that determines a reference data sequence when generating service data.

The site data shortage value determination unit 1132 is a functional block that determines the shortage value of the received site data based on the explanatory information of the explanatory information management tables 125 and 126. Missing values include, for example, missing values and abnormal values.

The service data series value determination unit 1133 is a functional block that determines the service data series value based on the site data generated by the site data shortage value determination unit 1132 and the explanatory information of the explanatory information management tables 125 and 126.

The service data series shortage value determination unit 1134 is a functional block that determines a value that has not been determined by the service data series value determination unit 1133. The processing flow of these four functional blocks will be described with reference to FIGS. 10 to 13.

FIG. 5 shows the configuration of the service table explanatory information management table 125. The service table description information management table 125 manages information for determining a reference data series of the service table. That is, the service table explanation information management table 125 stores, for example, each information of the service table name 1251, the reference data series name 1252, the data granularity 1253, the offset 1254, the start value 1255, and the end value 1256. ..

In the column of the service table name 1251, a name for uniquely identifying the service table is stored. The service table name 1251 stores information (ID, name, etc.) for identifying each service table, for example, "table A used in service A".

In the column of the reference data series name 1252, the information of the reference data series for generating the service table is stored. The name of the reference data series can be selected from the information stored in the service data series description information management table 126. Alternatively, the name of the data series existing in the field data other than the information stored in the service data series explanation information management table 126 may be selected as the name of the reference data series.

The data particle size 1253 column stores information on the data particle size of the reference data series specified by the reference data series name 1252. For example, if the reference data series is a "time series", the time particle size "3 seconds" or the like is stored.

The column of offset 1254 stores a value (hereinafter, referred to as "offset") meaning a difference from the reference value. The offset 1254 is information that is needed along with the data particle size 1253 when determining the reference data sequence. The offset 1254 is specified within the range of data particle size 1253.

For example, a case where a certain time series data is specified as the reference data series 1252 and the data particle size 1253 is set to "5 seconds" will be described. In this case, the reference value is a value obtained by repeatedly adding the data particle size "5 seconds" with "0" as a reference. That is, "0 seconds per minute", "5 seconds per minute", "10 seconds per minute", and the like. In the above example, the value of the reference data series is determined by the data particle size 1253 and the offset 1254, but the value of the data series can also be determined by specifying the start value 1255 and the end value 1256 described later.

The start value 1255 and the end value 1256 store the start value and the end value of the reference data series, respectively. For example, if the reference data series is a "time series", values such as the time "2018-01-01 0:00:00" are stored.

The record indicated by reference numeral 1257 is an example of service table explanatory information. This selects "time A" from the data series stored in the service data series explanation information management table 126 as the reference data series of "service table A", and it is the start time "2018-01-01 0: It shows that it is a time series of data granularity "1 second" and offset "0 second" from "00:00" to the time of the latest record of the acquired site data.

In determining the reference data series, instead of specifying the data series, information that can uniquely determine the data series may be given. For example, in the record indicated by reference numeral 1258, the reference data series is a "time series", which starts from the start time "2018-01-07 12:00:00" and ends at the end time "2018-01-07 12:10: 00". It shows that it is a time series with a time granularity of "5 seconds" and an offset of "1 second" up to.

In addition, columns 1252-1256 must be designated so that the reference data series is uniquely determined. For example, if the data particle size 1253 is specified but the offset 1254 is not specified, the value of the reference data series can take any value within the range in which the offset can be specified. Therefore, in this case, it is necessary to specify the offset. On the other hand, if it can be specified so that the reference data series is uniquely determined, it is not necessary to set some information of columns 1252 to 1256.

FIG. 6 shows the configuration of the service data series explanatory information management table 126. The service data series explanation information management table 126 includes, for example, a service table name 1261, a service data series name 1262, a site data name 1263, a site data shortage value determination rule 1264, a service data series value determination rule 1265, and a service. Each information with the data series shortage value determination rule 1266 is stored.

The column of the service data series name 1262 stores a name for uniquely identifying each column of the service table.

In the column of the site data name 1263, a data name for uniquely identifying the site data before generating the service data is stored.

In the column of the site data shortage value determination rule 1264, a rule for determining the site data shortage value specified by the site data name 1263 is stored. The rule for determining the shortage value of the site data is applied when the site data is missing or data indicating an abnormality is stored. For example, when the determination rule 1264 is "fixed value interpolation fixed value: 0", "0" is substituted for the insufficient value of the site data. In the determination rule 1264, additional conditions for applying the site data shortage value determination rule, such as a condition for determining an abnormal value, may be set.

In the column of the service data series value determination rule 1265, a rule for determining the series value of the service data series name 1262 is stored. For example, the decision rule 1265 is "linear interpolation", the value of "2018-01-01 0:00:00" in the field data is "100", and the value of "2018-01-01 0:00:10" is "200". , The value of "2018-01-01 0:00:05" in the service data series is determined to be "150".

In the column of the service data series shortage value determination rule 1266, a rule to be applied when the service data series value is insufficient as a result of applying the determination rule 1265 to generate the service data series is set.

For example, when the determination rule 1266 is "preliminary value interpolation", the shortage value of the service data series is assigned the same value as the time closest to the shortage value time from the time earlier than the shortage value time. .. For example, if the data particle size is "5 seconds" and the value of "2018-01-01 0:00:05" is insufficient, the value of the previous value "2018-01-01 0:00:00" The value is assigned. If the previous value does not exist, the value of the previous value "2017-12-31 23:59:55" is substituted. If that value does not exist, the time is further traced back in data particle size units, and the existing value is substituted as the insufficient value.

The record of reference numeral 1267 is an example of the service data series explanatory information 126. In this information, rules for generating "service A table A" and "data d1" from the data of "field system FS (1) sensor SS (1)" are described. Details of these determination rules will be described with reference to FIGS. 11 to 13.

It should be noted that the determination rules 1264 to 1266 may not set all or part of these rules.

A management screen for the explanatory information setting terminal 21 to manage the various explanatory information 125 and 126 shown in FIGS. 4 and 6 will be described with reference to FIGS. 7 and 8.

FIG. 7 is an example of the service table explanation information registration screen G10. This screen G10 is a user interface used by an end user who is a service user to register / change / delete a service table using the explanatory information setting terminal 21. Hereinafter, the end user who is a service user may be referred to as a user.

The screen G10 includes, for example, a service table name selection unit G100, a registration / update confirmation button G101, a service table name input unit G102, a reference data series selection unit G103, a data granularity input unit G104, and an offset input unit G105. , The start value input unit G106, the end value input unit G107, the add / update button G108, the service table explanation information display unit G109, the edit button G110, and the delete button G111 are included.

The service table name selection unit G100 is an interface for selecting a service table for editing the explanatory information 125. The user may directly input and specify the service table name in the service table name selection unit G100, or may select from the list of service tables already registered.

The registration / update confirmation button G101 is an interface for confirming the result of registration / change / deletion on the screen G10. When confirmed, the information in the explanatory information management table 125 shown in FIG. 5 is updated.

The service table name input unit G102 is an interface for determining the service table name when a new service table is added or the name of the already registered service table is changed.

The reference data series selection unit G103 is an interface for selecting a reference data series when generating a service table. The selection unit G103 selects from a list of names registered in various explanatory information management tables 125 and 126. If the reference data series is uniquely determined without specifying the reference data series, the type of the reference data series may be selected, for example, "time series".

The data particle size input unit G104 and the offset input unit G105 are interfaces for inputting the data particle size and the offset of the reference data series selected by the reference data series selection unit G103.

The start value input unit G106 and the end value input unit G107 are interfaces for inputting the start value and the end value of the reference data series selected by the reference data series selection unit G103. The start and end values are used in determining the range of the reference data series.

The add / update button G108 is an interface used when registering or updating the results input to the input units G102 to G107. When the add / update button G108 is pressed while the service table is not selected in the service table name selection unit G100, a new line of service table explanation information is added to the service table explanation information display unit G109. On the other hand, when the button G108 is pressed while the service table is selected by the service table name selection unit G100, the service table explanation information display unit G109 updates the line of the corresponding service table explanation information.

The service table explanation information display unit G109 is an interface for displaying the currently registered service table explanation information.

The edit button G110 is an interface used when editing the service data series explanatory information of each service table. The user can edit the service data series explanatory information of the corresponding service table by pressing the edit button G110 of each line of the display unit G109. Further, the user can perform various operations on the service data series explanation information registration screen G20 of FIG. 8 which will be described later.

The delete button G111 is an interface for deleting each service table on the service table explanation information display unit G109. When the user presses the delete button G111 of each row of the display unit G109, the corresponding service table explanatory information is deleted from the display unit G109.

FIG. 8 is an example of the service data series explanation information registration screen G20. This screen G20 is a user interface used by the user to register / change / delete service data series explanatory information using the explanatory information setting terminal 21.

The screen G20 includes, for example, a service data series name selection unit G200, a registration / update confirmation button G201, a service data series name input unit G202, a site data selection unit G203, a site data shortage value determination rule selection unit G204, and the like. Service data series value determination rule selection unit G205, service data series shortage value determination rule selection unit G206, add / update button G207, service table explanation information display unit G208, service data series explanation information display unit G209, and deletion Includes button 712 and.

The service data series name selection unit G200 is an interface for selecting a service data series for editing explanatory information. The user may directly enter and specify the service data series name, or may select from a list of service tables already registered.

The registration / update confirmation button G201 is an interface for confirming the result of registration / change / deletion on the main screen G20. When confirmed, the information in the explanatory information management table 126 managed in the table 126 in FIG. 6 is updated.

The service data series name input unit G202 determines the service data series name when a new service data series is added to the service table or when the name of the already registered service data series is changed. Interface.

The site data selection unit G203 is an interface used when designating site data for generating the service data series input to the service data series name input unit G202.

The site data shortage value determination rule selection unit G204, the service data series value determination rule selection unit G205, and the service data series shortage value determination rule selection unit G206 are interfaces for selecting the above-mentioned determination rules 1264, 1265, 1266. Details of these determination rules will be described with reference to FIGS. 11 to 13.

The add / update button G207 is an interface used when adding / updating the results input to the input units G202 to G206. When the add / update button G207 is pressed in the service data series name selection unit G200 when the service data series is not selected, a new line of service data series explanation information is added to the service data series explanation information display unit G209. Will be done. In the service data series name selection unit G200, when the button G207 is pressed while the service data series is selected, the service data series explanation information display unit G209 updates the line of the corresponding service data series explanation information. ..

The service table explanation information display unit G208 is an interface for displaying the service table explanation information to which the currently displayed service data series explanation information belongs.

The service data series explanation information display unit G209 is an interface for displaying the currently registered service table explanation information. The service data series explanation information display unit G209 may not be able to set or delete the service data series determination rule set in the reference data series. When the reference data series is changed, it may be possible to determine and delete each determination rule of the set service data series.

The delete button G210 is an interface for the user to delete each service data series in the service data series explanation information display unit G209. When the user presses the delete button G210 of each line of the display unit G209, the corresponding service data series explanatory information is deleted from the display unit G209.

Various processing flows of the data providing apparatus 10 will be described with reference to FIGS. 9 to 15. FIG. 9 is a flowchart showing a process in which the data providing device 10 provides service data to the service terminal 20. This process is executed when the service terminal 20 requests the service data from the data providing device 10.

When the data generation instruction unit 112 of the data providing device 10 receives the service data acquisition request from the service terminal 20 via the data access interface 111 (S10: YES), this process is started. The data generation instruction unit 112 passes the service table name and the service table data series name included in the service data request to the explanatory information management unit 124, and from the explanatory information management tables 125 and 126, the explanatory information regarding the service data is described. Get the list (S11).

The data generation instruction unit 112 generates a list of site data required for service data generation from the explanatory information acquired in step S11 (S12).

The data generation instruction unit 112 acquires necessary site data from the site system 30 (S13). For example, the data generation instruction unit 112 instructs the query generation unit 114 to generate a query for data acquisition. When the generated query is executed by the query control execution unit 108, the data generation instruction unit 112 can acquire the site data from the site system 30 via the communication interface 117 and the data reception unit 116.

The data generation instruction unit 112 passes the site data acquired from the site system 30 and various explanatory information 125 and 126 to the service data generation unit 113, and requests the service data generation unit 113 to start the data generation process (S14). Details of step S14 will be described with reference to FIG.

Finally, the data generation instruction unit 112 returns the service data generated by the service data generation unit 113 to the service terminal 20 (S15).

FIG. 10 is a flowchart illustrating a processing flow of the service data generation unit 113 when the data generation instruction unit 112 requests the service data generation unit 113 to generate the service data.

When the data generation instruction unit 112 passes the site data and various explanatory information 125 and 126 to the service data generation unit 113, the service data generation unit 113 combines the site data into one data using the time series as a key. (S21).

The time series is used as a key. For example, for field data acquired from two different sensors 313, if there are values acquired at the same time, these two values are arranged side by side to generate one row. For time values that exist only in one field data, only one value is described and the other value is empty to generate a row. By repeating these operations, step S21 is executed. By setting a key data series separately, on-site data may be combined.

The service data generation unit 113 determines a reference data series from the site data combined in step S21 by referring to the service table explanation information management table 125 (S22).

The service data generation unit 113 generates a reference data series by generating the value of the data series determined in step S22 with reference to the service table explanation information management table 125 (S23).

The service data generation unit 113 executes a three-step determination flow according to steps S25 to S27 for each service data series included in the service data (S24), and determines the value of each service data series. In steps S25 to S27, each determination process is carried out with reference to the determination rules 1264 to 1266 included in the service data series explanatory information 126.

However, not all of the decision rules 1264 to 1266 are implemented. It is possible that only some rules will be enforced and others will not. Details of each determination flow will be described with reference to FIGS. 11 to 13.

FIG. 11 is a flowchart illustrating a field data shortage value determination flow (S25) that is executed first among the above-mentioned three-stage determination flows.

The service data generation unit 113 confirms whether or not a rule for determining the shortage value of the site data is set (S31). When the rule for determining the shortage value of the site data is not set (S31: NO), the process returns to the data generation process of FIG. 10 and shifts to the service data series determination flow (S26).

When the rule for determining the shortage value of the site data is set (S31: YES), the service data generation unit 113 confirms whether or not the value exists at all the sequence points of the site data (S32).

When there are values in all the sequence points (S32: YES), the service data generation unit 113 returns to the process of FIG. 10 and shifts to the service data sequence determination flow (S26).

When there is a series point where the value does not exist (S32: NO), the service data generation unit 113 refers to the value existing in the data series of the site data and the site data shortage value determination rule, so that the value of the site data can be changed. Create a value for a series point that does not exist (S33). Then, the service data generation unit 113 returns to the process of FIG. 10 and shifts to the service data series determination flow (S26). Here, the value of the data series referred to when determining the shortage value of the field data may be that of the data series itself for which the value is created, or a data series other than the data series for which the value is created. It may be the value of.

FIG. 12 is a flowchart showing a service data series value determination flow (S26) executed in the second stage of the above-mentioned three-stage determination flow.

The service data generation unit 113 determines whether or not a rule for determining the series value of the service data is set for each service data series (S41).

When the rule for determining the series value of the service data is not set (S41: NO), the service data generation unit 113 returns to the process of FIG. 10 and shifts to the flow (S27) for determining the shortage value of the service data series. do.

On the other hand, when the rule for determining the series value of the service data is set (S41: YES), the service data generation unit 113 includes the reference data series included in the explanatory information 125 acquired in step S22 of FIG. , Data granularity, offset, start value, end value are referred to, and a value for determining a service data series value is extracted (S42).

Step S42 will be described in detail. For example, the reference data series "time A", the data particle size "5 seconds", the offset "0 seconds", the start value "2017-01-01 00:00:00", and the end value "none" will be described as examples. ..

As a value for determining the value of each series point of the service data, data for 5 seconds including the time of each series point is extracted from the data series of the site data. This 5 seconds is determined by the offset, and in this case, it is determined based on 0 seconds per minute. For example, 0 seconds to 4 seconds per minute, 5 seconds to 9 seconds, 10 seconds to 14 seconds, and the like. However, the extraction target is from "2017-01-01 00:00:00" to the record of the latest time at time A. In the above example, the value that determines the service data series value is determined to be "5 seconds" by the data particle size and the offset. Instead of this, even if the value for determining the service data series value is determined by registering the range for extracting the value for determining the service data series value in the service data series explanation information management table 126. good.

After the execution of step S42, the service data generation unit 113 refers to the value extracted in step S42 and the service data series value determination rule, and determines the service data series value (S43). For example, when determining the value of one series point, the data series value is extracted in the range of "2017-01-01 00:00:00" to "2017-01-01 00:00:04". When "linear interpolation" is set in the service data series value determination rule, the service data generation unit 113 determines the value based on the time of the series point by performing linear approximation using the extracted value. ..

By executing steps S42 and S43, the service data generation unit 113 can correct the time recorded in the site data. After the execution of step S43, the service data generation unit 113 returns to the process shown in FIG. 10 and shifts to the service data series shortage value determination flow (S27).

FIG. 13 is a flowchart illustrating a service data series shortage value determination flow (S27) executed in the third stage of the above-mentioned three-stage determination flow.

The service data generation unit 113 confirms whether or not a rule for determining a shortage value of the service data series is set (S51). If the rule for determining the shortage value of the service data series is not set (S51: NO), the process returns to the data generation process of FIG.

When the rule for determining the shortage value of the service data series is set (S51: YES), the service data generation unit 113 confirms whether or not the values exist at all the series points of the service data (S52). When the values are present in all the sequence points (S52: YES), the service data generation unit 113 returns to the process of FIG.

On the other hand, when there is a series point where the value does not exist (S52: NO), the service data generation unit 113 refers to the value existing in the data series of the service data and the service data series shortage value determination rule. Create a series point value for which there is no service data value (S53). Then, the service data generation unit 113 returns to the process of FIG.

FIG. 14 is a flowchart illustrating a processing flow when the user registers the service table explanatory information 125 using the explanatory information setting terminal 21.

When the management screen generation unit 123 of the data providing device 10 receives the request of the service table explanation information registration screen for registering the explanation information from the explanation information setting terminal 21 via the explanation information access interface 121, this process starts. Will be done. The management screen generation unit 123 acquires the list of explanatory information held in the service table explanatory information management table 125 by requesting the explanatory information management unit 124 for a list of the service table explanatory information (S61).

The management screen generation unit 123 generates a screen G10 for registering the service table explanation information based on the explanation information list acquired in step S61 (S62). The management screen generation unit 123 returns the explanation information registration screen G10 to the explanation information setting terminal 21 via the explanation information access interface 121 (S63).

When the user inputs to the explanatory information registration screen G10 using the explanatory information setting terminal 21, the information input to the screen from the explanatory information setting terminal 21 is transmitted to the data providing device 10. The management screen generation unit 123 detects the input to the screen G10 by the user (S64).

The management screen generation unit 123 confirms whether the screen input is "registration / update confirmation", that is, whether the registration / update confirmation button G101 of FIG. 7 is pressed (S65). When the "Registration / Update Confirmation" button G101 is pressed (S65: YES), the process proceeds to step S73.

On the other hand, when the "Registration / Update Confirmation" button G101 is not pressed (S65: NO), the management screen generation unit 123 determines whether the screen input by the user is "addition / update or deletion" (S65: NO). S66). That is, the management screen generation unit 123 determines whether or not the add / update button G108 or the delete button G111 of FIG. 7 is pressed by the user (S66).

When the screen input by the user is "addition / update or deletion", the management screen generation unit 123 creates a screen G10 in which the list information of the explanation information display unit G109 is updated according to the user's operation, and the explanation information. The updated screen G10 is returned to the setting terminal 21 (S67). Then, the process returns to step S64 and waits for the user's screen input again.

On the other hand, when the screen input by the user is not "add / update or delete" (S66: NO), the management screen generation unit 123 indicates whether the screen input by the user is "edit", that is, the edit of FIG. It is determined whether the button G110 is pressed (S68).

When the screen input by the user is "edit" (S68: YES), the processing flow for registering the service data series explanation information is executed (S69). Then, the process returns to S64 and waits for the user's screen input again. Details of step S69 will be described with reference to FIG.

When the screen input by the user is not "edit" (S68: NO), the management screen generation unit 123 searches various explanatory information management tables 125 and 126 for information related to the input information input by the user (S70). Check if the related information exists (S71). If there is no related information (S71: NO), the process returns to step S64 and waits for the user's screen input. On the other hand, when the related information is found (S71: YES), the screen G10 is updated based on the found information, and the updated screen G10 is returned to the explanation information setting terminal 21 (S72).

An example of steps S70 to S72 will be described. When the input from the user is the service table name selection unit G100 of FIG. 7, the management screen generation unit 123 sets the reference data series name, data granularity, offset, start value, and end value managed in the selected table. Service table Description Obtained from the information management table 125. Then, the management screen generation unit 123 updates the screen G10 so as to be displayed on the input units G103 to G107, then returns to step S64 and waits for the screen input from the user again.

In step S65, when the input from the user is "registration / update confirmation" (S65: YES), the management screen generation unit 123 passes the set of information updated by the user on the screen to the explanation information registration unit 122, and provides a service. Table description The information management table 125 is updated (S73).

FIG. 15 is a flowchart illustrating a processing flow when a user registers service data series explanatory information using the explanatory information setting terminal 21.

When the management screen generation unit 123 of the data providing device 10 receives the request of the service data series explanatory information registration screen G20 for registering the explanatory information from the explanatory information setting terminal 21 via the explanatory information access interface 121, the explanatory information Request the management unit 124 for a list of service data series explanation information (S81). As a result, the management screen generation unit 123 acquires the list of explanatory information held in the service data series explanatory information management table 125 (S81).

The management screen generation unit 123 generates the service data series explanation information registration screen G20 based on the acquired explanation information list (S82). The management screen generation unit 123 returns the explanation information registration screen G20 to the explanation information setting terminal 21 via the explanation information access interface 121 (S83).

When the user inputs to the explanatory information registration screen using the explanatory information setting terminal 21, the screen input information is transmitted from the explanatory information setting terminal 21 to the data providing device 10. As a result, the management screen generation unit 123 detects the screen input by the user (S84).

The management screen generation unit 123 determines whether the screen input is "registration / update confirmation", that is, whether the registration / update confirmation button G201 of FIG. 8 is pressed (S85). In the case of "registration / update confirmation" (S85: YES), the process proceeds to step S91 described later.

When the screen input by the user is not "registration / update confirmation" (S85: NO), the management screen generation unit 123 indicates whether the screen input by the user is "addition / update or deletion", that is, the addition / addition in FIG. It is determined whether either the update button G207 or the delete button G210 is pressed (S86).

When the screen input by the user is "addition / update or deletion" (S86: YES), the management screen generation unit 123 updates the list information of the service data series explanation information display unit G209 according to the user's operation. The screen G20 is created, and the updated screen G20 is returned to the explanation information setting terminal 21 (S87). Then, the management screen generation unit 123 returns to step S84 and waits for the screen input by the user again.

When the screen input is not "addition / update or deletion" (S86: NO), the management screen generation unit 123 searches various explanatory information management tables 125 and 126 for information related to the information input by the user (S88). , Determine if the relevant information exists (S89).

If there is no related information (S89: NO), the management screen generation unit 123 returns to step S84 and waits for the user's screen input. When the related information is found (S89: YES), the management screen generation unit 123 updates the screen G20 based on the found information, and returns the updated screen G20 to the explanatory information setting terminal 21 (S90). ).

An example of steps S88 to S90 will be described. When the user's input is the service data series name selection unit G200 of FIG. 8, the site data name and each determination rule managed in the selected table are acquired from the service data series explanation information management table 126, and the input unit G202 After updating the screen G20 so as to be displayed in ~ G206, the process returns to step S84.

When the user input is "registration / update confirmation" (S85: YES), the management screen generation unit 123 passes the set of information updated by the user on the screen to the explanation information registration unit 122, and the service data series explanation information management table. 126 is updated (S91).

The effect of the data providing method according to this embodiment will be described with reference to FIG. FIG. 16 (1) shows a case (comparative example) to which this embodiment is not applied. FIG. 16 (2) shows a case where this embodiment is applied. The comparative example is an example for explaining the effect obtained by this example in an easy-to-understand manner, and is not disclosed in the prior art.

In FIG. 16 (1), the reference data series is set to "time A", and the service data 41 (1) is generated using the times of the site data 42 (1) to 42 (3). Further, in FIG. 16 (1), the site data 42 (1) to 42 (2) are combined without performing time correction or value correction of the site data. Therefore, the values of the reference data series are different, and service data 41 (1) in which there are insufficient values or irregular values in the data is generated. Such values are not spaced and there are many missing values. The service data 41 (1) may interfere with the use of the service 200.

On the other hand, FIG. 16 (2) to which this embodiment is applied will be described. Also in FIG. 16 (2), the reference data series is defined as "time A". The data providing device 10 generates the service data 41 (2) by executing the processing flow shown in FIGS. 10 to 13 using the site data 42 (1) to 42 (3) and various explanatory information. ..

Various explanatory information used for generating the service data 42 (2) is stored in the various explanatory information management tables 125 and 126 shown in FIGS. 5 and 6. According to the method of this embodiment, the service data 41 (2) can be shaped by absorbing the difference in the characteristics of the site data 42 (1) to 42 (3), which is suitable for use in the service 200. Service data 41 (2) can be efficiently generated. That is, even if the characteristics of the field data such as the time accuracy, the missing value, and the abnormal value are different, and the characteristics of the data required by the service 200 are different, the data providing device 10 according to the present embodiment has them. It is possible to absorb the difference in the characteristics of the data and format the data into the form required by the service 200. Therefore, according to the present embodiment, the man-hours for shaping the site data according to the service 200 can be reduced, the service data can be efficiently generated, and the usability of the user is improved.

The present invention is not limited to the above-described embodiment. A person skilled in the art can make various additions and changes within the scope of the present invention. In the above-described embodiment, the configuration is not limited to the configuration example shown in the accompanying drawings. The configuration and processing method of the embodiment can be appropriately changed within the range of achieving the object of the present invention.

In addition, each component of the present invention can be arbitrarily selected, and an invention having the selected configuration is also included in the present invention. Further, the configurations described in the claims can be combined in addition to the combinations specified in the claims.

1: Data providing device 2: Data processing device 3: On-site equipment 4: On-site 10: Data providing device, 11: Data generation unit, 12: Specification explanation information management unit, 13: Data acquisition unit, 20: Service Terminal, 21: Explanation information setting terminal, 30: Field system, 112: Data generation instruction unit, 113: Service data generation unit, 122: Explanation information registration unit, 123: Management screen generation unit, 124: Explanation information management unit, 125 : Service data explanation information management table, 126: Service data series explanation information management table

Claims (7)

A data providing device that provides data in response to a request from a data processing device.
A data acquisition unit that acquires data from on-site equipment,
Based on the specification explanation information indicating the specifications of the predetermined data used in the data processing device, a predetermined table corresponding to the data processing executed by the data processing device is generated and acquired from the data acquisition unit. Data generation that generates the predetermined data by setting either the data or the data generated based on the data in the predetermined table and provides the generated predetermined data to the data processing apparatus. Department and
It is equipped with an information management unit that manages the specification explanation information.
The information management unit is a data providing device that provides an information registration unit for registering the specification explanation information. The predetermined table
A reference data series, which is a data series that serves as a reference for the predetermined data, and at least one other data series associated with the reference data series are provided, and the other data series includes the reference data series of the reference data series. Data corresponding to each value to have is set,
The data providing device according to claim 1. The data generation unit has a first setting unit that sets a shortage value of data acquired from the field apparatus by the data acquisition unit.
The data providing device according to claim 2. The data generation unit sets the data of the other data series so as to correspond to the respective values of the reference data series with respect to the data for which the shortage value is set by the first setting unit. Have,
The data providing device according to claim 3. The data generation unit has a third setting unit for setting a shortage value that could not be set by the second setting unit.
The data providing device according to claim 4. The data generation unit
A first setting unit that sets a shortage value of data acquired from the field device by the data acquisition unit, and
A second setting unit that sets data of the other data series so as to correspond to each value of the reference data series, and
With at least one of
The data providing device according to claim 2. Before SL information registration unit, the second description information indicating a first registration unit for registering the first description information indicating a configuration of said predetermined table, the contents of the other data sequence included in the predetermined table Including a second registration section for registering
The data providing device according to claim 2.

Images