JP2011054060A - Monitoring system, control method of the same, and control program for the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a mechanism for providing a device monitoring system and the like which recognize situations of each of pieces of facility equipment in detail at a lower cost. <P>SOLUTION: In a monitoring system in which a monitoring server 106, a video-recording server 104, and a management terminal for controlling photography of photography equipment are communicably configured, the video-recording server includes: an index generation means for generating index information for associating images corresponding to event information received from the monitoring server with one another; and an index transfer means for transferring the generated index information to the monitoring server. The monitoring server includes: an information transfer means for transferring the obtained event information to the video-recording server and the management terminal; and a history information storage means for storing history information which includes the obtained event information and the index information received from the video-recording server corresponding to the event information. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a device monitoring system, and in particular, for example, to grasp the operating status of each device in a building in detail by linking events such as malfunctions for each device, a captured image of the device at the time of the event, and the current status. The present invention relates to a monitoring system, a control method for the monitoring system, and a control program for the monitoring system.

  2. Description of the Related Art Conventionally, equipment monitoring systems that can transmit error and warning information of so-called building devices such as building air conditioning equipment, hot water supply equipment such as boilers, power distribution equipment, and the like to a monitoring terminal via a network have been widely used. In addition, for disaster prevention and crime prevention purposes, a mechanism for photographing various places such as a room in a building, an elevator hall, and a corridor with a surveillance camera and switching and displaying on a monitor of the disaster prevention center is widely used.

  Patent Document 1 discloses, via a network, image information indicating the display contents of a monitor of the monitoring device by photographing a screen of each customer's monitoring device (monitoring monitor) with a camera and warning information received from each facility by the monitoring device. There has been disclosed a remote monitoring system for equipment that is configured to be remotely identifiable.

Japanese Patent Laid-Open No. 2002-032880

  However, although the facility device remote monitoring system of Patent Document 1 can monitor many facility devices with a small number of people, the monitoring camera only captures the display content of the monitor of the monitoring device. There was a problem that the situation at the time of equipment failure could not be grasped. In particular, when a failure occurs in an important equipment that is directly connected to the safety of the building, it is necessary for the maintenance staff of the building to go directly to the status of the equipment. There was a problem that it was difficult to deal with. Furthermore, when troubles of equipment occur occasionally and end in a short period, but recur, there is also a problem that it is difficult to find out the cause because the trouble occurrence status cannot be grasped even when looking at the equipment.

  In addition, when equipment failure occurs in a short period of time after equipment maintenance and inspection, it is a problem whether the contents of the equipment maintenance and inspection work are appropriate. The contents of the inspection work could not be verified because it was not possible to shoot and store. Also, when an error or warning occurs in a specific facility device, if the error or warning occurs to the victim due to a malfunction of the facility device linked to the cause of the facility device itself, the cause is identified. There is also a problem that it takes a long time to recover the trouble and trouble to investigate the true cause.

On the other hand, even if an error or warning occurs due to a malfunction in the equipment, if a malfunction occurs in a specific part, especially a large part that is not normally in stock at the service base, an error or warning occurs in a specific equipment Since only the equipment manufacturer was informed of the situation by telephone, the equipment manufacturer's engineer checked the situation at the site and contacted the component manufacturer for the first time. There was a problem that it took time to recover from the failure.

  Accordingly, an object of the present invention is to provide a device monitoring system and the like that can quickly respond to errors and warnings.

The first invention for achieving the above-described object is as follows:
A monitoring system configured to be able to communicate with a monitoring server that stores event information received from a facility device to be monitored, a recording server that stores image information received from a photographing device, and a management terminal that performs photographing control on the photographing device Because
The recording server
Image storage means for storing images taken by the photographing device, index generation means for generating index information for associating the images corresponding to event information received from the monitoring server, and the generated index information An index transfer means for transferring to the monitoring server;
The monitoring server is
An acquisition means for acquiring event information including an error or a warning transmitted from the facility device or a sensor associated with the facility device and detecting a state of the facility device; the recording server and the management of the acquired event information Information transfer means for transferring to a terminal, and history information storage means for storing history information including the acquired event information and index information received from the recording server corresponding to the event information,
The management terminal
Control information storage means for storing correspondence between each equipment device and photographing equipment capable of photographing the equipment equipment and photographing parameters, and referring to the control information storage means using the transferred event information, Shooting control means for transmitting predetermined shooting parameters to the shooting device so as to cause the shooting device associated with the facility device to shot an event-time image that is an image of the facility device that has transmitted the event information, and the history information Display control information for generating display control information for comparing and displaying the event-time image of the facility device stored in the image storage means and the current image that is currently captured by the facility device Means.

  According to a second aspect of the invention for achieving the above-described object, the management terminal is any one of the event-time image and the event information, or the event information in accordance with event information received from the equipment or the sensor. And determining means for specifying to which image the event image and the event information or the event information are to be transferred.

The third invention for achieving the above-described object is as follows:
Control information storage means for storing the correspondence between equipment to be monitored and photographing equipment capable of photographing the equipment, image information received from the photographing equipment and the equipment associated with the equipment or the equipment A monitoring system control method comprising index information that associates event information including an error or warning transmitted from a sensor that detects the state of a device, and history information storage means that stores history information including the event information. And
An acquisition step of acquiring the event information from the equipment or the sensor,
Referring to the control information storage unit according to the event information acquired in the acquisition step, an event-time image that is an image of the facility device that has transmitted the event information is captured by a photographing device associated with the facility device. A shooting control step of transmitting predetermined shooting parameters to the shooting device to
And a display control step of comparing and displaying the event-time image of the equipment and the current image of the equipment using the history information.

A fourth invention for achieving the above-described object is as follows:
A monitoring system for monitoring facility equipment, comprising: control information storage means for storing correspondence between each of the equipment equipment and photographing equipment capable of photographing the equipment equipment; and image storage means for storing image information received from the photographing equipment. And history information including the event information and index information that associates the event information including an error or warning transmitted from the facility device or a sensor that detects the state of the facility device with the facility device. A control program for a monitoring system comprising information storage means,
The monitoring system;
An acquisition means for acquiring event information including an error or a warning transmitted from a sensor associated with the facility device or the facility device and detecting a state of the facility device;
The imaging device refers to the image storage unit according to the acquired event information, and causes the imaging device associated with the facility device to capture an event-time image that is an image of the facility device that has transmitted the event information. Photographing control means for transmitting predetermined photographing parameters to
The history information is used as a display control means for displaying the event image of the facility device and the current image of the facility device in a comparative manner.

  According to the present invention, according to the error or warning for each equipment device, it is possible to quickly take an image of the equipment in which the error or warning has occurred and display it on the monitoring terminal, as well as the error, warning and occurrence time of occurrence. Since images can be stored in association with each other, it is possible to provide a building facility monitoring system or the like that can grasp the situation of each facility device in detail at a low cost.

It is a system configuration figure showing an example of the composition of the building equipment monitoring system of the present invention. It is a hardware block diagram which shows an example of the hardware configuration of the monitoring server of the building equipment monitoring system of this invention, a control server, and a monitoring terminal. It is a block block diagram which shows the function structure of the building equipment monitoring system of this invention. It is a figure which shows the event processing flowchart of the monitoring server and scenario monitoring PC of the building equipment monitoring system of this invention. It is a figure which shows the event processing flowchart of scenario monitoring PC and network camera of the building equipment monitoring system of this invention. It is a figure which shows the display control process of viewer PC of the building equipment monitoring system of this invention, and MAP display PC, and the video recording process of a video recording server. It is a figure which shows the flowchart of the cooperation control process of MAP display PC101 of the building equipment monitoring system of this invention, viewer PC102, and each network camera. It is a figure which shows the flowchart of the report process of the building equipment monitoring system of this invention. It is a figure which shows the display screen of the monitoring terminal of the building equipment monitoring system of this invention. It is a figure which shows the example of a display screen of the past repair log | history list of the building equipment monitoring system of this invention. It is a figure which shows the example of a display screen of the failure report output of the building equipment monitoring system of this invention. ) It is a figure which shows the display screen (maintenance list) of the report process of the building equipment monitoring system of this invention. It is a figure which shows the display screen (output screen of a maintenance report) of the report process of the building equipment monitoring system of this invention. It is a figure which shows the table layout of the sensor master of the building installation monitoring system of this invention. It is a figure which shows the table layout of scenario DB of the building equipment monitoring system of this invention. It is a figure which shows the table layout of log DB of the building equipment monitoring system of this invention. It is a figure which shows the table layout of the search index of the video recording information of the building equipment monitoring system of this invention. It is a figure which shows the table layout of the preset information table of the building installation monitoring system of this invention. It is a figure which shows the table layout of the building device master of the building equipment monitoring system of this invention. It is a flowchart which shows the detail of transfer of the image information to the exterior via the gateway of this invention.

  DESCRIPTION OF EMBODIMENTS Hereinafter, a preferred embodiment of a building facility monitoring system according to the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a system configuration diagram illustrating an example of an equipment monitoring system according to the present embodiment. FIG. 3 is a diagram showing a functional configuration of the equipment monitoring system of the present invention. In FIG. 1, the MAP display PC 101, the viewer PC 102, the scenario management PC 103, the recording server 104, the monitoring client 105, the monitoring server 106, and the network cameras 110 to 115 are configured to be able to communicate with each other via the Ethernet (registered trademark) 100. ing. The monitoring server 106 further connects each building device and sensors for the building device (for example, building device A 120 and sensor A 121, building device B 122 and sensor B 123, building device C 124 and sensor C 125, building device G 132 and sensor via another sensor network). G133 and the like).

  The gateway 109 is a device for transmitting event information indicating the content of the event received from the monitoring server 106 to the outside, and has gateway software installed on dedicated hardware or a personal computer or workstation. The outside here means, for example, a manufacturer of a building device in which an event has occurred or a component manufacturer of a building device in which an event has occurred.

  For example, the building device (equipment) is typically an air conditioner for buildings, for example, and the sensor detects the state of the building device, for example, a temperature sensor for the air conditioners. The building device includes, but is not limited to, a distribution board for a building, a blower, a flon fire extinguishing device, a smoke exhausting facility, an uninterruptible power supply (so-called UPS), and the like. The sensor includes, but is not limited to, an infrared sensor, a humidity sensor, an open / close sensor, a human sensor, a pressure sensor, an acceleration sensor, a vibration sensor, and an optical sensor in addition to a temperature sensor. The sensor ID that uniquely identifies each sensor is stored in the hard disk 28 of the monitoring server 106 and the hard disk 28 of the scenario management PC 103 as one item of the building device master associated with the building device ID that uniquely identifies a specific building device. Has been. As shown in FIG. 19, the building device master has a unique building device ID, building device name, model number, building device IP address, building device port number, polling interval for health check (seconds), manufacturer name, building device. Sensor ID (s) corresponding to, the camera ID of the camera that monitors the screw device, the preset ID for monitoring the building device, the user ID for the building device administrator, the password installation location (location, zone), the installation The date is memorized here for each item of the date and date of renewal. The sensor output (status) may be simply on / off, may output a specific measurement value (eg, voltage value), and if it is an intelligent type sensor, an error code (overvoltage or undervoltage) 2 to 3 digit numerical values) may be output. These sensor outputs are transmitted to the monitoring server 106 via the sensor network 150 together with the sensor ID as event information including an error or a warning. In addition, the event information including the event code including the error or warning and the building device ID may be transmitted to the monitoring server 106 via the sensor network 150 instead of the sensor output.

  The network cameras 110 to 115, which are imaging devices, are installed at different locations, and PTZ control commands and presets specified by unique preset IDs in the preset information table shown in FIG. 18 received from the scenario management PC 103 or the viewer PC 102. In accordance with the command, the pan value, the tilt value, and the zoom value are changed to capture an image, and the captured image is transmitted to the recording server 104 and the viewer PC 102. For example, a dripping type protocol such as UDP is normally used as a protocol of an image to be transmitted, but it is of course possible to use a TCP / IP protocol (including IPV6) capable of retransmission control. One network camera captures about 1 to 10 building devices. The captured image is captured at a predetermined number of frames per second, and is transmitted to the recording server with a unique camera ID that is different for each network camera.

  The recording server 104 records captured images received from the network cameras 110 to 115 in a recorded video DB 109 (image storage unit 1043 in FIG. 3) in an external storage device such as a hard disk. The MAP display PC 101 displays a map for each floor of the building to be monitored, and the building device to be monitored and the network camera installed on this floor are displayed in an icon (pictogram) format.

  The viewer PC 102 appropriately switches and displays the images received from the network cameras 110 to 115. For example, images taken by four network cameras are simultaneously displayed on one screen. Actually, there are tens to hundreds of network cameras, and several to tens of recording servers 104 are connected accordingly. In other words, there is actually one recording server 104 for every tens of network cameras.

  The monitoring server 106 has a role of receiving and storing sensor information from each sensor and transmitting the sensor information to other hardware. When a sensor (for example, sensor A121) of a certain building device is turned on (for example, the temperature detected by the temperature sensor exceeds a predetermined threshold temperature, the pressure detected by the pressure sensor exceeds a predetermined threshold pressure, etc.) The sensor-on event information of the sensor A 121 (including the event occurrence time, the sensor ID and status where the event occurred, or the building device ID and event code items) is transmitted to the monitoring server 106. When the event information from each sensor is received, the acquisition unit 1061 in FIG. 3 of the monitoring server 106 assigns a unique event ID, and further refers to the building device master using the sensor ID or the building device ID as a key, and the camera ID. Event information including the event ID and camera ID is stored in the failure history table of the log DB 107 (history information storage means 1062 in FIG. 3) in the external storage device such as a hard disk. The monitoring server 106 transmits the event ID and sensor information from the information transfer means 1063 of the monitoring server 106 to the scenario management PC 103, and further transmits the event ID and the sensor information to the recording server 104. Further, the monitoring client 105 inputs the maintenance history of each building device, and the building device ID, maintenance date, maintenance content, maintenance work time (start and end), maintenance worker name or worker code are stored in the monitoring server 106. It is recorded in the maintenance history table (maintenance ID, building device ID, maintenance date, maintenance content, maintenance work time (start and end), maintenance worker name or worker code) in the log DB 107.

  The scenario management PC 103 has a role of controlling the operation of each hardware according to the sensor information. When the scenario management PC 103 receives the sensor information from the monitoring server 106, the scenario DB 108 (building device ID) in the external storage device such as a hard disk using the building device ID included in the sensor information or the building device ID and the sensor ID as a key. , Event code, sensor ID, status, camera ID (s), preset ID (FIG. 18, multiples) for specifying a PTZ control command for storing shooting parameters for shooting with a predetermined pan / tilt / zoom, Search for event continuation time, external transmission category, external transmission destination IP address, external transmission port number, external transmission user ID, external transmission password, etc.) and camera master using the read camera ID as a key Read the IP address of the network camera referring to A PTZ control command is transmitted to the network camera, a display control command is transmitted to the viewer PC 102 to display the image of the network camera with the corresponding camera ID on the monitor, and the MAP display PC 101 has the corresponding building device The installation floor number and the blink (flashing) display control command of the icon of this building device are transmitted. If the MAP display PC 101 displays another floor based on the information on the number of installed floors, the display is switched to the map of the floor where the building device where the event has occurred is installed.

  The corresponding network camera that has received the PTZ control command captures the image of the building device in which the event has occurred by changing the pan value, the tilt value, and the zoom value according to the received PTZ control command, and the captured image is recorded on the recording server. 104. The recording server 104 uses the event information received from the monitoring server 106 to search index information (event ID, image file name) of the image captured by the network camera that captures the building device in which the event has occurred and transmitted to the monitoring server 106. , The image frame number From and the image frame number To) are generated (index generation unit 1042 in FIG. 3) and transmitted to the monitoring server 106 (index transfer unit 1041 in FIG. 3). More specifically, when the recording server 106 receives the event information, the recording server 106 stores the image of the network camera with the camera ID using a camera ID for specifying the network camera that is an imaging unit included in the event information. The file name and start frame number of the image file. And event ID index information is generated. This end frame No. Is left blank at the start of the event, and when the event with the same event ID ends (the time when the event information from the sensor or building device ends, or the shooting duration of the scenario DB elapses), these times Updated to

  The monitoring server 106 searches the log table (history information storage means 1062) of the log DB using the received event ID as a key, and adds search index information to the row of the corresponding event ID. As a result, the event information and the captured image of the building device at the event occurrence corresponding to the event information are associated by the event ID, and the captured image of the building device at the event occurrence can be displayed together with the event content when referring to the log DB. This is the end of the description of the system configuration diagram of FIG. Details of the processing will be described with reference to the flowcharts of FIGS.

  FIG. 2 is a block diagram illustrating a hardware configuration of an information processing apparatus applicable to the MAP display PC 101, the viewer PC 102, the scenario management PC 103, the recording server 104, the monitoring client 105, and the monitoring server 106 illustrated in FIG.

  In FIG. 2, a CPU 21, a RAM 22, a ROM 23, a communication adapter 24, a video adapter 25, a keyboard 26, a mouse 27, a hard disk 28, and a DVD-ROM drive 29 are connected to each other via a system bus 20. The system bus 20 means, for example, a PCI bus, an AGP bus, a memory bus, and the like. Further, in FIG. 2, a connection chip between each bus, a keyboard interface, and an input / output interface such as a so-called SCSI or ATAPI are omitted.

  The CPU 21 performs various operations such as four arithmetic operations and comparison operations and hardware control based on an operating system program and an application program. The RAM 22 stores an operation system (OS) program and application programs read from a storage medium such as a CD-ROM or CD-R mounted in the hard disk 28 or DVD-ROM drive 29, and various work files at the time of execution. The input data is stored, and the CPU 21 controls the execution of each program.

  The ROM 23 stores in advance a startup program (boot program), a so-called BIOS (Basic Input Output System) that controls input / output of each hardware in cooperation with the operating system, and the like. The communication adapter 24 communicates with the outside via a network in cooperation with a communication program of an operating system controlled by the CPU, and a so-called LAN adapter (NIC) is a typical example. The display adapter 25 generates an image signal to be output to the display device. The kiosk terminal 100 has a display (for example, a liquid crystal display) connected to the display adapter. The keyboard 26 and mouse 27 are used to input instructions to the kiosk terminal 100.

  The hard disk 28 is a part of the operating system, the application programs shown in the flowcharts of FIGS. 4 to 8, and the application programs for displaying the screens of FIGS. 9 to 13 on the display of the document management device 130 or the terminal device 120. Stores screen information. Further, each DB and master files shown in FIGS. 14 to 19 are also stored in the hard disk 28. Instead of the hard disk 28, a non-volatile memory that also serves as the RAM 22 may be used. The DVD-ROM drive 29 is used to install a storage medium such as a DVD-ROM, DVD-R / W, or a so-called Blu-ray disc and install an application program on the hard disk 28. Needless to say, a DVD-R / W drive, a so-called Blu-ray drive, an MO drive, or the like may be used instead of the DVD-ROM drive.

Hereinafter, each embodiment will be described in detail with reference to the drawings.
[Example 1]
Embodiments of the present invention will be described below with reference to the flowcharts of FIGS. 4 to 8 and 20, the screens of FIGS. 9 to 13, and the table layout diagrams of DBs and masters of FIGS. 14 to 19.

  FIG. 4 is a diagram showing an event processing flowchart of the monitoring server and scenario monitoring PC of the building facility monitoring system of the present invention. Steps S401 to S405 in FIG. 4 are processes executed under the control of the CPU 21 of the monitoring server 106, and steps S421 to S426 in FIG. 4 are processes executed under the control of the CPU 21 of the scenario management PC 103.

  First, in step S401, the monitoring server 106 receives sensor information (event information such as sensor on of a specific building device) as interrupt information from at least one of the sensor numbers 0001 to 99999, the sensor ID and status, Receives sensor information that is three pieces of reception time and / or building device information that is three pieces of information of a building device ID, an event code, and an event occurrence time for specifying failure / trouble information of a specific building device. And stored in the work area of the RAM 22. When the monitoring server 106 detects from the interrupt request that the sensor information or the building device information has been received in step S401, the monitoring server 106 stores the received sensor information and / or building device information in the work area of the RAM 22, and advances the process to step S402.

  In step S402, the monitoring server 106 stores the sensor information and / or building device information in the RAM 22 in the event log table in the log DB 107, and the process proceeds to step S403. The table layout of the event log table in the log DB 107 is shown in FIG. The event log table includes a unique event ID, event occurrence date and time (event occurrence time for building devices, sensor information reception time for sensor information), building device ID and event code where the event occurred, and / or sensor Each item of ID and status is included. That is, the building device ID and the event code are codes that specify the ID of a specific building device and the event content of the building device, while the sensor ID and status are information indicating the specific sensor and the detection content of the sensor, One building device sends the event contents of the main body to the sensor network, but does not send the detection contents of the sensor, and vice versa.

  The event ID is a unique ID assigned by the monitoring server 106 when sensor information is received, and is stored in the work area of the RAM 22 in association with the sensor information. The event code is a code indicating the content of the event output by the building device, and the status is used to specify a plurality of outputs when a sensor with a specific sensor ID can output a plurality of types of output and measurement values. Means the category.

  In step S403, the monitoring server 106 transmits the event ID and sensor information and / or building device information in the RAM 22 to the scenario management PC 103, and the process proceeds to step S404. In step S404, the monitoring server 106 waits for reception of search index information of an image at the time of video recording of the recording server 104 for the current event ID. If there is an interrupt indicating that sensor information has been received in this waiting state, the process returns to step S401 (not shown in this partial flowchart). When a search key for video recording is received from the recording server 104, search index information (event ID, image file name, image frame number From, image frame number To) of the received image is stored in the work area of the RAM 22 and processed. Advances to step S405.

  In step S405, the monitoring server 106 adds the search index information stored in the RAM 22 using the event ID as a key to the event log table of the log DB 107, and returns the process to step S401.

  Next, processing on the scenario management PC 103 side will be described. In step S421, the scenario management PC 103 receives the event ID and sensor information and / or building device information from the monitoring server 106, stores them in the work area of the RAM 22, and advances the processing to step S422.

  In step S422, the scenario management PC 103 searches the scenario DB 108 using the pair of the sensor ID of the sensor information and the status and / or the pair of the building device ID of the building device information and the event code as a key to the received sensor information. The camera ID of the corresponding network camera 110 and the PTZ control command of the camera are read out and stored in the work area of the RAM 22 together with the event ID and sensor information and / or building device information, and the process proceeds to step S423. This camera ID is an ID for specifying a camera that should take an image with a predetermined PTZ corresponding to the event.

  The scenario DB 108 includes a building device ID, event code, sensor ID, status, camera ID (s), PTZ control command (s), shooting duration, external transmission classification, external transmission destination IP address, external transmission port number. Each item of external transmission user ID and external transmission password is stored. The external transmission classification is an event content (product device ID, event code, sensor ID corresponding to the building device ID or building device ID) depending on a combination of at least two of the building device ID, event code, sensor ID, and status. Alternatively, a classification of which of the sensor part code corresponding to the sensor ID and the image of the building device) is transmitted to the outside is stored.

  For example, when external transmission classification = 0, event contents are not transmitted to the outside. When external transmission classification = 1, at least two of the building device ID excluding the image of the building device or the product number corresponding to the building device ID, the event code, the sensor ID, or the sensor component code corresponding to the sensor ID Send. In the case of external transmission category = 2, at least two of the building device ID excluding the image of the building device or the product number corresponding to the building device ID, the event code, the sensor ID, or the sensor component code corresponding to the sensor ID This means that the image of the building device is transmitted. The external transmission destination IP address is an IP address of an external transmission destination computer, and the external transmission port number is a port number necessary for passing through an intermediate firewall in order to transmit event contents to this computer. The external transmission user ID, the external transmission user ID, and the external transmission password are necessary for authentication to pass through the firewall on the way.

  In step S423, the scenario management PC 103 reads out the camera ID of the network camera 110 read from the scenario DB 108 according to the received sensor information and / or building device information and stored in the work area of the RAM 22, and the PTZ control command for the network camera 110 ( The pan value, tilt value, and zoom value of the preset information table are read using the preset ID) as a key, the IP address of the transmission destination is read with reference to the camera master using the camera ID as a key, and the shooting parameters of the camera are set to these A control command for changing to a predetermined value is transmitted to the IP address of the corresponding network camera 110 (data connection point A), and the process proceeds to step S424. When transmitting, the destination address is specified by referring to the camera master (camera ID, IP address, home position pan value, tilt value, and zoom value information) stored in the hard disk 28. It is also possible to store a password corresponding to the camera ID in the camera master and perform password authentication prior to transmitting the PTZ control command.

  In step S424, the scenario management PC 103 causes the viewer PC 102 to display a captured image of the network camera 110 corresponding to the received sensor information on the screen of the viewer PC 102, and a display start command including the camera ID and event ID of the network camera 110. Is transmitted (data connection point B). The post-transmission process proceeds to step S425.

  In step S425, the scenario management PC 103 reads the building device ID corresponding to the sensor information stored in the work area of the RAM 22 (if there is no building device ID, the scenario management PC 103 responds by referring to the scenario DB 108 using the sensor information as a key). Read the building device ID) and map the blink display command of the icon of the corresponding building device (or the corresponding sensor icon if the corresponding sensor icon is displayed on the MAP) and this building device ID or sensor ID as a pair. The data is transmitted to the display PC 101 (via data connection point C), and the process proceeds to step S426.

  In step S426, the scenario management PC 103 refers to the scenario DB using the pair of sensor ID and status received in step S421 or the pair of building device ID and event code as a key, and the corresponding building device ID and event code. , Sensor ID, status, camera ID, external transmission classification, external transmission destination IP address, external transmission port number, external transmission user ID, external transmission password are read and stored in the work area of RAM 22 and stored in the work area of RAM 22 in S421 Stored with ID, if the external transmission classification is not 0, event ID, building device ID, event code, sensor ID, status, camera ID, external transmission classification, external transmission destination IP address, external transmission port number, external transmission user ID, external transmission After sending each information Seward to the gateway 109 as a transfer instruction, the processing proceeds to step S521 via the connection point 1 of the process. This is the end of the description of FIG.

  Next, the flowchart of FIG. 5 will be described. FIG. 5 is a diagram showing an event processing flowchart of the scenario monitoring PC and network camera of the building facility monitoring system of the present invention. Steps S521 to S528 in FIG. 5 are processes executed under the control of the CPU 21 of the scenario management PC 103, and steps S531 to S436 in FIG. 5 are under the control of the CPU 21 of the network camera (here, the network camera 110). It is a process to be executed.

  In step S521, the scenario management PC 103 stores the event ID stored in the RAM 22, the event occurrence time, the sensor ID and building device ID where the event has occurred, and the event code in the hard disk 28 using the sensor ID and event code as keys. The stored sensor master (sensor ID, event code, and event code meaning items are stored) is referred to, and the meaning of the event code is sensor ON, that is, the received sensor information is a sensor-on event. If it is determined that the sensor event is ON, sensor event ON information (including event occurrence time, event ID, camera ID, and sensor ON event) is transmitted to the recording server 104, and the process proceeds to step S522.

    In step S522, the scenario management PC 103 determines whether a time extension command (event ID, camera ID, extension time) has been received from the MAP display PC 101. If an instruction to extend the shooting duration is received, the instruction to extend the shooting duration is stored in the work area of the RAM 22, and the process proceeds to step S523. If an instruction to extend the shooting duration is not received, the process proceeds to step S523. Proceed to step S524.

  In step S523, the scenario management PC 103 uses the camera ID as a key to control the camera master with a control command for extending shooting for a predetermined extension time included in the shooting duration extension command stored in the work area of the RAM 22. The information is transmitted to the target network camera specified by reference, and the process proceeds to step S524. In step S524, the scenario management PC 103 determines whether or not the shooting duration defined in the scenario (shooting duration + extension time when an extension command is received) has elapsed, and if it has elapsed, the process proceeds to step S525. If not, the process returns to step S524.

  In step S525, the scenario management PC 103 transmits a display end command (including a camera ID) of an event for which the shooting duration has elapsed to the viewer PC 102, and the process proceeds to step S526. In step S526, the scenario management PC 103 refers to the sensor information stored in the RAM 22, reads out the building device ID or sensor ID of the event whose shooting duration has elapsed, and obtains the event ID and the building device ID or sensor ID. An instruction to stop the blink display of the included icon and a return instruction to the basic MAP are transmitted to the MAP display PC 101, and the process proceeds to step S527.

  In step S527, the scenario management PC 103 refers to the sensor information stored in the RAM 22, reads the event ID of the event whose shooting duration has elapsed, and sensor OFF event information including this event ID (end of shooting duration) Event end time, event ID, sensor ID, building device ID, and sensor off event) are transmitted to the recording server 104, and the process proceeds to step S528. In step S528, the scenario management PC 103 refers to the sensor information stored in the RAM 22, reads the camera ID of the event whose shooting duration has elapsed, and uses the camera ID as a key for the camera preset control command including this camera ID. Then, referring to the camera master, the pan value, tilt value, zoom value and IP address of the home position of the camera are read out. Then, the pan value, the tilt value, and the zoom value are transmitted toward the read IP address, and the process returns to step S421 in FIG.

  Next, processing on the network camera side in FIG. 5 will be described. Here, the description will be made on the assumption that the network camera 110 takes a picture of a building device in which an event has occurred. In step S531, when the network camera 110 is activated when the power is turned on, it performs a hardware self-check, and the process proceeds to step S532.

  In step S532, the network camera 110 sets shooting conditions corresponding to the shooting parameters (pan value, tilt value, zoom value, number of shots per second (fps), shooting resolution, aperture value) at the home position stored in the RAM 22. Shooting is started, and the process proceeds to step S533. The RAM 22 of the network camera is a non-volatile memory such as a so-called flash memory (memory that retains the stored contents even when the power is turned off). In addition to home position shooting parameters, a plurality of preset shootings using preset numbers as keys in a preset table. The parameter is memorized. Specifically, the preset table stores items such as a preset number, pan value, tilt value, zoom value, number of shots per second, shooting resolution, and aperture value.

  In step S533, the network camera 110 starts the transmission of the image information and proceeds to step S534 in order to transmit the image information of the image shot with the preset shooting parameters to the recording server and the gateway 109 (in step S534 and subsequent steps). Will continue to send image information).

  In step S534, the network camera 110 is waiting to receive a preset control command (camera ID and preset number, start / end) or PTZ control command (camera ID and PTZ value) from the scenario management PC 103 or the viewer PC 102. It is determined whether a control command or a PTZ control command has been received. If a PTZ control command is received, the received control command is stored in the work area of the RAM 22, and the shooting parameter of the camera is changed to the received PTZ value for shooting. continue. On the other hand, when the preset control command is received, the received preset control command is stored in the work area of the RAM 22, and the process proceeds to step S535.

  In step S535, the network camera 110 determines whether the preset control command stored in the work area of the RAM 22 is a preset end command. If the preset command is a preset end command, the process returns to step S532. The process proceeds to step S536. In step S536, the network camera 110 determines whether the preset control command stored in the work area of the RAM 22 is a preset start command. If the preset control command is a preset start command, the process proceeds to step S537. The process returns to step S533.

  In step S537, the network camera 110 refers to the preset table using the preset number of the preset control command stored in the work area of the RAM 22 as a key, and reads out the pan value, tilt value, zoom value, and the number of shots per second. The value is changed to a value, and shooting is continued, and the process returns to step S533.

  4 and 5, when an event occurs, the event ID and the sensor information are transmitted to the scenario management PC 103 via the monitoring server 104, and the scenario management PC 103 reads out the scenario according to the sensor information and shoots the network camera. Since parameter control and display control of the viewer PC 102 and the MAP display PC 101 are performed, the building supervisor can check the image of the occurrence location on the screen of the viewer PC 102 without going to the site. By confirming the position of occurrence of abnormality on the screen of the MAP display PC 101, the situation can be easily grasped and an appropriate response can be made. Further, since the image of the occurrence location at the time of occurrence of an abnormality is stored in the recording server 104, the cause investigation later becomes easy. This is the end of the description of FIG.

  Next, FIG. 20 is a flowchart showing details of image information transfer processing triggered by receiving from the scenario management PC 103 a transfer command for transferring image information to the outside. In FIG. 20, steps S541 to S547 are processes executed in the gateway 109 of FIG. 1, and steps S551 to S552 are processes executed in a gateway (not shown) of, for example, an external equipment manufacturer or component manufacturer. . The gateway 109 stores information of a pair of a camera ID and a camera IP address corresponding to the camera ID as an address table in a hard disk or a nonvolatile memory.

  First, in step S541, the gateway 109 receives an event ID, building device ID, event code, sensor ID, status, camera ID (s), external transmission category, external transmission destination IP address, external transmission port number, external from the scenario management PC 103. A transfer command including each information of the transmission user ID and the external transmission password is received and stored in the work area of the RAM, and the process proceeds to step S542. In step S542, the gateway 109 refers to the RAM work area, receives the sensor information of the sensor ID included in the transfer command from the sensor network, stores the sensor information in the RAM work area, and advances the process to step S543.

  In step S543, the gateway 109 refers to the RAM work area, determines that the image is not transferred when the external transmission section included in the transfer command is 1, and proceeds to step S546. In the case of 2, it is determined that the image is transferred, and the process proceeds to step S544.

  In step S544, the gateway 109 refers to the address table, and the network camera 110 having an IP address corresponding to the camera ID stored in the work area of the RAM in step S541 that has not been received (discarded) in the conventional network adapter. The image information received from is stored in the work area of the RAM, and the process proceeds to step S545.

  In step S545, the gateway 109 converts the image information stored in the RAM work area into a TCP / IP protocol (using each information of external transmission destination IP address, external transmission port number, external transmission user ID, and external transmission password). The transmission destination is specified to create TCP / IP header information and other packet information). The process proceeds to step S546.

  In step S546, the gateway 109 establishes a session (connection) based on the TCP / IP protocol with an external gateway or firewall, and the process proceeds to step S547.

  In step S546, the gateway 109 determines the sensor information and / or building device information and image information (only when the external transmission category is 2) and each information for authentication (external transmission port number, external transmission user ID, external) according to the established session. A TCP / IP packet including a transmission password) and an external destination IP address is transferred to an external gateway or firewall.

  On the other hand, in step S551, an external gateway or firewall establishes a session with the gateway 109, and the process proceeds to step S552.

  In step S552, the external gateway or firewall performs authentication using the external transmission user ID, the external transmission password, and the external transmission port number. If the authentication is OK, the received packet is transferred to the external transmission destination IP address.

  As a variation of the above live image transfer process, the image at the time of the event may contribute to the elucidation of the cause of the event such as a failure or abnormality rather than the transfer of the live image as described above. The scenario management PC 103 sends an image playback request to the recording server 104 to transfer the image at the time of the occurrence of the specific event of the specific building device to the gateway 109 instead of the live image, and the above-mentioned As described above, the scenario management PC 103 can also transmit the image transfer command to the gateway 109. By executing such processing, an image when a desired event occurs can be transferred to, for example, an equipment manufacturer. This is the end of the description of FIG.

  FIG. 6 is a diagram showing display control processing of the viewer PC 102 and MAP display PC 101 and recording processing of the recording server 104 of the building facility monitoring system of the present invention. Steps S611 to S617 in FIG. 6 are processes executed under the control of the CPU 21 of the viewer PC 102, and steps S631 to S636 in FIG. 6 are processes executed under the control of the CPU 21 of the MAP display PC 101. Steps S651 to S655 in FIG. 6 are processes executed under the control of the CPU 21 of the recording server 104.

  In step S611, the viewer PC 102 reads out the viewer program from the hard disk 28 to the RAM 22 after the operating system is started, and starts the normal display scenario stored in the hard disk 28 (when sensor information is not received, For example, a network camera image is displayed at a predetermined position on a screen divided into four for a predetermined time, and the display is switched from another network camera after a predetermined time has passed. The processed image is displayed, and the process proceeds to step S612. In step S612, the viewer PC 102 determines whether there is an input for operating the PTZ of the camera from the mouse or the keyboard. If there is an input, the input value (camera ID and PTZ value of the network camera to be operated) is input to the work area of the RAM 22. And the process proceeds to step S613. If there is no input, the process proceeds to step S614.

  In step S613, the viewer PC 102 uses a PTZ control command including the camera ID and PTZ value of the network camera to be operated stored in the work area of the RAM 22 as a target to be identified with reference to the camera master using the camera ID as a key. The data is transmitted to the network camera, and the process proceeds to step S614.

  In step S614, the viewer PC 102 waits for a control command from the scenario management PC 103, and displays an image received from the specific network camera transmitted from the scenario management PC 103 in step S424 in FIG. 4 (event ID, camera A command to start display of the camera image (including ID) or to end the display on the screen of the image received from the specific network camera transmitted from the scenario management PC 103 in step S525 of FIG. When a camera video display end command is received, or when a predetermined time (for example, 0.1 second) has elapsed without receiving the command, the process proceeds to step S615.

  In step S614, the viewer PC 102 branches the process depending on the presence / absence of the received control command. If a camera video display start command is received, the process advances to step S616. If a camera video display end command is received, the process advances to step S617. If neither the display start command nor the display end command is received, the warpage is returned to step S612.

  In step S616, the viewer PC 102 uses the camera ID included in the camera image display start command to display the image received from the network camera corresponding to the camera ID on the screen, and returns the process to step 612. In step S617, the viewer PC 102 uses the camera ID included in the camera video display end command to end the display on the screen of the image received from the network camera corresponding to the camera ID, and the network camera based on the normal scenario. The image received from is displayed, and the process returns to step 612.

  Next, display control of the MAP display PC 101 when the monitoring server 106 receives sensor information will be described. In step S631, the MAP display PC 101 displays the basic MAP stored in the hard disk 28 after startup. The basic MAP is a floor map of a predetermined floor that is displayed at a normal time when event information is not received. In addition, a floor map for every floor of the building is stored in the hard disk 28. The MAP display PC 101 stores a map master in the hard disk 28. The map master stores the corresponding map ID, camera ID, and PTZ control information using the building device ID or sensor ID as a key (that is, when the building device ID and sensor ID are specified, the icon of the building device ID and its A map including a sensor ID icon, a building device corresponding to the building device ID, a network camera that captures the sensor corresponding to the sensor ID, and a PTZ that the network camera should control to capture the building device or sensor Value is specified). Map data of the map body having this map ID as a name (drawing data in vector format such as each room, corridor, elevator, etc., each building device ID, its position coordinate data, its icon data, and each sensor ID, its position coordinates Data and its icon data) are also stored in the hard disk 28.

  Each floor map displays icons indicating each building device to be managed (monitored), icons indicating each network camera, and layout diagrams such as rooms, corridors, and elevators, and inputs from control commands or a keyboard or mouse Wait for. When there is a display control input from the keyboard or mouse (for example, an input for switching the floor to be displayed or an enlarged display request), a MAP corresponding to the control input is displayed. On the other hand, when a blink display control command of the icon of the corresponding building device (or the corresponding sensor icon if the corresponding sensor icon is displayed on the MAP) is received from the scenario management PC 103, the received display control command is transferred to the work of the RAM 22. The information is stored in the area, and the process proceeds to step S632.

  In step S632, the MAP display PC 101 reads the map data of the corresponding map ID from the hard disk by referring to the map master using the building device ID or sensor ID included in the display control command stored in the work area of the RAM 22 as a key, and displays it. Then, using the building device ID or sensor ID included in the display control command as a key, the icon of the corresponding building device or sensor in the map data is displayed blinking (blink display), and the process proceeds to step 633.

  In step S633, the MAP display PC 101 determines whether or not a time extension command (for example, to extend the display by 2 minutes) is input from an input unit such as a keyboard or a mouse. If a time extension command has been input, the process proceeds to step S634. If a time extension command has not been input, the process proceeds to step S635.

  In step S634, the MAP display PC 101 transmits a time extension command (event ID, camera ID, extension time) to the scenario management PC 103, and the process proceeds to step S635. In step S635, the MAP display PC 101 determines whether or not an instruction to stop blinking the icon and an instruction to return to the basic MAP are received from the scenario management PC 103. If these instructions are received, the blink display of the received icon is displayed. The event ID and building device ID or sensor ID and stop command included in the stop command are stored in the work area of the RAM 22, and the process proceeds to step S636. If these commands are not received, the process proceeds to step S633. return.

  In step S636, the MAP display PC 101 uses the map data and the building device ID or sensor ID corresponding to the stop command stored in the work area of the RAM 22 to stop the blinking of the icon corresponding to the stop command and perform the process. Return to S631. Next, processing of the recording server 104 will be described.

  First, in step S651, the recording server 104 starts normal recording (images from each target network camera) after starting the operating system (only for the first time after power-on). This normal recording continues even when other steps such as reception of a sensor-on event are being executed. The process proceeds to step S652.

  In step S652, the recording server 104 receives sensor ON event information (including event occurrence time, event ID, camera ID, and sensor on event) or sensor OFF event information (event ID, event end time, and the like) from the scenario management PC 103. If the event information is received, it is stored in the work area of the RAM 22 and the process proceeds to step S653.

  In step S653, the recording server 104 advances the process to step S654 if the event information stored in the work area of the RAM 22 is sensor ON event information, and advances the process to step S655 if the event information is sensor OFF event information.

  In step S654, the recording server 104 records the received event ON information on the hard disk 28, and the process proceeds to step S656. In step S655, the recording server 104 records the event OOFF information received by the recording server 104 on the hard disk 28, and the process proceeds to step S656.

  In step S656, the recording server 104 uses the event occurrence time and camera ID included in the received event ON information, and the captured image file stored in the hard disk 28 using the event end time included in the received event OFF information. , And the name and image frame number of the image file that captures an image between the event occurrence time and the event end time of the network camera (network camera 110 in this embodiment) corresponding to the camera ID (event The image frame number From at the occurrence time and the image frame number To at the event end time are acquired, and the monitoring server 106 is used as image search index information (event ID, image file name, image frame number From, image frame number To). To process Back to the flop S651. This is the end of the description of FIG.

  Next, FIG. 7 is a diagram showing a flowchart of the cooperative display control process (when a specific icon is selected) between the MAP display PC 101, the viewer PC 102, and each network camera when no event occurs in the building facility monitoring system of the present invention. It is. Steps 711 to S713 in FIG. 7 are processes executed under the control of the CPU 21 of the MAP display PC 101, and steps S721 to S725 in FIG. 7 are processes executed under the control of the CPU 21 of the viewer PC 102. Steps S731 to S736 in FIG. 7 are processes executed under the control of the CPU 21 of the network camera (the network camera 110 in this embodiment).

  First, in step 711, the MAP display PC 101 displays the basic MAP stored in the hard disk 28 after startup, and display control input from the keyboard or mouse (for example, an input to switch the floor to be displayed or an enlarged display request as in step S631). ), The MAP corresponding to the control input is displayed. The processing proceeds to step S712 at a predetermined timing.

  In step 712, when there is an input for selecting a specific icon (camera icon or building device icon or sensor icon) in the MAP, the MAP display PC 101 receives the camera ID or building of the network camera corresponding to the selected icon. The device ID or sensor ID of the device is stored in the work area of the RAM 22, and the process proceeds to step S713.

  In step 713, when the icon of the building device or the sensor icon is selected in step S712, the MAP display PC 101 refers to the map master using the device ID or sensor ID stored in the work area of the RAM 22 as a key, A camera ID and PTZ control information of a corresponding network camera (network camera 110 in this embodiment) is acquired, and a viewer display command (a camera ID and a display command for displaying an image of the camera ID, step) If a building device icon or a sensor icon is selected in S712, PTZ control information and a device ID or sensor ID are further transmitted), and the process returns to step S711.

  In step S721, the viewer PC 102 reads the viewer program from the hard disk 28 to the RAM 22 after the operating system is started, and starts the normal display scenario stored in the hard disk 28 (when sensor information is not received, The screen display is switched by a display control procedure in which, for example, a network camera image is displayed at a predetermined position on a screen divided into four for a predetermined time (for example, 20 seconds) and switched to another network camera image after the predetermined time has elapsed. The image received from each network camera is displayed, and the process proceeds to step S722.

  In step S722, the viewer PC 102 is waiting to receive a viewer display command, and during this time, the screen display is switched according to the normal display scenario. Viewer display command (a display command for displaying a camera ID and an image of the camera ID, and if a building device icon or a sensor icon is selected in step S712, further includes PTZ control information and a device ID or sensor ID) Is received, the received viewer display command is stored in the work area of the RAM 22, and the process proceeds to step S723.

  In step S723, the viewer PC 102 displays the image of the corresponding network camera on the screen using the camera ID of the viewer display command in the work area of the RAM 22, and the process proceeds to step S724.

  In step S724, the viewer PC 102 has a camera preset selection input (an input for pressing the PTZ button 921 of the camera 2 image at the upper right of the screen on the display screen of the viewer PC 102 shown in FIG. 9) from a colony means such as a mouse or a keyboard. If there is a selection input, the process proceeds to step S725. If there is no selection input, the process proceeds to step S726.

  In step S725, the viewer PC 102 refers to the camera master and the preset information table using the camera ID corresponding to the preset selection input as a key, and stores PTZ control information (destination IP address, pan value, tilt value, zoom value). The data is read and transmitted to the network camera 110, and the process returns to step S722. If a building device icon or a sensor icon is selected in step S712, the PTZ control information read from the map master is transmitted to the network camera 110, and the process proceeds to step S726.

  In step S726, the viewer PC 102 inputs a request for a failure image or a maintenance image (on the display screen of the viewer PC 102 shown in FIG. 9, for example, the camera 2 image failure image button 922 or the maintenance image button 923 on the upper right of the screen is pressed. If there is a request input, the process proceeds to step S727. If there is no request input, the process returns to step S722.

  In step S727, the viewer PC 102 requests a camera ID for displaying the current image stored in the work area of the RAM 22 in step S722 and a failure image or a maintenance image corresponding to the pressed button. An image request including the above is transmitted to the recording server 104, and the process proceeds to step S728. The recording server 104 executes processing in steps S842 to S845 in FIG. 8 to be described later, and transmits the failure-time image or maintenance-time image requested to be returned to the viewer PC 102.

  In step S728, the viewer PC 102 displays the current live image displayed in step S723 and the failure image or the maintenance image on the top and bottom of the screen of FIG. 9 (for example, the live image and the camera 4 image on the screen 920 of the camera 2 image). 940 at the time of failure or maintenance image) or left and right (for example, live image on camera 920 screen 920, camera 1 image 910 failure image or maintenance image) When playback ends or when it is detected that the normal display button 906 (instruction button for returning to the screen switching control according to the normal display scenario in step S721) is pressed on the screen of FIG. 9, the normal display scenario The display control is switched to and the process returns to step S722.

  Next, the network camera 110 performs the processing from step S731 to step S736 similar to the processing from step S731 to step S736 in FIG.

  FIG. 8 is a view showing a flowchart of report processing of the building facility monitoring system of the present invention. Steps S821 to S831 in FIG. 8 are processes executed under the control of the CPU 21 of the viewer PC. Steps S841 to S845 in FIG. 8 are processes executed under the control of the CPU 21 of the recording server 104.

  Next, in step S821, the viewer PC 102 activates the viewer (only for the first time), and when detecting the pressing of the “process selection” button on the viewer screen, displays a process selection menu (not shown).

  When an input to select "Reporting process" is detected in the process selection menu, a screen (not shown) for entering the report type and creation conditions (designation of report creation target device, target period, etc.) is displayed, and the report type (individual Repair history display for building devices (FIG. 10), failure report for individual building devices (FIG. 11), maintenance list (FIG. 12), maintenance report for individual building devices (FIG. 13) 4)) and creation conditions (designation of building device ID in the case of other than repair history display, and date and time of the target period From to To) are displayed, and these reports are displayed. Type and creation conditions are specified, and when the pressing of the “Create” button is detected, the report type and creation conditions are stored in the work area of the RAM 22. , The process proceeds to step S822.

  In step S822, the viewer PC 102 uses the report type and creation conditions stored in the work area of the RAM 22 to extract data necessary for the report from each table of the log DB 107 of the monitoring server 106. Statement (the date of event occurrence or the last maintenance date, according to the name of the failure history table or maintenance history table or event log table corresponding to the report type, and the date and time From to To of the target period corresponding to the report type, or Failure date) is created and transmitted to the monitoring server 106, and the process proceeds to step S823.

In step S823, the viewer PC 102 receives report creation information (detailed information of event log table, failure history table, or maintenance history table for each building device (recording data search index information) transmitted from the loopback monitoring server 106. Including)) from the monitoring server 106 and stored in the hard disk 28 as a work file, and the process advances to step S824.

  Here, the failure history table and the maintenance history table recorded in the log DB 107 of the monitoring server 106 will be described. The maintenance history table of the log DB 107 records building device ID (key item), device name, manufacturer, model, purchase date, last maintenance date, scheduled next maintenance date, last repair date, and remarks. The maintenance history table addition / update data is input from the monitoring client 105 and registered in the maintenance history table of the log DB 107 of the monitoring server 106. The repair history table of the log DB 107 includes a building device ID (key item), a facility name (building name, etc.), an equipment name (type of equipment such as air conditioning equipment), an equipment name, a manufacturer, a model, and a purchase date. Record the basic items (only one item per building device) of the last maintenance date and the next scheduled maintenance date, and the breakdown date, failure details, repair details, and remarks items (exists for the number of failures). Yes. The repair history table addition / update data is input from the monitoring client 105 and registered in the repair history table of the log DB 107 of the monitoring server 106.

  In step S824, the viewer PC 102 reads screen information corresponding to the type of report stored in the work area of the RAM 22 from the hard disk, and uses the report creation information included in the work file stored in the hard disk 28. Screen information for displaying the screens of FIGS. 10 to 13 is generated. At that time, the search index information of the recorded data is embedded as a playback button in the HTML link format or the dedicated application in each error code or failure log details of the failure log display column 1110 on the screen of FIG. In the screen of FIG. 11, the search index information of the recorded data is embedded in each detail of the maintenance history in the past maintenance history column 1113 as a link button of HTML or a playback button in a dedicated application. Alternatively, on the screen of FIG. 13, the search index information of the recorded data is embedded in each detail of the previous maintenance status display field 1307 as a link button of HTML or a playback button in a dedicated application. Alternatively, the search index information of the recorded data is embedded in each specification of the past maintenance history column 1309 as a link button of HTML or a playback button in a dedicated application. The screen information is generated and stored in the work area of the RAM 22, and the process proceeds to step S825.

  In step S825, a report screen is displayed using the created screen information. When the report type is a repair history display for an individual building device, the past repair history list screen of FIG. 10 is displayed, and for a failure report for an individual building device, the failure report screen of FIG. In the case of a maintenance list, the maintenance list screen of FIG. 12 is displayed, and in the case of a maintenance report for an individual building device, the maintenance report screen of FIG. 13 is displayed. In step S826, the viewer PC 102 selects the error code in the HTML format on the screen in FIG. 11, the specific error code in the failure log display column 1110 or the link location of the failure log (clicked with the mouse), or past maintenance. When a specific maintenance history link location in the history column 1113 is selected (clicked with the mouse), or in the screen of FIG. 13, the previous maintenance status display column 1307 link location or the past maintenance history column 1309 link If a location is selected (clicked with the mouse), the selected location is stored in the work area of the RAM 22 and the process proceeds to step S827. In the screen of FIG. 10, when the check mark column 1009 of the specific repair history detail line is checked and the detail & image display button 1016 is pressed, the selected history information is stored in the work area of the RAM 22. The process proceeds to step S827.

  In step S827, the viewer PC 102 transmits the search index information stored in the work area of the RAM 22 to the monitoring server 104 in accordance with the selection in step S826, and the process proceeds to step S828. In step S828, the viewer PC 102 receives the recording data corresponding to the search index information from the recording server 104, and the process proceeds to step S829.

  In step S829, if the viewer PC 102 detects that the screen of FIG. 11 is displayed and the live simultaneous display button 1117 is pressed, the process proceeds to step S830. Otherwise, the process proceeds to step S830. Proceed to S831.

In step S830, the viewer PC 102 reproduces the failure image or the maintenance image (maintenance operation image) received from the recording server 104 on the recorded image reproduction window 1112 on the screen of FIG. When the live image received from is reproduced in the recorded video reproduction window 1115 and pressing of the menu button 1116 is detected, the process returns to step S821. In this manner, the image at the time of failure or the image at the time of maintenance and the current live image are simultaneously displayed in comparison.
In step S831, the viewer PC 102 reproduces the failure image or the maintenance image received from the recording server 104 in the recording / reproduction window 1308 in the maintenance execution state of FIG. 13 and detects that the menu button 1312 is pressed. The process returns to step S821.

  Next, each process of step S841 to step S845 executed under the control of the CPU 21 of the recording server 104 in FIG. 8 will be described.

  In step S841, the recording server 104 advances the processing to step S842 at a predetermined timing (for example, every 0.1 second) while continuing the recording data reception processing and recording processing in the normal recording mode.

  In step S842, the recording server 104 determines whether a recording data request has been received from the viewer PC 102 based on the contents of the session memory of the viewer PC 102 in the RAM 22, and the process proceeds to step S843. In step S842, the recording server 104 branches the process according to the determination result of step S842. If it is determined that the recording data request has been received from the viewer PC 102, the process proceeds to step S844. If it is determined that the recording data request has not been received from the viewer PC 102, the process returns to step S841.

  In step S844, the recording server 104 activates a recording data transmission process to transmit the recording data corresponding to the recording data request target network camera included in the recording data request received from the viewer PC 102 and the shooting time. The process proceeds to step S845.

  In step S844, the recording server 104 reads out the recording data corresponding to the target network camera and shooting time included in the recording data request from the recording data recorded in the hard disk in the recording data transmission process to the RAM 22 and transmits it to the viewer PC 102. The process returns to step S841. The recording data transmission process ends when the recording data corresponding to the target network camera and shooting time is finished. This is the end of the description of steps S841 to S845.

  It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device. The outline of the modification is shown below.

[Example 2]
A system is configured with the monitoring server 106 and the scenario management PC 103 as one casing (integrated). In this case, steps S401 to S405 in FIG. 4, steps S421 to S425, and steps S521 to S528 in FIG. 5 are executed as separate processes in the same hardware. The sensor information in step S403 is transmitted to step S421 by interprocess communication. Since other points are the same as those of the first embodiment, description thereof is omitted.

[Example 3]
A system is configured with the MAP display PC 101 and the viewer PC 102 as one housing (integrated). In this case, steps S711 to S713 and steps S721 to S723 in FIG. 7 are executed as separate processes in the same hardware. The viewer display command in step S713 is transmitted to step S722 by inter-process communication. Since other points are the same as those of the first embodiment, description thereof is omitted.

Also in the following fourth to twelfth embodiments, processing executed by different hardware in the first embodiment is similarly executed as a separate process in the same hardware. Also, in the following fourth to twelfth embodiments, information and instructions are exchanged between different hardware in the first embodiment, for example, by inter-process communication between different processes. Since other points are the same as those of the first embodiment, description thereof is omitted.

[Example 4]
A system is configured with the viewer PC 102 and the recording server 104 as one casing (integrated).
[Example 5]
A system is configured with the MAP display PC 101 and the scenario management PC 103 as one casing (integrated).

[Example 6]
A system is configured with the scenario management PC 103 and the recording server 104 as one casing (integrated).
[Example 7]
The scenario management PC 103, the recording server 104, and the monitoring server 106 are configured as one casing (integrated) to constitute a system.

[Example 8]
The system is configured with the scenario management PC 103 and the viewer PC 102 as one casing (integrated).
[Example 9]
The scenario management PC 103, the monitoring server 106, and the viewer PC 102 are configured as one housing (integrated).

[Example 10]
The scenario management PC 103, the viewer PC 102, and the MAP display PC 101 are configured as one housing (integrated).
[Example 11]
The scenario management PC 103, the viewer PC 102, the MAP display PC 101, and the monitoring server 106 are configured as a single housing (integrated).
[Example 12]
The scenario management PC 103, the viewer PC 102, the MAP display PC 101, the recording server 104, and the monitoring server 106 are configured as a single housing (integrated).

  The program in the present invention is a program that can execute the processing method of FIGS. 5 to 8. The storage medium of the present invention is a program that can execute the processing method of FIGS. 5 to 8 and FIG. Screen information that can display the screen of FIG. 13 is stored. The program according to the present invention may be a program for each processing method of each apparatus shown in FIGS.

As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by executing the reading.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk or the like can be used.

Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

  Further, after the program read from the recording medium is written in the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network by a communication program, the system or apparatus can enjoy the effects of the present invention.

  In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

100 Ethernet (registered trademark)
101 MAP display PC
102 Viewer PC
103 Scenario management PC
104 Recording server 105 Monitoring client 106 Monitoring server 107 Log DB
108 Scenario DB
110 Network Camera 111 Network Camera 112 Network Camera 113 Network Camera

Claims (6)

A monitoring system configured to be able to communicate with a monitoring server that stores event information received from an equipment device to be monitored, a recording server that stores image information received from a photographing device, and a management terminal that performs photographing control on the photographing device Because
The recording server
Image storage means for storing an image captured by the imaging device;
Index generating means for generating index information for associating the image corresponding to the event information received from the monitoring server;
Index transfer means for transferring the generated index information to the monitoring server;
The monitoring server is
An acquisition means for acquiring event information including an error or a warning transmitted from a sensor associated with the facility device or the facility device and detecting a state of the facility device;
Information transfer means for transferring the acquired event information to the recording server and the management terminal;
History information storage means for storing history information including the acquired event information and index information received from the recording server corresponding to the event information;
With
The management terminal
Control information storage means for storing the correspondence between each equipment device and a photographing device capable of photographing the equipment device and photographing parameters;
With reference to the control information storage means using the transferred event information, an image at the time of an event, which is an image of an equipment device that has transmitted the event information, is taken by an imaging device associated with the equipment device. Therefore, photographing control means for transmitting predetermined photographing parameters to the photographing device,
Using the history information, display control information for displaying the event image of the equipment device stored in the image storage means and the current image that is currently captured by the equipment device is generated. And a display control means for monitoring. The management terminal
According to the event information received from the equipment or the sensor, it is determined whether to transfer the event-time image and the event information, or the event information, and the event-time image and the event information. The monitoring system according to claim 1, further comprising a determination unit that specifies to which event information is to be transferred. The control information storage means stores a unique ID that identifies the imaging device,
The event information of the history information storage means stores the occurrence time of the error or the occurrence time of the warning,
The monitoring server is
The monitoring system according to claim 1, further comprising a search unit that searches the history information using at least one of the event information and the ID. The display control means performs display control for displaying a desired image of the equipment in comparison with a maintenance-time image that is an image during maintenance work and a current image that is the current image of the equipment. The monitoring system according to any one of claims 1 to 3, wherein: Control information storage means for storing the correspondence between equipment to be monitored and photographing equipment capable of photographing the equipment, image information received from the photographing equipment and the equipment associated with the equipment or the equipment A monitoring system control method comprising index information that associates event information including an error or warning transmitted from a sensor that detects the state of a device, and history information storage means that stores history information including the event information. And
An acquisition step of acquiring the event information from the equipment or the sensor,
Referring to the control information storage unit according to the event information acquired in the acquisition step, an event-time image that is an image of the facility device that has transmitted the event information is captured by a photographing device associated with the facility device. A shooting control step of transmitting predetermined shooting parameters to the shooting device to
A monitoring system control method comprising: a display control step of comparing and displaying the event image of the equipment and the current image of the equipment using the history information. A monitoring system for monitoring facility equipment, comprising: control information storage means for storing correspondence between each of the equipment equipment and photographing equipment capable of photographing the equipment equipment; and image storage means for storing image information received from the photographing equipment. And history information including the event information and index information that associates the event information including an error or warning transmitted from the facility device or a sensor that detects the state of the facility device with the facility device. A control program for a monitoring system comprising information storage means,
The monitoring system;
An acquisition means for acquiring event information including an error or a warning transmitted from a sensor associated with the facility device or the facility device and detecting a state of the facility device;
The imaging device refers to the image storage unit according to the acquired event information, and causes the imaging device associated with the facility device to capture an event-time image that is an image of the facility device that has transmitted the event information. Photographing control means for transmitting predetermined photographing parameters to
A monitoring system control program for functioning as display control means for comparing and displaying the event image of the equipment and the current image of the equipment using the history information.