Method and device for managing alarm based on task mode and readable storage medium

Abstract

The invention relates to an alarm management method and device based on a task mode. The method comprises the following steps: screening high-level alarm information and sending the high-level alarm information to RabbitMQ; alarm information is acquired and stored in a database in real time, after analysis and verification, an event is generated according to conditions, a mail is sent, and if not, processing is not carried out; and the operation and maintenance personnel judges whether the event is processed or not, matches the associated task or creates a new work order, judges the scene when creating the new work order, needs double auditing for emergency disposal, and ends after problem checking. The method has the advantages that the generation events are automatically screened, redundant operations are reduced, and the working efficiency is improved; a dual auditing mechanism guarantees the accuracy and normalization of data, and standardizes an emergency processing flow; operation and maintenance information and precipitation experience are recorded, alarm configuration is reversely optimized through the alarm accuracy rate and the active discovery rate, a virtuous cycle is formed, and finally the stability and the anti-risk capacity of the system are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of civil aviation operation and maintenance monitoring, and in particular relates to a method, device, electronic device and computer-readable storage medium for task mode-based management alarms. Background Art

[0002] During civil aviation system operations and maintenance, an alarm system monitors system status in real time. By setting alarm rules for various indicators, such as virtual machines, servers, and interfaces, real-time monitoring and alarms are implemented to help operations personnel quickly respond to emergencies such as server downtime and system anomalies. Currently, most systems use a method of setting alarm recipients to notify relevant personnel immediately via phone, text message, or email when an alarm occurs. However, information about when and how operations personnel handled the alarm can only be retained in personal documents, resulting in untimely, incomplete, and non-standardized records. Summary of the Invention

[0003] This invention addresses the shortcomings of existing alarm recording methods by proposing a new task-based alarm management method and device, providing an automated and standardized recording method for operations and maintenance personnel. This method not only quickly notifies operations and maintenance personnel but also records the alarm time, post-alarm actions, and the effects of these actions. This helps analyze system operating status and accumulates experience, thereby improving the system's ability to operate stably.

[0004] In summary, the present invention adopts Python and Django as the main development framework, and combines RabbitMQ, MySQL, Celery and other technical components to achieve fast, efficient and accurate recording of system alarms, personnel operations and operation results information.

[0005] In order to achieve the above object, the present invention provides the following technical solutions: A first aspect of the present application provides a method for managing alarms based on a task mode, comprising: Filter alarm information and send high-level alarm information to RabbitMQ; Acquire alarm information from the message queue in real time and store it in the database. Parse the alarm information to extract the alarm software name and alarm recipient information. Then verify it against the pre-set software list and personnel responsibilities within the scope of operation and maintenance responsibilities to determine whether the alarm software is within the scope and whether the alarm recipient is an operation and maintenance personnel. If the conditions are met, generate an event and send an email to the alarm recipient. If not, no action is taken. The operation and maintenance personnel determine whether the event needs to be processed. For alarms that need to be processed, they match the alarm information with the existing task data. If the match is successful, the existing task is associated. If the match fails, a new task work order is created. Alarms that do not need to be processed are directly closed. When creating a new work order, determine the scenario to which the processing operation belongs. If it belongs to an emergency response scenario, an emergency response task is generated, which requires approval; otherwise, a troubleshooting task is generated, which ends directly after processing. Emergency response tasks are completed after being double-reviewed and approved by the team leader and emergency manager.

[0006] Optionally, in the method of the present application, the high-level alarm information refers to level three or level four alarm information.

[0007] Optionally, in the method of the present application, the work order for the troubleshooting task records the task occurrence time, processing time, and processing step information; the work order for the emergency response task records the task occurrence time, processing time, processing steps, event type, alarm occurrence time, emergency start and end time, emergency cause, emergency steps, fault level, functional coreness, associated alarms, and processing feedback information.

[0008] A second aspect of the present application provides a device for managing alarms based on task modes, wherein the device implements the steps of the aforementioned method for managing alarms based on task modes when running, and the device includes: Data source unit: The data source unit includes a data source and a workbench; the data source includes alarm data and work order data; the workbench provides the function of adding, deleting, modifying and checking task work orders; Data pre-processing unit: The data pre-processing unit pre-processes the alarm data through the event information module and generates event information from the alarm data that meets the conditions; Emergency Response Unit: The emergency response unit combines event information and task data through the emergency response information module for comprehensive recording and display. A multi-level review mechanism is established. After the operation and maintenance personnel submit an emergency response work order, it must be reviewed and approved by the team leader and emergency manager before the work order is closed. Data storage unit: The data storage unit includes message queues and databases; Data display unit: The data display unit includes emergency management module, event management module and task management module; the event management module displays alarm information, the emergency management module displays emergency response work order information, and the task management module displays task information.

[0009] Optionally, in the data source unit of the device of the present application, the alarm data is provided by an alarm system. After the alarm system detects a system abnormality, an alarm is issued according to a pre-configured alarm rule. The alarm data includes the alarm time, alarm content, and alarm recipient information; The work order data is provided by the operation and maintenance service platform; The user uses the workbench to create different task work orders and record different information according to the work scenarios corresponding to the actual tasks.

[0010] Optionally, the data preprocessing unit in the device of the present application preprocesses the alarm data through the event information module, including: Determine the alarm information level and send high-level alarm information to RabbitMQ, where the high-level alarm information refers to level 3 or 4 alarm information; Determine whether the alarm software is within the scope of operation and maintenance responsibilities through the software list within the scope of operation and maintenance responsibilities pre-set in the event information module; Determine whether the alarm recipient is an operation and maintenance personnel based on the personnel responsibilities pre-set in the event information module; If the alarm information level, alarm software, and alarm recipient all meet the requirements, an event will be generated and an email will be sent to the alarm recipient.

[0011] Optionally, in the emergency handling unit of the device of the present application, the alarm data is recorded in the event information, and the operation and maintenance personnel's processing process and results are recorded in the task data; During the double review process between the team leader and the emergency manager, each step of confirmation triggers the corresponding subsequent processing through Django's signal mechanism, and the confirmation results are recorded in the emergency data.

[0012] Optionally, in the data storage unit of the device of the present application, the message queue is a RabbitMQ message queue, and the alarm data is stored in the RabbitMQ message queue; The database is a MySQL database, and events, tasks, and emergency data are stored in the MySQL database in real time through Django ORM.

[0013] Optionally, in the data display unit of the device of the present application, the WEB front end adopts the Vue.js framework to construct the emergency management module, the event management module and the task management module; The front-end interacts with the back-end through the API interface provided by Django REST Framework, and uses Memcached as the cache layer to cache frequently accessed emergency data in memory.

[0014] A third aspect of the present application provides an electronic device, comprising: a memory and a processor; Memory: used to store computer programs; Processor: used to execute the computer program to implement the steps of the aforementioned method for managing alarms based on task modes.

[0015] A fourth aspect of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the aforementioned method for managing alarms based on task modes are implemented.

[0016] In summary, the present invention provides a method and device for managing alarms based on a task model. In addition to recording and analyzing alarms, the present invention also records and analyzes the operation and maintenance work during the alarm processing process, helping to conduct a more comprehensive evaluation of alarms, and forming a complete knowledge chain, promoting the sharing and inheritance of operation and maintenance experience, thereby improving operation and maintenance efficiency and system stability. The present invention has the following advantages: (1) Automatically obtain alarm information, filter it through software and personnel information, and automatically generate events. This can not only ensure that important alarms that affect system operation are generated as events for recording, but also prevent operation and maintenance personnel from handling too many events, reducing the workload of personnel in recording alarm-related operations and improving work efficiency.

[0017] (2) Alarm management is based on the task model. The entire process requires double confirmation from the team leader and the administrator before the work order is completed. The double review mechanism ensures the accuracy, completeness and standardization of data, and can also help operation and maintenance personnel establish a process for handling emergencies.

[0018] (3) Alarm management based on the task model can record the operation information of operation and maintenance personnel, making production operations traceable and helping operation and maintenance personnel accumulate experience in dealing with emergencies. The alarm accuracy is judged by whether a task is generated, and the alarm active detection rate is obtained by comparing the alarm time with the customer's fault reporting time. The alarm accuracy and alarm active detection rate can be used to reversely evaluate whether the alarm item settings are effective and whether the alarm threshold settings are reasonable, etc., which can help optimize the alarm configuration, improve the alarm accuracy and early detection rate, and form a virtuous cycle. Long-term use can improve the stability of software operation and maintenance, enhance the software's ability to provide early warnings and actively deal with emergencies, and increase the software's risk resistance.

[0019] Other features and advantages of the present invention will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present invention. The purposes and other advantages of the present invention can be realized and obtained by the techniques indicated in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief introduction is given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0021] Figure 1 A schematic diagram of the system structure of a device according to an embodiment of the present invention.

[0022] Figure 2The figure is a schematic diagram of an implementation flow of a method according to an embodiment of the present invention.

[0023] Figure 3 This is a framework diagram of the overall implementation process of a method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0024] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0025] The term "including" and its variations used in this document are open inclusions, i.e., "including but not limited to"; the term "based on" means "at least in part 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".

[0026] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless the context clearly indicates otherwise, it should be understood as "one or more".

[0027] Explanation of terms: Python: An object-oriented, dynamically typed language.

[0028] Django: A Python-based, open source, heavyweight WEB development framework. RabbitMQ: message queue.

[0029] MySQL: database.

[0030] Celery: Distributed asynchronous task queue.

[0031] ORM: Object-Relational Mapping.

[0032] WEB: web page or operation page.

[0033] Vue.js: A framework for building user interfaces.

[0034] Django REST Framework: A toolkit for building network interfaces.

[0035] API: interface.

[0036] Memcached: A distributed caching system.

[0037] Java: Object-oriented programming language.

[0038] Smalltalk: an object-oriented programming language.

[0039] C++: A high-level computer programming language.

[0040] Figure 1 FIG. 1 shows the system structure of a task mode-based alarm management device provided by the present invention. The method of the present invention is implemented by the device, which includes: Data Source Unit: This unit includes the data source and workbench. The data source includes alarm data and work order data. Alarm data is provided by the alarm system. Upon detecting a system anomaly, the alarm system issues an alarm based on preconfigured alarm rules and records information such as the alarm time, alarm content, and recipient. Work order data is provided by the operation and maintenance service platform. The workbench provides the ability to add, delete, modify, and query task work orders. Users can create different task work orders and record different information based on the specific work scenarios.

[0041] Data pre-processing unit: The event information module pre-processes the alarm data and generates event information for the alarm data that meets the conditions. First, determine the alarm level. The alarm level is divided into four levels, of which level three and level four alarms are high-level alarms and need to generate events; level one and level two alarms are usually notification information and do not need to be processed; secondly, determine whether the software is software within the scope of operation and maintenance responsibilities. The event information module pre-sets a list of software within the scope of operation and maintenance responsibilities, and blocks redundant alarm information through list comparison; finally, determine whether the alarm recipient is an operation and maintenance personnel. The alarm recipient can be set to development, operation and maintenance, system users and other personnel. The present invention aims to create a method for alarm management based on task mode for operation and maintenance personnel, so an event is only generated when the contact includes operation and maintenance personnel. In summary, an event is generated if the alarm level, software, and alarm recipient all meet the conditions.

[0042] This invention primarily relates to troubleshooting worksheets and emergency response worksheets. Troubleshooting worksheets record information such as the time the task occurred, processing duration, and processing steps. Emergency response worksheets, in addition to the above information, also record information such as the alarm occurrence time, emergency start and end times, emergency cause, emergency steps, fault level, functional coreness, associated alarms, and processing feedback.

[0043] Emergency Response Unit: Alarm data is recorded in the event information module, and the operations and maintenance personnel's handling process and results are recorded in the task data. Emergency response information combines event information and task data for comprehensive recording and display. A multi-level review mechanism is in place. Emergency response work orders submitted by operations and maintenance personnel must be confirmed by the team leader and then the emergency manager. Each confirmation step triggers subsequent processing via Django's signaling mechanism, and the confirmation results are recorded in the emergency data to ensure data integrity and traceability. Once the emergency response work order is processed, the task work order is closed.

[0044] Data Storage: Alarm data is stored in a RabbitMQ message queue. RabbitMQ's asynchronous processing capabilities enable stable message delivery in a highly concurrent environment. Event, task, and emergency response data are stored in real time in a MySQL database using the Django ORM.

[0045] Data Display Unit: The web frontend utilizes the Vue.js framework, building modules for emergency management, event management, and task management. The event management module displays alarm information, the emergency management module displays emergency response work order information, and the task management module displays task information, allowing users to view relevant information in real time. The frontend interacts with the backend through the API provided by the Django REST Framework. Memcached is used as a caching layer to cache frequently accessed emergency data in memory, reducing database query times, accelerating data response, and improving data display efficiency.

[0046] Figure 2 The present invention provides a method for managing alarms based on a task mode, comprising: filtering alarm information and sending high-level alarm information to RabbitMQ; Acquire alarm information from the message queue in real time and store it in the database. Parse the alarm information to extract the alarm software name and alarm recipient information. Then verify it against the pre-set software list and personnel responsibilities within the scope of operation and maintenance responsibilities to determine whether the alarm software is within the scope and whether the alarm recipient is an operation and maintenance personnel. If the conditions are met, generate an event and send an email to the alarm recipient. If not, no action is taken. The operation and maintenance personnel determine whether the event needs to be processed. For alarms that need to be processed, they match the alarm information with the existing task data. If the match is successful, the existing task is associated. If the match fails, a new task work order is created. Alarms that do not need to be processed are directly closed. When creating a new work order, determine the scenario to which the processing operation belongs. If it belongs to an emergency response scenario, an emergency response task is generated, which requires approval; otherwise, a troubleshooting task is generated, which ends directly after the processing is completed. Emergency response tasks are completed after being double-reviewed and approved by the team leader and emergency manager.

[0047] Figure 3 The figure shows the overall implementation process of a method for managing alarms based on task modes provided by the present invention, which includes the following steps: Step 1: Alarm information screening. Level 3 and 4 alarms are high-level alarms, which are sent to RabbitMQ. Level 1 and 2 alarms are usually notification information and do not need to be sent to RabbitMQ.

[0048] Step 2: Get the information in the message queue in real time and store it in the database. Pre-process the data and determine whether the software is in the scope and whether the alarm recipient is an operation and maintenance personnel through the pre-set software list and personnel responsibilities within the operation and maintenance responsibilities. If the conditions are met, an event is generated and an email is sent to the alarm recipient. If the conditions are not met, no processing is done.

[0049] Step 3: Operations personnel determine whether the event requires action. Alarms requiring action are matched against the task data based on their content. If a match is successful, an association is made. If a match fails, a new task ticket is created. Alarms requiring no action are closed.

[0050] Step 4: When creating a new task ticket, determine the scenario to which the operation belongs. If it belongs to an emergency response scenario, an emergency response task is generated and requires approval. Otherwise, a troubleshooting task is generated and ends after the task is processed. Troubleshooting task tickets record information such as the time the task occurred, processing duration, and processing steps. Emergency response task tickets also include the above information and record information such as the alarm occurrence time, emergency start and end time, emergency cause, emergency steps, fault level, functional coreness, related alarms, and processing feedback.

[0051] Step 5: Emergency response tasks require double confirmation from the team leader and the emergency manager before the work order is completed.

[0052] In order to better understand the technical solution of the present invention, its implementation process and key points are further explained with reference to the following business scenario examples.

[0053] (1) Confirming the accuracy of the alarm based on the task mode A sudden software anomaly triggers a Level 4 alarm. A Level 4 alarm is a high-level alarm. The alarm system pushes the alarm information to RabbitMQ, retrieves the alarm data from the message queue in real time, and stores it in the database. The alarm information is then parsed to extract the alarm software name and recipient information for verification. Verification confirms that the software is within the scope of O&M responsibilities and the alarm recipient is an O&M personnel, meeting the requirements for event generation. An event information is generated in the workbench and an email is sent to the alarm recipient. The event handler is the alarm recipient. The handler determines that the anomaly requires action. However, keywords such as the alarm information are not matched in existing tasks, so a new task is created. Since the alarm handling operation falls under the emergency response category, an emergency response task is generated. When filling out a work order, the alarm information is automatically displayed, and detailed information such as the event type, alarm occurrence time, emergency response start and end times, emergency response cause, emergency response steps, fault level, functional coreness, related alarms, and handling feedback is recorded. The emergency response work order is closed after approval by the team leader and emergency manager. This task verifies that the alarm is accurate and the operation is appropriate.

[0054] (2) Confirming inaccurate alarms based on task mode A sudden software anomaly triggers a Level 4 alarm. A Level 4 alarm is a high-level alarm. The alarm system pushes the alarm information to RabbitMQ, retrieves the alarm data from the message queue in real time, and stores it in the database. The alarm information is then parsed to extract the alarm software name and recipient information for verification. Verification confirms that the software is within the scope of O&M responsibilities and the alarm recipient is an O&M person, meeting the requirements for event generation. Event information is generated in the workbench and an email is sent to the alarm recipient. The event handler is the alarm recipient. If the event handler, based on the system's operating status, determines that no action is required, the event is closed directly without generating a task. The absence of a task, and therefore no O&M action, indicates that the alarm is inaccurate.

[0055] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the apparatus, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, program segment, or a part of code, and the part of the module, program segment, or code contains one or more executable instructions for realizing the specified logical function. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart, can be implemented by a special hardware-based system that performs the specified function or operation, or can be implemented by a combination of special hardware and computer instructions.

[0056] The names of messages or data exchanged between multiple modules in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or data.

[0057] Furthermore, an embodiment of the present invention also discloses an electronic device, comprising: a memory and a processor; The memory is used to store a computer program, and the processor is used to run the computer program to implement the steps of the above-mentioned method for managing alarms based on task modes.

[0058] It is understood that, in addition to the memory and processor, the electronic device may also include an input device such as a keyboard, an output device such as a display, and a communication module. The input device, output device, and communication module communicate with the processor via an I / O interface (i.e., an input / output interface).

[0059] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0060] Furthermore, the present invention also discloses a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can execute the various steps of the method for managing alarms based on task modes disclosed in this application.

[0061] In the context of the present disclosure, a computer-readable storage medium can be a tangible medium that can contain or store a program for use by or in combination with an instruction execution system, device or equipment. The readable storage medium can be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. More specific examples of machine-readable storage media can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0062] In particular, according to an embodiment of the present disclosure, the process described in the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processing device, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0063] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0064] Although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0065] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0066] Those skilled in the art should also understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for managing alarms based on task mode, characterized in that: The method comprises: Filter alarm information and send high-level alarm information to RabbitMQ; Acquire alarm information from the message queue in real time and store it in the database. Parse the alarm information to extract the alarm software name and alarm recipient information. Then verify it against the pre-set software list and personnel responsibilities within the scope of operation and maintenance responsibilities to determine whether the alarm software is within the scope and whether the alarm recipient is an operation and maintenance personnel. If the conditions are met, generate an event and send an email to the alarm recipient. If not, no action is taken. The operation and maintenance personnel determine whether the event needs to be processed. For alarms that need to be processed, they match the alarm information with the existing task data. If the match is successful, the existing task is associated. If the match fails, a new task work order is created. Alarms that do not need to be processed are directly closed. When creating a new work order, determine the scenario to which the processing operation belongs. If it belongs to an emergency response scenario, an emergency response task is generated, which requires approval; otherwise, a troubleshooting task is generated, which ends directly after processing. Emergency response tasks are completed after being double-reviewed and approved by the team leader and emergency manager.

2. The method according to claim 1, characterized in that The high-level alarm information refers to level three or level four alarm information.

3. The method according to claim 1, characterized in that The work order for the troubleshooting task records the task occurrence time, processing time, and processing step information; the work order for the emergency response task records the task occurrence time, processing time, processing steps, event type, alarm occurrence time, emergency start and end time, emergency cause, emergency steps, fault level, functional coreness, related alarms, and processing feedback information.

4. A device for managing alarms based on task modes, characterized in that: The device comprises: Data source unit: The data source unit includes a data source and a workbench; the data source includes alarm data and work order data; the workbench provides the function of adding, deleting, modifying and checking task work orders; Data pre-processing unit: The data pre-processing unit pre-processes the alarm data through the event information module and generates event information from the alarm data that meets the conditions; Emergency Response Unit: The emergency response unit combines event information and task data through the emergency response information module for comprehensive recording and display. A multi-level review mechanism is established. After the operation and maintenance personnel submit an emergency response work order, it must be reviewed and approved by the team leader and emergency manager before the work order is closed. Data storage unit: The data storage unit includes message queues and databases; Data display unit: The data display unit includes emergency management module, event management module and task management module; the event management module displays alarm information, the emergency management module displays emergency response work order information, and the task management module displays task information.

5. The device according to claim 4, characterized in that In the data source unit, the alarm data is provided by the alarm system. After the alarm system detects a system anomaly, it will issue an alarm according to the pre-configured alarm rules. The alarm data includes the alarm time, alarm content, and alarm recipient information. The work order data is provided by the operation and maintenance service platform; The user uses the workbench to create different task work orders and record different information according to the work scenarios corresponding to the actual tasks.

6. The device according to claim 4, characterized in that The data preprocessing unit preprocesses the alarm data through the event information module, including: Determine the alarm information level and send high-level alarm information to RabbitMQ, where the high-level alarm information refers to level 3 or 4 alarm information; Determine whether the alarm software is within the scope of operation and maintenance responsibilities through the software list within the scope of operation and maintenance responsibilities pre-set in the event information module; Determine whether the alarm recipient is an operation and maintenance personnel based on the personnel responsibilities pre-set in the event information module; If the alarm information level, alarm software, and alarm recipient all meet the requirements, an event will be generated and an email will be sent to the alarm recipient.

7. The device according to claim 4, characterized in that In the emergency response unit, the alarm data is recorded in the event information, and the operation and maintenance personnel's processing process and results are recorded in the task data; During the double review process between the team leader and the emergency manager, each step of confirmation triggers the corresponding subsequent processing through Django's signal mechanism, and the confirmation results are recorded in the emergency data.

8. The device according to claim 4, characterized in that In the data storage unit, the message queue is a RabbitMQ message queue, and the alarm data is stored in the RabbitMQ message queue; The database is a MySQL database, and events, tasks, and emergency data are stored in the MySQL database in real time through Django ORM.

9. The device according to claim 4, characterized in that In the data display unit, the WEB front-end uses the Vue.js framework to build emergency management module, event management module and task management module; The front-end interacts with the back-end through the API interface provided by Django REST Framework, and uses Memcached as the cache layer to cache frequently accessed emergency data in memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method for managing alarms based on task modes according to any one of claims 1 to 3 are implemented.

Images