JP5436309B2 - Data processing apparatus, data processing method, and program - Google Patents

Description

  The present invention relates to a technique for managing the version number of data.

  There are multiple devices (such as sensors) that generate data at the time of event detection or at regular intervals, and in the process of collecting and accumulating data generated by these devices, the data from the device is the data type and accuracy Regardless of, etc., it is stored in a database (sensor DB) in a fixed format record, and configuration information such as data attributes (accuracy, type, unit, etc.), storage location in the sensor DB, information on the device that generated the data is sensor There is a method of managing by a configuration information database (configuration information DB) separately from the DB.

  FIG. 25 is a system configuration diagram showing such a data storage method.

In FIG. 25, the data storage device 101 stores the data collected and transmitted by the data collection unit 032 from the sensor device 031.
In the data storage device 101, the data reception unit 102 receives data from the data collection unit 032 and delivers the data to the data storage unit 103.
The data storage unit 103 outputs the data received from the data receiving unit 102 to the sensor data 106 according to the contents of the configuration information 109.
The DB management unit 104 performs input / output processing for the sensor DB 105.
The sensor DB 105 stores data generated by the sensor device 031 as sensor data 106.
The configuration information DB management unit 107 performs input / output processing for the configuration information DB 108.
The configuration information DB 108 records configuration information 109 including data attributes from the sensor device 031, storage locations in the sensor DB 105, information on the sensor device 031, and the like.
The sensor DB search unit 110 searches the sensor data 106 according to the contents of the configuration information 109, and outputs search result data and related configuration information 109.
The configuration information setting APP 111 is an application that registers and updates the configuration information 109, and the search APP 112 is an application that searches the sensor data 106 and the configuration information 109.
In the data storage device 101, the DB management unit 104 and the sensor DB 105 are dedicated to managing the sensor data 106 from the sensor device 031, so that the efficiency of input / output processing and storage use can be improved.

In such a data storage device 101, when a device configuration change occurs due to addition or change of the sensor device 031, the data storage unit 103 changes the content of the configuration information 109 in response to the change, so that the data storage unit 103 has a new device configuration. Data can be stored in
However, since the configuration information 109 corresponding to the sensor data 106 that has been accumulated before the device configuration change is lost from the configuration information DB 108, the sensor DB search unit 110 uses the sensor data 106 accumulated before the device configuration change. Since the corresponding configuration information 109 cannot be acquired, the processing cannot be performed.
Therefore, in the search APP 112, the sensor data 106 after the device configuration change can be used, but there is a problem that the sensor data 106 before the device configuration change cannot be used.

As a solution to such a problem, there is a method of managing configuration information including a change history.
In the history management of configuration information that consists of multiple component data as configuration information and is referenced during execution of various processes, as a method of coexisting multiple versions of information accompanying changes in element data, in the conventional history management method, element data The information of multiple versions coexists by specifying the version to be referred to at the time of processing execution from the version identification information corresponding to and the validity period information for each version of the information (for example, Patent Document 1).
The version identification information corresponding to the element data is obtained by adding a start version and an end version of information corresponding to the element data as a column to each record of the element data.
The valid period information for each version of information is composed of three columns of version number, valid start date / time, and valid end date / time.
When adding element data as a change to element data, set the current version at the time of addition to the start version column and add element data.
When updating the element data, the end version column of the element data to be updated is updated to the current version, and the updated element data is newly added with the current version set in the start version column.
When deleting element data, the end version column of the element data to be deleted is updated to the current version.
By such an operation, information of multiple versions accompanying the change of element data coexists.
In referencing element data in process execution, the required version number is derived from the date and time at the time of process execution using the validity period information for each version, and the element data of the corresponding version is extracted using version identification information. Was getting information.

JP 2008-310710 A

In the conventional history management system, it is an implicit premise that a plurality of element data are changed by a single operation.
In other words, when a plurality of element data is changed due to the addition of a new version, the changed values of all the element data as information as a whole need to be made clear in advance.
Therefore, for information where the changed value of the element data is not fixed as a whole at once, the changed value is stored separately when the value is changed for each element data, and the changed information as a whole There is a problem that each element data has to be changed based on the changed value recorded at the stage when the values of the values are aligned.

For example, in a system that collects and accumulates data transmitted from devices such as various sensors at remote locations, the configuration information for managing device data such as device configuration, data attributes, data storage destination database, etc. Data is determined by installing and operating actual equipment.
When a plurality of types of devices are targeted and there are a plurality of installation locations of devices, there is a time lag in units of several days to several weeks when devices are installed or changed.
When there are a large number of target devices, it is inefficient to store the changed values separately until the processing is completed in all devices, for example, a recording system is required in addition to the original system.

  Further, in the conventional history management apparatus, a change (addition / update / deletion) to the element data is handled as a fixed value immediately, so that there is a problem that it cannot be recorded in the element data unless the change content is fixed.

For example, in the system that collects and accumulates the above-mentioned device data, when adding a new device to an already operating system and increasing the data to be stored, the system is not stopped and parallel to this operation. When device data related to an additional device is added as component data for the purpose of performing a test operation, it is essentially undetermined test device data and cannot be handled.
If test equipment data is added to the component data, if there is no problem in the test operation, the test equipment data can be handled as actual equipment data as it is. However, when the component data is changed accordingly, there is a problem that test device data that does not exist as device data remains as a history.

  One of the main purposes of the present invention is to solve the above-mentioned problems, enabling flexible data update, tracing data update history and update time, and past data before update. Realize a mechanism that can use data.

The data processing apparatus according to the present invention
A data processing device that performs data processing using a plurality of object IDs (Identification) for identifying a plurality of management objects,
A table data storage unit that includes a plurality of records and stores one or more table data in which any object ID is described in each record;
A table data management unit that updates table data in units of records;
For each object ID, a version value that is updated as the table data is updated by the table data management unit is described in chronological order until at least the current version, and the start time at which the version becomes valid for each version value And a version information storage unit for storing version information in which an invalid end time is described,
A version management unit that updates the version information when any table data is updated by the table data management unit;
The table data storage unit
Each record includes one or more table data including a version range field for describing a range of version values corresponding to the validity period from when the record is provided to the table data until the record content is changed Remember,
The table data management unit
When updating any of the table data, the version value of the current version of the object ID described in the update target record to be updated and the next generation of the current version according to the update form of the table data Acquiring at least one of the version values of the version from the version information storage unit, describing the acquired version value in the version range field of the update target record, and updating the table data;
The version management unit
The update time when the table data management unit has updated the table data and the object ID described in the update target record are notified, and the notified update time is used as the end time of the current version of the notified object ID. Described in the version information, described in the version information such that the next generation version of the current version of the notified object ID becomes the new current version of the object ID, and the notified update time It is described in the version information as the start time of a new current version.

  According to the present invention, the version value corresponding to the validity period from when the record is provided until the record content is changed is described in each record of the table data, and the start time is set for each version value in the version information. Describe the end time and update the table data for each record. For this reason, when there is a change, the table data can be updated immediately in record units, and there is no need to record the changed value. Further, since the record contents of the past version are also left, the record update history and update time can be traced, and the record of the past version can also be used.

FIG. 3 is a diagram illustrating an example of a system configuration according to the first embodiment. 1 is a diagram illustrating a configuration example of a data storage device according to Embodiment 1. FIG. FIG. 4 is a diagram illustrating an example of a measurement value table according to the first embodiment. FIG. 3 is a diagram showing an example of a measurement value attribute table according to the first embodiment. FIG. 4 is a diagram showing an example of a measurement value / column correspondence table according to the first embodiment. FIG. 4 is a diagram showing an example of a device attribute table according to the first embodiment. FIG. 4 is a diagram showing an example of a position attribute table according to the first embodiment. FIG. 4 is a diagram illustrating an example of a version management table according to the first embodiment. FIG. 4 is a diagram showing an example of a base management table according to the first embodiment. FIG. 3 is a diagram showing a relationship between tables according to the first embodiment. FIG. 6 is a flowchart showing an operation example when changing configuration information according to the first embodiment. FIG. 6 is a flowchart showing an operation example when adding data according to the first embodiment. FIG. 3 is a flowchart showing an operation example in data rewriting according to the first embodiment. FIG. 6 is a flowchart showing an operation example when deleting data according to the first embodiment. FIG. 5 is a flowchart showing an operation example when a version name is revised according to the first embodiment. FIG. 3 is a flowchart showing an operation example when changing a base according to the first embodiment. FIG. 6 is a flowchart showing an operation example when canceling a change according to the first embodiment. FIG. 3 is a flowchart showing an operation example when storing data according to the first embodiment. FIG. 6 is a flowchart showing an operation example when searching for configuration information according to the first embodiment. FIG. 3 is a flowchart showing an operation example when searching for sensor data according to the first embodiment. FIG. 5 shows a specific example of data addition according to the first embodiment. FIG. 3 is a diagram showing a specific example of data rewriting according to the first embodiment. FIG. 6 is a diagram showing a specific example of data deletion according to the first embodiment. 2 is a diagram illustrating a hardware configuration example of the data storage device according to the first embodiment. FIG. The figure explaining a prior art.

Embodiment 1 FIG.
In the present embodiment, in a data storage device including a database for storing data collected from devices and a configuration information database for managing configuration information such as data attributes and storage locations, change history and information confirmation of each element data of the configuration information A data storage device that can cope with a change in configuration information by enabling management of previous element data will be described.

FIG. 1 shows a system configuration example according to the present embodiment.
As shown in FIG. 1, the data storage device 001 is connected to a plurality of data collection units 032 via a network 500.
The data storage device 001 stores the data transferred from the data collection unit 032 of each base 030 in the database.
The data storage device 001 is an example of a data processing device.
Each of the data collection units 032 is arranged at the base 030.
The base 030 is a physical place where a sensor device 031 that generates data to be stored in the data storage device 001 is installed, and corresponds to, for example, a building or a site.
The base 030 is an example of a management target object and a management target area.
Each data collection unit 032 collects data from one or more sensor devices 031 arranged at each base 030 and transmits the collected data to the data storage device 001 via the network 500.
The sensor device 031 is a device that outputs time-related data, such as a device that outputs measurement values at regular intervals (for example, a temperature sensor) or a device that outputs a log according to an event (for example, an entrance / exit management device). .
The sensor device 031 is an example of a data collection device.
In the present embodiment, the method by which the data collection unit 032 collects data from the sensor device 031 is not limited (for example, data acquisition from a file output by the sensor device 031 or data using an API provided by the sensor device 031). Acquisition).

  Next, a configuration example of the data storage device 001 according to the present embodiment will be described with reference to FIG.

The data storage device 001 has two databases.
The sensor DB 006 is a database for storing sensor data received from the data collection unit 032.
On the other hand, the configuration information DB 011 is a database that stores configuration information such as data attributes (accuracy, type, unit, etc.), storage location in the sensor DB 006, and information about the device that generated the data.
The data storage device 001 stores sensor data in the sensor DB 006 according to the contents of the configuration information DB 011.
Details of the sensor DB 006 and the configuration information DB 011 will be described later.

  The data receiving unit 002 receives the data transferred for each data collecting unit 032 at the base 030 and transfers it to the data storage unit 003.

  The data storage unit 003 assembles the reception data received from the data reception unit 002 based on the contents of the configuration information DB 011 into a record format, and outputs the data to the sensor DB 006 using the DB management unit 005.

  The data search unit 004 searches the data of the sensor DB 006 using the DB management unit 005.

  The DB management unit 005 is a data management function that executes input / output with respect to the sensor DB 006.

The sensor DB 006 is a database in which data generated by the sensor device 031 at the base 030 is accumulated in a fixed record format.
The sensor DB 006 is an example of a received data storage unit.

The version information update unit 007 performs revision processing of a version (version) in the configuration information DB 011 using the configuration information DB management unit 010.
More specifically, the version information update unit 007 uses any one of the table data (measurement value attribute table 012, measurement value / column correspondence table 013, device attribute table 014, position attribute table 015 described later) by the configuration information update unit 008. Is updated), a later-described version management table 016 is updated.
The version information update unit 007 is an example of a version management unit.

The configuration information update unit 008 uses the configuration information DB management unit 010 to update the table data of the configuration information DB 011 in units of records.
The configuration information update unit 008 is an example of a table data management unit.

The configuration information search unit 009 performs a record search process in the table data of the configuration information DB 011 using the configuration information DB management unit 010.
The configuration information search unit 009 is an example of a record search unit.

  The configuration information DB management unit 010 is a data management function that executes input / output with respect to the configuration information DB 011.

The configuration information DB 011 is a database that records various types of information related to the data storage device 001. The measurement value attribute table 012, the measurement value / column correspondence table 013, the device attribute table 014, the position attribute table 015, the version management table 016, and the site management It consists of a table 017.
In the following, the measurement value attribute table 012, the measurement value / column correspondence table 013, the device attribute table 014, the position attribute table 015, the version management table 016, and the site management table 017 correspond to the measurement value attribute 012 and the measurement value / column correspondence, respectively. 013, device attribute 014, location attribute 015, version management 016, and base management 017.
The configuration information DB 011 is an example of a table data storage unit and a version information storage unit.

The measurement value attribute table 012 is table data that records information regarding data from the sensor device 031.
The measurement value / column correspondence table 013 is table data that records information on the storage destination of the data from the sensor device 031 in the sensor DB 006.
The device attribute table 014 is table data that records information related to the sensor device 031.
The position attribute table 015 is table data that records information related to the installation location of the sensor device 031 or the like.
The version management table 016 is table data that records information related to the version (version) of data stored in the configuration information DB 011.
The version management table 016 is an example of version information.
The base management table 017 is table data that records information about the base 030.

  The configuration information setting APP 018 is an application program for setting the data of the configuration information DB 011. In the present embodiment, the format of the external interface for the user is not limited.

  The sensor DB search unit 019 performs a search process for data stored in the sensor DB 006 based on the data of the configuration information DB 011.

  The search APP020 is an application for searching the data in the sensor DB 006, and the form of the external interface for the user is not limited in this embodiment.

  FIG. 3 is a schematic diagram illustrating an example of data stored in the sensor DB 006 in FIG.

In FIG. 3, a measurement value table 040 is table data that records data from the sensor device 031.
The record of the measurement value table 040 is mainly composed of one occurrence date / time column and columns for a plurality of data values.
Data from the sensor device 031 is associated with one column of the measurement value table 040, and data of the plurality of sensor devices 031 is collected as one record for each occurrence date and time.

  FIG. 4 is a schematic diagram illustrating an example of the measurement value attribute table 012 in FIG.

In FIG. 4, the measurement value attribute table 012 includes columns of base ID, measurement value ID, start version name, end version name, measurement value name, device ID, position ID, type, and accuracy.
The base ID is an identifier for specifying the base 030 from which the measurement values are collected, and is managed by the base management 017.
The measurement value ID is an identifier for distinguishing measurement values, and is numbered by the measurement value attribute 012 as a unique value for each base ID.
The start version name is information indicating the start position of the range of the version corresponding to the data of the measurement value attribute 012 in the data version of the configuration information DB 011.
The end version name is information indicating the end position of the range of the version corresponding to the data of the measurement value attribute 012 in the data version of the configuration information DB 011.
The measurement value name is descriptive information that can be referred to when the user identifies the measurement value.
The device ID is an identifier for identifying the device that generated the measurement value, and is managed by the device attribute 014.
The position ID is an identifier indicating a place related to a measurement value or an installation place of a device that has generated the measurement value, and is managed by a position attribute 015.
The type is information representing the contents of measurement values such as temperature, humidity, and electric energy.
The accuracy is information indicating the accuracy of the numerical value of the measurement value.
In the measurement value attribute 012, there can be a column of information regarding measurement values in addition to these columns.

The start version name and the end version name are in other words the range of the version number (version value) corresponding to the valid period from when each record is provided in the measurement value attribute table 012 until the record content is changed. Is a field for describing (version range field).
The start version name is a field (version subfield) for describing the version number (version value) corresponding to the beginning of the valid period, and the end version name is the version number (version value) corresponding to the end of the valid period. Is a field (terminal subfield).

  FIG. 5 is a schematic diagram showing an example of the measured value / column correspondence table 013 in FIG.

In FIG. 5, the measurement value / column correspondence table 013 includes a base ID, a measurement value ID, a start version name, an end version name, a server, a table, and an output column.
The base ID is an identifier for specifying the base 030 to which the measurement value belongs, and is managed by the base management 017.
The measurement value ID is an identifier for specifying the measurement value, and is managed by the measurement value attribute 012.
The start version name is information indicating the start position of the version range corresponding to the data of the measured value / column correspondence 013 in the data version of the configuration information DB 011.
The end version name is information indicating the end position of the range of the version corresponding to the information of the measured value / column correspondence 013 in the data version of the configuration information DB 011.
The server is information indicating a server where the sensor DB 006 exists.
The table is information indicating a table name for storing data indicated by the measurement value ID in the sensor DB 006.
The output column is information indicating the column name of the table that is the storage destination of the data indicated by the measurement value ID.
In the measurement value / column correspondence 013, there may be columns of related information in addition to these columns.

Also in the measurement value / column correspondence table 013, the above-described start version name and end version name are the versions corresponding to the valid period from when each record is provided in the measurement value / column correspondence table 013 until the record content is changed. This is a field (version range field) for describing the range of numbers (version values).
The start version name is a field (version subfield) for describing the version number (version value) corresponding to the beginning of the valid period, and the end version name is the version number (version value) corresponding to the end of the valid period. Is a field (terminal subfield).

  FIG. 6 is a schematic diagram showing an example of the device attribute table 014 in FIG.

In FIG. 6, the device attribute 014 table includes columns of base ID, device ID, start version name, end version name, device name, and device type.
The base ID is an identifier for specifying the base 030 where the device exists, and is managed by the base management 017.
The device ID is an identifier for identifying the device, and is numbered by the device attribute 014 as a unique value for each base ID.
The start version name is information indicating the start position of the version range corresponding to the data of the device attribute 014 in the data version of the configuration information DB 011.
The end version name is information indicating the end position of the range of the version corresponding to the data of the device attribute 014 in the data version of the configuration information DB 011.
The device name is descriptive information that can be referred to when the user identifies the device.
The device type is information indicating the type of device such as a temperature sensor or a power sensor.
In the device attribute 014, in addition to these columns, there can be a column of information about the device.

Also in the device attribute table 014, the above-mentioned start version name and end version name are the version number (version value) corresponding to the validity period from when each record is provided in the device attribute table 014 until the record content is changed. This is a field (version range field) for describing a range.
The start version name is a field (version subfield) for describing the version number (version value) corresponding to the beginning of the valid period, and the end version name is the version number (version value) corresponding to the end of the valid period. Is a field (terminal subfield).

  FIG. 7 is a schematic diagram showing an example of the position attribute table 015 in FIG.

In FIG. 7, the position attribute table 015 includes a base ID, a position ID, a start version name, an end version name, a position name, a section, and a building column.
The base ID is an identifier for specifying the base 030 to which the position indicated by the position ID belongs, and is managed by the base management 017.
The position ID is an identifier for distinguishing the physical location where the device or the like is installed, and is numbered by the position attribute 015 as a unique value for each base ID.
The start version name is information indicating the start position of the range of the version corresponding to the data of the position attribute 015 in the data version of the configuration information DB 011.
The end version name is information indicating the end position of the range of the version corresponding to the information of the position attribute 015 in the data version of the configuration information DB 011.
The position name is descriptive information that can be referred to when the user identifies the position.
The section is information indicating an area in the base 030 including the position indicated by the position ID.
The building is information indicating a building having a position indicated by the position ID.
In the position attribute 015, there can be a column of information related to the position in addition to these columns.

Also in the position attribute table 015, the above-mentioned start version name and end version name are the version numbers (version values) corresponding to the validity period from when each record is provided in the position attribute table 015 until the record contents are changed. This is a field (version range field) for describing a range.
The start version name is a field (version subfield) for describing the version number (version value) corresponding to the beginning of the valid period, and the end version name is the version number (version value) corresponding to the end of the valid period. Is a field (terminal subfield).

FIG. 8 is a schematic diagram showing an example of the version management table 016 in FIG.
In FIG. 8, the version management 016 is composed of columns of base ID, version name, status, start date / time, and end date / time.
The base ID is an identifier for specifying the base 030 to which the version indicated by the version name belongs, and is managed by the base management 017.
The version name is an identifier indicating the version of the data in the configuration information DB 011 and is assigned by the version management 016 as a unique value for each base ID. The value of the version name is a positive integer that gradually increases as the version becomes new, and the value range is 1 or more and VER_MAX (for example, 0x7fffffff or the like when the data type of the version name column is a 32-bit integer type).
The state is information indicating the state of the plate indicated by the plate name, and has a value of PAST, CUR, or NEXT.
A version whose status is PAST indicates that the data in the configuration information DB 011 has been revised and becomes a history.
The version whose status is CUR indicates that it is the latest version (current version) that is currently valid in the data of the configuration information DB 011.
The version whose status is NEXT indicates that it is candidate data of the next version of the configuration information DB 011 (the version of the next generation after the current version).
There is only one version of CUR and NEXT for each base ID in version management 016.
The start date / time indicates the start date / time in the valid period of the version indicated by the version name.
The end date and time is the end date and time or TIMESTAMP_MAX (for example, 23:59:59 on December 31, 9999) in the valid period of the version indicated by the version name.
In the version management 016, there can be a column of information about the version in addition to these columns.

In this way, the version management table 016 updates each table data of the measurement value attribute 012, the measurement value / column correspondence 013, the device attribute 014, and the position attribute 015 for each base ID (example of object ID and area ID). The version (version value) that is updated with the current version is described in chronological order up to the next generation version of the current version, and for each version (version value), the start time at which the version becomes valid and the end at which it becomes invalid Time is described.
As described above, the version management table 016 is an example of version information.

  FIG. 9 is a schematic diagram showing an example of the site management 017 in FIG.

In FIG. 9, the base management 017 is composed of a base ID, a group ID, and a base name column.
The base ID is an identifier for distinguishing the base 030 and is numbered by the base management 017 as a unique value.
The group ID is an identifier that defines the group of the base 030, and base IDs having the same group ID belong to the same group. The site name is descriptive information that can be referred to when the user identifies the site.
In the base management 017, there may be a column of information about the base other than these columns.

FIG. 10 shows the relationship among the measurement value attribute 012, measurement value / column correspondence 013, device attribute 014, position attribute 015, version management 016, site management 017, and sensor DB 006 in the configuration information DB 011.
FIG. 10 is a relationship diagram showing the data configuration of the configuration information DB 011 in FIG.
10, components having the same reference numerals as those in FIG. 1 indicate the same contents as those in FIG.

The measured value attribute 012, measured value / column correspondence 013, device attribute 014, location attribute 015, and version management 016 all have a base ID column, and the base ID value is managed by the base management 017.
That is, the data storage device 001 according to the present embodiment uses the base ID (example of the object ID) for the measurement value attribute 012, the measurement value / column correspondence 013, the device attribute 014, the position attribute 015, and the version management 016. Process.
The measurement value attribute 012 has a device ID as information of a measurement value measurement device and a position ID as location information related to the measurement value, and these values are managed by the device attribute 014 and the position attribute 015, respectively.
The measured value / column correspondence 013 has a measured value ID as measured value information, and the measured value ID is managed by a measured value attribute 012.
The measured value / column correspondence 013 includes server, table, and output column information as measurement value storage destination information, and the corresponding column of the measured value table 040 in the sensor DB 006 is specified based on these pieces of information.
As described above, the measurement value attribute 012, the measurement value / column correspondence 013, the device attribute 014, and the position attribute 015 are all in the corresponding version range (effective until the record contents are changed after the record is provided in the table). Version range information) has a column of start version name and end version name, and the version value and the start time when each version becomes valid and the end time when it becomes invalid are managed by version management 016 .

Next, the operation will be described.
The operation of the data storage device 001 shown in FIG. 1 includes three main operations: change of configuration information, storage of data from a device, and search of stored data.
These three operations will be described in order.

First, the change of configuration information will be described.
FIG. 11 is a flowchart showing the procedure for changing the configuration information in the data storage apparatus shown in FIG.

First, in step S001, if the change target is information related to the base, the process proceeds to step S008, and if not, the process proceeds to step S002.
In step S002, processing to be executed is determined according to the operation content.
When adding new data to the configuration information DB 011, the process proceeds to step S 003, when rewriting existing data, the process proceeds to step S 004, and when deleting existing data, the process proceeds to the step S 005.
Here, configuration information that can be added, rewritten, and deleted is a measurement value attribute 012, a measurement value / column correspondence 013, a device attribute 014, and a position attribute 015.
Version management 016 is added and updated in step S007.
The site management 017 is executed in step S008.

In step S003, new data is added to the configuration information DB 011.
That is, a record is added to any one of the measurement value attribute 012, the measurement value / column correspondence 013, the device attribute 014, and the position attribute 015.
In the data addition process, configuration information setting APP018 is used.
After completion of the addition, the process proceeds to step S006.

In step S004, the existing data in the configuration information DB 011 is rewritten.
That is, the content of any one of the measurement value attribute 012, measurement value / column correspondence 013, device attribute 014, and position attribute 015 is rewritten.
In the data rewriting process, the configuration information setting APP018 is used.
After completion of the update, the process proceeds to step S006.

In step S005, the existing data in the configuration information DB 011 is deleted.
That is, any one of the measurement value attribute 012, measurement value / column correspondence 013, device attribute 014, and position attribute 015 is deleted.
In the data deletion process, the configuration information setting APP018 is used.
After completion of deletion, the process proceeds to step S006.

In step S006, if all the changes to the configuration information DB 011 have been completed, the process proceeds to step S007, and if not, the process proceeds to step S002.
In step S007, the version of the configuration information DB 011 is revised.
That is, a process for describing the end time of the CUR version (current version) managed by the version management 016, a process for changing the NEXT version (the next generation version of the current version) to a new CUR version, Processing for describing the start time of the CUR version is performed.
The configuration information setting APP018 is used for the revision process of the version.

In step S008, the data for the base management 017 is changed.
Configuration information setting APP018 is used for the data change processing.
As described above, the data of the configuration information DB 011 is changed.

  Details of the processing of steps S003, S004, S005, S007, and S008 in FIG. 11 will be described.

  FIG. 12 is a flowchart showing the flow of data addition processing to the configuration information in step S003 in FIG.

First, in step S011, information related to additional data is input through configuration information setting APP018.
As information about the additional data, the information type to be added (any one of the measurement value attribute 012, the measurement value / column correspondence 013, the device attribute 014, and the position attribute 015), the column data excluding the start version name and the end version name, Become.
In step S012, the configuration information update unit 008 uses a column (data identification column) for identifying a record to check whether additional data exists in the table of addition target information.
The data identification column includes a combination of the base ID and the measurement value ID in the measurement value attribute 012, a combination of the base ID and the measurement value ID in the measurement value / column correspondence 013, a combination of the base ID and the device ID in the device attribute 014, and a position attribute 015. Then, it becomes a combination of the base ID and the position ID.
If it is determined in step S013 that the same data as the data identification column of the additional data already exists in the addition target table, the process proceeds to step S014. Otherwise, the process proceeds to step S015.
In step S014, the configuration information setting APP018 performs error processing for the reason of adding duplicate data.
In step S015, additional data is inserted into the addition target table.
At this time, a version name having a base ID equal to the base ID of the additional data from the version management 016 and a state of NEXT is acquired and set as the start version name. VER_MAX is set as the end version name.
As described above, the process of adding data to the configuration information DB 011 can be executed.

Here, a specific example of adding a new record to the measurement value attribute table 014 will be described with reference to FIG.
Note that the state of the version management 016 when a new record 0121 (an example of an update target record) is added is as shown in FIG.
When performing update to add a new record 0121 to the measurement value attribute table 014 (S015), the configuration information update unit 008 performs version management 016 on the version name “3” of the NEXT version ID of base 100 of this record 0121. NEXT version name “3” is described in the start version name field of record 0121, and VER_MAX meaning “undecided” is described in the end version name field of record 0121.

  FIG. 13 is a flowchart showing the flow of the configuration information data update process in step S004 in FIG.

First, in step S021, information related to rewrite data is input through configuration information setting APP018.
Information related to rewrite data includes information type to be updated (any one of measurement value attribute 012, measurement value / column correspondence 013, device attribute 014, and position attribute 015), data identification column, data identification column, start version name, and end It becomes the data of the column that rewrites the data in the column other than the version name.
In step S022, the configuration information update unit 008 checks whether data (rewrite target data) having a data identification column equal to the value of the data identification column of the rewrite data and an end version name of VER_MAX exists in the rewrite target table.
If rewrite target data exists in step S023, the process proceeds to step S025. If not, the process proceeds to step S024.
In step S024, the configuration information setting APP018 performs error processing because there is no data to be rewritten.
In step S025, the configuration information update unit 008 obtains the data state value (starting version name state) from the version management 016 where the base ID is equal to the base ID of the data to be rewritten and the version name is equal to the starting version name of the data to be rewritten. Investigate.
If the state of the start version name is NEXT in step S026, the process proceeds to step S029, and if not, the process proceeds to step S027.
In step S027, the configuration information update unit 008 acquires from the version management 016 the version name of which the base ID is the same as the base ID of the data to be rewritten and the state is CUR, and the final version of the rewrite target data in the rewrite target table with the version name. Update the name.
In step S028, the configuration information update unit 008 reflects the contents of the rewrite data in the rewrite target data and newly inserts it into the rewrite target table. At this time, a version name having a base ID equal to the base ID of the data to be rewritten from the version management 016 and a state of NEXT is acquired from the version management 016 and set. VER_MAX is set to the end column name.
In step S029, the configuration information update unit 008 updates the rewrite target data in the rewrite target table using the rewrite data. At this time, the data identification column, start version name, and end version name columns are not updated.
As described above, the data rewriting process for the configuration information DB 011 can be executed.

Here, a specific example of rewriting the record of the measurement value attribute table 014 will be described with reference to FIG.
Note that the state of the version management 016 when processing is performed on the record 0120, the record 0122, and the record 0123 (all of which are update target records) is as shown in FIG.
Note that the record 0120 is an existing record whose end version name is updated in step S027 in FIG. 13 (a record whose start version name is not the NEXT version name).
A record 0122 is a record in which the rewritten data added in step S028 in FIG. 13 is described.
The record 0123 is an existing record (a record whose start version name is NEXT whose data is rewritten in step S029 in FIG. 13).

First, the record 0120 and the record 0122 will be described.
In the determination of step S026 in FIG. 13, since the start version name of the record 0120 is “1” and not NEXT, in step S027, the configuration information update unit 008 uses the CUR version name of the base ID: 100 of this record 0120. A certain “2” is acquired from the version management 016, and the CUR version name “2” is described in the end version name field of the record 0120. Note that the contents of the record 0120 other than the end version name are not changed.
Next, in step S028, the configuration information update unit 008 acquires “3”, which is the NEXT version name of the base ID: 100 of the record 0122 including the rewritten data, from the version management 016, and the NEXT version name. “3” is described in the field of the start version name of the record 0122. Also, VER_MAX, which means “undecided”, is set as the final version name.

Next, rewriting of the record 0123 will be described.
Here, it is assumed that only the record 0123 is rewritten and the above-described record 0120 is not rewritten.
Since the start version name of the record 0123 is “3” and NEXT, in step S029, the data of the record 0123 is rewritten (rewriting the device ID) without changing the description of the start version name and the end version name.

  FIG. 14 is a flowchart showing the flow of the configuration information data deletion process in step S005 in FIG.

First, in step S041, information related to deletion data is input by configuration information setting APP018.
The information related to the deletion data includes the information type to be deleted (any one of the measurement value attribute 012, the measurement value / column correspondence 013, the device attribute 014, and the position attribute 015) and the data identification column.
In step S042, the configuration information update unit 008 checks whether there is data (deletion target data) whose data identification column is equal to the value of the data identification column of the deletion data and whose end version name is VER_MAX in the deletion target table.
If it is determined in step S043 that the data to be deleted exists, the process proceeds to step S045. If not, the process proceeds to step S044.
In step S044, the configuration information setting APP018 performs error processing because there is no data to be deleted.
In step S045, the configuration information update unit 008 determines the value of the data state from the version management 016 where the base ID is equal to the base ID of the deletion target data and the version name is equal to the start version name of the deletion target data (start version name state) Check out.
If the state of the start version name is NEXT in step S046, the process proceeds to step S048, and if not, the process proceeds to step S047.
In step S047, the configuration information update unit 008 acquires from the version management 016 the version ID having the base ID equal to the base ID of the data to be deleted and the state of CUR, and ends the deletion target data in the deletion target table with the version name. Update the version name.
In step S048, the configuration information update unit 008 deletes the deletion target data in the deletion target table.
In step S049, the configuration information update unit 008 acquires from the version management 016 a version name whose base ID is equal to the base ID of the deleted data and whose state is CUR.
Then, data whose version name and end version name are the same and whose base ID is the same as the base ID of the deletion data is acquired from the deletion target table.
In step S050, the configuration information update unit 008 updates the end version name of the data in the deletion target table with respect to the data acquired in step S049 to VER_MAX.
As described above, the data deletion process for the configuration information DB 011 can be executed.

Here, a specific example of deleting a record in the measurement value attribute table 014 will be described with reference to FIG.
Note that the state of the version management 016 when processing is performed on the record 0120, the record 0124, and the record 0125 (all of which are update target records) is as shown in FIG.
Note that the record 0120 is an existing record whose end version name is updated in step S047 of FIG. 14 (a record whose start version name is not the NEXT version name).
The record 0124 is an existing record whose end version name is updated in step S050 of FIG. 14 (a record whose start version name is not the NEXT version name).
The record 0125 is an existing record that is deleted in step S048 of FIG. 14 (a record whose start version name is NEXT).

First, the record 0120 will be described.
In the determination in step S046 in FIG. 14, the start version name of the record 0120 is “1” and not NEXT. A certain “2” is acquired from the version management 016, and the CUR version name “2” is described in the end version name field of the record 0120. Note that the contents of the record 0120 other than the end version name are not changed.

Next, deletion of the record 0125 and update of the end version name of the record 0124 will be described.
Here, it is assumed that only the deletion of the record 0125 occurs and the deletion of the record 0120 described above does not occur.
Since the start version name of the record 0125 is “3” and NEXT, the configuration information update unit 008 deletes the record 0125 in step S048.
Next, in step S049, the configuration information update unit 008 acquires the version name “2” of the CUR with the base ID: 100 of the record 0125 from the version management 016 in step S049.
Next, the configuration information update unit 008 extracts the record 0124 having the base ID: 100 and the end version name “2”, and changes the end version name of the record 0124 to VER_MAX meaning undecided in step S050. To do.

As described with reference to FIGS. 21 to 23, when the same base ID is described in two or more records in the same table, the start version name of another record having the same base ID as the record to be updated The version name acquired from the version management 016 is described in the start version name and / or end version name of the record to be updated without changing the description of the end version name.
Then, as will be described later, the version information update unit 007 displays the update time in the update target record even if there is no change in the record contents in another record in which the same base ID as the base ID of the update target record is described. The information is reflected in the management 016, and the generation of the version to be CUR and NEXT is updated.

  FIG. 15 is a flowchart showing the flow of the revision process of the version of the configuration information in step S007 in FIG.

First, in step S061, instruction information related to the revision is input by the configuration information setting APP018. The revision instruction information includes the base ID to be revised and the revision date and time (update time when one of the records of the measurement value attribute 012, the measurement value / column correspondence 013, the device attribute 014, and the position attribute 015 is updated).
In step S062, the version information update unit 007 acquires data of the base ID to be revised from the base management 017 and checks the value of the group ID.
When the value of the group ID is null, the site ID does not belong to the group, so the revision target is only the site ID input in step S061.
If the group ID value is not null, all base IDs having the same group ID are acquired from the base management 017.
All the base IDs acquired here are subject to revision, and Steps S063 to S065 are executed for each base ID.
In step S063, the version information update unit 007 updates the status to PAST and the end date / time to the revised date / time for data whose version ID is the same as the base ID to be revised in version management 016.
In step S 064, the version information update unit 007 updates the status to CUR, the start date / time to the revised date / time, and the end date / time to TIMESTAMP_MAX for data whose version ID is the same as the revision-target site ID in version management 016. .
In step S065, the version information update unit 007 adds a version management 016 with a base ID to be revised as a base ID, a version name plus a version interval unit (for example, 1) to the version name of the data updated in step S064, Insert data with NEXT set to state.
If it is determined in step S066 that there is an unprocessed base ID among the revision-target base IDs, the process proceeds to step S063, where the unprocessed base ID is processed.
As described above, the revision process of the version of the configuration information DB 011 can be executed.

  FIG. 16 is a flowchart showing the flow of the data change process for the base management 017 in step S008 in FIG.

First, in step S101, operation instruction information related to base change is input by configuration information setting APP018.
As the operation instruction information, a base change operation (addition or deletion), additional data to the base management 017 in the case of addition, and a base ID to be deleted in the case of deletion.
If the change operation is added in step S102, the process proceeds to step S103. If the change operation is to be deleted, the process proceeds to step S105.
In step S103, the configuration information update unit 008 inserts additional data into the base management 017.
In step S <b> 104, the version information update unit 007 inserts into the version management 016 data with the base ID of the additional data as the base ID, the initial value of the version (for example, 1) as the version name, and NEXT as the state.
In step S105, the configuration information update unit 008 applies to all the tables (measurement value attribute 012, measurement value / column correspondence 013, device attribute 014, location attribute 015, version management 016, site management 017) of the configuration information DB 011. Data whose base ID is equal to the base ID to be deleted is deleted.
As described above, the data change process for the base management 017 of the configuration information DB 011 can be executed.

The change operations executed in steps S003, S004, and S005 in FIG. 11 can be canceled all at once before execution of step S007.
FIG. 17 is a flowchart showing the flow of change cancellation processing in steps S003, S004, and S005.

First, in step S071, the base ID to be canceled is input by the configuration information setting APP018.
In step S072, the configuration information update unit 008 acquires from the version management 016 a version name whose base ID is equal to the base ID to be canceled and whose state is NEXT.
For all of the measurement value attribute 012, the measurement value / column correspondence 013, the device attribute 014, and the position attribute 015, data whose base ID is equal to the base ID to be canceled and whose start version name is equal to the acquired version name is deleted.
In step S073, the configuration information update unit 008 acquires from the version management 016 a version name whose base ID is equal to the base ID to be canceled and whose state is CUR.
For all of the measurement value attribute 012, measurement value / column correspondence 013, device attribute 014, and position attribute 015, the end version name of the data whose base ID is equal to the base ID of the cancellation target and whose end version name is equal to the acquired version name Is updated to VER_MAX.
As described above, the change canceling process in steps S003, S004, and S005 can be executed.

Next, storage of data from the device will be described.
FIG. 18 is a flowchart showing the flow of data storage processing from the device in the data storage device shown in FIG.

First, in step S081, the data collection unit 032 collects data from the sensor device 031 at regular time intervals and transmits the collected data to the data reception unit 002.
At this time, the data collection unit 032 adds the data measurement value ID, the date and time of occurrence, and the base ID of the base 030 to the data as additional information and transmits the data.
Note that the measurement value ID and the site ID may not be added by the data collection unit 032 but may be added to the data when received by the data reception unit 002.
In step S082, the data reception unit 002 delivers the received data set and parameters indicating the operation mode to the data storage unit 003.
The parameter indicating the operation mode has a value of either an actual operation or a test operation, and the mode is specified when the data receiving unit 002 is activated, and becomes an actual operation mode in normal execution.
In the data storage unit 003, data is classified and grouped for each occurrence date and time in units of base IDs.
In step S083, the data storage unit 003 makes an inquiry to the configuration information search unit 009 with respect to individual data of the grouped data group using the base ID, measurement value ID, and occurrence date and time as parameters, and stores the data. Get the destination (server, table, output column).
In step S084, the data storage unit 003 assembles a record for each table according to the data storage destination table and output column information acquired in step S083, and outputs the records to the corresponding table of the sensor DB 006.
As described above, the data from the device is stored in the sensor DB 006 according to the information in the configuration information DB 011.

Details of the processing of the configuration information search unit 009 in step S083 in FIG. 18 will be described.
FIG. 19 is a flowchart showing the flow of configuration information search processing in the configuration information search unit 009.

First, in step S091, the configuration information search unit 009 inputs a search condition for the configuration information DB 011.
Search conditions include a search target (measurement value attribute 012, measurement value / column correspondence 013, device attribute 014, position attribute 015), output target, extraction condition, and the like.
In the case of step S083 in FIG. 18, the search target is the measurement value / column correspondence 013, the output target is the server, the table, the output column, the extraction condition is the base ID, the equality condition for the measurement value ID, and the date / time designation.
In step S092, it is checked whether there is an extraction condition for the version name of the data in the configuration information DB 011 as a search condition. If there is a condition, the process proceeds to step S098, and if not, the process proceeds to step S093.
In the case of step S083, since there is no condition, the process proceeds to step S093.
In step S093, it is checked whether there is an extraction condition for specifying date and time as a search condition. If there is a condition, the process proceeds to step S095, and if not, the process proceeds to step S094. In the case of step S083, since the date and time is specified, the process proceeds to step S095.
In step S094, the version name of the status CUR is acquired from the version management 016.
At this time, if there is an extraction condition for the base ID, the corresponding base ID is executed, and if there is no condition, it is executed for all base IDs.
In the case of step S083, this step is not executed.
In step S095, it is checked whether the date / time designation value is date / time data or null.
If date / time data is specified as the value, the process proceeds to step S096. If null is specified as the value, the process proceeds to step S097.
In the case of step S083, since date / time data is normally designated as a value, the process proceeds to step S096.
In step S096, the version name to be searched is derived from the version management 016 based on the date and time designation. A version name satisfying the condition that the value (target date and time) specified from the version management 016 does not exceed the end date and time after the start date and time (start date and time <target date and time <end date and time) is acquired.
At this time, if there is an extraction condition for the base ID, the corresponding base ID is executed, and if there is no condition, it is executed for all base IDs. In the case of step S083, one version name is acquired from the base ID and date designation.
In step S097, a version name having a start date and time value of null is acquired.
Since the state of the version name whose start date and time value is null is NEXT, the version name whose state is NEXT is acquired.
At this time, if there is an extraction condition for the base ID, the corresponding base ID is executed, and if there is no condition, it is executed for all base IDs. In step S083, this step is not normally executed.
In step S098, a condition that the version name is greater than or equal to the start version name and less than or equal to the end version name (start version name ≦ version name ≦ end version name) is generated.
The condition is added to the search condition input in step S091, the search process of the configuration information DB 011 is executed, and the result is returned.
In the case of step S083, the extraction condition search processing is executed by adding the version name condition to the base ID and the equality condition for the measurement value ID for the measurement value / column correspondence 013. As a result, the server, the table, and the output string are obtained. return.
As described above, the configuration information search process corresponding to the required version name can be executed from the configuration information DB 011.

When storing data from the device and performing data storage using configuration information corresponding to the version name of NEXT as a test operation, the data receiving unit 002 that receives the data of the test operation is activated in the test operation mode.
In step S082 of FIG. 18, the data receiving unit 002 notifies the data storage unit 003 that it is in the test operation mode, and the data storage unit 003 sets the occurrence date and time value to null when making an inquiry to the configuration information search unit 009 in step S083. By doing so, the configuration information corresponding to the version name of NEXT can be acquired.

The search for the last stored data will be described.
FIG. 20 is a flowchart showing the flow of search processing for stored data in the data storage device 001 shown in FIG.

First, in step S111, data search conditions are input from the search APP020.
The search conditions include the base ID of the target base 030, the measurement value table to be searched, the output target column, the extraction condition, and the like, the version name and information type of the output target configuration information, the output target column, and the like. .
The input search condition is passed to the sensor DB search unit 019.
In step S112, the sensor DB search unit 019 checks whether there is a date and time designation as an extraction condition for the measurement value table. If there is a designation, the process proceeds to step S116. If not, the process proceeds to step S113.
In step S113, the sensor DB search unit 019 checks whether the version name of the configuration information to be output has been specified. If so, the process proceeds to step S115. If not, the process proceeds to step S114.
In step S114, the sensor DB search unit 019 inquires of the configuration information search unit 009 about the version name of the CUR state using the base ID input in step S111 as a parameter.
In the configuration information search unit 009, the value of the base ID from the version management 016 is the same as the base ID passed from the sensor DB search unit 019, and the version name having the state CUR is searched and returned to the sensor DB search unit 019.
In step S115, the sensor DB search unit 019 inquires of the configuration information search unit 009 about the start date / time and the end date / time of the version using the site ID and the version name as parameters.
The configuration information search unit 009 acquires the start date / time and end date / time of the data whose base ID and version name are the same as the values passed from the sensor DB search unit 019 from the version management 016, and returns them to the sensor DB search unit 019.
The sensor DB search unit 019 uses the acquired start date / time and end date / time to generate a date / time specification condition (start date / time ≦ occurrence date / end date / time) for the measurement value table.
In step S116, the sensor DB search unit 019 specifies search conditions such as a measurement value table, an output target column, a date and time designation condition, and an extraction condition other than the date and time designation condition input in step S111, and the data search unit 004 A search query for the sensor DB 006 is made.
The data search unit 004 uses the DB management unit 005 to execute search processing according to the search condition, and passes the result to the sensor DB search unit 019.
In step S117, the sensor DB search unit 019 uses the version name and information type of the output target configuration information input in step S111, the output target column, and the date / time designation (when date / time designation for the measurement value table) as parameters. An inquiry is executed to the search unit 009.
The configuration information search unit 009 searches for configuration information based on the parameters.
The processing here is as shown in the flowchart of FIG.
The search result is returned to the sensor DB search unit 019.
In step S118, the sensor DB search unit 019 combines the data obtained in step S116 with the configuration information obtained in step S118, and returns it to the search APP020, and the search APP020 outputs the data and configuration information.
As described above, the data stored in the sensor DB 006 can be searched together with the corresponding configuration information in the configuration information DB 011.

  When searching the stored data using the configuration information corresponding to the NEXT version name as a test operation, the stored data can be searched by specifying the NEXT version name as the search condition. .

As described above, the configuration information is also managed for each version as a history of changed data, so even if the configuration information is changed, the configuration information before the change is not lost, and the configuration information is thereby changed. For the corresponding data, the data accumulated before the change can be used.
Further, since the next version is defined in addition to the history / current version as the state of the configuration data version data, the next version data can be registered in the configuration information database.
Furthermore, since the next version of the version data is generated in advance at the time of revision regardless of whether or not the configuration information is changed, no change process for the version information is required when the configuration information is changed.
In addition, when the configuration information is changed, the current version of the data is not updated and the next version of the data is operated, so the confirmed data is not lost and is stored as a history, and only one data is changed. No data remains in the middle of the change.
Furthermore, since the search for the configuration information can be performed under conditions based on the date and time designation, no information about the version is required on the sensor DB side, and the search operation can be performed without being aware of the version.
In addition, since it can be ensured that the configuration information of the next version does not meet the date and time designation condition until the revision of the version, the configuration information can be changed in parallel with the data storage process (configuration information search).
Furthermore, since the configuration information of the next version being changed can be searched, a test operation using the configuration information of the next version can be performed in parallel with the actual operation.
In addition, the revision process of the version of the configuration information is completed only by the process for the version information, so that the revision process can be made more efficient by eliminating the process for each piece of configuration information (processing steps, shortening the execution time). .
Furthermore, since the setting of the end date and time of the version accompanying the revision of the version can be designated at an arbitrary date and time, the revision of the version can be performed in the future or when going back in the past.
Further, since the configuration information and version management information are managed in units of bases, the configuration information can be operated for each base as independent information for each base, and data from a plurality of bases can be handled.
Furthermore, since a set of a plurality of bases can be defined and the revision of the configuration information is synchronized for each set of bases, it is possible to manage versions across a plurality of bases.

As described above, in the present embodiment, the configuration information management apparatus including the following in the data storage apparatus that collects data from a plurality of devices and enables data storage and retrieval has been described.
(A) Configuration information consisting of component data having information on equipment, collected data, data storage location, etc., and information on the start version name and end version name of the version to which the information corresponds;
(B) Version management information which is composed of version data having the version name and status of the configuration information, the start date and time, and the end date and time, and the status of the version data is one of three values of history / current version / next version;
(C) Configuration information database comprising configuration information and version management information;
(D) Configuration information updating means for registering and updating configuration information;
(E) Version information updating means for revising the version of configuration information;
(F) Configuration information retrieval means for retrieving configuration information from the configuration information database.

  In addition, it has been described that (b) the version data of the next version is prepared in advance in the (b) version management information regardless of the presence or absence of the component data corresponding to the next version in the (a) configuration information.

In the (d) configuration information updating means,
When adding component data to the configuration information, insert the component data by setting the version name of the version data of the next version as the start version name of the component data to be added,
When changing the component data in the configuration information, if the status of the version data set in the starting version name of the component data to be changed is the next version, the component data to be changed is directly updated and the status is next If it is not a version, the end version name of the component data to be changed is updated to the version name of the current version data, and the changed component data has the start version name and the version data version of the next version data. Insert a new name
When deleting the component data of the configuration information, if the status of the version data set in the starting version name of the component data to be deleted is the next version, the component data to be deleted is deleted directly and the status is If it is not the next version, the final version name of the component data to be deleted is updated to the version name of the current version data,
(E) When the version of the configuration information is revised in the version information updating means, the status is updated to the history for the version data of the current version and the end date is set, and the status is set for the version data of the next version. We explained that the configuration information database is changed by updating to the current version, setting the start date and time, and inserting the new version of the version data.

  In addition, in the (e) version information updating means, the end date and time of the version data whose status is updated from the current version to the history by the revision of the configuration information and the start date and time of the version data whose status is updated from the next version to the current version are arbitrary. It was explained that the date and time can be specified, so that the version change time can be set in the future or when going back in the past.

  In the (f) configuration information search means, if the version name is specified in the search condition, the specified version name is specified. If not, the start date / time of the version management information is determined from the date / time specification condition. It has been described that the configuration information corresponding to the version name is extracted from the information of the start version name and end version name of the configuration information (a) using the version name of the version data derived from the end date and time.

  Also, it is explained that in the configuration information search means, when the date is specified as the search condition, the configuration information corresponding to the next version is not extracted, and the configuration information corresponding to the history or the current version is always extracted. did.

In addition, it has been described that the data storage device further includes the following elements.
(G) a database for accumulating data from equipment;
(H) data collection means for collecting data from a plurality of devices;
(I) (h) data receiving means for receiving data from the data collecting means;
(J) Based on (a) configuration information in the (c) configuration information database, (i) data storage means for storing data received from the data reception means in the database;
(K) (g) data retrieval means for retrieving data from the database;
(L) Database search means for searching for data by using a combination of (f) configuration information search means and (k) data search means;

  Further, in the (j) data storage means, the information on the data storage location is obtained from the version of the configuration information corresponding to the data by the (f) configuration information search means based on the date / time information of the data, and stored in the predetermined storage location. Explained storing data.

  In the (l) database search means, the data from the device is acquired by the (k) data search means based on the date and time designation condition, and the configuration information corresponding to the data is acquired by the (f) configuration information search means. Thus, it has been explained that the configuration information corresponding to the data is acquired simultaneously.

In addition, the (h) data collection means exist independently at a plurality of remote sites, and the following information is added to the (c) configuration information database, and the (a) configuration information and (b) version Explained that base information is added to management information.
(M) Base management information composed of base data having information regarding the base to which the configuration information and version management information belong.

  In the (d) configuration information update unit, the (e) version information update unit, and the (f) configuration information search unit, (h) the configuration information of the operation target from the site data corresponding to the site to which the data collection unit belongs, and Explained the identification of version management information.

Finally, a hardware configuration example of the data storage device 001 shown in the first embodiment will be described.
FIG. 24 is a diagram illustrating an example of hardware resources of the data storage device 001 illustrated in the first embodiment.
Note that the configuration in FIG. 24 is merely an example of the hardware configuration of the data storage device 001. The hardware configuration of the data storage device 001 is not limited to the configuration described in FIG. Also good.

In FIG. 24, the data storage device 001 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program.
The CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
Further, the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907. Further, instead of the magnetic disk device 920, a storage device such as an SSD (Solid State Drive), an optical disk device, or a memory card (registered trademark) read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
The “configuration information DB” and “sensor DB” described in the first embodiment are realized by the magnetic disk device 920 or the like.
A communication board 915, a keyboard 902, a mouse 903, a scanner device 907, an FDD 904, and the like are examples of input devices.
The communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.

As shown in FIG. 1, the communication board 915 is connected to a network.
For example, the communication board 915 may be connected to a LAN (local area network), the Internet, a WAN (wide area network), a SAN (storage area network), or the like.

The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
The programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.

The RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
The RAM 914 stores various data necessary for processing by the CPU 911.

The ROM 913 stores a BIOS (Basic Input Output System) program, and the magnetic disk device 920 stores a boot program.
When the data storage device 001 is activated, the BIOS program in the ROM 913 and the boot program in the magnetic disk device 920 are executed, and the operating system 921 is activated by the BIOS program and the boot program.

  The program group 923 stores programs that execute the functions described as “˜unit” and “˜means” in the description of the first embodiment. The program is read and executed by the CPU 911.

In the description of the first embodiment, the file group 924 includes “determination of”, “addition of”, “rewrite of”, “deletion of”, “update of”, “revision of”, Results of processes described as “confirmation of”, “examination of”, “comparison of”, “extraction of”, “setting of”, “registration of”, “selection of”, etc. Information, data, signal values, variable values, and parameters indicating “” are stored as items of “˜file” and “˜database”.
The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory.
Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit.
The read information, data, signal value, variable value, and parameter are used for CPU operations such as extraction, search, reference, comparison, calculation, calculation, processing, editing, output, printing, and display.
Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
In addition, the arrows in the flowchart described in the first embodiment mainly indicate input / output of data and signals.
Data and signal values are recorded on a recording medium such as a memory of the RAM 914, a flexible disk of the FDD 904, a compact disk of the CDD 905, a magnetic disk of the magnetic disk device 920, other optical disks, a mini disk, and a DVD.
Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

In the description of the first embodiment, what is described as “to part” and “to means” may be “to circuit”, “to device”, and “to device”. It may be “step”, “˜procedure”, “˜processing”.
That is, the “data processing method” according to the present invention can be realized by the steps, procedures, and processes shown in the flowchart described in the first embodiment.
In addition, what is described as “˜unit” and “˜means” may be realized by firmware stored in the ROM 913.
Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware.
Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD.
The program is read by the CPU 911 and executed by the CPU 911.
That is, the program causes the computer to function as “to part” and “to means” in the first embodiment. Alternatively, the procedure and method of “˜unit” and “˜means” of the first embodiment are executed by a computer.

As described above, the data storage device 001 described in Embodiment 1 includes a CPU as a processing device, a memory as a storage device, a magnetic disk, a keyboard as an input device, a mouse, a communication board, and a display device as an output device, a communication board, and the like. It is a computer provided with.
As described above, the functions indicated as “˜unit” and “˜means” are realized by using these processing devices, storage devices, input devices, and output devices.

  001 data storage device, 002 data reception unit, 003 data storage unit, 004 data search unit, 005 DB management unit, 006 sensor DB, 007 version information update unit, 008 configuration information update unit, 009 configuration information search unit, 010 configuration information DB management unit, 011 configuration information DB, 012 measurement value attribute table, 013 measurement value / column correspondence table, 014 device attribute table, 015 location attribute table, 016 version management table, 017 site management table, 018 configuration information setting APP, 019 Sensor DB search unit, 020 search APP, 030 base, 031 sensor device, 032 data collection unit, 500 network.

Claims (16)

A data processing device that performs data processing using a plurality of object IDs (Identification) for identifying a plurality of management objects,
A table data storage unit that includes a plurality of records and stores one or more table data in which any object ID is described in each record;
A table data management unit that updates table data in units of records;
For each object ID, a version value that is updated as the table data is updated by the table data management unit is described in chronological order until at least the current version, and the start time at which the version becomes valid for each version value And a version information storage unit for storing version information in which an invalid end time is described,
A version management unit that updates the version information when any table data is updated by the table data management unit;
The table data storage unit
Each record includes one or more table data including a version range field for describing a range of version values corresponding to the validity period from when the record is provided to the table data until the record content is changed Remember,
The table data management unit
When updating any of the table data, the version value of the current version of the object ID described in the update target record to be updated and the next generation of the current version according to the update form of the table data Acquiring at least one of the version values of the version from the version information storage unit, describing the acquired version value in the version range field of the update target record, and updating the table data;
The version management unit
The update time when the table data management unit has updated the table data and the object ID described in the update target record are notified, and the notified update time is used as the end time of the current version of the notified object ID. Described in the version information, described in the version information such that the next generation version of the current version of the notified object ID becomes the new current version of the object ID, and the notified update time A data processing apparatus characterized in that it is described in the version information as the start time of a new current version. The table data management unit
2. The data processing apparatus according to claim 1, wherein the table data is updated while maintaining contents other than the version range field described in each record before updating. The table data storage unit
Stores table data in which the same object ID is described in two or more records,
The table data management unit
When updating the table data in which the object ID described in the update target record is also described in another record, the description of the version range field of the other record is not changed, and the update target record Describe the version value acquired from the version information storage unit in the version range field,
The version management unit
When the table data management unit is notified of the update time when the table data is updated and the object ID described in the update target record, the same object ID as the object ID of the update target record is described. Even if there is no change in record contents in other records, the update time notified is described in the version information as the end time of the current version of the notified object ID, and the current version of the notified object ID Describing in the version information such that the next generation version becomes the new current version of the object ID, and describing the notified update time in the version information as the start time of the new current version. The data processing apparatus according to claim 1 or 2, characterized in that The table data storage unit
The version range field includes a record divided into an initial subfield for describing a version value corresponding to the beginning of the effective period and an end subfield for describing a version value corresponding to the end of the effective period. Stores table data,
The table data management unit
When updating to add a new record to any of the table data, the newly added record is the update target record, and the version of the next generation of the current version of the target object ID described in the update target record The version value is acquired from the version information storage unit, the acquired version value of the next-generation version is described in the start subfield of the update target record, and information meaning “undecided” is used as the end subfield of the update target record The data processing apparatus according to any one of claims 1 to 3. The table data storage unit
The version range field includes a record divided into an initial subfield for describing a version value corresponding to the beginning of the effective period and an end subfield for describing a version value corresponding to the end of the effective period. Stores table data,
The table data management unit
When performing an update that rewrites the data of a record included in any of the table data, the record to be rewritten is set as the update target record, and is next to the current version of the object ID described in the update target record. Determine whether the version value of the version of the next generation is described in the start subfield of the record to be updated,
When the version value of the next generation version is described in the start subfield, the data of the update target record is rewritten without changing the description of the start subfield and the end subfield,
If a version value other than the next generation version is described in the start subfield, the version value of the current version of the object ID described in the update target record and the version value of the next generation version of the current version are displayed. Acquired from the version information storage unit, the version value of the acquired current version is described in the final subfield of the record to be updated, and is a new record including the rewritten data and acquired from the version information storage unit A new record is generated in which the version value of the next generation version is described in the initial subfield, the information indicating undecided is described in the final subfield, and the generated new record is added to the table data. And any one of claims 1 to 4 Over data processing apparatus. The table data storage unit
The version range field includes a record divided into an initial subfield for describing a version value corresponding to the beginning of the effective period and an end subfield for describing a version value corresponding to the end of the effective period. Stores table data,
The table data management unit
When performing an update that deletes a record from any table data, the record to be deleted is set as the update target record, and the version value of the next generation version of the current version of the object ID described in the update target record is Determine whether it is described in the initial subfield of the record to be updated,
When a version value other than the next generation version is described in the initial subfield, the version value of the current version of the object ID described in the update target record is acquired from the version information storage unit, and the acquired current Describe the version value of the version in the end subfield of the record to be updated,
When the version value of the next generation version is described in the initial subfield, the update target record is deleted, the version value of the current version of the target object ID of the update target record is acquired from the version information storage unit, 6. The record in which the version value of the current version is described in an end subfield is extracted, and the end subfield of the extracted record is rewritten with information meaning undecided. Data processing equipment. The version information storage unit
The version information in which version values are described in time series until the next generation version of the current version is stored for each object ID. Data processing device. The table data storage unit
The version range field includes a record divided into an initial subfield for describing a version value corresponding to the beginning of the effective period and an end subfield for describing a version value corresponding to the end of the effective period. Stores table data,
The table data management unit
After updating the one or more table data by describing the version value of the next generation version acquired from the version information storage unit in the initial subfield of one or more records in which the specific object ID is described. When the update performed on one or more table data is canceled before the version information is updated by the version management unit, the specific object ID is described and the specific sub-field is specified in the initial subfield. A record in which the version value of the next-generation version of the object ID is described is extracted from the plurality of table data, the extracted record is deleted, the specific object ID is described, and the specific Extract the record that describes the version value of the current version of the object ID, and end the extracted record The data processing apparatus according to claim 1, characterized in that rewriting the information indicating undetermined subfields. The table data storage unit
The version range field includes a record divided into an initial subfield for describing a version value corresponding to the beginning of the effective period and an end subfield for describing a version value corresponding to the end of the effective period. Stores table data,
The data processing device further includes:
Enter a search condition with a specified version value,
Record search that searches the table data storage unit for records in which the version value before the specified version value specified in the search condition is described in the start subfield and the version value after the specified version value is described in the end subfield The data processing apparatus according to claim 1, further comprising a section. The table data storage unit
The version range field includes a record divided into an initial subfield for describing a version value corresponding to the beginning of the effective period and an end subfield for describing a version value corresponding to the end of the effective period. Stores table data,
The data processing device further includes:
Enter search criteria with a specified time,
The start time before the specified time specified in the search condition is described, and the version value in which the end time after the specified time is described is extracted from the version information,
A record retrieval unit for retrieving from the table data storage unit a record in which a version value before the extracted extracted version value is described in the initial subfield and a version value after the extracted version value is described in the final subfield; The data processing device according to claim 1, wherein the data processing device is a data processing device. The version information storage unit
For each object ID, version information in which version values are described in time series until the next generation version of the current version is stored,
The record search unit
The data processing apparatus according to claim 10, wherein the version value of the next generation version described in the version information is not extracted. The data processing device includes:
The plurality of management objects are set as a plurality of management target areas each having one or more data generation devices,
Each object ID is an area ID for identifying each management target area,
The data processing device further includes:
A data receiving unit that receives data generated by each data generating device as received data;
A reception data storage unit for storing the reception data received by the data reception unit, distinguishing the management target area from the data generation device;
The table data storage unit
A data attribute table data including a plurality of records, each area ID is described in each record, and each record includes a data attribute table data indicating data attributes of data generated in the management target area corresponding to the area ID. In addition, each area ID and any data generation device ID is described in each record, and each record indicates an identifier of a storage area for each management target area and each data generation device in the received data storage unit. Storage area table data, including a plurality of records, each area ID and any data generation device ID is described in each record, and each record is a data generation device in the management target area corresponding to the area ID Storing at least one of the device attribute table data indicating the device attributes of The data processing apparatus according to any one of claims 1 to 11 that. The table data storage unit
Storing at least the storage area table data;
The data processing device further includes:
The record indicating the identifier of the storage area in the received data storage unit corresponding to the received data received by the data receiving unit is set as the ID of the data generating device that generated the received data and the area ID of the management target area. The data processing apparatus according to claim 12, further comprising: a record search unit that extracts from the storage area table data. The data receiver is
Receive the received data together with the data generation time by the data generation device,
The received data storage unit
Store the data generation time in association with the received data,
The data processing device further includes:
A data search unit that inputs a search condition in which a time is specified, and extracts received data that is associated with a data generation time that matches the specified time specified in the input search condition;
A search condition in which the same time as the data search unit is specified is input, a start time before the specified time specified in the input search condition is described, and an end time after the specified time is described A record search unit that extracts a version value from the version information and extracts a record in which a range of version values matching the extracted version value is described in a version range field from the table data storage unit, The data processing apparatus according to claim 12 or 13. Using multiple object IDs (Identification) for identifying multiple managed objects,
A table data storage unit that includes a plurality of records and stores one or more table data in which any object ID is described in each record;
For each object ID, the version value to be updated with the update of the table data is described in time series until at least the current version, and for each version value, the start time at which the version becomes valid and the end time at which the version becomes invalid A data processing method performed by a computer having a version information storage unit that stores version information describing
A table data management step in which the computer updates the table data in units of records;
When any table data is updated by the table data management step, the computer has a version management step for updating the version information,
The computer
In the table data storage unit,
Each record includes one or more table data including a version range field for describing a range of version values corresponding to the validity period from when the record is provided to the table data until the record content is changed Remember,
In the table data management step,
When updating any of the table data, the version value of the current version of the object ID described in the update target record to be updated and the next generation of the current version according to the update form of the table data Acquiring at least one of the version values of the version from the version information storage unit, describing the acquired version value in the version range field of the update target record, and updating the table data;
In the version management step,
The update time when the table data is updated in the table data management step and the object ID described in the update object record are notified, and the end time of the current version of the object ID notified of the notified update time As described in the version information, and described in the version information so that the next generation version of the current version of the notified object ID becomes a new current version of the object ID, and the notified update time A data processing method described in the version information as a start time of the new current version. Using multiple object IDs (Identification) for identifying multiple managed objects,
A table data storage unit that includes a plurality of records and stores one or more table data in which any object ID is described in each record;
For each object ID, the version value to be updated with the update of the table data is described in time series until at least the current version, and for each version value, the start time at which the version becomes valid and the end time at which the version becomes invalid In a computer having a version information storage unit that stores version information describing
A table data management step for updating table data in units of records;
A program for executing a version management step for updating the version information when any table data is updated by the table data management step;
The computer
In the table data storage unit,
Each record includes one or more table data including a version range field for describing a range of version values corresponding to the validity period from when the record is provided to the table data until the record content is changed Remember,
In the table data management step,
When updating any of the table data, the version value of the current version of the object ID described in the update target record to be updated and the next generation of the current version according to the update form of the table data Obtaining at least one of the version values of the version from the version information storage unit, describing the obtained version value in the version range field of the update target record, and causing the computer to execute a process of updating the table data;
In the version management step,
The update time when the table data is updated in the table data management step and the object ID described in the update object record are notified, and the end time of the current version of the object ID notified of the notified update time As described in the version information, and described in the version information so that the next generation version of the current version of the notified object ID becomes a new current version of the object ID, and the notified update time A program for causing the computer to execute a process described in the version information as a start time of the new current version.

Images