Emergency plan management method, storage medium, program product and electronic device
By acquiring information on emergency response drills, results verification, and changes, the system automatically detects the effectiveness of emergency response plans, thus solving the problem of low efficiency in digital emergency response plan management and achieving efficient and reliable emergency response plan management.
Patent Information
- Application Number
- CN202610313557.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-03-13
- Publication Date
- 2026-06-23
AI Technical Summary
In existing technologies, the effectiveness of digital emergency plans is difficult to maintain in the long term, and manual management is time-consuming and labor-intensive, failing to meet the basic requirements for the real-time performance, accuracy, and reliability of the plans, especially in large-scale, highly complex digital systems.
By acquiring information on emergency response drills, results verification, and changes, the system automatically detects the effectiveness of emergency response plans and conducts objective evaluations based on multi-dimensional information, thereby enabling the management of emergency response plans.
This improves the management efficiency of emergency response plans, ensuring that their effectiveness testing changes from an occasional activity to a continuous process, avoiding the arbitrariness of human judgment, promptly identifying and isolating plans with low effectiveness, preventing operational errors, and maintaining the effectiveness of emergency response plans at a high level.
Smart Images

Figure CN122264565A_ABST
Abstract
Description
Technical Field
[0001] This specification relates to the field of data management, and in particular to an emergency response plan management method, storage medium, program product, and electronic device. Background Technology
[0002] Emergency response plans are a crucial tool for responding to emergencies, system failures, or operational anomalies, and their effectiveness directly impacts an organization's responsiveness and recovery efficiency in crisis scenarios. As enterprises undergo deeper digital transformation, emergency response plans are gradually evolving from traditional paper documents or static electronic files into structured, executable digital forms, thus forming digital emergency response plans.
[0003] However, in actual operation, the availability of digital emergency response plans is difficult to maintain in the long term. On the one hand, over time, frequent personnel changes, responsibilities adjustments, or team restructuring within organizations can lead to the invalidation of designated responsible persons or the failure of communication mechanisms in the emergency response plan. On the other hand, continuous iteration of external processes, ongoing upgrades to IT system architecture, and frequent changes to interface protocols can cause the logic of emergency response plans, originally adapted to specific environments, to gradually become disconnected from the current operational status. In addition, changes in the objective environment, such as infrastructure migration, replacement of third-party services, and updates to security policies, may also render key operational steps in the emergency response plan unenforceable or produce unexpected consequences.
[0004] To ensure the effectiveness of emergency response plans, existing technologies generally rely on manual management, such as periodic drills to simulate failure scenarios and verify the feasibility of the plans. However, manual management of emergency response plans is time-consuming and labor-intensive, especially in large-scale, highly complex digital systems where the number of plans is enormous and their relationships are complex. Traditional manual maintenance methods can no longer meet the basic requirements for the real-time performance, accuracy, and reliability of the plans. Summary of the Invention
[0005] This specification provides an emergency response plan management method, storage medium, program product, and electronic device, which can solve the above-mentioned problems. The technical solution is as follows: Firstly, embodiments of this specification provide an emergency response plan management method, the method comprising: Obtain emergency response plan drill information, result verification information, and change information; wherein, the drill information indicates the historical drill execution status of the emergency response plan, the verification result information includes at least functional verification results and transaction verification results, and the change information includes change records of environmental elements on which the emergency response plan depends; Based on the exercise information, the result verification information, and the change information, determine the effectiveness status of the emergency plan; The emergency response plan is managed according to its effectiveness status.
[0006] Secondly, embodiments of this specification provide an emergency response plan management device, the device comprising: The information acquisition module is used to acquire the exercise information, result verification information, and change information of the emergency plan; wherein, the exercise information indicates the historical exercise execution status of the emergency plan, the verification result information includes at least the functional verification results and transaction verification results, and the change information includes the change records of the environmental elements on which the emergency plan depends; The status determination module is used to determine the effectiveness status of the emergency plan based on the exercise information, the result verification information, and the change information. The emergency plan management module is used to manage the emergency plan based on its effectiveness status.
[0007] Thirdly, embodiments of this specification provide a computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the above-described method steps.
[0008] Fourthly, embodiments of this specification provide a computer program product that stores multiple instructions adapted for loading by a processor and executing the above-described method steps.
[0009] Fifthly, embodiments of this specification provide an electronic device that may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to execute the above-described method steps.
[0010] The beneficial effects of the technical solutions provided in some embodiments of this specification include at least the following: In the embodiments of this specification, the effectiveness status of emergency plans can be periodically and automatically detected, transforming the effectiveness detection of emergency plans from an occasional activity relying on manual organization into a continuous process. This effectively supports the daily maintenance of a large number of emergency plans and improves management efficiency. Furthermore, the effectiveness status of emergency plans is determined based on drill information, result verification information, and change information. Based on an objective and quantifiable evaluation system, and combining information from multiple dimensions, the effectiveness status of emergency plans can be reliably and credibly assessed, avoiding the arbitrariness of human judgment. Furthermore, emergency plans are managed according to their effectiveness status, promptly identifying and isolating emergency plans with low effectiveness status. This prevents operational errors during the execution of emergency plans with low effectiveness status from causing secondary failures, maintaining the effectiveness status of emergency plans at a consistently high level, thereby effectively improving the ability of emergency plans to protect against real-world events. Attached Figure Description
[0011] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0012] Figure 1 This is a schematic diagram of the architecture of an emergency response plan management method provided in the embodiments of this specification; Figure 2 This is a flowchart illustrating an emergency response plan management method provided in the embodiments of this specification; Figure 3 This is a flowchart illustrating an emergency response plan management method provided in the embodiments of this specification; Figure 4 This is a flowchart illustrating an emergency response plan management method provided in the embodiments of this specification; Figure 5 This is a flowchart illustrating an emergency response plan management method provided in the embodiments of this specification; Figure 6 This is a flowchart illustrating an emergency response plan management method provided in the embodiments of this specification; Figure 7 This is a schematic diagram of the structure of an emergency response plan management device provided in the embodiments of this specification; Figure 8 This is a schematic diagram of the structure of an electronic device provided in the embodiments of this specification. Detailed Implementation
[0013] The technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.
[0014] In the description of this specification, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. In the description of this specification, it should be noted that, unless otherwise expressly specified and limited, "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. Those skilled in the art can understand the specific meaning of the above terms in this specification based on the specific circumstances. Furthermore, in the description of this specification, unless otherwise stated, "multiple" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.
[0015] The present specification will now be described in detail with reference to specific embodiments.
[0016] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the features, information, and data involved in this specification were all obtained under full authorization.
[0017] like Figure 1 As shown, Figure 1 This is a flowchart illustrating an emergency response plan management method provided in the embodiments of this specification. Figure 1 It includes at least a server 101 for implementing emergency response plan management methods, and also includes multiple electronic devices for uploading or storing emergency response plans. These multiple electronic devices include at least electronic device 1021, electronic device 1022, and electronic device 1023. It is understood that... Figure 1 The number of servers and electronic devices shown is for illustrative purposes only, and the embodiments in this specification do not impose any limitations on them.
[0018] The aforementioned server 101 can be a standalone server device, such as a rack-mounted, tower-mounted, or cabinet-type server device, or a workstation, mainframe computer, or other hardware device with strong computing power; it can also be a server cluster composed of multiple servers. The servers in the service cluster can be composed in a symmetrical manner, where each server is functionally and hierarchically equivalent in the transaction chain, and each server can provide services to the outside world independently. Providing services independently can be understood as not requiring the assistance of other servers.
[0019] For example, a server can be multiple physical servers, each with independent hardware. Alternatively, a server can be multiple virtual servers deployed within the same hardware resource pool. Virtual server deployment methods include, but are not limited to, VMware, VirtualBox, and Virtual PC.
[0020] It is understood that server 101 also possesses other service capabilities and functions to complete the tasks described in the following embodiments. For example, server 101 also provides portal services, resource management services, and CI / CD services, etc.
[0021] Electronic devices include, but are not limited to: wearable devices, handheld devices, personal computers, tablets, in-vehicle devices, smartphones, computing devices, or other processing devices connected to a wireless modem. Electronic devices may have different names in different networks, such as: user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, personal digital assistant (PDA), and electronic devices in 5G networks or future evolved networks.
[0022] In the embodiments of this specification, electronic devices such as electronic devices 1021, 1022, and 1023 may also be equipped with display devices. These display devices can be various devices capable of display functions, such as cathode ray tube displays (CR), light-emitting diode displays (LED), electronic ink screens, liquid crystal displays (LCD), and plasma display panels (PDP). For example, a user can use the display device on electronic device 1021 to view the status report of the emergency plan to server 101, or send pre-contact information configuration commands based on the pre-contact information configuration request sent by server 101.
[0023] Multiple electronic devices and multiple servers can communicate through communication links established by communication protocols. For example, the network can be a wireless network or a wired network. Wireless networks include, but are not limited to, cellular networks, wireless LANs, infrared networks, or Bluetooth networks. Wired networks include, but are not limited to, Ethernet, universal serial bus (USB), or controller area networks. In one or more embodiments of the specification, technologies and / or formats including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network (such as target compressed packets). Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), and Internet Protocol Security (IPsec) can be used to encrypt all or some of the links. In other embodiments, customized and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.
[0024] In one embodiment, such as Figure 2 The diagram shown is a flowchart illustrating an emergency response plan management method provided in an embodiment of this specification. This method can be implemented using a computer program and can run on an emergency response plan management device based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone utility application.
[0025] Specifically, the emergency response plan management methods include: S102. Obtain information on emergency response drills, results verification, and changes.
[0026] The exercise information indicates the historical execution status of the emergency response plan, the verification result information includes at least the functional verification results and the transaction verification results, and the change information includes the change records of the environmental elements on which the emergency response plan depends.
[0027] Specifically, exercise information can be obtained after the system automatically triggers the contingency plan exercise process, or it can be received when the user sends it to the processor through electronic devices, or it can be obtained synchronously from external platforms such as the exercise management system.
[0028] Exercise information is used to reflect whether the emergency response plan has been fully validated in historical practice and the timeliness of that validation. Exercise information may include, but is not limited to, the following: the execution time of the most recent exercise; whether the exercise was successfully completed, for example, successful, failed, or partially successful; the type of exercise, such as fault injection, process review, or full-link stress testing; the scope of the exercise, such as the system modules and transaction scenarios involved; whether the exercise was executed automatically; whether an exercise was conducted after the validity status of the emergency response plan changed; the duration of the exercise; and whether it included reverse rollback operations.
[0029] Multiple result verification items are pre-set during the emergency plan creation or configuration phase and stored as metadata for the emergency plan. After the emergency plan is executed, the exercise results are obtained. The exercise results are analyzed based on the multiple result verification items to obtain structured result verification information. The result verification information includes at least functional verification results and transaction verification results.
[0030] Functional verification results reflect whether the technical processes of the emergency plan are executed as expected. For example, verifying interface availability includes checking the response status, response latency, and error code distribution of external interfaces called by the emergency plan; verifying resource accessibility includes checking the connectivity and load status of servers, databases, and network devices involved in the emergency plan; and verifying the validity of permissions in the emergency plan includes verifying the account permissions and certificate validity required for execution. Transaction verification results reflect the impact of the emergency plan's execution on real transactions. For example, verifying the correctness of the process logic; verifying the accuracy of pre-defined data mappings in the emergency plan includes checking the mapping matching degree between the emergency plan's input / output parameters and actual transaction data fields; and checking the compliance of the emergency plan with relevant regulations and laws.
[0031] Change information is monitored in real time or periodically synchronized with entity change events related to the emergency response plan. When changes are detected in related system components, interfaces, organizations, personnel, resources, processes, etc., the change time, content, and scope of impact are automatically recorded and linked to the affected emergency response plan. Change information is used to identify risks where the emergency response plan logic does not match the current operational status due to the evolution of the external environment.
[0032] For example, changes to the emergency response plan may include, but are not limited to: whether the person in charge specified in the emergency response plan has changed positions or left the company, whether the API interface version called by the emergency response plan has been upgraded or deprecated, whether the IP address, domain name, and database connection string of the associated system have changed, whether the configuration of the middleware (such as message queues and caches) has been adjusted, and whether the relevant transaction process has been restructured, causing the steps of the emergency response plan to become invalid.
[0033] In the embodiments of this specification, a globally unique identifier can be assigned to each emergency plan, and the exercise information, result verification information and change information of the emergency plan can all be uniformly stamped with a standard timestamp to achieve timestamp alignment, thereby supporting time correlation analysis across information types.
[0034] S104. Determine the effectiveness status of the emergency plan based on the exercise information, result verification information, and change information.
[0035] The effectiveness status of an emergency response plan can be understood as whether the plan's structured logic, specified operational steps, and associated resources, under the current configuration, system architecture, and process conditions, can achieve the expected emergency objectives. In the embodiments of this specification, the effectiveness status of an emergency response plan is divided into several different levels, including the "fresh" level, which indicates that the emergency response plan can achieve the emergency objectives on schedule; the "less fresh" level, which indicates that the emergency response plan has a slight risk of timeliness but may still achieve the emergency objectives; the "critical" level, which indicates that the emergency response plan has a significant risk of timeliness and requires confirmation before execution; and the "ineffective" level, which indicates that the emergency response plan lacks emergency support capabilities.
[0036] The determination of the effectiveness status does not rely on a single information dimension, but rather on the fusion calculation of exercise information, verification result information and change information, and the analysis of multiple items included in each piece of information to achieve a comprehensive judgment of multi-source information and determine the level of effectiveness status of the emergency plan.
[0037] Specifically, if the emergency response plan has been thoroughly validated recently based on exercise information, and its content has a high degree of matching with the actual execution environment, then the emergency response plan is considered to have a higher level of effectiveness. Conversely, if the exercise information includes factors such as exercise frequency being lower than the preset baseline, insufficient exercise completeness, a continuously declining historical exercise pass rate, or the emergency response plan not being exercised after information changes, then these factors will be considered as factors that downgrade the effectiveness status.
[0038] The functional verification results in the verification information indicate that the technical resources upon which the emergency plan depends are unavailable, causing the technical processes to fail to execute as expected. This will serve as a degradation factor, impacting the emergency plan's effectiveness status to a lower level. The transaction verification results in the verification information reflect the degree of impact on actual transactions. The greater the impact, such as incorrect logic, inaccurate data mapping, or non-compliance, the more likely it is to lead to a degradation in the emergency plan's effectiveness status.
[0039] Changes to core elements in the emergency response information (such as the transfer of responsible personnel or the shutdown of key equipment) will directly lead to a significant decrease in timeliness. Even if the emergency response plan has not been drilled, its effectiveness can be determined based on the change information.
[0040] The impact of the above information on the validity status can be calculated through weighted scoring, rule engines, or state machine transitions. For example, a validity status of "fresh" must simultaneously meet the following conditions: the most recent exercise in the exercise information is ≤ 30 days ago; both functional and transaction verification results in the verification results information have passed; and the core elements in the change information have not changed or have been exercised after the change. If any of the above conditions are not met, the validity status will be downgraded. As another example, a validity status of "second-fresh" must meet any of the following conditions: the most recent exercise in the exercise information is > 30 days ago; the verification results information after the most recent exercise indicates that either the functional or transaction verification result failed; the core elements in the change information have changed; or the change information has changed but has not been exercised after the change. A validity status of "critical" must meet the following condition: the most recent exercise in the exercise information is > N days ago (N can be any number, such as 50 days). The validity status of setting the "failure" level must meet the following conditions: the most recent exercise in the exercise information is more than M days ago (M can be any number, such as 60 days).
[0041] S106. Manage the emergency response plan according to its effectiveness status.
[0042] Based on the effectiveness level of the emergency response plan and the downgrade factors affecting its effectiveness, the emergency response plans are managed in a differentiated hierarchical manner. The goal of managing emergency response plans is to restore their effectiveness, preferably to a high level. For example, an emergency response plan at the "partially fresh" level would be restored to the "fresh" level.
[0043] Since the effectiveness status reflects the availability level of the emergency plan in the current environment, and the exercise information, result verification information, or change information include downgrade factors that affect the effectiveness status of the emergency plan from a high level, as well as the goal of upgrading the effectiveness level of the emergency plan, the emergency plan is managed according to the effectiveness status level, downgrade factors, and management objectives to achieve optimized resource allocation, proactive risk prevention and control, and improved maintenance efficiency.
[0044] For example, for an emergency plan with an effectiveness status of "fresh," only its availability needs to be maintained. As another example, for an emergency plan with an effectiveness status of "slightly fresh," and the degradation factor affecting its effectiveness status to "slightly fresh" is drill information—specifically, if the most recent drill event was more than 30 days ago—then the management of the emergency plan involves conducting drills. As yet another example, for an emergency plan with an effectiveness status of "slightly fresh," and the degradation factor is a failed functional verification result, the management of the emergency plan involves detecting and reconfiguring the failed functional verification content, such as reconfiguring a pre-set external interface. As yet another example, for an emergency plan with an effectiveness status of "critical," and the degradation factor is a significant change in the emergency plan's information, the management of the emergency plan involves conducting a new drill. For example, for emergency plans whose effectiveness status is at the "failed" level, the management of the emergency plan involves sending a notification to the target device that the emergency plan has failed, so that the user can reconfigure and rehearse the emergency plan.
[0045] In one embodiment, managing an emergency plan based on its effectiveness status includes managing the emergency plan when its effectiveness status is downgraded or falls below a threshold.
[0046] Specifically, when the effectiveness status of the emergency plan is downgraded, for example from the "fresh" level to the "critical" level, or when the current effectiveness status is below a threshold, such as the "critical" or "ineffective" level, management operations on the emergency plan are triggered.
[0047] Based on the downgrade factors affecting the effectiveness of the emergency response plan, and based on the objectives of restoring the effectiveness of the emergency response plan, corresponding management operations are carried out on the emergency response plan.
[0048] In this embodiment, when the effectiveness of an emergency plan is downgraded or falls below a threshold, the emergency plan is managed. This allows for the identification of availability degradation trends before the emergency plan becomes ineffective, enabling timely management of the emergency plan. Additionally, management measures such as freezing emergency plans that have been in an ineffective state for a long time can be implemented to reduce interference from the emergency plan in emergency decision-making and improve the overall accuracy and reliability of the emergency system's response.
[0049] In the embodiments of this specification, the effectiveness status of emergency plans can be periodically and automatically detected, transforming the effectiveness detection of emergency plans from an occasional activity relying on manual organization into a continuous process. This effectively supports the daily maintenance of a large number of emergency plans and improves management efficiency. Furthermore, the effectiveness status of emergency plans is determined based on drill information, result verification information, and change information. Based on an objective and quantifiable evaluation system, and combining information from multiple dimensions, the effectiveness status of emergency plans can be reliably and credibly assessed, avoiding the arbitrariness of human judgment. Furthermore, emergency plans are managed according to their effectiveness status, promptly identifying and isolating emergency plans with low effectiveness status. This prevents operational errors during the execution of emergency plans with low effectiveness status from causing secondary failures, maintaining the effectiveness status of emergency plans at a consistently high level, thereby effectively improving the ability of emergency plans to protect against real-world events.
[0050] In one embodiment, such as Figure 3 The diagram shown is a flowchart illustrating an emergency response plan management method provided in an embodiment of this specification. This method can be implemented using a computer program and can run on an emergency response plan management device based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone utility application.
[0051] Specifically, the emergency response plan management methods include: S202. Obtain information on emergency response drills, results verification, and changes.
[0052] The above S102 will not be repeated here.
[0053] S204. According to the preset target weight allocation strategy, assign weights to the exercise information, result verification information and change information respectively.
[0054] The purpose of weight allocation is to reflect the varying degrees of impact of different types of information on the effectiveness of an emergency response plan. Specifically, a weight allocation strategy is a pre-configured set of parameters or rules used to characterize the relative importance of three different types of information: exercise information, result verification information, and change information. The assigned weights can be numerical (such as decimals or percentages) or non-numerical, such as priority indicators or condition trigger flags, as long as they can guide the subsequent effectiveness determination logic.
[0055] Before each assessment of the effectiveness of the emergency response plan, the corresponding target weight allocation strategy is first loaded, and then the three types of information currently acquired are assigned corresponding weights according to the target weight allocation strategy.
[0056] In one embodiment, based on the type of emergency plan, a target weight allocation strategy corresponding to the emergency plan is determined from multiple preset weight allocation strategies.
[0057] During the emergency plan creation or initialization phase, the user or the automatic classification module assigns a plan type to the emergency plan. For example, an emergency plan for a power outage in a data center falls under the infrastructure disaster recovery type; an emergency plan for payment transaction recovery falls under the transaction continuity maintenance type; or an emergency plan falls under the compliance detection type. Pre-configured weight allocation strategies are associated with various plan types, and each weight allocation strategy defines a set of specific weight configurations for exercise information, result verification information, and change information.
[0058] For example, for contingency plans related to transaction continuity, such as those used for payment transaction recovery, since the execution results directly affect user experience and fund security, the preset weight allocation strategy could be 50% for result verification information, 30% for change information, and 20% for drill information.
[0059] For example, for emergency plans for infrastructure disaster recovery, the frequency of historical drills is low due to the cost and safety constraints of drills. However, their feasibility is highly dependent on the completeness of the operational procedures. Therefore, the matching strategy may be set as follows: drill information accounts for 60%, result verification information accounts for 20%, and change information accounts for 20%.
[0060] For example, for emergency plans of the compliance testing type, such as those used to report when a data leak is detected, if a uniform weight is used, it is easy to downgrade high-value plans with low drill frequency, or to allow plans that are frequently drilled but have never been verified.
[0061] In this embodiment, different weight allocation strategies are set for different types of emergency plans. Among multiple preset weight allocation strategies, the target weight allocation strategy corresponding to the emergency plan is determined so as to assign weights to exercise information, result verification information and change information respectively. This can significantly improve the accuracy of effectiveness status determination and avoid misjudgment.
[0062] S206. Determine the effectiveness status of the emergency plan based on the weights and contents corresponding to the exercise information, result verification information, and change information.
[0063] After assigning weights to the exercise information, result verification information, and change information respectively, the effectiveness status of the emergency plan is comprehensively determined by combining the specific content of each piece of information.
[0064] Specifically, the three types of information are quantified or structured to generate assessable indicator values. For example, the exercise timeliness score is calculated based on the recent exercise time decay function in the exercise information; the verification pass rate is calculated based on each verification item included in the result verification information; and the environmental stability score is calculated based on the change information. Furthermore, according to a preset target weight allocation strategy, the weight values corresponding to the exercise information, result verification information, and change information are obtained respectively. Further, a weighted fusion method, such as weighted summation or weighted average, is used to calculate the comprehensive evaluation value, and the level of the emergency plan is determined based on the preset range in which this value falls.
[0065] S208. Manage emergency response plans according to their effectiveness status.
[0066] The above S106 will not be repeated here.
[0067] In the embodiments of this specification, the effectiveness status of emergency plans can be periodically and automatically detected, transforming the effectiveness detection of emergency plans from an occasional activity relying on manual organization into a continuous process. This effectively supports the daily maintenance of a large number of emergency plans and improves management efficiency. Furthermore, the effectiveness status of emergency plans is determined based on drill information, result verification information, and change information. Based on an objective and quantifiable evaluation system, and combining information from multiple dimensions, the effectiveness status of emergency plans can be reliably and credibly assessed, avoiding the arbitrariness of human judgment. Furthermore, emergency plans are managed according to their effectiveness status, promptly identifying and isolating emergency plans with low effectiveness status. This prevents operational errors during the execution of emergency plans with low effectiveness status from causing secondary failures, maintaining the effectiveness status of emergency plans at a consistently high level, thereby effectively improving the ability of emergency plans to protect against real-world events.
[0068] In one embodiment, such as Figure 4 The diagram shown is a flowchart illustrating an emergency response plan management method provided in an embodiment of this specification. This method can be implemented using a computer program and can run on an emergency response plan management device based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone utility application.
[0069] Specifically, the emergency response plan management methods include: S302. Obtain information on emergency response drills, results verification, and changes.
[0070] See S102 above, which will not be repeated here.
[0071] S304. Determine the effectiveness status of the emergency plan based on the exercise information, result verification information, and change information.
[0072] See S104 above, which will not be repeated here.
[0073] S306. Based on the pre-defined correlation between different effectiveness states and management actions, determine the target management actions corresponding to the effectiveness states of the emergency plan.
[0074] In this embodiment, multiple validity status levels are preset, and corresponding management actions are associated with different validity status levels. Based on the validity status level of the emergency plan, the target management action associated with that level is determined.
[0075] For example, four validity states are preset: "Fresh", "Partially Fresh", "Critical", and "Invalid". The target management action associated with the "Fresh" level is to maintain the availability of the emergency plan; the target management action associated with the "Partially Fresh" level is to configure advance information and enhance drills; the target action associated with the "Critical" level is to increase drills; and the target action associated with the "Invalid" level is to take the emergency plan offline.
[0076] S308. Based on target management actions, manage emergency response plans.
[0077] For example, if the effectiveness status of an emergency plan is at the "secondary fresh" level, the emergency plan will be managed based on the target management actions corresponding to the "secondary fresh" level, including configuring the pre-configuration information of the emergency plan and enhancing drills.
[0078] In this embodiment, the effectiveness status and management actions are externalized in the form of a strategy through a mapping relationship. Users can flexibly adjust the classification of effectiveness status levels and the content of management actions associated with different levels of effectiveness status according to their needs, thereby improving the scalability of emergency plan management and improving management efficiency.
[0079] In one embodiment, an emergency plan status report is sent to the target device based on the effectiveness status of the emergency plan.
[0080] The status reporting system aims to deliver the effectiveness status and evaluation results of emergency plans to the users corresponding to the target equipment in a structured, readable, and operable format, so as to support users in making subsequent decisions and taking actions based on the emergency plan.
[0081] Status reports are structured data messages such as JSON and XML, or visual notifications such as emails and work orders. The content of the status report can dynamically adapt to the effectiveness status of the emergency. For example, when the effectiveness status is high, the status report focuses on "the emergency plan is confirmed to be usable"; when the effectiveness status is medium-high or medium-low, the status report emphasizes "risk warnings for the emergency plan" and provides lightweight optimization suggestions; when the effectiveness status is low, the status report can include highlighted warnings, failure details, and mandatory review requirements, and can also include the specific content of the emergency plan.
[0082] The status report may include, but is not limited to, the following information: basic information about the contingency plan, such as the plan ID, name, domain, and responsible person; current validity status, such as "fresh," "medium fresh," "critical," or "ineffective" level; a summary of the basis for status determination, such as exercise information including the most recent exercise time and whether it was successful, result verification information including the functional verification pass rate and whether key verification indicators meet the standards, change information including whether key dependency changes have occurred; and suggested management actions.
[0083] In this embodiment, an emergency plan status report is sent to the target device so that the user of the target device can view content related to the effectiveness status of the emergency plan based on the status report, and better maintain and manage the emergency plan.
[0084] In the embodiments of this specification, the effectiveness status of emergency plans can be periodically and automatically detected, transforming the effectiveness detection of emergency plans from an occasional activity relying on manual organization into a continuous process. This effectively supports the daily maintenance of a large number of emergency plans and improves management efficiency. Furthermore, the effectiveness status of emergency plans is determined based on drill information, result verification information, and change information. Based on an objective and quantifiable evaluation system, and combining information from multiple dimensions, the effectiveness status of emergency plans can be reliably and credibly assessed, avoiding the arbitrariness of human judgment. Furthermore, emergency plans are managed according to their effectiveness status, promptly identifying and isolating emergency plans with low effectiveness status. This prevents operational errors during the execution of emergency plans with low effectiveness status from causing secondary failures, maintaining the effectiveness status of emergency plans at a consistently high level, thereby effectively improving the ability of emergency plans to protect against real-world events.
[0085] In one embodiment, such as Figure 5 The diagram shown is a flowchart illustrating an emergency response plan management method provided in an embodiment of this specification. This method can be implemented using a computer program and can run on an emergency response plan management device based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone utility application.
[0086] Specifically, the emergency response plan management methods include: S402. Obtain information on emergency response drills, results verification, and changes.
[0087] See S102 above, which will not be repeated here.
[0088] S404. Determine the effectiveness status of the emergency response plan based on the exercise information, result verification information, and change information.
[0089] See S104 above, which will not be repeated here.
[0090] S406. Based on the effectiveness status of the emergency plan, configure the emergency plan with prerequisite information to obtain the prerequisite information configuration status.
[0091] Pre-emptive information refers to the set of metadata that needs to be pre-defined before the formal drill or execution of a contingency plan, used to control the drill methods and verification standards. Its core function is to define "how to drill" and "how to judge," ensuring that the drill process is controllable and the results are evaluable. In other words, pre-emptive information includes drill methods and / or result verification items.
[0092] The exercise method is used to control the execution strategy and scope of impact of the exercise, including: execution mode, automatic or manual triggering; exercise type, such as fault injection, process review, full-link stress testing, rollback verification; target environment, such as production environment, pre-release environment, sandbox environment; exercise cycle, such as one-time / periodic (e.g., every 7 days); timeout control, including maximum exercise duration, automatic termination upon timeout.
[0093] Results verification items define the metrics that need to be automatically verified after the exercise, including functional verification items and transaction verification items. Functional verification results reflect whether the technical processes of the emergency plan are executed as expected, verifying interface availability, resource accessibility, and the validity of permissions in the emergency plan. Transaction verification results reflect the impact of the emergency plan's execution on real-world transactions, such as verifying the correctness of process logic, the accuracy of pre-defined data mappings, and checking the compliance of the emergency plan with relevant regulations and rules.
[0094] In one embodiment, a preliminary information configuration request is sent to the target device based on the effectiveness status of the emergency plan; based on the preliminary information configuration instruction returned by the target device based on the preliminary information configuration request, the preliminary information configuration of the emergency plan is performed to obtain the preliminary information configuration status.
[0095] In this embodiment, the pre-configuration information is configured collaboratively by humans and machines. Some items in the pre-configuration information are configured automatically, while others are configured through pre-configuration information configuration instructions returned by the user. The target device refers to the terminal or system used by the person responsible for the contingency plan or the operation and maintenance user. The pre-configuration information configuration instructions are used to receive the recommended configuration in the pre-configuration information configuration request, and may also include adjusting the exercise method, such as changing "automatic exercise" to "manual triggering", adding or deleting result verification items, such as adding "SMS notification success rate" verification, and specifying the exercise time window or environment.
[0096] Upon receiving the pre-configuration information instruction, the exercise method and result verification items of the pre-configuration information instruction are parsed, and the parsing results are written into the metadata storage of the emergency plan to form the pre-configuration information, so that the subsequent exercise scheduling engine will strictly execute according to this configuration.
[0097] In this embodiment, emergency plans are configured with pre-configured information through a combination of automation efficiency and human controllability. This improves configuration efficiency while preventing automated misjudgments through human verification, reducing the risk of configuration errors and minimizing drill failures or production safety accidents caused by improper configuration.
[0098] In one embodiment, the emergency plan is configured with prerequisite information based on its effectiveness status, drill information, result verification information, and change information to obtain the prerequisite information configuration status.
[0099] Based on the specific content affecting the effectiveness status in the emergency response plan's drill information, result verification information, and change information, the emergency response plan's pre-emptive information configuration is performed to obtain the pre-emptive information configuration status. Specifically, the drill methods in the pre-emptive information are configured based on the historical drill methods in the drill information, and the drill methods affecting the effectiveness status are modified. For example, based on the drill information showing no drills for 30 days, the pre-emptive information is configured to have drills every 7 days. The pre-emptive information is configured based on the historical functional verification results and transaction verification results in the result verification information. Items that have changed in the change information are added to the result verification items in the pre-emptive information configuration.
[0100] In this embodiment, the effectiveness status of the emergency plan, as well as exercise information, result verification information, and change information, are integrated to configure the emergency plan in advance, thereby achieving a more accurate and context-aware configuration of the advance information and supporting intelligent decision-making in complex scenarios.
[0101] S408. Based on the pre-configured information, conduct drills for the emergency response plan, and manage the emergency response plan based on the drill results.
[0102] The scheduling and exercise engine reads the pre-configuration information, deploys the target environment required for the exercise, and collects the data needed for verification. It then triggers the emergency response plan's exercise process according to the exercise method, such as calling the plan script or injecting faults, and records execution logs, timestamps, and operation steps. After the exercise, it retrieves the result verification items from the pre-configuration information, compares each item against the judgment rules for the result verification items, and generates the exercise results.
[0103] The results of the exercise can include metadata such as start / end time, execution mode, environment, and whether it was successfully completed. It can also include functional verification results and transaction verification results, as well as records of abnormal events, including errors, timeouts, and unexpected behaviors that occurred during the exercise, and resource consumption data. Based on the specific content of the exercise results, the emergency response plan will be managed accordingly.
[0104] In one embodiment, the emergency response plan is practiced based on the prior information configuration, and the effectiveness status of the emergency response plan is updated based on the practice results.
[0105] The results of the drills will be used as new assessment inputs to recalculate or directly adjust the effectiveness status of the emergency plan. For example, if the drill is successfully completed and all result verification items are completed, the effectiveness status of the emergency plan will be upgraded. Conversely, if the drill is successfully completed but some result verification items are found to be non-compliant, the effectiveness status of the emergency plan will be downgraded.
[0106] like Figure 6 As shown, Figure 6 This is a flowchart illustrating an emergency response plan management method provided in the embodiments of this specification. For a specific emergency response plan's management cycle, the following steps are triggered: A101, updating the validity status; A102, configuring prerequisite information; A103, periodically executing drills; A104, obtaining drill results after the drills; and A101, updating the validity status again based on the drill results. Based on these multiple steps, periodic management of the emergency response plan is achieved.
[0107] In the embodiments of this specification, the effectiveness status of emergency plans can be periodically and automatically detected, transforming the effectiveness detection of emergency plans from an occasional activity relying on manual organization into a continuous process. This effectively supports the daily maintenance of a large number of emergency plans and improves management efficiency. Furthermore, the effectiveness status of emergency plans is determined based on drill information, result verification information, and change information. Based on an objective and quantifiable evaluation system, and combining information from multiple dimensions, a credible and reliable assessment of the effectiveness status of emergency plans can be conducted, avoiding the arbitrariness of human judgment. Furthermore, emergency plans are managed according to their effectiveness status, promptly identifying and isolating emergency plans with low effectiveness status. This prevents operational errors during the execution of emergency plans with low effectiveness status from causing secondary failures, maintaining the effectiveness status of emergency plans at a consistently high level, thereby effectively improving the ability of emergency plans to protect against real-world events.
[0108] The following are embodiments of the apparatus described in this specification, which can be used to execute the embodiments of the methods described in this specification. For details not disclosed in the apparatus embodiments of this specification, please refer to the embodiments of the methods described in this specification.
[0109] Please see Figure 7 This diagram illustrates the structure of an emergency response plan management device provided in an exemplary embodiment of this specification. The emergency response plan management device can be implemented as all or part of a device through software, hardware, or a combination of both. The emergency response plan management device includes an information acquisition module 501, a status determination module 502, and a plan management module 503.
[0110] The information acquisition module 501 is used to acquire the exercise information, result verification information and change information of the emergency plan; wherein, the exercise information indicates the historical exercise execution status of the emergency plan, the verification result information includes at least the functional verification result and the transaction verification result, and the change information includes the change record of the environmental elements on which the emergency plan depends; The status determination module 502 is used to determine the effectiveness status of the emergency plan based on the exercise information, the result verification information, and the change information. The emergency plan management module 503 is used to manage the emergency plan according to its effectiveness status.
[0111] In one or more embodiments, the state determination module 502 includes: The weight allocation unit is used to allocate weights to the exercise information, the result verification information, and the change information according to a preset target weight allocation strategy. The status determination unit is used to determine the effectiveness status of the emergency plan based on the weights and contents corresponding to the exercise information, the result verification information, and the change information, respectively.
[0112] In one or more embodiments, the weight allocation unit includes: The weight allocation subunit is used to determine the target weight allocation strategy corresponding to the emergency plan from multiple preset weight allocation strategies based on the type of the emergency plan.
[0113] In one or more embodiments, the contingency plan management module 503 includes: The target determination unit is used to determine the target management action corresponding to the effectiveness status of the emergency plan based on the preset correlation between different effectiveness statuses and management actions. The target management unit is used to manage the emergency plan based on the target management actions.
[0114] In one or more embodiments, the contingency plan management module 503 includes: The pre-configuration unit is used to configure pre-configuration information for the emergency plan based on its effectiveness status, thereby obtaining the pre-configuration information; wherein, the pre-configuration information includes the exercise method and / or result verification items; The exercise result unit is used to conduct exercises on the emergency plan based on the configuration of the prior information, and to manage the emergency plan based on the exercise results.
[0115] In one or more embodiments, the pre-configuration unit includes: The first configuration subunit is used to send a preliminary information configuration request to the target device based on the effectiveness status of the emergency plan. The second configuration subunit is used to configure the emergency plan with prerequisite information according to the prerequisite information configuration instruction returned by the target device based on the prerequisite information configuration request, and to obtain the prerequisite information configuration status.
[0116] In one or more embodiments, the pre-configuration unit includes: The third configuration subunit is used to configure the emergency plan with prerequisite information based on the effectiveness status of the emergency plan, the exercise information, the result verification information, and the change information, so as to obtain the prerequisite information configuration status.
[0117] In one or more embodiments, the exercise result unit includes: The status update subunit is used to conduct drills on the emergency plan based on the prior information configuration, and update the effectiveness status of the emergency plan based on the drill results.
[0118] In one or more embodiments, the contingency plan management module 503 includes: The trigger management unit is used to manage the emergency plan when the effectiveness status of the emergency plan is downgraded or falls below a threshold.
[0119] In one or more embodiments, the emergency response plan management device includes: The report sending module is used to send a status report of the emergency plan to the target device based on the effectiveness status of the emergency plan.
[0120] In the embodiments of this specification, the effectiveness status of emergency plans can be periodically and automatically detected, transforming the effectiveness detection of emergency plans from an occasional activity relying on manual organization into a continuous process. This effectively supports the daily maintenance of a large number of emergency plans and improves management efficiency. Furthermore, the effectiveness status of emergency plans is determined based on drill information, result verification information, and change information. Based on an objective and quantifiable evaluation system, and combining information from multiple dimensions, the effectiveness status of emergency plans can be reliably and credibly assessed, avoiding the arbitrariness of human judgment. Furthermore, emergency plans are managed according to their effectiveness status, promptly identifying and isolating emergency plans with low effectiveness status. This prevents operational errors during the execution of emergency plans with low effectiveness status from causing secondary failures, maintaining the effectiveness status of emergency plans at a consistently high level, thereby effectively improving the ability of emergency plans to protect against real-world events.
[0121] It should be noted that the emergency response plan management device provided in the above embodiments is only illustrated by the division of the above functional modules when executing the emergency response plan management method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the emergency response plan management device and the emergency response plan management method embodiments provided in the above embodiments belong to the same concept, and the implementation process is detailed in the method embodiments, which will not be repeated here.
[0122] The example numbers in this specification are for descriptive purposes only and do not represent the superiority or inferiority of the examples.
[0123] This specification also provides a computer storage medium that can store multiple instructions adapted to be loaded and executed by a processor as described above. Figure 1 - Figure 6 The emergency response plan management method shown in the embodiment can be found in the following document for detailed implementation process. Figure 1 - Figure 6 The specific details of the illustrated embodiments will not be elaborated here.
[0124] This specification also provides a computer program product that stores at least one instruction, which is loaded and executed by a processor as described above. Figure 1 - Figure 6 The emergency response plan management method shown in the embodiment can be found in the following document for detailed implementation process. Figure 1 - Figure 6 The specific details of the illustrated embodiments will not be elaborated here.
[0125] Please see Figure 8 This document provides a schematic diagram of the structure of an electronic device as an embodiment of the present specification. Figure 8 As shown, the electronic device 600 may include: at least one processor 601, at least one network interface 604, user interface 603, memory 605, and at least one communication bus 602.
[0126] The communication bus 602 is used to enable communication between these components.
[0127] The user interface 603 may include a display screen and a camera. Optionally, the user interface 603 may also include a standard wired interface and a wireless interface.
[0128] The network interface 604 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface).
[0129] The processor 601 may include one or more processing cores. The processor 601 connects to various parts within the electronic device 600 using various interfaces and lines, and performs various functions and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 605, and by calling data stored in the memory 605. Optionally, the processor 601 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 601 may integrate one or a combination of several of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content to be displayed on the screen; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor 601 and may be implemented as a separate chip.
[0130] The memory 605 may include random access memory (RAM) or read-only memory. Optionally, the memory 605 may include a non-transitory computer-readable storage medium. The memory 605 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 605 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 605 may also be at least one storage device located remotely from the aforementioned processor 601. Figure 8 As shown, the memory 605, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an emergency response plan management application.
[0131] exist Figure 8In the illustrated electronic device 600, the user interface 603 is mainly used to provide an input interface for the user and to acquire user input data; while the processor 601 can be used to call the emergency plan management application stored in the memory 605 and specifically perform the following operations: Obtain emergency response plan drill information, result verification information, and change information; wherein, the drill information indicates the historical drill execution status of the emergency response plan, the verification result information includes at least functional verification results and transaction verification results, and the change information includes change records of environmental elements on which the emergency response plan depends; Based on the exercise information, the result verification information, and the change information, determine the effectiveness status of the emergency plan; The emergency response plan is managed according to its effectiveness status.
[0132] In one embodiment, the processor 601 executes the step of determining the effectiveness status of the emergency plan based on the exercise information, the result verification information, and the change information, specifically by: According to the preset target weight allocation strategy, weights are assigned to the exercise information, the result verification information, and the change information, respectively. The effectiveness status of the emergency plan is determined based on the weights and contents corresponding to the exercise information, the result verification information, and the change information, respectively.
[0133] In one embodiment, the processor 601 executes the preset target weight allocation strategy to allocate weights to the exercise information, the result verification information, and the change information, specifically: Based on the type of the emergency plan, the target weight allocation strategy corresponding to the emergency plan is determined from multiple preset weight allocation strategies.
[0134] In one embodiment, the processor 601 manages the emergency plan based on its validity status, specifically by: Based on the pre-defined correlation between different effectiveness states and management actions, determine the target management actions corresponding to the effectiveness states of the emergency plan; The emergency response plan is managed based on the aforementioned target management actions.
[0135] In one embodiment, the processor 601 manages the emergency plan based on its validity status, specifically by: Based on the effectiveness status of the emergency plan, the emergency plan is configured with prerequisite information to obtain the prerequisite information configuration status; wherein, the prerequisite information includes the exercise method and / or result verification items; Based on the aforementioned pre-configured information, the emergency response plan is rehearsed, and the emergency response plan is managed based on the rehearsal results.
[0136] In one embodiment, the processor 601 executes the step of configuring prerequisite information for the emergency plan based on its validity status, and obtains the prerequisite information configuration status. Specifically, the following steps are performed: Based on the effectiveness status of the emergency plan, a preliminary information configuration request is sent to the target device; Based on the pre-configuration instructions returned by the target device based on the pre-configuration request, the emergency plan is configured with pre-configuration information to obtain the pre-configuration information status.
[0137] In one embodiment, the processor 601 executes the step of configuring prerequisite information for the emergency plan based on its validity status, and obtains the prerequisite information configuration status. Specifically, the following steps are performed: Based on the effectiveness status of the emergency plan, as well as the exercise information, result verification information, and change information, the emergency plan is configured with prerequisite information to obtain the prerequisite information configuration status.
[0138] In one embodiment, the processor 601 executes the following steps: performing a drill on the emergency plan based on the configuration of the prior information, and managing the emergency plan based on the drill results. Specifically, the following actions are performed: Based on the aforementioned pre-configured information, the emergency response plan is rehearsed, and the effectiveness status of the emergency response plan is updated based on the rehearsal results.
[0139] In one embodiment, the processor 601 manages the emergency plan based on its validity status, specifically by: When the effectiveness of the emergency plan is downgraded or falls below a threshold, the emergency plan is managed.
[0140] In one embodiment, after the processor 601 manages the emergency plan according to its validity status, it further performs the following: Based on the effectiveness status of the emergency plan, a status report of the emergency plan is sent to the target device.
[0141] In the embodiments of this specification, the effectiveness status of emergency plans can be periodically and automatically detected, transforming the effectiveness detection of emergency plans from an occasional activity relying on manual organization into a continuous process. This effectively supports the daily maintenance of a large number of emergency plans and improves management efficiency. Furthermore, the effectiveness status of emergency plans is determined based on drill information, result verification information, and change information. Based on an objective and quantifiable evaluation system, and combining information from multiple dimensions, the effectiveness status of emergency plans can be reliably and credibly assessed, avoiding the arbitrariness of human judgment. Furthermore, emergency plans are managed according to their effectiveness status, promptly identifying and isolating emergency plans with low effectiveness status. This prevents operational errors during the execution of emergency plans with low effectiveness status from causing secondary failures, maintaining the effectiveness status of emergency plans at a consistently high level, thereby effectively improving the ability of emergency plans to protect against real-world events.
[0142] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented. Each of the above methods can be executed by a computer program instructing related hardware. The program corresponding to each method can be stored in a computer-readable storage medium. When executed, the program can include the processes of the embodiments of the above methods. The storage medium of the electronic device 600 can be a magnetic disk, optical disk, read-only memory, or random access memory, etc.
[0143] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0144] The above-disclosed embodiments are merely preferred embodiments of this specification and should not be construed as limiting the scope of this specification. Therefore, any equivalent variations made in accordance with the claims of this specification shall still fall within the scope of this specification.
Claims
1. An emergency response plan management method, the method comprising: Obtain emergency response plan drill information, result verification information, and change information; wherein, the drill information indicates the historical drill execution status of the emergency response plan, the verification result information includes at least functional verification results and transaction verification results, and the change information includes change records of environmental elements on which the emergency response plan depends; Based on the exercise information, the result verification information, and the change information, determine the effectiveness status of the emergency plan; The emergency response plan is managed according to its effectiveness status.
2. The emergency response plan management method according to claim 1, wherein determining the effectiveness status of the emergency response plan based on the exercise information, the result verification information, and the change information includes: According to the preset target weight allocation strategy, weights are assigned to the exercise information, the result verification information, and the change information, respectively. The effectiveness status of the emergency plan is determined based on the weights and contents corresponding to the exercise information, the result verification information, and the change information, respectively.
3. The emergency response plan management method according to claim 2, wherein assigning weights to the exercise information, the result verification information, and the change information according to a preset target weight allocation strategy includes: Based on the type of the emergency plan, the target weight allocation strategy corresponding to the emergency plan is determined from multiple preset weight allocation strategies.
4. The emergency response plan management method according to claim 1, wherein managing the emergency response plan based on its effectiveness status includes: Based on the pre-defined correlation between different effectiveness states and management actions, determine the target management actions corresponding to the effectiveness states of the emergency plan; The emergency response plan is managed based on the aforementioned target management actions.
5. The emergency response plan management method according to claim 1, wherein managing the emergency response plan based on its effectiveness status includes: Based on the effectiveness status of the emergency plan, the emergency plan is configured with prerequisite information to obtain the prerequisite information configuration status; wherein, the prerequisite information includes the exercise method and / or result verification items; Based on the aforementioned pre-configured information, the emergency response plan is rehearsed, and the emergency response plan is managed based on the rehearsal results.
6. The emergency response plan management method according to claim 5, wherein configuring the emergency response plan with prerequisite information based on its effectiveness status to obtain the prerequisite information configuration status includes: Based on the effectiveness status of the emergency plan, a preliminary information configuration request is sent to the target device; Based on the pre-configuration instructions returned by the target device based on the pre-configuration request, the emergency plan is configured with pre-configuration information to obtain the pre-configuration information status.
7. The emergency response plan management method according to claim 5 or 6, wherein configuring the emergency response plan with prerequisite information based on its effectiveness status to obtain the prerequisite information configuration status includes: Based on the effectiveness status of the emergency plan, as well as the exercise information, result verification information, and change information, the emergency plan is configured with prerequisite information to obtain the prerequisite information configuration status.
8. The emergency response plan management method according to claim 5, wherein the step of conducting drills on the emergency response plan based on the pre-configured information and managing the emergency response plan based on the drill results includes: Based on the aforementioned pre-configured information, the emergency response plan is rehearsed, and the effectiveness status of the emergency response plan is updated based on the rehearsal results.
9. The emergency response plan management method according to claim 1, wherein managing the emergency response plan based on its effectiveness status includes: When the effectiveness of the emergency plan is downgraded or falls below a threshold, the emergency plan is managed.
10. The emergency response plan management method according to claim 1, further comprising, after managing the emergency response plan according to its effectiveness status: Based on the effectiveness status of the emergency plan, a status report of the emergency plan is sent to the target device.
11. An emergency response plan management device, the device comprising: The information acquisition module is used to acquire the exercise information, result verification information, and change information of the emergency plan; wherein, the exercise information indicates the historical exercise execution status of the emergency plan, the verification result information includes at least the functional verification results and transaction verification results, and the change information includes the change records of the environmental elements on which the emergency plan depends; The status determination module is used to determine the effectiveness status of the emergency plan based on the exercise information, the result verification information, and the change information. The emergency plan management module is used to manage the emergency plan based on its effectiveness status.
12. A computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the method steps of any one of claims 1 to 10.
13. A computer program product storing a plurality of instructions adapted for loading by a processor and executing the method steps of any one of claims 1 to 10.
14. An electronic device, comprising: A processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and executed the method steps as claimed in any one of claims 1 to 10.
