WO2015029969A1 - Data processing device, and data processing method and program - Google Patents

Abstract

A measured value table design unit (121) which: divides tree structure data into a plurality of subtrees in a manner such that the number of measuring instruments associated with each subtree is equal to or less than a number of table storage instruments, which is the upper limit number of measuring instruments that can store measured values in a measured value table; determines whether the divided subtrees are in an established state; and allocates measured value tables to the subtrees that are in an established state, said measured value tables storing the measured values from the measuring instruments associated with the subtrees. The subtrees that are not in an established state are further divided into a plurality of subtrees.

Description

Data processing apparatus, data processing method, and program

The present invention relates to a technique for managing measurement results of a measuring device (also referred to as a sensor).

In a measurement data management device that aggregates measurement data measured by a measurement device from various viewpoints such as the arrangement, affiliation, or usage of the measurement device, the actual measurement point where the measurement device is actually installed is actually A method of providing a virtual measurement point where no measuring device is installed is disclosed (for example, Patent Document 1).
The actual measurement point corresponds to measurement data measured by an actual measurement device, and the virtual measurement point corresponds to fictitious measurement data calculated using the sum or apportionment of the measurement data of the actual measurement point.
In addition, a method for obtaining measurement data of virtual measurement points by distributing the measurement data of actual measurement points according to management categories such as time lapse units, building units, location units, measurement type units, and usage units has been released. (For example, Patent Document 2).

Japanese Patent No. 4640212 JP 2006-185318 A

The measurement data has a characteristic that it arrives continuously with the passage of time, and the measurement data measured in the same time zone are often closely related.
Therefore, when storing measurement data in a database table, it is convenient to use it by associating individual measurement values with each column of the table and storing the measurement values at the same measurement time in one record.

On the other hand, in response to technical backgrounds such as high performance and low price of measurement equipment, expansion of network bandwidth, and reduction of storage price per unit capacity in recent years, a shorter collection cycle from a larger number of measurement equipment. It is now possible to collect measurement data and store / save it.
In addition, there is a growing need for users of measurement data to utilize such measurement data.
For example, there are needs such as collecting and analyzing power consumption and determining measures to enhance the effects of energy saving measures, and collecting and analyzing machine and equipment status data to prevent machine and equipment failures before they occur. is there.
Against the background described above, the measurement data managed by one system of the measurement data management apparatus is increasing.

In a general database management system, the maximum number of columns that can be defined per table is about 1,000.
For this reason, when managing measurement data of a type far exceeding the upper limit of the number of columns generated from the measuring device, it is necessary to divide the table in the column direction and store the measurement data in a plurality of tables.
When measurement data is distributed to multiple tables, the measurement data may be read from multiple tables when performing aggregation using virtual measurement points or analysis using multiple types of measurement data. To do.
For this reason, there is a problem that the time required for aggregation / analysis increases as compared with the case of reading measurement data from a single table.
Basically, this time increases as the number of tables from which measurement data is read increases.
In addition, when measuring data is read from a plurality of tables, post-processing such as additional tabulation processing may be necessary on the user's application side, and there is a problem that the development load of the application increases.

The main object of the present invention is to solve the above-described problems, and when the measurement values are distributed in a plurality of tables and stored in a plurality of tables, the aggregation and analysis can be efficiently performed. Thus, the main purpose is to determine a table for storing measurement values.

The data processing apparatus according to the present invention
A data processing device for managing tree structure data associated with a measuring device,
The tree structure data is converted into a plurality of subtree data so that the number of measuring devices associated with each subtree data is equal to or less than the number of table storage devices that is the upper limit number of measuring devices that can store measurement values in the measurement value table. A data dividing unit that divides the data into
A state determination unit that determines whether the subtree data divided by the data division unit is in a definite state;
A table allocating unit for allocating a measurement value table for storing measurement values from a measuring device associated with the partial tree data, with respect to the partial tree data determined to be in a finalized state by the state determination unit; ,
The state determination unit
A measuring device associated with one subtree data is not associated with any other subtree data, and the number of measuring devices associated with the one subtree data is equal to or less than the number of table storage devices. Is determined that the one subtree data is in the first definite state,
At least one measuring device among measuring devices associated with one subtree data is duplicated and associated with other subtree data, and the number of measuring devices associated with the one subtree data When the total number obtained by eliminating duplication with the number of measuring devices associated with the other subtree data is equal to or less than the number of table storage devices, the one subtree data and the other subtree data are It is determined to be in the second final state,
The partial tree data determined not to be in either the first finalized state or the second finalized state is further divided into a plurality of partial tree data by the data dividing unit.

According to the present invention, since the subtree data is divided while determining whether the subtree data is in the first definite state or the second definite state, the measurement values used for aggregation and analysis can be simultaneously performed. As long as they can be associated with the same measurement value table, it is possible to efficiently perform aggregation and analysis.

FIG. 3 is a diagram illustrating a configuration example of a measurement data management device according to the first embodiment. 1 is a diagram illustrating a configuration example of a measurement data management system according to Embodiment 1. FIG. 1 is a diagram illustrating a configuration example of a measurement data management system according to Embodiment 1. FIG. FIG. 4 is a diagram illustrating a format example of measurement data according to the first embodiment. FIG. 4 is a diagram illustrating an example of a measurement value table according to the first embodiment. FIG. 4 is a diagram showing an example of configuration information according to Embodiment 1. FIG. 4 is a diagram showing an example of configuration information according to Embodiment 1. FIG. 4 is a diagram showing an example of configuration information according to Embodiment 1. The figure which shows the relationship between the structure information tree which concerns on Embodiment 1, virtual measurement point information, a real measurement point, and a measured value table. FIG. 3 is a diagram illustrating an example of a configuration information table according to the first embodiment. The figure which shows the example of the group name table and level name table which concern on Embodiment 1. FIG. FIG. 4 shows an example of a virtual measurement point definition table according to the first embodiment. FIG. 4 is a diagram showing an example of measurement value table design information according to the first embodiment. FIG. 5 is a diagram showing an example of an alternative measurement point definition table according to the first embodiment. FIG. 4 is a flowchart showing a procedure for generating measurement value table design information according to the first embodiment. FIG. 4 is a flowchart showing a procedure for generating measurement value table design information according to the first embodiment. FIG. 4 is a diagram showing an example of a measurement point management information table according to the first embodiment. FIG. 6 is a diagram showing an example of a partial configuration information tree management table according to the first embodiment. The flowchart figure which shows the procedure which divides | segments the partial structure information tree which concerns on Embodiment 1 into a partial tree. The figure which shows the operation preparation stage of the measurement data management apparatus which concerns on Embodiment 1. FIG. The figure which shows the collection and accumulation | storage stage of the measurement data of the measurement data management apparatus which concerns on Embodiment 1. FIG. The figure which shows the read-out and totaling step of measurement data of the measurement data management apparatus which concerns on Embodiment 1. FIG. FIG. 6 shows an example of a first confirmed state according to the first embodiment. FIG. 6 is a diagram showing an example of a second confirmed state according to the first embodiment. FIG. 10 shows an example of a third finalized state according to the first embodiment. FIG. 3 is a diagram illustrating an example of a configuration information tree according to the first embodiment. FIG. 3 is a diagram illustrating an example of a configuration information table according to the first embodiment. FIG. 3 is a diagram illustrating an example of a configuration information tree according to the first embodiment. FIG. 3 is a diagram illustrating an example of a configuration information table according to the first embodiment. The figure which shows the relationship between the structure information tree which concerns on Embodiment 1, and an actual measurement point. FIG. 4 shows an example of a virtual measurement point definition table according to the first embodiment. FIG. 4 shows an example of a virtual measurement point definition table according to the first embodiment. FIG. 4 is a diagram illustrating an example of a temporary configuration information table according to the first embodiment. FIG. 4 is a diagram illustrating an example of a temporary configuration information table according to the first embodiment. FIG. 4 is a diagram showing an example of a measurement point management information table according to the first embodiment. FIG. 5 is a diagram showing an example of a partial configuration information tree table according to the first embodiment. The figure which shows the example of an update of the temporary structure information table which concerns on Embodiment 1. FIG. The figure which shows the example of an update of the measurement point management information table which concerns on Embodiment 1. FIG. The figure which shows the example of an update of the partial structure information tree table which concerns on Embodiment 1. FIG. The figure which shows the example of an update of the temporary structure information table which concerns on Embodiment 1. FIG. The figure which shows the example of an update of the measurement point management information table which concerns on Embodiment 1. FIG. The figure which shows the example of an update of the partial structure information tree table which concerns on Embodiment 1. FIG. The figure which shows the example of an update of the partial structure information tree table which concerns on Embodiment 1. FIG. FIG. 3 is a diagram illustrating a hardware configuration example of a measurement data management device according to the first embodiment. The figure which shows the example of an update of the virtual measurement point definition table which concerns on Embodiment 1. FIG. The figure which shows the example of an update of the virtual measurement point definition table which concerns on Embodiment 1. FIG. The figure which shows the example of an update of the measurement point management information table which concerns on Embodiment 1. FIG. FIG. 6 is a diagram showing a procedure for deriving an alternative point measurement point definition according to the first embodiment.

Embodiment 1 FIG.
In the present embodiment, when the number of measurement devices is large and the number of types of measurement data is much larger than the maximum number of columns in one table of the database management system, the measurement data used for simultaneous counting and analysis is as much as possible. A measurement data management apparatus that can suppress an increase in execution time at the time of execution of aggregation and execution time at the time of execution of analysis and reduce a user's application development load by associating with the above table will be described.

The measurement data management apparatus 100 according to the present embodiment has a configuration illustrated in FIG.
Details of each component of the measurement data management apparatus 100 shown in FIG. 1 will be described later.
The measurement data management device 100 corresponds to an example of a data processing device.

Further, as shown in FIGS. 2 and 3, the measurement data management apparatus 100 according to the present embodiment constitutes a measurement data management system 200 together with the measurement device 201, the base apparatus 210, and the operation terminal 220.
Details of the measuring device 201, the base device 210, and the operation terminal 220 shown in FIGS. 2 and 3 will be described later.

Before describing details of the configuration and operation of the measurement data management apparatus 100 according to the present embodiment, first, an outline of the operation of the measurement data management apparatus will be described.

The operation of the measurement data management apparatus 100 is divided into the following three types of processes.
(1) Preparation for operation (2) Collection and accumulation of measurement data (3) Reading and aggregation of measurement data

(1) Operation preparation In the operation preparation stage, the following processing is executed as preparation prior to the start of actual operation such as collection and accumulation of sensor data, reading and aggregation (FIG. 20).
The user sets the virtual measurement point definition table 141 in the measurement data management device 100 using the virtual measurement point information input / output unit 111 (S11).
The user sets the configuration information table 142 in the measurement data management apparatus 100 using the configuration information input / output unit 112 (S12).
The measurement value table design unit 121 generates measurement value table design information 143 based on the virtual measurement point definition table 141 and the configuration information table 142 (S13).
At this time, the measurement value table design unit 121 describes information on alternative measurement points in the virtual measurement point definition table 141 as necessary.
The alternative measurement points will be described later.
By this step S13, the correspondence between the actual measurement points and the columns of the measurement value table 144 (plurality) is determined.
The measurement value table definition unit 122 generates (CREATE) the measurement value table based on the measurement value table design information 143 (S14).
In the present embodiment, the process of S13 will be mainly described.

(2) Collection and Accumulation of Measurement Data When normal operation is started, measurement data is collected from measurement equipment corresponding to each actual measurement point, and measurement values are accumulated in the measurement value table 144.
In the collection and accumulation of measurement data, specifically, the following processing is executed (FIG. 21).
In each measuring device 201, data is measured repeatedly (in many cases periodically) (S21).
The measurement data is collected by the measurement data management device 100 via the base device 210.
The collected measurement data is written in the measurement data collection / storage unit 131 of the measurement data management apparatus 100 (S22).
Based on the measurement value table design information 143, the measurement data collection / accumulation unit 131 determines the measurement value table 144 and the column where the measurement values are stored, and writes the measurement value of the measurement data in the corresponding column (S23).
Further, when an alternative measurement point related to the actual measurement point ID of the measurement data is defined, the measurement data is written in the corresponding column.
The alternative measurement points will be described later.

(3) Reading and totaling of measurement data When normal operation is started and the measurement values of the measurement data are accumulated in the measurement value table 144, the measurement data is read and totaled as necessary, and the measurement data management apparatus 100 Users use measurement data.
Specifically, the following processing is executed in reading and tabulating measurement data (FIG. 22).
The user designates the virtual measurement point name and the measurement time period of the measurement data, and requests the measurement data management device 100 to read the measurement data from the operation terminal 220 (S31).
The virtual measurement data calculation unit 132 acquires a list of actual measurement points for obtaining measurement data desired by the user from the designated virtual measurement point name based on the virtual measurement point definition table 141 (S32).
At this time, if an alternative measurement point is defined for a certain virtual measurement point and the measurement data of the alternative measurement point and other actual measurement points are assigned to the same table, the virtual measurement data calculation unit 132 is used. Reads out the measurement data from the column corresponding to the alternative measurement point (S32).
Then, the virtual measurement data calculation unit 132 outputs the measurement data calculated according to the virtual measurement point definition to the operation terminal 220 (S33).

The measurement value table design unit 121 corresponds to an example of a data division unit, a state determination unit, a table allocation unit, and an alternative measurement point setting unit.
The measurement data collection / storage unit 131 corresponds to an example of an alternative measurement point calculation unit.

Next, (1) Operation preparation (S13 in FIG. 20) will be described in more detail.

The measurement data management apparatus 100 according to the present embodiment manages a configuration information tree 700 and a configuration information tree 710 that are tree structure data as illustrated in FIG.
Further, the measurement data management apparatus 100 manages the measurement value table 144.
In the measurement value table 144, measurement values measured by a plurality of measurement devices 201 are stored.
Each of the configuration information tree 700 and the configuration information tree 710 has a hierarchical structure with a plurality of nodes.
Each node is a unit of measurement value aggregation.
Each node defines a calculation formula for calculation of aggregation, and the calculation formula includes zero or more actual measurement points and zero or more virtual measurement points.
The actual measurement point is an identifier that is directly associated with the measurement value in the measurement value table 144, and the virtual measurement point is an identifier that is directly associated with the actual measurement point or indirectly through another virtual measurement point. .
That is, each node is associated with the measurement device via the actual measurement point and the virtual measurement point.
In FIG. 9, 721, 722, and 723 are virtual measurement points, and 731, 732, and 733 are actual measurement points.
The number of columns in the measurement value table 144, that is, the number of measurement devices that can store measurement values in the measurement value table 144 (the number of table storage devices) is finite, and the number of actual measurement points (that is, the number of measurement devices) is measured. The number of columns in the value table 144 may be exceeded.
When the number of actual measurement points exceeds the number of columns in the measurement value table 144, it is necessary to use a plurality of measurement value tables 144.
The measurement data management apparatus 100 according to the present embodiment determines which measurement value table 144 of the plurality of measurement value tables 144 stores the measurement value.

In the measurement data management apparatus 100 according to the present embodiment, the measurement value table design unit 121 has the number of measurement devices associated with the partial configuration information tree (also referred to as partial tree data or partial tree) in the measurement value table 214. The configuration information tree 700 and the configuration information tree 710 are each divided into a plurality of partial configuration information trees so that the number of columns is less than or equal to the number of columns.
For example, for the configuration information tree 700, the measurement value table design unit 121 includes a partial configuration information tree having only the node 701, a partial configuration information tree having the node 702a as a root node, and a partial configuration information tree having 702b as a root node. Divide into
If the number of measuring devices associated with the partial configuration information tree of the node 702a is less than or equal to the number of columns in the measurement value table 214, the partial configuration information tree is not further divided.
On the other hand, when the number of measuring devices associated with the partial configuration information tree of the node 702b exceeds the number of columns of the measurement value table 214, the partial configuration information tree is, for example, a partial tree of only the node 702b, The node is divided into a partial configuration information tree having the node 703a as a root node and a partial configuration information tree having the node 703b as a root node.
When the number of measurement devices associated with all the partial configuration information trees is equal to or less than the number of columns in the measurement value table 214, the measurement value table design unit 121 determines whether or not each partial configuration information tree is in a definite state. to decide.
Then, the measurement value table design unit 121 assigns a measurement value table that stores measurement values from the measuring device associated with the partial configuration information tree to the partial configuration information tree in the finalized state.
For a partial configuration information tree that is not in a fixed state, the measurement value table design unit 121 further divides the partial configuration information tree into a plurality of partial configuration information trees.

In the present embodiment, there are two types of confirmed states.
The measurement value table design unit 121 measures the number of measurement devices associated with one partial tree, while the measurement device associated with one partial tree is not associated with any other partial tree. When the number of columns of the value table is less than or equal to, it is determined that the one subtree is in the first definite state.
The measurement value table design unit 121 also associates at least one measurement device among the measurement devices associated with one subtree in duplicate with each other, and is associated with the one subtree. When the total number (unique total number) obtained by removing the overlap between the number of measuring devices and the number of measuring devices associated with the other subtree is equal to or less than the number of columns in the measurement value table, It is determined that one subtree and the other subtree are in the second definite state.

The subtrees 1101 and 1102 in FIG. 23 are in the first finalized state.
The actual measurement points 1 to 5 related to the subtree 1101 are related only to the subtree 1101 and the number of columns in the measurement value table is 8 or less.
Similarly, the actual measurement points 6 to 11 related to the subtree 1102 are related only to the subtree 1102 and the number of columns in the measurement value table is 8 or less.
Therefore, the subtrees 1101 and 1102 in FIG. 23 are in the first confirmed state.

The subtrees 1111 and 1112 in FIG. 24 are in the second finalized state.
The actual measurement points associated with the subtree 1111 are 1 to 6, and the actual measurement points associated with the subtree 1112 are 2 to 7.
Since the actual measurement points 2 to 6 are associated with both the subtree 1111 and the subtree 1112, when this overlap is removed and counted, the number of actual measurement points associated with the subtree 1111 and the subtree 1112 are counted. The total number of related actual measurement points is seven, that is, actual measurement points 1 to 7.
The seven actual measurement points are 8 or less in the number of columns in the measurement value table.
For this reason, the subtrees 1111 and 1112 in FIG. 24 are in the second finalized state.

Further, the measurement value table design unit 121 according to the present embodiment (when two or more actual measurement points are included) in the calculation formula of the root node (node R in FIG. 23) includes a measurement point other than one actual measurement point. Is included, when a combination of a real measurement point and a virtual measurement point is included, or when only a virtual measurement point is included), an alternative measurement point is associated with the root node.
The alternative measurement point is an identifier indicating that it is necessary to perform a calculation for counting of measurement values in advance before receiving a counting instruction from the user.
Measurement is also performed when a virtual measurement point is included in the calculation formula of the root node (node R in FIG. 23) (when a combination of an actual measurement point and a virtual measurement point is included, only a virtual measurement point is included). The value table design unit 121 uses the actual measurement point to which the virtual measurement point is directly or indirectly related, and includes only the actual measurement point, and obtains the same calculation result as the calculation formula defined in the root node. The alternative calculation formula is generated and the alternative calculation formula is associated with the alternative measurement point.
Then, the measurement data collection and accumulation unit 131 pre-calculates a measurement value for the root node associated with the alternative measurement point before receiving an aggregation instruction for the root node. Associating with an alternative measurement point.
By doing in this way, since the total value has been calculated at the time when the total instruction for the root node is received from the user, the total value can be presented to the user without delay.

Based on the above description of the outline, details of the configuration and operation of the measurement data management apparatus 100 according to the present embodiment will be described.

FIG. 1 is a functional configuration diagram of a measurement data management apparatus 100 according to the first embodiment.
A functional configuration of the measurement data management apparatus 100 according to Embodiment 1 will be described with reference to FIG.

The measurement data management device 100 is a computer device that manages various measurement data.
The measurement data management apparatus 100 generally includes a virtual measurement point management unit 110, a measurement value table management unit 120, a measurement data management unit 130, and a data storage unit 140.

The virtual measurement point management unit 110 includes a virtual measurement point information input / output unit 111 and a configuration information input / output unit 112.
The virtual measurement point information input / output unit 111 receives input of virtual measurement point information from the user, and stores the virtual measurement point information in the virtual measurement point definition table 141.
The configuration information input / output unit 112 receives input of configuration information from the user and stores the configuration information in the configuration information table 142 of the data storage unit 140.
Further, the virtual measurement point information input / output unit 111 reads virtual measurement point information from the virtual measurement point definition table 141 in accordance with a request from the user, and outputs the read virtual measurement point information.
Further, the configuration information input / output unit 112 reads the configuration information from the configuration information table 142 in accordance with a request from the user, and outputs the read configuration information.
The virtual measurement point information, the configuration information, the virtual measurement point definition table 141, and the configuration information table 142 will be described later.

The measurement value table management unit 120 includes a measurement value table design unit 121 and a measurement value table definition unit 122.
The measurement value table design unit 121 generates design information of the measurement value table 144 based on information recorded in the virtual measurement point definition table 141 and the configuration information table 142, and the generated design information is used as measurement value table design information 143. Record.
Further, the measurement value table definition unit 122 actually generates the measurement value table 144 based on the measurement value table design information 143.

The measurement data management unit 130 includes a measurement data collection / storage unit 131, a virtual measurement data calculation unit 132, and a measurement data output unit 133.
The measurement data collection / accumulation unit 131 accepts input of measurement data collected from various measurement devices and stores it in the measurement value table 144.
The virtual measurement data calculation unit 132 calculates the measurement data of the virtual measurement point based on the virtual measurement point definition in the virtual measurement point definition table 141.
The measurement data output unit 133 reads measurement data from the measurement value table 144 in accordance with a measurement data read request from the user, such as aggregation, and outputs the read measurement data to the user.

The data storage unit 140 stores various data such as a virtual measurement point definition table 141, a configuration information table 142, a measurement value table design information 143, and a measurement value table 144.

Each functional unit of the measurement data management device 100 may be realized on a single computer device, or may be realized in a distributed manner on a plurality of computer devices connected via a network.

2 and 3 are diagrams illustrating a configuration example of the measurement data management system 200 according to the first embodiment.
A configuration example of the measurement data management system 200 according to Embodiment 1 will be described with reference to FIGS. 2 and 3.

In addition to the measurement data management apparatus 100, the measurement data management system 200 shown in FIG. 2 includes one or more base apparatuses 210 and one or more operation terminals 220 connected to the measurement data management apparatus 100 via a network.
However, when the measurement data management apparatus 100 includes the function (application execution unit 221) of the operation terminal 220, the measurement data management system 200 may not include the operation terminal 220.

The base device 210 is a computer or communication device that transmits measurement data including measurement values (eg, power consumption, voltage, water consumption, temperature, etc.) to the measurement data management device 100.
The base device 210 includes a measurement data reception unit 211, a measurement data transmission unit 212, and a base device storage unit 219.
The measurement data receiving unit 211 receives measurement data including measurement values from each measurement device 201 (for example, a distribution board, a voltmeter, a water meter, a thermometer, etc.) that measures the measurement values.
The measurement data transmission unit 212 transmits the measurement data received by the measurement data reception unit 211 to the measurement data management device 100.
The base device storage unit 219 stores data used by the base device 210 such as measurement data received by the measurement data reception unit 211.

The operation terminal 220 is an apparatus (computer) that executes an application program (hereinafter referred to as an application) for performing processing requested by a user, such as measurement value aggregation processing.
The operation terminal 220 includes an application execution unit 221 that executes an application, and an operation terminal storage unit 229 that stores data used by the operation terminal 220.
For example, the application execution unit 221 of the operation terminal 220 operates as follows by executing the application.
The application execution unit 221 requests a measurement value from the measurement data management device 100, acquires the measurement value from the measurement data management device 100, and executes a totaling process regarding the acquired measurement value.

The measurement data collection and accumulation unit 131 (see FIG. 1) of the measurement data management device 100 collects measurement data including measurement values from each base device 210 connected to the measurement data management device 100, and uses the collected measurement data as measurement values. Store in table 144.

The measurement data management system 200 illustrated in FIG. 2 is configured in a star shape in which each base device 210 is connected to the measurement data management device 100. However, in the measurement data management system 200, as shown in FIG. 3, the measurement data management device 100 and each site device 210 are connected in a tree configuration in which the site devices 210 are hierarchically connected, or in other connection forms. You may be the structure which carried out.
In the measurement data management system 200 shown in FIG. 3, the base device 210A collects measurement data from the lower base devices 210B and 210C connected via the network, and transmits the collected measurement data to the measurement data management device 100. .

FIG. 4 is a diagram showing a basic structure of measurement data according to the present embodiment.
The measurement data 400 of the first embodiment includes at least an actual measurement point ID 401, a measurement time 402, and a measurement value 403.
The actual measurement point ID 401 is an identifier for uniquely identifying the measurement device 201 or the location where the measurement device 201 is installed.
Hereinafter, the measurement device 201 or a place where the measurement device 201 is set is referred to as an “actual measurement point”.
Further, the actual measurement point ID is expressed in the format of “$ x”.
Here, “x” is an arbitrary integer value.
The measurement time 402 indicates the date and time when the measurement value was measured.
The measurement time 402 is set by each measuring device 201 and each base device 210.
A measured value 403 indicates a measured value measured by the measuring device 201.

FIG. 5 is a diagram showing the measurement value table 144 in the first embodiment.
Each record (row) of the measurement value table 144 includes a row number 501, a measurement time 502, and a plurality of measurement values 503A to 503E measured at the same time.
The line number 501 is a number for identifying a measured value measured at the same time.
The measurement time 502 corresponds to the measurement time 402, but may include some errors.
There may be an error in the measurement time 402 due to a clock deviation of each measuring device 201 or base device 210.
In that case, it is necessary to round the measurement time 402 within the allowable error range and use the same measurement time 502 as measurement data.
For example, an allowable error is set to 100 milliseconds in advance, and a measurement time 402 from “2013/4/1 18: 00: 00.000” to “2013/4/1 18: 00: 00.099” is set. A plurality of measurement data included in the same record as measurement data with a measurement time 502 of “2013/4/1 18: 00: 0.0000”.
Note that, in this embodiment, the rounding method of the error at the measurement time 402 is not an essential problem, and the details are omitted.
The measured value 403 is stored in any of the measured values 503.
The corresponding relationship is determined based on measurement value table design information 143 described later.

In the present embodiment, in order to represent the configuration of the target object for which virtual measurement points are set, it is assumed that the configuration information has a hierarchical structure.
This hierarchical structure can be expressed as a tree structure as shown in FIG. 6, for example, and information having such a hierarchical structure is referred to as a configuration information tree here.
This hierarchical relationship is also called a parent-child relationship or a hierarchical relationship.
The configuration information tree has a plurality of types (viewpoints) as shown in the examples of FIGS.

FIG. 9 is a diagram for explaining the relationship among the configuration information trees 700 and 710, the virtual measurement point information 720, the actual measurement point information 730, and the measurement value 503 stored in the measurement value table 144.
The configuration information has a plurality of configuration information trees such as configuration information trees 700 and 710.
The configuration information tree is a tree structure composed of nodes called configuration information nodes.
The configuration information node includes normal nodes 702 and 703 having a parent node and a child node, a root node 701 having no parent node, and leaf nodes 704 and 711 having no child node.
Each configuration information node is associated with one virtual measurement point (for example, 722) in the virtual measurement point information 720.
A plurality of configuration information nodes, such as configuration information nodes 704 and 711, may point to one virtual measurement point 723.

The virtual measurement points included in the virtual measurement point information 720 are associated with one or more actual measurement points (eg, 731) included in the one or more actual measurement point information 730, or one or more virtual measurement points.
For example, the virtual measurement point 722 is associated with two actual measurement points 731 and 732.
In addition, the virtual measurement point 721 may be associated with only the virtual measurement point (here, the virtual measurement point 722), or the virtual measurement point 723 may be associated with both the actual measurement point 733 and the virtual measurement point. In some cases.
Thus, the virtual measurement point is an identifier that is directly associated with the actual measurement point or indirectly through another virtual measurement point.

Furthermore, the actual measurement points 731 included in the actual measurement point information 730 are associated with one or more columns of measurement values 503 in the measurement value table 144.
The actual measurement point is thus an identifier that is directly associated with the measurement value of the measurement device.

An example of the configuration information tree is shown using FIG.
The configuration information tree is composed of nodes (rounded rectangles in FIG. 6) that represent the components of the target for which virtual measurement points are provided, and edges (lines connecting the nodes) that represent the hierarchical relationship between the components. It is a tree structure provided with.
A node (for example, a “company” node in FIG. 6) located at the top of the tree structure is a root node, and is the highest parent node.
Also, a node located at the end of the tree structure (for example, “one-piece” node in FIG. 6) is a leaf node and is the lowest child node.

FIG. 6 is a configuration information tree representing the configuration of an “organization” that is a target for providing virtual measurement points.
A “company” node 601 represents the entire company.
The “company” is composed of a plurality of “departments” such as “management department” 602, “○ business department” 603, and “△ business department” 604.
The management department 602 includes a plurality of “departments” such as a “personnel department” 605, a “general affairs department” 606, and an “accounting department” 607.
The personnel department 605 includes a plurality of “sections” such as a “personnel section” 608 and a “training section” 609.
Each node “company” 601, “management department” 602, “HR department” 605, “HR section” 608, etc. are examples of virtual measurement points.

FIG. 7 is an example of a configuration information tree representing a configuration of “arrangement” that is a target for providing virtual measurement points.

FIG. 8 is an example of a configuration information tree representing the configuration of a “device” that is a target for providing virtual measurement points.

10 and 11 are diagrams illustrating the configuration information table 142 according to the first embodiment.
The configuration information table 142 is an example of data indicating configuration information representing an object to be provided with virtual measurement points.
The configuration information table 142 shown in FIGS. 10 and 11 includes configuration information related to the configuration information trees shown in FIGS.

The configuration information table 142 includes a record in which “node ID”, “parent ID”, “group ID”, “level”, “virtual measurement point ID”, and “node name” are associated with each other.
“Node ID” indicates an identifier for identifying a configuration information node.
“Parent ID” indicates an identifier for identifying a parent node having a parent-child relationship with the configuration information node.
When the “parent ID” is “null”, the node means a root node.
“Group ID” indicates an identifier for identifying a configuration information tree.
“Level” indicates the depth (level) of the hierarchy in which the configuration information node is located.
The level of the root node is set to “1”, and the numerical value increases by 1 every time one level is lowered toward the lower level.
“Virtual measurement point ID” indicates an identifier for identifying a virtual measurement point associated with the configuration information node.
Hereinafter, the virtual measurement point ID is described as “#x”.
Here, “x” is an arbitrary integer value.
“Node name” indicates a node name representing the contents of the configuration information node.

For example, the node ID of the “company” node shown in FIG. 6 is “1”, the group ID is “1”, the level is “1”, and the virtual measurement point ID is “# 1”.
The node ID of the “management department” node is “2”, the parent ID is “1” (that is, “company” node), the group ID is “1”, and the level is “2”. The virtual measurement point ID is “# 2”.

The configuration information table 142 is associated with a group name table 142A that defines group names that represent the contents of the configuration information tree, and a level name table 142B that defines level names that represent the contents of each hierarchy of the configuration information tree ( Both are FIG. 11).

The group name table 142A includes a record in which “group ID” and “group name” are associated with each other.
For example, the configuration information tree shown in FIG. 6 is identified by the group ID “1” and represents the “organization” in the company.
Further, the tree structure shown in FIG. 7 is identified by the group ID “2” and represents “placement (location)” in the company.

The level name table 142B includes a record in which “group ID”, “level”, and “level name” are associated with each other.
For example, the level “1” hierarchy in the tree structure shown in FIG. 6 represents the entire “company”, and the level “2” hierarchy represents the “department” in the company.
Further, the level “1” hierarchy in the tree structure shown in FIG. 7 represents the entire “location”, the level “2” hierarchy represents the “district” where the company office is located, and the level “3” The hierarchy represents the “office” in the company.

FIG. 12 is a diagram showing the virtual measurement point definition table 141 in the first embodiment.
The virtual measurement point definition table 141 is an example of data in which virtual measurement points are defined in association with actual measurement points.
The virtual measurement point definition table 141 includes a record in which “virtual measurement point ID” 901, “virtual measurement point name” 902, “virtual measurement point definition” 903, and “alternative measurement point flag” 904 are associated with each other.
“Virtual measurement point ID” 901 indicates an identifier for identifying a virtual measurement point.
The “virtual measurement point ID” 901 corresponds to the virtual measurement point ID 805 in the configuration information table 142.
A “virtual measurement point name” 902 indicates a virtual measurement point name representing the contents of the virtual measurement point.
The virtual measurement point name may not match the node name.
A “virtual measurement point definition” 903 indicates the definition of a virtual measurement point in association with an actual measurement point or another virtual measurement point.
An “alternative measurement point flag” 904 indicates a flag as to whether or not the virtual measurement point definition includes an alternative measurement point.

For example, the virtual measurement point “# 1” is associated with “company-wide power” which means power consumption of the entire company.
In particular, in the case of a large-scale organization such as the entire company, there is no measuring device for directly measuring the power consumption, and “company-wide power” is a virtual measuring point that is not actually provided.
Therefore, the power consumption of the virtual measurement point “# 1” is the power consumption of the virtual measurement point “# 2” (management department power) of the lower organization, the power consumption of “# 10” (○ business department power), and “# It is equal to the sum of the power consumption of 20 ”(△ business sector power).
That is, the virtual measurement point “# 1” is defined by the definition formula “# 2 + # 10 + # 20”.

The virtual measurement point “# 201” is associated with “Tokyo first building substation equipment” that controls the power consumption of the entire building “Tokyo first building”.
The power consumption at the virtual measurement point “# 201” is equal to the power consumption measured at the actual measurement point “$ 1” representing the substation facility in the first building in Tokyo.

Here, in the virtual measurement point definition of the virtual measurement point “# 1”, an alternative measurement point “% 1” is defined in addition to the definition formula “# 2 + # 10 + # 20”.
The alternative measurement point is a measurement point defined in the measurement value table 144 in addition to the original virtual measurement point definition formula or the actual measurement point, and a column for reading the measurement value of the virtual measurement point.
That is, when an alternative measurement point is defined, the measurement value can be read directly from the corresponding column of the measurement value table 144 as with the actual measurement point.
Whether or not an alternative measurement point is defined in the virtual measurement point definition is also set in the alternative measurement point flag 904.
Details of the alternative measurement points will be described later.
Hereinafter, the alternative measurement point ID that is the identifier of the alternative measurement point is referred to as “% x”.
Here, “x” is an arbitrary integer value.
In FIG. 12, alternative measurement points “% 1”, “% 2”, “% 3”, and “% 4” are described, but the alternative measurement points are measured value table design in S13 (FIG. 20) in the operation stage. Since the unit 121 sets, the alternative measurement points “% 1”, “% 2”, “% 3”, and “% 4” are described in the measurement value table 144 after the process of S13 is performed.

FIG. 13 is a diagram showing measurement value table design information 143 in the first embodiment.
The measurement value table design information 143 is an example of data defining a correspondence relationship between an actual measurement point or an alternative measurement point and the measurement value table 144.
The measurement value table design information 143 includes a record in which “measurement point ID” 1001, “DB server name” 1002, “database name” 1003, “table name” 1004, “column name” 1005, and “data type” 1006 are associated with each other. Is provided.
“Measurement point ID” 1001 indicates an actual measurement point ID or an alternative measurement point ID.
“DB server name” 1002 indicates a server name in which the database management system in which the measurement value table 144 is defined exists.
“Database name” 1003 indicates a database name in which the measurement value table 144 is defined.
“Table name” 1004 indicates the actual table name of the measurement value table 144.
Note that “DB server name” 1002, “database name” 1003, and “table name” 1004 are examples, and information that can uniquely identify the table of the measurement value table 144 corresponding to the actual measurement point or the alternative measurement point is set. It only has to be.
“Column name” 1005 indicates a column name on the measurement value table 144 in which measurement values of actual measurement points or alternative measurement points are stored.
“Data type” 1006 indicates the data type of the measurement value.

FIG. 14 is a diagram showing an alternative measurement point definition table 143A attached to the measurement value table design information 143 in the first embodiment.
The alternative measurement point definition table 143A includes a record in which “alternative measurement point ID” 1011 and “alternative measurement point definition” 1012 are associated with each other.
“Alternative measurement point ID” 1011 indicates an alternative measurement point ID.
“Alternative measurement point definition” 1012 indicates an alternative measurement point definition for calculating measurement data of an alternative measurement point.
The alternative measurement point definition is composed of measurement data of a single actual measurement point, or an arithmetic expression of measurement data of the actual measurement point and the alternative measurement point.
Details of the alternative measurement point definition will be described later.

When there are a large number of measuring devices used there, such as a large building or organization, the number of actual measurement points associated with one configuration information tree is the number of columns in one table of the measurement value table 144. May be much more than the upper limit.
In that case, a measure can be considered in which the table is divided in the column direction and the measurement data of the actual measurement points are distributed and managed in a plurality of tables.
At this time, as a method of storing which measurement data of which actual measurement point is stored in which table, a method of focusing on a certain configuration information tree and dividing the table in units of the subtrees can be considered.
For example, paying attention to the configuration information of “placement”, the configuration information tree is divided into subtrees for each “establishment”, and a table for storing measurement data related to “Tokyo establishment” and “Kanagawa establishment” The table is divided into a table for storing related measurement data and a table for storing measurement data related to “Saitama office”.
In this case, when the range of measurement value aggregation and analysis is within the office, the problem of reduction in efficiency of the aggregation and analysis processing does not occur.
On the other hand, when the aggregation and analysis are performed according to the configuration information other than “arrangement”, the efficiency of the aggregation and analysis processing may decrease.

As shown in FIG. 9, one virtual measurement point or real measurement point may be associated with a plurality of configuration information trees.
In actual cases, most virtual measurement points and actual measurement points may be associated with a plurality of configuration information trees.
Here, if each department belonging to “○ business department” exists in business offices throughout the country, reading of measurement values from a plurality of measurement value tables 144 for aggregation and analysis of measurement data related to “○ business department” Is required.
Further, in the case of a virtual measurement point corresponding to a higher-order node of the configuration information tree, for example, in the case of “company” or “Kanto district” when the measurement value table 144 is divided focusing on the configuration information of the above “placement” When the measurement data is calculated by the virtual measurement point definition formula, it is necessary to always read the measurement values from the plurality of measurement value tables 144.
Such a state in which measurement data necessary for aggregation and analysis is dispersed in a plurality of measurement value tables 144 is referred to as fragmentation of measurement data here.

The measurement value table design unit 121 generates design information of the measurement value table 144 that suppresses such fragmentation of measurement data.

Here, it is assumed that virtual measurement point information and configuration information are created in advance and stored in the virtual measurement point definition table 141 and the configuration information table 142, respectively.
Note that since the alternative measurement points are defined by the measurement value table design unit 121, the alternative measurement points are not defined in the virtual measurement point definition at this time.
Further, it is assumed that “measurement point ID” 1001 and “data type” 1006 of actual measurement points are set in the measurement value table design information 143.

Here, it is defined as follows.
C: Number of columns in which measurement data can be stored in one table of the measurement value table 144 Tree size: Number of all nodes included in the tree Tree size: Unique actual measurement point and alternative measurement associated with the tree Number of points

Based on FIGS. 15 and 16, the operation of the measurement value table design unit 121 in the first embodiment (operation of S13 shown in FIG. 20) will be described.
FIGS. 15 and 16 are flowcharts showing a flow of processing for generating the measurement value table design information 143 in the measurement value table design unit 121 according to the first embodiment.

(Step S1101) The measurement value table design unit 121 generates a temporary configuration information table, which is a copy of the configuration information table 142, in the working storage device.
The measurement value table design unit 121 creates and initializes a measurement point management information table and a partial configuration information tree management table.
These tables may be created in a temporary storage device provided independently in the measurement value table design unit 121, or may be created on a temporary storage device on the measurement data management device 100.

Here, the temporary configuration information table is used to manage the state of the partial configuration information tree.

FIG. 17 is a diagram illustrating an example of the measurement point management information table 1200 generated in step S1101.
The measurement point management information table 1200 includes a record in which “measurement point ID” 1201, “own node ID” 1202, “root node ID” 1203, “column name” 1204, and “alternative measurement point definition” 1205 are associated with each other. .
“Measurement point ID” 1201 indicates an actual measurement point ID or an alternative measurement point ID.
“Own node ID” 1202 indicates the node IDs of all nodes associated with virtual measurement points having a virtual measurement point definition that directly includes the actual measurement point ID specified by the “measurement point ID” 1201.
For example, in the virtual measurement point definition table 141 of FIG. 12, the virtual measurement point definition 903 of the virtual measurement point ID “# 201” is “$ 1”, and directly includes the actual measurement point ID.
In this case, “201” is extracted as the node ID 801 associated with the virtual measurement point ID “# 201” from the configuration information table 142, and is set to “own node ID” 1202.
On the other hand, in the virtual measurement point definition table 141 in FIG. 12, the virtual measurement point definition 903 with the virtual measurement point ID “# 1” is all composed of the calculation formula of the measurement data of the virtual measurement point, and thus directly includes the actual measurement point ID. Absent.
A “root node ID” 1203 in the measurement point management information table 1200 of FIG. 17 indicates the root node ID of the partial configuration information tree associated with the actual measurement point or the alternative measurement point specified by the “measurement point ID” 1201.
When an actual measurement point or an alternative measurement point is associated with a plurality of partial configuration information trees, the node IDs of the root nodes of all the partial configuration information trees associated with the root node ID are set.
If the size of all the related partial configuration information trees is 1 (one node) or is not related to any partial configuration information tree, “null” is set.
A “column name” 1204 indicates a column name on the measurement value table 144 that stores the measurement data specified by the “measurement point ID” 1201.
“Alternative measurement point definition” 1205 indicates a definition formula for calculating measurement data of an alternative measurement point.
The definition formula of the alternative measurement point definition is composed of measurement data of a single actual measurement point, or an arithmetic expression of the measurement data of the actual measurement point and the alternative measurement point.

FIG. 18 is a diagram showing the partial configuration information tree management table 1210 generated in step S1101.
The partial configuration information tree management table 1210 includes “partial configuration information tree ID” 1211, “root node ID” 1212, “partial configuration information tree group ID” 1213, “confirmation flag” 1214, “DB server name” 1215, “database”. A record in which “name” 1216 and “table name” 1217 are associated with each other is provided.
The “partial configuration information tree ID” 1211 indicates an identifier for uniquely identifying the partial configuration information tree.
“Root node ID” 1212 indicates the node ID of the root node of the partial configuration information tree identified by the partial configuration information tree ID.
The “partial configuration information tree group ID” 1213 indicates an identifier for uniquely identifying a set of related partial configuration information trees (partial configuration information tree group).
The same “partial configuration information tree group ID” is set for a plurality of partial configuration information trees determined to be in the second confirmed state.
The “confirmation flag” 1214 indicates whether or not the partial configuration information tree identified by the “partial configuration information tree ID” 1211 is fixed.
“DB server name” 1215, “database name” 1216, and “table name” 1217 indicate the DB server name, database name, and table name of the measurement value table 144, respectively.
This is information for uniquely identifying a table storing measurement data of actual measurement points or alternative measurement points associated with the partial configuration information tree identified by the “partial configuration information tree ID” 1211. This is the same as “DB server name” 1002 and “database name” 1003 in the measurement value table design information 143.

Here, “partial configuration information tree T1 is determined” means that the partial configuration information tree is in the following “first determined state” or “second determined state” as described above. Point to.
A partial configuration information tree that does not correspond to either the “first confirmed state” or the “second confirmed state” is referred to as an “undefined partial configuration information tree”.

(First confirmed state)
It is a partial configuration information tree T1 having an actual size of C or less, and all associated actual measurement points or alternative measurement points are not associated with other partial configuration information trees T2.
In the measurement point management information table 1200, the root node IDs of all the associated actual measurement points or alternative measurement points are only the root node of the partial configuration information tree T1.

(Second final state)
Even if all actual measurement points or alternative measurement points associated with the partial configuration information tree T1 having an actual size of C or less are associated with other partial configuration information trees T2, the partial configuration information trees T1 and T2 The number of unique measurement points (excluding duplicates) associated with is less than or equal to C.
An actual measurement point N1 associated with a partial configuration information tree T1 is also associated with another partial configuration information tree T2, and another actual measurement point N2 associated with the partial configuration information tree T2 is a further portion. If it is related to the configuration information tree T3, the unique number of all actual measurement points or alternative measurement points related to any of the partial configuration information trees T1, T2, T3 is measured, and the number is less than or equal to C If there is, it is the second definite state.

The measurement value table design unit 121 first sets all the actual measurement point IDs one by one in the measurement point ID 1201 of each record in the measurement point management information table 1200.
Next, for each actual measurement point ID, a related configuration information tree is extracted, and the node ID of the root node is set as the root node ID 1203.
Therefore, the measurement value table design unit 121 searches the virtual measurement point definition 903 in the virtual measurement point definition table 141 and extracts all virtual measurement point IDs 901 corresponding to the virtual measurement point definition including the corresponding actual measurement point ID. To do.
Next, all group IDs 803 associated with the virtual measurement point ID are extracted from the configuration information table 142.
Finally, among the node IDs belonging to the extracted group ID, the node ID of the root node is extracted and set in the root node ID 1203 of the measurement point management information table 1200.

In order to know the size of a tree, in the temporary configuration information table, the number of nodes having the node ID as the parent ID may be recursively counted in order from the node corresponding to the root node of the tree.
In order to know the actual size of a tree, the number of times that the root node ID of the tree appears in the root node ID 1203 of the measurement point management information table 1200 may be counted.

Similarly, the measurement value table design unit 121 first defines an identifier = partial configuration information tree ID for uniquely identifying each configuration information tree, and sets partial configuration information of each record in the partial configuration information tree management table 1210. Set to tree ID1211.
The group ID 803 of the configuration information table 142 may be used as the partial configuration information tree ID at this time.

(Step S1102) The measurement value table design unit 121 divides the configuration information tree into partial trees so that the actual sizes of all the partial configuration information trees are C or less.
An example of this step is as follows.
(1) The measurement value table design unit 121 selects one partial configuration information tree T whose actual size exceeds C from all the partial configuration information trees.
(2) The measurement value table design unit 121 divides the selected partial configuration information tree T into a partial tree having a root node and a child node of the root node as a new root node.
Then, the measurement value table design unit 121 updates the measurement point management information table 1200 and the partial configuration information tree management table 1210.
Details of this procedure will be described later.
(3) The measurement value table design unit 121 repeats the operations (1) and (2) until there is no partial configuration information tree whose actual size exceeds C.

(Step S1103) The measurement value table design unit 121 selects the partial configuration information tree T1 having the largest size from the partial configuration information trees that are not fixed.

(Step S1104) The measurement value table design unit 121 makes another undefined partial configuration information tree related to the actual measurement point or the alternative measurement point N1 related to the partial configuration information tree T1 selected in step S1103. The partial configuration information tree T2 having the largest size is selected from among them.

(Step S1105) The measurement value table design unit 121 compares the number of child nodes of the root node among the partial configuration information trees T1 and T2, and selects the partial configuration information tree T ′ having a larger number of child nodes. To do.
Then, the measurement value table design unit 121 divides the partial configuration information tree T ′ into a root node R and a partial configuration information tree whose child node is a new parent.
Here, in the division of the selected partial configuration information tree T ′, the same procedure as (2) of step S1102 is applied.

(Step S1106) The measurement value table design unit 121 checks whether or not the actual measurement point is directly included in the virtual measurement point definition of the root node R in step S1105.
That is, the measurement value table design unit 121 extracts the virtual measurement point ID 805 related to the node ID of the root node R from the configuration information table 142.
Then, the measurement value table design unit 121 extracts the virtual measurement point definition 903 of the virtual measurement point ID from the virtual measurement point definition table 141, and checks whether the actual measurement point is directly included.
If it is included directly as a result of the check (YES), the process proceeds to step S1109.
If not included directly (NO), the process proceeds to step S1107.
“Directly including actual measurement points” refers to a case where the virtual measurement point definition 903 is defined by one actual measurement point.
If the virtual measurement point definition 903 is defined by a plurality of actual measurement points, if it is defined only by virtual measurement points, or if it is defined by a combination of actual measurement points and virtual measurement points, it is included directly No (NO) is determined.

(Step S1107) The measurement value table design unit 121 newly assigns an alternative measurement point ID to the root node R in step S1105 and adds it to the measurement point management information table 1200.
The measurement value table design unit 121 adds a new record to the measurement point management information table 1200, sets an alternative measurement point ID newly assigned as “measurement point ID” 1201 to “own node ID” 1202, and The node ID of the root node R is set in the “root node ID” 1203.
The “column name” 1204 is set later.
In “Alternative measurement point definition” 1205, a definition formula for calculating measurement data of the alternative measurement point is set.

In order to set a definition formula in the “alternative measurement point definition” 1205, the measurement value table design unit 121 uses the virtual measurement point ID associated with the node ID of the root node R as the virtual measurement point ID 805 in the configuration information table 142. And the virtual measurement point definition of the virtual measurement point is extracted from the virtual measurement point definition 903 of the virtual measurement point definition table 141.
Further, the measurement value table design unit 121 recursively expands the definition formula until the virtual measurement point ID is not included in the extracted definition formula of the virtual measurement point definition 903, and displays the expansion result as “alternative measurement”. Point definition "1205 is set.

At this time, the “alternative measurement point definition” 1205 after deployment is very complicated and the measurement data calculation load is high, the measurement data of the alternative measurement point cannot be calculated only from the measurement data at the same measurement time, etc. In some cases, the measurement value table design unit 121 need not define alternative measurement points.

(Step S1108) The measurement value table design unit 121 adds information on alternative measurement points to the virtual measurement point definition table 141.
The measurement value table design unit 121 identifies the virtual measurement point definition 903 related to the node ID of the root node R in the same manner as in the above step S1107, and sets the alternative measurement point ID assigned to the root node R therein. to add.

(Step S1109) The measurement value table design unit 121 adds the root node R to the partial configuration information tree management table as a partial configuration information tree of size 1.
The measurement value table design unit 121 generates a record corresponding to the root node R, newly assigns a partial configuration information tree ID, and sets it to “partial configuration information tree ID” 1211.
Further, the measurement value table design unit 121 sets the node ID of the root node R to “root node ID” 1212.
Furthermore, the measurement value table design unit 121 newly assigns a group ID to the partial configuration information tree, and sets it to “partial configuration information tree group ID” 1213.

(Step S1110) The measurement value table design unit 121 checks the partial configuration information tree management table 1210, and determines whether all the partial configuration information trees have been confirmed (whether the “confirmation flag” 904 is set). To check.
If all the partial configuration information trees have been confirmed (YES when “confirmation flag” 904 is set), the process proceeds to step S1111.
If there is an undefined partial configuration information tree (NO), the process returns to step S1103.

(Step S1111) The measurement value table design unit 121 sets the DB server name 1215, the database name 1216, the table name 1217, and the column name 1204 when all the partial configuration information trees are determined.
First, the measurement value table design unit 121 uses the same “DB server name” 1215 and “database name” for records in which the same “partial configuration information tree group ID” 1213 is set in the partial configuration information tree management table 1210. 1216, “table name” 1217 is set.
The measurement value table design unit 121 has at least one of “DB server name” 1215, “database name” 1216, and “table name” 1217 in a record in which a different “partial configuration information tree group ID” 1213 is set. Set a different value.
Subsequently, the measurement value table design unit 121 extracts the root node ID of the partial configuration information tree belonging to the same partial configuration information tree group from the “root node ID” 1212, and “root node ID” 1203 of the measurement point management information table 1200. A unique “column name” 1204 is assigned to the measurement point for which the root node ID is set.

(Step S1112) The measurement value table design unit 121 updates the measurement value table design information 143 and the alternative measurement point definition table 143A based on the information in the measurement point management information table 1200 and the partial configuration information tree management table 1210.
That is, it sets as follows.
“Measurement point ID” 1201 in the measurement point management information table 1200
→ "Measurement point ID" 1001 of the measurement value table design information 143
“DB server name” 1215 in the partial configuration information tree management table 1210
→ "DB server name" 1002 of the measurement value table design information 143
“Database name” 1216 of the partial configuration information tree management table 1210
→ "Database name" 1003 of the measurement value table design information 143
“Table name” 1217 of the partial configuration information tree management table 1210
→ "Table name" 1004 of the measurement value table design information 143
“Column name” 1204 of the measurement point management information table 1200
→ "Column name" 1005 of the measurement value table design information 143
Alternative measurement point ID in “measurement point ID” 1201 of the measurement point management information table 1200
→ "Alternative measurement point ID" 1011 in the alternative measurement point definition table 143A
“Alternative measurement point definition” 1205 in the measurement point management information table 1200
→ "Alternative measurement point definition" 1012 in the alternative measurement point definition table 143A
Here, the “data type” 1006 of the alternative measurement point in the measurement value table design information 143 can be set based on the “data type” 1006 of the actual measurement point related to the alternative measurement point.

In step S1112, the correspondence between the “measurement point ID” 1001 of the measurement value table design information 143 and the “DB server name” 1215 and “database name” 1216 of the partial configuration information tree management table 1210 is the measurement point management information table. It can be determined by using “root node ID” 1203 of 1200 and “root node ID” 1212 of the partial configuration information tree management table 1210 as keys.

In step S1111, “DB server name” 1215, “database name” 1216, “table name” 1217, and “column name” 1204 are assigned. "Measurement point ID" 1201, "own node ID" 1202, "root node ID" 1203, "alternative measurement point definition" 1205, "partial configuration information tree ID" 1211 of the partial configuration information tree management table 1210, "root" Only the “node ID” 1212, “partial configuration information tree group ID” 1213, “confirmation flag” 1214 are set, and the remaining “DB server name” 1215, “database name” 1216, “table name” 1217, “column name” 1204 may be set by the user.

(Step S1113) The measurement value table design unit 121 records the updated measurement value table design information 143 and the alternative measurement point definition table 143A in the data storage unit 140, and ends.

The larger the size of the partial configuration information tree, the higher the probability that an actual measurement point or an alternative measurement point associated therewith is associated with another partial configuration information tree.
Therefore, in steps S1103 and S1104 described above, the measurement value table design unit 121 preferentially selects and divides a tree having a large partial configuration information tree size.
In steps S1103 and S1104 described above, the partial configuration information tree T may be selected based on the actual tree size instead of the tree size.
Alternatively, the partial configuration information tree having the largest number of child nodes of the root node may be selected.
As the number of child nodes of the root node increases, the number of steps until all partial configuration information trees are determined is reduced because the partial configuration information tree is divided into smaller partial configuration information trees. Can be expected.
Also, a threshold value is set in advance for the size of the tree, the actual size, or the number of child nodes of the root node, and the first partial configuration information tree found in the partial configuration information tree exceeding the threshold is selected. You may do it.
As a result, the effect of reducing the time required for searching for candidates for the partial configuration information tree to be divided can be expected.

In step S1105, the partial configuration information tree may be selected based on the size of the tree or the actual size of the tree instead of the number of children nodes of the root node.
In addition, a threshold value is set in advance for the number of child nodes of the root node, the tree size, or the actual tree size, and the first partial configuration information tree found in the partial configuration information tree exceeding the threshold is selected. You may do it.

FIG. 19 is a flowchart showing a flow of processing for dividing the partial configuration information tree into partial trees in the first embodiment.
That is, the details of the procedure (2) of step S1102 are shown.

(Step S1301) A partial configuration information tree T to be divided is designated.

(Step S1302) The measurement value table design unit 121 extracts all records in which the node ID of the root node R of the partial configuration information tree T is “parent ID” 802 in the temporary configuration information table.
Let Ri be the node of those records.
Then, the measurement value table design unit 121 sets “parent ID” 802 of the corresponding record to “null”.

(Step S1303) The measurement value table design unit 121 extracts a record having the node ID of the root node R of the partial configuration information tree T as the “root node ID” 1203 of the measurement point management information table 1200, and the root node ID. Update. At the same time, the measurement value table design unit 121 updates the “level” 804 of all nodes included in the partial configuration information tree T in the configuration information table 142.

An example of a procedure for updating the “root node ID” 1203 of the measurement point management information table 1200 in step S1303 will be described.
First, the measurement value table design unit 121 selects one of the node IDs of the record of the node Ri extracted in step S1302.
Then, the measurement value table design unit 121 searches the node ID of the child node in the configuration information table 142 in order from the selected node ID, and subtracts 1 from the “level” 804 of the corresponding record. Furthermore, when the measurement value table design unit 121 detects the node ID included in the “own node ID” 1202 of the measurement point management information table 1200, the “root node ID” of the record of the measurement point management information table 1200 is The selected node ID is set instead of the original ID.
The measurement value table design unit 121 repeats this operation for the node IDs of all the records extracted in step S1302.

(Step S1304) The measurement value table design unit 121 adds the information of the partial configuration information tree Ti divided by the operations of steps S1302 to S1303 to the partial configuration information tree management table 1210.
The measurement value table design unit 121 generates a record corresponding to each partial configuration information tree Ti, assigns a new partial configuration information tree ID, and sets it to “partial configuration information tree ID” 1211.
Further, the measurement value table design unit 121 sets the node ID of the root node Ri of the partial configuration information tree Ti to “root node ID” 1212. Furthermore, the measurement value table design unit 121 newly assigns a group ID of the partial configuration information tree and sets it to “partial configuration information tree group ID” 1213.

(Step S1305) The measurement value table design unit 121 checks the confirmed partial configuration information tree, and if there is a confirmed partial configuration information tree, it corresponds to the partial configuration information tree in the partial configuration information tree management table 1210. “Confirm flag” 1214 is set.
When a plurality of confirmed partial configuration information trees are associated with the same actual measurement point or alternative measurement point, the measurement value table design unit 121 sets “partial configuration information tree group ID” 1213 of those partial configuration information trees. Are assigned the same partial configuration information tree group ID.
In addition, even if the partial configuration information trees that belong to different partial configuration information tree groups have a unique number of actual measurement points or alternative measurement points associated with them, the measurement value table design The unit 121 may reset the same partial configuration information tree group ID.

Another condition (third confirmed state) for determining that the partial configuration information tree has been confirmed in step S1305 will be described.
Even when one or more actual measurement points P are associated with a plurality of undefined partial configuration information trees, the actual measurement points P are regarded as independent measurement points and assigned different alternative measurement point IDs. Thus, the partial configuration information tree can be determined.
That is, the measurement value table design unit 121 stores the measurement data of the actual measurement point P in the plurality of measurement value tables 144.
However, when there are a large number of such actual measurement points P, a large amount of measurement data is stored in duplicate and triple, which is a waste of storage capacity.
Therefore, the measurement value table design unit 121 sets the number of measurement points that can be overlapped in advance as a threshold, and the number of actual measurement points associated with a plurality of undefined partial configuration information trees sets the threshold. If not, a record is added to the measurement point management information table 1200, an alternative measurement point ID is newly assigned to the actual measurement point P, and the alternative measurement point ID is set in the “measurement point ID” 1201.
At the same time, the measurement value table design unit 121 sets the original actual measurement point ID in the “alternative measurement point definition” 1205 of the record.
Then, the measurement value table design unit 121 determines the partial configuration information tree associated with the actual measurement point P as it is.
By assigning different alternative measurement point IDs to the actual measurement points P, the partial configuration information trees associated with the actual measurement points P can be regarded as independent partial configuration information trees. In the case of satisfying one confirmed state or the second confirmed state, the partial configuration information tree can be confirmed.

In the example shown in FIG. 25, the subtree data 1101 is associated with the actual measurement points 1 to 6, and the subtree data 1102 is associated with the actual measurement points 6 to 11.
The actual measurement point 6 is associated with both the partial tree data 1101 and the partial tree data 1102.
In the example of FIG. 25, the number of columns in one measurement value table is 8, and the number of actual measurement points associated with the subtree data 1101 and the subtree data 1102 is 11. Therefore, the second measurement shown in FIG. It does not correspond to the fixed state.
In the example of FIG. 25, since the number of actual measurement points associated with a plurality of subtree data does not exceed the threshold value, it is determined that the subtree data 1101 and the subtree data 1102 are in the third final state. The
The actual measurement point 6 is assigned to both the measurement value table of the subtree data 1101 and the measurement value table of the subtree data 1102.
The threshold for the number of actual measurement points can be arbitrarily determined by the user.

Here, an operation example of the measurement value table design unit 121 will be described using a specific example.

26 and 28 show a configuration information tree 1131 and a configuration information tree 1132 used in the following description.
Group ID = 1 is set in the configuration information tree 1131, and group ID = 2 is set in the configuration information tree 1132.
In FIG. 26 and FIG. 28, the node with the double outline is a node directly associated with the actual measurement point.
27 is a configuration information table (corresponding to the configuration information table 142 in FIG. 10) of the configuration information tree 1131 in FIG. 26, and FIG. 29 is a configuration information table in the configuration information tree 1132 in FIG.
The configuration information tree 1131 and the configuration information tree 1132 are associated with actual measurement points $ 1 to $ 15 as shown in FIG.
FIG. 31 is a virtual measurement point definition table (corresponding to the virtual measurement point definition table 141 of FIG. 12) of the configuration information tree 1131, and FIG. 32 is a virtual measurement point definition table of the configuration information tree 1132.
FIG. 33 is a temporary configuration information table of the configuration information tree 1131, and FIG. 34 is a temporary configuration information table of the configuration information tree 1132.
FIG. 35 is a measurement point management information table (corresponding to the measurement point management information table 1200 of FIG. 17) of the configuration information tree 1131 and the configuration information tree 1132.
FIG. 36 is a partial configuration information tree table (corresponding to the partial configuration information tree management table 1210 in FIG. 18) before the measurement value table design unit 121 starts dividing the configuration information tree 1131 and the configuration information tree 1132.
In the following, it is assumed that the actual size C = 8, that is, the number of actual measurement points (measurement devices) that can store measurement values in the measurement value table 144 is eight.

The measurement value table design unit 121 divides the configuration information tree 1131 and the configuration information tree 1132 so that the actual size of each partial tree is C = 8 or less, as shown in S1102 of FIG.

Specifically, the measurement value table design unit 121 selects, for example, the configuration information tree 1131 (S1301 in FIG. 19), and extracts nodes “A02” and “A03” that are child nodes of the root node “A01”. (S1302).
Then, the measurement value table design unit 121 subtracts 1 from the “level” of the nodes “A02” to “A39” of the temporary configuration information table (FIG. 33) of the configuration information tree 1131 (S1303).
As a result, the temporary configuration information table of the configuration information tree 1131 is updated as shown in FIG.
Further, the measurement value table design unit 121 updates the root node ID of the record in which “1” (ID of the root node “A01”) is described in the root node ID column in the measurement point management information table (FIG. 35). (S1303).
As a result, the measurement point management information table is updated as shown in FIG.

Next, the measurement value table design unit 121 stores the partial tree information having the node “A02” as the root node and the partial tree information having the node “A03” as the root node into the partial configuration information tree table (FIG. 36). (S1304).
At this time, neither the subtree having the node “A02” as the root node nor the subtree having the node “A03” as the root node has been determined.
Since the actual measurement points directly associated with the subtree having the node “A02” as the root node are the actual measurement points 1 to 7, the actual size is 7, but the actual measurement points 1 to 7 are the configuration information. Also associated with tree 1132.
For this reason, the subtree having the node “A02” as the root node is not in the first definite state.
Since the configuration information tree 1132 is not divided at this point, the configuration information tree 1132 associated with the actual measurement points 1 to 7 is also associated with the actual measurement points 8 to 15, so that the second confirmation is made. It is not in a state.
Further, the configuration information tree 1132 is not in the third finalized state.
Since the actual measurement points directly associated with the subtree having the node “A03” as the root node are the actual measurement points 8 to 14, the actual size is 7, but the actual measurement points 8 to 14 are the configuration information. Also associated with tree 1132.
For this reason, the subtree having the node “A03” as the root node is not in the first definite state.
Since the configuration information tree 1132 is not divided at this point, the configuration information tree 1132 associated with the actual measurement points 8 to 14 is also associated with the actual measurement points 1 to 7 and 15, so that the second It is not in the final state.
Further, the configuration information tree 1132 is not in the third finalized state.
Therefore, the partial configuration information tree table is updated as shown in FIG.
In the partial configuration information tree table of FIG. 39, the confirmation flag is “1” in the partial tree composed only of the root node “A01”, but the confirmation flag is “0” in the other partial trees.

Next, the measurement value table design unit 121 selects the configuration information tree 1132 (S1301 in FIG. 19), and extracts nodes “B11” to “B13” that are child nodes of the root node “B01” (S1302).
Then, the measurement value table design unit 121 subtracts 1 from the “level” of the nodes “B11” to “B44” in the temporary configuration information table (FIG. 34) of the configuration information tree 1132 (S1303).
As a result, the temporary configuration information table of the configuration information tree 1132 is updated as shown in FIG.
Further, the measurement value table design unit 121 updates the root node ID of the record in which “101” (the ID of the root node “B01”) is described in the root node ID column in the measurement point management information table (FIG. 38). (S1303).
As a result, the measurement point management information table is updated as shown in FIG.

Next, the measurement value table design unit 121 uses the subtree information having the node “B11” as the root node, the subtree information having the node “B12” as the root node, and the node “B13” as the root node. The partial tree information is added to the partial configuration information tree table (FIG. 39) (S1307).
At this point, all subtrees are fixed.
Since the unique number of actual measurement points associated with the subtree having the node “A02” as the root node and the subtree having the node “B11” as the root node is 7, the node “A02” is defined as the root node. And the subtree having the node “B11” as the root node corresponds to the second definite state.
Eight unique measurement points are associated with the subtree having the node “A03” as the root node, the subtree having the node “B12” as the root node, and the subtree having the node “B13” as the root node. Therefore, the subtree having the node “A03” as the root node, the subtree having the node “B12” as the root node, and the subtree having the node “B13” as the root node correspond to the second definite state.
Therefore, the partial configuration information tree table is updated as shown in FIG.
In the partial configuration information tree table of FIG. 42, the confirmation flag is “1” in all the partial trees.

Next, the measurement value table design unit 121 updates the “partial configuration information tree group ID” field of the partial configuration information tree table.
Specifically, the measurement value table design unit 121 updates the “partial configuration information tree group ID” field as shown in FIG.

Next, the measurement value table design unit 121 performs S1103 to S1105 in FIG. 15. In this example, since all subtrees have been determined, the processing of S1103 to S1105 is omitted.
The measurement value table design unit 121 determines whether the actual measurement point is directly included in the virtual measurement point definition of the root node (S1106).
Referring to the virtual measurement point definition tables in FIG. 31 and FIG. 32, all of the root nodes “A01”, “A02”, “A03”, “B01”, “B11”, “B12”, “B13” The actual measurement point is not directly included in the virtual measurement point definition (NO in S1106).
Therefore, the measurement value table design unit 121 virtually transmits the information of the alternative measurement points for each of “A01”, “A02”, “A03”, “B01”, “B11”, “B12”, and “B13”. It adds to a measurement point definition table (S1108).
Further, in this example, since the information of all the partial trees has already been registered in the partial configuration information tree management table, the process of S1109 is omitted.
Since all subtrees have been determined (YES in S1110), the measurement value table design unit 121 performs the processes of S1111 to S1113.
Since the processing of S1111 to S1113 is as described with reference to FIG. 16, the description thereof is omitted here.
At the stage where the processing of S1113 is completed, the virtual measurement point definition table is updated as shown in FIGS. 45 and 46, and the measurement point management information table is updated as shown in FIG.
In the virtual measurement point definition table of FIG. 45, the alternative measurement point “% 1” is added in the virtual measurement point definition of the virtual measurement point ID: # 1, and the alternative measurement point flag is “1”.
In addition, alternative measurement points “% 2” and “% 3” are added to the virtual measurement point definitions of the virtual measurement point IDs: # 2 and # 3, and the alternative measurement point flag is “1”.
Similarly, in the virtual measurement point definition table of FIG. 46, the alternative measurement points “% 4”, “% 5”, “%” in the virtual measurement point definitions of the virtual measurement point IDs: # 101, # 111, # 112, and # 113 6 ”and“% 7 ”are added, and the alternative measurement point flag is“ 1 ”.
In the measurement point management information table of FIG. 47, records of measurement point IDs:% 1 to% 7 are added.
The alternative measurement point definition in the measurement point management information table is derived, for example, according to the procedure shown in FIG.
FIG. 48 shows a procedure for deriving% 1 alternative measurement points.
As shown in FIG. 45, the alternative measurement point% 1 corresponds to the virtual measurement point # 1, and from the virtual measurement point definition, # 1 = # 2 + # 3 and # 2 = # 11 + # 12 + # 13 and # 3 = # 14 + # 15 + # 16.
Therefore, the alternative measurement point of% 1 is # 1 = (# 11 + # 12 + # 13) + (# 14 + # 15 + # 16).
Thereafter, similarly, when each virtual measurement point is expanded in accordance with the virtual measurement point definition, an alternative measurement point definition such as the last line in FIG. 48 is obtained.

As described above, in the present embodiment, the following measurement data management device has been described.
(A) A measurement data collection and storage unit that receives input of a plurality of measurement data measured by a measurement device, and a storage device for storing the measurement data, and a plurality of input measurement data defined in the storage device Stored in one of the measured value tables.
(B) The measuring device is associated with configuration information having a plurality of hierarchies (tree structure).
(C) A virtual measurement point definition for calculating the measurement data of the virtual measurement point depending on the hierarchical relationship of the configuration information is provided, based on the measurement data stored in the measurement value table and the virtual measurement point definition A measurement data output unit that calculates and outputs measurement data of virtual measurement points is provided.
(D) A measurement value table design unit is provided that divides the configuration information into subtrees based on the configuration information and the virtual measurement point definition.
(E) The measurement value table design unit further associates measurement data associated with one or more subtrees of the configuration information with the measurement value table, and records the corresponding information as measurement value table design information.
(F) A measurement value table definition unit that defines a plurality of tables in the storage device based on the measurement value table design information is provided.
(G) The measurement data collection and accumulation unit determines a measurement value table for storing the measurement data based on the measurement data identifier and the measurement value table design information.

In the present embodiment, the configuration information is stored in the subtree so that the number of types of measurement data associated with the subtree of the configuration information is within the specifications of the database management system used for storing the measurement data. The measurement value table design unit for recursively dividing has been described.

In this embodiment, when one or a plurality of measurement data is associated with a plurality of pieces of configuration information, any one of the pieces of associated configuration information is selected and associated with one or a plurality of subtrees. A measurement value table design unit that repeatedly divides the measurement data into subtrees until the number of measurement data falls within the range of the above specifications has been described.

In the present embodiment, the measurement value table design unit described below has been described.
(A) The division of the configuration information into subtrees is performed by dividing the root node of the tree structure into a subtree whose new root is a child node of the root node.
(B) The identifier of the alternative measurement point is newly assigned to the original root node, and the identifier and the calculation formula for calculating the measurement data of the virtual measurement point corresponding to the root node are used as the measurement value table design information. Remember.

Further, in the present embodiment, when one or a plurality of measurement data is associated with a plurality of subtrees of configuration information, an identifier of a plurality of alternative measurement points is assigned to the measurement data, The measurement value table design unit that stores the measurement device identifier or calculation formula for obtaining the measurement data in the measurement value table design information has been described.

Finally, a hardware configuration example of the measurement data management apparatus 100 shown in the present embodiment will be described with reference to FIG.
The measurement data management apparatus 100 is a computer, and each element of the measurement data management apparatus 100 can be realized by a program.
As a hardware configuration of the measurement data management apparatus 100, an arithmetic device 1901, an external storage device 1902, a main storage device 1903, a communication device 1904, and an input / output device 1905 are connected to the bus.

The arithmetic device 1901 is a CPU (Central Processing Unit) that executes a program.
The external storage device 1902 is, for example, a ROM (Read Only Memory), a flash memory, or a hard disk device.
The main storage device 1903 is a RAM (Random Access Memory).
The communication device 1904 is, for example, a NIC (Network Interface Card).
The input / output device 1905 is, for example, a mouse, a keyboard, a display device, or the like.

The program is normally stored in the external storage device 1902, and is sequentially read into the arithmetic device 1901 and executed while being loaded in the main storage device 1903.
The program is a program that realizes the function described as “˜unit” (excluding the data storage unit, the same applies hereinafter) shown in FIG.
Further, an operating system (OS) is also stored in the external storage device 1902. At least a part of the OS is loaded into the main storage device 1903, and the arithmetic unit 1901 executes “OS” while executing “OS” shown in FIG. ”Is executed.
In the description of the present embodiment, “determining”, “determining”, “extracting”, “dividing”, “detecting”, “setting of”, “registering” ”,“ Selection of ”,“ generation of ”,“ addition of ”,“ update of ”,“ input of ”,“ output of ”, etc. Data, signal values, and variable values are stored in the main storage device 1903 as files.
Also, the encryption key / decryption key, random number value, and parameter may be stored in the main storage device 1903 as a file.

The configuration in FIG. 44 is merely an example of the hardware configuration of the measurement data management device 100, and the hardware configuration of the measurement data management device 100 is not limited to the configuration described in FIG. There may be.

Further, the data processing method according to the present invention can be realized by the procedure shown in the present embodiment.

100 measurement data management device, 110 virtual measurement point management unit, 111 virtual measurement point information input / output unit, 112 configuration information input / output unit, 120 measurement value table management unit, 121 measurement value table design unit, 122 measurement value table definition unit, 130 measurement data management unit, 131 measurement data collection storage unit, 132 virtual measurement data calculation unit, 133 measurement data output unit, 140 data storage unit, 141 virtual measurement point definition table, 142 configuration information table, 143 measurement value table design information, 144 measurement value table, 200 measurement data management system, 201 measurement device, 210 base device, 211 measurement data reception unit, 212 measurement data transmission unit, 219 base device storage unit, 220 operation terminal, 221 application execution unit, 229 operation terminal storage , 400 measurement data, 1200 measurement points management information table, 1210 partial configuration information tree management table.

Claims (10)

1. A data processing device for managing tree structure data associated with a measuring device,
   The tree structure data is converted into a plurality of subtree data so that the number of measuring devices associated with each subtree data is equal to or less than the number of table storage devices that is the upper limit number of measuring devices that can store measurement values in the measurement value table. A data dividing unit that divides the data into
   A state determination unit that determines whether the subtree data divided by the data division unit is in a definite state;
   A table allocating unit for allocating a measurement value table for storing measurement values from a measuring device associated with the partial tree data, with respect to the partial tree data determined to be in a finalized state by the state determination unit; ,
   The state determination unit
   A measuring device associated with one subtree data is not associated with any other subtree data, and the number of measuring devices associated with the one subtree data is equal to or less than the number of table storage devices. Is determined that the one subtree data is in the first definite state,
   At least one measuring device among measuring devices associated with one subtree data is duplicated and associated with other subtree data, and the number of measuring devices associated with the one subtree data When the total number obtained by eliminating duplication with the number of measuring devices associated with the other subtree data is equal to or less than the number of table storage devices, the one subtree data and the other subtree data are It is determined to be in the second final state,
   A data processing apparatus characterized by causing the data dividing unit to further divide subtree data determined to be neither in the first definite state or the second definite state into a plurality of subtree data.
2. The state determination unit
   At least one measuring device among measuring devices associated with one subtree data is duplicated and associated with other subtree data, and the number of measuring devices associated with the one subtree data The total number obtained by eliminating duplication with the number of measuring devices associated with the other subtree data exceeds the number of table storage devices, and is duplicated in the one subtree data and the other subtree data. When it is determined that the number of associated measuring devices is equal to or less than a predetermined number and the one subtree data and the other subtree data are in the first or second definite state, Judging that the one subtree data and the other subtree data are in the third definite state,
   The subtree data determined not to be in any of the first definite state, the second definite state, and the third definite state is further divided into a plurality of subtree data by the data dividing unit. The data processing apparatus according to 1.
3. The data processing device includes:
   Manage tree structure data including multiple nodes,
   The data dividing unit
   Dividing the plurality of subtree data into subtree data of only a root node and each of two or more subtree data having a child node of the root node as a new root node;
   The state determination unit
   Until all the subtree data except the subtree data of only the root node is in a definite state, the subtree data that is not in the definite state excluding the subtree data of only the root node is further divided into a plurality of subtree data. The data processing apparatus according to claim 1, wherein the data processing apparatus is divided.
4. The data processing device includes:
   Multiple nodes that are the unit of measurement value aggregation are included, and each node is directly or indirectly associated with an actual measurement point, which is an identifier that is directly associated with the measurement value of the measurement device. Manage tree-structured data that defines at least one of the virtual measurement points that are identifiers, and for which calculation formulas for measurement value aggregation are defined,
   The data processing device further includes:
   Determining whether or not the number of measurement points included in the calculation formula of the root node of the subtree data divided by the data dividing unit is only one actual measurement point;
   An identifier indicating that it is necessary to pre-calculate the measurement values before the aggregation instruction is given when there is not only one actual measurement point in the root node calculation formula The data processing apparatus according to claim 3, further comprising an alternative measurement point setting unit that associates an alternative measurement point that is a root node with the root node.
5. The alternative measurement point setting unit is
   When a virtual measurement point is included in the calculation formula of the root node, only the actual measurement point is included using the actual measurement point directly or indirectly related to the virtual measurement point, and the calculation formula of the root node Generate an alternative formula that yields the same calculation results as
   The data processing apparatus according to claim 4, wherein the alternative calculation formula is associated with the alternative measurement point.
6. The data processing device further includes:
   For the root node associated with the alternative measurement point, an alternative measurement point that performs a calculation for totaling the measurement values in advance before the aggregation instruction for the root node is given, and associates the calculation result with the alternative measurement point The data processing apparatus according to claim 4, further comprising a calculation unit.
7. The table allocation unit
   One measurement value table is assigned to one subtree data determined to be in the first definite state by the state determination unit,
   The data processing apparatus according to claim 1, wherein one measurement value table is assigned to a plurality of partial tree data determined to be in the second definite state by the state determination unit.
8. The table allocation unit
   One measurement value table is assigned to each of the plurality of subtree data determined to be in the third finalized state by the state determination unit,
   The data processing apparatus according to claim 2, wherein measurement values from measurement devices that are associated with the plurality of partial tree data are stored in a measurement value table of each partial tree data.
9. A data processing method performed by a computer that manages tree structure data associated with a measuring device,
   The computer includes a plurality of pieces of tree structure data such that the number of measurement devices associated with each partial tree data is equal to or less than the number of table storage devices that is the upper limit number of measurement devices that can store measurement values in the measurement value table. Data division processing to divide into subtree data of
   A state determination process in which the computer determines whether the subtree data divided by the data division process is in a definite state;
   Table allocation processing for assigning a measurement value table for storing measurement values from a measuring device associated with the partial tree data to the partial tree data determined by the computer to be in a definite state by the state determination processing And
   In the state determination process,
   The computer is
   A measuring device associated with one subtree data is not associated with any other subtree data, and the number of measuring devices associated with the one subtree data is equal to or less than the number of table storage devices. Is determined that the one subtree data is in the first definite state,
   At least one measuring device among measuring devices associated with one subtree data is duplicated and associated with other subtree data, and the number of measuring devices associated with the one subtree data When the total number obtained by eliminating duplication with the number of measuring devices associated with the other subtree data is equal to or less than the number of table storage devices, the one subtree data and the other subtree data are It is determined to be in the second final state,
   In the data division process,
   The computer is
   A data processing method characterized by further dividing the partial tree data determined to be neither in the first fixed state or the second fixed state in the state determination processing into a plurality of partial tree data.
10. To the computer that manages the tree structure data associated with the measuring device,
    The tree structure data is converted into a plurality of subtree data so that the number of measuring devices associated with each subtree data is equal to or less than the number of table storage devices that is the upper limit number of measuring devices that can store measurement values in the measurement value table. Data division processing to divide into
    A state determination process for determining whether or not the subtree data divided by the data division process is in a definite state;
    A table allocation process for allocating a measurement value table for storing a measurement value from a measuring device associated with the subtree data, for the subtree data determined to be in the finalized state by the state determination process; ,
    In the state determination process,
    In the computer,
    A measuring device associated with one subtree data is not associated with any other subtree data, and the number of measuring devices associated with the one subtree data is equal to or less than the number of table storage devices. In the case where the one subtree data is in the first definite state,
    At least one measuring device among measuring devices associated with one subtree data is duplicated and associated with other subtree data, and the number of measuring devices associated with the one subtree data When the total number obtained by eliminating duplication with the number of measuring devices associated with the other subtree data is equal to or less than the number of table storage devices, the one subtree data and the other subtree data are Let them determine that they are in the second final state,
    In the data division process,
    In the computer,
    A program characterized in that the subtree data determined to be neither in the first definite state or the second definite state in the state determination process is further divided into a plurality of subtree data.

Images