Management device, management method, and management program

Abstract

The alarm management device (10) stores each attribute of messages indicating the same or similar content and an internal attribute indicating the same or similar content in an associated manner for each type of alarm device (20) that outputs the messages, and upon receiving a message from the alarm device (20), transmits the message to the alarm device (20). An internal attribute associated with an attribute included in the received message is acquired from the storage unit, an internal message in which the attribute of the message is converted into the internal attribute is generated, and the internal message is output.

Description

Technical Field

[0001] The embodiments discussed herein relate to management devices, management methods, and management procedures. Background Technology

[0002] In factory control systems, the migration to the Open Platform Communication Unified Architecture (OPCUA) as the standard is accelerating; however, OPC Classic is still frequently used in existing systems, and hybrid environments combining multiple standards are increasing. Furthermore, environments with OPC UA servers from multiple vendors coexisting are also on the rise.

[0003] Reference List

[0004] Patent documents

[0005] PTL1: Japanese Patent Application Publication No. 2022-177415 Summary of the Invention

[0006] Technical issues

[0007] In the hybrid environment described above, the attributes of various messages generated in the factory control system are uniquely defined by each vendor, making it difficult for operators of the factory control system to quickly identify the details of the messages. Furthermore, in this hybrid environment, vendor-defined attributes with the same meaning are defined using unique names, such as "importance," "alarm priority," and "priority." This results in an increase in alarm data if all alarm attributes are to be displayed, making it difficult to compare attribute values ​​between alarms.

[0008] The present invention was conceived in view of the above circumstances, and its object is to efficiently output messages generated in a mixed environment with multiple vendors.

[0009] Solution to the problem

[0010] According to one aspect of an embodiment, a management apparatus includes: a storage unit that, for each type of apparatus that outputs messages, stores in an associated manner each attribute of a message indicating the same or similar content and an internal attribute indicating the same or similar content; and a generation unit that, upon receiving a message from the apparatus, retrieves the internal attribute associated with an attribute included in the received message from the storage unit, generates an internal message in which the attributes of the message are converted into the internal attribute, and outputs the internal message.

[0011] According to one aspect of an embodiment, a computer-implemented management method includes: storing, in an associated manner, each attribute of a message indicating the same or similar content and an internal attribute indicating the same or similar content for each type of device that outputs messages; when a message is received from the device, acquiring the internal attribute associated with the attribute included in the received message; generating an internal message in which the attributes of the message are converted into the internal attribute; and outputting the internal message.

[0012] According to one aspect of an embodiment, a management program that enables a computer to perform processing, the processing comprising: storing, in an associated manner, each attribute of a message indicating the same or similar content and an internal attribute indicating the same or similar content for each type of device that outputs the message; when a message is received from the device, acquiring the internal attribute associated with an attribute included in the received message; generating an internal message in which the attributes of the message are converted into the internal attribute; and outputting the internal message.

[0013] Beneficial effects of the invention

[0014] According to the present invention, it is possible to efficiently output messages generated in a mixed environment with multiple vendors. Attached Figure Description

[0015] Figure 1 This is a schematic diagram illustrating a configuration example and a processing example of an alarm management system according to one embodiment.

[0016] Figure 2 This is a block diagram illustrating an example configuration of each device in an alarm management system according to one embodiment.

[0017] Figure 3 This is a schematic diagram illustrating the attribute name storage unit of an alarm management device according to one embodiment.

[0018] Figure 4 This is a schematic diagram illustrating the attribute value storage unit of an alarm management device according to one embodiment.

[0019] Figure 5 This is a schematic diagram illustrating the internal alarm storage unit of an alarm management device according to one embodiment.

[0020] Figure 6 This is a schematic diagram illustrating a specific example of unified processing of alarm attributes according to one embodiment.

[0021] Figure 7 This is a flowchart illustrating an example of the entire process of an alarm management system according to one embodiment.

[0022] Figure 8 This is a flowchart illustrating an example of a process for receiving engineering details performed by an alarm management system according to one embodiment.

[0023] Figure 9 This is a flowchart illustrating an example of the entire process of unified processing of alarm attributes performed by an alarm management system according to one embodiment.

[0024] Figure 10 This is a flowchart illustrating an example of the entire process of alarm notification processing performed by an alarm management system according to one embodiment.

[0025] Figure 11 This is a schematic diagram illustrating an example of a hardware configuration according to one embodiment. Detailed Implementation

[0026] An embodiment of the management device, management method, and management procedure according to the present invention will now be described in detail with reference to the accompanying drawings. The present invention is not limited to the embodiments described below.

[0027] The configuration and processing of the alarm management system 100 according to one embodiment, the configuration and processing of each device of the alarm management system 100, and the flow of processing performed by the alarm management system 100 will be described in sequence, and finally the effects of the embodiment will be described.

[0028] 1. Configuration and processing of alarm management system 100

[0029] The following will refer to Figure 1 The configuration and processing of an alarm management system 100 according to one embodiment are described in detail. Figure 1 This is a schematic diagram illustrating a configuration example and a processing example of an alarm management system 100 according to one embodiment. The following will describe, in sequence, the configuration example of the entire alarm management system 100, the processing example of the alarm management system 100, and the problems of the alarm management system 100P according to the reference technology, and finally, the effects of the alarm management system 100 will be described. Meanwhile, in this embodiment, remote monitoring of factory production using factory equipment will be described as an example, wherein the factory equipment is equipment installed in a factory; however, there are no particular limitations on the equipment and the field of use, and the technology can be applied to remote monitoring of environmental measurements, such as power monitoring, wind power generation, water and sewage monitoring, or river monitoring.

[0030] 1-1. Configuration example of the entire alarm management system 100

[0031] The alarm management system 100 includes an alarm management device 10, alarm devices 20 (server devices 20A, 20B, and 20C), an engineer terminal 30, and an operator terminal 40. The alarm management device 10, alarm devices 20, engineer terminal 30, and operator terminal 40 are communicatively connected to each other via a predetermined communication network (network not shown) in a wired or wireless manner. Various communication networks, such as the Internet or dedicated lines, can be used as the predetermined communication network.

[0032] The alarm device 20 will now be described. The alarm device 20 is a device that has alarm detection capabilities and detects alarms indicating abnormalities in the factory or its equipment based on sensor values, process values, etc., within the factory. Here, the server device 20A in the alarm device 20 is an OPC US server. Furthermore, the server device 20B in the alarm device 20 is an OPC A&E server. Additionally, the control device 20C in the alarm device 20 is a controller constituting a distributed control system (DCS).

[0033] Furthermore, engineer terminal 30 is the terminal used by engineer E who manages alarm management device 10. Additionally, operator terminal 40 is the terminal used by operator O who manages the plant. Meanwhile, Figure 1 The alarm management system 100 shown may include multiple alarm management devices 10, multiple engineer terminals 30, or multiple operator terminals 40.

[0034] 1-2. Example of the entire process performed by the alarm management system 100

[0035] The entire process performed by the alarm management system 100 as described above will now be described. The processes from S1 to S7 can be performed in different orders. Furthermore, some processes from S1 to S7 can be omitted.

[0036] 1-2-1. Project Details Acceptance and Processing

[0037] First, the alarm management device 10 receives engineering details (S1). For example, the alarm management device 10 receives the definition of the devices in the factory (hereinafter, appropriately referred to as "device definition") from the engineer terminal 30 and stores the definition therein. Furthermore, the alarm management device 10 receives the definition of the attribute name of the alarm corresponding to the device in the factory (hereinafter, appropriately referred to as "attribute name definition" or "attribute name mapping definition") and stores the definition therein. Additionally, the alarm management device 10 receives the definition of the attribute value of the alarm corresponding to the device in the factory (hereinafter, appropriately referred to as "attribute value definition" or "attribute value mapping definition") and stores the definition therein.

[0038] Here, device definition is information indicating the type of alarm device 20 included in the factory control system of the factory, such as information including the supplier name and device type of each alarm device 20, such as: {Server device 20A: Supplier A (OPC UA server), Server device 20B: Supplier B (OPC A&E server), Control device 20C: Supplier C (CENTUM PCS)}.

[0039] In addition, the attribute name mapping definition is information that associates the alarm attribute name defined for each alarm device 20 with the internal attribute name used to display the attribute name in a uniform manner. For example, it is information that includes the internal attribute name of each alarm attribute name of alarm device 20, such as: {Attribute name of server device 20A: "Importance", internal attribute name: "Priority"}, {Attribute name of server device 20B: "Alarm Priority", internal attribute name: "Priority"} or {Attribute name of control device 20C: "Priority", internal attribute name: "Priority"}.

[0040] In addition, the attribute value mapping definition is information that associates the alarm attribute value defined for each alarm device 20 with the internal attribute value used to display the attribute value in a uniform manner. For example, it includes information on the internal attribute value of each alarm attribute value of alarm device 20, such as: {attribute value of server device 20A: "critical alarm", internal attribute value: "high"}, {attribute value of server device 20B: "high", internal attribute value: "high"}, or {attribute value of control device 20C: "M", internal attribute value: "medium"}.

[0041] In the engineering details reception process described above, the alarm management device 10 can receive from the engineer terminal 30 the definition of alarm attribute types corresponding to devices in the plant (hereinafter, appropriately referred to as "attribute type definition" or "attribute type mapping definition"). Here, the attribute type mapping definition is information that associates alarm attribute types (e.g., "string") defined for alarm device 20 with internal attribute types used to display attribute names in a uniform manner, and includes information on the internal attribute types of each alarm attribute type of alarm device 20.

[0042] 1-2-2. Alarm Reception and Processing

[0043] Next, the alarm management device 10 receives alarms (S2). For example, the alarm management device 10 receives alarm A from the server device 20A: {Source: "EQP_A", Message: "EQP_AHH", Importance: "Critical Alarm"}. Furthermore, the alarm management device 10 receives alarm B from the server device 20B: {Source: "EQP_B", Message: "EQP_B HI", Alarm Priority: "High"}. Additionally, the alarm management device 10 receives alarm C from the control device 20C: {Source: "EQP_C", Message: "EQP_C HI", Priority: "M"}.

[0044] 1-2-3. Processing for retrieving internal attribute names

[0045] Third, the alarm management device 10 acquires the internal attribute name (S3). For example, the alarm management device 10 acquires the internal attribute name "priority" corresponding to the attribute name "importance" of alarm A, received from the server device 20A, by referring to the stored attribute name mapping definition. Furthermore, the alarm management device 10 acquires the internal attribute name "priority" corresponding to the attribute name "alarm priority" of alarm B, received from the server device 20B, by referring to the stored attribute name mapping definition. Additionally, the alarm management device 10 acquires the internal attribute name "priority" corresponding to the attribute name "priority" of alarm C, received from the control device 20C, by referring to the stored attribute name mapping definition.

[0046] In the internal attribute name acquisition process described above, the alarm management device 10 can obtain the internal attribute type corresponding to the alarm attribute type (e.g., "string") received from the alarm device 20 by referring to the stored attribute type mapping definition.

[0047] 1-2-4. Processing for obtaining internal attribute values

[0048] Fourth, the alarm management device 10 acquires internal attribute values ​​(S4). For example, the alarm management device 10 acquires the internal attribute value "High" corresponding to the attribute value "Critical Alarm" of alarm A, received from the server device 20A, by referring to the stored attribute value mapping definition. Furthermore, the alarm management device 10 acquires the internal attribute value "High" corresponding to the attribute value "High" of alarm B, received from the server device 20B, by referring to the stored attribute value mapping definition. Additionally, the alarm management device 10 acquires the internal attribute value "Medium" corresponding to the attribute value "M" of alarm C, received from the control device 20C, by referring to the stored attribute value mapping definition.

[0049] 1-2-5. Internal Alarm Generation and Processing

[0050] Fifth, the alarm management device 10 generates an internal alarm (S5). For example, the alarm management device 10 generates an internal alarm A' with unified attribute name and attribute value by converting the attribute name "importance" of alarm A received from server device 20A into the internal attribute name "priority" and converting the attribute value "critical alarm" of alarm A received from server device 20A into the internal attribute value "high", and stores the internal alarm A'. Furthermore, the alarm management device 10 generates an internal alarm B' with unified attribute name and attribute value by converting the attribute name "alarm priority" of alarm B received from server device 20B into the internal attribute name "priority" and converting the attribute value "high" of alarm B received from server device 20B into the internal attribute value "high", and stores the internal alarm B'. In addition, the alarm management device 10 generates an internal alarm C' with unified attribute name and attribute value by converting the attribute name "priority" of the alarm C received from the control device 20C into the internal attribute name "priority" and converting the attribute value "M" of the alarm C received from the control device 20C into the internal attribute value "medium", and stores the internal alarm C'.

[0051] 1-2-6. Internal Alarm Sending Processing

[0052] Sixth, the alarm management device 10 sends internal alarms (S6). For example, the alarm management device 10 sends the generated internal alarm A', generated internal alarm B', and generated internal alarm C' to the operator terminal 40.

[0053] 1-2-7. Internal Alarm Display Handling

[0054] Seventh, the operator terminal 40 controls the display of internal alarms (S7). For example, the operator terminal 40 controls the display of internal alarms A', B' and C' received from the alarm management device 10 on the monitor.

[0055] 1-3. The effectiveness of the alarm management system 100

[0056] The following will first describe the background, overview, and problems of the alarm management system 100P based on the reference technology, and then describe the effects of the alarm management system 100.

[0057] 1-3-1. Background of Alarm Management System 100P

[0058] In the Alarm Management System 100P, migration to OPC UA as the standard has begun; however, OPC Classic is still frequently used in existing systems, and hybrid environments combining multiple standards are increasing. Furthermore, environments with OPC UA servers from multiple vendors coexisting are also on the rise. Therefore, in the Alarm Management System 100P, standardization of these hybrid environments as described above is necessary.

[0059] Specifically, in the Alarm Management System 100P, alarm attributes need to be displayed uniformly for facilities based on multiple vendors' OPC UA and OPC Classic. Furthermore, the Alarm Management System 100P requires uniform display of alarm attributes because, for each third party, vendor-defined attributes with the same meaning should be defined using unique names.

[0060] 1-3-2. Problems with Alarm Management System 100P

[0061] In the alarm management system 100P, in the hybrid environment described above, the attributes of various messages generated in the factory control system are uniquely defined by each vendor. Therefore, it is difficult for operators of the factory control system to quickly identify the details of the messages. For example, in the alarm management system 100P, in the hybrid environment described above, vendor-defined attributes with the same meaning are defined using unique names, such as "importance," "alarm priority," and "priority." This results in an increase in alarm data if all alarm attributes are to be displayed, and makes it difficult to compare attribute values ​​between alarms.

[0062] 1-3-3. Overview of Alarm Management System 100

[0063] First, the alarm management device 10 receives project details (device definition, attribute name mapping definition, attribute value mapping definition, etc.) from the engineer terminal 30. Second, the alarm management device 10 receives alarms from the alarm device 20. Third, the alarm management device 10 retrieves the internal attribute names stored during the project. Fourth, the alarm management device 10 retrieves the internal attribute values ​​stored during the project. Fifth, the alarm management device 10 generates an internal alarm by converting alarm attribute names to internal attribute names and alarm attribute values ​​to internal attribute values. Sixth, the alarm management device 10 sends the generated internal alarm to the operator terminal 40. Seventh, the operator terminal 40 controls the display of the internal alarms received from the alarm management device 10.

[0064] 1-3-4. The effectiveness of the alarm management system 100%

[0065] The effects of the alarm management system 100 will be described below. The alarm management system 100 has a mapping rule setting function to receive project details (device definition, attribute name mapping definition, attribute value mapping definition, etc.) during project execution, and an internal attribute function to generate internal alarms based on the aforementioned project details at runtime, allowing alarms to be processed independently of the interface and server type. Therefore, by using internal attributes, the alarm management system 100 can reduce alarm data and easily compare attribute values ​​between alarms.

[0066] Furthermore, in the alarm management system 100, the host-to-host binding or collaboration information (CI) server acts as an OPC UA server, and it is satisfactory to send only the values ​​of internal attributes when providing information to higher-level apparatuses. Therefore, the alarm management system 100 can improve performance by reducing the amount of information sent from lower-level apparatuses to higher-level apparatuses.

[0067] 2. Configuration and processing of each device in the alarm management system 100

[0068] The following will refer to Figure 2 describe Figure 1 The alarm management system 100 shown in the figure includes the configuration and processing of the alarm management device 10. Figure 2 This is a block diagram illustrating configuration examples of each device included in an alarm management system 100 according to one embodiment. Below, a configuration example of the entire alarm management system 100 according to one embodiment will first be described, followed by detailed descriptions of configuration and processing examples of alarm management device 10, alarm device 20, engineer terminal 30, and operator terminal 40.

[0069] 2-1. Configuration example of the entire alarm management system 100

[0070] The following will refer to Figure 2 describe Figure 1 The image shows a configuration example of the entire alarm management system 100. (Example...) Figure 2 As shown, the alarm management system 100 includes an alarm management device 10, an alarm device 20, an engineer terminal 30, and an operator terminal 40. The alarm management device 10 is communicatively connected to the alarm device 20, the engineer terminal 30, and the operator terminal 40 via a communication network N implemented by the Internet, dedicated lines, etc.

[0071] 2-2. Configuration and processing examples of alarm management device 10

[0072] The following will refer to Figure 2 This describes a configuration example and a processing example of an alarm management device 10 as a management device. The alarm management device 10 includes a communication unit 11, a storage unit 12, and a control unit 13. The alarm management device 10 also includes an input unit (e.g., a keyboard, mouse, etc.) for receiving various operations from an engineer E or other manager of the alarm management device 10, or a display unit (e.g., a liquid crystal display, etc.) for displaying various information.

[0073] 2-2-1. Communication Unit 11

[0074] The communication unit 11 controls data communication with different devices. For example, the communication unit 11 communicates with each communication device via a router or the like. Furthermore, the communication unit 11 can communicate with an operator terminal (not shown).

[0075] 2-2-2. Storage Unit 12

[0076] Storage unit 12 stores various information referenced by control unit 13 during operation, as well as various information acquired by control unit 13 during operation. Storage unit 12 includes attribute name storage unit 12a, attribute value storage unit 12b, and internal alarm storage unit 12c. Here, storage unit 12 can be implemented using, for example, semiconductor storage devices (such as random access memory (RAM) or flash memory) or storage devices (such as hard disks or optical disks). Meanwhile, in Figure 2 In the example shown, storage unit 12 is installed inside alarm management device 10, but storage unit 12 can be installed outside alarm management device 10, or multiple storage units can be installed.

[0077] Storage unit 12 stores, in an associated manner, each attribute of a message indicating the same or similar content and an internal attribute indicating the same or similar content for each type of device outputting the message. For example, storage unit 12 stores each alarm attribute and internal attribute in an associated manner, wherein each vendor sets the alarm attribute for each vendor device collecting alarms output from each device included in the system, and the internal attribute is unified by the alarm attributes set by each vendor. Furthermore, storage unit 12 stores, in an associated manner, each attribute name as each attribute and the internal attribute name as an internal attribute for each type of device. Additionally, storage unit 12 stores, in an associated manner, each attribute value as each attribute and the internal attribute value as an internal attribute for each type of device. Furthermore, storage unit 12 may also store, in an associated manner, each attribute type as each attribute and the internal attribute type as an internal attribute for each type of device.

[0078] Furthermore, for example, the message described above is an alarm indicating an anomaly in the system and one of the devices included in the system. Specifically, the message described above is an alarm indicating an anomaly in the plant control system that controls the plant, and one of the plant devices included in the plant control system. Furthermore, the devices described above conform to OPC UA or OPC Classic.

[0079] 2-2-2-1. Attribute Name Storage Unit 12a

[0080] The attribute name storage unit 12a stores the attribute name definitions (attribute name mapping definitions) received by the receiving unit 13a of the control unit 13, which will be described later. (Refer to below...) Figure 3 An example describing the data stored in attribute name storage unit 12a. Figure 3 This is a schematic diagram illustrating an example of the attribute name storage unit 12a of an alarm management device 10 according to one embodiment. Figure 3 In the example shown, the attribute name storage unit 12a stores the items "source", "attribute name", "internal attribute name" and "attribute type".

[0081] "Source" indicates the identification information used to identify the alarm device 20, such as the identification number or symbol of the alarm device 20. "Attribute Name" indicates the name of the attribute included in the alarm of the alarm device 20. "Internal Attribute Name" indicates the name of the transformed alarm associated with the alarm device 20. "Attribute Type" indicates how the alarm data of the alarm device 20 is managed.

[0082] Specifically, Figure 3 The following example is shown, in which the attribute name storage unit 12a stores: data {attribute name: "importance", internal attribute name: "priority", attribute type: "string"} for alarm device 20 (server device 20A) identified by "EQP_A", data {attribute name: "alarm priority", internal attribute name: "priority", attribute type: "string"} for alarm device 20 (server device 20B) identified by "EQP_B", and data {attribute name: "priority", internal attribute name: "priority", attribute type: "string"} for alarm device 20 (control device 20C) identified by "EQP_C".

[0083] 2-2-2-2. Attribute value storage unit 12b

[0084] The attribute value storage unit 12b stores the attribute value definitions (attribute value mapping definitions) received by the receiving unit 13a of the control unit 13, which will be described later. (Refer to below...) Figure 4An example describing the data stored in attribute value storage unit 12b. Figure 4 This is a schematic diagram illustrating an example of the attribute value storage unit 12b of an alarm management device 10 according to one embodiment. Figure 4 In the example shown, attribute value storage unit 12b stores items for “source”, “attribute value”, and “internal attribute value”.

[0085] "Source" indicates the identification information used to identify the alarm device 20, such as the identification number or identification symbol of the alarm device 20. "Attribute value" indicates the status value corresponding to the attribute of the alarm of the alarm device 20 as a device. "Internal attribute value" indicates the status value corresponding to the converted attribute, wherein the converted attribute is associated with each alarm device 20 as a device.

[0086] Specifically, Figure 4 The following example is shown, in which the attribute value storage unit 12b stores: data {attribute value: "critical alarm", internal attribute value: "high"} for alarm device 20 (server device 20A) identified by "EQP_A", data {attribute value: "high", internal attribute value: "high"} for alarm device 20 (server device 20B) identified by "EQP_B", and data {attribute value: "M", internal attribute value: "medium"} for alarm device 20 (control device 20C) identified by "EQP_C".

[0087] 2-2-2-3. Internal alarm storage unit 12c

[0088] The internal alarm storage unit 12c stores internal alarms generated by the generation unit 13c of the control unit 13, which will be described later. (Refer to the following...) Figure 5 An example describing the data stored in the internal alarm storage unit 12c. Figure 5 This is a schematic diagram illustrating an example of the internal alarm storage unit 12c of an alarm management device 10 according to one embodiment. Figure 5 In the example shown, the internal alarm storage unit 12c stores items such as "source", "message" and "priority".

[0089] "Source" indicates the identification information used to identify the alarm device 20 as a device, such as the identification number or identification symbol of each alarm device 20. "Message" indicates the alarm message included in the alarm of the alarm device 20 as a device and received by the receiving unit 13b. "Priority" indicates the status value corresponding to the name of the converted attribute, wherein the converted attribute is associated with each alarm device 20 as a device.

[0090] Specifically, Figure 5The following example is shown, in which the internal alarm storage unit 12c stores: data {message: "EQP_A HH", priority: "high"} for server device 20A identified as alarm device 20 by "EQP_A", data {message: "EQP_BHI", priority: "high"} for server device 20B identified as alarm device 20 by "EQP_B", and data {message: "EQP_C HI", priority: "medium"} for control device 20C identified as alarm device 20 by "EQP_C".

[0091] 2-2-3. Control Unit 13

[0092] The control unit 13 controls the entire alarm management device 10. The control unit 13 includes an receiving unit 13a, a receiving unit 13b, a generating unit 13c, and a transmitting unit 13d. The control unit 13 is implemented, for example, by electronic circuitry, such as a central processing unit (CPU) or a microprocessor unit (MPU), or by integrated circuits, such as application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs).

[0093] 2-2-3-1. Receiving Unit 13a

[0094] The receiving unit 13a receives various types of information. Simultaneously, the receiving unit 13a can store the received information in the storage unit 12. For example, the receiving unit 13a receives project details from the engineer terminal 30. The device definition receiving process, attribute name definition receiving process, and attribute value definition receiving process will be described sequentially below.

[0095] Device definition acceptance processing

[0096] The receiving unit 13a receives device definitions as engineering details. For example, the receiving unit 13a receives device definitions that indicate the type of alarm device 20 included in the factory's factory control system, including the supplier name and device type of the alarm device 20 set by engineer E.

[0097] As a specific example, the receiving unit 13a receives device definitions such as {Server device 20A: Supplier A (OPC UA server), Server device 20B: Supplier B (OPCA&E server), Control device 20C: Supplier C (CENTUM PCS)} from the project details setting screen input to the engineer terminal 30.

[0098] Attribute name definition and acceptance processing

[0099] The receiving unit 13a receives the attribute name definition (attribute name mapping definition) as project details. For example, the receiving unit 13a receives the attribute name definition and stores the attribute name definition in the attribute name storage unit 12a, wherein the attribute name definition is information that associates the alarm attribute name defined for each alarm device 20 with the internal attribute name used to display the attribute name in a uniform manner, and includes the internal attribute name of each alarm attribute name of the alarm device 20 set by the engineer E.

[0100] As a specific example, the receiving unit 13a receives the attribute name definitions input to the engineering details setting screen of the engineer terminal 30, such as {attribute name of server device 20A: "Importance", internal attribute name: "Priority"}, {attribute name of server device 20B: "Alarm Priority", internal attribute name: "Priority"}, {attribute name of control device 20C: "Priority", internal attribute name: "Priority"}, etc.

[0101] At this time, receiving unit 13a can receive attribute type definitions (attribute type mapping definitions) as project details. For example, receiving unit 13a can receive attribute type definitions that are information about the association between alarm attribute types (e.g., "string") defined for alarm device 20 and internal attribute types used to display attribute names in a uniform manner, and include internal attribute types for each alarm attribute type of alarm device 20 set by engineer E.

[0102] Attribute value definition acceptance processing

[0103] The receiving unit 13a receives attribute value definitions (attribute value mapping definitions) as engineering details. For example, the receiving unit 13a receives attribute value definitions and stores them in the attribute value storage unit 12b. The attribute value definitions are information that associates alarm attribute values ​​defined for the alarm device 20 with internal attribute values ​​used to display attribute values ​​in a uniform manner, and include internal attribute values ​​for each alarm attribute value of the alarm device 20 set by the engineer E.

[0104] As a specific example, the receiving unit 13a receives the following attribute value definitions from the engineering details setting screen of the engineer terminal 30: for example, {attribute value of server device 20A: "crisis alarm", internal attribute value: "high"}, {attribute value of server device 20B: "high", internal attribute value: "high"}, {attribute value of control device 20C: "M", internal attribute value: "medium"}.

[0105] 2-2-3-2. Receiving Unit 13b

[0106] The receiving unit 13b receives various types of information. Simultaneously, the receiving unit 13b can store the received information in the storage unit 12. For example, the receiving unit 13b receives an alarm from the alarm device 20, which has an alarm detection function.

[0107] As a specific example, receiving unit 13b receives alarm A {Source: "EQP_A", Message: "EQP_A HH", Importance: "Critical Alarm"} sent by server device 20A, which acts as an OPC UA server in alarm device 20. Furthermore, receiving unit 13b receives alarm B {Source: "EQP_B", Message: "EQP_B HI", Alarm Priority: "High"} sent by server device 20B, which acts as an OPC A&E server in alarm device 20. Additionally, receiving unit 13b receives alarm C {Source: "EQP_C", Message: "EQP_C HI", Priority: "M"} sent by control device 20C, which acts as a controller in the DCS of alarm device 20.

[0108] 2-2-3-3. Generating Unit 13c

[0109] Generation unit 13c generates various types of information. Simultaneously, generation unit 13c acquires various types of information received by receiving unit 13b. Furthermore, generation unit 13c acquires various types of information stored in storage unit 12. Additionally, generation unit 13c stores the generated information in storage unit 12. For example, when a message is received from a device, generation unit 13c acquires internal attributes corresponding to the attributes included in the received message from storage unit 12, generates an internal message by converting the message's attributes into internal attributes, and outputs the internal message. Furthermore, when an alarm is received from any one of multiple supplier devices, generation unit 13c generates an internal message by converting the received alarm's attributes into internal attributes, and outputs the internal message. The internal attribute name acquisition process, internal attribute type acquisition process, internal attribute value acquisition process, and internal alarm generation process will be described sequentially below.

[0110] Internal attribute name retrieval processing

[0111] The generation unit 13c obtains the internal attribute name. For example, when an alarm message is received from the alarm device 20, which is a device, the generation unit 13c obtains the internal attribute name associated with the attribute name included in the received alarm message from the attribute name storage unit 12a.

[0112] As a specific example, generation unit 13c obtains the internal attribute name "priority" associated with the attribute name "importance" of alarm A received from server device 20A by referring to the attribute name definitions stored in attribute name storage unit 12a. Furthermore, generation unit 13c obtains the internal attribute name "priority" associated with the attribute name "alarm priority" of alarm B received from server device 20B by referring to the attribute name definitions stored in attribute name storage unit 12a. Additionally, generation unit 13c obtains the internal attribute name "priority" associated with the attribute name "priority" of alarm C received from control device 20C by referring to the attribute name definitions stored in attribute name storage unit 12a.

[0113] Internal property type retrieval processing

[0114] The generation unit 13c acquires the internal attribute type. For example, when an alarm message is received from the alarm device 20, which is a device, the generation unit 13c acquires the internal attribute type associated with the attribute type included in the received alarm message from the storage unit 12.

[0115] Internal attribute value retrieval processing

[0116] The generation unit 13c acquires internal attribute values. For example, when an alarm message is received from the alarm device 20, which is a device, the generation unit 13c acquires internal attribute values ​​associated with the attribute values ​​included in the received alarm message from the attribute value storage unit 12b.

[0117] As a specific example, generation unit 13c obtains the internal attribute value "High" associated with the attribute value "Critical Alarm" of alarm A received from server device 20A by referring to the attribute value definitions stored in attribute value storage unit 12b. Furthermore, generation unit 13c obtains the internal attribute value "High" associated with the attribute value "High" of alarm B received from server device 20B by referring to the attribute value definitions stored in attribute value storage unit 12b. Additionally, generation unit 13c obtains the internal attribute value "Medium" associated with the attribute value "M" of alarm C received from control device 20C by referring to the attribute value definitions stored in attribute value storage unit 12b.

[0118] Internal attribute value retrieval processing

[0119] Generation unit 13c generates internal alarms. For example, generation unit 13c generates and outputs an internal alarm, wherein the internal alarm is an internal message in which the attribute name of the alarm message is converted into an internal attribute name. Furthermore, generation unit 13c generates and outputs an internal alarm, wherein the attribute type of the alarm message is converted into an internal attribute type. Additionally, generation unit 13c generates and outputs an internal alarm, wherein the attribute value of the alarm message is converted into an internal attribute value.

[0120] As a specific example, generation unit 13c generates an internal alarm A' with unified attribute name and value by converting the attribute name "Importance" of alarm A received from server device 20A into the internal attribute name "Priority" and the attribute value "Critical Alarm" of alarm A received from server device 20A into the internal attribute value "High", and stores internal alarm A' in internal alarm storage unit 12c. Furthermore, generation unit 13c generates an internal alarm B' with unified attribute name and value by converting the attribute name "Alarm Priority" of alarm B received from server device 20B into the internal attribute name "Priority" and the attribute value "High" of alarm B received from server device 20B into the internal attribute value "High", and stores internal alarm B' in internal alarm storage unit 12c. In addition, the generation unit 13c generates an internal alarm C' with unified attribute name and attribute value by converting the attribute name "priority" of the alarm C received from the control device 20C into the internal attribute name "priority" and converting the attribute value "M" of the alarm C received from the control device 20C into the internal attribute value "medium", and stores the internal alarm C' in the internal alarm storage unit 12c.

[0121] 2-2-3-4. Transmitting Unit 13d

[0122] The sending unit 13d sends various types of information. For example, the alarm management device 10 retrieves internal alarms from the internal alarm storage unit 12c and sends the retrieved internal alarms to the operator terminal 40.

[0123] As a specific example, the sending unit 13d sends to the operator terminal 40 internal alarms generated by the generating unit 13c: internal alarm A'{source: "EQP_A", message: "EQP_A HH", priority: "high"}, internal alarm B'{source: "EQP_B", message: "EQP_B HI", priority: "high"}, and internal alarm C'{source: "EQP_C", message: "EQP_CHI", priority: "medium"}.

[0124] 2-3. Specific examples of unified alarm attribute processing performed by the alarm management system 100

[0125] The following will refer to Figure 6 Specific examples of data related to the unified processing of alarm attributes performed by an alarm management system 100 according to one embodiment are described below. Non-unified alarms, attribute name definitions, attribute name unified alarms, attribute value definitions, and attribute name and attribute value unified alarms will be described in sequence below.

[0126] 2-3-1. Non-uniform alarm

[0127] Figure 6 (1) shows an example of a non-uniform alarm that alarm management device 10 has received from alarm device 20. Figure 6 In the example shown in (1), the non-uniform alarms {source: "EQP_A", message: "EQP_AHH", importance: "critical alarm"} of server device 20A, the non-uniform alarms {source: "EQP_B", message: "EQP_B HI", alarm priority: "high"} of server device 20B, and the non-uniform alarms {source: "EQP_C", message: "EQP_C HI", priority: "M"} of control device 20C are shown as examples.

[0128] 2-3-2. Attribute Name Definition

[0129] Figure 6 (2) shows the attribute name definition stored in the alarm management device 10. Figure 6 In the example shown in (2), the attribute name definition of server device 20A is {attribute name: "importance", internal attribute name: "priority", attribute type: "string"}, the attribute name definition of server device 20B is {attribute name: "alarm priority", internal attribute name: "priority", attribute type: "string"}, and the attribute name definition of control device 20C is {attribute name: "priority", internal attribute name: "priority", attribute type: "string"} as examples are shown.

[0130] 2-3-3. Uniform Alerts for Attribute Names

[0131] Figure 6 Example (3) shows a uniform attribute name alarm, in which the attribute names are uniform and the uniform attribute name alarm is generated by alarm management device 10. Figure 6In the example shown in (3), the attribute name uniform alarm {source: "EQP_A", message: "EQP_A HH", priority: "critical alarm"} of server device 20A, the attribute name uniform alarm {source: "EQP_B", message: "EQP_B HI", priority: "high"} of server device 20B, and the attribute name uniform alarm {source: "EQP_C", message: "EQP_C HI", priority: "M"} of control device 20C are shown as examples.

[0132] 2-3-4. Attribute Value Definition

[0133] Figure 6 (4) shows the attribute value definitions stored in the alarm management device 10. Figure 6 In the example shown in (4), the attribute value definition of server device 20A is {attribute value: "crisis alarm", internal attribute value: "high"}, the attribute value definition of server device 20B is {attribute value: "high", internal attribute value: "high"}, and the attribute value definition of control device 20C is {attribute value: "M", internal attribute value: "medium"} as an example.

[0134] 2-3-5. Unified Alert for Attribute Name and Attribute Value

[0135] Figure 6 Example (5) shows a unified alarm for attribute name and attribute value, in which the attribute name and attribute value are unified, and the unified alarm for attribute name and attribute value is generated by alarm management device 10. Figure 6 In the example shown in (5), the attribute name and attribute value unified alarm {source: "EQP_A", message: "EQP_AHH", priority: "high"} of server device 20A, the attribute name and attribute value unified alarm {source: "EQP_B", message: "EQP_BHI", priority: "high"} of server device 20B, and the attribute name and attribute value unified alarm {source: "EQP_C", message: "EQP_C HI", priority: "medium"} of control device 20C are shown as examples.

[0136] 2-3-6. Others

[0137] Although in the above Figure 6Example (5) shows an example of a unified alarm for attribute name and attribute value, in which the attribute name and attribute value are unified. However, the alarm management device 10 can generate an attribute value unified alarm in which only the attribute value is unified. In addition, the alarm management device 10 can generate an attribute type unified alarm in which only the attribute type is unified, an attribute type and attribute name unified alarm in which the attribute type and attribute name are unified, an attribute type and attribute value unified alarm in which the attribute type and attribute value are unified, or an attribute type / attribute name / attribute value unified alarm in which the attribute type, attribute name and attribute value are unified.

[0138] 2-4. Configuration and processing examples of alarm device 20

[0139] The following will refer to Figure 2 This describes configuration and processing examples for alarm device 20. Alarm device 20 may be, for example, server device 20A, server device 20B, control device 20C, etc. Alarm device 20 is a device with alarm detection functionality, detecting sensor values, process values, etc., in the factory, and issuing alarms indicating abnormalities in the factory or its equipment.

[0140] 2-4-1. Server Unit 20A

[0141] The server device 20A in the alarm device 20 is, for example, an OPC UA server. It collects process values ​​such as temperature data, pressure data, and flow data from sensor devices such as temperature sensors, pressure sensors, and flow sensors in the factory. When the process value exceeds the threshold, it generates an alarm A and sends the generated alarm A to the alarm management device 10.

[0142] 2-4-2. Server device 20B

[0143] Server device 20B, for example, is an OPC A&E server, which collects process values ​​such as temperature data, pressure data, and flow data from sensor devices such as temperature sensors, pressure sensors, and flow sensors in the factory. When the process value exceeds the threshold, an alarm B is generated and sent to the alarm management device 10.

[0144] 2-4-3. Control device 20C

[0145] The control device 20C, for example, is a controller included in a DCS, which collects process values ​​such as temperature data, pressure data, and flow data from sensor devices such as temperature sensors, pressure sensors, and flow sensors in the factory. When the process value exceeds the threshold, an alarm C is generated and sent to the alarm management device 10.

[0146] 2-5. Configuration and processing examples for Engineer Terminal 30

[0147] The following reference Figure 2 The following describes configuration and processing examples for the engineer terminal 30. The engineer terminal 30 is a terminal used by the engineer E who manages the alarm management device 10, and includes an input / output unit 31, a transmit / receive unit 32, and a communication unit 33.

[0148] 2-5-1. Input / Output Unit 31

[0149] The input / output unit 31 controls the input of various information to the engineer terminal 30. For example, the input / output unit 31 may be implemented using a mouse, keyboard, touch panel, etc., and receives input such as setting information to the engineer terminal 30. Furthermore, the input / output unit 31 controls the display of various information from the engineer terminal 30. For example, the input / output unit 31 may be implemented using a display, etc., and controls the display of setting information stored in the engineer terminal 30.

[0150] The input / output unit 31 controls the display of the engineering details setting screen used to set engineering details in the alarm management device 10.

[0151] 2-5-2. Transmitting and Receiving Unit 32

[0152] The sending and receiving unit 32 sends various types of information. For example, the sending and receiving unit 32 sends project details such as device definitions, attribute name definitions, and attribute type definitions that engineer E inputs into the project details setting screen to the alarm management device 10. In addition, the sending and receiving unit 32 receives various types of information.

[0153] 2-5-3. Communication Unit 33

[0154] The communication unit 33 controls data communication with different devices. For example, the communication unit 33 communicates with each communication device via a router or the like. Furthermore, the communication unit 33 can communicate with an operator terminal (not shown).

[0155] 2-6. Configuration Example of Operator Terminal 40

[0156] The following reference Figure 2 This describes a configuration example and a processing example of the operator terminal 40. The operator terminal 40 is a terminal used by operator O who manages the plant, and includes an input / output unit 41, a transmit / receive unit 42, and a communication unit 43.

[0157] 2-6-1. Input / Output Unit 41

[0158] The input / output unit 41 controls the input of various information to the operator terminal 40. For example, the input / output unit 41 may be implemented using a mouse, keyboard, touch panel, etc., and receives input such as setting information to the operator terminal 40. Furthermore, the input / output unit 41 controls the display of various information from the operator terminal 40. For example, the input / output unit 41 may be implemented using a display, etc., and controls the display of setting information stored in the operator terminal 40.

[0159] The input / output unit 41 controls the display of internal alarms sent from the alarm management device 10. For example, the input / output unit 41 controls the display of internal alarms A', B', and C' sent from the alarm management device 10.

[0160] 2-6-2. Transmitting and Receiving Unit 42

[0161] The transmitting and receiving unit 42 transmits various types of information. In addition, the transmitting and receiving unit 42 receives various types of information. For example, the transmitting and receiving unit 42 receives internal alarms A', B', and C' transmitted from the alarm management device 10.

[0162] 2-6-3. Communication Unit 43

[0163] The communication unit 43 controls data communication with different devices. For example, the communication unit 43 communicates with each communication device via a router or the like. Furthermore, the communication unit 43 can communicate with an operator terminal (not shown).

[0164] 3. The process flow of each operation performed by the alarm management system 100

[0165] The following will refer to Figures 7 to 10 This document describes the processing flow performed by an alarm management system 100 according to one embodiment. The overall processing flow of the alarm management system 100 will be described first, followed by the sequential description of the process details acceptance processing, alarm attribute unification processing, and alarm notification processing.

[0166] 3-1. The entire processing flow executed by the alarm management system 100

[0167] The following will refer to Figure 7 The flow of the entire process performed by an alarm management system 100 according to one embodiment is described. Figure 7 This is a flowchart illustrating an example of the overall process performed by an alarm management system 100 according to one embodiment. The processes described below, S101 to S103, can be performed in a different order. Furthermore, some processes in S101 to S103 described below can be omitted.

[0168] First, the alarm management device 10 performs engineering details acceptance processing (S101). Second, the alarm management device 10 performs alarm attribute unification processing (S102). Third, the alarm management device 10 performs alarm notification processing (S103).

[0169] 3-2. Process for Accepting and Handling Project Details

[0170] The following will refer to Figure 8 The process of engineering details acceptance processing performed by an alarm management system 100 according to one embodiment is described. Figure 8 This is a flowchart illustrating an example of the process of receiving engineering details performed by an alarm management system 100 according to one embodiment. The processes S201 to S203 described below can be performed in a different order. Furthermore, some processes in S201 to S203 described below can be omitted.

[0171] First, the alarm management device 10 performs device definition acceptance processing (S201). Second, the alarm management device 10 performs attribute name definition acceptance processing (S202). Third, the alarm management device 10 performs attribute value definition acceptance processing (S203).

[0172] 3-3. Unified Process for Alarm Attributes

[0173] The following will refer to Figure 9 This describes the process of unified alarm attribute processing performed by an alarm management system 100 according to one embodiment. Figure 9 This is a flowchart illustrating an example of a unified alarm attribute processing procedure performed by an alarm management system 100 according to one embodiment. The processes described below, S301 to S305, can be performed in a different order. Furthermore, some processes in S301 to S305 described below can be omitted.

[0174] First, the alarm management device 10 performs attribute name acquisition processing (S301). Second, the alarm management device 10 performs internal attribute name acquisition processing (S302). Third, the alarm management device 10 performs attribute value acquisition processing (S303). Fourth, the alarm management device 10 performs internal attribute value acquisition processing (S304). Fifth, the alarm management device 10 performs internal alarm generation processing (S305).

[0175] 3-4. Alarm Notification Process

[0176] The following will refer to Figure 10 The process of alarm notification processing performed by an alarm management system 100 according to one embodiment is described. Figure 10This is a flowchart illustrating an example of an alarm notification processing procedure performed by an alarm management system 100 according to one embodiment. The processes described below, S401 to S403, can be performed in a different order. Furthermore, some processes in S401 to S403 described below can be omitted.

[0177] First, the alarm management device 10 performs internal alarm acquisition processing (S401). Second, the alarm management device 10 performs internal alarm transmission processing (S402). Third, the operator terminal 40 performs internal alarm display processing (S403).

[0178] 4. Effects of the Implementation Example

[0179] Finally, the effects of one embodiment will be described below. The first to seventh effects corresponding to the processing of one embodiment will be described below.

[0180] 4-1. First Effect

[0181] First, in the processing according to one embodiment described above, the alarm management device 10 stores, in an associated manner, each attribute of a message indicating the same or similar content and an internal attribute indicating the same or similar content for each type of device that outputs the message. When a message is received from a device, the internal attribute associated with the attribute included in the received message is obtained, an internal message is generated in which the message's attributes are converted into internal attributes, and the internal message is output. Therefore, in this processing, messages generated in a mixed environment with multiple vendors can be efficiently output.

[0182] 4-2. Second Effect

[0183] Second, in the processing according to one embodiment described above, the message is an alarm indicating an anomaly in the system and one of the devices included in the system, and the alarm management device 10 stores each alarm attribute and internal attribute in an associated manner. Each vendor sets alarm attributes for each vendor device that collects alarms output from each device included in the system. The internal attributes unify the alarm attributes set by each vendor. When an alarm is received from any vendor device, an internal message is generated where the attributes of the received alarm are converted into internal attributes, and this internal message is output. Therefore, in this processing, messages generated in a mixed environment with multiple vendors can be effectively output for generated alarms.

[0184] 4-3. Third Effect

[0185] Third, in the processing according to one embodiment described above, the alarm management device 10 stores, in an associated manner, each attribute name as an attribute and an internal attribute name as an internal attribute for each type of device, and when a message is received from a device, it obtains the internal attribute name associated with the attribute name included in the received message, generates an internal message in which the attribute names of the message are converted into internal attribute names, and outputs the internal message. Therefore, in this processing, by integrating attribute names, messages generated in a mixed environment with multiple vendors can be efficiently output.

[0186] 4-4. Fourth Effect

[0187] Fourth, in the processing according to one embodiment described above, the alarm management device 10 stores, in an associated manner, each attribute type as an attribute and an internal attribute value as an internal attribute for each type of device, and when a message is received from the device, it obtains the internal attribute type associated with the attribute type included in the received message, generates an internal message in which the attribute type of the message is converted into the internal attribute type, and outputs the internal message. Therefore, in this processing, by integrating attribute types, messages generated in a mixed environment with multiple vendors can be output efficiently.

[0188] 4-5. Fifth Effect

[0189] Fifth, in the processing according to one embodiment described above, the alarm management device 10 stores, in an associated manner, each attribute value as an attribute and an internal attribute value as an internal attribute for each type of device, and when a message is received from a device, it acquires the internal attribute value associated with the attribute value included in the received message, generates an internal message in which the attribute value of the message is converted into the internal attribute value, and outputs the internal message. Therefore, in this processing, by integrating attribute values, messages generated in a mixed environment with multiple vendors can be output efficiently.

[0190] 4-6. Sixth Effect

[0191] Sixth, in the processing according to one embodiment described above, the device conforms to OPC UA or OPC Classic. Therefore, in this processing, with the progress of international standardization, messages generated in a mixed environment with multiple vendors can be efficiently output.

[0192] 4-7. The Seventh Effect

[0193] Seventh, in the processing of one embodiment as described above, the message is an alarm indicating an anomaly in either the factory control system controlling the factory or the factory equipment included in the factory control system. Therefore, in this processing, messages generated in a mixed environment with multiple vendors can be efficiently output within the factory control system.

[0194] system

[0195] Unless otherwise specified, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above description and drawings may be changed at will.

[0196] Furthermore, the components shown in the accompanying drawings are functionally conceptual and do not necessarily have to be physically configured as shown. In other words, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings. That is, depending on various loads or usage conditions, all or part of the devices may be functionally or physically distributed or unified in any unit.

[0197] Furthermore, for each processing function executed by each device, all or any part of the processing function can be implemented by the CPU and the program analyzed and executed by the CPU, or it can be implemented in hardware by wired logic.

[0198] hardware

[0199] The following describes an example of the hardware configuration of the alarm management device 10, which serves as an alarm management device. Other devices may also have the same hardware configuration. Figure 11 This is a schematic diagram illustrating an example of a hardware configuration according to one embodiment. For example... Figure 11 As shown, the alarm management device 10 includes a communication device 10a, a storage device 10b, a memory 10c, and a processor 10d. Furthermore, Figure 11 All the units shown are connected to each other via buses or the like.

[0200] The communication device 10a is a network interface card, etc., and communicates with different servers. The memory 10b stores data used for implementation... Figure 2 The program and database with the functions shown in the figure.

[0201] Processor 10d reads and executes data from storage device 10b, etc. Figure 2 Each processing unit shown in the diagram processes the same procedure, loads the read procedure into memory 10c, and implements the above-described procedure. Figure 2Each function described herein. For example, this processing implements the same function as each processing unit included in the alarm management device 10. Specifically, the processor 10d reads programs from the storage device 10b, etc., that have the same functions as the receiving unit 13a, receiving unit 13b, generating unit 13c, sending unit 13d, etc. Furthermore, the processor 10d executes processing that performs the same processing as the receiving unit 13a, receiving unit 13b, generating unit 13c, sending unit 13d, etc.

[0202] As described above, the alarm management device 10 functions as a means of reading and executing programs and implementing various processing methods. Furthermore, the alarm management device 10 can enable a media reading device to read the aforementioned program from a recording medium, execute the read program, and perform the same functions as in the above embodiments. At the same time, the programs described in different embodiments are not always executed by the alarm management device 10. For example, the invention can also be applied when programs are executed on different computers or servers, or when programs are executed collaboratively by different computers and servers.

[0203] The program can be distributed via networks such as the Internet. Furthermore, the program can be recorded on computer-readable recording media (such as hard disks, floppy disks (FD), optical discs (CD-ROM), magneto-optical discs (MO), or digital versatile discs (DVDs)) and can be executed by having a computer read the program from the recording medium.

[0204] List of reference numerals

[0205] 10 Alarm Management Devices

[0206] 11 Communication Units

[0207] 12 storage units

[0208] 12a Attribute Name Storage Unit

[0209] 12b attribute value storage unit

[0210] 12c internal alarm storage unit

[0211] 13 control units

[0212] 13a Reception Unit

[0213] 13b receiving unit

[0214] 13c generation unit

[0215] 13D Transmitting Unit

[0216] 20 alarm devices

[0217] 30 Engineer Terminal

[0218] 31 Input / Output Unit

[0219] 32 Transmitting and Receiving Units

[0220] 33 communication units

[0221] 40 operator terminals

[0222] 41 Input / Output Unit

[0223] 42 Transmitting and Receiving Units

[0224] 43 Communication Units

[0225] 100 Alarm Management System

Claims

1. A management device, comprising: A storage unit, for each type of device that outputs messages, stores in an associated manner each attribute of a message indicating the same or similar content and an internal attribute indicating said same or similar content; as well as A generation unit, upon receiving a message from the device, retrieves internal attributes associated with attributes included in the received message from the storage unit, generates an internal message in which the attributes of the message are converted into the internal attributes, and outputs the internal message.

2. The management device according to claim 1, wherein, The message is an alert indicating an anomaly in the system or one of the devices included in the system. The storage unit stores each alarm attribute and internal attribute in an associated manner, wherein the alarm attributes are set by each vendor for each vendor device that collects alarms output from each device included in the system, and the internal attributes are unified by the alarm attributes set by the various vendors. When the generation unit receives an alarm from any supplier device, it generates an internal message in which the attributes of the received alarm are converted into the internal attributes, and outputs the internal message.

3. The management device according to claim 1, wherein, For each type of the device, the storage unit stores, in an associated manner, each attribute name as an attribute and the internal attribute name as an internal attribute, and When the generation unit receives a message from the device, it retrieves the internal attribute name associated with the attribute name included in the received message from the storage unit, generates an internal message in which the attribute name of the message is converted into the internal attribute name, and outputs the internal message.

4. The management device according to claim 1, wherein, The storage unit stores, in an associated manner, each attribute type as an attribute and the internal attribute type as an internal attribute for each type of the device, and When the generation unit receives a message from the device, it retrieves an internal attribute type associated with the attribute type included in the received message from the storage unit, generates an internal message in which the attribute type of the message is converted into the internal attribute type, and outputs the internal message.

5. The management device according to claim 1, wherein, The storage unit stores, in an associated manner, each attribute value as an attribute and the internal attribute value as an internal attribute for each type of the device, and When the generation unit receives a message from the device, it retrieves an internal attribute value associated with the attribute value included in the received message from the storage unit, generates an internal message in which the attribute value of the message is converted into the internal attribute value, and outputs the internal message.

6. The management device according to any one of claims 1 to 5, wherein, The device conforms to either the Open Platform Communication Unified Architecture (OPC UA) or OPC Classic.

7. The management device according to any one of claims 1 to 5, wherein, The message is an alarm indicating an anomaly in one of the plant control system controlling the plant or in one of the plant devices included in the plant control system.

8. A management method implemented by a computer, the management method comprising: For each type of device that outputs messages, each attribute of a message indicating the same or similar content and an internal attribute indicating the same or similar content are stored in an associated manner; When a message is received from the device, internal attributes associated with the attributes included in the received message are obtained; Generate an internal message, in which the message's attributes are converted to the internal attributes; and Output the internal message.

9. A management program that enables a computer to perform processing, said processing comprising: For each type of device that outputs messages, each attribute of a message indicating the same or similar content and an internal attribute indicating the same or similar content are stored in an associated manner; When a message is received from the device, internal attributes associated with the attributes included in the received message are obtained; Generate an internal message, in which the message's attributes are converted to the internal attributes; and Output the internal message.

Images