Display device, control device, control method, and computer program

Abstract

Provided are a display device, a control device, a control method, and a computer program with which it is possible to visualize the occurrence frequency of an alarm.　Provided is a display device (32) that displays an operating state of a plant (1), wherein the occurrence frequency in a first period of each of a plurality of alarm types, which indicate the respective types of a plurality of alarms generated in the plant (1), are displayed so as to be arrayed by alarm type. As a result, it is possible to visualize the occurrence frequency of the alarms in the first period by alarm type.

Description

[Technical field]

[0001] The present invention relates to a display device, a control device, a control method, and a computer program for displaying an operating state of a plant. [Background technology]

[0002] Conventionally, sensors are installed in plants, and the operating status of the plants is monitored through the measured values ​​of the sensors. For example, Patent Document 1 discloses that when an object on a display screen is selected, information from the sensor relating to the object is displayed so that an operator can intuitively grasp the detection target and detection results of the sensor. Patent Document 2 discloses that a plurality of warning messages are displayed on an warning monitoring screen, and when an operator presses a graph display on the display screen, graph information of the corresponding warning message is displayed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 4-308895 [Patent Document 2] JP 2016-115195 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the conventional configuration, it was possible to display alarms that occurred in a plant in chronological order. However, in the conventional configuration, for example, when a certain type of alarm occurred many times in a certain period of time, it was difficult to grasp the occurrence frequency of the alarm, such as the number of times the alarm occurred.

[0005] It is an exemplary object of an embodiment of the present invention to provide a display device, a control device, a control method, and a computer program capable of visualizing the frequency of occurrence of an alarm. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, a display device according to one embodiment of the present invention is a display device that displays the operating status of a plant, and displays, for a plurality of alarms that have occurred in the plant, the occurrence frequency during a first period of each alarm type indicating the type of alarm, in a manner arranged by alarm type.

[0007] In the above-described display device, displaying the occurrence frequency in the first period for each alarm type in a manner arranged by alarm type may be displaying the occurrence frequency in the first period for each alarm type in a graph format.

[0008] In the above-mentioned display device, displaying the occurrence frequency in the first period for each alarm type in a manner arranged by alarm type may mean displaying a bar graph corresponding to the occurrence frequency in the first period for each alarm type arranged in descending or ascending order of occurrence frequency for each alarm type.

[0009] In the above-mentioned display device, for an alarm type whose occurrence frequency in a first period is displayed, an occurrence history of the alarm type in a second period included in the first period may be further displayed.

[0010] In the above-mentioned display device, together with the occurrence history of the alarm type during the second period, the occurrence history of a related event related to the alarm type during the second period may further be displayed.

[0011] In the above-described display device, the related event may be a plant process, or may be an alarm type different from the alarm type whose occurrence frequency in the first period is displayed.

[0012] In the above-described display device, the first period may be a part of an operation period of the plant.

[0013] In the above-described display device, the occurrence frequency may be the number of occurrences.

[0014] A control device of another embodiment of the present invention is a control device that controls a display device that displays the operating status of a plant, and includes an acquisition unit that acquires alarm information indicating alarms that occur in the plant, a calculation unit that calculates an occurrence frequency of a first period for each alarm type indicating the type of alarm based on the alarm information, and a display control unit that causes the display device to display the calculated occurrence frequency of each alarm type in the first period in a manner arranged by alarm type.

[0015] The above-mentioned control device may further include a generation unit that generates, for an alarm type whose occurrence frequency for a first period is displayed based on the alarm information, occurrence history information indicating an occurrence history for a second period included in the first period of the alarm type, and the display control unit may further cause the display device to display the generated occurrence history information for the second period.

[0016] In the above-described control device, the display control may further cause the display device to display, based on the generated occurrence history information for the second period, the occurrence of alarm types in a graph format arranged in chronological order.

[0017] The above-mentioned control device may further include a receiving unit that receives a selection of an associated event related to the alarm type for which the occurrence frequency for the first period has been displayed, and the generating unit may generate occurrence history information indicating an occurrence history for a second period of the selected associated event based on process information or alarm information of the plant, and the display control unit may display, on the display device, the generated occurrence history information for the second period of the associated event together with the generated occurrence history information for the alarm type.

[0018] In the above-mentioned control device, the display control unit may cause the display device to arrange occurrences of the alarm type in chronological order based on occurrence history information for the generated alarm type during a second period, and may further display in a graph format the occurrences of the associated events arranged in chronological order based on occurrence history information for the generated associated events during a second period.

[0019] The control device described above may further include a true / false input unit configured to be able to input whether the occurrence of the alarm type for which the occurrence frequency in the first period is displayed is true or false.

[0020] Another aspect of the control method of the present invention is a control method for controlling a display device that displays an operating status of a plant, and includes the steps of acquiring alarm information indicating alarms that occur in the plant, calculating an occurrence frequency in a first period for each alarm type indicating the type of alarm based on the alarm information, and displaying on the display device the calculated occurrence frequency in the first period for each alarm type in a manner arranged by alarm type.

[0021] A program according to another aspect of the present invention is a program to be executed by a computer to control a display device that displays the operating status of a plant, and includes the steps of acquiring alarm information indicating alarms that occur in the plant, calculating an occurrence frequency in a first period for each alarm type indicating the type of alarm based on the alarm information, and displaying on the display device the calculated occurrence frequencies in the first period for each alarm type in a manner arranged by alarm type.

[0022] Any combination of the above components or mutual substitution of the components or expressions of the present invention between methods, devices, systems, computer programs, data structures, recording media, etc. are also valid aspects of the present invention. Effect of the Invention

[0023] According to the present invention, it is possible to visualize the frequency of occurrence of an alarm. [Brief description of the drawings]

[0024] [Figure 1] 1 is a schematic diagram showing an overall configuration of a plant according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing functional blocks of the system according to the present embodiment. [Diagram 3]FIG. 1 is a diagram showing a physical configuration of a system according to an embodiment of the present invention. [Figure 4] 3A to 3C are diagrams showing transitions of various display screens according to the embodiment. [Diagram 5] FIG. 4 is a diagram illustrating an example of a dashboard display screen according to the embodiment. [Figure 6] FIG. 13 is a diagram showing an example of an occurrence history screen according to the embodiment. [Figure 7] 10 is a flowchart illustrating an example of an operation process according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] The present invention will be described below through the embodiments of the invention with reference to the drawings, but the following embodiments do not limit the invention according to the claims, and all combinations of features described in the embodiments are not necessarily essential to the solution of the invention. The same or equivalent components, parts, and processes shown in each drawing are given the same reference numerals, and duplicated descriptions are omitted as appropriate.

[0026] FIG. 1 is a schematic diagram showing the overall configuration of a plant according to this embodiment. First, the configuration of a plant 1 to which this embodiment is applied will be described with reference to FIG. 1. The plant 1 is, for example, a power plant (incineration plant) including a circulating fluidized bed boiler (circulating fluidized bed type), and is equipped with a boiler that generates steam by burning fuel while circulating a circulating material such as silica sand that flows at high temperature. As fuel for the plant 1, in addition to fossil fuels such as coal, for example, non-fossil fuels (wood biomass, waste tires, waste plastics, sludge, etc.) can be used. The steam generated in the plant 1 is used to drive a turbine 100. Note that the plant to which this embodiment is applied is not limited to a power plant or incineration plant including a boiler, but may be any plant from which process data can be acquired, such as a chemical plant or a wastewater treatment plant.

[0027] The plant 1 is configured to burn fuel in a furnace 2, separate the circulating material from the exhaust gas by a cyclone 3 that functions as a solid-gas separator, and return the separated circulating material to the furnace 2 for circulation. The separated circulating material is returned to the bottom of the furnace 2 via a circulating material recovery pipe 4 connected to the bottom of the cyclone 3. The bottom of the circulating material recovery pipe 4 and the bottom of the furnace 2 are connected via a loop seal section 4a with a narrowed flow path. This results in a predetermined amount of circulating material being stored in the bottom of the circulating material recovery pipe 4. The exhaust gas from which the circulating material has been removed by the cyclone 3 is supplied to the rear flue 5 via the exhaust gas flow path 3a.

[0028] The boiler includes a furnace 2 for burning fuel and a heat exchanger for generating steam and the like using heat obtained by the combustion. A fuel supply port 2a for supplying fuel is provided in the middle of the furnace 2, and a gas outlet 2b for discharging combustion gas is provided in the upper part of the furnace 2. Fuel supplied to the furnace 2 from a fuel supply device (not shown) is supplied to the inside of the furnace 2 through the fuel supply port 2a. In addition, a furnace wall tube 6 for heating boiler feed water is provided on the furnace wall of the furnace 2. The boiler feed water flowing through the furnace wall tube 6 is heated by combustion in the furnace 2.

[0029] In the furnace 2, the solids containing the fuel supplied from the fuel supply port 2a are fluidized by the air for combustion and fluidization introduced from the air supply line 2c at the bottom, and the fuel is burned at about 800 to 900°C while flowing. The combustion gas generated in the furnace 2 is introduced into the cyclone 3 together with the circulating material. The cyclone 3 separates the circulating material from the gas by centrifugal separation, and returns the separated circulating material to the furnace 2 via the circulating material recovery pipe 4, while sending the combustion gas from which the circulating material has been removed through the exhaust gas flow path 3a to the rear flue 5.

[0030] In the furnace 2, a part of the circulating material, called the in-furnace bed material, accumulates at the bottom. This bed material may contain bed material with a coarse particle size that is unsuitable for circulating flow and exhaust combustion impurities, and these bed materials that are unsuitable for circulating flow may cause poor flow. Therefore, in order to suppress poor flow, the in-furnace bed material is continuously or intermittently discharged to the outside from the discharge port 2d at the bottom of the furnace 2. After removing unsuitable materials such as metals and coarse particle size from the discharged bed material on a circulation line not shown, the discharged bed material is either supplied to the furnace 2 again or discarded as it is. The circulating material of the furnace 2 circulates in a circulation system consisting of the furnace 2, the cyclone 3, and the circulating material recovery pipe 4.

[0031] The rear flue 5 has a flow path for flowing the gas discharged from the cyclone 3 to the rear stage. The rear flue 5 has a superheater 10 that generates superheated steam and an economizer 12 that preheats boiler feed water as an exhaust heat recovery section that recovers heat from the exhaust gas. The exhaust gas flowing through the rear flue 5 is cooled by heat exchange with the steam and boiler feed water flowing through the superheater 10 and the economizer 12. The rear flue 5 also has a steam drum 8 in which the boiler feed water that has passed through the economizer 12 is stored, and the steam drum 8 is also connected to the furnace wall tube 6.

[0032] The economizer 12 transfers heat from the exhaust gas to the boiler feed water to preheat the boiler feed water. The economizer 12 is connected to the pump 7 by a pipe 21, and is also connected to the steam drum 8 by a pipe 22. The boiler feed water is supplied from the pump 7 through the pipe 21 to the economizer 12 and preheated by the economizer 12, and is then supplied to the steam drum 8 through the pipe 22.

[0033] A downcomer pipe 8a and a furnace wall pipe 6 are connected to the steam drum 8. The boiler feed water in the steam drum 8 flows down the downcomer pipe 8a, is introduced into the furnace wall pipe 6 at the lower side of the furnace 2, and flows toward the steam drum 8. The boiler feed water in the furnace wall pipe 6 is heated by the combustion heat generated in the furnace 2, and evaporates in the steam drum 8 to become steam.

[0034] A saturated steam pipe 8b that discharges the steam inside is connected to the steam drum 8. The saturated steam pipe 8b connects the steam drum 8 and a superheater 10. The steam inside the steam drum 8 is supplied to the superheater 10 via the saturated steam pipe 8b. The superheater 10 superheats the steam using the heat of the exhaust gas to generate superheated steam. The superheated steam passes through a pipe 10a and is supplied to a turbine 100 outside the plant 1 and is used for power generation.

[0035] The pressure and temperature of the steam discharged from the turbine 100 are lower than the pressure and temperature of the steam discharged from the superheater 10. Although not particularly limited, the pressure of the steam supplied to the turbine 100 is about 10 to 17 MPa, and the temperature is about 530 to 570°C.

[0036] A condenser 102 is provided downstream of the turbine 100. The steam discharged from the turbine 100 is supplied to the condenser 102, where it is condensed and returned to saturated water, and then supplied to the pump 7. A generator is connected to the turbine 100, which converts kinetic energy obtained by the rotation of the turbine 100 into electrical energy.

[0037] The pump 7a supplies makeup water so as to maintain a constant water level in the condenser 102. In Fig. 1, a flow rate u1 of makeup water supplied by the pump 7a (an example of "process data") is shown.

[0038] The process data (data related to the operation of the plant 1) handled in this embodiment may be any data related to the plant 1, and may be, for example, data obtained by measuring the state of the plant 1 with a sensor (an example of "process data"), and more specifically, may include measured values ​​of the temperature, pressure, flow rate, and the like of the plant 1. FIG. 1 shows a boiler feedwater flow rate u2 (an example of "process data") supplied from the pump 7 to the economizer 12. FIG. 1 also shows a boiler outlet steam flow rate u3 (an example of "process data") supplied from the superheater 10 to the turbine 100, and a saturated steam flow rate u4 (an example of "process data") supplied from the steam drum 8 to the superheater 10. The make-up water flow rate u1 may be controlled to follow the saturated steam flow rate u4. The boiler feedwater flow rate u2 may be controlled to follow the adjustment while monitoring both the boiler outlet steam flow rate u3 (or the superheated steam flow rate) and the liquid level of the steam drum 8.

[0039] If a hole occurs in the pipe system that constitutes the plant 1, the make-up water flow rate u1 increases, and the flow rate difference between the boiler feedwater flow rate u2 and the boiler outlet steam flow rate u3 increases. A DCS (Distributed Control System, Fig. 2) 20 receives process data of the plant 1, such as the make-up water flow rate u1, the boiler feedwater flow rate u2, the boiler outlet steam flow rate u3, and the saturated steam flow rate u4, from the plant 1, monitors the operating status of the plant 1, and monitors whether any abnormality has occurred in the plant 1. As will be described later, a monitoring device 40 (Fig. 2) evaluates the process data based on alarm judgment logic set for each type of abnormality, and issues an alarm if an abnormality occurs.

[0040] Although the make-up water flow rate u1, the boiler feed water flow rate u2, the boiler outlet steam flow rate u3, and the saturated steam flow rate u4 are exemplified as process data, the process data related to the plant 1 may be other data or data calculated based on a plurality of process data. The process data related to the plant 1 may be other data such as temperature, pressure, etc., or may be data obtained from a sensor or the like that has not been subjected to calculation processing.

[0041] Next, the system 30 according to the present embodiment will be described with reference to Fig. 2 and Fig. 3. Fig. 2 is a diagram showing functional blocks of the system 30 according to the present embodiment. Fig. 3 is a diagram showing the physical configuration of the system 30 according to the present embodiment.

[0042] DCS 20 is a distributed control system for controlling plant 1, and as shown in FIG. 2, acquires process data from sensors and the like installed in plant 1, and supplies control signals to plant 1 for controlling plant 1 based on this data.

[0043] The system 30 includes a display device 32 and a monitoring device 40. The monitoring device 40 includes a control unit 31 and a storage unit 33. The control unit 31 includes, as functional components, an acquisition unit 311, a calculation unit 312, a generation unit 313, a reception unit 314, and a display control unit 315. The storage unit 33 stores various types of data, for example, a process information DB 33A, an alarm information DB 33B, and an occurrence history information DB 33C.

[0044] The acquisition unit 311 acquires process data from, for example, the DCS 20. The acquisition unit 311 sequentially acquires process data from the DCS 20 while the plant 1 is in operation. The acquired process data is stored in the process information DB 33A as information related to the process of the plant 1 (hereinafter also referred to as "process information"). Note that the plant 1 is "in operation" as long as at least a part of the plant 1 is in operation. The operating period of the plant 1 is the period during which at least a part of the plant 1 is in operation, excluding pre-planned downtime periods for maintenance or the like.

[0045] The acquisition unit 311 also acquires alarm information from the DCS 20. The acquisition unit 311 acquires alarm information from the DCS 20 each time an alarm is issued (an example of "occurrence") during operation of the plant 1. The alarm information indicates an alarm that has occurred in the plant 1, and is information on an alarm (warning) regarding an abnormality that has occurred. The alarm information includes an alarm item (type of the alarm), an alarm occurrence date and time (date and time when the alarm occurred), an alarm level (the level (importance) of the alarm, etc., and is classified, for example, into a heavy alarm, a medium alarm, a light alarm, etc.), and a value of process data related to the alarm (for example, the value of the make-up water flow rate u1 or the boiler feedwater flow rate u2 determined to be abnormal), etc.

[0046] The DCS 20 judges whether an abnormality or the like has occurred in the plant 1, and generates alarm information when it is judged that an abnormality has occurred. The DCS 20 judges that an abnormality has occurred, for example, when some value included in the process data exceeds a predetermined threshold value or when a predetermined change occurs in the trend. More specifically, the DCS 20 may evaluate predetermined process data based on an alarm judgment logic and judge whether an abnormality that may occur in the plant 1, such as a blowout (a state in which metal materials such as tubes and pipes constituting a boiler are damaged and ruptured, causing internal steam to leak to the outside, such as a boiler tube leak. This includes a state in which a blowout is likely to occur in the future. The same applies below) has occurred. The alarm information generated by the DCS 20 is also particularly referred to as "DCS alarm information". Similarly, the system 30 may also judge whether an abnormality or the like has occurred in the plant 1 based on the process data acquired by the acquisition unit 311, and judge that an abnormality has occurred. The alarm information generated at this time is also particularly referred to as "system alarm information". Hereinafter, the DCS alarm information and the system alarm information are collectively referred to as "alarm information". The alarm information is stored in the alarm information DB 33B.

[0047] The calculation unit 312 calculates the occurrence frequency in the first period for each alarm type indicating the type of alarm, based on the alarm information stored in the alarm information DB 33B. The calculated occurrence frequency for each alarm type is an index indicating the frequency of alarms of that alarm type that occurred in the plant 1 during a certain period in the past. The first period is a part of the operation period of the plant 1, for example, 24 hours. The first period may be a period that is set in advance, or may be a period that can be changed as appropriate. In this way, since the first period is a part of the operation period of the plant 1, it is possible to display the occurrence frequency for each alarm type by focusing on a period extracted from the operation period of the plant 1, and it is possible to easily grasp the occurrence frequency of an alarm type that occurs in a specific time period, for example.

[0048] The occurrence frequency is, for example, the number of occurrences in a first period, which makes it easy to grasp the number of occurrences of each alarm type in the first period.

[0049] The occurrence frequency is not limited to the number of occurrences in the first period, but may be the occurrence ratio in the first period (e.g., the ratio of the number of occurrences of the alarm type to the average number of occurrences of all alarm types in the first period), the occurrence frequency (e.g., the frequency of the alarm type when the average number of occurrences of all alarm types in the first period is set to a reference value {e.g., "1"}), etc.

[0050] The calculation unit 312 calculates the occurrence frequency of each alarm type in the first period, for example, at any preset timing (for example, the timing when the alarm occurs, every second, every minute, every hour, etc.). The alarm types for calculating the occurrence frequency are classified in any manner. The alarm types may be classified, for example, for each sensor that measures the state of the plant 1. In this case, the alarm types may include, for example, alarms related to makeup water flow rate, alarms related to boiler feedwater flow rate, alarms related to boiler outlet steam flow rate, alarms related to saturated steam flow rate, etc.

[0051] Furthermore, the calculation unit 312 calculates the occurrence frequency of each alarm type in the first period based on the DCS alarm information. That is, the occurrence frequency of each alarm type in the first period calculated by the calculation unit 312 is calculated from the alarm information of the DCS 20.

[0052] The generating unit 313 generates occurrence history information indicating the occurrence history of an alarm type for which the occurrence frequency for the first period has been displayed on the display device 32 by the display control unit 315 described later, based on the alarm information stored in the alarm information DB 33B. The generated occurrence history information of the alarm type is information regarding the occurrence history of alarms of the alarm type that occurred in the plant 1 during a certain period in the past. The second period is a period included in the above-mentioned first period, and is, for example, 24 hours, the same as the first period. The second period may be a period that is set in advance, or may be a period that can be changed as appropriate. The second period may be a period shorter than the first period, for example, 12 hours, 8 hours, or 6 hours.

[0053] The occurrence history information includes, for example, the timing of the alarm occurrence during the second period (e.g., the date and time when the alarm type occurred), the alarm occurrence interval (e.g., the time interval when the alarm type occurred, and the alarm occurrence density (e.g., the rate at which the alarm type occurred within a certain period of time (or occurrence rate)).

[0054] The generating unit 313 generates occurrence history information for the second period for each alarm type at any preset timing (for example, the timing when an alarm occurs, the timing when an operator operates, every second, every minute, every hour, etc.) The alarm types for generating the occurrence history information are classified in the same manner as the alarm types for calculating the occurrence frequency.

[0055] Furthermore, the generating unit 313 generates occurrence history information for each alarm type for the second period based on the DCS alarm information. That is, the occurrence history information for each alarm type for the second period generated by the generating unit 313 is generated from the alarm information of the DCS 20.

[0056] The reception unit 314 receives various information inputs, instructions, selections, etc. in response to operations by the operator. For example, the reception unit 314 receives instructions for display screen transition, designation of a planned downtime period, inputs, selections, selection of an alarm type displayed on the display device 32, selection of an associated event related to an alarm type displayed on the display device 32, etc.

[0057] The relevant event related to the alarm type is a process of the plant 1, or an alarm of a different type from the alarm type whose occurrence frequency in the first period is displayed on the display device 32. The process of the plant 1 is, for example, an event (event) performed in the plant 1, such as measuring the state of the plant 1 with a sensor or recording an operation in the plant 1. The reception unit 314 receives a selection of an event related to the alarm type displayed on the display device 32 among these relevant events. In addition, the alarms to be selected by the reception unit 314 include both an alarm (DCS alarm) generated when the DCS 20 judges whether or not an abnormality or the like has occurred in the plant 1 and judges that an abnormality has occurred, and an alarm (system alarm) generated when the system 30 judges whether or not an abnormality or the like has occurred in the plant 1 and judges that an abnormality has occurred. The reception unit 314 receives a selection of an alarm of a different type from the alarm type whose occurrence frequency in the first period is displayed on the display device 32 among these alarms.

[0058] Furthermore, the generating unit 313 generates occurrence history information for a second period for the related event selected via the receiving unit 314, based on the process information stored in the process information DB 33A or the alarm information stored in the alarm information DB 33B. The generated occurrence history information is information on the occurrence history of processes or alarm types that occurred in the plant 1 during a certain period in the past.

[0059] The occurrence history information includes, for example, the timing of the occurrence of a process or alarm during the second period (e.g., the date and time when the process or alarm type occurred), the interval at which the process or alarm occurred (e.g., the time interval at which the process or alarm type occurred), the occurrence density of the process or alarm (e.g., the rate at which the process or alarm type occurred within a certain period of time (or occurrence rate)), etc.

[0060] The generating unit 313 generates occurrence history information of the second period for each related event at, for example, any preset timing (for example, the timing when a process or an alarm occurs, the timing when an operator operates, every second, every minute, every hour, etc.). The alarm types for generating the occurrence history information may be classified in the same manner as the alarm types for calculating the occurrence frequency, or may be classified in a different manner.

[0061] The generating unit 313 generates the occurrence history information for each associated event during the second period based on the DCS alarm information and the system alarm information. That is, as described above, the associated event may include both a DCS alarm and a system alert, so the occurrence history information for each associated event during the second period generated by the generating unit 313 is generated from both the alarm information of the DCS 20 and the alarm information of the system 30.

[0062] The display control unit 315 generates display data based on the process data, alarm information, occurrence frequency in the first period, and occurrence history information in the second period, and causes the display device 32 to display a display screen based on the display data. That is, the display control unit 315 controls the display of information related to the operating state of the plant 1, such as displaying the process data, the occurrence frequency in the first period for each alarm type, and displaying occurrence history information, on the display device 32. Examples of the screens displayed on the display device 32 will be described later.

[0063] The process information DB 33A stores the process information (process data) acquired by the acquisition unit 311. That is, the process information DB 33A stores process information (process history information) related to processes that have occurred so far.

[0064] The alarm information DB 33B stores alarm information (DCS alarm information) acquired by the acquisition unit 311 from the DCS 20, and alarm information (system alarm information) acquired from the system 30. That is, the alarm information DB 33B stores alarm information (alarm history information) related to alarms that have occurred in both the DCS 20 and the system 30.

[0065] The occurrence history information DB 33C stores occurrence history information generated by the generating unit 313, the occurrence history information indicating the occurrence history of the alarm type during the second period, and the occurrence history information indicating the occurrence history of the related event during the second period.

[0066] The display device 32 displays various display screens including information related to the operation of the plant 1 based on the display data supplied by the display control unit 315. The various display screens displayed by the display device 32 will be described later.

[0067] The process information DB33A, the alarm information DB33B, and the occurrence history information DB33C stored in the storage unit 33 are not limited to the example shown in Fig. 6. For example, at least a part of the process information DB33A, the alarm information DB33B, and the occurrence history information DB33C stored in the storage unit 33 may be subjected to a predetermined normalization to subdivide any group unit. Furthermore, the information (data) stored in the process information DB33A, the alarm information DB33B, and the occurrence history information DB33C is not limited to being stored in a database format, and may be stored in any structure and format, such as a table format, a block format, or a file format.

[0068] Physically, the system 30 has a CPU (Central Processing Unit) 30a, a RAM (Random Access Memory) 30b, a ROM (Read only Memory) 30c, a communication unit 30d, an input unit 30e, and a display unit 30f, as shown in Fig. 3, and these components are connected to each other via a bus so as to be able to transmit and receive data. Each functional block of the system 30 shown in Fig. 2 is realized by the physical configuration shown in Fig. 3.

[0069] In this embodiment, the system 30 is configured by one computer. However, the system 30 may be realized by combining a plurality of computers. For example, in addition to the display unit 30f, a display constituting a different display unit for displaying other information may be provided. The system 30 may be configured by a tablet terminal. By configuring the system 30 by a tablet terminal, the system 30 can be carried around, and the system 30 can be used while traveling around the plant 1, for example. The configuration shown in FIG. 3 is an example, and the system 30 may have other configurations, or may not have some of these configurations. Also, some of the configurations may be provided in a remote location. For example, the control unit 31 having the CPU 30a, etc. may be provided in a remote location. In this case, the display device 32 having the display unit 30f, etc. may be configured to acquire a control signal generated in the control unit 31 provided in the remote location via a network.

[0070] The CPU 30a is a calculation unit that performs control related to the execution of the programs stored in the RAM 30b or the ROM 30c, and performs calculations and processing of data. The CPU 30a is a calculation unit that executes a program (monitoring program) that displays a graph and an explanatory text of the process data of the plant 1. The CPU 30a receives various data from the input unit 30e and the communication unit 30d, and displays the calculation results of the data on the display unit 30f or stores them in the RAM 30b.

[0071] The RAM 30b is a rewritable part of the storage unit, and may be configured with a semiconductor storage element such as a DRAM or an SRAM. The RAM 30b may store data such as a program executed by the CPU 30a and process data of the plant 1. Note that these are merely examples, and the RAM 30b may store data other than these, or some of these data may not be stored.

[0072] The ROM 30c is a storage unit from which data can be read, and may be configured, for example, with a semiconductor storage element such as a flash memory or a HDD. The ROM 30c may store, for example, computer programs for executing various processes shown in this embodiment and data that is not rewritten. The data that is not rewritten includes, for example, information related to the plant 1 and specifications of components of the plant 1. The ROM 30c may also store data such as process data of the plant 1, indicators related to the operation of the plant 1 (such as availability and efficiency), and planned shutdown periods.

[0073] The communication unit 30d is an interface that connects the system 30 to other devices and may be connected to a communication network such as the Internet.

[0074] The input unit 30e receives data input in response to operations by an operator, and may include, for example, a keyboard and a touch panel.

[0075] The display unit 30f has a screen for visually displaying the results of calculations performed by the CPU 30a, and may be configured, for example, with an LCD (Liquid Crystal Display). The display unit 30f may display graphs and explanatory text of process data. The display unit 30f may also be provided so that a single screen is configured by connecting multiple displays.

[0076] A computer program for executing various processes shown in this embodiment may be provided by being stored in a computer-readable storage medium such as ROM 30c, or may be provided via a communication network connected by a communication unit 30d. In the system 30, the CPU 30a executes the monitoring program to realize various operations included in this embodiment. Note that these physical configurations are merely examples and do not necessarily have to be independent configurations. For example, the system 30 may include an LSI (Large-Scale Integration) in which the CPU 30a and the RAM 30b or ROM 30c are integrated.

[0077] FIG. 4 is a diagram showing transitions of various display screens according to the present embodiment. As shown in FIG. 4, the display device 32 displays a login display screen DP0, a dashboard display screen DP1, and an occurrence history display screen DP2. The arrows between the display screens shown in FIG. 4 indicate that the display screens transition based on an instruction from the operator. That is, in the system 30, based on an instruction from the operator, transitions are possible from the login display screen DP0 to the dashboard display screen DP1, and further from the dashboard display screen DP1 to the occurrence history display screen DP2. Note that, when each display screen transitions in the system 30, the previous display screen may be replaced with the next display screen, or the previous display screen may remain and the next display screen may be displayed together. Also, the above-mentioned display screens are merely examples, and the display device 32 may display display screens other than these display screens.

[0078] The login display screen DP0 displays information necessary for the operator to log in to the system 30. The information necessary for logging in is, for example, the operator's user ID and password. The login display screen DP0 accepts input of the user ID and password from the operator. From the login display screen DP0, it is possible to transition to a dashboard display screen DP1, etc.

[0079] The dashboard display screen DP1 displays various latest indicators related to the operation of the plant 1 at predetermined time intervals. The dashboard display screen DP1 displays, for example, trend graphs and the like based on various indicators related to the operation of the plant 1. The dashboard display screen DP1 also displays, for example, an abnormality display indicating the occurrence or possibility of an abnormality that may cause the plant 1 to be stopped, and a warning display indicating the occurrence or possibility of a warning when process data related to the plant 1 reaches a predetermined state. The dashboard display screen DP1 also displays, for example, the number of alarms and the time of occurrence. Furthermore, the dashboard display screen DP1 displays the occurrence frequency in a first period for each alarm type.

[0080] The occurrence history display screen DP2 displays the occurrence history in the second period for the alarm type selected on the dashboard display screen DP1. Also, on the occurrence history display screen DP2, it is possible to select an associated event related to the alarm type selected on the dashboard display screen DP1. The occurrence history display screen DP2 can also display the occurrence history in the second period for the selected associated event.

[0081] Next, an example of the dashboard display screen DP1 will be described with reference to Fig. 5. The dashboard display screen DP1 includes areas R10 to R13. Note that the example shown in Fig. 5 is a part of the dashboard display screen DP1, and the actual dashboard display screen DP1 also includes areas other than the areas R10 to R13.

[0082] In region R10, “Dashboard” is displayed as the status of the current screen. The display in region R10 makes it easy to know what status the current screen is in.

[0083] In the area R11 of the dashboard display screen DP1, a warning display is displayed as the "latest alarm information" to indicate the occurrence of a warning when the process data related to the plant becomes a predetermined state. The warning display is a display of a predetermined state of the process data that affects the operation efficiency of the plant 1, and does not have the possibility of stopping the plant 1, such as a blowout, but reduces the operation efficiency of the plant 1. In the area R11, the occurrence history of the warning display is displayed in a state in which time information indicating the occurrence and information indicating the content are arranged in the order of occurrence. For example, at the beginning of the area R11, time information "YYYY / MM / DD hh:mm:ss" and information indicating the content of the warning "Alarm A" are displayed in association with each other. From the information displayed in this area R11, the operator of the plant 1 can recognize that the warning about Alarm A occurred at YYYY year MM month DD day hh hour mm minute ss second. Similarly, the operator of the plant 1 can recognize the history of time information indicating the occurrence of a predetermined state of other process data that affects the operation efficiency of the plant 1 and information indicating the content.

[0084] Area R12 of the dashboard display screen DP1 displays indices such as efficiency related to the operation of the plant 1. For example, area R12 displays one or more trend graphs with the vertical axis representing indices important for stable operation of the plant 1 and the horizontal axis representing time. The times at the rightmost ends of these trend graphs are the latest times at which these indices were calculated.

[0085] In the area R13 of the dashboard display screen DP1, the occurrence frequency of each alarm type in the first period is displayed in a manner arranged by alarm type. This makes it possible to visualize the occurrence frequency of each alarm type in the first period. Therefore, by understanding the occurrence frequency of an alarm, rather than simply whether an alarm has occurred, it is possible to prevent, for example, a malfunction that gradually develops over a certain period of time.

[0086] Specifically, the "alarm total" information is, for example, the number of times (occurrences) that DCS 20 has determined to be an abnormality in the past 24 hours, totaled for each type of alarm. Note that "alarm 1", "alarm 2", etc. in Fig. 5 may display identification information for identifying the type of alarm. The identification information may be, for example, the name of a specific sensor, the name of an alarm item detected by the sensor, etc.

[0087] Then, the bar graphs, the lengths of which correspond to the number of occurrences in the first period that are tallied and calculated for each alarm type, are arranged in descending order of the number of occurrences, and displayed in the form of a so-called Pareto chart. Note that the bar graphs displayed in region R13 may also be arranged in ascending order of the number of occurrences. In this way, by arranging and displaying the bar graphs corresponding to the occurrence frequency in the first period for each alarm type in descending or ascending order of occurrence frequency for each alarm type, the occurrence frequency in the first period for each alarm type can be easily visualized using a so-called Pareto chart.

[0088] For example, when the operator places the pointer or cursor over the bar graph for "Alarm 1" in area R13 and clicks (single clicks), the content of the alarm type "Alarm 1" and the number of occurrences in the past 24 hours "508 occurrences" are displayed, as shown in Figure 5.

[0089] Furthermore, when the operator places the pointer or cursor on the bar graph of "alarm 1" displayed in region R13 and double-clicks it, the dashboard display screen DP1 transitions to the occurrence history display screen DP2.

[0090] The occurrence frequency in the first period for each alarm type is not limited to the display example shown in Fig. 5. The occurrence frequency in the first period for each alarm type may be displayed in other formats as long as the alarms are arranged by alarm type. The occurrence frequency in the first period for each alarm type may be displayed in a graph format, such as a line graph, a stacked graph, or a bar graph.

[0091] Next, an example of the occurrence history display screen DP2 will be described with reference to Fig. 6. The occurrence history display screen DP2 includes areas R20 to R22.

[0092] Area R20 displays "Occurrence Date and Time", "Display Method", "Item", "Alarm Type", "Maximum Number of Items to Display", and "Search". "Occurrence Date and Time" included in area R20 can be double-clicked by the operator to input the start and end points of the second period for displaying the occurrence history of the selected alarm type. For example, if the first period for the occurrence frequency of each alarm type shown in FIG. 5 is the past 24 hours, the start and end points of the second period can be input within the past 24 hours.

[0093] The "Display method" included in area R20 can be selected from either "List" or "Graph". When "List" is selected in the "Display method", either "ALL", "Evaluation item", or "DCS" can be selected in the "Alarm type" included in area R20. On the other hand, when "Graph" is selected in the "Display method", related events related to the selected alarm type can be selected in the "Item" included in area R20. For example, a maximum of five related events (five items) can be selected. In the example shown in FIG. 6, "Graph" is selected in the "Display method", and two related events (two items) are selected in the "Item".

[0094] The "Maximum number of items to display" included in area R20 allows the input of a numerical value, and when the "Search" display included in area R20 is selected (pressed), occurrence history information of the alarm type selected on the dashboard display screen DP1 and occurrence history information of the related event selected in the "Item" included in area R20 from the start to the end of the entered second period are displayed in area R22.

[0095] In the area R21, "occurrence date and time", "correct / incorrect judgment", and "update" are displayed. The "occurrence date and time" included in the area R21 is the start and end points of the occurrence date and time input in the area R20. The "correct / incorrect judgment" included in the area R21 can be selected and input as either "correct" or "incorrect". In other words, the "correct / incorrect judgment" in the area R21 is configured to allow input of the correctness of the occurrence of the alarm type selected on the dashboard display screen DP1. This allows, for example, the operator to input and register the correctness of the occurrence of the alarm type judged by looking at a graph described later in the system 30 or the monitoring device 40. When the "update" display included in the area R21 is selected (pressed), the occurrence history information of the alarm type and the occurrence history information of the related event displayed in the area R22 are updated to the latest state.

[0096] Area R22 displays occurrence history information for the alarm type during the second period. In this way, by displaying occurrence history information for the second period for the alarm type selected on the dashboard display screen DP1, it is possible to grasp, for example, occurrence intervals, occurrence density, occurrence timing, etc., for the alarm type during the second period.

[0097] More specifically, based on the occurrence history information of the alarm type during the second period, the occurrence of the alarm type is displayed in a graph format arranged in chronological order. In the example shown in Fig. 6, the alarm type is displayed in a graph in which the horizontal axis represents time and each occurrence is plotted (drawn) in chronological order. In this way, for the alarm type selected on the dashboard display screen DP1, by displaying the occurrence of the alarm type in a graph format arranged in chronological order based on the occurrence history information during the second period, it is possible to easily grasp, for example, the occurrence interval, occurrence density, occurrence timing, etc., of the alarm type during the second period.

[0098] Moreover, area R22 also displays occurrence history information of related events during a second period. In this way, by displaying occurrence history information of related events during a second period together with occurrence history information of the alarm type selected on dashboard display screen DP1 during a second period, it is possible to grasp, for example, the causal relationship between the alarm type and the related event, the operating state of the plant when the alarm type occurred, and the like.

[0099] More specifically, the occurrences of the alarm type are arranged in chronological order based on the occurrence history information of the alarm type during the second period, and the occurrences of the related events are arranged in chronological order based on the occurrence history information of the related events during the second period. In the example shown in FIG. 6, the alarm type and the related events are displayed in a graph in which the horizontal axis is time and each occurrence is plotted (drawn) in chronological order. Here, when the alarm type plotted with a white circle is, for example, an "alarm indicating that the nitrogen oxide concentration in the exhaust gas has exceeded a predetermined value," if an "alarm indicating that the oxygen concentration in the exhaust gas has fallen below a predetermined value" is selected as the related event plotted with a black square, the occurrence history information of the alarm type during the second period and the occurrence history information of the related events during the second period are displayed in a graph format arranged in chronological order in the region R22, and it can be seen that there is a causal relationship between the two. In this way, by displaying in a graph format in which the occurrences of an alarm type selected on the dashboard display screen DP1 are arranged in chronological order based on the occurrence history information of the alarm type over a second period, and the occurrences of related events are arranged in chronological order based on the occurrence history information of the related events over a second period, it is possible to easily grasp, for example, the causal relationship between the alarm type and the related event, the operating state of the plant at the time of the occurrence of the alarm type, etc.

[0100] As described above, the related event related to the alarm type is a process in the plant 1, or an alarm type different from the alarm type whose occurrence frequency in the first period is displayed on the dashboard display screen DP1. This makes it easy to understand the causal relationship between the alarm type selected on the dashboard display screen DP1 and other alarms or processes, the occurrence status of other alarms or processes at the time of occurrence of the alarm type, etc.

[0101] Next, the flow of processing by the system 30 according to this embodiment will be described with reference to the flowchart in Fig. 7. This flowchart particularly shows the flow of processing for displaying information related to an alarm that has occurred in the plant 1. This processing is executed under the control of the control unit 31. Note that the contents and order of the steps shown below are merely examples, and the operation processing is not limited to these.

[0102] In the following description, it is assumed that the plant 1 is in operation, the acquisition unit 311 acquires process data of the plant 1 via the DCS 20 and stores it in the process information DB 33A, and acquires alarm information (DCS alarm information) generated as a result of the DCS 20 determining whether or not there is an abnormality in the plant 1 and stores it in the alarm information DB 33B. It is also assumed that alarm information (system alarm information) generated as a result of the system 30 determining whether or not there is an abnormality in the plant 1 is also stored in the alarm information DB 33B.

[0103] The calculation unit 312 determines whether or not a predetermined time has elapsed (S11). Here, the length of the predetermined time is not particularly limited, and may be, for example, in units of seconds, such as 1 second, 5 seconds, 10 seconds, or 30 seconds, or in units of minutes, such as 1 minute or 2 minutes. However, it is preferable that the length of the predetermined period is shorter, since this improves the real-time nature of the information displayed on the dashboard display screen DP1. The length of the predetermined time may be arbitrarily set by an operator or the like. The calculation unit 312 repeats step S11 until it is determined that the predetermined time has elapsed.

[0104] If it is determined that the predetermined period has elapsed (S11; Yes), the calculation unit 312 calculates the occurrence frequency during the first period for each alarm type based on the alarm information stored in the alarm information DB 33B (S12).

[0105] Next, the display control unit 315 displays the occurrence frequency for each alarm type in the first period calculated by the calculation unit 312 in an arrangement by alarm type in an area R13 of the dashboard display screen DP1 (S13). For example, as shown in Fig. 5, the display control unit 315 displays a bar graph with a length corresponding to the occurrence frequency for each alarm type, arranged in descending or ascending order of occurrence frequency.

[0106] Next, the generation unit 313 determines whether or not one of the multiple alarm types displayed in area R13 of the dashboard display screen DP1 has been selected (S14). As described above, the operator can select an alarm type, for example, by bringing the pointer or cursor to one of the bar graphs for each alarm type displayed in area R13 and double-clicking. The generation unit 313 repeats step S14 until it determines that one of the multiple alarm types has been selected.

[0107] When it is determined that one of the multiple alarm types has been selected (S14; Yes), if the operator has selected a related event, the reception unit 314 receives the selection (S15). For example, the display control unit 315 displays the occurrence history display screen DP2, and the reception unit 314 receives the selection of a related event related to the alarm type selected in step S14 in response to the operator's operation on the area R20 of the occurrence history display screen DP2.

[0108] Next, the generation unit 313 generates occurrence history information indicating the occurrence history during the second period for the alarm type selected in step S14 based on the alarm information stored in the alarm information DB33B, and also generates occurrence history information indicating the occurrence history during the second period for the related event whose selection was accepted in step S15 based on the process information stored in the process information DB33A or the alarm information stored in the alarm information DB33B (S16).

[0109] Next, the display control unit 315 displays the occurrence history information for the second period of the alarm type and the occurrence history information for the second period of the related event, which were generated in step S15, in the area R22 of the occurrence history display screen DP2 (S17). Note that the display of the occurrence history information for the second period of the alarm type and the occurrence history information for the second period of the related event may be in the graph format shown in Fig. 6 or in a list format. This ends the processing.

[0110] As described above, according to the present embodiment, the occurrence frequency of each alarm type in the first period is displayed in a manner arranged by alarm type. This makes it possible to visualize the occurrence frequency of each alarm type in the first period. Therefore, by understanding the occurrence frequency of an alarm, rather than simply whether or not an alarm has occurred, it is possible to prevent, for example, a malfunction that gradually develops over a certain period of time.

[0111] The embodiments described in the above embodiments can be combined or modified or improved as appropriate depending on the application, and the present invention is not limited to the above-mentioned embodiments. It is clear from the claims that such combinations, modifications, or improvements are also included in the technical scope of the present invention. [Explanation of symbols]

[0112] 1...plant, 2...furnace, 2a...fuel supply port, 2b...gas outlet, 2c...air supply line, 2d...exhaust port, 3...cyclone, 3a...exhaust gas flow path, 4...circulating material recovery pipe, 4a...loop seal section, 5...rear flue, 6...furnace wall tube, 7...pump, 7a...pump, 8...steam drum, 8a...downcomer, 8b...saturated steam pipe, 10...superheater, 10a...tube, 12...econservator, 13...area, 21...tube, 22...tube, 30...system, 30a...CPU, 30d...communication section, 30e...input section, 30f...display section, 31...control section, 32...display device, 100...turbine, 102...condenser, 311...acquisition section, 312...calculation section, 313...generation section, 314...reception section, 315...display control section.

Claims

1. A display device that displays an operating state of a plant, displaying, for a plurality of alarms that have occurred in the plant, the occurrence frequency during a first period for each alarm type indicating the type of the alarm in a manner arranged for each alarm type, and displaying, in a chronological order, a predetermined state of process data that affects real-time operation efficiency and an index of efficiency related to operation of the plant; Display device.

2. Displaying the occurrence frequency of each alarm type during the first period in a manner arranged for each alarm type includes displaying the occurrence frequency of each alarm type during the first period in a graph format. The display device according to claim 1 .

3. Displaying the occurrence frequency of each alarm type during the first period in a manner arranged for each alarm type means displaying a bar graph corresponding to the occurrence frequency of each alarm type during the first period arranged in descending or ascending order of occurrence frequency for each alarm type. The display device according to claim 2 .

4. for the alarm type whose occurrence frequency during the first period is displayed, further displaying an occurrence history of the alarm type during a second period included in the first period; The display device according to claim 1 .

5. and further displaying, together with the occurrence history of the alarm type during the second period, an occurrence history of a related event related to the alarm type during the second period. The display device according to claim 4.

6. The related event is a process of the plant, or the alarm type whose occurrence frequency in the first period is different from the alarm type displayed, The display device according to claim 5 .

7. The first period is a part of an operation period of the plant. The display device according to claim 1 .

8. The occurrence frequency is the number of occurrences. The display device according to claim 1 .

9. A control device that controls a display device that displays an operating state of a plant, an acquisition unit that acquires alarm information indicating an alarm occurring in the plant; a calculation unit that calculates an occurrence frequency for each alarm type indicating a type of the alarm in a first period based on the alarm information; a display control unit that causes the display device to display the calculated occurrence frequencies for each of the alarm types in the first period in a manner arranged for each of the alarm types, and also causes the display device to display a predetermined state of process data that affects real-time operation efficiency and an efficiency index related to the operation of the plant in chronological order. Control device.

10. a generating unit that generates, based on the alarm information, occurrence history information indicating an occurrence history of the alarm type during a second period included in the first period, for the alarm type whose occurrence frequency during the first period is displayed; The display control unit causes the display device to further display the generated occurrence history information for the second period. The control device according to claim 9.

11. the display control unit further causes the display device to display, based on the generated occurrence history information for the second period, occurrences of the alarm types in a graph format arranged in chronological order. The control device according to claim 10.

12. a reception unit that receives a selection of a related event related to the alarm type for which the occurrence frequency for the first period is displayed, the generation unit generates occurrence history information indicating an occurrence history of the selected related event during the second period based on process information of the plant or the alarm information; the display control unit causes the display device to display the occurrence history information for the second period of the generated alarm type and the occurrence history information for the second period of the generated associated event. The control device according to claim 10 or 11.

13. the display control unit causes the display device to arrange occurrences of the alarm type in chronological order based on the generated occurrence history information for the second period of the alarm type, and to further display in a graph format the occurrences of the associated event arranged in chronological order based on the generated occurrence history information for the second period of the associated event. The control device according to claim 12.

14. a right / wrong input unit configured to be able to input right / wrong about the occurrence of the alarm type for which the occurrence frequency in the first period is displayed, The control device according to claim 13.

15. A control method for controlling a display device that displays an operating state of a plant, comprising: acquiring alarm information indicating an alarm occurring in the plant; calculating an occurrence frequency during a first period for each alarm type indicating a type of the alarm based on the alarm information; and displaying, on the display device, the calculated occurrence frequencies for each of the alarm types during the first period in a manner arranged for each of the alarm types, and displaying, in chronological order, a predetermined state of process data that affects real-time operation efficiency and an index of efficiency related to operation of the plant. Control methods.

16. A program for causing a computer to execute the program to control a display device that displays an operating state of a plant, acquiring alarm information indicating an alarm occurring in the plant; calculating an occurrence frequency during a first period for each alarm type indicating a type of the alarm based on the alarm information; and displaying, on the display device, the calculated occurrence frequencies for each of the alarm types during the first period in a manner arranged for each of the alarm types, and displaying, in chronological order, a predetermined state of process data that affects real-time operation efficiency and an index of efficiency related to operation of the plant. program.

Images