JP2007129425A - Data collection method, and data collection device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To securely collect data even in a stage wherein a data collection error is apt to occur. <P>SOLUTION: A data collection device 1 has a collection means of collecting data from devices (a center monitor device 3 and a local monitor device 4), a writing means of writing the collected data to a history file, a decision means of deciding whether a collection error occurs during the collecting of the data, a retrial registering means of registering a device to which a collection error occurs to a retrial list file when it is decided that the collection error occurs, an error registering means of registering the occurrence of the collection error to an error log file when it is decided that the collection error occurs, and a recollecting means of recollecting data from devices registered in the retrial list file and passing the data to the writing means. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a monitoring system such as a building management system and a plant management system, and more particularly to a data collection method and a data collection apparatus for collecting data from devices of the monitoring system for uses other than the monitoring system.

  Data collected by a building management system, a plant management system, or the like may be used for purposes other than the management system. For example, entry / exit data that is originally used for security purposes in a building management system and that is generated by a card reader upon entry / exit of an individual includes entry / exit time information, cardholder information, room location information, etc. Although it is included, attendance management of the personnel management system may be performed using these entrance / exit data. In addition, from the aspect of health and safety management, it is possible to manage whether the stay time exceeds the specified time based on the stay time of one individual's radiation laboratory obtained based on the entry / exit data. .

  As described above, data collected by a building management system, a plant management system, or the like may be used by another management system. And in such a case, since it is data used for personnel management, safety and health management, etc., it is important to collect data reliably. Therefore, since any omission of collection of data becomes a problem, the data collection system is required to collect data reliably.

  Conventionally, data collection has been interrupted due to, for example, line abnormality, and data collection has sometimes been missed. Therefore, a data collection device has been proposed that can re-collect data when data collection is not completed and completed (see, for example, Patent Document 1). The data collection device disclosed in Patent Literature 1 reads that the data collection completion notification written in the automatic log data returned from the data collection destination device does not exist when data collection fails, Re-collect data from the device. Specifically, the data collection retry flag of the device is registered in the execution time table in which the data collection time is written, and the data is collected again. In addition, since recollection is executed sequentially in the order of the devices registered in the execution time table, when recollection is performed, data is collected from the device in which the retry flag is registered.

JP-A-6-141095

  As described above, the data collection device collects data from a large number of devices. At the time of data collection, a large amount of data is collected, so the load on the network increases. When the network load increases, data collection errors caused by network abnormalities such as communication disconnection at the time of data collection, protocol abnormalities, and completion without being able to collect data up to a predetermined size It tends to occur.

  When the re-collection technique using the data collection device described in Patent Document 1 is applied to an environment where the network load is increasing, the device whose retry flag is registered in the execution time table is originally executed at a predetermined time. Based on the data collection execution order of the devices registered in the time table, data collection is started from the device to be recollected.

  However, if a network error occurs during device data recollection, a data collection error occurs again. At this time, in the data collection device disclosed in Patent Document 1, data collection is performed sequentially in the order of the devices registered in the execution time table. There was a problem that data could not be collected. In particular, in an environment where the data collection device collects data from a large number of devices as described above, the load on the network increases, so that a data collection error is likely to occur. A data collection error may occur, and the above problem is more noticeable. As described above, the data collection device disclosed in Patent Document 1 is insufficient to achieve the object of reliably collecting data.

  The present invention has been made to solve the above-described problems, and provides a data collection method and a data collection apparatus that can reliably collect data even in a situation where a data collection error is likely to occur. Objective.

The present invention provides a data collection method for collecting data from devices connected via a network, a collection procedure for collecting data from the device, a writing procedure for writing the collected data to a history file in a storage means, A determination procedure for determining whether or not a collection error has occurred during data collection, and a device in which the collection error has occurred when the determination procedure determines that the collection error has occurred, the retry list of the storage means A retry registration procedure for registering in a file, an error registration procedure for registering the occurrence of the collection error in an error log file of the storage means when the determination procedure determines that the collection error has occurred, and the retry list Re-collect data from the devices registered in the file into the history file of the storage means It is intended and a re-collection procedure burn them.
In addition, one configuration example of the data collection method of the present invention further includes a data format conversion procedure for converting the history file, the retry list file, and the error log file into a predetermined file format.
Moreover, in one configuration example of the data collection method of the present invention, the data format conversion procedure assigns a different file name to the converted history file according to the result of data collection when converting the history file. .

  Further, the present invention provides a data collection apparatus that collects data from devices connected via a network, a collection unit that collects data from the device, and a writing unit that writes the collected data to a history file of a storage unit. Determining means for determining whether or not a collection error has occurred at the time of collecting the data; and if the determination means determines that the collection error has occurred, the device in which the collection error has occurred is stored in the storage means. A retry registration unit for registering in a retry list file; an error registration unit for registering the occurrence of the collection error in an error log file of the storage unit when the determination unit determines that the collection error has occurred; and Recollection of data collected from devices registered in the retry list file and passed to the writing means It is intended and means.

  According to the present invention, even when data collection fails, data collection is not interrupted and resumed from the device again as in the prior art. For each device that has a collection error, each time an error occurs, it is registered in the retry list file for recollection, and then data is recollected from the devices registered in the retry list file, resulting in an error. Since data is collected continuously from the device in the next data collection order of the newly collected device, even if a network error occurs due to the network load being applied, for devices in the order after the device in which the collection error occurred Can also collect data.

  In the present invention, the history file, the retry list file, and the error log file are converted into a predetermined file format such as a CSV file or a TEXT file, so that the history file and the retry list file can be used in systems other than the monitoring system. And error log files can be used. In addition, since the error log file can be output to another system, the error history can be confirmed in the other system when the other system reads the error log file as necessary. In addition, when there is a device that continuously generates a data collection error, the device in which this data collection error has occurred can be confirmed using the error log file, and appropriate measures can be taken for that device. Can be taken.

  In the present invention, the history file can be collected by the scheduled collection procedure by giving the converted history file a different file name according to the data collection result at the time of the history file conversion, or It can be distinguished whether it was collected by the recollection procedure. If the data cannot be collected by the re-collection procedure, the operator can operate the data collection device and send the data re-collection signal to ensure that the data is collected. As a result, the file name after conversion of the collected history file is also given a unique name different from the file name, so that it can be distinguished that it can be collected by the recollection procedure executed by the operator's operation be able to.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The data collection device according to the present embodiment has the following characteristics in order to solve the problems of the prior art and reliably collect data.

  (1) First, when executing data collection, the data collection apparatus according to the present embodiment executes data collection for all target devices regardless of whether or not a data collection error due to a network error or the like occurs. To do. The data collection device registers a device in which a data collection error has occurred due to a network error or the like in the predetermined retry list file as a data re-collection target when an error occurs, and simultaneously indicates that an error has occurred in a predetermined error log file. Record. At a predetermined data recollection time, the data collection device refers to the retry list file and retries data collection only for the data recollection device. As a result of the re-collection, the data collection device records in the file the devices for which data collection has been completed normally and the devices for which data collection errors have occurred.

  (2) The data collection apparatus according to the present embodiment uses a history file in which collected data is recorded as electronic data in a general-purpose file format obtained by converting original data. Further, the data collection device also uses electronic data in a general file format for the retry list file and the error log file. These three types of files are stored in the storage unit of the data collection device, and any of them can be exported to the outside.

  (3) The data collection apparatus according to the present embodiment generates a file with a distinguished file name so that it can be known whether or not an error has occurred when the file is exported to the outside. The data collection device assumes that the file name related to the data that can be automatically collected on time without any error is added with “yyyymmdd.csv” after the device number. It is assumed that the file name is “yyyymmdd1.csv” added after the device number, an error occurs and the data cannot be collected by retry, and the operator operates the data collection device to send a data recollection signal. It is assumed that “yyyymmdd2.csv” is added after the device number to the file name related to the data collected in step (b).

  Hereinafter, this embodiment will be described in more detail. FIG. 1 is a block diagram showing a configuration of a monitoring system according to the present embodiment. In the monitoring system (for example, building monitoring system) of the present embodiment, a central monitoring device 3 and a local monitoring device 4 are connected on a network 2, and under the local monitoring device 4, for example, air conditioning equipment, power equipment, security equipment, Equipment 5 such as disaster prevention equipment is connected. The local monitoring device 4 collects data from each equipment device 5 and stores it as a history file. The local monitoring device 4 may be a card reader, and in this case, the local monitoring device 4 is not connected to the equipment 5. The central monitoring device 3 collects and stores the history files stored in the local monitoring device 4, and generates and stores a history file of alarm occurrence, for example, based on the history file.

In this embodiment, the data collection device 1 is connected to the network 2 of such a monitoring system so that the data collected by the data collection device 1 can be used in other systems (for example, a personnel management system). .
FIG. 2 is a block diagram showing the configuration of the data collection device 1. The data collection device 1 includes a collection unit 10 that collects data from devices (the central monitoring device 3 and the local monitoring device 4), and data collected by the collection unit 10 or data collected by the recollection unit 15 described later. The writing unit 11 that writes to the history file 160 of the storage unit 16 to be described later, the determination unit 12 that determines whether or not a collection error has occurred during data collection, and the determination unit 12 have determined that a collection error has occurred In this case, the retry registration unit 13 registers the device in which the collection error has occurred in the retry list file 161 of the storage unit 16, and the storage unit stores the occurrence of the collection error when the determination unit 12 determines that the collection error has occurred. The error registration means 14 registered in the 16 error log files 162, and the retry list in the storage means 16. A recollection unit 15 that recollects data from devices registered in the file 161 and passes the data to the writing unit 11, a history file 160, a retry list file 161, an error log file 162, and a device that is a data collection destination are stored in advance. Storage means 16 for storing the set collection destination setting file 163.

  The writing unit 11 includes a data format conversion unit 110 that converts the history file 160, the retry list file 161, and the error log file 162 into a predetermined file format. The data format conversion unit 110 assigns a different file name to the converted history file according to the data collection result as described in (3) above when the history file 160 is converted.

Hereinafter, the operation of the data collection device 1 of the present embodiment will be described. FIG. 3 is a flowchart showing the automatic collection function of the data collection device 1.
The collection means 10 of the data collection apparatus 1 collects a device as a data collection destination in advance when a predetermined data collection time (for example, once a day) is reached (YES in step S1 in FIG. 3). Referring to 163, the history file is collected from the central monitoring device 3, and the history file is collected from the data of the equipment 5 collected by the local monitoring device 4 (step S2).

The determination unit 12 of the data collection device 1 determines whether there is a device that has failed to collect history files in the process of step S2 (step S3). The determination unit 12 determines that a collection error has occurred when there is a device for which history file collection has failed.
The data format conversion unit 110 in the writing unit 11 processes the history file collected by the collection unit 10 according to a predetermined conversion rule when it is determined in step S3 that the history file collection is successful, for example, a csv file or a txt file The converted history file 160 is stored in the storage means 16 (step S4). Thereby, in the present embodiment, a management device (not shown) of, for example, a personnel management system other than the monitoring system can read the history file 160 stored in the storage unit 16, and the necessary monitoring information is stored in the own system. Can be used.

  In addition, when it is determined in step S3 that a collection error has occurred, the data format conversion unit 110 processes only the history file that has been successfully collected according to a predetermined conversion rule, converts it into a general-purpose file format, The history file 160 is stored in the storage means 16 (step S5).

  When it is determined in step S3 that a collection error has occurred, the retry registration unit 13 stores the history file collection execution date and time and the device number of the history file collection failure in order to perform data recollection by retry. The error registration means 14 stores the history file collection execution date and time and the device number of the history file collection failure in order to notify the outside that a collection error has occurred. 16 error log files 162 are registered (step S6). The above is the automatic collection function of the data collection device 1.

  In the present embodiment, when a history file cannot be collected due to a communication failure or connection failure with the central monitoring device 3 or the facility device 5 when collecting history files, an error log file 162 indicates that a collection error has occurred. Since registration is performed, for example, a management device (not shown) of the personnel management system other than the monitoring system can check whether the system is operating normally by reading the error log file 162 of the storage unit 16. Further, by registering the device in which the collection error has occurred in the retry list file 161, the history file can be collected again.

Next, an operation in which the data collection device 1 recollects the history file will be described. FIG. 4 is a flowchart showing the history automatic retry function of the data collection device 1.
When the recollection means 15 of the data collection device 1 reaches a pre-designated data recollection time (for example, twice a day) (YES in step S10 in FIG. 4), the recollection means 15 refers to the retry list file 161 in the storage means 16, The history file is recollected from the device in which the collection error has occurred (step S11).

The determination unit 12 of the data collection device 1 determines whether there is a device that has failed to collect history files in the process of step S11 (step S12).
When it is determined in step S12 that the history file collection is successful, the data format conversion unit 110 in the writing unit 11 processes the history file collected by the recollection unit 15 and converts it into a general-purpose file format. The later history file 160 is stored in the storage means 16 (step S13).

Further, when it is determined in step S12 that a collection error has occurred, the data format conversion unit 110 processes only the history file that has been successfully collected in accordance with a predetermined conversion rule, converts it into a general-purpose file format, The history file 160 is stored in the storage means 16 (step S14).
If it is determined in step S12 that a collection error has occurred, the retry registration unit 13 registers the history file collection execution date and time and the device number of the history file collection failure in the retry list file 161 of the storage unit 16, The error registration unit 14 registers the history file collection execution date and time and the device number of the history file collection failure in the error log file 162 of the storage unit 16 (step S15). The above is the history automatic retry function of the data collection device 1.

  With the process of FIG. 4, the recollection is completed for the device that has collected the history file. On the other hand, for a device for which the history file could not be collected, the processing of FIG. However, if the history file cannot be collected even after re-collection for the predetermined number of retries, the operator refers to the retry list file 161 and operates the data collection device to collect the history file. Re-collection may be performed by sending a data re-collection signal.

  The data collection device 1 according to the present embodiment can be realized by, for example, a computer having a CPU, a storage device, and an interface, and a program that controls these hardware resources. In such a computer, the program for the data collection device is provided in a state of being recorded on a recording medium such as a flexible disk, a CD-ROM, a DVD-ROM, or a memory card. The CPU writes the program read from the recording medium into the storage device, and executes the processing described in this embodiment in accordance with this program.

  The present invention can be applied to a monitoring system such as a building management system or a plant management system.

It is a block diagram which shows the structure of the monitoring system which concerns on embodiment of this invention. It is a block diagram which shows the structure of the data collection device in the monitoring system of FIG. It is a flowchart which shows the automatic collection function of the data collection device in the monitoring system of FIG. It is a flowchart which shows the log | history automatic retry function of the data collection device in the monitoring system of FIG.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Data collection apparatus, 2 ... Network, 3 ... Central monitoring apparatus, 4 ... Local monitoring apparatus, 5 ... Device, 10 ... Collection means, 11 ... Writing means, 12 ... Determination means, 13 ... Retry registration means, 14 ... Error registration means, 15 ... recollection means, 16 ... storage means, 110 ... data format conversion means, 160 ... history file, 161 ... retry list file, 162 ... error log file, 163 ... collection destination setting file.

Claims (4)

In a data collection method for collecting data from devices connected via a network,
A collection procedure for collecting data from the device;
A writing procedure for writing the collected data to a history file of a storage means;
A determination procedure for determining whether a collection error has occurred during the collection of the data; and
A retry registration procedure for registering the device in which the collection error has occurred in the retry list file of the storage means when it is determined by the determination procedure that the collection error has occurred;
An error registration procedure for registering the occurrence of the collection error in an error log file of the storage means when it is determined by the determination procedure that the collection error has occurred;
A data collection method comprising: a re-collection procedure for re-collecting data from a device registered in the retry list file and writing the data in a history file of the storage means. The data collection method according to claim 1,
The data collection method further comprises a data format conversion procedure for converting the history file, the retry list file, and the error log file into a predetermined file format. The data collection method according to claim 1,
In the data format conversion procedure, a different file name is given to the converted history file according to a result of data collection when the history file is converted. In a data collection device that collects data from devices connected via a network,
A collection means for collecting data from the device;
Writing means for writing the collected data to a history file of storage means;
Determination means for determining whether a collection error has occurred during the collection of the data;
A retry registration unit that registers the device in which the collection error has occurred in a retry list file of the storage unit when the determination unit determines that the collection error has occurred;
An error registration unit that registers the occurrence of the collection error in an error log file of the storage unit when the determination unit determines that the collection error has occurred;
A data collection apparatus comprising: a recollection unit that recollects data from a device registered in the retry list file and passes the data to the writing unit.

Images