JP2010224893A - Monitoring device and monitoring method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a monitoring device and a monitoring method for surely and efficiently monitoring a facility state. <P>SOLUTION: The monitoring device of a facility with a plurality of facility equipment 2 is provided with: a measurement data storage part for storing the history of measurement data from the facility equipment 2; a history DB 34 for storing the alarm information of an alarm generated according to the measurement data of the facility equipment 2 with a time stamp; an alarm management DB 33 for storing the picture information of an association picture corresponding to the alarm; and an alarm management engine 35 for successively updating the past measurement data displayed on a relevant picture corresponding to the designated alarm in a sequence following the time series. The alarm management engine displays the measurement data including an alarm generation time in a prescribed period at a specific update interval, and fast-forwards the display of the measurement data until the start time of the prescribed period. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a facility monitoring device and a monitoring method, and particularly relates to a monitoring device and a monitoring method for performing monitoring based on data from facility equipment.

  In recent years, the state of equipment is displayed on a display device as a monitoring application for equipment such as plants and buildings. For example, data measured by equipment such as a thermometer, an air flow meter, and a hygrometer is displayed on the display screen. Specifically, an icon indicating equipment and measurement data measured by the equipment are displayed on a plan view on which the layout of the building is displayed.

  Patent Document 1 discloses a process monitoring window system having a multi-window function. In this window system, the times of multiple panes are synchronized. In addition, in order to monitor various processes, past process data history and event history are displayed.

JP 2006-338343 A

  By replaying the process data acquired in the past, the contents of events that occurred in the past can be analyzed in detail. For example, by displaying process data for a certain period of time along a time series, it is possible to grasp what behavior the equipment has shown.

  When replay is performed, the past process data is updated at a predetermined update interval and displayed. In this case, there is a risk of overlooking the behavior during an important period in which an alarm is generated from the equipment. That is, when no alarm is generated, the process data is updated in the same manner as when the alarm is generated. Therefore, it may take a long time from the start of replay until the critical period in which the alarm is generated, and the behavior of the critical period may be overlooked. As described above, the conventional monitoring apparatus has a problem in that the important period in which an alarm or the like is generated is overlooked, and the facility cannot be reliably monitored. In this case, it becomes impossible to appropriately analyze the cause of the alarm.

  The present invention has been made to solve such problems, and an object of the present invention is to provide a monitoring device and a monitoring method capable of reliably monitoring.

  A monitoring device according to a first aspect of the present invention is a facility monitoring device provided with a plurality of facility devices, and alarm information of an alarm generated according to measurement data of the facility devices is attached with a time stamp. An alarm information storage unit for storing, a screen information storage unit for storing screen information of a related screen corresponding to the alarm, and past measurement data displayed on the related screen corresponding to a specified alarm in time series A replay execution unit that updates the data in a predetermined order, displaying the measurement data of a predetermined period including the time of the alarm occurrence at a predetermined update interval, and displaying the measurement data until a start time of the predetermined period A replay execution unit for fast-forwarding. Thereby, since the screen related to the alarm is displayed, it is possible to reliably monitor.

  A monitoring apparatus according to a second aspect of the present invention is the monitoring apparatus described above, wherein a list of alarms in time series is displayed, and a replay including an alarm occurrence time specified from the list of alarm information is displayed. A time is set and replay is executed. As a result, it is possible to easily replay and replay an alarm that has been noticed, and to efficiently analyze the cause of the alarm.

  A monitoring apparatus according to a third aspect of the present invention is the monitoring apparatus described above, wherein the alarm is filtered and displayed on the list. As a result, it is possible to replay and replay an alarm that has been easily noticed.

  A monitoring device according to a fourth aspect of the present invention is the above monitoring device, wherein the monitoring device has a server-client configuration, acquires user information of a user who operates the client, and With reference to the user information, the alarms generated during the stop period in which the client is stopped are replayed in order. Thereby, suitable monitoring can be performed according to the user.

  A monitoring device according to a fifth aspect of the present invention is the monitoring device described above, wherein the alarm is generated in response to alarms from a plurality of facility devices. Thereby, it can monitor more reliably.

  A monitoring method according to a sixth aspect of the present invention is the monitoring method described above, and is a monitoring method for a facility provided with a plurality of facility devices, and stores a history of measurement data from the facility device. A step of storing alarm information of an alarm generated according to the measurement data of the equipment with a time stamp, a step of displaying a related screen corresponding to the designated alarm, and the related screen displayed on the related screen A replay step of updating the past measurement data in a time-sequential order, displaying the measurement data for a predetermined period including the time of occurrence of the alarm at a predetermined update interval; and A replay step of fast-forwarding the display of the measurement data until the start time.

  A monitoring method according to a seventh aspect of the present invention is the monitoring method described above, wherein a list of the alarms along a time series is displayed, and a replay including an alarm occurrence time designated from the list of alarm information is included. A time is set and replay is executed. As a result, it is possible to easily replay and replay an alarm that has been noticed, and to efficiently analyze the cause of the alarm.

  A monitoring method according to an eighth aspect of the present invention is the monitoring method described above, wherein the alarm is filtered and displayed on the list of alarms. As a result, it is possible to replay and replay an alarm that has been easily noticed.

  A monitoring method according to a ninth aspect of the present invention is the monitoring method described above, wherein the server approves the access of the client, acquires the user information of the user who operates the client, and the user information , Further comprising the step of sequentially replaying and replaying alarms generated during the stop period in which the client is stopped. Thereby, suitable monitoring can be performed according to the user.

  A monitoring method according to a tenth aspect of the present invention is the monitoring method described above, wherein the alarm is generated in response to alarms from a plurality of facility devices. Thereby, it can monitor more reliably.

  ADVANTAGE OF THE INVENTION According to this invention, the monitoring apparatus and monitoring method which can monitor an equipment state reliably and efficiently can be provided.

It is a figure which shows the whole structure of the monitoring system concerning this Embodiment. It is a figure which shows the monitoring screen in the monitoring system concerning this Embodiment. It is a figure which shows the replay execution screen which performs replay in a monitoring screen. It is a figure which shows the structure of the server used for the monitoring system concerning this Embodiment. It is a table | surface which shows an example of the alarm information stored in log | history DB. It is a table | surface which shows an example of the alarm information stored in management server DB. It is a table | surface which shows an example of the log | history of the measurement data stored in alarm management DB.

  Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings. FIG. 1 is a diagram schematically illustrating the overall configuration of the equipment monitoring system.

  The equipment monitoring system monitors equipment in equipment such as a plant and a building, for example. In the facility monitoring system, for example, a plurality of facility devices 2 are provided. The facility device 2 is a field device that has been arranged at a predetermined position indoors or outdoors. Examples of the equipment 2 include an air conditioner, a heater, a humidifier, an air flow meter, a thermometer, a calorimeter, a power meter, a flow meter, a compressor, and a valve. The equipment 2 monitors the temperature, air volume, humidity, flow rate, etc. in the building equipment. That is, the facility equipment 2 measures temperature, air volume, humidity, heat consumption, power consumption, and the like at each point. The equipment 2 acquires these measurement data at predetermined time intervals. For example, measurement data can be acquired every minute or every second. Thus, the time change of measurement data is acquired in each equipment 2.

  Then, the measurement data measured by the facility device 2 is transferred to the server 1. Then, the server 1 stores the transferred measurement data. Here, the equipment data 2 and the server 1 may be connected via a network, and the measurement data from the equipment equipment 2 may be transmitted sequentially. Alternatively, the measurement data may be accumulated in the equipment device 2 for a certain period, and the accumulated measurement data may be collected and transmitted. In this case, a data file including measurement data for a certain period is transferred to the server 1. Further, the measurement data may be stored in a storage medium such as an external memory or a storage disk, and the server 1 may read the measurement data on the storage medium. In this case, the facility device 2 and the server 1 may not be connected via a network. Of course, the measurement data may be transferred to the server 1 by combining them. The server 1 stores measurement data with a time stamp. The server 1 is an information processing apparatus such as a personal computer. This server 1 manages and monitors equipment.

  Further, the alarm information from the facility device 2 is transferred to the server 1. The server 1 stores alarm information. For example, the time when the alarm occurred, the location where the alarm occurred, the ID of the equipment 2 where the alarm occurred, the type of alarm, etc. are stored in association with each other. Thus, alarm information and measurement data are stored as a history with a time stamp. That is, alarm information and measurement data are stored as a history along the time series.

  Furthermore, a client 3 is connected to the server 1 via a network or the like. That is, the monitoring device has a server 1-client 3 configuration. The client 3 is an information processing apparatus such as a PC, and includes an input unit 4, a display unit 5, and a processing unit 6. For example, the user inputs a user name, a password, and the like through the input unit 4. As a result, the client 3 is accessed with the server 1 and the data in the server 1 can be referred to. Then, the processing unit 6 performs processing based on the data. Then, the processing result in the processing unit 6 is displayed on the display unit 2. Although FIG. 1 shows an example in which one client is connected, the number of clients 3 to be connected is not limited to this. A plurality of clients 3 may be simultaneously connected to the server 1. Furthermore, the server 1 and the client 3 are not limited to a physically single device. In addition, a user level (user authority level) is set for the user in accordance with his / her job title and position.

  The processing unit 6 includes an MPU or the like and storage means for storing data and programs necessary for calculation, and performs various calculation processes. The input unit 4 has input means such as a mouse and a keyboard. Various data are input by the user operating the input unit 4. The display unit 5 includes a display device such as a CRT or a liquid crystal display. The display unit 5 displays processing results and the like on a window of the display screen. The display unit 5 displays a monitoring screen for performing facility management.

  Next, the monitoring screen displayed on the display unit 5 will be described with reference to FIG. FIG. 2 is a diagram schematically showing a monitoring screen of the monitoring screen. The monitoring screen 10 is, for example, a window displayed on a display. The monitoring screen 10 includes a layout screen 11, a plant hierarchy screen 12, a trend screen 13, and a replay execution screen 14. An alarm list screen 15 is included. Of course, these may be displayed as different windows.

  The layout screen 11 displays the layout of the entire facility or a part of the facility. That is, the icon 18 corresponding to the equipment 2 is displayed in the layout screen 11. The icons 18 are displayed in an arrangement corresponding to the layout of the equipment. On the layout screen 11, for example, icons 18 such as pipes, tanks, valves, and compressors are arranged according to the layout of the equipment. Therefore, a plan view showing a part of the facility is displayed on the layout screen 11. Furthermore, the data acquired by the equipment 2 is displayed in association with the equipment icon 18. That is, measurement data (process data) measured by the equipment 2 is displayed near the icon 18 of the equipment 2. Thereby, the state of an installation can be grasped quickly.

  On the plant hierarchy screen 12, blocks that divide the entire facility are displayed in a tree shape. Thereby, it can be grasped to which part of the whole equipment the layout currently displayed on the layout screen 11 corresponds. From this tree, it is possible to specify a block to be monitored. The layout screen 11 is changed by designating the block monitored by the user.

  The trend screen 13 displays a trend of measurement data measured by the equipment device 2. For example, when attention is paid to a certain equipment 2, measurement data such as temperature data and flow rate data acquired by the equipment 2 is displayed. Here, the graph of the time change of measurement data is displayed. The trend data that the user wants to monitor may be specified.

  The replay execution screen 14 is a screen for executing replay display. The replay execution screen 14 will be described later. The alarm list screen 15 displays a list of alarms. The alarm is generated according to measurement data transmitted from one or a plurality of facility devices 2. For example, when data measured by one equipment device 2 exceeds a threshold value, an alarm is output from the equipment device 2. The server 1 receives the alarm as an alarm. Then, the server 1 stores the alarm with a time stamp for the occurrence time. Thus, an alarm database is constructed. The alarm list screen 15 displays alarms and their occurrence times. Of course, a filter may be provided for the alarms displayed on the alarm list screen 15. For example, you may filter by time, ID of the installation equipment 2, installation information, etc. Furthermore, you may filter according to user information, such as the area | region in the whole installation, a user level, and user ID. Convenience can be improved by using such an alarm list screen 15 as a general-purpose journal part.

  The alarm information stored in the server 1 includes not only the alarm occurrence time but also alarm information. For example, the ID or name of the equipment 2 that has generated the alarm, or the alarm type is added as the alarm information.

  Further, the alarm does not correspond to only one alarm or one equipment device 2 but may correspond to two or more alarms or equipment 2. For example, a state in which two or more facility devices 2 are simultaneously generating alarms may be set as one alarm. Such alarm conditional expressions are set in advance by the user. Thus, it is possible to monitor more appropriately by setting the alarm in a complex manner. The alarm list screen 15 displays a list of alarms. Here, a list in which alarms are arranged in order of occurrence time is displayed. Thereby, it is possible to appropriately grasp that an alarm has occurred.

  The alarm is not limited to the occurrence of the alarm, but may be generated in response to the return or confirmation of the alarm. That is, the alarm is determined by an event to be notified to the user. In other words, an event to be notified to the user is registered as an alarm. In order to record such an alarm history, the concept of a monitoring point is introduced. In the monitoring point, information on the equipment 2 arranged at the location to be monitored is registered. A plurality of facility devices 2 may be registered in the monitoring point. In this case, for example, when alarms of a plurality of facility devices 2 are simultaneously generated, a certain alarm may be generated. That is, an alarm is generated by taking an AND of a plurality of alarms. Of course, the alarm conditional expression is not limited to AND (AND), but may be OR (OR), and further, a conditional expression combining AND (AND) and OR (OR) may be used. By registering such a monitoring point in advance by the user, it is possible to reliably monitor the portion to be watched.

  Next, the replay execution screen 14 will be described with reference to FIG. FIG. 3 is a diagram showing the replay execution screen 14. A track bar 21 is displayed on the replay execution screen 14. The track bar 21 corresponds to a replay period in which replay is performed. For example, when the replay start time 23 and end time 28 are input, the period between them becomes the time corresponding to the track bar. Further, a cursor 27 indicating the time point at which the replay display is currently being performed is arranged on the track bar 21. By moving the cursor 27, the playback time can be determined.

  The replay period start time 23 and end time 28 are displayed on the replay execution screen 14. The start time 23 and the end time 28 correspond to the start point (left end) and end point (right end) of the track bar 21. Therefore, in FIG. 3, 1 hour from 17:25:32 on February 2, 2009 is the replay period. The track bar 21 corresponds to this one hour. Of course, the replay period is not limited to one hour.

  Further, on the track bar 21, an alarm occurrence point 22 is displayed. The alarm occurrence location 22 is a position corresponding to the alarm occurrence time during the replay period. Here, it is possible to recognize that three alarms have occurred between 17 hours 25 minutes 32 seconds and 1 hour. Thus, by displaying the alarm occurrence point 22 on the track bar 21, it is possible to easily grasp the time when the alarm has occurred.

  Further, a replay button 25 and a rewind button 26 are displayed on the replay execution screen 14. When the play button 25 is pressed, replay is executed. That is, the pointer on the display screen is set on the playback button 25 using a mouse or the like. When the play button 25 is clicked with the left button of the mouse, replay is executed. Similarly, when the rewind button 26 is clicked, rewinding is performed. Of course, in addition to this, there may be a pause button and a fast-forward button.

  Next, execution of replay will be described. When the replay is executed, the status of the replay period is reproduced. For example, on the monitoring screen 10 shown in FIG. 2, the process data and the like for the replay period are updated. That is, the measurement data is sequentially displayed on the display screen with reference to the measurement data history. For example, measurement data is displayed on the layout screen 11 shown in FIG. In addition, an update interval 24 of measurement data is displayed on the replay execution screen 14. That is, when replay is executed, the measurement data is updated at the specified intervals. Further, the replay execution screen 14 includes a frame for setting the update interval 24. Here, measurement data is updated every second. Of course, the user may change the update interval 24.

  Furthermore, in the present embodiment, the measurement data is reproduced during the replay period, paying attention to the alarm occurrence time. For example, if the track bar 21 for 1 hour is set, the measurement cycle of measurement data is 1 second, and the update interval is 1 second, 3600 seconds are required to perform all replays. However, the point of time that the user wants to focus on is usually the alarm occurrence time and its surroundings. Therefore, in the present embodiment, the playback key time including the alarm occurrence time is set. Here, 5 seconds before and after the alarm occurrence time is set as the reproduction key time. That is, replay for one alarm is executed in 10 seconds.

  For example, if an alarm occurs at 17:45:10, the start point of the playback key time is 17: 45: 5, and the end point is 17:45:15. Thus, the reproduction key time is set to 10 seconds. On the monitoring screen 10, the measurement data acquired during this time is updated at 1 second intervals. Of course, the playback key time is not limited to 10 seconds.

  During times other than the playback key time, the replay is fast forwarded. For example, display of measurement data is skipped between playback key times. Specifically, when three alarms are generated, from the start time of the replay period (17:25:32) to the start point of the first playback key time and from the end point of the first playback key time. Until the start point of the second playback key time, from the end point of the second playback key time to the start point of the third playback key time, and from the end point of the third playback key time to the end time of the replay period ( 18:25:32), the replay is fast forwarded. Of course, during the fast-forwarding period, the measurement data may be thinned and displayed. For example, the measurement data may be displayed every two or more during the playback key time. In this way, replay is fast-forwarded during times other than the alarm. Thereby, the reproduction time can be shortened. Furthermore, it is possible to monitor the state of the facility by paying attention to the alarm. The cause of the alarm can be analyzed efficiently. Therefore, monitoring can be performed reliably, and minute behavioral changes can be recognized. Of course, this replay function can be executed in addition to the conventional functions such as through playback, pause, move to the beginning, and move to the end.

  Furthermore, the replay period is set by the user specifying an alarm. For example, one alarm is selected from the alarm list screen 15. A replay period may be set around this alarm. For example, when the replay period is 1 hour, 30 minutes before and after the selected alarm occurrence time is set as the replay period. Specifically, the user operates the mouse or the like to place a pointer on one alarm from the monitoring screen 10 alarm list screen 15. An alarm is designated by right-clicking in this state. Thus, the replay period can be set by designating the alarm. As a result, it is possible to analyze the alarms generated before and after the alarm of interest and the behavior of the equipment in the vicinity of the alarm generation time. Furthermore, the replay period may be set by designating two or more alarms. In this case, a replay period including all alarms is set.

  In this way, the replay execution screen can be read using the alarm list screen 15 as a source. Of course, the alarm may be specified directly from the history database storing the alarm history. Furthermore, the start time 23 and the end time 28 may be directly input in the replay execution screen 14. Alarms may be referred to with reference to other than the alarm list screen 15.

  An alarm search function may be provided on the alarm list screen 15 or the like. Then, an alarm may be designated from the retrieved alarm list and replayed. Further, during replay execution, it may be displayed so that the part where the alarm has occurred can be identified. For example, the color of the icon 18 of the equipment 2 causing the alarm is changed. Thereby, the equipment 2 which is the cause of the alarm can be easily recognized. Therefore, the cause of the alarm can be analyzed efficiently. In addition, on the alarm list screen 15, the currently reproduced alarm may be focused. For example, the currently reproduced alarm line is changed to a different color from the other lines. Switching to the target alarm time may be performed by interrupting the replay and clicking a line on the replay screen or the alarm list screen.

  Further, the display screen is switched for each alarm during replay playback. At the playback key time of a certain alarm, the layout screen 11 is switched to a screen related to the alarm. This related screen includes the equipment 2 that causes an alarm. For example, assume that the three alarms shown in FIG. 3 are different alarms. In this case, the layout screen 11 is switched according to the alarm. That is, the layout screen 11 related to the alarm that has actually occurred is displayed. For this purpose, a layout screen closely related to the alarm is set in advance as a related screen. In the layout screen 11, the measurement data is updated. By associating the related screen for each alarm in this way, it is possible to easily analyze the abnormality of the equipment 2 related to the alarm at the time of replay.

  Such an association between an alarm and a related screen may be set according to user information such as a user and a user level. That is, when the user or the user level is different, even when the same alarm is generated, a different layout screen 11 is displayed. In this way, analysis according to the user can be performed. Therefore, it can monitor more reliably and can improve the convenience. Further, the layout screen 11 displayed by the user may be switched.

  For example, the alarm and the related layout screen 11 are set in advance for each user ID or each user level. That is, a related screen is set in advance according to user information. When the user operates the client to log in to the server 1, the server 1 acquires user information such as a user name, a user ID, and a user level at the time of login. Thereby, the related screen with respect to an alarm can be displayed for every user information. Thereby, suitable monitoring according to a user can be performed.

  Furthermore, in order to grasp whether or not the user has browsed the alarm, browsing information indicating whether the user has not browsed or browsed may be added to the alarm list screen 15. Such browsing information may also be set for each user or each user level. Thereby, it is possible to grasp an alarm that has already been browsed.

  For example, it is assumed that the user operates the client 3 and logs in to the server 1. In this case, a list of alarms generated when the user has logged off is displayed on the alarm list screen 15. Of course, the alarm generated at the time of logoff is in an unviewed state. Then, the client 3 causes the user to confirm an unviewed alarm. For example, the replay is automatically executed to reproduce the related screen related to each alarm. As a result, it is standardized as a confirmation work that is first performed by the user at the start of work. Moreover, when performing confirmation work, you may filter an alarm.

  Of course, even when the confirmation work is performed, it is possible to pause for each alarm. That is, switching to the previous or next alarm can be requested. Thus, the convenience can be improved by adding browsing information indicating unread or already browsed for each user. Of course, browsing information may be set not for each user but for each user level.

  Next, the configuration of the server 1 will be described with reference to FIG. FIG. 4 is a block diagram schematically showing the configuration of the server 1. The server 1 includes a management server engine 31, a management server DB (database) 32, an alarm management DB 33, a history DB 34, and an alarm management engine 35. Each engine has an arithmetic processing unit of a processor and performs various arithmetic processes. Each DB (database) has storage means such as a memory and a storage medium, and stores various data.

  The management server engine 31 manages the client 3 and the equipment 2 using the management server DB 32. For example, the management server DB 32 stores data as shown in FIG. That is, the management server DB 32 stores a user name, a user ID, a password, and a user level in association with each other. In the client 3, when the user inputs the user ID and the user name together with the password, the server 1 approves the access. Thereby, the client 3 can refer to the data in the server 1. At this time, the server 1 stores the user ID of the user who operates the client. As described above, the management server DB 32 stores information about users as a DB.

  The alarm management engine 35 manages alarms using the alarm management DB 33 and the history DB 34. That is, the alarm management engine 35 refers to various data and displays the appropriate monitoring screen 10 on the display unit of the client 3 or the server 1. That is, as described above, the alarm management engine 35 fast-forwards the time until the alarm and executes replay. Further, the alarm management engine 35 displays the layout screen 11 related to the alarm. In other words, the alarm management engine is a replay execution unit that updates past measurement data displayed on the layout screen 11 corresponding to the designated alarm in order along the time series. Then, the alarm management engine 35 displays the reproduction key time measurement data including the time of occurrence of the alarm at a predetermined update interval, and fast-forwards the display of the measurement data until the reproduction key time start time. The alarm management engine 35 displays a list of alarms being managed and a list of alarms. Of course, the alarm management engine 35 may have a search function. In this case, a filtered alarm list is displayed.

  The history DB 34 stores an alarm history as a database. For example, as shown in FIG. 6, the occurrence date, time, tag name, and alarm type are stored in association with each other. Accordingly, the history of the alarm is added to the history DB 34 when the alarm occurs. The tag name is an identifier indicating the generated equipment device 2. The alarm type indicates, for example, whether the measurement data exceeds a lower limit value or an upper limit value. Then, alarms are accumulated in order along the time series. The alarm occurrence history is accumulated in the history DB 34. That is, the history DB 34 stores an alarm history with a time stamp. Further, the history DB 34 stores the history of measurement data. That is, measurement data from each equipment 2 is recorded in the history DB 34 with a time stamp.

  The alarm management DB 33 stores information on monitoring points and related screens as a database. For example, in the alarm management DB 33, as shown in FIG. 7, the user level, the monitoring point ID, and the related screen ID are associated with each other. The monitoring point specifies a location to be monitored in the equipment 2 or other equipment, and corresponds to an alarm. That is, the monitoring point stores the tag name of the equipment 2 to be referred to or a conditional expression thereof. Thereby, each alarm can be defined. Then, the related screen is associated with the monitoring point. The related screen is the layout screen 11 displayed in the monitoring screen 10 as described above. Therefore, while the alarm replay is being reproduced, the layout screen 11 corresponding to the alarm is displayed. Different layout screens are registered in advance for each related screen ID.

  Further, the user level is associated with the monitoring point ID. Thereby, a different layout screen 11 is displayed for each user level. Of course, the same related screen may be set for two or more user levels. Note that the monitoring point ID may be associated with the user ID instead of the user level. In this case, a different layout screen 11 is displayed for each user. Furthermore, the alarm management DB 33 and the management server DB 32 may be associated with browsing information indicating that browsing is not performed or has been browsed. Thereby, it is possible to determine whether the user has not browsed yet or has already browsed. The browsing information indicating whether the alarm is not browsed or browsed is stored in association with the alarm. Further, browsing information is set according to the user. Thereby, the convenience can be improved more.

  Thus, the monitoring method according to the present embodiment is a facility monitoring method in which a plurality of facility devices are provided. The monitoring method includes a step of storing a history of measurement data from the equipment 2, a step of storing alarm information of an alarm generated according to the measurement data of the equipment 2 with a time stamp, and a designated alarm And a replay step in which past measurement data displayed on the related screen is updated in order along the time series, and includes a predetermined time including an alarm occurrence. A replay step of displaying the process data of the period at a predetermined update interval and fast-forwarding the display of the process data until the start time of the predetermined period. Thereby, it can monitor reliably. Further, the server 1 approves the access of the client 3, the step of acquiring the user information of the user who operates the client 3, and the alarm generated during the stop period in which the client 3 is stopped with reference to the user information. May be further replayed in order. Thereby, it can monitor simply and reliably.

  In the above description, the monitoring device is described as having a server 1-client 3 configuration. For example, if the client 3 is a Web browser, the alarm management engine 35 of the server 1 sets a file equivalent to display HTML and sends it to the client 3 as a Web server. Alternatively, a separate Web server may be provided. Or you may comprise a monitoring apparatus with one computer. For example, the server 1 may execute replay playback. Furthermore, the monitoring device may be configured using two or more servers 1.

DESCRIPTION OF SYMBOLS 1 Server 2 Equipment 3 Client 4 Input part 5 Display part 6 Processing part 10 Monitoring screen 11 Layout screen 12 Plant hierarchy screen 13 Trend screen 14 Replay execution screen 15 Alarm list screen 18 Icon 21 Track bar 23 Alarm generation time 23 Replay period 24 Update interval 25 Play button 26 Rewind button 31 Management server engine 32 Management server DB
33 Alarm management DB
34 History DB
35 Alarm management engine

Claims (10)

A facility monitoring device provided with a plurality of facility devices,
An alarm information storage unit for storing alarm information of an alarm generated according to the measurement data of the equipment with a time stamp;
A screen information storage unit for storing screen information of a related screen corresponding to the alarm;
A replay execution unit that updates the past measurement data displayed on the related screen corresponding to a specified alarm in a time-series order, and the measurement data of a predetermined period including the time of occurrence of the alarm And a replay execution unit that fast-forwards display of the measurement data until the start time of the predetermined period. Display a list of the alarms in chronological order,
The monitoring apparatus according to claim 1, wherein the replay is executed by setting a replay time including an alarm occurrence time designated from the alarm information list.   The monitoring apparatus according to claim 2, wherein the alarm is filtered and displayed on the list. The monitoring device has a server-client configuration;
Obtaining user information of a user operating the client;
5. The monitoring apparatus according to claim 1, wherein alarms generated during a stop period in which the client is stopped are replayed in order with reference to the user information.   The monitoring apparatus according to any one of claims 1 to 4, wherein the alarm is generated in response to an alarm from a plurality of facility devices. A facility monitoring method provided with a plurality of facility devices,
Storing a history of measurement data from the equipment;
Storing alarm information of an alarm generated according to the measurement data of the equipment with a time stamp;
Displaying a related screen corresponding to the specified alarm;
A replay step of updating the past measurement data displayed on the related screen in a time-sequential order, and displaying the measurement data for a predetermined period including the time of occurrence of the alarm at a predetermined update interval. And a replay step of fast-forwarding the display of the measurement data until the start time of the predetermined period. Display a list of the alarms in chronological order,
The supervision method according to claim 6, wherein the replay is executed by setting a replay time including an alarm occurrence time designated from the alarm information list.   The monitoring apparatus according to claim 7, wherein the alarm is filtered and displayed on the list. The server authorizes the client's access;
Obtaining user information of a user operating the client;
The method according to any one of claims 6 to 8, further comprising a step of replaying in sequence the alarms generated during the stop period in which the client is stopped with reference to the user information. Monitoring method.   The monitoring method according to claim 6, wherein the alarm is generated in response to an alarm from a plurality of facility devices.

Images