JP6080631B2 - DATA COLLECTION / RECORDING DEVICE, MANAGEMENT SYSTEM, AND DATA COLLECTION / RECORDING METHOD - Google Patents

Description

The present invention, management state data collection recording device collects and records data about the target system, relates to the management system, and data acquisition records how.

  A hot water supply system, which is an example of a system subject to maintenance (managed system), is composed of a plurality of parts such as a heat exchanger, a pump, a solenoid valve, a fan, and various sensors, and operates according to a control sequence. Therefore, maintenance by a system provider or the like is necessary. For such maintenance, a failure management apparatus that records a history of the operating state of a hot water supply system has been proposed (see, for example, Patent Document 1). This device accumulates data (error information) indicating an abnormality of the hot water supply system in a storage means (EEPROM) in the hot water supply system, and displays the abnormality content based on the accumulated data at the time of failure diagnosis.

  In addition, a data collection / recording apparatus that records data indicating the state of a managed system over a longer period has been proposed (see, for example, Patent Document 2). This device acquires data related to the state of the managed system at a predetermined time interval and records it in a storage device, and performs data thinning according to the remaining capacity of the storage device and the importance of the data to reduce the amount of data. By reducing the data, longer-term data is recorded.

JP-A-6-317324 JP 2011-258064 A

  By the way, in the configuration in which the status data related to the status of the managed system is acquired and recorded from the managed system, the status data is transmitted to the managed system during a period when the processing load (for example, CPU load) of the managed system is high. If requested frequently, the processing load on the managed system may become excessive due to communication processing. If the processing load on the managed system becomes excessive, for example, the original operation of the managed system may not be performed correctly.

The present invention, while suppressing the processing load on the managed system is excessive, the data collection recording apparatus can acquire the state data from the managed system, the management system, and to provide a data collection records how With the goal.

The data collection and recording apparatus according to the present invention is
At a predetermined time interval (hereinafter referred to as “data acquisition interval”), a data acquisition unit that acquires state data related to the state of the management target system from the management target system, and state data acquired by the data acquisition unit A data recording unit for recording, and a data acquisition interval control unit for controlling the data acquisition interval based on feature data indicating a processing load of the management target system among the state data acquired by the data acquisition unit, When acquiring the state data, the data acquisition unit acquires current feature data indicating a current processing load of the management target system as the feature data, and the current feature data is a processing load of the management target system. Indicates that data other than the current feature data is acquired from the state data, and the current data When the symptoms data indicates a higher processing load of the managed system, without acquiring the other data, the data acquisition unit, as the other data, a predetermined time interval (hereinafter in the managed system The oldest stored data that has not yet been transmitted among the stored data relating to the state of the managed system is acquired every time .

Moreover, the management system according to the present invention includes:
A management target system and a data collection and recording device, the management target system including a control unit that controls the operation of the management target system, and the data collection and recording device includes a predetermined time interval (hereinafter referred to as “data acquisition”). A data acquisition unit that acquires state data related to the state of the managed system from the managed system, a data recording unit that records the state data acquired by the data acquisition unit, and the data A data acquisition interval control unit that controls the data acquisition interval based on feature data indicating a processing load of the control unit of the management target system among the state data acquired by the acquisition unit, the data acquisition unit When acquiring the state data, the current feature data indicating the current processing load of the managed system is used as the feature data. When the current feature data indicates that the processing load of the managed system is low, other data other than the current feature data is acquired from the state data, and the current feature data is When the processing load of the management target system is high, the other data is not acquired, and the control unit stores storage data related to the state of the management target system at a predetermined time interval, and the data acquisition The unit acquires the oldest stored data that has not yet been transmitted among the stored data as the other data .

The data collection and recording method according to the present invention includes:
At a predetermined time interval (hereinafter referred to as “data acquisition interval”), a data acquisition step of acquiring state data related to the state of the managed system from the managed system, and the status data acquired by the data acquisition step A data recording step for recording, and a data acquisition interval control step for controlling the data acquisition interval based on feature data indicating the processing load of the managed system among the state data acquired in the data acquisition step The data acquisition step acquires current feature data indicating a current processing load of the management target system as the feature data when the state data is acquired, and the current feature data is processed by the management target system. When the load is low, the current feature data among the state data Acquires other data outside, the when the current feature data indicating a high processing load of the managed system, without acquiring the other data, the data acquisition step, as the other data Obtaining the oldest unsent storage data among the storage data related to the state of the management target system stored at predetermined time intervals (hereinafter referred to as “data storage interval”) in the management target system. Features.

  According to the present invention, by determining the data acquisition interval based on the characteristic data indicating the processing load of the management target system, it is possible to obtain the state data from the management target system while suppressing an excessive processing load on the management target system. Can be acquired.

1 is a block diagram schematically illustrating an example of a configuration of a management system according to a first embodiment. 6 is a sequence diagram illustrating an example of processing for data acquisition by the data collection and recording device according to Embodiment 1. FIG. 6 is a diagram illustrating an example of data acquisition interval control according to a CPU load in the first embodiment. FIG. 4 is a flowchart illustrating an example of the operation of the data collection and recording apparatus according to the first embodiment. 6 is a block diagram schematically showing an example of a configuration of a management system according to Embodiment 2. FIG. 10 is a diagram illustrating an example of a structure of saved data saved by a management target system according to Embodiment 2. FIG. FIG. 10 is a diagram illustrating an example of data acquisition interval and data acquisition level control according to a CPU load in the second embodiment. 6 is a flowchart illustrating an example of an operation of the data collection and recording apparatus according to the second embodiment. FIG. 10 is a block diagram schematically illustrating an example of a configuration of a management system according to a third embodiment. FIG. 20 is a diagram showing an example of a setting file in the third embodiment. FIG. 11 is a sequence diagram illustrating an example of a process for acquiring data by the data collection and recording apparatus according to the third embodiment. FIG. 20 is a diagram illustrating another example of a setting file in the third embodiment. FIG. 10 is a block diagram schematically illustrating an example of a configuration of a management system according to a fourth embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
Embodiment 1 FIG.
FIG. 1 is a block diagram schematically showing an example of the configuration of the management system 1 according to the first embodiment. In FIG. 1, a management system 1 includes a management target system 10 and a data collection / recording apparatus 20 (an apparatus capable of performing the data collection / recording method according to the first embodiment).

  The management target system 10 is a system to be managed or maintained. For example, the management target system 10 is a hot water supply system, and includes a plurality of components such as a heat exchanger, a pump, a solenoid valve, a fan, and various sensors.

  The managed system 10 includes a communication unit 11 that communicates with the data collection and recording device 20, a data storage unit 12 that stores data, and a control unit 13 that controls the operation of the managed system 10. Specifically, the control part 13 is a central processing unit (CPU: Central Processing Unit). In addition, the control unit 13 acquires a state value indicating the state of the components constituting the management target system 10 and controls the operation of the management target system 10 using the state value. FIG. 1 illustrates a solenoid valve 17, a pump 18, and sensors A to Z as components constituting the management target system 10. Further, the control unit 13 receives a request from the data collection / recording apparatus 20 via the communication unit 11 and transmits a response to the request to the data collection / recording apparatus 20.

  The data collection and recording device 20 is a device that acquires and records state data related to the state (or operation state) of the management target system 10 from the management target system 10. In FIG. 1, the data collection / recording apparatus 20 includes a data acquisition unit 21, a data recording unit 22, a data acquisition interval control unit 23, and a control unit 24.

  The data acquisition unit 21 requests the managed system 10 to transmit state data at predetermined time intervals (hereinafter referred to as “data acquisition interval”), and is transmitted from the managed system 10 in response to the request. Get state data. In the example of FIG. 1, the data acquisition unit 21 includes a system communication unit 21a, a data request transmission unit 21b, and a response data reception unit 21c.

  The system communication unit 21a is communicably connected to the management target system 10 that is a target of data acquisition by wire or wireless, and transmits a command to the management target system 10 and receives data from the management target system 10 I do.

  The data request transmission unit 21b generates a command for requesting data transmission to the management target system 10 and transmits the command via the system communication unit 21a.

  The response data receiving unit 21c receives response data from the management target system 10 for the command transmitted by the data request transmitting unit 21b via the system communication unit 21a.

  The system communication unit 21a is configured with, for example, a serial communication specification of the RS-232C standard. In the serial communication specification, data can be transmitted from the data collection / recording apparatus 20 to the management target system 10, and the data collection / recording apparatus 20 can receive data from the management target system 10. The system communication unit 21a is not limited to the configuration of the RS-232C standard. For example, the system communication unit 21a may have a configuration based on another serial communication standard such as the RS-485 standard or a configuration based on the parallel communication standard. . Further, when the communication standard adopted by the system communication unit 21a of the data collection / recording apparatus 20 is different from the communication standard adopted by the communication unit 11 of the management target system 10, the system communication unit 21a and the management that is the connection destination thereof. What is necessary is just to interpose the conversion apparatus (not shown) which converts a communication system between the communication parts 11 of the object system 10. FIG.

  The data recording unit 22 records the state data acquired by the data acquisition unit 21. Specifically, the data recording unit 22 records the status data received by the response data receiving unit 21c in chronological order. Here, the data recording unit 22 is a recording device or a recording medium that can be inserted into and removed from (inserted into and removed from) the apparatus main body by a user operation, but may be a recording apparatus or a recording medium incorporated in the apparatus main body. . Further, the data recording unit 22 may record the status data on a recording device or a recording medium provided outside the data collection and recording device 20.

  The data acquisition interval control unit 23 controls the data acquisition interval based on the feature data indicating the processing load of the management target system 10 among the state data acquired by the data acquisition unit 21. Specifically, the data acquisition interval control unit 23 increases the data acquisition interval as the processing load of the management target system 10 indicated by the feature data is higher. Here, the processing load is the load on the control unit 13 (specifically, the CPU) of the management target system 10. The feature data indicates the state of parts of the managed system 10 (for example, the operating state of one or both of the solenoid valve 17 and the pump 18), and one or more states used for controlling the operation in the managed system 10 Consists of values.

  In the example of FIG. 1, the data acquisition interval control unit 23 includes a feature data extraction unit 23a, a processing load determination unit 23b, and a data acquisition interval determination unit 23c.

  The feature data extraction unit 23 a extracts feature data from the data acquired by the data acquisition unit 21.

  The processing load determination unit 23b determines or estimates the processing load of the management target system 10 from the feature data extracted by the feature data extraction unit 23a. For example, the processing load determination unit 23b determines the CPU load based on the magnitude relationship between the feature data and a threshold value determined in advance according to the management target system 10. Specifically, it is determined that the CPU load is high when the feature data exceeds a threshold, and it is determined that the CPU load is low when it does not exceed the threshold. For example, when the feature data is the number of revolutions of the pump and 1000 revolutions is set as the threshold value, when the obtained number of revolutions of the pump exceeds 1000 revolutions (for example, 1500 revolutions), the CPU load Is determined to be high.

  The data acquisition interval determination unit 23c determines the data acquisition interval based on the determination result of the processing load determination unit 23b, and sends a control signal indicating the data acquisition interval to the data request transmission unit 21b. Specifically, the data acquisition interval determination unit 23c increases the data acquisition interval as the determined CPU load is higher.

  The control unit 24 controls the entire data collection / recording apparatus 20. For example, based on an instruction from the user, the control unit 24 instructs the data acquisition unit 21 to start or end the data acquisition process, or sets a setting value such as a data acquisition interval in the data acquisition interval control unit 23. .

  In this example, from the viewpoint of suppressing an excessive processing load on the management target system 10, when acquiring data, the data acquisition unit 21 first indicates a current processing load on the management target system 10. When the feature data is acquired and the current feature data indicates that the processing load of the management target system 10 is low, data other than the current feature data is acquired from the state data, and the current feature data is stored in the management target system. When the processing load of 10 indicates that it is high, the other data is not acquired. The other data includes, for example, more state values than feature data, and indicates the state of the managed system 10 in detail. In the following description, the other data is referred to as “detailed data”. For example, the data acquisition unit 21 acquires current feature data as a response to a data acquisition start request to the managed system 10, determines the CPU load from the current feature data, and determines that the CPU load is low When the detailed data is acquired and it is determined that the CPU load is high, the detailed data is not acquired. The data acquisition unit 21 may receive and use the determination result of the processing load determination unit 23b.

  Here, when the processing load of the management target system 10 is high, if the data acquisition interval is simply increased or detailed data acquisition is not performed, state data ( It is conceivable that highly important data) cannot be acquired.

  Therefore, in this example, the management target system 10 stores the storage data relating to the state of the management target system 10 at predetermined time intervals (hereinafter referred to as “data storage intervals”), and requests from the data collection and recording device 20. In response, the oldest stored data that has not been transmitted among the stored data (hereinafter referred to as “oldest stored data”) is transmitted to the data collection and recording device 20. For example, the management target system 10 temporarily saves saved data in the data storage unit 12 at a data saving interval, and saves data saved in the data storage unit 12 every time a transmission request is received from the data collection and recording device 20. Are sequentially sent to the data collection and recording device 20 in the order of storage. The data storage interval is always a constant interval, for example, but may vary according to the processing load of the management target system 10. In the data collection and recording device 20, the data acquisition unit 21 acquires the current feature data of the management target system 10, and acquires the oldest stored data as detailed data.

  In the above configuration, for example, when the acquired current feature data indicates that the processing load of the management target system 10 is high, the data acquisition interval control unit 23 determines the data acquisition interval as a time interval longer than the data storage interval. After that, when the current feature data indicating that the processing load is low is acquired by the data acquisition unit 21, the data acquisition interval is determined to be a time interval shorter than the data storage interval.

  The data acquisition interval control unit 23 determines that the data acquisition interval is a time interval shorter than the data storage interval, and if there is no stored data to be transmitted in the managed system 10 (or data acquisition catches up with data storage). The data acquisition interval is determined to be the same time interval as the data storage interval. Here, the same time interval may not be exactly the same time interval, but may be substantially the same time interval. Further, for example, the management target system 10 notifies whether there is no unsent stored data or whether data acquisition has caught up, but may be determined by another method.

  It should be noted that other elements not shown may be installed or connected to the data collection / recording apparatus 20. For example, the data collection / recording apparatus 20 is temporarily used for a command input unit that receives an instruction to start or stop recording from a user, a display unit that displays information such as status data of the management target system 10, control, and the like. A storage unit for storing data may be installed or connected.

  FIG. 2 is a sequence diagram illustrating an example of processing for data acquisition by the data collection and recording device 20 according to the first embodiment. Hereinafter, the data acquisition operation of the data collection and recording apparatus 20 according to the first embodiment will be described with reference to FIG.

  In FIG. 2, when starting the i-th (i is an integer) data acquisition process, the data collection and recording device 20 sends a data acquisition start request to the management target system 10 to start data acquisition. The managed system 10 returns a data acquisition start response to the data collection / recording device 20 if the data can be sent in response to the data acquisition start request from the data collection / recording device 20. At this time, the management target system 10 sends one of the state values of the management target system 10 at that time as feature data included in the data acquisition start response. This feature data is, for example, a state value indicating the rotation speed of the pump 18.

  Upon receiving the data acquisition start response from the management target system 10, the data collection / recording apparatus 20 extracts feature data from the data acquisition start response by the feature data extraction unit 23a, and uses the extracted feature data to determine the processing load. The CPU 23 of the management target system 10 is determined by the unit 23b.

  In the i-th data acquisition process, it is determined that the CPU load is low. In this case, the data collection / recording apparatus 20 requests the managed system 10 to transmit the detailed data, and acquires the detailed data from the managed system 10. Specifically, the data collection and recording device 20 sends a transmission request for the detection value (data value) of the sensor A (for example, a temperature sensor of a can body such as a hot water supply system) to the management target system 10. The managed system 10 returns the detection value of the sensor A in response to the transmission request from the data collection / recording device 20. Similarly, the data collection and recording apparatus 20 sends a transmission request for the detection value of the sensor B to the management target system 10, and the management target system 10 returns the detection value of the sensor B. Thereafter, similarly, the data collection and recording device 20 acquires necessary data (for example, detection values of the sensors C to Z).

  When the acquisition of the state data ends, the data collection and recording device 20 sends a data acquisition end notification to the effect that the data acquisition has ended to the management target system 10, and the management target system 10 responds with a data acquisition end response. Return it. Then, the data collection / recording apparatus 20 determines the time interval (data acquisition interval) until the next data acquisition process to the basic time interval T1 by the data acquisition interval determination unit 23c, and ends the i-th data acquisition process. The basic time interval T1 is, for example, 10 seconds and is determined in advance.

  When the data acquisition interval (T1 in this case) determined in the i-th data acquisition process elapses from the start of the i-th data acquisition process, the data collection and recording device 20 acquires the next (i + 1) -th data acquisition. Start processing. At this time, similarly to the i-th data acquisition process, the data collection and recording device 20 sends a data acquisition start request to the management target system 10, and the management target system 10 returns a data acquisition start response including feature data. . Then, the data collection / recording apparatus 20 extracts feature data from the data acquisition start response and determines the CPU load.

  In the (i + 1) th data acquisition process, it is determined that the CPU load is high. In this case, the data collection / recording apparatus 20 sends a data acquisition end notification to the management target system 10 without receiving the detailed data, and receives a data acquisition end response from the management target system 10. Then, the data collection and recording device 20 determines the time interval (data acquisition interval) until the next data acquisition process to be a time interval T2 (> T1) longer than the basic time interval T1, and acquires the (i + 1) th data acquisition. The process ends. The time interval T2 is 20 seconds, for example, and is determined in advance.

  When the data acquisition interval (T2 in this case) determined in the (i + 1) th data acquisition process elapses from the start time of the (i + 1) th data acquisition process, the data collection and recording device 20 performs the following (i + 2) The second data acquisition process is started.

  FIG. 3 is a diagram illustrating an example of data acquisition interval control according to the CPU load. In FIG. 3, the horizontal axis represents time t, and the vertical axis represents the amount of data. The upper side of FIG. 3 shows the time of data storage processing and the amount of stored data stored at the time in the management target system 10. The lower side of FIG. 3 shows the time point of data acquisition processing and the amount of state data acquired at the time point in the data collection and recording device 20. A plurality of arrows directed from the upper side to the lower side in FIG. 3 indicate correspondences between stored data and state data (or movement of stored data from the management target system 10 to the data collection and recording device 20). The period TH indicates a period during which the CPU load of the management target system 10 is high.

  As shown in FIG. 3, the management target system 10 stores the stored data at a fixed period at a basic time interval T1. FIG. 3 shows the (j−1) to (j + 11) th data storage processing.

  In the (i-1) th data acquisition process, the data collection / recording apparatus 20 acquires the current feature data from the management target system 10, determines that the CPU load is low from the feature data, and from the management target system 10 ( j-1) While acquiring the 1st preservation | save data, the data acquisition interval until the next i-th data acquisition process is determined to be the basic time interval T1.

  Also in the i-th data acquisition, the data collection / recording apparatus 20 determines that the CPU load is low from the current feature data, acquires the j-th stored data from the managed system 10, and determines the data acquisition interval to T1. To do.

  Next, in the (i + 1) th data acquisition, the data collection and recording device 20 determines that the CPU load is high from the current feature data, interrupts data acquisition at that time, and sets the data acquisition interval to be greater than T1. The long time interval T2 is determined.

  Also in the (i + 2) -th data acquisition, the data collection / recording apparatus 20 determines that the CPU load is high, interrupts data acquisition at that time, and determines the data acquisition interval to T2.

  Next, in the (i + 3) th data acquisition, the data collection / recording apparatus 20 determines that the CPU load is low, acquires the (j + 1) th stored data from the managed system 10, and sets the data acquisition interval from T1. Is also changed to a short time interval T0. The relationship between the time intervals T0, T1, and T2 is T0 <T1 <T2.

  Thereafter, in the (i + 4) to (i + 11) th data acquisition, the data collection / recording apparatus 20 sequentially acquires the (j + 2) to (j + 9) th stored data at the time interval T0. In the (i + 11) -th data acquisition process, the data collection / recording apparatus 20 determines that the data acquisition has caught up with data storage, and changes the data acquisition interval to T1.

  In the (i + 12) th and subsequent data acquisition processes, the data collection and recording device 20 sequentially acquires the (j + 10) th and subsequent stored data at the time interval T1.

  FIG. 4 is a flowchart showing an example of the operation of the data collection and recording apparatus 20 according to the first embodiment. Hereinafter, the operation of the data collection and recording apparatus 20 (or the data collection and recording method according to Embodiment 1) will be described with reference to FIG. Note that the process in FIG. 4 is repeatedly executed, and the first process is started according to a start instruction from the user, for example, and the second and subsequent processes are timings based on the data acquisition interval determined in the previous process. Start with. It is assumed that the initial value of the data acquisition interval is set to the basic time interval T1.

  The data collection and recording device 20 transmits a data acquisition start request to the management target system 10 (S11), receives a data acquisition start response from the management target system 10 (S12), and extracts the current feature data from the data acquisition start response Then, it is determined whether or not the CPU load of the management target system 10 is high from the current feature data (S14).

  When it is determined that the CPU load is high (S14: YES), the data collection and recording device 20 transmits a data acquisition end notification to the management target system 10 (S15) and receives a data acquisition end response from the management target system 10. (S16). Then, the data collection and recording apparatus 20 sets the data acquisition interval to T2 (S17), and ends the process.

  On the other hand, when it is determined that the CPU load is low (S14: NO), the data collection and recording device 20 acquires and records the oldest stored data from the management target system 10 (S18). When the data acquisition is completed, the data collection and recording device 20 transmits a data acquisition end notification to the management target system 10 (S19), and receives a data acquisition end response from the management target system 10 (S20).

  Next, the data collection and recording device 20 determines whether the currently set data acquisition interval is T1 (S21). If it is T1 (S21: YES), the data acquisition interval remains T1 (S22). ), The process is terminated. On the other hand, when it is not T1 (S21: NO), the data collection and recording device 20 determines whether the currently set data acquisition interval is T2 (S23), and when it is T2 (S23: YES), data acquisition The interval is changed to T0 (S24), and the process ends. On the other hand, if it is not T2, that is, if it is T0 (S23: NO), the data collection and recording device 20 determines whether or not the data acquisition has caught up with data storage (S25). For example, the data acquisition start response from the management target system 10 describes the number of unsent storage data stored in the management target system 10, and the data collection and recording device 20 receives the data received in step S12. With reference to the acquisition start response, if the number of unsent stored data is “1”, it is determined that the catch-up has been caught up.

  If it is determined in step S25 that the data has been caught up (S25: YES), the data collection and recording device 20 changes the data acquisition interval to T1 (S26), and ends the process. On the other hand, if it has not caught up (S25: NO), the data acquisition interval remains T0 (S27), and the process ends.

  In the above description, the case where the data acquisition interval is switched in three stages, that is, T1 in the normal state, T2 when it is determined that the CPU load is high, and T0 when the temporarily stored data is extracted is illustrated. However, the data acquisition interval is not limited to three stages, and may be switched to multiple stages (four or more stages) according to the load state of the CPU.

  Further, the state value used as the feature data is not limited to the number of rotations of the pump, and other state values correlated with the CPU load of the management target system 10 such as the opening degree of various valves may be used.

  In the example of FIG. 2, the data collection / recording apparatus 20 indicates a case where desired data is specified and acquired one by one. However, the data collection / recording apparatus 20 may acquire a plurality of data collectively. And all the data may be acquired by one communication.

  In addition, when the data collection and recording device 20 is applied to different managed systems (for example, different types of hot water supply systems), it is assumed that the specifications of the communication unit of the managed system are different. In this case, for example, the data request transmitting unit 21b and the response data receiving unit 21c of the data collection and recording device 20 may be changed, and this change is realized by rewriting firmware that is control software in the data collection and recording device 20. it can. Instead of rewriting the firmware each time the managed system to be connected is changed, firmware corresponding to a plurality of managed systems is built in the data collection / recording apparatus 20 and the communication specification is switched by a switch (not shown). It may be a method or a method in which software automatically switches communication specifications in response to a response to a data acquisition start request.

In the above description, the configuration in which the processing load of the management target system is determined from the feature data and the data acquisition interval is determined based on the determination result has been exemplified. May be determined directly. For example, the data collection / recording apparatus 20 may obtain the data acquisition interval from the acquired feature data using a function (calculation formula, table, etc.) for converting the feature data into the data acquisition interval. Similarly, the data collection / recording apparatus 20 may directly determine whether to acquire detailed data from the feature data.
In the above description, a configuration having a plurality of features is illustrated, but the configuration is not limited to this, and the plurality of features may be appropriately omitted.

  According to the data collection and recording apparatus and data collection and recording method according to the first embodiment described above, the following effects (1) to (8) can be obtained.

  (1) The data collection / recording apparatus controls the data acquisition interval based on the feature data indicating the processing load of the management target system. As a result, the data acquisition interval can be controlled according to the processing load of the managed system, and the status data can be acquired from the managed system while suppressing the processing load of the managed system from becoming excessive. It becomes. Specifically, the higher the processing load of the managed system indicated by the feature data, the longer the data acquisition interval, thereby lowering the communication frequency when the managed system has a high processing load and managing it for communication processing. It is possible to suppress an excessive processing load on the target system.

  (2) When acquiring the status data, the data collection and recording device acquires the current feature data of the managed system, and when the current feature data indicates that the processing load of the managed system is low, When the detailed data is acquired and the processing load is high, the detailed data is not acquired. According to this configuration, it is possible to reduce the amount of communication during a period when the processing load of the management target system is high, and to suppress the processing load of the management target system from becoming excessive. Specifically, the feature data is received as a response to the data acquisition start request, and when it is determined that the CPU load of the managed system is high based on the feature data, the data acquisition is completed without acquiring the detailed data. This makes it possible to reduce the processing load for data acquisition when the CPU load of the management target system is high.

  (3) The data collection and recording device acquires the current feature data as the feature data, and as the detailed data, the oldest saved data that has not been transmitted among the saved data that is sequentially saved at a predetermined data saving interval in the managed system. Get the oldest saved data. According to this configuration, it is possible to appropriately control the data acquisition interval according to the current processing load of the management target system, and it is possible to acquire stored data stored at a predetermined time interval regardless of the data acquisition interval. For example, in a period when the processing load of the managed system is high, the communication frequency is suppressed by increasing the data acquisition interval, and detailed data (high importance data) in that period (high importance period) is acquired. Can do.

  (4) When the current characteristic data indicates that the processing load of the management target system is high, the data collection and recording device determines the data acquisition interval to be a time interval longer than the data storage interval, and then acquires the current acquired When the characteristic data indicates that the processing load of the management target system is low, the data acquisition interval is determined to be a time interval shorter than the data storage interval. As a result, the frequency of data acquisition is reduced during the period when the processing load of the managed system is high, and the frequency of data acquisition is set higher than the frequency of data storage during the period when the processing load of the managed system is low. The stored data stored in a high period can be quickly acquired.

  (5) After determining the data acquisition interval to be a time interval shorter than the data storage interval, the data collection and recording device has the same data acquisition interval as the data storage interval when there is no stored data to be transmitted in the managed system. Decide on a time interval. As a result, after there is no stored data that has not yet been transmitted, the status data can be acquired at appropriate time intervals.

  (6) The characteristic data indicates the state of the parts constituting the management target system (for example, the operation state of one or both of the solenoid valve and the pump), and is constituted by the state value used for controlling the operation in the management target system. . In this case, it is not necessary to acquire feature data specially on the management target system side, and the processing load on the management target system side can be reduced. Specifically, the CPU load of the managed system is estimated using the state value (for example, the pump state value) that the managed system already has, so that the CPU load is newly added on the managed system side. It is not necessary to perform processing for monitoring the system, and the processing load on the management target system can be reduced.

  (7) When it is estimated that the CPU load of the managed system is high, the communication interval for data acquisition is lengthened, temporarily held in the managed system, and when the CPU load is estimated to be low, Reduce the data acquisition interval. As a result, for example, even in a management target system that is configured with an inexpensive CPU and has a sufficient processing capacity of the CPU, it is possible to acquire data in a period during which the management target system is operating in detail.

  (8) In acquiring the status data, it is important to acquire detailed and long-term data when the managed system is operating. However, in the technique described in Patent Document 2, recording can be performed for a long time by reducing the amount of data in a period of low importance such as a period in which the management target system is not operating, but the management target system operates. If it is attempted to acquire detailed data during a period of high importance, the CPU load on the management target system increases due to communication processing. The operating state data is acquired from the managed system by serial communication, for example, but when acquiring detailed operating state data during a period of high importance, the CPU load of the managed system is interrupted by this communication processing interrupt. In some cases, the original operation of the management target system, such as control of hot water supply, may not be performed correctly. On the other hand, in the present embodiment, the CPU load of the management target system is estimated using the feature data, and when the CPU load is estimated to be high, the data acquisition time interval is widened temporarily on the management target system side. When the CPU load is estimated to be low and the CPU load is estimated to be low, the data held on the managed system side is acquired. This makes it possible to collect important state data without hindering the operation of the management target system using a CPU with low processing capability, and as a result, it is possible to appropriately analyze the operation state of the management target system. It becomes possible.

Embodiment 2. FIG.
FIG. 5 is a block diagram schematically showing an example of the configuration of the management system 2 according to the second embodiment. In the following description, the description of the same parts as those in the first embodiment is omitted or simplified, and the same or corresponding elements as those in the first embodiment are denoted by the same reference numerals. In FIG. 5, the management system 2 includes a management target system 10 and a data collection / recording apparatus 20 (an apparatus that can perform the data collection / recording method according to the second embodiment).

  The storage data stored in the managed system 10 typically includes a lot of data (state values). For example, in a hot water supply system, about 250 items of data such as detection values of various sensors are acquired. In such cases, not all the data is always useful for maintenance. During the period when the management target system 10 is not operating, much of the data is not necessary for maintenance or the like. On the other hand, during the period in which the management target system 10 is operating, a lot of data is useful for maintenance. Therefore, from the viewpoint of maintenance and management, it is desirable to acquire and record a lot of data, for example, all data during the period during which the management target system 10 is operating.

  On the other hand, from the viewpoint of the processing load of the managed system 10, as described in the first embodiment, during the period in which the managed system 10 is operating, the communication frequency is set so as not to hinder the operation of the managed system 10. It is desirable to reduce traffic and traffic.

  Therefore, the data collection / recording apparatus 20 according to the present embodiment controls the data acquisition interval based on the current feature data of the management target system 10 and is configured as follows, as in the first embodiment.

  When acquiring the oldest stored data, the data acquisition unit 21 receives characteristic data (hereinafter referred to as “storage time point”) indicating the processing load of the managed system 10 from the managed system 10 when the oldest stored data is stored. The data to be acquired is determined from the oldest stored data based on the feature data at the time of storage, and the determined data is acquired from the management target system 10. Specifically, the data acquisition unit 21 sets the data to be acquired so that as the processing load of the management target system 10 indicated by the feature data at the time of storage is higher, more data is acquired from the management target system 10. decide.

  In the example of FIG. 5, the data acquisition unit 21 includes a second feature data extraction unit 21d, a second processing load determination unit 21e, and an acquisition data determination unit 21f.

  The second feature data extraction unit 21d extracts feature data at the time of storage from the data received by the response data reception unit 21c. For example, in the data acquisition start response, the management target system 10 transmits the feature data at the time of storage together with the current feature data, and the second feature data extraction unit 21d obtains the feature data at the time of storage from the data acquisition start response. Extract. As in the first embodiment, the current feature data included in the data acquisition start response is extracted by the feature data extraction unit 23a and used for determination of the processing load by the processing load determination unit 23b. The acquisition interval is controlled. Note that the feature data extraction at the time of storage may be performed by the feature data extraction unit 23a.

  The second processing load determination unit 21e determines or estimates the processing load at the storage time of the management target system 10 from the feature data at the storage time extracted by the second feature data extraction unit 21d. For example, similarly to the processing load determination unit 23b, the second processing load determination unit 21e compares the feature data at the storage time with a predetermined threshold value to determine whether the processing load at the storage time is high.

  Based on the determination result of the second processing load determination unit 21e, the acquisition data determination unit 21f determines data to be acquired from the data included in the stored data, and acquires the determined data. 21b is instructed.

  In this example, in the management target system 10, a plurality of data included in the stored data is grouped (or hierarchized). For example, the importance of each data is determined from the viewpoint of the purpose of using the data such as maintenance, and the data is grouped according to the importance of each data. Then, the acquisition data determination unit 21f determines a data acquisition level indicating at which level the hierarchical data is acquired, and instructs the data request transmission unit 21b of the determined data acquisition level. The data request transmission unit 21b requests data based on the instructed data acquisition level, and the response data reception unit 21c selects the data corresponding to the data acquisition level (all hierarchized data among the oldest stored data). Or part).

  FIG. 6 is a diagram illustrating an example of the structure of saved data. FIG. 6 shows stored data 200 stored in one data storage process. The saved data 200 includes data groups 201, 202, and 203, and each data group includes a plurality of data (state values). A plurality of data included in the saved data 200 are grouped into three data groups 201, 202, and 203 according to the importance of each data (for example, the degree of importance in maintenance of the management target system 10). It has become. The data groups 201, 202, and 203 are arranged in the order of importance, have levels 1, 2, and 3, respectively, and the data group 201 has the highest importance. Further, a feature data address 211 and a feature data value 212 are arranged at the head portion of the saved data 200.

  In the above hierarchization, data is not dynamically exchanged according to importance, but, for example, data of parts that perform important operations (for example, the number of rotations of the pump) is grouped into the data group 201 and software The version information and the like are grouped into the data group 203, so that each data is fixedly grouped.

  When transmitting the data acquisition start response, the managed system 10 transmits the feature data value 212 arranged at the head of the stored data 200 to the data collection and recording device 20 as the feature data at the time of storage.

  The data collection / recording apparatus 20 determines the CPU load at the time of storage based on the feature data value 212 from the management target system 10 and, based on the determination result, all of the oldest stored data (hierarchical data) or Get a part. If all the data groups 201, 202, and 203 are acquired, a large amount of data is acquired for the operation state at that time, and if only the data group 201 is acquired, only important data is acquired with a small amount of data. If the data groups 201 and 202 are acquired, data is acquired with an intermediate data amount. Therefore, when it is determined that the CPU load at the time of storage is high, the data collection / recording apparatus 20 acquires all data in the data groups 201, 202, and 203, and when it is determined that the CPU load at the time of storage is low. In this case, only the data of the data group 201, that is, only some data having the highest importance is acquired.

  FIG. 7 is a diagram illustrating an example of the control of the data acquisition interval and the data acquisition level according to the CPU load. In FIG. 7, the horizontal axis indicates time t, and the vertical axis indicates the data amount. The upper side of FIG. 7 shows the time point of data storage processing and the amount of stored data stored at the time point in the management target system 10. The lower side of FIG. 7 shows the time point of data acquisition processing and the amount of state data acquired at the time point in the data collection and recording device 20. A plurality of arrows directed from the upper side to the lower side in FIG. 7 represent correspondences between saved data and status data (or movement of saved data from the management target system 10 to the data collection and recording device 20). The period TH indicates a period during which the CPU load of the management target system 10 is high.

  As illustrated in FIG. 7, the management target system 10 stores the stored data at a constant period at a basic time interval T1. FIG. 7 shows the (j−1) to (j + 11) th data storage processing.

  In the (i-1) th data acquisition process, the data collection / recording apparatus 20 determines that the current CPU load is low from the current feature data, and acquires the (j-1) th stored data from the management target system 10. At the same time, the data acquisition interval is determined to be the basic time interval T1. At this time, the data collection / recording apparatus 20 acquires the feature data at the (j−1) th storage time, determines that the CPU load at the storage time is low based on the feature data, and the (j−1) th storage data. Only the most important data (data of the data group 201) is acquired.

  Also in the i-th data acquisition, the data collection and recording device 20 determines that the current CPU load is low and determines that the CPU load at the time of storage is low, and only the most important data of the j-th stored data is obtained. At the same time, the data acquisition interval is determined as T1.

  In the (i + 1) and (i + 2) th data acquisition, the data collection and recording device 20 determines that the current CPU load is high from the current feature data, interrupts the data acquisition at that time, and sets the data acquisition interval. Determine to T2.

  In the (i + 3) th data acquisition, the data collection and recording device 20 determines that the current CPU load is low, acquires the (j + 1) th stored data from the managed system 10, and changes the data acquisition interval to T0. To do. At this time, the data collection / recording apparatus 20 determines that the CPU load at the (j + 1) th storage time is high, and acquires all of the (j + 1) th storage data. Similarly, also in the (i + 4) and (i + 5) th data acquisition, the data collection and recording device 20 acquires all of the (j + 2) and (j + 3) th stored data.

  In the (i + 6) to (i + 11) th data acquisition, the data collection / recording apparatus 20 determines that the CPU load at the time of storage is low, and sequentially selects only the most important data from the (j + 4) to (j + 9) th storage data. get. In the (i + 11) -th data acquisition process, the data collection / recording apparatus 20 determines that the data acquisition has caught up with data storage, and changes the data acquisition interval to T1.

  In the (i + 12) th and subsequent data acquisition processes, the data collection and recording device 20 sequentially acquires only the most important data among the (j + 10) th and subsequent stored data at the time interval T1.

  FIG. 8 is a flowchart showing an example of the operation of the data collection and recording apparatus 20 according to the second embodiment. The operation of the data collection / recording apparatus 20 (or the data collection / recording method according to the second embodiment) will be described below with reference to FIG. Note that the process of FIG. 8 is repeatedly executed in the same manner as the process of FIG. Further, it is assumed that the initial value of the data acquisition interval is set to the basic time interval T1.

  The data collection and recording device 20 transmits a data acquisition start request to the management target system 10 (S31), and receives a data acquisition start response from the management target system 10 (S32). Then, the data collection and recording device 20 extracts the current feature data and the feature data at the time of storage from the data acquisition start response (S33), and determines whether or not the current CPU load of the management target system 10 is high from the current feature data. Is determined (S34).

  When it is determined that the current CPU load is high (S34: YES), the data collection and recording device 20 transmits a data acquisition end notification to the management target system 10 (S35), and sends a data acquisition end response from the management target system 10. Receive (S36), set the data acquisition interval to T2 (S37), and terminate the process.

  On the other hand, when it is determined that the current CPU load is low (S34: NO), the data collection and recording device 20 determines the CPU load at the time of storage of the managed system 10 from the feature data at the time of storage extracted in step S33. It is determined whether or not it is high (S38).

  When it is determined that the CPU load at the time of storage is high (S38: YES), the data collection and recording device 20 determines the data acquisition level to “all” and acquires all of the oldest stored data from the management target system 10. (S39), and the process proceeds to step S41.

  On the other hand, when it is determined that the CPU load at the time of saving is low (S38: NO), the data collection and recording device 20 determines the data acquisition level to be “only the most important data” and stores the oldest saving from the managed system 10. Of the data, only the most important data is acquired and recorded (S40), and the process proceeds to step S41.

  In step S41, the data collection / recording apparatus 20 transmits a data acquisition end notification, receives a data acquisition end response, and sets a data acquisition interval, as in steps S19 to S27 of FIG.

  In the above description, the case where the stored data is hierarchized in three stages is illustrated, but the number of data hierarchies is not limited to this, and may be two hierarchies or four hierarchies.

  Further, in the above description, the case where the data acquisition level is switched to two stages is illustrated, but when the stored data is hierarchized in three stages, the data acquisition level is switched to three stages according to the determination result of the CPU load. Is possible. Further, when the stored data is hierarchized into four hierarchies, the data acquisition level can be switched to four stages.

  In the above description, the processing load at the time of storage of the management target system is determined from the feature data at the time of storage, and the data acquisition level is determined based on the determination result. The data acquisition level may be determined directly from the feature data. For example, the data collection / recording apparatus 20 may obtain the data acquisition level from the acquired feature data using a function (calculation formula, table, etc.) for converting the feature data into the data acquisition level.

  As described above, in the present embodiment, the data collection and recording device acquires feature data at the time of storage indicating the processing load of the management target system at the time when the oldest stored data is stored, and based on the feature data, The data to be acquired is determined from the oldest stored data. Thereby, it becomes possible to acquire appropriate data according to the processing load (or operation state) at the time of storage of the management target system.

  Specifically, the data to be acquired is determined so as to acquire more data from the managed system as the processing load of the managed system indicated by the feature data at the time of saving increases. Thereby, it is possible to acquire more data in the period during which the management target system is operating (period of high importance). For example, by controlling the data acquisition interval based on the current CPU load of the managed system and controlling the data acquisition level based on the CPU load when the stored data is stored, the CPU load of the managed system is excessive. It is possible to acquire detailed data for the period during which the managed system is operating.

  In addition, the lower the processing load on the managed system indicated by the feature data at the time of storage, the more data can be acquired from the managed system, thereby reducing the amount of communication data and not recording unnecessary data. , Visibility when checking data can be improved.

Embodiment 3 FIG.
FIG. 9 is a block diagram schematically showing an example of the configuration of the management system 3 according to the third embodiment. In the following description, the description of the same parts as those in the first embodiment is omitted or simplified, and the same or corresponding elements as those in the first embodiment are denoted by the same reference numerals. In FIG. 9, the management system 3 includes a management target system 10 and a data collection / recording apparatus 20 (an apparatus that can perform the data collection / recording method according to the third embodiment).

  In the present embodiment, the data collection and recording device 20 includes a file storage unit 25. The file storage unit 25 is a readable / writable recording device or recording medium, and may be included in the data recording unit 22. The file storage unit 25 includes data items to be acquired from the management target system 10 as feature data, and control information for determining one or both of whether to acquire a data acquisition interval and detailed data from the feature data. Is stored. For example, the setting file describes conditions for determining the processing load of the management target system 10 from the feature data as control information.

  The data collection and recording device 20 acquires feature data from the management target system 10 according to the items described in the setting file of the file storage unit 25, and is described in the setting file of the file storage unit 25 based on the feature data. In accordance with the control information, one or both of the data acquisition interval and whether to acquire the detailed data is determined.

  In the example of FIG. 9, the data collection and recording device 20 includes a data reading unit 26, a setting file reading unit 27, and a feature data instruction unit 28.

  The data reading unit 26 reads data stored in the file storage unit 25. The setting file reading unit 27 reads the setting file stored in the file storage unit 25 via the data reading unit 26. The feature data instruction unit 28 designates the feature data received as a data acquisition start response from the management target system 10 to the data request transmission unit 21b based on the setting file read by the setting file reading unit 27.

  FIG. 10 is a diagram illustrating an example of the data format of the setting file stored in the file storage unit 25.

  In FIG. 10, the setting file 300 describes target items 301, addresses 302, and threshold values 303 in association with each other. The target item 301 is an item of data to be acquired as feature data, and the address 302 indicates the data position on the management target system 10 of the data of the target item 301. The threshold 303 is a value used for determining the CPU load state.

  When the data collection / recording apparatus 20 is activated, the setting file reading unit 27 reads the setting file 300 stored in the file storage unit 25, reads the number of target items 301 described in the setting file 300, The number of items used for CPU load determination is calculated and the address of the target item is read.

  FIG. 11 is a sequence diagram illustrating an example of processing for data acquisition by the data collection and recording device 20 according to the third embodiment. Hereinafter, the data acquisition operation of the data collection and recording apparatus 20 according to the third embodiment will be described with reference to FIG.

  In FIG. 11A, when starting the k-th (k is an integer) data acquisition process, the data collection and recording device 20 sends a data acquisition start request to the management target system 10. The managed system 10 returns a data acquisition start response to the data collection recording device 20 in response to the data acquisition start request. At this time, when sending the data acquisition start request, the data collection and recording apparatus 20 notifies the management target system 10 of the address of the target item read from the setting file 300, and the management target system 10 returns a data acquisition start response. At this time, the data stored in the notified address is transmitted as feature data to the data collection and recording apparatus 20.

  When receiving the data acquisition start response from the management target system 10, the data collection / recording apparatus 20 extracts feature data from the data acquisition start response as in the first embodiment, and the CPU load of the management target system 10 based on the feature data Determine.

  In the k-th data acquisition process, it is determined that the CPU load is high, and the data collection and recording apparatus 20 interrupts the data acquisition and determines the data acquisition interval as in the first embodiment.

  In FIG. 11B, when starting the l-th (l is an integer) data acquisition process, the data collection and recording device 20 sends a data acquisition start request to the management target system 10 in the same way as the k-th process. The managed system 10 returns a data acquisition start response to the data collection / recording apparatus 20. Further, the data collection and recording device 20 extracts feature data from the data acquisition start response and determines the CPU load of the management target system 10.

  In the l-th data acquisition process, it is determined that the CPU load is low, and the data collection and recording device 20 acquires detailed data and determines the data acquisition interval as in the first embodiment.

  In each of the data acquisition processes, the data collection / recording apparatus 20 determines the CPU load using the threshold value for each target item described in the setting file 300. Specifically, the data collection and recording device 20 determines whether the value of the acquired feature data exceeds the threshold value described in the setting file 300 for each target item, and exceeds the threshold value for at least one target item. The CPU load is determined to be high. In the example of FIG. 10, it is determined that the CPU load is high when the pump rotational speed exceeds 1000 or the mixing valve opening degree exceeds 300.

  In the above description, one threshold is set for one target item in the setting file 300, but two or more thresholds may be set for one target item. Furthermore, a load determination condition using this threshold value may be described together with the threshold value. Such an example is shown in FIG.

  FIG. 12 is a diagram illustrating another example of the data format of the setting file stored in the file storage unit 25. In FIG. 12, the setting item 300a describes a target item 301 and an address 302 as in FIG. Further, unlike FIG. 10, two threshold values 304 and 305 are described as threshold values, and a conditional expression 306 is also described. In this example, at least one of the conditions that the number of revolutions of the pump is larger than 1000, the condition that the opening degree of the mixing valve 1 is 1, and the condition that the opening degree of the mixing valve 2 is larger than 500 and smaller than 1000 is satisfied. When it is determined that the CPU load is high. With such a data structure, it is possible to specify a determination range.

  In the setting file 300a in FIG. 12, a NULL character may be set for an item for which no value is set, such as a pump rotation speed threshold value 305, or a unique value that clearly indicates that no value is set, for example, For example, 0xFFFFFFFF may be set.

  Further, in the above description, when there is a plurality of target items, an example in which it is determined that the CPU load is high when any one of the items exceeds the threshold value, the CPU load determination method is limited to this. I can't. For example, if only one of the two elements corresponding to two target items operates and the CPU load differs greatly when both operate, the threshold comparison result of the two target items is It may be used in combination. Specifically, when both of the two target items exceed the threshold, the CPU load may be determined to be high (or low). That is, the CPU load may be determined based on the AND condition of the comparison result of the two target items. Alternatively, the CPU load may be determined by a combination of the OR condition and the AND condition in three or more target items. These conditions can be determined in advance based on the operation flow of the managed system 10.

  Further, the data structure of the setting file is not limited to the structure of FIG. 11 or FIG. 12, and for example, the number of target items may be described as a numerical value in the setting file. As a result, the feature data instruction unit can instantly recognize the number of target items.

  The setting file may include a model number of the management target system (or management target device), a version number of the data format, and date information. As a result, when a plurality of setting files are stored, the data collection and recording device 20 can identify them and switch the setting files according to the target device to acquire data.

  Further, the control information for determining the data acquisition interval from the feature data is not limited to the condition for determining the processing load of the management target system 10 from the feature data. For example, a table for converting the feature data into the data acquisition interval For example, it may be information for directly determining a data acquisition interval from feature data.

  In the above description, the case where the configuration related to the setting file is applied to the data collection / recording apparatus of the first embodiment is illustrated. However, the configuration of the present embodiment is applied to the data collection / recording apparatus of the second embodiment. May be.

  As described above, in the present embodiment, the data collection and recording apparatus stores a setting file in which items of data to be acquired as feature data and control information for determining a data acquisition interval and the like from the feature data are stored. A readable / writable file storage unit is provided. According to this configuration, it is possible to change feature data items and control information by rewriting the setting file, and it is possible to easily cope with various managed systems.

  Specifically, the feature data items to be used for the determination of the CPU load are different by specifying the item of the feature data of the management target system and the threshold condition for determining the CPU load based on the value by the setting file. When the data collection and recording device is applied to other managed systems and other managed systems that have the same feature data for CPU load determination but have different CPU load thresholds, only rewrite the configuration file. The state data can be acquired appropriately.

  For example, in a data collection and recording apparatus configured without using a setting file, in order to obtain appropriate data when the characteristics of the management target system change due to version upgrade of the management target system, the data collection and recording apparatus It is necessary to rewrite the program. On the other hand, according to the present embodiment, it is possible to cope with a change in the configuration of the management target system and a change in characteristics by simply rewriting the setting file.

Embodiment 4 FIG.
FIG. 13 is a block diagram schematically showing an example of the configuration of the management system 4 according to the fourth embodiment. In the following description, the description of the same parts as those in the first embodiment is omitted or simplified, and the same or corresponding elements as those in the first embodiment are denoted by the same reference numerals. In FIG. 13, the management system 4 includes a management target system 10 and a data collection / recording apparatus 20 (an apparatus that can perform the data collection / recording method according to the fourth embodiment).

  In the present embodiment, the data collection / recording device 20 averages the feature data acquired by the data acquisition unit 21 and uses the averaged feature data to determine the data acquisition interval and acquire detailed data. Make one or both decisions.

  In the example of FIG. 13, the data collection / recording apparatus 20 includes a feature data averaging unit 23d and a feature data holding unit 23e.

  The feature data averaging unit 23d averages the feature data acquired by the data acquisition unit 21 and extracted by the feature data extraction unit 23a, and sends the averaged feature data to the processing load determination unit 23b. Specifically, the feature data averaging unit 23d records the feature data for the past predetermined number of times in the feature data holding unit 23e, and averages the feature data for the past predetermined number of times held in the feature data holding unit 23e. Is sent to the processing load determination unit 23b. For example, when using feature data for the past three times, the feature data averaging unit 23d averages the average values of the feature data acquired this time, the previous feature data, and the previous feature data. It is calculated as converted feature data. When the new feature data is acquired, the feature data holding unit 23e deletes the oldest feature data and holds the latest feature data. When there is no past feature data immediately after the start of data acquisition, the feature data averaging unit 23d calculates feature data averaged using only the latest feature data, for example.

  The processing load determination unit 23b determines the CPU load of the management target system 10 based on the averaged feature data from the feature data averaging unit 23d.

  In the above description, the example for the past three times has been shown, but the number of data used for averaging is not limited to this, for example, according to the data recording interval, the operating state fluctuation rate of the management target system 10, etc. What is necessary is just to determine suitably.

  In the above description, the case where the configuration related to averaging is applied to the data collection and recording apparatus of the first embodiment is illustrated, but the configuration of the present embodiment is applied to the data collection and recording apparatus of the second or third embodiment. May be applied.

  As described above, in the present embodiment, the data collection and recording device averages the acquired feature data, and uses the averaged feature data to determine the data acquisition interval and acquire detailed data. Make at least one of the decisions. Thereby, it becomes possible to smooth the change of the characteristic data and perform more appropriate data acquisition.

  Specifically, when determining the CPU load of the management target system, by using a value obtained by averaging the operation state values of the past certain period, the instantaneous change in the operation state is smoothed, and the CPU load is more accurately detected. As a result, more appropriate data can be acquired.

  In the first to fourth embodiments described above, the function of the data collection and recording apparatus may be realized only by hardware resources such as an electronic circuit, or may be realized by cooperation of hardware resources and software. . When realized by the cooperation of hardware resources and software, the function of the data collection and recording device is realized by, for example, a data collection and recording program being executed by a computer. More specifically, the functions of the data collection and recording device are executed by a central processing unit (CPU) by reading a data collection and recording program recorded on a recording medium such as a ROM (Read Only Memory) into the main storage device. It is realized by doing. The data collection / recording program may be provided by being recorded on a computer-readable recording medium such as an optical disk, or may be provided via a communication line such as the Internet.

  In addition, this invention is not limited to the said embodiment, In the range which does not deviate from the summary of this invention, it can implement with a various aspect.

  1 to 4 management system, 10 managed system, 20 data collection and recording device, 21 data acquisition unit, 22 data recording unit, 23 data acquisition interval control unit, 23a feature data extraction unit, 23b processing load determination unit, 23c data acquisition interval A determination unit, 25 a file storage unit.

Claims (17)

A data acquisition unit that acquires state data related to the state of the managed system from the managed system at predetermined time intervals (hereinafter referred to as “data acquisition interval”);
A data recording unit for recording state data acquired by the data acquisition unit;
A data acquisition interval control unit that controls the data acquisition interval based on feature data indicating a processing load of the management target system among the state data acquired by the data acquisition unit;
When acquiring the state data, the data acquisition unit acquires current feature data indicating a current processing load of the management target system as the feature data, and the current feature data is a processing load of the management target system. Indicates that data other than the current feature data is acquired from the state data, and when the current feature data indicates a high processing load on the managed system, the other data Without obtaining
The data acquisition unit stores, as the other data, unstored data stored in the managed system at a predetermined time interval (hereinafter referred to as “data storage interval”) regarding the status of the managed system. A data collection and recording apparatus characterized by acquiring the oldest stored data to be transmitted .   The data collection / recording apparatus according to claim 1, wherein the data acquisition interval control unit increases the data acquisition interval as the processing load of the management target system indicated by the feature data increases. The data acquisition interval control unit sets the data acquisition interval to a time interval longer than the data storage interval when the current feature data acquired by the data acquisition unit indicates that the processing load on the managed system is high. After that, when the current characteristic data indicating that the processing load of the management target system is low is acquired by the data acquisition unit, the data acquisition interval is determined to be a time interval shorter than the data storage interval. The data collection and recording apparatus according to claim 1 or 2 , The data acquisition interval control unit sets the data acquisition interval to the data acquisition interval when there is no unsent storage data in the managed system after determining the data acquisition interval to be a time interval shorter than the data storage interval. 4. The data collection and recording apparatus according to claim 3 , wherein the time interval is determined to be the same as the storage interval. When acquiring the oldest stored data, the data acquisition unit acquires feature data at a storage time indicating a processing load of the management target system at the time when the oldest stored data is stored, and features at the storage time based on the data, the oldest data to be acquired among the stored data to determine the data collection recording device according to claim 1, characterized in that to obtain the determined data in any one of four. The data acquisition unit determines the data to be acquired so that as the processing load of the management target system indicated by the feature data at the time of storage increases, more data is acquired from the management target system. The data collection and recording apparatus according to claim 5 . The feature data, the management target constituting the system indicates the state of the components, any one of the six claim 1, characterized in that it is constituted by the state value which is used to control the operation in the managed system The data collection and recording device according to Item. The said characteristic data are comprised by the state value which shows the operation state of either the solenoid valve or pump which comprises the said management object system, or both, The one of Claim 1 to 7 characterized by the above-mentioned. Data collection and recording device. The data acquisition interval control unit
A feature data extraction unit that extracts the feature data from the data acquired by the data acquisition unit;
A processing load determination unit that determines the processing load of the management target system from the feature data extracted by the feature data extraction unit;
The processing load on the basis of the determination of the determination result, the data collection apparatus according to any one of claims 1 8, characterized in that it comprises a data acquisition interval determination unit configured to determine the data acquisition interval. The data collection and recording apparatus according to any one of claims 1 to 9 , wherein the processing load of the managed system is a load of a CPU that controls the operation of the managed system. Data items to be acquired as the feature data from the managed system and control information for determining one or both of whether to acquire the data acquisition interval and the other data from the feature data It further comprises a readable / writable file storage unit for storing the described setting file,
According to the items described in the setting file of the file storage unit, the feature data is acquired from the managed system, and based on the feature data, according to the control information described in the setting file of the file storage unit, the data acquisition apparatus according to any one of claims 1 to 10, characterized in that determining the one or both of whether or not to acquire the data acquisition interval and the other data. The feature data acquired by the data acquisition unit is averaged, and the averaged feature data is used to determine one or both of determining the data acquisition interval and determining whether to acquire the other data. The data collection and recording apparatus according to any one of claims 1 to 11 , wherein Including a managed system and a data collection and recording device,
The managed system includes a control unit that controls the operation of the managed system,
The data collection and recording device includes:
A data acquisition unit that acquires state data relating to the state of the managed system from the managed system at a predetermined time interval (hereinafter referred to as “data acquisition interval”);
A data recording unit for recording state data acquired by the data acquisition unit;
A data acquisition interval control unit that controls the data acquisition interval based on feature data indicating a processing load of the control unit of the management target system among the state data acquired by the data acquisition unit;
When acquiring the state data, the data acquisition unit acquires current feature data indicating a current processing load of the management target system as the feature data, and the current feature data is a processing load of the management target system. Indicates that data other than the current feature data is acquired from the state data, and when the current feature data indicates a high processing load on the managed system, the other data Without obtaining
The control unit stores storage data regarding the state of the managed system at a predetermined time interval,
The data acquisition unit acquires the oldest stored data that has not been transmitted among the stored data as the other data . A data acquisition step of acquiring state data relating to the state of the managed system from the managed system at a predetermined time interval (hereinafter referred to as “data acquisition interval”);
A data recording step for recording the state data acquired by the data acquisition step;
A data acquisition interval control step for controlling the data acquisition interval based on feature data indicating a processing load of the management target system among the state data acquired in the data acquisition step;
When acquiring the state data, the data acquisition step acquires current feature data indicating a current processing load of the management target system as the feature data, and the current feature data is a processing load of the management target system. Indicates that data other than the current feature data is acquired from the state data, and when the current feature data indicates a high processing load on the managed system, the other data Without obtaining
The data acquisition step includes, as the other data, unstored data stored in the managed system that is stored at predetermined time intervals (hereinafter referred to as “data storage intervals”) in the managed system. A method for collecting and recording data, characterized by obtaining the oldest stored data to be transmitted . In the data acquisition step, when acquiring the oldest stored data, the data acquisition step acquires characteristic data at a storage time indicating a processing load of the management target system at the time when the oldest stored data is stored, and features at the storage time 15. The data collection and recording method according to claim 14 , further comprising: determining data to be acquired from among the oldest stored data based on data, and acquiring the determined data. A file that stores in a readable / writable file storage unit a setting file in which items of data to be acquired as the feature data from the managed system and control information for determining the data acquisition interval from the feature data are described And further comprising a memory step,
According to the items described in the setting file of the file storage unit, the feature data is acquired from the managed system, and based on the feature data, according to the control information described in the setting file of the file storage unit, the 16. The data collection and recording method according to claim 14 , wherein a data acquisition interval is determined. The characteristic data obtained by the data acquisition step averages, using the feature data averaged, according to any one of claims 14 to 16, characterized in that the determination of the data acquisition interval Data collection and recording method.

Images