JP2005018117A - Data collector - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a time required for preparation of collection definition information necessary when collecting a data from a monitoring point to be stored, so as to enhance efficiency for engineering work and to reduce cost. <P>SOLUTION: In this data collector 5, the monitoring points to collect the data are found in every monitoring objective monitor, based on monitor definition information for defining an identifier of the each monitoring objective monitor, and a collection template for defining the identifier of the each monitoring point to collect the data, and for defining setting information required when storing the data collected from the monitoring point, every type of the monitoring objective monitors, and the collected data is stored in a storage means, based on the monitor definition information and the collection template. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a data collection device that collects data from monitoring points of a plurality of monitoring target devices and manages each monitoring target device in a facility such as a building, factory, or plant.
[0002]
[Prior art]
Conventionally, in facilities such as buildings, factories, and plants, data collection devices that collect data from monitoring points of a plurality of monitoring target devices and manage each monitoring target device have been proposed (see, for example, Patent Document 1). . In such a data collection device, in order to collect and store data from the monitoring points of the monitoring target device at a constant cycle, collection definition information that defines the monitoring points to be collected is necessary.
[0003]
FIG. 11 is a diagram showing an example of collection definition information that defines identifiers of monitoring points to be collected and setting information necessary for storing data collected from the monitoring points. The collection definition information shown in FIG. 11 corresponds to the configuration of FIG. FIG. 1 is a diagram showing the configuration of the monitoring system according to the first embodiment of the present invention, but the configuration is the same in the conventional monitoring system. explain.
[0004]
The collection definition information in FIG. 11 includes an apparatus name that is an identifier necessary for specifying the monitoring target apparatus (the fume hoods 1 and 2, the general exhaust valve 3, and the constant air flow valve 4) in the data collection apparatus 5 in FIG. Collection item name that is an identifier of data stored in the storage device in the data collection device, collection item description that describes the contents of the collection item, and whether the data stored in the storage device is data collected from a monitoring point The collection type indicating whether the data is sometimes processed, the source indicating the collection source of the data stored in the storage device, and the industrial unit are associated with each other. The data collection device 5 refers to the collection definition information in FIG. 11, accesses the monitoring point where data is to be collected, and saves the collected data with the collection item name defined in the collection definition information. The applicant has not yet found prior art documents related to the present invention by the time of filing other than the prior art documents specified by the prior art document information described in this specification.
[0005]
[Patent Document 1]
JP-A-8-210694
[0006]
[Problems to be solved by the invention]
If there are N points to be monitored, the number of items to be set in the collection definition information is N × (number of set items for each monitoring point). In the example of the fume hood monitoring system shown in FIG. 1, the total number of fume hoods may reach several hundreds, and the number N of monitoring points may reach several thousand. As a result, the amount of entries for collection definition is enormous, and the creation of collection definition information performed by users (workers who install monitoring systems or workers who use monitoring systems) is prone to mistakes. It becomes. As a result, the conventional data collection apparatus has a problem that it takes a lot of time to create collection definition information and to confirm and correct the collection definition information when constructing the system.
The present invention has been made to solve the above-described problems, and reduces the time required to create collection definition information necessary for collecting and storing data from monitoring points, thereby improving the efficiency and low cost of engineering work. The purpose is to make it easier.
[0007]
[Means for Solving the Problems]
The present invention relates to device definition information in which an identifier of the monitoring target device is defined in a data collection device that manages the monitoring target device by collecting data from monitoring points of a plurality of monitoring target devices connected via a network. Storage means for storing an identifier of a monitoring point to collect data and a collection template that defines setting information necessary for saving data collected from the monitoring point for each type of device to be monitored, and the device definition Based on the information and the collection template, a monitoring point for obtaining a monitoring point for collecting data for each monitoring target device and generating a data access request designating the monitoring point for collecting the data, and responding to the data access request Data access means for accessing the monitoring point to collect the data and acquiring data And it has a storage means for storing in said storage means on the basis of the acquired data into the collection template and the device definition information.
Further, in one configuration example of the data collection device of the present invention, the collection template includes data processing processing at the time of data collection and setting information necessary for storing the processed data for each type of monitoring target device. Defined.
In one configuration example of the data collection device of the present invention, the collection template specifies a default collection device template and a default collection device template to be referred to, and defines a difference between the default collection device template and a monitoring target. The monitoring unit collects the data by referring to the default collection device template specified in the collection device template for each type of the monitoring target device and the difference. The monitoring means is determined for each monitoring target device, and the storage means stores data by referring to the default collection device template specified by the collection device template for each type of the monitoring target device and the difference. is there.
[0008]
DETAILED DESCRIPTION OF THE INVENTION
[First Embodiment]
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a monitoring system according to the first embodiment of the present invention. In the present embodiment, a fume hood monitoring system will be described as an example of the monitoring system. The fume hood monitoring system includes a plurality of fume hoods 1 that locally exhaust toxic gases generated in facilities such as research facilities, factories, and hospitals, another fume hood 2 that is different from the fume hood 1, and a fume hood 1. , 2, a general exhaust valve 3 that exhausts excess air supply from the facility according to the total displacement that changes depending on the operating state, a constant air flow valve 4 that constantly exhausts a constant air volume from the facility, a fume hood 1, 2, a data collection device 5 that collects data from monitoring points of the general exhaust valve 3 and the constant air flow valve 4, a plurality of terminal devices 6 that display data transmitted from the data collection device 5, a fume hood 1, 2, A router 7 that connects the general exhaust valve 3 and the constant air flow valve 4 to the network, and a gateway that connects the network and the data collection device 5. And Lee device 8 has an intranet 9 the terminal device 6 is connected, and a router 10 for connecting the data collection device 5 and intranet 9.
[0009]
FIG. 2 is a block diagram showing the configuration of the data collection device 5. The data collection device 5 includes a first interface device 51 connected to the gateway device 8, a second interface device 52 connected to the router 10, an arithmetic device 53, and a storage device 54. Such a data collection device 5 can be realized by a computer. The arithmetic device 53 is mounted with at least a monitoring application program (monitoring means 531) that realizes a monitoring function and a data access program (data access means 532) that realizes a data access function. The monitoring unit 531 includes a storage unit that stores the collected data in the storage device 54.
[0010]
Hereinafter, the operation of such a monitoring system will be described. FIG. 3 is a flowchart showing the operation of the monitoring system of FIG. A plurality of monitoring points exist in each device to be monitored, such as the fume hoods 1 and 2, the general exhaust valve 3, and the constant air flow valve 4. For example, in the case of the fume hoods 1 and 2, there are an exhaust air volume, a sash opening, a human detection sensor, an alarm, and the like. At this time, in the data collection device 5, the monitoring point is managed based on a unique identifier (for example, the name of the monitoring point). On the other hand, in order to access an actual monitoring point in the monitoring target device, data The network connecting the collection device 5 and the monitoring target device and the monitoring point address information necessary for the monitoring target device to identify the monitoring point are required.
[0011]
The data access means 532 of the data collection device 5 creates point definition information in which the monitoring point identifier and the address information are associated in advance (step S1 in FIG. 3).
On the other hand, the monitoring means 531 of the data collection device 5 creates in advance collection definition information that defines the monitoring points to be collected and the data processing at the time of data collection (step S2 in FIG. 3). A method of creating the collection definition information and point definition information will be described later.
[0012]
Next, the monitoring unit 531 periodically generates a data access request for accessing field data (step S3). At this time, the monitoring unit 531 refers to the collection definition information created in step S1, and designates a monitoring point for data collection with a data access request.
[0013]
When the data access unit 532 receives the data access request from the monitoring unit 531, the data access unit 532 acquires data representing the operating state of the fume hoods 1 and 2 from the controllers (not shown) of the respective fume hoods 1 and 2, and Data representing the operating state of the general exhaust valve 3 is obtained from a controller (not shown), and data representing the operating state of the constant air flow valve 4 is obtained from a controller (not shown) of the constant air flow valve 4 (step S4).
[0014]
In order to collect data from the monitoring point specified in the data access request, the data access means 532 creates a data request packet addressed to the monitoring target device with reference to the point definition information created in step S2, and this data request The packet is sent to the gateway device 8. The monitoring target device that has received the data request packet via the gateway device 8 and the router 7 sends the data of the monitoring point designated by the address information of the data request packet to the data collection device 5. Then, the data access unit 532 passes the data received from the monitoring target device to the monitoring unit 531.
[0015]
The monitoring means (save means) 531 stores the data received from the data access means 532 in the storage device 54 in the data collection device and sends this data to the terminal device 6. Each terminal device 6 displays the data received from the data collection device 5 (step S5). The processes in steps S3 to S5 are repeatedly performed until an instruction to end the monitoring work is received from the worker (YES in step S6).
[0016]
Thus, the data collection device 5 periodically collects field data and displays it on the monitoring screen of the terminal device 6. In some cases, not only the collected data is displayed as it is, but also a trend graph representing the data history is created by the monitoring means 531 and displayed on the terminal device 6.
[0017]
Next, a method for creating point definition information according to this embodiment will be described. First, in the present embodiment, a device template Dtemp is created in advance for each type of monitoring target device. FIG. 4 is a diagram illustrating an example of the device template Dtemp. The device template Dtemp is a template type that indicates the type of device template, that is, the type of device to be monitored, a point name that is an identifier necessary for specifying the type of monitoring point in the data collection device 5, the network, and on the network. The point number and the point type, which are address information necessary for specifying the type of the monitoring point in the monitoring target device, are associated with the point description describing the contents of the monitoring point.
[0018]
In FIG. 4, “FUMEHOOD”, “FUMEHOOD_2”, “GEX”, and “CAV” indicate device templates corresponding to the fume hood 1, the fume hood 2, the general exhaust valve 3, and the constant air flow valve 4, respectively. Yes.
[0019]
In the same type of monitoring target device, the combination of monitoring points is the same. In the same type of monitoring target device, the same point name, the same point number, and the same point type are assigned to the same type of monitoring point. For example, in the plurality of fume hoods 1 corresponding to the template type “FUMEHOOD”, the exhaust air volume point names are all “flow”, the point number is “12”, and the point type is “AI”.
[0020]
The device template Dtemp as described above is created when a user (a worker who installs the monitoring system or a worker who performs monitoring work using the monitoring system) operates the terminal device 6. The created device template Dtemp is stored in the storage device 54 in the data collection device.
[0021]
In addition, not only the monitoring point of the monitoring target device but also a management data item can be arbitrarily added to the device template Dtemp. In the example of FIG. 4, “miniFlow” indicating the minimum air volume of the device, “ROOM” that is the name of the room in which the device is installed, and “MANIFOLD” that is the name of the manifold to which the device is connected as data items for management. “FLOOR”, which is the name of the floor on which the apparatus is installed, is added.
[0022]
Next, in this embodiment, device definition information Ddef is created in advance for each monitoring target device. FIG. 5 is a diagram showing an example of the device definition information Ddef. The device definition information Ddef is necessary for specifying the monitoring target device among the device name, which is an identifier necessary for specifying the monitoring target device in the data collection device 5, the template type, and the devices on the network and the network. A device number, which is address information, and a device description describing the contents of the device are associated with each monitoring target device. The device definition information Ddef is also created by the user operating the terminal device 6, and the created device definition information Ddef is stored in the storage device 54 in the data collection device.
[0023]
Based on the device definition information Ddef and the device template Dtemp as described above, the data access unit 532 of the data collection device 5 creates the point definition information Pdef. FIG. 6 is a diagram showing an example of the point definition information Pdef. The point definition information Pdef associates a device name, a template type, a device number, a point number, a point type, a point name, and a point description. Among these pieces of information, the device number, the point number, and the point type constitute address information necessary for specifying the monitoring target device in the network and the devices on the network and specifying the monitoring point in the monitoring target device. Yes.
[0024]
The data access unit 532 of the data collection device 5 extracts one record from the device definition information Ddef, that is, the device definition information of one monitoring target device, acquires the template type from this device definition information, and based on this template type The device template corresponding to the monitoring target device is acquired from the device template Dtemp. Then, the data access unit 532 creates the point definition information of the monitoring target device by combining the acquired device definition information and the device template. The data access unit 532 creates such point definition information for each monitoring target device registered in the device definition information Ddef.
[0025]
Next, a method for creating collection definition information according to this embodiment will be described. In the present embodiment, a collection template Ctemp in which the monitoring points to be collected and the data processing at the time of data collection is defined for each type of the monitoring target device is created in advance. FIG. 7 is a diagram illustrating an example of the collection template Ctemp. The collection template Ctemp includes collection cycle information that defines a data collection cycle and a collection template (collection device template) for each type of monitoring target device. The collection template Ctemp is also created by the user operating the terminal device 6, and the created collection template Ctemp is stored in the storage device 54 in the data collection device.
[0026]
The collection device template includes a collection item name that is setting information (identifier of data stored in the storage device 54) necessary for storing data collected from the monitoring point, a collection item description that describes the content of the collection item, A collection type indicating whether the data accumulated in the storage device 54 is data collected from monitoring points or data processed at the time of data collection, and a collection source of data accumulated in the storage device 54 (identifier of monitoring points to be collected) Alternatively, a source indicating data processing at the time of data collection) and an industrial unit are associated with each type of device to be monitored.
[0027]
In FIG. 7, template types “FUMEHOOD” and “FUMEHOOD_2” indicate that they are collection device templates corresponding to fume hood 1 and fume hood 2, respectively. According to the collection device template whose template type is “FUMEHOOD”, it can be seen that the data accumulated in the storage device 54 with the collection item name “FLOW” is collected from the monitoring point named “exhaust”.
[0028]
Further, the data accumulated in the storage device 54 with the collection item name “IDEALFLOW” has the collection type “calculation”, and it can be seen that the data is processed at the time of data collection. The calculation formula at this time is described in the source, and when using the monitoring point data, the point name is described in the calculation formula. When the monitoring point data is described in the source calculation formula, the monitoring means 531 designates the monitoring point in the calculation formula as the monitoring point to be collected, and the data collected by the data access means 532 Perform calculations on In the collection device template, as in the device template Dtemp, the same type of monitoring point is assigned the same collection item name to the same type of monitoring point in the same type of monitoring target device.
[0029]
The monitoring unit 531 of the data collection device 5 creates collection definition information Cdef based on the device definition information Ddef, the device template Dtemp, and the collection template Ctemp. FIG. 8 is a diagram illustrating an example of the collection definition information Cdef. The collection definition information Cdef is composed of collection cycle information and information for each monitoring target device. The information for each monitoring target device includes a device name, a template type, a collection item name, a collection item description, a collection type, a source, and an industrial unit. Are associated with each other.
[0030]
The monitoring unit 531 of the data collection device 5 extracts one record from the device definition information Ddef, that is, the device definition information of one monitoring target device, acquires the template type from this device definition information, and based on this template type The collection device template corresponding to the monitoring target device is acquired from the collection template Ctemp. Then, the monitoring unit 531 creates the collection definition information of the monitoring target device by combining the acquired device definition information and the collection device template. The monitoring unit 531 creates such collection definition information for each monitoring target device registered in the device definition information Ddef.
[0031]
When generating a data access request in step S3 of FIG. 3, the monitoring unit 531 refers to the collection definition information Cdef and designates a monitoring point for data collection. Further, the monitoring unit (storage unit) 531 stores the data with the collection item name defined by the collection definition information Cdef when the data received from the data access unit 532 is stored in the storage device 54 in the data collection device. (FIG. 3, step S5).
[0032]
As described above, since the same type of monitoring point is assigned to the same type of monitoring point in the same type of monitoring target device, individual monitoring points cannot be managed only by the point name. In order for the monitoring unit 531 to specify a monitoring point for data collection to the data access unit 532, it is necessary to use the device name and the like as the monitoring point identifier together with the point name (source). In addition, since the same collection item name is assigned to the same type of monitoring point in the same type of monitoring target device, when the collected data is stored in the storage device 54, the device name and the like are collected together with the collection item name. It must be used as an identifier for data.
[0033]
As described above, in the present embodiment, the collection definition information Cdef can be created from the device definition information Ddef, the device template Dtemp, and the collection template Ctemp, so that collection definition information is created point by point as in the past. There is no need. As a result, collection definition can be performed efficiently, and the cost required for the engineering work of collection definition can be reduced.
[0034]
In the present embodiment, a collection template Ctemp is prepared for each type of monitoring target device. In the collection template Ctemp, since the same point name and the same collection item name are assigned to the same type of monitoring points of the same type of monitoring target device, the amount of entries for collection definition should be reduced as compared to the conventional case. Can do. Therefore, this embodiment is particularly effective in a monitoring system having a large number of monitoring target devices of the same type.
[0035]
In the present embodiment, the collection definition information Cdef is created by inheriting the collection template Ctemp. However, when the collection template Ctemp of the inheritance source is changed by the user, the monitoring unit 531 changes the collection template Ctemp. The collection definition information Cdef is automatically changed according to the above. Therefore, the change of the collection template Ctemp can be reflected in the collection definition information Cdef without delay.
[0036]
[Second Embodiment]
In the first embodiment, the monitoring points to be collected and the data processing at the time of data collection are all defined by the collection device template for each type of the device to be monitored. However, the monitoring of the first embodiment In the system, a default collection device template may be prepared, and only collection items different from the default collection device template may be defined by the collection device template for each type of the monitoring target device. FIG. 9 is a diagram illustrating an example of the collection template Ctemp according to the present embodiment.
[0037]
In the example of FIG. 9, the template types of the two default collection device templates are “DEF_CTRL_1” and “DEF_ALARM”, respectively. In the collection device template of the template type “FUMEHOOD”, only “INHERIT: DEF_CTRL_1, DEF_ALARM” is described. This “INHERIT: DEF_CTRL_1, DEF_ALARM” indicates that the default collection device templates of the template types “DEF_CTRL_1” and “DEF_ALARM” should be referred to.
[0038]
When the monitoring unit 531 of the data collection device 5 acquires the collection device template from the collection template Ctemp based on the template type acquired from the device definition information Ddef as described in the first embodiment, the template type is “FUMEHOOD. ”With reference to the default collection device templates of the template types“ DEF_CTRL_1 ”and“ DEF_ALARM ”, this default collection device template is set as a collection device template of the template type“ FUMEHOOD ”.
[0039]
On the other hand, in FIG. 9, in the collection device template whose template type is “FUMEHOOD_2”, in addition to “INHERIT: DEF_CTRL_1, DEF_ALARM”, definitions relating to data of collection item names “FLOW” and “IDEALFLOW” are described. This indicates that the definition described in the collector template should be used instead of the definitions of “FLOW” and “IDEALFLOW” described in the default collector template.
[0040]
For example, when the template type acquired from the device definition information Ddef is “FUMEHOOD_2”, the monitoring unit 531 refers to the default collection device templates of the template types “DEF_CTRL_1” and “DEF_ALARM”, but the data of the collection item name “FLOW” Since the definition described in the collection device template of the template type “FUMEHOOD_2” is used for “”, the monitoring point (source) for data collection is “suppli”. The monitoring unit 531 uses a calculation formula described in the collection device template of the template type “FUMEHOOD_2” for the data of the collection item name “IDEALFLOW”.
[0041]
As described above, in the present embodiment, the definition amount of the collection template Ctemp can be reduced by using the default collection device template.
Also in the present embodiment, when the collection template Ctemp is changed by the user, it goes without saying that the collection definition information Cdef is automatically changed according to this change.
[0042]
[Third Embodiment]
In the first and second embodiments, the collection definition information Cdef and the point definition information Pdef are created in advance, and the data access unit 532 is generated when the monitoring unit 531 of the data collection device 5 generates a data access request. Is accessing the monitoring point, but in the monitoring system according to the first or second embodiment, data is collected from the monitoring point without creating the collection definition information Cdef and the point definition information Pdef. It is also possible to save.
[0043]
FIG. 10 is a flowchart showing the operation of the monitoring system of the present embodiment, and the same processes as those in FIG. The difference from the first and second embodiments is that the collection definition information Cdef and the point definition information Pdef are not created, the data access request generation process in step S3a, the data collection process in step S4a, and the step S5a. Data storage processing.
[0044]
When generating the data access request, the monitoring unit 531 of the data collection device 5 acquires the device definition information and the collection device template in the same manner as when creating the collection definition information Cdef, and this device definition information and the collection device template. From this, a monitoring point for data collection is obtained, and this monitoring point for data collection is designated by a data access request (step S3a).
[0045]
When the data access unit 532 of the data collection device 5 receives the data access request from the monitoring unit 531, the data access unit 532 acquires the device definition information and the device template in the same manner as when the point definition information Pdef is created. Address information necessary for specifying a monitoring target device in the network and devices on the network and specifying a monitoring point in the monitoring target device from the device template and the device template, and generating a data request packet based on the address information (step S4a).
[0046]
Then, the monitoring unit 531 of the data collection device 5 stores the device definition information in the same manner as when creating the collection definition information Cdef when saving the data received from the data access unit 532 in the storage device 54 in the data collection device. And the collection device template are obtained, a data collection item name is obtained from the device definition information and the collection device template, and the data is stored with this collection item name (step S5a). In this way, data collection and data storage similar to those in the first embodiment can be realized.
[0047]
In the first to third embodiments, the address information is a simple list of device numbers, point numbers, and point types, but the address information described in the device definition information Ddef. And final address information may be generated by performing a predetermined calculation based on the address information described in the device template Dtemp (point template Ptemp).
[0048]
In the first to third embodiments, a fume hood monitoring system that monitors the plurality of fume hoods 1, 2, the general exhaust valve 3, and the constant air volume valve 4 is described as an example. However, the present invention is not limited to this, and a system for monitoring other devices may be used. Needless to say, the router 7, the gateway device 8, and the router 10 are not necessarily provided, and can be appropriately changed according to the network status of each facility.
[0049]
【The invention's effect】
According to the present invention, device definition information and a collection template are created in advance, and based on the device definition information and the collection template, a monitoring point to be collected is obtained for each monitoring target device, and the collected data is obtained. Since it is stored in the storage means, it is not necessary to create the collection definition information point by point as in the prior art. As a result, the repetition of monotonous work can be reduced and errors in collection definitions can be reduced, so the engineering work for creating, checking, and correcting collection definition information (device definition information and collection templates) can be performed efficiently. The cost required for engineering work can be reduced. In recent years, the price of monitoring systems has been decreasing, but when viewed from the perspective of system delivery prices to customers, the ratio of costs required for engineering work for creating, checking, and correcting collection definition information has become extremely high. It is coming. If the cost required for this engineering work can be reduced, not only can the delivery price to the customer be reduced, but the customer's willingness to purchase will be stimulated to increase the sales amount by increasing the sales volume and increase the profit by reducing the cost. Can be aimed. Since the present invention prepares a collection template for each type of monitoring target device, it is particularly effective in a monitoring system having many monitoring target devices of the same type.
[0050]
Further, by using the default collection device template, the amount of collection template definition can be reduced.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a monitoring system according to a first embodiment of the present invention.
FIG. 2 is a block diagram showing a configuration of a data collection device according to the first embodiment of the present invention.
FIG. 3 is a flowchart showing an operation of the monitoring system of FIG. 1;
FIG. 4 is a diagram illustrating an example of a device template according to the first embodiment of the present invention.
FIG. 5 is a diagram showing an example of device definition information according to the first embodiment of the present invention.
FIG. 6 is a diagram showing an example of point definition information according to the first embodiment of the present invention.
FIG. 7 is a diagram showing an example of a collection template according to the first embodiment of the present invention.
FIG. 8 is a diagram illustrating an example of collection definition information according to the first embodiment of this invention.
FIG. 9 is a diagram showing an example of a collection template according to the second embodiment of the present invention.
FIG. 10 is a flowchart showing the operation of the monitoring system according to the third embodiment of the present invention.
FIG. 11 is a diagram showing an example of conventional collection definition information.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1, 2 ... Hume hood, 3 ... General exhaust valve, 4 ... Constant air volume valve, 5 ... Data collection device, 6 ... Terminal device, 7 ... Router, 8 ... Gateway device, 9 ... Intranet, 10 ... Router, 51, 52 ... interface device, 53 ... arithmetic device, 54 ... storage device, 531 ... monitoring means, 532 ... data access means.

Claims (3)

In a data collection device that collects data from monitoring points of a plurality of monitoring target devices connected via a network and manages the monitoring target device,
Device definition information that defines the identifier of the monitoring target device, the identifier of the monitoring point that should collect data, and the setting information that is required when saving data collected from this monitoring point is defined for each type of monitoring target device Storage means for storing the collection template;
Based on the device definition information and the collection template, monitoring means for obtaining a monitoring point for data collection for each monitoring target device, and generating a data access request specifying the monitoring point for data collection;
Data access means for accessing the monitoring point to collect data in response to the data access request and obtaining data;
A data collection device comprising: a storage unit that stores the acquired data in the storage unit based on the device definition information and the collection template. The data collection device according to claim 1,
The collection template defines a data processing process at the time of data collection and setting information necessary for storing the processed data for each type of monitoring target apparatus. The data collection device according to claim 1 or 2,
The collection template includes a default collection device template and a collection device template for each type of monitoring target device that defines a default collection device template to be referred to and defines differences from the default collection device template.
The monitoring means refers to the default collection device template specified in the collection device template for each type of the monitoring target device and the difference, and determines the monitoring point for data collection for each monitoring target device,
The storage unit stores data with reference to a default collection device template specified by a collection device template for each type of the monitoring target device and the difference.

Images