Deployment method and device of factory-level alarm system, electronic equipment and storage medium

Abstract

The invention provides a method for deploying a plant-level alarm system, which comprises the following steps that: a whole-plant-level plant model is constructed according to a plant department architecture or a business object node, the plant model comprises a plurality of levels, each level at least comprises one sub-model, and the sub-models of different levels have a mapping relationship; importing instrument equipment data and binding the instrument equipment data to the corresponding sub-models; newly establishing instrument position numbers and binding the instrument position numbers to the corresponding sub-models and instrument equipment, wherein the instrument position numbers and the collector position numbers are in one-to-one correspondence; and configuring an alarm platform based on the configuration, establishing a whole plant appearance map, and binding each component with a corresponding sub-model, instrument equipment and an instrument position number. According to the technical scheme, by establishing a core concept of'factory equipment objects', alarm information of a plurality of'instrument position numbers' bound with the'factory equipment objects' is aggregated upwards, so that the equipment becomes a comprehensive alarm state indicator, and an operator can quickly master the overall operation health condition of the equipment from a macroscopic level.

Description

Technical Field

[0001] This invention relates to the field of equipment alarm technology, and specifically to a deployment method, apparatus, electronic device, and storage medium for a factory-level alarm system. Technical Background

[0002] In modern industrial automation systems, especially in process industries such as petrochemicals, power generation, and metallurgy, the stable operation of factory equipment is crucial. To ensure production safety and efficiency, Supervisory Control and Data Acquisition (SCADA) systems or Distributed Control Systems (DCS) are commonly used to monitor data from numerous sensors and instruments in real time. When this data exceeds preset safety limits, the system triggers an alarm to alert operators for timely intervention. Although many automated alarm control solutions exist, they generally suffer from the following drawbacks:

[0003] (1) Alarms are isolated and lack information aggregation. A device may have multiple key parameters (such as temperature, pressure, vibration), and each parameter may trigger an alarm independently. Operators need to manually associate this information in multiple scattered alarm lists to determine the overall health status of the device, which greatly increases the workload and the risk of misjudgment. For example, if a pump's bearing high temperature alarm and high vibration alarm occur simultaneously, its severity is far greater than a single alarm, but existing systems usually cannot automatically associate the alarms at these two points and escalate them into a comprehensive alarm of "pump failure". (2) Alarm configuration flexibility is insufficient. Although there are ordinary alarms and simple advanced alarms (such as rate of change), support for more complex scenarios is limited. For example, the mechanism of "alarms not cleared after confirmation", which can effectively urge the handling of legacy issues, is not built into many traditional systems; "line alarms" used to detect sensor jamming or communication interruption are also often ignored. (3) Visualization and operation and maintenance are disconnected. Alarm information is usually displayed in a list-style alarm window, while the physical layout of the factory and the equipment structure are reflected in the configuration diagram, which is a disconnect. Operators need to frequently switch between configuration diagrams and alarm lists, making it impossible to intuitively see "which device is alarming" on a single diagram, thus reducing monitoring efficiency. (4) Weak model-driven capability. Existing systems rarely establish clear, factory-wide object models and use these models for alarm inheritance, aggregation, and display. This makes it difficult for existing alarm systems to adapt to changes in factory structure and hinders knowledge accumulation and reuse.

[0004] Technical content

[0005] The present invention aims to solve at least one of the above-mentioned technical problems.

[0006] To address the aforementioned problems, this invention provides a method, apparatus, electronic device, and storage medium for deploying a factory-level alarm system.

[0007] In a first aspect, the present invention provides a method for deploying a factory-level alarm system, comprising:

[0008] A factory-wide model is constructed based on the factory department structure or business object nodes. The factory model includes multiple levels, and each level includes at least one sub-model. There is a mapping relationship between the sub-models of different levels.

[0009] Import instrument and equipment data and bind it to the corresponding sub-model;

[0010] Create a new instrument tag number and bind it to the corresponding sub-model and the instrument device. The instrument tag number and the data collector tag number are in one-to-one correspondence.

[0011] Based on the configuration alarm platform, a plant-wide overview map is established, and each component is bound to the corresponding sub-model, instrument equipment, and instrument tag number.

[0012] Optionally, the method further includes setting alarm conditions for each instrument tag number, including one or a combination of simple threshold alarm, alarm frequency, alarm delay, alarm dead zone, straight line alarm, alarm not cleared after confirmation, and price fluctuation alarm.

[0013] Optionally, the process involves constructing a factory-wide model based on business object nodes, and establishing the hierarchy sequentially according to the order of "scenario - specialty - sub-specialty".

[0014] Optionally, the process involves constructing a full-plant-level factory model based on the factory's departmental structure, establishing the hierarchy from top to bottom according to the order of "factory area - department - device - unit".

[0015] Optionally, the settings for the instrument equipment include: equipment number, equipment name, equipment type, specifications, tag number, factory area, factory model, functional location, technical identification, category, and device.

[0016] Optionally, the settings for the instrument tag number may also include: tag number name, tag number description, instrument control tag number, priority, factory model, equipment, whether tag number alarm is enabled, and tag number type.

[0017] Optionally, the overall plant overview diagram is a deep fusion of alarm status and visual configuration diagram, and different colors are used to distinguish the health status of the instruments and equipment.

[0018] Secondly, the present invention provides a deployment device for a factory-level alarm system, comprising:

[0019] The factory model unit is used to construct a factory-wide factory model based on the factory area department architecture or business object nodes. The factory model includes multiple levels, and each level includes at least one sub-model. There is a mapping relationship between the sub-models of different levels.

[0020] The data entry unit is used to import instrument and equipment data and bind it to the corresponding sub-model; and to bind newly created instrument tag numbers to the corresponding sub-model and the instrument and equipment, wherein the instrument tag number and the data collector tag number correspond one-to-one.

[0021] The configuration display unit is used to establish a plant overview map based on the configuration of the alarm platform, and each component is bound to the corresponding sub-model, the instrument equipment and the instrument tag number.

[0022] Thirdly, the present invention provides an electronic device, including a memory and a processor;

[0023] The memory is used to store computer programs;

[0024] The processor is configured to, when executing the computer program, implement a deployment method for a factory-level alarm system as described in the first aspect.

[0025] Fourthly, the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements a deployment method for a factory-level alarm system as described in the first aspect.

[0026] The beneficial effects of this technical solution are as follows:

[0027] 1) Achieve intelligent aggregation of alarm information: By establishing the core concept of "factory equipment object", the alarm information of multiple "instrument tag numbers" bound to it is aggregated upwards, making the equipment itself a comprehensive alarm status indicator, so that the operator can quickly grasp the overall operational health status of the equipment from a macro perspective.

[0028] 2) Enhance the flexibility and accuracy of alarm configuration: Based on traditional ordinary alarms, integrate a variety of advanced alarm types to provide richer and more accurate alarm methods for different working conditions and needs, effectively reducing missed alarms and false alarms.

[0029] 3) Enhance the intuitiveness and convenience of monitoring: Deeply integrate alarm status with the visualized configuration diagram, and directly reflect the health status of the bound devices through component colors, without the need to switch between different systems for comparison, greatly reducing the cognitive load of operators and the cost of equipment operation and maintenance.

[0030] 4) Building a model-driven monitoring system: By constructing a plant-wide factory model, a structured master data system is formed, which enables alarm configuration, data association and status display to be based on a unified object model, thereby improving the maintainability and scalability of the system.

[0031] Instruction manual illustrations

[0032] Figure 1 This is a flowchart illustrating the deployment method of a factory-level alarm system according to an embodiment of the present invention.

[0033] Figure 2 This is a basic configuration diagram of the factory model in an embodiment of the present invention;

[0034] Figure 3 This is a basic configuration diagram of the instrument equipment in an example of the present invention;

[0035] Figure 4 This is a basic configuration diagram of the instrument tag number in an example of the present invention;

[0036] Figure 5 This is an advanced alarm configuration diagram for an instrument tag number in an example of the present invention;

[0037] Figure 6 This is a diagram showing the effect of binding the instrument tag number to the instrument device in this invention example;

[0038] Figure 7 This is a schematic diagram illustrating the working principle of the alarm system according to an example of the present invention.

[0039] Figure 8 This is a system architecture diagram of the deployment device for the factory-level alarm system according to an embodiment of the present invention;

[0040] Figure 9 This is a system architecture diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0041] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Although some embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present invention. It should be understood that the accompanying drawings and embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of protection of the present invention.

[0042] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0043] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to"; the term "based on" means "at least partially based on"; the term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments"; and the term "optionally" means "optional embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first," "second," etc., mentioned in this invention are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0044] It should be noted that the terms "a" and "a plurality of" used in this invention are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0045] The names of the messages or information exchanged between the multiple devices in the embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0046] Reference Appendix Figure 1 The present invention provides a method for deploying a factory-level alarm system, the steps of which are as follows:

[0047] S1. Construct a factory-wide model based on the factory department architecture or business object nodes. The factory model includes multiple levels, and each level includes at least one sub-model. There are mapping relationships between the sub-models at different levels.

[0048] Specifically, there are two ways to construct the factory model in this technical solution:

[0049] If structured according to the factory's departmental framework, the hierarchy should be established from top to bottom in the order of "Factory Area - Department - Unit - Device". (See attached reference.) Figure 2First, the entire plant area is taken as the first-level factory model. Its corresponding first-level sub-models can include all categorizable monitoring needs within the plant area, such as instrumentation health management, equipment health management, process health management, and electrical health management. The specific names and classification methods of the sub-models can be adjusted and determined according to different plant monitoring needs; this embodiment only provides one feasible construction approach. Second, the departments within the plant area are taken as the second-level factory model, and each department is treated as a second-level sub-model and mapped to the first-level sub-model. For example, in this embodiment, the first-level sub-model "Instrumentation Health Management" includes more than ten departments such as the second-level sub-models "Refinery Department 1," "Refinery Department 2," "Olefins Department 1," and "Storage and Transportation Department." In particular, cross-mapping is also possible; for example, the second-level sub-model "Refinery Department 1" can also be mapped to the first-level sub-model "Equipment Health Management." Then, the equipment is treated as a Level 3 plant model, with each specific unit as a Level 3 sub-model, such as an atmospheric and vacuum distillation unit or a catalytic cracking unit, and a mapping is established between them and each Level 2 sub-model. Finally, the unit is treated as a Level 3 plant model, with each instrument and device as a Level 4 sub-model, and a mapping is established between them and each Level 3 sub-model. See the appendix for details. Figure 5 This will be explained in detail later. Of course, depending on the organizational structure, a level three factory model can also be a group or unit under a level two (department) factory model, with devices and units extending to the next level.

[0050] If constructed based on business object nodes, the hierarchy is established sequentially according to the order of "scenario - specialty - sub-specialty". For example, to display the overall factory layout in different scenarios, the scenario is first set as the first level of the factory model, with health and risk as first-level sub-models. Then, the specialty is set as the second level of the factory model, representing the sub-fields within the scenario. The second-level sub-models could be interlocking specialties, control specialties, quality specialties, etc., and a mapping relationship is established between the second-level and first-level sub-models. The sub-specialty is set as the third level of the factory model, and a third-level sub-model is established based on further sub-fields. Of course, the levels can be determined based on the actual professional fields involved in the factory, establishing different hierarchical levels. For example, it can be extended to the fourth level of the factory model, or it can be set up up to the second level. Similarly, devices and units are extended as the next level and established using the same mapping method, which will not be elaborated further here.

[0051] S2. Import instrument and equipment data and bind it to the corresponding sub-model.

[0052] Reference Appendix Figure 3 and Figure 6Equipment data can be manually entered or synchronized from external systems to complete the basic configuration of equipment master data. This basic configuration includes equipment number, equipment name, equipment type, specifications, tag number, factory area, factory model, functional location, technical identifier, category, and device, so that each instrument and device can be mapped to the corresponding sub-model. For example, a cracking furnace is mapped to a sub-model at the device level, then to a sub-model at the department level, and finally bound to the first-level sub-model of instrument professional health management at the plant level.

[0053] S3. Create a new instrument tag number and bind it to the corresponding sub-model and instrument device. The instrument tag number and the data acquisition device tag number are in one-to-one correspondence.

[0054] See attached document Figure 4 and Figure 5 Each instrument tag number needs to have alarm conditions set, including one or a combination of the following: simple threshold alarm, alarm frequency, alarm delay, alarm dead zone, linear alarm, alarm not cleared after confirmation, and price fluctuation alarm.

[0055] Specifically, in this embodiment, ordinary alarms can be categorized into different types based on the data type of different instrument tag numbers. Analog alarms can be divided into four types: high-limit alarm (H), high-high-limit alarm (HH), low-limit alarm (L), and low-low-limit alarm (LL). Digital alarms can be either 0 or 1. Enumerated alarms are distinguished by configured enumeration values. Virtual tag numbers can use custom alarm expressions. Ordinary alarm limitations: In some situations, ordinary alarms may continuously clear, so there are some simple limitations, such as alarm frequency, alarm delay, and alarm dead zone. Alarm frequency: After the previous alarm is cleared, no new alarm of the same type should be generated within n seconds; subsequent alarms are ignored. Alarm delay: The system does not display or record the alarm information currently generated; instead, it delays the alarm. If the alarm disappears after the delay, it indicates that the alarm was likely a false alarm and can be automatically cleared by the system. Alarm dead zone: For a pressure range of 0-1.5MPa, a high alarm at 1MPa should theoretically clear the alarm when PV ≤ 1MPa. However, sometimes, because the process is not yet stable, PV fluctuates around 1MPa, causing the alarm system to continuously issue alarms. To prevent this, the alarm exit condition is set to 1 - range * 2% MPa, i.e., 0.97MPa. This means the alarm is considered cleared only when PV < 0.97MPa. Range * 2% is the so-called dead zone, actually called alarm exit lag, preferably set to 2%-5%. Advanced alarms include linear alarms, alarms not cleared after confirmation, increase alarms, and decrease alarms. Linear alarms are generated when the data value does not change within a specified threshold. Alarms not cleared after confirmation are generated when an alarm record is confirmed but not cleared after n seconds. Increase / decrease alarms are generated for analog signals when the increase or decrease of two consecutive values ​​exceeds a threshold.

[0056] After configuring the alarm conditions, you can choose to bind the factory model and the corresponding instrument device, thus associating the instrument tag number with the instrument device. The bound instrument tag number can also be viewed in the device. The settings for the instrument tag number include: tag number name, tag number description, instrument control tag number, priority, factory model, device, whether tag number alarm is enabled, tag number type, etc.

[0057] S4. Based on the configuration alarm platform, establish a plant-wide overview map, with each component bound to a corresponding sub-model, instrument / equipment, and instrument tag number. The plant-wide overview map deeply integrates alarm status with the visual configuration map, using different colors to distinguish the health status of the instruments / equipment. For example, after an instrument tag number alarms, the alarm is aggregated to the instrument / equipment alarm, ultimately reflecting the equipment alarm status on the plant-wide overview map. Preferably, red indicates the equipment is currently alarming, yellow indicates the alarm has been confirmed but not cleared, green indicates the equipment is normal, and gray can indicate that the component is not bound to a plant model, instrument / equipment, or instrument tag number.

[0058] Reference Appendix Figure 7 The specific instrument tag number alarm process is as follows: The instrument tag number data comes from the point data sent by the data acquisition unit. The sent data needs to exclude data with a quality code status other than GOOD. The real-time value of the sent point is determined by the data type and alarm conditions configured in the instrument tag number configuration to determine whether an alarm is generated. Finally, it is combined with the component binding in the configuration configuration to the factory model, equipment and tag number, and reflected in the configuration diagram to display the alarm status of the factory equipment.

[0059] like Figure 8 As shown, this embodiment of the invention provides a deployment device 300 for a factory-level alarm system, comprising:

[0060] Factory model unit 310 is used to construct a factory-wide factory model based on the factory area department architecture or business object nodes. The factory model includes multiple levels, each level includes at least one sub-model, and there are mapping relationships between the sub-models of different levels.

[0061] The data entry unit 320 is used to import instrument and equipment data and bind it to the corresponding sub-model; and to bind newly created instrument tag numbers to the corresponding sub-model and instrument and equipment, with the instrument tag number and the data acquisition tag number corresponding one-to-one.

[0062] The configuration display unit 330 is used to configure the alarm platform based on the configuration and establish a full plant overview map. Each component is bound to the corresponding sub-model, instrument equipment and instrument tag number.

[0063] like Figure 9 As shown, an electronic device 400 provided in this embodiment of the invention includes a memory 410 and a processor 420; the memory 410 is used to store a computer program; the processor 420 is used to implement a deployment method for a factory-level alarm system as described above when the computer program is executed.

[0064] Alternatively, an electronic device 400 includes a memory 410 and a processor 420 coupled to the memory 410; the memory 410 is configured to store a computer program; and the processor 420 is configured to perform the following operations when the computer program is executed:

[0065] A factory-wide model is constructed based on the factory department structure or business object nodes. The factory model includes multiple levels, and each level includes at least one sub-model. There are mapping relationships between the sub-models of different levels.

[0066] Import instrument and equipment data and bind it to the corresponding sub-model;

[0067] Create a new instrument tag number and bind it to the corresponding sub-model and the instrument device. The instrument tag number and the data collector tag number are in one-to-one correspondence.

[0068] Based on the configuration alarm platform, a plant-wide overview map is created, with each component bound to a corresponding sub-model, instrument, and instrument tag number.

[0069] This invention provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements a deployment method for a factory-level alarm system as described above.

[0070] Alternatively, a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the following operations:

[0071] A factory-wide model is constructed based on the factory department structure or business object nodes. The factory model includes multiple levels, and each level includes at least one sub-model. There are mapping relationships between the sub-models of different levels.

[0072] Import instrument and equipment data and bind it to the corresponding sub-model;

[0073] Create a new instrument tag number and bind it to the corresponding sub-model and instrument device. The instrument tag number and the data acquisition tag number are in one-to-one correspondence.

[0074] Based on the configuration alarm platform, a plant-wide overview map is created, with each component bound to a corresponding sub-model, instrument, and instrument tag number.

[0075] The present invention will now be described an electronic device 400 that can serve as a server or client of the present invention, which is an example of a hardware device that can be applied to various aspects of the present invention. Electronic device 400 is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic device 400 can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0076] Electronic device 400 includes a computing unit that can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) or a computer program loaded from a storage unit into random access memory (RAM). The RAM may also store various programs and data required for device operation. The computing unit, ROM, and RAM are interconnected via a bus. Input / output (I / O) interfaces are also connected to the bus.

[0077] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc. In this application, the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of the present invention according to actual needs. Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units can be implemented in hardware or as software functional units.

[0078] While the present invention has been disclosed above, its scope of protection is not limited thereto. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention, and all such changes and modifications will fall within the scope of protection of the present invention.

Claims

1. A method for deploying a factory-level alarm system, characterized in that... include: A factory-wide model is constructed based on the factory department structure or business object nodes. The factory model includes multiple levels, and each level includes at least one sub-model. There is a mapping relationship between the sub-models of different levels. Import instrument and equipment data and bind it to the corresponding sub-model; Create a new instrument tag number and bind it to the corresponding sub-model and the instrument device. The instrument tag number and the data collector tag number are in one-to-one correspondence. Based on the configuration alarm platform, a plant-wide overview map is established, and each component is bound to the corresponding sub-model, instrument equipment, and instrument tag number.

2. The deployment method of a factory-level alarm system as described in claim 1, characterized in that... The method also includes: Alarm conditions are set for each instrument tag number, including one or a combination of simple threshold alarm, alarm frequency, alarm delay, alarm dead zone, linear alarm, alarm not cleared after confirmation, and price fluctuation alarm.

3. The deployment method of a factory-level alarm system as described in claim 2, characterized in that... The process involves constructing a factory-wide model based on business object nodes, and establishing the hierarchy sequentially according to the order of "scenario - specialty - sub-specialty".

4. The deployment method of a factory-level alarm system as described in claim 2, characterized in that... The factory model is constructed based on the factory area departmental structure, and the hierarchy is established from top to bottom according to the order of "factory area - department - device - unit".

5. A deployment method for a factory-level alarm system as described in any one of claims 1-4, characterized in that... The settings for the instrument and equipment include: equipment number, equipment name, equipment type, specifications, tag number, factory area, factory model, functional location, technical identification, category, and device.

6. A deployment method for a factory-level alarm system as described in any one of claims 1-4, characterized in that... The settings for the instrument tag number also include: tag number name, tag number description, instrument control tag number, priority, factory model, equipment, whether tag number alarm is enabled, and tag number type.

7. A deployment method for a factory-level alarm system as described in any one of claims 1-4, characterized in that... The overall plant overview diagram is a deep integration of alarm status and visual configuration diagram, and different colors are used to distinguish the health status of the instruments and equipment.

8. A deployment device for a factory-level alarm system, characterized in that... include: The factory model unit is used to construct a factory-wide model based on the factory department architecture or business object nodes. The factory model includes multiple levels, and each level includes at least one sub-model. The data entry unit is used to import instrument and equipment data and bind it to the corresponding sub-model; In addition, it is used to bind the newly created instrument tag number to the corresponding sub-model and the instrument device, wherein the instrument tag number and the data collector tag number correspond one-to-one; The configuration display unit is used to establish a plant overview map based on the configuration of the alarm platform, and each component is bound to the corresponding sub-model, the instrument equipment and the instrument tag number.

9. An electronic device, characterized in that, Including memory and processor; The memory is used to store computer programs; The processor is configured to, when executing the computer program, implement a deployment method for a factory-level alarm system as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements a deployment method for a factory-level alarm system as described in any one of claims 1 to 7.

Images