JPH11238043A - Host host data linking device for facility management - Google Patents

Abstract

(57) Abstract: The present invention relates to an upper host data linking device connected to a remote host device via a line and connected to a server device for managing facilities such as buildings and factories. An object of the present invention is to be unaffected by the load condition and to shorten the line use time. A processing device of an upper-level host cooperative apparatus is activated at regular intervals, generates a request for time-series data representing the state of each section of a facility to a server apparatus, and transmits the time-series data of each section collected from the server apparatus. A time-series data collection unit for storing data in the data storage unit, and when receiving a request for daily report data from a higher-level host device, retrieving the requested daily report data from the data storage unit and responding to the higher-level host device And a response unit.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an upper host data linking apparatus for facility management in cooperation with a remote upper host apparatus provided in a system for comprehensively monitoring and managing facilities such as buildings and factories.

2. Description of the Related Art A facility management system for maintaining and managing various facilities (e.g., lighting and air-conditioning devices for buildings, and various types of equipment) installed and operated in buildings, factories, etc. Monitoring information and time-series data information may be displayed and printed. However, if a trouble occurs in the facility management system for some reason, the acquisition of important monitoring information may be delayed, and the reliability of monitoring by the host device may be reduced.

[0003] Further, when cooperating with an upper-level host device via a public line, a large amount of data may be cooperated at a low speed. Therefore, if transfer is not performed as efficiently as possible, useless communication charges will increase. .

It is desired to improve the reliability of monitoring when a trouble occurs in the facility management system and to reduce the line use cost when using a public line.

[0005]

2. Description of the Related Art FIG. 19 shows a schematic configuration of a conventional facility management system. Reference numeral 80 denotes an upper-level host device provided remotely to a facility to be monitored, 81 denotes a public line (or a dedicated line or a LAN line). ), 82 is a host data linking device provided in each facility management system, 83 is a server device (including a display device and a control device) for monitoring and controlling the facility, and 84 is each point to be monitored and controlled. It is equipment provided with the device of.

In such a configuration, the following three techniques will be described below as conventional techniques. (1) Daily report data collection technique: When a daily report data request is issued from the upper host device 80, data for the previous day is collected from the server device 83 holding the master data of the daily report, and To respond to daily report data. This process does not require real-time processing,
Batch processing of data before the previous day.

(2) Equipment control / setting technology: control / setting request from the host device 80 to the equipment 84 (setting request such as turning on or off the state of a point device, setting a temperature value, etc.) ) Occurs, the server device 8
After notifying the control / setting request to the third device, the control unit waits for the completion of the control / setting for the equipment, and notifies the host device of the completion of the control / setting. This process is performed in real time.

[0008] (3) Application data linking technology: application data from an upper host device (for each group of devices, operation schedule data corresponding to daily time from Monday to Sunday, for example, temperature and the like are set within a certain range) When the data transfer is performed, the data transfer is performed to the display device or the monitoring device, the data transfer completion response wait is waited, and after the response is notified, the upper host device is notified of the data transfer completion. This processing is also performed in real time.

The prior arts (1) to (3) will be described below.
This will be described with reference to the drawings. (1) Daily report data collection technique FIG. 20 shows a conventional signal transmission / reception sequence for daily report data collection, and FIG. 21 shows a process configuration in a higher-level host data linking apparatus for conventional daily report data collection. As shown in FIG. 20, an upper-level host device 80 makes an irregular call and sends a daily report data request to a higher-level host data coordination device 82 via a public line 81. Send this request to 83.
At this time, as shown in FIG. 21, the host data linking device 82 activates the transmission / reception process p-2 in response to the daily report data request, and the transmission / reception process p-2 responds to the time-series data collection process p-1. When a daily report data request is output, and the time series data collection process p-1 receives the daily report data request, it acquires a time series data collection point from a daily report number table (not shown) and sends a time series data read request to the server device 83. Then, it waits for a time-series data read response. After receiving the time series data read response, returning a daily report data response to the transmission / reception process p-2, a next time series data collection point is acquired from the daily report number table, and the server device 8
3. Time series data acquisition is performed.

(2) Equipment control / setting technique FIG. 22 shows a conventional control / setting signal transfer sequence between devices, and FIG. 23 shows a conventional control / setting upper-level host data linking apparatus process configuration. Is shown. As shown in FIG. 23, a call is sent from the host device 80 to the line, and a control / setting request is sent to the host data cooperation device 82. The upper-level host data cooperation device 82 operates according to the process configuration shown in FIG. 23. When the transmission / reception process p2 is activated upon receiving a control / setting request, the transmission / reception process
2 is the control / setting request event is the control / setting process p1
Start Thereby, the control / setting process p1 transmits a control / setting request event to the target server device 83, and upon receiving a control / setting request response event from the target server device 83, sends the control / setting request event to the higher-level host device 80 via the transmitting / receiving process p2. Notifies control and setting completion. At this time, the field device starts operating in response to the control / setting instruction from the server device 83, and when a state change (state change) of the site is detected upon completion of the operation, it is sent to the server device 83. Thus, the server device 83 returns a request response event to the host data linking device 82.

(3) Application Data Linking Technology FIG. 24 shows a signal transfer sequence between conventional devices for transferring application data, and FIG. 25 shows a sequence in a higher-level host data linking device for conventional application data transfer. 2 shows a process configuration. As shown in FIG. 24, a call is made from the higher-level host device 80 to the line, and application data (schedule data corresponding to each day of the week for each equipment group and alarms for devices are transmitted to the higher-level host data cooperation device 82). Transfer large amounts of data, such as values in the upper and lower limits of the generated analog. Upon receiving the application data transfer request, the host data linking device 82 starts the transmission / reception process p-2 and sends an application data transfer request event to the application processing process p-1.

The application processing process p-1 processes the received event into an application data change notification event, and processes the server device 8 to which the data is to be transferred.
3 and wait for the data change to be completed.
The server device 83 issues an application data change completion notification event to the application data processing process p-1 when the reflection of the change data (set in each device of the facility) is completed, and the data reflection is normal. Is notified of whether or not it has been performed. The received application processing process p-1 notifies the host device 80 of the transfer result through the transmission / reception process p-2. The communication line is disconnected when an application data transfer end notification is received from the host device 80.

Although FIG. 24 shows that the data transfer is performed a plurality of times from the host data linking device to the server device, a large amount of data is divided into, for example, each group of facilities. This is done when transferring.

[0014]

In the above-described host data linking apparatus of the conventional facility management system, there are the following problems corresponding to the above (1) to (3), respectively.

As described above, according to the conventional technique for collecting daily report data, since the daily report data request from the host device is irregular, if the daily report data request is received when the server device is stopped due to maintenance or system down, Time series data cannot be returned to the host device.
This lowers the monitoring reliability of the host device. Also, if a daily report data request occurs when the server device is overloaded, a response delay of the time-series data read response to the time-series data read request occurs. At sites where there are many data collection points, communication efficiency is reduced, and there is a problem in that charges for lines are increased.

According to the conventional equipment control / setting technology,
Since the control / setting request is sent to the server device and then the control / setting request response event is waited for, the control / setting completion is notified to the host device after the control / setting request response event is received. There is a problem that the higher-level host device that is connected increases billing by the time for waiting for the control / setting request response event.

According to the application data linking technology, the application processing process waits until the application data is reflected. Therefore, when a large amount of data is transferred from the host device, the response waiting time increases in proportion to the data amount. When a connection is made via a public line, there is a problem that the charge increases due to an increase in response time.

An object of the present invention is to provide a host data linking apparatus for facility management which is not affected by the load condition of the server apparatus and can reduce the line use time. This is the first purpose. A second object of the present invention is to eliminate the need to occupy the line for waiting for the completion of control and setting, thereby eliminating unnecessary connection of the line. A third object is to shorten the line occupation in setting data.

[0019]

FIG. 1 shows a first principle configuration of the present invention, FIG. 2 shows an example of an operation sequence according to the first principle configuration, and FIG. 3 shows a second principle configuration of the present invention. , FIG.
5 shows an example of an operation sequence according to the second principle, FIG. 5 shows a third principle configuration of the present invention, and FIG. 6 shows an example of an operation sequence according to the third principle.

FIG. 1 shows a configuration for solving the first object of the present invention. In FIG. 1, reference numeral 1 denotes an upper host data linking device, 10 denotes a time-series data collection unit, 11 denotes a data storage unit,
12 is a daily report responder, 13 is a transmission / reception processor, 2 is a line, 3
Is a host device, 4 is a server device including a monitoring / control device and a display device of a facility such as a building, and 5 is a device of a facility to be managed and controlled.

In the host data linking apparatus 1 shown in FIG. 1, when the time series data collection unit 10 is started by an input representing a certain period, it requests the server apparatus 4 for time series data. When the server device 4 takes out the time series data of each device 5 of the facility and returns it as a normal response to the host data linking device 1, the time series data collection unit 10 stores it in the data storage unit 11. If a failure occurs on the server device 4 side, an error response is sent to the host data linking device 1.
, The time-series data collection unit 10 retries the request for the time-series data, and returns a normal response when the server device 4 recovers. After collection is performed by the upper host data linking apparatus 1, a call is sent from the upper host apparatus 3 from the line 2 to the upper host data linking apparatus 1 to send a request for daily report data. The transmission / reception processing unit 13 identifies the requested content and activates the daily report response unit 12. The daily report response unit 12 retrieves the requested daily report data from the data storage unit 11 and responds.
The data is sent to the host device 3 via the transmission / reception processing unit 13.

FIG. 2 shows an example of an operation sequence according to the first principle configuration, showing the relationship between the upper host device 3, the upper host data linking device 1, and the server device (monitoring / control device) 4 in the mutual control operation. In this way, even if a trouble occurs, a normal response is returned by retry in response to the generation of the time-series data request from the upper host data linking apparatus 1 and the daily report data from the upper host apparatus 3 is saved. Indicates an immediate response to the request.

FIG. 3 shows a configuration for solving the second object of the present invention. In FIG. 3, reference numerals 1 to 5 are the same as those in FIG. In the host data linking apparatus 1, 13 is a transmission / reception processing unit, 14 is a control / setting unit, 15 is an automatic alarm unit, and 16 is the state of the device to be controlled / monitored, information on each point, and the like. It is a device table to be stored.

In FIG. 3, when a request for control / setting is sent from the host device 3 to the line 2 to the host data linking device 1 to each device 5 in the facility, When received by the transmission / reception processing unit 13 of the device 1, the control / setting unit 14 refers to the device table 16 and determines whether a point to be controlled / set exists, and if so, its state (normal, abnormal, or deleted). Check). Note that “delete” means a state of being out of the monitoring or control target. If normal, the contents of the control / setting are sent to the server device 4 as a control / setting request, and the completion of reception is sent to the host device. Further, the control / setting unit 14 sets the state of the corresponding part of the device table 16 according to the contents of the control / setting. If the device table 16 is checked and an abnormality or deletion occurs, a monitoring flag corresponding to each device in the device table 16 is set, a timer (not shown) is started, and when a timeout occurs, a setting control retry is started. Further, control and setting of each unit of each device 5 of the facility are performed by the control of the server device 4, the operation of the on-site equipment is started, and when the operation is completed, the on-site state changes and the server device 4 changes the on-site state. When the information is input, it is also given to the host data linking apparatus 1. Here, if the contents are not matched with the contents of the device table 16, it is determined that an error has occurred, and control and setting are performed.
When an abnormal response is input to the host data linking apparatus 1, the automatic alerting unit 15 is started, and a facility error message is created, and the transmission / reception processing unit 13 sends a call to the host apparatus 3. Sent via line 2. As a result, the host device 3 can recognize the abnormal result of the control / setting request.

FIG. 4 shows an example of an operation sequence according to the second principle, showing the relationship between the upper host device 3, the upper host data linking device 1, and the server device (monitoring / control device) 4 in a mutual control operation. FIG. 4 shows an operation sequence according to the operation described with reference to FIG. 3. Even if a higher-level host device 3 calls a higher-level host data cooperation device 1 to control or set a line, the connection time is accepted. Short time to receive completion. If the control / setting is not performed normally, a call is issued from the host data linking apparatus 1 and notified to the host apparatus 3, so that the control / setting can be confirmed.

FIG. 5 shows a configuration for solving the third object of the present invention. In FIG. 5, reference numerals 1 to 5 denote the same components as those in FIGS. Then, in the host data linking apparatus 1, 13 is a transmission / reception processing unit,
Reference numeral 17 denotes an application processing unit that processes an application, 18 denotes an application transmitting / receiving unit that transmits / receives an application, and 19 denotes an application data storage unit.

In FIG. 5, when a call is sent from the host device 3 to the line 2 and an application data transfer request is made to the host data link device 1, the transmission / reception processing unit 1
At 3, the data is received for each group and sent to the application transmitting / receiving unit 18. The application transmitting / receiving unit 18 checks the received application data, and if the data is normal,
A normal response is sent from the application transmission / reception unit 18 to the host device 3 and a flag indicating a change is set and stored in the application data storage unit 19. In the case of an error, an error response is sent to the host device 3. When the transfer completion notification is received after the transfer of the data of all the groups is completed, the activation signal of the application processing unit 17 is sent.
Thus, when the application processing unit 17 starts,
The change data (change flag is set) stored in the application data storage unit 19 is transmitted to the server device 4 as data of each group. Thereafter, when the application processing unit 17 receives the notification of the completion of the data change from the server device 4 and detects that the data processing has been completed normally, the application processing unit 17 resets the change flag of the application data storage unit 19, and when an abnormality is detected, If the transfer to the device is not successful, the transmission / reception processing unit 13 transmits a notification of the occurrence of an abnormality to the host device 3.

FIG. 6 shows an example of an operation sequence according to the third principle, showing the relationship between the upper host device 3, the upper host data linking device 1, and the server device (monitoring / control device) 4 in the mutual control operation. FIG. 6 shows an operation sequence according to the operation described with reference to FIG. 5. When a call is made from the higher-level host device 3 to the higher-level host data cooperation device 1 and a large amount of application data is transferred, the reception completion is returned. Since the host device disconnects the line, the line connection time can be shortened. Further, when the setting (change) of the application data is abnormal, the notification of the abnormality is notified to the host device 3 as in FIG. 4, so that the result can be recognized.

[0029]

FIG. 7 shows an example of the configuration of a system in which the present invention is implemented. In FIG. 7, 1 to 5 correspond to FIGS.
6, 1 is an upper host data linking device, 2 is a line (any of LAN / dedicated line / switched line), 3 is an upper host device, and 4 is a controller for controlling the entire facility management system. Server device for monitoring (including input / output device including display), 5a is a facility management LAN, 5b is monitoring / control provided corresponding to devices (lighting device, air conditioner, etc.) constituting each group of the facility. The device, 5c is a terminal device (RS: Remote Station) provided at each site, and 5d is a facility monitoring point (control device or sensing device) in the facility.

The host data linking apparatus 1 cooperates with the host apparatus 3 via the line 2 and also manages the facility management LA.
It is connected to the server device 4 via N5a, and sends and receives data for monitoring and control. The server device 4 manages (monitoring / control) a number of monitoring / control devices 5b under the server device 4.

FIG. 8 shows the hardware configuration of the host data linking apparatus, and FIG. 9 shows the overall configuration of the process according to the present invention. In FIG. 8, reference numerals 1a to 1h denote components constituting a host data linking apparatus, 1a is a processing unit of the host data linking apparatus having a CPU and an internal memory, and 1b is an auxiliary storage device for holding a daily report time series file. (A hard disk or the like), 1c is an NCU (Network Control Unit) built-in modem for controlling transmission / reception to / from the host device 3 via the public line 2 and modulating / demodulating data, and 1d is communication control hardware , 1e is a communication driver program (dedicated line / public line), 1f is TC
P / IP driver, 1g is LAN driver, 1h is server device (display device and monitoring control device of facility management system)
LAN card for transmitting and receiving to and from the connected LAN,
2 is a public line, 3 is an upper host device, and 3a is a NCU built-in modem. 10a to 19a represent a process, a memory, and a table, each of which will be described later. 2 is a public line, 3 is an upper host device, and 3a is a NCU built-in modem.

Processing device 1 of host data linking device 1
a, a real-time OS, 101
Is a control processing unit having software shown in FIG. 9 described later, and 102 is another device communication process for performing communication processing with another device such as a server device.

The configuration of the processing apparatus shown in FIG.
A large number of processes, memories and tables indicated by reference numerals a to 19a are included, and each unit will be described below. 10a is a time series data collection process that is started by the time management process 10b to collect time series data from the server device (display device or monitoring / control device) and stores it in the daily report time series data file. 11a is a daily report time series data file for storing collected daily report time series data, 11b is a sigma table for setting system constants (process number, high load time, etc.), and 11c is facility equipment points A daily report number (indicated by NO) table storing correspondence information between addresses and daily report data numbers. A daily report 12a is activated when a daily report data is requested from an upper host device.
This is an inquiry processing daily report response process for responding to the time-series data in 1a.

Reference numeral 13a denotes a transmission / reception process which is started when a daily report data is requested from an upper-level host device and responds to time-series data in a daily report time-series data file. A control / setting process that is started and issues a remote control / setting command to the server device (target monitoring / control device). 15a receives a state change from the server device (target monitoring / control device), and if the control state changes, Automatic alerting process for issuing alerts, 1
Reference numeral 6a denotes a scanning memory in which the status of each equipment point in the facility is stored. 17a is activated under the control of an application transmission / reception process (18a to be described later) to request a server device (target monitoring / control device) to change application data. Application processing to be performed, 18
Reference numeral a denotes an application transmission / reception process which is started when an application data transfer request is received from the host device and issues an application data transfer request to the application processing process. Reference numeral 19a denotes an application data storage table for storing setting data of the application to be transferred. .

Various events i-1 to i-16 input from each process or output to each process shown in FIG. 9 will be described. i-1 is a daily report data request event that is notified when the daily host data is requested from the host device.

Reference numeral i-2 denotes a daily report data response event which is notified when daily report data is responded to the host computer. i-3 is a time-series data read request notified to the server device when reading the time-series data.

Reference numeral i-4 denotes a time-series data read response which is notified as a response to read the time-series data from the server device. i-5 is a remote control setting command event which is notified to the control setting process 14a when a remote control and setting is performed from the host device.

Reference numeral i-6 denotes a remote control setting command response event which is notified as a response when a remote control setting command from the host device is received. Reference numeral i-7 denotes a change data notification event that is notified when the remote control setting command of the host device ends abnormally.

Reference numeral i-8 denotes a remote control setting command event which is notified when a control / setting request is made to the server device (target monitoring control device) when a remote control setting command is issued from the host device.

Reference numeral i-9 denotes a change data notification event that is notified from the server device as a status change notification of the on-site equipment point by control / setting when a remote control setting command is issued from the host device.

Reference numeral i-10 denotes an application data transfer request event which is notified to the application transmission / reception process when the transfer of the host host application data is requested.

Reference numeral i-11 denotes an application data transfer end notification event notified from the application transmission / reception process when the transfer of the application data is ended from the host device.

Reference numeral i-12 denotes an application data transfer result notification event notified from the application processing process when the application data transfer end request ends abnormally.

Reference numeral i-13 denotes an application data change request event that is notified when a request for terminating the transfer of application data is made to the server device (target monitoring control device).

Reference numeral i-14 denotes an application data change response event which is notified as a response when a request for terminating the transfer of application data is made to the server device (target monitoring control device).

Reference numeral i-15 denotes an application processing start request event which is notified when a data transfer request is sent to the application processing process when a transfer request for application data is received from the host device.

FIGS. 8 and 9 show the configuration of the entire system having a plurality of functions according to the present invention and the configuration of the processing unit of the host data linking apparatus. The first to third principles of the present invention are realized. The configuration of each embodiment for achieving this will be described below.

FIGS. 10 to 12 show the configuration of the first embodiment corresponding to the first principle configuration (FIG. 1) of the present invention.
0 shows a configuration of a process for collecting daily report data according to the present invention, FIG. 11 shows a processing flow of a time series data collection process, and FIG. 12 shows a processing flow of an inquiry processing daily report response process.

The configuration shown in FIG. 10 is provided with other components related to the process related to daily data collection in the whole configuration shown in FIG. In FIG. 10, 1a is a processing device, 10a, 11a to 11c, 12a, 13a, 3, 4
Are the same as those in FIG. 9 having the same reference numerals, and a description thereof will be omitted. 10b is a time management process, 10c is a time management package (indicated by PKG) for managing the time of regular startup, and 10e is a time monitoring table. When the time is set in the time monitoring table 10e, the time management process 10b performs a timer operation and generates an output due to timeout.

FIG. 11 shows a time series data collection process (FIG. 1).
0, that is, 10a), and the received event ID is checked first (S1 in FIG. 11). Normally, regular time (for example, every n minutes on the hour) from the time management package (10c in FIG. 10)
Is waiting for the time start event, and when the ID of the time start event is received, the sigma table (1 in FIG. 10)
The time-series data collection prohibition time is referred to from 1b), and a prohibition time zone check is performed (S2 in FIG. 11). If it is not a prohibition time zone, the day of the week from the previous day to seven days before is acquired (S3 in FIG. 11), the date is acquired from the daily report time series data file 11a corresponding to the day of the previous day (S4), and the date is matched. The start completion determination of the time series data collection is performed by the sex check (S5). If the dates match, it is determined whether collection of the time-series data for that date has been completed for all points (S12 in FIG. 11), and if completed, it is determined whether collection has been completed for one week (S16). ). If all are consistent, it is determined that time-series data collection has been completed, and the process is terminated.

If there is no match in S12, a time-series data collection point is acquired from the daily report number (displayed as NO) table 11c (S13 in FIG. 11), and a time-series data read request is transmitted to the server device 4 (S14). . At this time, the response monitoring timer for the time-series data read request is started, and the response time is monitored (S15 in FIG. 11). When a time-series data read response is received after the transmission of the time-series data read request, a reception event ID check is performed in S1 of FIG. 11 and if a time-series data read response event is identified, a response monitoring timer is stopped. (Figure 1
1 S6), the response contents are converted to the daily report time series data file 11
is written to a (S7), and the collection pointer number is set as collected (S8).

After the response monitoring timer is started in S15 and timed out and a timeout event occurs, if this is identified by the reception event ID check, a retry count check is performed (S9 in FIG. 11). If so, the retry counter is counted up (S17), and the time series data read request of the same series data collection point is transmitted again. If the number of retries is exceeded, the retry counter is cleared (S10 in FIG. 11), and missing data (no data) is written to the corresponding point position in the daily report time series data file (S10).
11), the next time-series data collection point is obtained from the daily report number table and time-series data collection is performed. This process is performed for the number of time-series data collection points registered in the daily report number table. If collection of time-series data for one week has not been completed after collection of all points has been completed, time-series data collection for the next date is performed. If the time series data collection for one week has been completed, the process is terminated.

FIG. 12 shows an inquiry processing daily report response process (FIG. 1).
0, 12a). First, the received event ID is checked (S1 in FIG. 12), and upon receipt of the daily report data request event, the request date is checked for validity (S2). This check checks whether the request date of the daily report data request event is within the range of seven days before the previous day. If the daily report data request date is out of the range, an error response transmission process is performed to the host device (S11 in FIG. 12), and the process is terminated. If appropriate, obtain the day of the week for the requested date (Fig. 1
2 S3), a time-series reference position (address) of the requested daily report number is obtained from the requested daily report number table 11c (S3).
4) It is determined whether the requested daily report number exists in the daily report number table 11c (S5), and if not, an error in the daily report data is returned, and the process proceeds to the next requested daily report number.

If the requested daily report number exists, the date is acquired from the daily report time series data file 11a for the corresponding day (S6 in FIG. 12), and the consistency with the requested date is checked (S7). If the date in the daily report time series data file is different from the requested date, an error response is sent and the process ends. When the consistency is obtained, the data of the corresponding daily report number is obtained from the daily report time series data file (S8 in FIG. 12),
Sends a daily report data response to the host device (S
9). Thereafter, the process moves to the next requested daily report number and continues until data transmission is completed for all requested daily report numbers (S10 in FIG. 12).

As described above, time-series data can be notified irrespective of the state of a failure or load of the server device. FIG.
3 and FIG. 14 show a configuration of a second embodiment corresponding to the second principle configuration (FIG. 3) of the present invention, FIG. 13 shows a configuration of a process for control and setting according to the present invention, and FIG. It is a processing flow of a control setting process.

FIG. 13 shows a process related to control / setting and a related configuration in the entire configuration shown in FIG. In FIG. 13, reference numeral 1a denotes an upper-level host cooperative apparatus;
0d is a time monitoring process that performs time monitoring with a timer,
13a is a transmission / reception process, 14a is a control setting process for controlling and setting the server device (target monitoring / control device) 4, 15a is an automatic alarm process, 16a is a scanning memory, 16b is a device information table, Reference numeral 3 denotes an upper host device, and reference numeral 4 denotes a server device (object monitoring / control device).

FIG. 14 shows a control setting process (14 in FIG. 13).
This is a processing flow of a), in which a reception event ID check is first performed (S1 in FIG. 14), and a transmission / reception process (FIG. 13)
When the control / setting request event from 13a) is received, it is determined whether the control content of the received message from the upper host device is normal (S2), and if abnormal, a response message indicating an error is transmitted to the upper host device ( The process of notifying to 3) of FIG. 13 is performed (S15 and S16), and the process is terminated. If the control content is normal, the process proceeds to the next process. That is, a scanning memory (FIG. 13) that performs message address conversion (S3 in FIG. 14) and manages points of the monitoring / control device of the server device.
16a) is referred to (S4), and it is checked whether there is a control point requested to be controlled / set (S5). If the control point does not exist, an abnormality is notified to the host device in the same manner as described above, and if the control point exists, the device status is referred from the device information table (16b in FIG. 13) (S6).

The device information table stores the device status of the target monitoring / control device (node error or deletion, line error or deletion, RS error or deletion, normal, etc.). Check (S7 in FIG. 14). If an error occurs during this device status check,
Since the control / setting request event cannot be transmitted to the target monitoring / control device, the monitoring flag of the control / setting request target point in the scanning memory is set to “1” (S1 in FIG. 14).
0), a time monitoring timer for performing re-control / setting after a predetermined time is started (S11). When the device status is normal, the scanning memory (1 in FIG. 13) is used.
With reference to 6a), it is determined whether the control / setting point state is normal (S8 in FIG. 14).
0 and S11, and if it is normal, an event of a control / setting request is transmitted to the corresponding monitoring / control device (S1).
9).

The control / setting request is sent to the server (object monitoring /
After transmission to the control device, it is determined whether the control transmission result is normal (S12 in FIG. 14), and if it is normal, control information is set in the scanning memory (S13), and the display device (display device of the server device) ) Is output and displayed (S14). Subsequently, a response message indicating normality is created (S15 in FIG. 14), and the response message is transmitted to the upper-level host device (S16).

After setting the monitoring timer in S11, when a monitoring timeout event is detected in the reception event ID check (S1 in FIG. 14), the retry counter is counted up (S17 in FIG. 14), and the retry count is exceeded. It is determined whether or not the process has been performed (S18). If the value does not exceed the value, the process proceeds to step S6. .

The automatic alerting process 15a shown in FIG.
Starts when a control / setting request response event from the target monitoring / control device (server device) is notified, stores the contents of the state of the point of the control / setting request response event in the scanning memory, and sends it to the upper-level post device. A notification is made as a status change notification.

When the control / setting request from the host device is notified to the server device according to the second embodiment, it is not necessary to occupy the line to notify the host device of the completion notification.

FIGS. 15 to 18 show the structure of the third embodiment corresponding to the third principle structure (FIG. 5) of the present invention.
5 shows a configuration of a process for controlling and setting application data according to the present invention. FIG. 16 shows a processing flow of an application transmission / reception process, FIG. 17 shows a processing flow of an application processing process, and FIG. 18 shows a flow of a retry process.

In FIG. 15, 13a is a transmission / reception process, 17a is an application processing process, 18a is an application transmission / reception process, 19a is an application data storage table, 3 is an upper host device, and 4 is a server device (target monitoring / control device). .

FIG. 12 is a processing flow of the application transmission / reception process (18a in FIG. 15). When an application data transfer request is received from the host device through the transmission / reception process (13a in FIG. 15), the event reception is determined. (S1 in FIG. 16), when this transfer request is detected, the data consistency is checked (S2), the normality of the data is checked (S3), and if an error occurs, a data error is set in an error code and the host An error code is set in the error details in the application data transfer result notification event responding to (1), and the error code is transmitted to the host device via the transmission / reception process (S8).

If the data is normal, the normal is set in the error details in the application data transfer result notification event responding to the host and transmitted. Next, the received data is stored in the storage area of its own group in the application data storage table (table configuration differs for each application, and storage area is provided for each group) (FIG. 1).
6, S5), the change flag of the group that has been changed in the application data storage table is updated to ON (S6). This operation is repeated for the number of transfer requests received. The communication line is closed when the application data transfer end notification is transferred from the host device. At that time, the application transmission / reception process transmits an application processing start notification to the application processing process (S9 in FIG. 16). The application processing process (17a in FIG. 15) of FIG.
Event reception is determined (S1 in FIG. 17), and upon receiving an application processing start notification from the application transmission / reception process in FIG. 16, the loop count a is set to 0 (S2). This loop count a represents the number of groups. It is determined whether or not the loop count a reaches the total number of groups (S3 in FIG. 17). If not, it is determined whether or not the change flag of the corresponding group number (loop count + 1) in the application data storage table (19a in FIG. 15) is on. (S6), if it is ON, a change notification event is created based on the application data storage table and transmitted to the server device (target monitoring / control device) (S6).
7). If it is determined in S3 that the total number of groups has been reached, it is determined whether the retry count is 0 (S4 in FIG. 17). If the retry count is 0, the process returns to S1, and if not, the retry process (see FIG. 18 described later). ) (S5).

Next, the process waits for reception of a data change completion notification event from the monitoring / control device (S8 in FIG. 17), and upon reception, determines whether the processing result in the event ends normally (S8).
9) If the processing ends normally, the change flag of the corresponding group in the application data storage table is updated to OFF (S10), and the loop count a is incremented by 1 (S1).
1) For the corresponding group, the process proceeds to S3 and subsequent steps. If the data change completion notification event is not received from the monitoring / control device in S8, or if the processing result in the event does not end normally in S9, the retry count is incremented by 1 (S12 in FIG. 17), and the retry count is valid from the application data. Calculate the time. This result is stored in the effective time storage area of the corresponding group in the application data storage table (S13), and the transmission count of the corresponding group in the application data storage table is incremented by +
Then, the process returns to S3 and the same process is repeated for the next group. Note that the valid time of the above data is meaningless unless the data is set by a certain time. For example, in the schedule time parameter setting, when the first ON time has passed, or when the analog There is a case where the start time of the monitoring time period has elapsed in setting the upper and lower limit monitoring parameters.

FIG. 18 shows the contents of the retry processing (S5 in FIG. 17). In this retry process, when the first transmission of the changed group in FIG. 17 is completed, the retransmission of the group whose transfer has been abnormally terminated is retransmitted.

First, the retry count is set to 0 (S1 in FIG. 18), and the loop count b is set to 0 (S1).
2). It is determined whether or not the loop count b matches the total number of groups (S3).
It is determined whether or not it is (S4). If the value is 0, the process shifts to the event reception wait. If the value is not 0, the process returns to S1 in FIG. If they do not match, it is determined whether the change flag of the corresponding group number in the application data storage table is on and the transmission count is other than 0 (S5 in FIG. 18). If so, it is determined whether the current time is before the effective time (S in FIG. 18).
6) In the previous case, it is determined whether the number of transmissions in the application data storage table is within the maximum retry (MAX) (S7). When the current time has passed in S6 and when the number of retries has reached the maximum in S7, an application data abnormality occurrence notification is transmitted to the host device at that time (S12). When the retry limit is not reached, a change notification event is created based on the application data storage table and transmitted to the server device (S8 in FIG. 18).

Subsequently, it is determined whether or not a data change completion notification event has been received from the monitoring / control device (S9 in FIG. 18).
Upon receipt, it is determined whether the processing result in the event is normal termination (S10). If the processing result is normal termination, the change flag of the corresponding group in the application data storage table is updated to OFF (S11), and the next group proceeds to S3. Return. When the data change completion notification event is not received in S9, or when the processing result in the event is not completed normally in S10, the retry count is incremented by one (S13), and the transmission count of the corresponding group in the application data storage table is incremented by one. And store it (S1
4). In this way, if the transfer result is abnormal even if retransmission is performed a certain number of times within the valid time, an application data transfer error occurrence notification is reported to the host device at that time.

[0071]

According to the present invention, the following effects can be obtained. (1) According to the first principle of the present invention, time-series data can be notified to an upper-level host device irrespective of a failure condition or a load condition of a server device.

(2) According to the second principle of the present invention, there is no need to occupy the line for waiting for the completion of control / setting, so that no extra charge is charged even if the connection is made via a public line. Also, even when an error occurs, the host is not required to retry, so that the communication is simplified.

(3) According to the third principle of the present invention, there is no need to occupy the line for waiting for the completion of application data setting. There is no charge. In addition, even when an abnormality occurs, the host device does not need to retry, so that communication is simplified.

By combining these effects, it is possible to improve the performance and security of the facility management system and reduce the communication cost.

[Brief description of the drawings]

FIG. 1 shows a first principle configuration of the present invention.

FIG. 2 is a diagram showing an example of an operation sequence according to the first principle configuration.

FIG. 3 shows a second principle configuration of the present invention.

FIG. 4 is a diagram showing an example of an operation sequence according to the second principle configuration.

FIG. 5 shows a third principle configuration of the present invention.

FIG. 6 is a diagram showing an example of an operation sequence according to a third principle configuration.

FIG. 7 is a diagram illustrating a configuration example of a system in which the present invention is implemented.

FIG. 8 is a diagram illustrating a hardware configuration of an upper-level host data cooperation device.

FIG. 9 is a diagram showing an overall configuration of a process according to the present invention.

FIG. 10 is a diagram showing a configuration of a process for collecting daily report data according to the present invention.

FIG. 11 is a diagram showing a processing flow of a time-series data collection process.

FIG. 12 is a diagram showing a processing flow of an inquiry processing daily report response process.

FIG. 13 is a diagram showing a configuration of each process for control / setting according to the present invention.

FIG. 14 is a diagram showing a processing flow of a control setting process.

FIG. 15 shows application data control according to the present invention.
FIG. 4 is a diagram illustrating a configuration of a process for setting.

FIG. 16 is a diagram showing a processing flow of an application transmission / reception process.

FIG. 17 is a diagram illustrating a processing flow of an application processing process.

FIG. 18 is a diagram illustrating a flow of a retry process.

FIG. 19 is a diagram showing a system configuration of a conventional facility management.

FIG. 20 is a diagram showing a conventional signal transmission / reception sequence for collecting daily report data.

FIG. 21 is a diagram showing a process configuration in a conventional host data linking apparatus for collecting daily report data.

FIG. 22 is a diagram showing a conventional signal transmission / reception sequence for control / setting.

FIG. 23 is a diagram showing a process configuration in a higher-order host data cooperation apparatus for control / setting according to the related art.

FIG. 24 is a diagram showing a conventional signal transmission / reception sequence for application data transfer.

FIG. 25 is a diagram showing a process configuration in a higher-order host data cooperation device for transferring application data in the related art.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 High-order host data cooperation apparatus 10 Time series data collection part 11 Data storage part 12 Daily report response part 13 Transmission / reception processing part 2 line 3 High-order host apparatus 4 Server apparatus 5 Each facility equipment

Claims (5)

[Claims] 1. An upper host data linking device connected to a remote host device via a line and connected to a server device for managing facilities such as buildings and factories, wherein the processing device of the host data linking device is A time-series data collection unit that starts at a fixed period, generates a request for time-series data indicating the state of each unit of the facility to the server device, and stores the time-series data of each unit collected from the server device in a data storage unit And a daily report responding unit that, when receiving a request for daily report data from a higher-level host device, retrieves the requested daily report data from the data in the data storage unit and responds to the higher-level host device. Host host data linking device for facility management. 2. The processing device of the upper host data linking device according to claim 1, further comprising a device table for holding status information of each unit of each device to be controlled / monitored. When a request to control and set the status is received, the status of each device is checked with reference to the device table, and the request for control and setting is checked. A control / setting unit that returns a notice of completion of reception to the host device, and, when receiving a notification of a change in the status of the device by the control / setting from the server device, checks the normality and detects an error, and generates an abnormal response to the host device. An upper host data linking device for facility management, comprising: 3. The control / setting unit according to claim 2, wherein the device table of the control / setting unit comprises a scanning memory for storing a status of each control point and a device information table for holding a status of each device. If the control point corresponding to the setting request does not exist, an abnormal response is notified to the upper host device. If the device status and the control point status are not normal, a monitoring flag is set in the scanning memory. An upper-level host data linking device for facility management, wherein a monitoring timer is set, and when a timeout occurs, a retry of checking the device status and the control point is performed. 4. The processing device according to claim 1, wherein the processing device of the higher-level host data cooperation device receives the request for setting application data including schedule data for each equipment group from the higher-level host device, and completes the reception with the higher-level host device. And an application transmitting / receiving unit that stores and saves a flag indicating a change and corresponding data in an area corresponding to each facility in the application data storage unit, and is activated by the application transmission / reception unit and stores the data in the application data storage unit. Application data in which a flag indicating a change to each group is set is transferred to the server device as change data, and a data change completion notification is received from the server device, and is notified to the host device only in the case of abnormal termination. An upper host data linking apparatus for facility management, comprising: an application processing unit that generates an abnormal response. 5. The application processing unit according to claim 4, wherein the application processing unit does not receive a data change completion notification from the server device for the transfer of the application data for each group, or within a predetermined number of times if the notification content is not normal. A retry of the corresponding application data is stored in the application data storage unit, and if the time is within the valid time, the transmission of the change data is retried. Host data linkage device.