Power grid dispatch operation ticket processing method, device, equipment, medium and product

Abstract

This application relates to a method, apparatus, device, medium, and product for processing power grid dispatch operation tickets. The method includes: receiving a dispatch request for a target power grid; during the sequential execution of power grid dispatch operation tickets according to the execution order in the target power grid; upon detecting an abnormal operation ticket; determining the missing pre-operation based on the standard and actual pre-operation associated with the abnormal operation ticket; determining the executability of the abnormal operation ticket based on the power grid operation data of the target power grid and the operation type of the missing pre-operation; if the executability is determined to be continuable, determining the execution strategy for the abnormal operation ticket based on the reason for the missing pre-operation; and continuing to execute the abnormal operation ticket and subsequent power grid dispatch operation tickets according to the execution strategy and execution order. This method can improve the efficiency of power grid dispatch operations.

Description

Technical Field

[0001] This application relates to the field of power distribution network technology, and in particular to a method, apparatus, equipment, medium and product for processing power grid dispatch operation tickets. Background Technology

[0002] In the field of power grid dispatching, power grid dispatching operation tickets are the core control tool for the safe operation of power systems. Essentially, they transform dispatching instructions into a standardized, executable sequence of operational steps to regulate switching operations and prevent misoperation accidents. However, manually written power grid dispatching operation tickets have significant drawbacks: they are not only cumbersome and time-consuming, but also prone to errors such as typos and omissions due to human negligence, severely limiting the efficiency of generating power grid dispatching operation tickets. To address these pain points, a new approach has emerged that programs the operational steps in traditional power grid dispatching operation tickets into automated processes. Then, a single start command automatically executes multiple consecutive operations, thereby achieving automated execution of complex operations.

[0003] However, when executing multiple power grid dispatch operation tickets using the above method, if any power grid dispatch operation in any power grid dispatch operation ticket is abnormal, the execution of all power grid dispatch operation tickets will be stopped directly, which will reduce the efficiency of power grid dispatch operations. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, apparatus, equipment, medium, and product for processing power grid dispatch operation tickets that can improve the efficiency of power grid dispatch operation, addressing the aforementioned technical problems.

[0005] Firstly, this application provides a method for processing power grid dispatch operation tickets, including:

[0006] Receive dispatch requests for the target power grid; wherein, the dispatch request includes dispatch operation tickets for each power grid and the execution order among the dispatch operation tickets for each power grid;

[0007] During the process of executing each grid dispatch operation ticket in the target grid according to the execution order, if an abnormal operation ticket is detected, the missing pre-operation is determined based on the standard pre-operation and actual pre-operation associated with the abnormal operation ticket; wherein, the abnormal operation ticket is a grid dispatch operation ticket that contains grid dispatch operations that have failed the feasibility verification.

[0008] Based on the target power grid's operation data and the type of operation for which no preceding operations are needed, determine the feasibility of the abnormal operation ticket.

[0009] If the executable condition is that execution can continue, determine the execution strategy for the abnormal operation ticket based on the reason for the missing operation preceding the missing operation, and continue to execute the abnormal operation ticket and the power grid dispatch operation ticket following the abnormal operation ticket according to the execution strategy and execution order.

[0010] In one embodiment, the executable status of the abnormal operation ticket is determined based on the target power grid's operation data and the operation type of the missing preceding operation, including:

[0011] Based on the power grid operation data of the target power grid, determine the electrical safety information, mechanical status information, and system redundancy information corresponding to the missing pre-operation procedures; among them, the system redundancy information refers to the redundancy information of each module in the sequential control system that executes the power grid dispatch operation ticket;

[0012] Based on electrical safety information, mechanical status information, and system redundancy information, determine the operational risk value of missing pre-operation procedures;

[0013] Based on the operational risk value and operation type of the missing preceding operation, determine the executable status of the abnormal operation ticket.

[0014] In one embodiment, the executable status of an abnormal operation ticket is determined based on the operation risk value and operation type of the missing preceding operation, including:

[0015] If the operation type lacking the preceding operation is a critical operation type, the executable status of the abnormal operation ticket is determined to be that it cannot continue to be executed;

[0016] If the operation type lacking a prerequisite operation is not a critical operation type, the executable status of the abnormal operation ticket is determined based on the operation risk value of the missing prerequisite operation.

[0017] In one embodiment, the execution strategy for the abnormal operation ticket is determined based on the reason for the missing pre-operation, including:

[0018] When the reason for the missing operation of the preceding operation is that the parameter value of the non-critical parameter is outside the target parameter range corresponding to the non-critical parameter, the parameter difference ratio is determined based on the minimum parameter difference between the parameter value and the target parameter range.

[0019] When the parameter difference ratio is less than the ratio threshold, the target parameter range is adjusted according to the parameter value; wherein, the adjusted target parameter range includes the parameter value.

[0020] In one embodiment, when the executable condition is no longer executable, the method further includes:

[0021] Extract key operational elements from the missing preceding operations;

[0022] Based on the standard operation and maintenance strategy associated with key operational elements, determine the operation and maintenance strategy for missing preceding operations, and send the operation and maintenance strategy to the operation and maintenance end.

[0023] In one embodiment, when the executable condition is no longer executable, the method further includes:

[0024] Send an operation confirmation request to the operation and maintenance terminal of the target power grid;

[0025] Upon receiving the operation confirmation instruction from the operation and maintenance terminal, the abnormal operation ticket and the subsequent power grid dispatch operation ticket will continue to be executed according to the execution order.

[0026] Secondly, this application also provides a power grid dispatching operation ticket processing device, comprising:

[0027] The request receiving module is used to receive dispatch requests for the target power grid; wherein, the dispatch request includes dispatch operation tickets for each power grid and the execution order between the dispatch operation tickets of each power grid;

[0028] The operation determination module is used to determine the missing pre-operation based on the standard pre-operation and the actual pre-operation associated with the abnormal operation ticket when an abnormal operation ticket is detected during the sequential execution of each power grid dispatch operation ticket in the target power grid according to the execution order. The abnormal operation ticket is a power grid dispatch operation ticket that contains a power grid dispatch operation that failed the feasibility verification.

[0029] The judgment module is used to determine the executability of abnormal operation tickets based on the power grid operation data of the target power grid and the operation type of the missing preceding operation;

[0030] The operation adjustment module is used to determine the execution strategy of the abnormal operation ticket based on the reason for the missing operation of the missing preceding operation when the executable situation is that it can continue to be executed, and to continue to execute the abnormal operation ticket and the power grid dispatch operation ticket after the abnormal operation ticket according to the execution strategy and execution order.

[0031] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0032] Receive dispatch requests for the target power grid; wherein, the dispatch request includes dispatch operation tickets for each power grid and the execution order among the dispatch operation tickets for each power grid;

[0033] During the process of executing each grid dispatch operation ticket in the target grid according to the execution order, if an abnormal operation ticket is detected, the missing pre-operation is determined based on the standard pre-operation and actual pre-operation associated with the abnormal operation ticket; wherein, the abnormal operation ticket is a grid dispatch operation ticket that contains grid dispatch operations that have failed the feasibility verification.

[0034] Based on the target power grid's operation data and the type of operation for which no preceding operations are needed, determine the feasibility of the abnormal operation ticket.

[0035] If the executable condition is that execution can continue, determine the execution strategy for the abnormal operation ticket based on the reason for the missing operation preceding the missing operation, and continue to execute the abnormal operation ticket and the power grid dispatch operation ticket following the abnormal operation ticket according to the execution strategy and execution order.

[0036] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0037] Receive dispatch requests for the target power grid; wherein, the dispatch request includes dispatch operation tickets for each power grid and the execution order among the dispatch operation tickets for each power grid;

[0038] During the process of executing each grid dispatch operation ticket in the target grid according to the execution order, if an abnormal operation ticket is detected, the missing pre-operation is determined based on the standard pre-operation and actual pre-operation associated with the abnormal operation ticket; wherein, the abnormal operation ticket is a grid dispatch operation ticket that contains grid dispatch operations that have failed the feasibility verification.

[0039] Based on the target power grid's operation data and the type of operation for which no preceding operations are needed, determine the feasibility of the abnormal operation ticket.

[0040] If the executable condition is that execution can continue, determine the execution strategy for the abnormal operation ticket based on the reason for the missing operation preceding the missing operation, and continue to execute the abnormal operation ticket and the power grid dispatch operation ticket following the abnormal operation ticket according to the execution strategy and execution order.

[0041] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0042] Receive dispatch requests for the target power grid; wherein, the dispatch request includes dispatch operation tickets for each power grid and the execution order among the dispatch operation tickets for each power grid;

[0043] During the process of executing each grid dispatch operation ticket in the target grid according to the execution order, if an abnormal operation ticket is detected, the missing pre-operation is determined based on the standard pre-operation and actual pre-operation associated with the abnormal operation ticket; wherein, the abnormal operation ticket is a grid dispatch operation ticket that contains grid dispatch operations that have failed the feasibility verification.

[0044] Based on the target power grid's operation data and the type of operation for which no preceding operations are needed, determine the feasibility of the abnormal operation ticket.

[0045] If the executable condition is that execution can continue, determine the execution strategy for the abnormal operation ticket based on the reason for the missing operation preceding the missing operation, and continue to execute the abnormal operation ticket and the power grid dispatch operation ticket following the abnormal operation ticket according to the execution strategy and execution order.

[0046] The aforementioned method, apparatus, equipment, medium, and product for processing power grid dispatch operation tickets, when detecting an abnormal operation ticket during the sequential execution of each power grid dispatch operation ticket according to the execution order in the target power grid, determines the missing pre-operation based on the standard and actual pre-operation associated with the abnormal operation ticket. Then, based on the power grid operation data of the target power grid and the operation type of the missing pre-operation, the executability of the abnormal operation ticket is determined. If the executability is deemed acceptable, an execution strategy for the abnormal operation ticket is determined based on the reason for the missing pre-operation. Finally, based on the execution strategy and execution order, the abnormal operation ticket and subsequent power grid dispatch operation tickets continue to be executed. Compared to related technologies that directly stop the execution of all power grid dispatch operation tickets upon detecting an abnormal operation ticket, this method, by determining the executability of the abnormal operation ticket based on the power grid operation data of the target power grid and the operation type of the missing pre-operation, and generating an execution strategy if the abnormal operation ticket can continue to be executed, ensures the operational safety of the target power grid without affecting the execution of each power grid dispatch operation ticket, thereby guaranteeing the efficiency of power grid dispatch operations. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a flowchart illustrating a method for processing power grid dispatch operation tickets in one embodiment;

[0049] Figure 2 This is a flowchart illustrating the process of determining the executable status in one embodiment;

[0050] Figure 3 This is a flowchart illustrating the process of determining an execution strategy in one embodiment;

[0051] Figure 4 This is a flowchart illustrating the process of generating an operation and maintenance strategy in one embodiment;

[0052] Figure 5 This is a flowchart illustrating the method for processing power grid dispatch operation tickets in another embodiment;

[0053] Figure 6 This is a structural block diagram of a power grid dispatch operation ticket processing device in one embodiment;

[0054] Figure 7 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0055] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0056] In the field of power grid dispatching, power grid dispatching operation tickets are the core control tool for the safe operation of power systems. Essentially, they transform dispatching instructions into a standardized, executable sequence of operational steps to regulate switching operations and prevent misoperation accidents. However, manually written power grid dispatching operation tickets have significant drawbacks: they are not only cumbersome and time-consuming, but also prone to errors such as typos and omissions due to human negligence, severely limiting the efficiency of generating power grid dispatching operation tickets. To address these pain points, a new approach has emerged that programs the operational steps in traditional power grid dispatching operation tickets into automated processes. Then, a single start command automatically executes multiple consecutive operations, thereby achieving automated execution of complex operations.

[0057] However, when executing multiple power grid dispatch operation tickets using the above method, if any power grid dispatch operation in any power grid dispatch operation ticket is abnormal, the execution of all power grid dispatch operation tickets will be stopped directly, which will reduce the efficiency of power grid dispatch operations.

[0058] Based on this, in an exemplary embodiment, a method for processing power grid dispatch operation tickets is provided. The method is illustrated using an application to a server as an example. Figure 1 As shown, the specific steps include:

[0059] S101, Receives a dispatch request for the target power grid.

[0060] The target power grid refers to the distribution network with power grid dispatching needs. The dispatching request is a request to dispatch the target power grid, which can be a one-click sequential control command initiated to the sequential control system. Furthermore, the dispatching request includes dispatching operation tickets for each power grid and the execution order between the dispatching operation tickets.

[0061] Optionally, when there is a need to schedule the target power grid, maintenance personnel can initiate a scheduling request for the target power grid to the sequential control system via a terminal. The server will then receive the scheduling request for the target power grid.

[0062] S102, during the process of executing each power grid dispatch operation ticket in the target power grid according to the execution order, after an abnormal operation ticket is detected, the missing pre-operation is determined based on the standard pre-operation and actual pre-operation associated with the abnormal operation ticket.

[0063] Among them, the so-called power grid dispatch operation ticket is a written, standardized operation instruction document in the power system, used to regulate the switching operations (i.e., operations that change the operating status of equipment) of electrical equipment (such as circuit breakers, disconnectors, grounding switches, etc.). An abnormal operation ticket is a power grid dispatch operation ticket that includes power grid dispatch operations whose feasibility verification has failed.

[0064] Standard pre-operations are the theoretically mandatory operations that must be performed before executing a dispatch operation. Different power grid dispatch operation tickets correspond to different standard pre-operations. For example, the standard pre-operation for grounding is the voltage verification step; the standard pre-operation for bus de-energization is disconnecting all incoming and outgoing lines; and the standard pre-operation for capacitor switching is an operation interval > 300 seconds. Actual pre-operations are other dispatch operations performed before the actual dispatch operation. Missing pre-operations are the pre-operations for which an abnormal operation ticket is missing.

[0065] Optionally, the dispatch operation tickets can be executed sequentially in the target power grid according to their execution order. Before executing each dispatch operation ticket, its feasibility needs to be verified. For example, the standard prerequisite operations before executing the dispatch operation ticket can be obtained based on the dispatch operations in the ticket. Furthermore, the feasibility verification of the dispatch operation ticket can be determined by comparing the standard prerequisite operations with the actual prerequisite operations that have already been executed.

[0066] For example, if the actual pre-operation of the power grid dispatch operation ticket includes all standard pre-operation, the feasibility verification of the power grid dispatch operation ticket is determined to be passed; if the actual pre-operation of the power grid dispatch operation ticket does not include all standard pre-operation, the feasibility verification of the power grid dispatch operation ticket is determined to be failed, that is, the power grid dispatch operation ticket is an abnormal operation ticket.

[0067] If the feasibility verification of the power grid dispatch operation ticket is passed, the power grid dispatch operation ticket shall be executed in the target power grid; if the power grid dispatch operation ticket is an abnormal operation ticket, the missing pre-operation of the abnormal operation ticket can be determined based on the standard pre-operation not included in the actual pre-operation of the abnormal operation ticket.

[0068] S103, based on the target power grid's operation data and the operation type of the missing preceding operation, determine the executability of the abnormal operation ticket.

[0069] The so-called power grid operation data refers to the relevant parameters affecting the operation of the target power grid. For example, it may include the operating parameters of various power equipment during the operation of the target power grid, as well as the environmental parameters of the environment in which the power equipment is located. The so-called operation type refers to the specific type of missing preceding operations. For example, it may include operation types that are strictly prohibited from being skipped or ignored, such as those related to five-prevention logic, key equipment parameters, and safety interlocking; it may also include operation types that are allowed to be skipped or ignored, such as those related to non-safety monitoring, such as missing auxiliary signals, the presence of redundant or backup modules, skippable conditions approved by expert evaluation, and alarms that can be delayed.

[0070] Optionally, based on the target power grid's operation data and the type of operation lacking prerequisite operations, the operational risk value for executing the abnormal operation ticket in the absence of these prerequisite operations can be assessed. Then, based on the operational risk value of the abnormal operation ticket, its executable status can be determined. For example, if the operational risk value is less than the risk threshold, the abnormal operation ticket is determined to be executable; if the operational risk value is greater than or equal to the risk threshold, the abnormal operation ticket is determined to be inexecutable.

[0071] S104. If the executable condition is that execution can continue, determine the execution strategy of the abnormal operation ticket based on the reason for the missing operation of the missing preceding operation, and continue to execute the abnormal operation ticket and the power grid dispatch operation ticket after the abnormal operation ticket according to the execution strategy and execution order.

[0072] The execution strategy refers to the strategy for executing abnormal operation tickets. The reason for operation missing refers to the specific reason for the missing preceding operation, such as the parameter values ​​of certain key parameters not being within the preset parameter range.

[0073] Optionally, if the executable status of an abnormal operation ticket is determined to be that it can continue to be executed, an execution strategy can be generated based on the reason for the missing preceding operation. For example, if the reason for the missing preceding operation is insufficient fixed power supply voltage, and if a redundant power supply module exists, the execution strategy is to use the redundant power supply module for power supply. If the reason for the missing preceding operation is a sensor malfunction leading to missing information, and if redundant sensors exist, the execution strategy is to use redundant sensors or strongly correlated sensor information to replace the missing information and continue executing the operation ticket.

[0074] Furthermore, after determining the execution strategy, the abnormal operation ticket can be executed in conjunction with the execution strategy, and the power grid dispatching operation tickets following the abnormal operation ticket can be executed according to the execution order.

[0075] It is worth noting that before continuing to execute the abnormal operation ticket, an execution confirmation request can be sent to the operation and maintenance personnel through the terminal. At the same time, the information and permissions of the operation and maintenance personnel can be recorded. After electronic signature, the abnormal operation ticket and the power grid dispatch operation ticket following the abnormal operation ticket can be executed, which facilitates post-event review.

[0076] In the aforementioned method for processing power grid dispatch operation tickets, when an abnormal operation ticket is detected during the sequential execution of each power grid dispatch operation ticket according to the execution order in the target power grid, the missing pre-operation is determined based on the standard and actual pre-operation associated with the abnormal operation ticket. Furthermore, the executability of the abnormal operation ticket is determined based on the target power grid's operation data and the operation type of the missing pre-operation. If the executability is deemed acceptable, the execution strategy for the abnormal operation ticket is determined based on the reason for the missing pre-operation. Then, the abnormal operation ticket and subsequent power grid dispatch operation tickets continue to be executed according to the execution strategy and execution order. Compared to related technologies that directly stop the execution of all power grid dispatch operation tickets upon detecting an abnormal operation ticket, this method, by determining the executability of the abnormal operation ticket based on the target power grid's operation data and the operation type of the missing pre-operation, and generating an execution strategy when the abnormal operation ticket can continue to be executed, ensures the operational safety of the target power grid without affecting the execution of each power grid dispatch operation ticket, thereby guaranteeing the efficiency of power grid dispatch operations.

[0077] Based on the above embodiments, this application provides an optional method for determining the executable status, such as... Figure 2 As shown, the specific steps include:

[0078] S201, Based on the power grid operation data of the target power grid, determine the electrical safety information, mechanical status information and system redundancy information corresponding to the missing pre-operation procedures.

[0079] Among them, the so-called electrical safety information refers to the electrical parameters involved in the missing pre-operation; the so-called mechanical status information refers to the equipment status involved in the missing pre-operation; and the so-called system redundancy information refers to the redundancy information of each module in the sequential control system that executes the power grid dispatch operation ticket.

[0080] Optionally, electrical safety and mechanical status information related to the missing pre-operation steps can be obtained from the target power grid's power grid operation data. Then, system redundancy information can be obtained from the sequential control system's configuration information.

[0081] S202, based on electrical safety information, mechanical status information and system redundancy information, determine the operational risk value of missing pre-operation procedures.

[0082] The so-called operational risk value refers to the operational risk when the standard continues to execute abnormal operation tickets.

[0083] Optionally, a basic matrix can be constructed for each power device that lacks pre-operation associations. Then, electrical safety information, mechanical status information, and the operating status of functional modules in each power device are used to process the basic matrix to construct an electrical safety matrix, a mechanical status matrix, and a functional operation matrix. Subsequently, preset electrical safety weights and mechanical status weights, as well as functional operation weights determined based on system redundancy information, are used to add to the electrical safety matrix, mechanical status matrix, and functional operation matrix to obtain the operational risk value for missing pre-operations.

[0084] For example, the operational risk value H for missing pre-operation can be calculated using the formula H = (x1×k1 + x2×k2 + x3×k3). Here, x1 is the electrical safety matrix, representing the exceedance of various electrical safety parameters, including the exceedance ratio of each parameter; x2 corresponds to the mechanical state matrix, which is 0 under normal conditions and a preset value under abnormal conditions; x3 is the functional operation matrix, representing the abnormal conditions of functional modules, with its elements set to a preset value when an abnormality occurs. k1, k2, and k3 are the weight parameter matrices for the electrical safety matrix x1, mechanical state matrix x2, and functional operation matrix x3, respectively. When a functional module has redundancy, the corresponding element in matrix k3 is 0; otherwise, it is 1. The redundancy settings for functional modules vary in different sequential control systems. With redundant modules, even if a functional module malfunctions, it will not cause risk.

[0085] S203, determine the executable status of the abnormal operation ticket based on the operation risk value and operation type of the missing preceding operation.

[0086] Optionally, the executability of an abnormal operation ticket can be assessed based on the operational risk value of the missing prerequisite operation and the operational risk level corresponding to the operation type. For example, if the operational risk value of the missing prerequisite operation is low and the operational risk level corresponding to the operation type is low, the executability of the abnormal operation ticket is determined to be executable; if the operational risk value of the missing prerequisite operation is high and / or the operational risk level corresponding to the operation type is high, the executability of the abnormal operation ticket is determined to be inexecutable.

[0087] In this embodiment of the application, by determining the operational risk value based on electrical safety information, mechanical status information, and system redundancy information, and by determining the executability of the abnormal operation ticket based on the operational risk value and the operation type, the reliability of the power grid operation can be guaranteed.

[0088] Based on the above embodiments, this application provides another optional method for determining the executable status. Specifically, if the operation type with missing pre-operation is a critical operation type, the executable status of the abnormal operation ticket is determined to be unexecutable; if the operation type with missing pre-operation is not a critical operation type, the executable status of the abnormal operation ticket is determined based on the operation risk value of the missing pre-operation.

[0089] Among them, the so-called critical operation types are those that cannot be skipped, such as those related to the five-prevention logic, those related to key equipment parameters, and those related to safety interlocks.

[0090] Optionally, the operation type with missing prerequisite operations can be compared with each preset critical operation type to determine whether the operation type with missing prerequisite operations is a critical operation type. If it is determined that the operation type with missing prerequisite operations is a critical operation type, it proves that the risk of continuing to execute the abnormal operation ticket is high. Therefore, the executable status of the abnormal operation ticket can be directly determined as not being able to continue execution.

[0091] If the operation type with missing prerequisite operations is determined not to be a critical operation type, it indicates a low risk of continuing to execute the abnormal operation ticket. Therefore, the executable status of the abnormal operation ticket can be determined by combining the operational risk value of the missing prerequisite operations. For example, if the operational risk value is less than the risk threshold, the abnormal operation ticket is determined to be executable; if the operational risk value is greater than or equal to the risk threshold, the abnormal operation ticket is determined to be inexecutable.

[0092] Alternatively, if it is determined that the operation type with missing prerequisite operations is not a critical operation type, the operation type with missing prerequisite operations can be compared with each preset non-critical operation type. If the operation type with missing prerequisite operations is a non-critical operation type, the executable status of the abnormal operation ticket is directly determined to be that it can continue to be executed; if the operation type with missing prerequisite operations is not a non-critical operation type, the executable status of the abnormal operation ticket is determined by combining the operation risk value of the missing prerequisite operations.

[0093] It is worth noting that when the operational risk value is greater than or equal to the risk threshold, the execution interval between each power grid dispatching operation ticket can be increased. The execution interval is proportional to the difference between the operational risk value and the risk threshold. Subsequently, a manual confirmation node is added to power grid dispatching operation tickets containing critical operation types. When execution reaches the manual confirmation node, manual verification and confirmation are required before continuing.

[0094] Furthermore, the higher the risk level of a power grid dispatch operation ticket, the lower the degree of automation of its execution method. The execution methods include fully automatic execution, semi-automatic execution, and step-by-step execution. Semi-automatic execution means that manual confirmation is required when the operation reaches the location specified in the power grid dispatch operation ticket. Step-by-step execution means that staff issue and execute the corresponding power grid dispatch operation tickets one by one.

[0095] In this embodiment of the application, by selecting the corresponding method for determining the executable status based on the operation type, the flexibility and accuracy of determining the executable status can be guaranteed.

[0096] Based on the above embodiments, this application provides an optional method for determining the execution strategy, such as... Figure 3 As shown, the specific steps include:

[0097] S301, when the reason for the missing operation of the preceding operation is that the parameter value of the non-critical parameter is outside the target parameter range corresponding to the non-critical parameter, the parameter difference ratio is determined based on the minimum parameter difference between the parameter value and the target parameter range.

[0098] Non-critical parameters are those that have a relatively low impact on scheduling instructions. Examples include ambient temperature and humidity. The target parameter range is the standard range within which the values ​​of non-critical parameters fall.

[0099] The minimum parameter difference is the smallest difference between a parameter value and the target parameter range. The parameter difference ratio is the ratio between the parameter difference and the parameter threshold used to calculate the difference. The parameter threshold is the upper or lower limit of the target parameter range.

[0100] Optionally, if the analysis shows that the missing operation is due to a non-critical parameter value being outside the corresponding target parameter range, the minimum parameter difference between the parameter value and the target parameter range can be calculated first. Then, the ratio between the minimum parameter difference and the parameter threshold for which the minimum parameter difference is calculated can be used as the parameter difference ratio.

[0101] S302, when the parameter difference ratio is less than the ratio threshold, adjust the target parameter range according to the parameter value.

[0102] The so-called proportion threshold is a parameter that measures the magnitude of the difference in parameters; for example, it can be 30%. The adjusted target parameter range includes the parameter values.

[0103] Optionally, a comparison can be made between the parameter difference ratio and a ratio threshold. If the parameter difference ratio is less than the ratio threshold, it indicates that the difference between the non-critical parameter value and the target parameter range is small. In this case, the upper or lower limit of the target parameter range can be temporarily adjusted based on the non-critical parameter value to ensure that the adjusted target parameter range includes the parameter value. This completes the pre-emptive action for missing abnormal operation tickets. It is worth noting that manual review can be performed before temporarily adjusting the target parameter range.

[0104] If the parameter difference ratio is greater than or equal to the ratio threshold, it indicates a significant difference between the non-critical parameter values ​​and the target parameter range. In this case, the non-critical parameter values ​​can be provided to the operations and maintenance personnel for reference. Alternatively, an execution strategy for adjusting the non-critical parameters can be generated based on their parameter types.

[0105] Furthermore, in some implementations, if the missing operation is due to an abnormal state of the functional module, the controller can correct the state of the functional module. For example, the controller can switch the on or off state of a remote control switch.

[0106] In this application embodiment, an optional method for generating execution strategies for non-critical parameters is provided, which can ensure the rationality of the generated execution strategy.

[0107] Based on the above embodiments, in this application embodiment, when the executable situation is that execution cannot continue, an optional method for generating operation and maintenance strategies is provided, such as... Figure 4 As shown, the specific steps include:

[0108] S401, extract key operational elements from missing preceding operations.

[0109] Among them, the so-called key operational elements are the main operational elements in the missing pre-operation process.

[0110] Understandably, power grid dispatch operation tickets correspond to a vast logical rule base. The operational logic is not a simple "A then B," but rather a large set of "IF-THEN-ELSE" rules; each operation step corresponds to dozens or even hundreds of interlocking conditions. For example, the preconditions for "branch line switch" might include: no protection action signal, no control circuit open circuit alarm, no SF6 low pressure interlock on the switch body, and the remote / local switching switch being in the "remote" position. Therefore, it is necessary to identify the decisive operational elements.

[0111] Optionally, to improve the efficiency of operation and maintenance strategy generation, corresponding standard operation and maintenance strategies can be pre-configured for each critical operation type and each non-critical operation type. Then, if an operation type lacking a prerequisite operation is either a critical or non-critical operation type, the corresponding operation and maintenance strategy can be selected from the preset standard operation and maintenance strategies.

[0112] When an operation type that lacks a prerequisite operation is neither a critical operation type nor a non-critical operation type, the missing prerequisite operation can be decomposed, and the operation element with the highest importance among the resulting operation elements can be taken as the critical operation element.

[0113] S402, based on the standard operation and maintenance strategy associated with key operation elements, determine the operation and maintenance strategy for missing preceding operations, and send the operation and maintenance strategy to the operation and maintenance end.

[0114] The so-called standard operation and maintenance strategy refers to the operation and maintenance strategy pre-configured for each key operational element. The standard operation and maintenance strategy can include information such as the handling method, cause, and risk level of each key operational element.

[0115] Optionally, the actual parameter values ​​of key operational elements can be used to optimize the standard operation and maintenance strategies associated with these elements, resulting in operation and maintenance strategies for missing pre-operation steps. For example, these strategies could include replacing equipment with redundant devices, temporarily adjusting preset threshold ranges, using a status switching module to switch statuses, stopping one-click operations, skipping or ignoring them, or seeking remote expert guidance or manual inspection.

[0116] Furthermore, operation and maintenance policies can be sent to the operation and maintenance team so that they can handle abnormal operation tickets in a timely manner.

[0117] It is worth noting that while generating operation and maintenance strategies, it is also possible to isolate the functions associated with key operational elements and use other unprocessed functions to execute subsequent power grid dispatch operation tickets.

[0118] In this embodiment of the application, by determining the operation and maintenance strategy for missing pre-operation steps based on the standard operation and maintenance strategy associated with key operation elements, the accuracy and efficiency of the operation and maintenance strategy determination can be guaranteed.

[0119] Based on the above embodiments, in this application embodiment, when the executable situation is that execution cannot continue, an optional method of manual verification is provided. Specifically, an operation confirmation request is sent to the operation and maintenance terminal of the target power grid; upon receiving the operation confirmation instruction from the operation and maintenance terminal, the abnormal operation ticket and the power grid dispatch operation ticket following the abnormal operation ticket are executed according to the execution order.

[0120] The so-called operation confirmation request is used to confirm whether to execute the abnormal operation ticket. The so-called operation confirmation instruction is the instruction to confirm the execution of the abnormal operation ticket.

[0121] Optionally, since the feasibility verification speed of the power grid dispatch operation ticket is faster than the execution speed of the power grid dispatch operation ticket, if the execution status of the abnormal operation ticket is determined to be unexecutable, the abnormal operation ticket is not actually executed. In this case, a breakpoint can be set at the location of the abnormal operation ticket, and when the operation reaches the breakpoint, an operation confirmation request can be sent to the operation and maintenance terminal of the target power grid.

[0122] After the operation and maintenance terminal detects the confirmation operation of the operation and maintenance personnel on the abnormal operation ticket, it can send an operation confirmation instruction to the sequential control system. At this time, the sequential control system can continue to execute the abnormal operation ticket and the power grid dispatch operation ticket that follows the abnormal operation ticket according to the execution order.

[0123] Furthermore, to facilitate debugging by maintenance personnel, corresponding breakpoints or start points can be manually set in the execution sequence between various power grid dispatch operation tickets. This allows execution to proceed to the power grid dispatch operation ticket position corresponding to the breakpoint, or to start execution from the power grid dispatch operation ticket position corresponding to the breakpoint. For example, if an anomaly occurred at the 13th operation ticket position last time, after investigation, a breakpoint can be set at the 8th and / or 10th operation ticket positions this time, allowing execution to proceed only to that operation ticket position; alternatively, a start point can be set at the 9th operation ticket position, allowing execution to start from the 9th operation ticket position corresponding to the start point.

[0124] In this embodiment of the application, the operation and maintenance process is carried out by setting breakpoints, which can ensure the flexibility of operation and maintenance and thus ensure the safety of power grid operation.

[0125] Figure 5 This is a flowchart illustrating a method for processing power grid dispatch operation tickets in another embodiment. Based on the above embodiments, this embodiment provides an optional example of a method for processing power grid dispatch operation tickets. (Combined with...) Figure 5 The specific implementation process is as follows:

[0126] S501 receives a dispatch request for the target power grid.

[0127] The dispatch request includes dispatch operation tickets for each power grid and the execution order among the dispatch operation tickets.

[0128] S502: During the process of executing each power grid dispatch operation ticket in the target power grid according to the execution order, if an abnormal operation ticket is detected, the missing pre-operation is determined based on the standard pre-operation and the actual pre-operation associated with the abnormal operation ticket.

[0129] Among them, abnormal operation tickets are power grid dispatch operation tickets that include power grid dispatch operations that have failed feasibility verification.

[0130] S503, based on the power grid operation data of the target power grid, determines the electrical safety information, mechanical status information and system redundancy information corresponding to the missing pre-operation procedures.

[0131] Among them, the system redundancy information refers to the redundancy information of each module in the sequential control system that executes the power grid dispatch operation ticket.

[0132] S504 determines the operational risk value for missing pre-operation procedures based on electrical safety information, mechanical status information, and system redundancy information.

[0133] S505, determine the executable status of the abnormal operation ticket based on the operation risk value and operation type of the missing preceding operation.

[0134] Optionally, if the operation type lacking the preceding operation is a critical operation type, the executable status of the abnormal operation ticket is determined to be non-executable; if the operation type lacking the preceding operation is not a critical operation type, the executable status of the abnormal operation ticket is determined based on the operation risk value of the missing preceding operation.

[0135] S506, if the executable condition is that execution can continue, determine the execution strategy of the abnormal operation ticket based on the reason for the missing operation of the missing preceding operation, and continue to execute the abnormal operation ticket and the power grid dispatch operation ticket after the abnormal operation ticket according to the execution strategy and execution order.

[0136] Optionally, if the reason for the missing operation of the preceding operation is that the parameter value of a non-critical parameter is outside the target parameter range corresponding to the non-critical parameter, the parameter difference ratio is determined based on the minimum parameter difference between the parameter value and the target parameter range; if the parameter difference ratio is less than the ratio threshold, the target parameter range is adjusted based on the parameter value; wherein the adjusted target parameter range includes the parameter value.

[0137] If the executable condition is deemed unexecutable, extract key operational elements from the missing preceding operations; determine the operational strategy for the missing preceding operations based on the standard operational strategy associated with the key operational elements, and send the operational strategy to the operational end. Alternatively, send an operation confirmation request to the operational end of the target power grid; upon receiving the operation confirmation instruction from the operational end, continue executing the abnormal operation ticket and the subsequent power grid dispatch operation tickets according to the execution order.

[0138] The specific processes of S501-S506 described above can be found in the description of the above method embodiments. Their implementation principles and technical effects are similar, and will not be repeated here.

[0139] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0140] Based on the same inventive concept, this application also provides a power grid dispatching operation ticket processing device for implementing the above-mentioned power grid dispatching operation ticket processing method. The solution provided by this device is similar to the implementation described in the above method. Therefore, the specific limitations of one or more power grid dispatching operation ticket processing device embodiments provided below can be found in the limitations of the power grid dispatching operation ticket processing method described above, and will not be repeated here.

[0141] In one exemplary embodiment, such as Figure 6 As shown, a power grid dispatching operation ticket processing device 1 is provided, comprising: a request receiving module 10, an operation determining module 20, a judgment module 30, and an operation adjusting module 40, wherein:

[0142] The request receiving module 10 is used to receive dispatch requests for the target power grid; wherein, the dispatch request includes dispatch operation tickets for each power grid and the execution order between the dispatch operation tickets of each power grid;

[0143] The operation determination module 20 is used to determine the missing pre-operation based on the standard pre-operation and the actual pre-operation associated with the abnormal operation ticket when an abnormal operation ticket is detected during the process of executing each power grid dispatch operation ticket in the target power grid according to the execution order; wherein, the abnormal operation ticket is a power grid dispatch operation ticket that contains a power grid dispatch operation that failed the feasibility verification.

[0144] The judgment module 30 is used to determine the executability of the abnormal operation ticket based on the power grid operation data of the target power grid and the operation type of the missing preceding operation;

[0145] The operation adjustment module 40 is used to determine the execution strategy of the abnormal operation ticket based on the reason for the missing operation of the missing preceding operation when the executable situation is that it can continue to be executed, and to continue to execute the abnormal operation ticket and the power grid dispatch operation ticket after the abnormal operation ticket according to the execution strategy and execution order.

[0146] In an exemplary embodiment, the determination module 30 is specifically used for:

[0147] Based on the power grid operation data of the target power grid, determine the electrical safety information, mechanical status information, and system redundancy information corresponding to the missing pre-operation; among which, the system redundancy information refers to the redundancy information of each module in the sequential control system that executes the power grid dispatch operation ticket; based on the electrical safety information, mechanical status information, and system redundancy information, determine the operation risk value of the missing pre-operation; based on the operation risk value and operation type of the missing pre-operation, determine the executability of the abnormal operation ticket.

[0148] In one exemplary embodiment, the determination module 30 is further configured to:

[0149] If the operation type lacking a prerequisite operation is a critical operation type, the executable status of the abnormal operation ticket is determined to be non-executable; if the operation type lacking a prerequisite operation is not a critical operation type, the executable status of the abnormal operation ticket is determined based on the operation risk value of the missing prerequisite operation.

[0150] In one exemplary embodiment, the operation adjustment module 40 is specifically used for:

[0151] If the missing operation of a prerequisite operation is due to a non-critical parameter value being outside the target parameter range corresponding to the non-critical parameter, the parameter difference ratio is determined based on the minimum parameter difference between the parameter value and the target parameter range. If the parameter difference ratio is less than the ratio threshold, the target parameter range is adjusted based on the parameter value. The adjusted target parameter range includes the parameter value.

[0152] In an exemplary embodiment, when the executable condition is that execution cannot continue, the power grid dispatching operation ticket processing device 1 further includes an operation and maintenance module, wherein the operation and maintenance module is specifically used for:

[0153] Extract key operational elements from the missing pre-operation steps; determine the operation and maintenance strategy for the missing pre-operation steps based on the standard operation and maintenance strategy associated with the key operational elements, and send the operation and maintenance strategy to the operation and maintenance end.

[0154] In an exemplary embodiment, when the executable condition is that execution cannot continue, the operation and maintenance module is specifically used for:

[0155] Send an operation confirmation request to the operation and maintenance terminal of the target power grid; upon receiving the operation confirmation instruction from the operation and maintenance terminal, continue to execute the abnormal operation ticket and the power grid dispatch operation ticket following the abnormal operation ticket according to the execution order.

[0156] Each module in the aforementioned power grid dispatch operation ticket processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0157] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 7 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores power grid operation data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communication with external terminals via a network connection. When executed by the processor, the computer program implements a method for processing power grid dispatch operation tickets.

[0158] Those skilled in the art will understand that Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0159] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0160] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0161] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0162] It should be noted that the data involved in this application (including but not limited to power grid operation data) are all data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0163] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0164] 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 application.

[0165] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for processing power grid dispatch operation tickets, characterized in that, The method includes: Receive a dispatch request for a target power grid; wherein the dispatch request includes dispatch operation tickets for each power grid and the execution order among the dispatch operation tickets for each power grid; During the process of the target power grid sequentially executing each power grid dispatch operation ticket according to the execution order, after an abnormal operation ticket is detected, the missing pre-operation is determined based on the standard pre-operation and actual pre-operation associated with the abnormal operation ticket; wherein, the abnormal operation ticket is a power grid dispatch operation ticket that contains a power grid dispatch operation that failed the feasibility verification. Based on the power grid operation data of the target power grid and the operation type of the missing pre-operation, determine the executability of the abnormal operation ticket; If the executable condition is that execution can continue, the execution strategy for the abnormal operation ticket is determined according to the reason for the missing operation of the missing preceding operation, and the abnormal operation ticket and the power grid dispatch operation ticket following the abnormal operation ticket are executed according to the execution strategy and the execution order.

2. The method according to claim 1, characterized in that, The step of determining the executable status of the abnormal operation ticket based on the power grid operation data of the target power grid and the operation type of the missing preceding operation includes: Based on the power grid operation data of the target power grid, determine the electrical safety information, mechanical status information, and system redundancy information corresponding to the missing pre-operation; wherein, the system redundancy information is the redundancy information of each module in the sequential control system that executes the power grid dispatch operation ticket; Based on the electrical safety information, the mechanical status information, and the system redundancy information, determine the operational risk value of the missing pre-operation; Based on the operational risk value and operation type of the missing pre-operation, the executability of the abnormal operation ticket is determined.

3. The method according to claim 2, characterized in that, The step of determining the executable status of the abnormal operation ticket based on the operation risk value and operation type of the missing preceding operation includes: If the operation type with missing prerequisite operations is a critical operation type, the executable status of the abnormal operation ticket is determined to be unexecutable. If the operation type with missing prerequisite operations does not belong to the critical operation type, the executability of the abnormal operation ticket is determined based on the operation risk value of the missing prerequisite operations.

4. The method according to claim 1, characterized in that, The step of determining the execution strategy for the abnormal operation ticket based on the reason for the missing preceding operation includes: When the reason for the missing operation of the pre-operation is that the parameter value of a non-critical parameter is outside the target parameter range corresponding to the non-critical parameter, the parameter difference ratio is determined based on the minimum parameter difference between the parameter value and the target parameter range. If the parameter difference ratio is less than a ratio threshold, the target parameter range is adjusted according to the parameter value; wherein the adjusted target parameter range includes the parameter value.

5. The method according to claim 1, characterized in that, If the executable condition is that execution cannot continue, the method further includes: Extract key operational elements from the missing preceding operations; Based on the standard operation and maintenance strategy associated with the key operation elements, determine the operation and maintenance strategy for the missing pre-operation and send the operation and maintenance strategy to the operation and maintenance end.

6. The method according to claim 1, characterized in that, If the executable condition is that execution cannot continue, the method further includes: Send an operation confirmation request to the operation and maintenance terminal of the target power grid; Upon receiving the operation confirmation instruction from the operation and maintenance terminal, the abnormal operation ticket and the subsequent power grid dispatch operation ticket shall continue to be executed according to the execution order.

7. A device for processing power grid dispatching operation tickets, characterized in that, The device includes: The request receiving module is used to receive dispatch requests for a target power grid; wherein, the dispatch request includes dispatch operation tickets for each power grid and the execution order among the dispatch operation tickets for each power grid; The operation determination module is used to determine the missing pre-operation based on the standard pre-operation and the actual pre-operation associated with the abnormal operation ticket after detecting an abnormal operation ticket during the process of the target power grid sequentially executing each power grid dispatch operation ticket according to the execution order; wherein, the abnormal operation ticket is a power grid dispatch operation ticket that contains a power grid dispatch operation that failed the feasibility verification. The judgment module is used to determine the executability of the abnormal operation ticket based on the power grid operation data of the target power grid and the operation type of the missing pre-operation. The operation adjustment module is used to determine the execution strategy of the abnormal operation ticket based on the reason for the missing operation of the missing preceding operation when the executable condition is that it can continue to be executed, and to continue to execute the abnormal operation ticket and the power grid dispatch operation ticket after the abnormal operation ticket according to the execution strategy and the execution order.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images