JP5036754B2 - Plant monitoring device - Google Patents

Description

  The present invention relates to a plant monitoring device, and in particular, in an industrial plant such as an industrial plant where a large number of devices such as pumps and valves and sensors such as flow meters and pressure gauges are arranged, the operation data detected by the sensors is displayed by the operator. It is related to the case where the state of the plant is immediately grasped by monitoring and stable operation is performed.

  The plant is composed of a plurality of facilities, and each facility is provided with a large number of sensors such as operating devices such as pumps and valves, pressure gauges and flow meters. In order to monitor the plant, the signals of these devices are assigned to symbols displayed on GUI (Graphic User Interface) screens such as system diagrams and equipment configuration diagrams, and the current values are monitored, or displayed in a message or graphic format. The operator was operating while confirming information on the failure that occurred in the equipment.

  In this situation, it is becoming difficult for one operator to learn the contents of many signals, and it is difficult to immediately identify which part is abnormal from the alarm. For example, Patent Document 1 discloses a method of managing the configuration and easily displaying related signals.

  In the method disclosed in Patent Document 1, in order to reduce the burden on the operator and facilitate the operation, a plurality of structure tags constituting the plant are divided into a hierarchical structure, The structure tag of the hierarchy and the structure tag belonging to the lower hierarchy are stored respectively. Therefore, even if the tag name is not remembered, it is the target when the related structure tag is sequentially traced from the upper hierarchy to the lower hierarchy. You can get to the structure tag. In addition, information related to the stored element tag can be switched and displayed according to the mode.

JP-A-4-347798

  However, if the structure of the plant changes due to renovation or expansion, when the database needs to be updated, which part can be changed because the number of signals is large and items are mutually referenced Judgment may be difficult. That is, there is a first problem that it is difficult to update the database when the plant is expanded or renovated.

  Plants are continuously expanded and refurbished due to equipment failure and longevity. In such a case, the database storing operation data and facility management data must be updated. When there are many devices handled at this time, the data stored in the database becomes complicated, and therefore the first problem is that correction is often difficult unless the data structure is sufficiently known. .

  In addition, since the equipment included in the plant is enormous, there are many signals and alarms that must be monitored, and it is difficult to immediately understand what kind of operating conditions it is. That is, when there are many signals handled in plant management, there is a second problem that it is difficult to understand the operation state.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a plant monitoring apparatus that simplifies updating of a database accompanying plant expansion or modification. Furthermore, it aims at obtaining the plant monitoring apparatus which is easy to grasp | ascertain the operating condition of a plant.

The plant monitoring device according to claim 1 according to the present invention is a plant monitoring device that monitors a plant including a plurality of plant elements, and the plurality of plant elements have a hierarchical structure including a predetermined number of hierarchical levels. A plant element configuration table storage means for storing a plant element configuration table that defines the relationship between the plurality of plant elements, wherein the plant element configuration table is associated with each of the plurality of plant elements and indicates an element ID And a signal definition table storage for storing a signal definition table in which a plurality of plant monitoring target signals generated in any one of the plurality of plant elements are associated with a host element ID indicating a host plant element including itself. further comprising means, the signal definition table in association with each of the plurality of signals, And element ID shows the body, and associates the device ID indicating the plant element itself is Zui associated one of the plurality of plants elements, driving condition monitoring means for monitoring the operating conditions based on a change in the plurality of signals And an analysis unit that displays an analysis result on a predetermined display unit so as to be visually recognizable based on the operation state, and the analysis unit indicates a plant element desired to be analyzed for the plurality of plant elements. An analysis target element can be selected, and includes an aggregation / detailing means for displaying an analysis result on the predetermined display unit at an analysis level based on the analysis target element, provided corresponding to the plurality of signals, Analysis signal identification information storage means for storing analysis signal identification information defining at least signal types and calculation types for the plurality of signals for obtaining the analysis results; A calculation means for obtaining a calculation result for analysis by performing calculation processing based on the driving situation with reference to the signal identification information for analysis, and the analysis unit obtains the analysis result based on the calculation result for analysis, The operating status monitoring means generates operating status monitoring data for operating status monitoring based on changes in the plurality of signals, and the analysis signal identification information storage means is provided corresponding to the plurality of plant elements. A plurality of analysis signal identification information buffer areas, wherein each of the plurality of analysis signal identification information buffer areas can temporarily store the analysis calculation results in association with the analysis signal identification information; And when the driving condition monitoring data is generated by the driving condition monitoring means, the calculating means performs calculation processing in conjunction with the driving condition monitoring means to obtain the calculation result for analysis. The analysis signal identification information buffer area is temporarily stored.

  According to a first aspect of the present invention, there is provided the plant monitoring apparatus according to claim 1, wherein each of the plurality of plant monitoring target signals generated in any one of the plurality of plant elements and the plurality of plant elements constituting the plant by the plant element configuration table and the signal definition table, respectively. Since the element ID indicating itself and the upper element ID indicating the upper plant element including itself are associated with each other, the hierarchical structure of the entire plant including a plurality of plant elements and a plurality of signals can be centrally managed by the element ID. Can do.

  As a result, there is an effect that it is possible to simplify the update of the database including the plant element configuration table and the signal definition table that accompanies the expansion or modification of the plant. In particular, the degree of effect is large when there is no change in the hierarchical structure between plant elements.

It is a block diagram which shows the structure of the plant monitoring apparatus which is Embodiment 1 of this invention. It is explanatory drawing which shows the internal structure of the database shown in FIG. It is a block diagram which shows the hardware structural example of the computer which can implement | achieve the plant monitoring apparatus of Embodiment 1 shown in FIG. It is explanatory drawing which shows an example of the apparatus ledger shown in FIG. 2 in a table format. It is explanatory drawing which shows an example of the equipment structure table shown in FIG. 2 in a table format. It is explanatory drawing which represented the classification structure based on the equipment structure table shown in FIG. It is explanatory drawing which shows an example of the trend table shown in FIG. It is explanatory drawing which shows an example of the event table shown in FIG. It is explanatory drawing which shows an example of the signal definition table shown in FIG. 2 in a table format. 4 is a flowchart illustrating a monitoring operation of the plant monitoring apparatus according to the first embodiment. It is explanatory drawing which shows the example of a definition of the plant component element information by the plant element configuration definition means shown in FIG. It is a block diagram which shows the structure of the plant monitoring apparatus which is Embodiment 2 of this invention. FIG. 13 is an explanatory diagram showing an example of an asset tag definition list shown in FIG. 12 in a table format. 13 is a flowchart showing an analysis operation (aggregation / detailing operation) by the aggregation / detailing means shown in FIG. It is explanatory drawing which shows the example of aggregation / detailing by the aggregation / detailing means in the case of the equipment configuration table shown in FIG. 5 and the asset tag definition list shown in FIG. It is a block diagram which shows the structure of the plant monitoring apparatus which is Embodiment 3 of this invention. It is explanatory drawing which shows the asset tag content provided corresponding to one apparatus in the asset tag buffer shown in FIG. 16 in a table format.

<Embodiment 1>
(overall structure)
1 is a block diagram showing a configuration of a plant monitoring apparatus according to Embodiment 1 of the present invention.

  The plant monitoring apparatus according to the first embodiment includes an input unit 14, a display unit 15, and a plant monitoring unit 21. The plant monitoring unit 21 includes an engineering tool 30A, a server 40A, and a database 50A. The input unit 14 is connected to the plant monitoring unit 21 so that data can be input by an operator, and the display unit 15 displays the output result from the plant monitoring unit 21 in a graphic or text format.

  The engineer tool 30 is connected to the database 50 </ b> A, and includes a plant element configuration definition unit 31, a signal definition unit 32, and an equipment ledger management unit 33.

  The plant element configuration defining means 31 defines what kind of equipment is present and what kind of equipment is included in the equipment according to the plant processing process. The signal definition means 32 defines the signal handled in the plant and the equipment and equipment related to the signal. The device ledger management means 33 records information related to the device delivered to the plant or the repaired device. In addition, the server 40A includes a data collection unit 41 and an event creation unit 42 which are operation status monitoring units.

  FIG. 2 is an explanatory diagram showing the internal configuration of the database 50A shown in FIG. As shown in the figure, in the database 50A, a device ledger 51 that records device ledger information, a plant element configuration table 52 that records plant element configuration information, a signal definition table 53 that records signal definition information, and a server 40A collect A trend table 54 in which the operation data recorded in time series and an event table 55 in which alarms created by the server 40A are recorded in time series are stored.

  Therefore, the database 50A functions as a storage unit for the device ledger 51, the plant element configuration table 52, the plant element configuration table 52, the trend table 54, and the event table 55. Information of the table (ledger) recorded in the database 50A can be displayed by the display unit 15.

  The plant element configuration defining unit 31, the signal defining unit 32, and the equipment ledger managing unit 33 in the engineering tool 30A mainly function as a user interface of the input unit 14 when the operator operates the input unit 14.

  The plant element configuration defining means 31 records plant element configuration information indicating what device configuration the plant input from the input unit 14 has in the plant element configuration table 52 in the database 50A. The device ledger management means 33 records device ledger information, which is a record of device delivery, inspection, failure, carry-out, etc., input from the input unit 14, in the device ledger 51 in the database 50A. The signal definition means 32 records signal definition information indicating attributes of signals used in the plant input from the input unit 14 in the signal definition table 53 in the database 50A.

  The server 40A is connected to the database 50A, collects operation data (values of a plurality of signals to be monitored by the plant) from the plant, and creates an alarm. Specifically, the following processing is performed. The data collection means 41 in the server 40A stores the operation data periodically collected from the plant in the trend table 54 together with related element IDs. The event creation means 42 in the server 40A generates an event when the operation data collected by the data collection means 41 satisfies the conditions for generating an alarm included in the signal definition table 53, and relates to the event. Together with the element ID of the device to be stored in the event table 55.

  The point that the server 40A can collect the operation data from the plant will be described below. A sensor and a machine are installed in the plant, and a signal to be monitored for the plant related to these devices (sensor, machine) is connected to a controller. The controller stores the signal of the connected device in the memory. The controller is connected to a network called a control network, and a server 40A is also connected to this control network. Therefore, the server 40A has a dedicated I / F card for each control network, and can refer to data on a memory stored in a controller connected to the network. In this way, the server 40A can collect operation data from the plant by referring to the signal values of the plant equipment via the control network and storing them in a predetermined memory in the server 40A.

(Realization by computer)
FIG. 3 is a block diagram showing a hardware configuration example of a computer that can be realized by the plant monitoring apparatus according to the first embodiment shown in FIG. As shown in the figure, the computer includes a CPU 1, a hard disk 2, a memory 3, a keyboard 4, and a display 5 that are commonly connected to a shared bus 28. In the hard disk 2, a plant monitoring unit program 21 P and an OS 27 are stored. Stored.

  The keyboard 4 and the display 5 correspond to the input unit 14 and the display unit 15 in the plant monitoring apparatus of the first embodiment. Further, the engineering tool 30A and the server 40A of the plant monitoring unit 21 are realized by the CPU 1 executing the plant monitoring unit program 21P stored in the hard disk 2 on the OS 27. The database 50A is realized by securing an area for the database 50A in the hard disk 2.

(Equipment ledger 51)
FIG. 4 is an explanatory diagram showing an example of the device ledger 51 shown in FIG. 2 in a table format. As shown in the figure, the device ledger 51 stores information on devices constituting the plant, and includes an element ID, a processing type, an implementation date, a serial number, a model name, a model name, a manufacturer name, and the like. Here, processing types include delivery, repair, and carry-out.

(Plant element configuration table 52)
FIG. 5 is an explanatory diagram showing an example of the plant element configuration table 52 shown in FIG. 2 in a table format. As shown in the figure, the plant element configuration table 52 is information indicating the equipment constituting the equipment and the equipment configuration, etc., and identifying the constituent ID and the higher-order constituent elements including the elements. The upper element ID and the name of the element are included. In the plant element configuration table 52 shown in FIG. 5, as the plant elements constituting the plant, the municipality level C1 for classification of the municipality level that manages the plant, and for the classification of the machine level (treatment plant, water treatment plant) level managed by the municipality There is a facility classification C3 for facility level classification that is included in a machinery field such as a water purification plant and classified according to the treatment process. In addition, it has equipment classification C4 for classifying equipment levels included in each facility, and equipment classification C for classifying equipment levels that constitute equipment, and classifies elements at a total of five hierarchical levels. is doing.

  For example, as facility classification C3 in “A City D River Water Treatment Plant” (element ID: 01000), there are four types of “sedimentation”, “first sedimentation basin”, “reaction tank”, and “final sedimentation basin” for each treatment process. are categorized. Furthermore, each item of the facility classification C3 is classified as the facility classification C4 for each function. For example, in the facility classification C3 “sedimentation basin” (element ID: 00100), the facility classification C3 is classified into three facility classifications C4 consisting of “sediment removal”, “scum treatment”, and “sedimentation removal”. Since one function at the equipment classification C4 level is realized by a plurality of equipment at the equipment classification C5 level, a plurality of equipment belongs to one equipment.

  For example, “sludge pump” with element ID: 00001 classified in equipment class C5 is equipment that constitutes “sludge extraction” equipment (equipment classification C4) with high-order element ID: 000A0, and “sludge extraction” equipment is a high-order element. It exists in the “final sedimentation basin” facility (facility classification C3) with ID: 00400, and the “final sedimentation pond” facility is included in the “A city D river water purification plant” machine station (machine classification C2) with the upper element ID: 01000 Means that.

  FIG. 6 is an explanatory diagram schematically showing the classification configuration based on the plant element configuration table 52 shown in FIG. As shown in the figure, according to the municipality classification C1, it is classified into “A city” corresponding to the municipality classification C1A, “B city” corresponding to the municipality classification C1B, and the like.

  Furthermore, “A city” is classified into “A city D river water purification plant” of machine field classification C2A1, “A city E river water purification plant” of machine field classification C2A2, and the like by machine field classification C2.

  Then, according to the facility classification C3, the “A city D river water purification plant” has the facility classification C3A1 “sedimentation basin”, the facility classification C3A2 “first sedimentation basin”, the facility classification C3A3 “reaction tank”, and the facility classification C3A4. Classified as “Final Settlement”.

  Further, according to the equipment classification C4, the “sedimentation basin” is classified into “sediment carry-out” of the equipment classification C4A11, “scum treatment” of the equipment classification C4A12, and “sedimentation carry-out” of the equipment classification C4A13.

  Similarly, by the equipment classification C4, the “first sand basin” is classified into “sludge extraction” of the equipment classification C4A21 and “scum treatment” of the equipment classification C4A22.

  Similarly, according to the equipment classification C4, the “reaction tank” is “sewage adjustment” in the equipment classification C4A31, “blower” in the equipment classification C4A32, “tank aeration” in the equipment classification C4A33, and “air flow control” in the equipment classification C4A34. are categorized.

  Similarly, by the equipment classification C4, the “final sedimentation basin” is classified into “sludge extraction” of the equipment classification C4A41, “scum treatment” of the equipment classification C4A42, and “deodorization” of the equipment classification C4A44.

  Furthermore, “sludge extraction” is classified into “sludge pump” in equipment classification C5A211 and “sludge extraction valve” in equipment classification C4A212 by the equipment classification C5.

  In addition, each name in the municipality classification C1-equipment classification C5 shown in FIG.5 and FIG.6 is used as a general term, and at least by referring to "the sewer glossary" etc. published by Japan Sewerage Association Since it is a term that can be easily recognized, explanation of the meaning of each term is omitted.

(Trend table 54)
FIG. 7 is an explanatory diagram showing an example of the trend table 54 stored in the database 50A shown in FIG. 2 in a table format. As shown in the figure, the trend table 54, which is operation status monitoring data, records operation data (values) of signals to be monitored in time series, and includes element IDs for identifying signals, collection times, and operations. Contains data (values).

(Event table 55)
FIG. 8 is an explanatory diagram showing an example of the event table 55 stored in the database 50A shown in FIG. As shown in the figure, the event table 55, which is data for monitoring operating conditions, includes element IDs of devices, facilities, and signals related to events (failures, abnormalities, etc.), occurrence times, event names, and values (event occurrences). Etc.).

(Signal definition table 53)
FIG. 9 is an explanatory diagram showing an example of the signal definition table 53 stored in the database 50A shown in FIG. 2 in a table format. As shown in the figure, signal definition table 53 identifies the signal (signal) component ID, tag name used to refer to the signals, related equipment and facilities (signal high) element ID (device ID) , signal name, occurrence name which is a name indicating that the signal value is ON, recovery name which is a name indicating the state when the signal value is OFF, and upper limit value and lower limit value which are alarm generation conditions And units.

(Operation)
FIG. 10 is a flowchart showing the monitoring operation of the plant monitoring apparatus according to the first embodiment. In this flowchart, the transfer status of the device ledger 51, the plant element configuration table 52, the signal definition table 53, the trend table 54, and the event table 55 is schematically shown. Hereinafter, the process procedure of the plant monitoring operation of the first embodiment will be described with reference to FIG.

  First, in step S1, the device ledger management means 33 in the engineering tool 30A records the device ledger information obtained based on the information input by the input unit 14 in the device ledger 51 in the database 50A.

  Next, in step S2, the plant element configuration defining means 31 in the engineering tool 30A stores the plant component information obtained based on the information input by the input unit 14 in the plant element configuration table 52 in the database 50A. .

  FIG. 11 is an explanatory diagram showing a definition example of plant component information by the plant component configuration defining means 31 shown in FIG. As shown in the figure, the plant component information may be defined graphically using a tree view or the like. When an element is newly added under the tree structure, a new element ID is generated for the new element by the plant element configuration defining means 31, and the element ID of the element at the upper part of the part where the new element is specified is set as the upper element ID. Plant component information to be registered is registered in the plant component configuration table 52.

  For example, in FIG. 11, “element ID: 1021” of “final sludge extraction” of equipment classification C4 is taken up. Here, if a new device: “No. 4 sludge pump” is added to the “final sludge extraction” facility, an element ID is newly added to this pump (ID: 1031), and 1 is added to the plant element configuration table 52. A line entry is added. “Element ID: 1021” 1021 of “final sludge extraction” is registered in the upper element of this entry.

  Returning to FIG. 10, after that, in step S <b> 3, signal definition information handled in the plant obtained based on the information input by the input unit 14 is stored in the signal definition table 53 in the database 50 </ b> A.

  By executing the processes in steps S1 to S3 described above, necessary information is recorded in the device ledger 51, the plant element configuration table 52, and the signal definition table 53 in the database 50A.

  In step S4, the data collection means 41 of the server 40A collects operation data (signals of devices such as sensors) from facilities and devices.

  Subsequently, in step S5, the signal collected in step S4 is searched and specified from the signal definition table 53. Further, after searching for the element ID corresponding to the specified signal, the element ID, the signal collection time and the signal value are obtained. Record in the trend table 54.

  Thereafter, in step S6, the event creating means 42 refers to the signal definition table 53, determines whether or not the event can be generated from the operation data collected in step S4, and if the condition for generating the event is satisfied, the event is generated. The generated event is stored in the event table 55 in the database 50A.

  Event recording at the time of event generation is performed using limit values (upper limit value, lower limit value) and attribute names (occurrence names) in the signal definition table 53. For example, if the collected signal value is “70” and the upper limit value of the signal shown in the signal definition table 53 is “50”, an event of an upper limit value abnormality is generated. If the occurrence name is “failure”, an event indicating “failure” is generated when the corresponding signal is turned ON. The generated event is stored in the event table 55 together with the element ID and generation time of the related signal acquired in step S5.

  Thereafter, in step S7, after waiting until the time for obtaining the next operation data, the process returns to step S4 again. Thereafter, as long as the plant monitoring state is continued, steps S4 to S7 are repeatedly executed.

  Hereinafter, the processes of steps S4 to S6 will be described with specific examples. In the plant, a signal name called a tag is attached to the device signal (see FIG. 9). An example of the tag is “002 / AI003”, which means “means the third signal of the terminal using the analog signal in the second controller”. In the plant, when a tag number is obtained, a memory in which the server 40A collects data is determined in advance. In addition, the element ID associated with the tag name is stored in the signal definition table 53.

  Therefore, when the server 40A collects the operation data (device signal) from the plant in step S4, the tag name can be recognized from the collected memory address. When the tag name is known, the signal definition table 53 is referred to. Thus, the element ID of the signal can be recognized.

  Accordingly, since the limit value is also described in the signal definition table 53, in step S6, for example, when the upper limit value is “100”, if the collected value is “110”, an event such as an upper limit error is generated. be able to.

(Update of database 50A)
The database 50A is updated when plant expansion or refurbishment occurs. When a device is added, the device is added to the device ledger 51 by the device ledger management means 33 of the engineering tool 30 based on information obtained from the input unit 14.

  Then, based on the information obtained from the input unit 14, the plant element configuration defining unit 31 defines the plant element configuration for the added equipment, updates the plant component element information, and records it in the plant element configuration table 52. Furthermore, based on information obtained from the input unit 14, the signal definition unit 32 updates the signal of the added device and adds it to the signal definition table 53.

  On the other hand, when a device is deleted, the device is deleted from the device ledger 51 by the device ledger management means 33 of the engineering tool 30 based on information obtained from the input unit 14. Thereafter, the plant element configuration defining unit 31 and the signal defining unit 32 search for the element ID of the deleted device from the plant element configuration table 52 and the signal definition table 532, and automatically delete the contents of only the corresponding part of each table. To do.

  When the device is moved or exchanged and the tag name or attribute is changed, the device ledger management means 33 of the engineering tool 30 records the change contents of the corresponding device in the device ledger 51 based on the information obtained from the input unit 14. Based on the information obtained from the input unit 14, the tag name and the like in the signal definition table 53 are updated by the signal definition means 32 of the engineering tool 30.

  As described above, the plant monitoring apparatus according to the first embodiment sets an element ID for a plant component that does not physically change such as a signal and a device, and associates the plant configuration with a hierarchical structure between the municipality classification C1 to the equipment classification C5. Element information is centrally managed by element ID in the plant element configuration table 52. For this reason, as long as the hierarchical structure itself constituting the plant does not change, only a relatively simple update process of the device ledger 51 and the signal definition table 53 can be performed, so that the database can be easily updated.

  As described above, the plant monitoring apparatus according to the first embodiment uses the plant element configuration table 52 and the signal definition table 53 to identify the plant monitoring target that is generated in any one of the plurality of plant elements and the plurality of plant elements that constitute the plant. For each of a plurality of signals, an element ID indicating itself is associated with an upper element ID indicating an upper component including itself. For this reason, the hierarchical structure of the whole plant consisting of a plurality of plan elements and a plurality of signals can be centrally managed by the element ID.

  As a result, particularly in the case where there is no change in the hierarchical structure between plant elements, it is possible to simplify the update of the database including the plant element configuration table 52 and the signal definition table 53 that accompanies the addition or modification of the plant.

<Embodiment 2>
In the first embodiment, the plant elements constituting the plant can be centrally managed by the element ID. In addition to the functions of the first embodiment, the plant monitoring apparatus of the second embodiment is characterized by further comprising means for analyzing the operation data of the centrally managed plant.

  FIG. 12 is a block diagram showing the configuration of a plant monitoring apparatus according to Embodiment 2 of the present invention. In FIG. 12, the same components as those shown in the first embodiment are denoted by the same reference numerals, and description thereof will be omitted as appropriate. Note that the second embodiment can be realized by using the computer having the hardware configuration shown in FIG. 3 as in the first embodiment.

  The plant monitoring apparatus according to the second embodiment includes an input unit 14, a display unit 15, and a plant monitoring unit 22. The plant monitoring unit 22 includes an engineering tool 30B, a server 40B, a database 50B, and an analysis unit 60.

  The engineering tool 30B has asset tag defining means 34A in addition to the configuration of the engineering tool 30A of the first embodiment. The server 40B further includes a calculation unit 43 in addition to the configuration of the server 40A of the first embodiment.

  The database 50B has an asset tag definition list 56 in addition to the contents of the database 50A shown in FIG. Therefore, the database 50B functions as a storage unit (analysis signal identification information storage unit) of the asset tag definition list 56. Also, the newly added analysis unit 60 has aggregation / detailing means 61 inside. As will be described in detail later, the asset tag definition list 56 is provided corresponding to at least one plant monitoring target signal, and is an analysis signal identification that defines at least a calculation type for the at least one signal for obtaining an analysis result. Store information.

  The asset tag definition unit 34A of the engineering tool 30B defines an asset tag based on information input from the input unit 14 and records it in the asset tag definition list 56 in the database 50B.

  FIG. 13 is an explanatory diagram showing an example of the asset tag definition list 56 shown in FIG. 12 in a table format. The asset tag in the asset tag definition list 56 means a unit of aggregation that can be defined in units of equipment or devices. The asset tag definition list 56 describes the definition of signals (data) to be aggregated, and is one for the entire plant. The asset tag definition list 56 is set.

  One unit of asset tag is item No. , Comprising a set of calculation type and signal type. For example, in item 1, an asset for obtaining “average” specified by the calculation type for a signal whose signal type is “current value” is defined. Item 2 defines that “average” specified by the calculation type is obtained for a signal whose signal type is “current value”. Hereinafter, this point will be described in detail.

  For example, regarding the element of “element ID: 00001”, when the plant element configuration table 52 shown in FIG. 5 is referred to, it is “sludge pump” that has this element ID, and the signal definition table 53 of FIG. For example, it can be seen that a signal having the device ID (signal upper element ID) has the element ID “000001” of the signal having the name “current value”.

  At this time, according to the asset definition of item 1 of the asset tag definition list 56, the operation data of the signal with the element ID: 000001 is totaled from the trend table 54, and the average is obtained. Similarly, the operation data of the signal with element ID: 000001 is totaled according to the asset of item 2, and the maximum value is obtained. The asset type signal type of item 3 is “failure”. At this time, the “failure” event of the signal having the element ID: 00001 of “sludge pump” is searched from the event table 55, and the number is counted to obtain the “total number” as the calculation type.

  Note that the operation data totaling and calculation based on the asset tag definition list 56 described above are performed by the calculation means 43 in the server 40B, and the calculation result becomes the asset calculation result (analysis calculation result).

  The aggregation / detailing means 61 in the analysis unit 60 generates analysis target information that indicates the selected equipment or the like to be analyzed by the calculation means 43 to be aggregated and calculated, and this analysis target information and asset tag definition Based on the asset calculation result obtained from the calculation means 43 based on the list 56, the analysis result is displayed on the display unit 15.

  In such a configuration, in order to obtain the asset calculation result, first, the asset tag definition means 34A records the asset tag definition list 56 based on the information obtained from the input unit 14. Further, analysis target information is obtained by the aggregation / detailing means 61.

  Next, as in the first embodiment, plant operation data is collected by the server 40B. Thereafter, the calculation means 43 in the server 40B performs operation data aggregation and calculation based on the analysis target information and the asset tag definition list 56 described above to obtain an asset calculation result.

  Then, the aggregation / detailing means 61 displays the asset calculation result on the display unit 15 as the analysis result of the desired analysis level. The analysis results are displayed in a list or table format.

  At this time, an analysis target element indicating an element desired to be analyzed is selected by the input unit 14. The aggregation / detailing unit 61 in the analysis unit 60 reads the asset tag definition list 56 and displays the asset calculation result obtained by the calculation unit 43 on the display unit 15 at an analysis level based on the selected analysis target element. Let

  FIG. 14 is a flowchart showing an analysis operation (aggregation / detailing operation) by the aggregation / detailing means 61 shown in FIG. Hereinafter, the analysis operation by the aggregation / detailing unit 61 will be described with reference to FIG. FIG. 14 shows an example in which device signals (data) are aggregated in units of equipment.

  First, in step S11, at least one facility for performing analysis based on information obtained from the input unit 14 is selected by the aggregation / detailing unit 61 in the analysis unit 60 as a selected facility, and an analysis target instructing the selected facility get information.

  Next, in step S12, the element ID of the selected facility indicated by the analysis target information is searched from the plant element configuration table 52.

  Thereafter, in step S13, the element IDs of the selected equipment searched in step S12 are totaled and added to the element ID list 62 configured in a list format in a buffer (not shown in FIG. 12) in the analysis unit 60.

  Next, in step S14, one device is selected from the plant element configuration table 52, and it is determined whether or not the upper element ID is the same as the selected equipment selected in step S11. If there is a difference, the process proceeds to step S16.

  In step S15, which is executed in the case of YES in step S14, the element ID of the device having the selected facility as a higher element is added to the element ID list 62 in the buffer of the analysis unit 60.

  In the case of NO in step S14 and in step S16 executed after step S15, it is determined whether or not the determination in step S14 has been performed for all devices. If it has been performed (YES), the process proceeds to step S17. (NO) Return to step S14. After returning to step S14, steps S14 to S16 are repeated until YES is executed in step S16.

  With the above processing, the element ID list 62 in the buffer of the analysis unit 60 stores the element ID of the selected facility selected in step S11 and the element IDs of all devices in the selected facility.

  In step S <b> 17, the computing unit 43 refers to the asset tag definition list 56 based on the element ID list 62 and performs computation based on the asset tag from the trend table 54 and the event table 55. That is, the calculation means 43 refers to the asset tag definition list 56 and calculates the item using the trend table 54 and the event table 55 for each device according to the definition of the item included in the asset tag. Such calculations are performed for all the devices registered in the element ID list 62 and totaled to obtain an asset calculation result.

  In step S17, the device ID (signal upper element ID) indicating the related device to be calculated is stored in the element ID list 62 in the buffer, and the device registered in the element ID list 62 is calculated by the calculation means 43. Although the calculation using the trend table 54 and the event table 55 is performed, when the number of devices registered in the element ID list 62 increases, the calculation may take time.

  In such a case, it is conceivable to provide a buffer area for storing the calculation result in the asset tag definition list 56 for each device. That is, when the operation data from the plant is collected and the trend table 54 and the event table 55 are created, the calculation means 43 is operated in conjunction with the data collection means 41 and the event creation means 42, and at least in the asset tag definition list 56. It is conceivable that a calculation instructed by the asset tag definition list 56 is performed for each device having a registered element ID, and the result is stored in advance in the buffer area as a pre-calculation result.

  Thus, by providing a buffer area for storing the pre-computation result in the asset tag definition list 56, the pre-computation result corresponding to the device registered in the asset tag definition list 56 when performing the computation in step S17. Since the asset calculation result can be obtained by a relatively simple calculation process based on, the calculation can be performed efficiently.

  FIG. 15 is an explanatory diagram showing an example of aggregation / detailing by the aggregation / detailing means 61 in the case of the plant element configuration table 52 shown in FIG. 5 and the asset tag definition list 56 shown in FIG. In the figure, (a) and (b) show the analysis result 63A and the analysis result 63B. The result of collecting the analysis results 63A is the analysis result 63B.

  As shown in FIG. 15 (a), the analysis result 63A shows the details of the “sludge extraction” facility of the “first sedimentation pond” facility. The “sludge extraction” facility consists of three devices: “sludge extraction pump”, “sludge extraction valve”, and “flow meter”. Four items (item 1 to item 4) are aggregated according to the asset tag definition list 56 for each device.

  However, the analysis result of the entire “sludge extraction” facility may be considered more important than the analysis results of the three devices “sludge extraction pump”, “sludge extraction valve”, and “flow meter”. In this case, when the “sludge extraction” is aggregated as the analysis target element, the analysis result 63B shown in FIG. 15B can be displayed.

  That is, the values of three devices “sludge extraction pump”, “sludge extraction valve”, and “flow meter” included in the same “sludge extraction” facility are aggregated and displayed. For example, in the example of “failure”, the number of failures of the three devices, a value “8” obtained by integrating “5, 1, 2”, respectively, is displayed. The aggregated table can be refined by selecting equipment as well. The average value indicates the total average value “40.0” of the three devices, and the maximum value indicates the maximum value “200.0” within the maximum values of the three devices.

  On the contrary, when the “sludge extraction” facility, which is the analysis target element, is refined from the analysis result 63B. It becomes like the analysis result 63A. Each instruction and process of aggregation / detailing can be set by the aggregation / detailing means 61 based on information obtained from the input unit 14.

  Aggregation and refinement can be performed not only between facilities / equipment, but also between facilities / equipment and machine / facility. That is, it can carry out about all the plant elements contained under the arbitrary hierarchy which comprises a plant. For example, all devices included in all facilities can be aggregated.

  As described above, in the plant monitoring apparatus according to the second embodiment, analysis results can be aggregated and detailed, so that the status of a large number of devices can be immediately grasped by aggregation. In addition, it is possible to know the exact driving state by refining the items found by aggregation. As a result, the plant can be monitored at a desired analysis level centered on the analysis target element, so that the life of the plant system itself can be extended (long-term use).

  As described above, in the plant monitoring apparatus according to the second embodiment, the aggregation / detailing unit 61 causes the display unit 15 to display the analysis result of the analysis level determined by aggregation / detailing based on the analysis target element. Therefore, by displaying the analysis results in various modes, it is possible to recognize the operation state of the plant (summary or details of the failure occurrence state) immediately and in detail.

  In addition, since the plant monitoring apparatus of the second embodiment obtains the asset calculation result based on the asset tag definition list 56 and acquires the analysis result based on the asset calculation result, the contents of the asset tag definition list 56 are changed. By doing so, various analysis results can be obtained.

<Embodiment 3>
In the plant monitoring apparatus according to the first embodiment, the plant elements handled in the plant can be centrally managed by the element ID. In addition to the function of the first embodiment, the plant monitoring apparatus of the second embodiment is further provided with means for analyzing data that is centrally managed. In the third embodiment, in addition to the function of the second embodiment, a view for designating analysis contents can be defined when analyzing data.

  16 is a block diagram showing a configuration of a plant monitoring apparatus according to Embodiment 3 of the present invention. In FIG. 16, the same constituent elements as those shown in the first embodiment or the second embodiment are denoted by the same reference numerals, and the description thereof is omitted as appropriate. Note that the third embodiment can be realized by using the computer having the hardware configuration shown in FIG. 3 as in the first and second embodiments.

  The plant monitoring apparatus according to the third embodiment includes an input unit 14, a display unit 15, and a plant monitoring unit 23. The plant monitoring unit 23 includes an engineering tool 30C, a server 40C, a database 50C, and an analysis unit 60.

  The asset tag definition unit 34B of the engineering tool 30C has a function of setting an asset tag buffer 57 described later in addition to the function of the asset tag definition unit 34A of the second embodiment.

  The server 40C further includes notification means 44 in addition to the configuration of the server 40B of the second embodiment. The database 50C has an asset tag buffer 57 in addition to the contents of the database 50B shown in FIG. Therefore, the database 50C functions as a storage unit for the asset tag buffer 57.

  The asset tag buffer 57 (analysis signal identification information buffer area) stores contents equivalent to the asset tag definition list 56 provided corresponding to all plant elements.

  FIG. 17 is an explanatory diagram showing the contents of the asset tag provided corresponding to one device in the asset tag buffer 57 shown in FIG. 16 in a table format. An asset tag buffer 57 as shown in FIG. 17 is provided for all plant elements.

  As shown in the figure, the asset tag buffer 57 is an area created for each plant element and is an operation type. The type of signal (data) used for calculation and the calculation result are defined for each view. Here, two views (view item 1 and view item 2) are defined, and view item 1 has three elements of calculation type: average value, maximum value, and total number, and signal type: current value and current value, respectively. , Generating (calculating) from a failure signal. On the other hand, the view item 2 has two elements of calculation type: total number and minimum value, and indicates that generation (calculation) is performed from signals of signal type: driving and current value, respectively. Further, the classification of view items can be appropriately set according to purposes such as “energy saving” and “power consumption”. In this way, the view item functions as a calculation identification item that can specify a plurality of different calculation contents.

  As described above, the database 50C is provided corresponding to a plurality of plant elements constituting the plant, and the asset tag buffer capable of temporarily storing the asset calculation result in each plant element in association with the asset tag definition list 56. (Region) 57 is provided.

  The notification unit 44 notifies the calculation unit 43 of the recalculation when the calculation result stored in the asset tag buffer 57 needs to be recalculated.

  In such a configuration, first, the asset tag definition means 34B of the engineering tool 30C stores the asset tag definition list 56 having the structure shown in FIG. 13 as in the second embodiment. However, unlike the second embodiment, a view item as shown in FIG. 17 is additionally defined. That is, the asset tag definition content in the asset tag definition list 56 is the content defined with the view item and the signal type and operation type of the plant data (operation data + event data) necessary for updating (the content without the operation result in FIG. 17). Yes, stored in the database 50.

  Further, the asset tag definition unit 34B reflects the contents of the asset tag definition list 56 in association with all plant elements (city, village, facility, facility, equipment, and equipment) that constitute the plant based on the asset tag definition list 56. Further, an asset tag buffer 57 having a calculation result storage area is provided in the database 50.

  Next, operation data is collected from the plant by the server 40, that is, a trend table 54 including operation data and an event table 55 including event data are generated by the data collection unit 41 and the event creation unit 42. At this time, the calculation means 43 performs a recalculation operation in conjunction with the data collection means 41 and the event creation means 42 as necessary, so that the calculation type of each device is also displayed in the calculation result column of the asset tag buffer 57. The calculation result is stored (updated).

  The notification unit 44 determines whether or not recalculation is necessary from the signal type of the collected operation data by referring to the asset tag buffer 57. Then, the notification unit 44 performs recalculation notification to the calculation unit 43 when notification is necessary, and the calculation unit 43 that receives the notification extracts a device that needs recalculation and performs recalculation. The calculation result is stored in the calculation result column in the asset tag buffer 57.

  Thereafter, the calculation means 43 in the server 40B performs operation data aggregation and calculation based on the analysis target information and the information in the asset tag buffer 57 as in the second embodiment, and obtains an asset calculation result.

  Then, as in the second embodiment, the aggregation / detailing unit 61 causes the display unit 15 to display the asset calculation result and the analysis result of the desired analysis level. The analysis results are displayed in a list or table format.

  As described above, when the calculation means 43 of the server 40 receives the recalculation notification from the notification means 44, the asset tag according to the asset tag definition in the asset tag buffer 57 in conjunction with the processing of the data collection means 41 and the event creation means 42. Recalculate the elements of. This recalculation will be described using the signal definition table 53 shown in FIG. 9 as an example.

  For example, consider a case where the signal “002 / AI003” is updated. It can be seen from the signal definition table 53 that this signal is a parameter (signal type) indicating “current value”, and the related device is the element ID: 00003. It can be seen from the plant element configuration table 52 shown in FIG. 5 that the element ID: 00003 is “flow meter”. Referring to the asset tag buffer 57 related to the element ID: 00003, it is understood that the “average value” and the “maximum value” need to be recalculated by updating the “current value”. Therefore, the element ID: 00003 performs recalculation to obtain the “average” and “maximum value” of the “flow meter”.

  Further, since the plant element configuration table 52 shows that the upper element of the element ID: 00003 is the element ID: 000A0 and is the “sludge extraction” facility, it is comprehensive in the equipment used in the “sludge extraction” facility of the element ID: 000A0. Repeat the maximum value calculation again. Similarly, the same operation is performed for the element ID: 00200 (first sedimentation basin), which is the upper element of the facility 000A0, and the element ID: 01000 (A city D river water purification plant), which is the upper element, to the asset tag buffer 57. Store it.

  For example, if it is necessary to recalculate the device for power consumption measurement and the asset tag buffer 57 indicates the total power consumption, the total power consumption of the device, the device consumption in the entire “sludge extraction” facility The total power consumption, the total power consumption of the equipment in the entire “first sedimentation pond” facility, and the total power consumption of the equipment in the entire “A city D river water purification plant” station are recalculated, and the calculation result column of the corresponding asset tag buffer 57 is displayed. Will be stored.

  As described above, in the plant monitoring apparatus according to the third embodiment, the calculation unit 43 generates the trend table 54 and the event table 55 by the data collection unit 41 and the event generation unit 42 in response to the recalculation notification from the notification unit 44. Occasionally, calculation processing is performed in conjunction with the data collection means 41 and the event creation means 42 to obtain an asset calculation result, which is temporarily stored in the buffer area (calculation result column) of the asset tag buffer 57. For this reason, the calculation means 43 has an effect that the asset tag buffer 57 can be used to obtain the asset calculation result and the analysis result in a relatively short time.

  Furthermore, in the plant monitoring apparatus of the third embodiment, the asset tag definition list 56 and the asset tag buffer 57 have a view item that is an identification item for calculation that can specify a plurality of types of calculation contents different from each other. Various analysis results can be obtained by changing the calculation contents.

  14 input unit, 15 display unit, 30A-30C engineering tool, 31 plant element configuration defining unit, 32 signal defining unit, 33 device ledger managing unit, 34A, 34B asset tag defining unit, 40A-40C server, 41 data collecting unit, 42 Event creation means, 43 Asset tag definition means, 44 Notification means, 50A-50C database, 51 Device ledger, 52 Plant element configuration table, 53 Signal definition table, 54 Trend table, 55 Event table, 56 Asset tag definition list, 57 Asset tag buffer, 60 analysis unit, 61 aggregation / detailing means.

Claims (2)

A plant monitoring apparatus for monitoring a plant composed of a plurality of plant elements, wherein the plurality of plant elements have a hierarchical structure composed of a predetermined number of hierarchical levels,
A plant element configuration table storage means for storing a plant element configuration table defining a relationship between the plurality of plant elements, the plant element configuration table being associated with each of the plurality of plant elements, and an element ID indicating itself , Associated with a higher element ID indicating a higher plant element including itself,
Further comprising a signal definition table storage means for storing a signal definition table defining a plurality of signals of plant monitoring target that occurs in any of said plurality of plant components, the signal definition table in association with each of the plurality of signals , we can associate the element ID shows the own, the device ID which indicates a plant element itself is Zui associated one of the plurality of plants elements,
Further comprising an operation status monitoring means for monitoring the operation status based on the change of the plurality of signals ,
An analysis unit that displays the analysis result on a predetermined display unit so that the analysis result can be visually recognized based on the driving situation;
The analysis unit can select an analysis target element indicating a plant element desired to be analyzed for the plurality of plant elements, and an analysis result is displayed on the predetermined display unit at an analysis level based on the analysis target element. Including aggregation and refinement means to display,
Analysis signal identification information storage means for storing analysis signal identification information provided corresponding to the plurality of signals and defining at least signal types and calculation types for the plurality of signals for obtaining the analysis results;
A calculation means for obtaining a calculation result for analysis by performing calculation processing based on the driving situation with reference to the signal identification information for analysis;
The analysis unit obtains the analysis result based on the calculation result for analysis,
The driving status monitoring means generates driving status monitoring data for driving status monitoring based on changes in the plurality of signals,
The analysis signal identification information storage means has a plurality of analysis signal identification information buffer areas provided corresponding to the plurality of plant elements, and the plurality of analysis signal identification information buffer areas are respectively In relation to the analysis signal identification information, the analysis calculation result can be temporarily stored,
The calculation means performs calculation processing in conjunction with the driving condition monitoring means when the driving condition monitoring means generates the driving condition monitoring data, obtains the analysis calculation result, and corresponds to the analysis signal identification information. Temporarily save in the buffer area,
Plant monitoring device. The plant monitoring device according to claim 1,
The analysis identification information further includes a calculation identification item capable of designating a plurality of types of calculation contents different from each other.
Plant monitoring device.

Images