Method and system for auditing power grid dispatching operation instruction ticket

Abstract

The invention provides an auditing method and system for a power grid dispatching operation instruction ticket. The method comprises the following steps: acquiring a to-be-audited instruction ticket; extracting key information of the instruction ticket to form a structured instruction ticket; judging whether the structured instruction ticket meets a preset format requirement or not; judging whether the structured instruction ticket comprises more than two instruction tickets or not; judging whether the execution sequence of the more than two instruction tickets meets a preset condition and an operation habit or not; acquiring a real-time state of the equipment; judging whether the real-time state of the equipment meets the execution condition of the structured instruction ticket or not; acquiring an equipment ledger of the power grid; judging whether the structured instruction ticket is consistent with the equipment information in the equipment ledger or not; and generating an audit report according to a judgment result. And four-layer verification is carried out on the instruction ticket, so that the intelligent level of instruction ticket auditing is remarkably improved. While safe operation of a power grid is guaranteed, the cost of manually checking the instruction ticket is greatly reduced, and the efficiency of checking the instruction ticket is remarkably improved.

Description

Technical Field

[0001] This invention relates to the field of power system automation control, and in particular to a method and system for reviewing power grid dispatch operation instruction tickets. Background Technology

[0002] A power grid dispatching operation instruction ticket (also known as an instruction ticket or operation ticket) is a written command document issued by the dispatching agency in the power system to guide relevant units in completing corresponding adjustments. Its core function is to ensure the safety and standardization of power system operations. Currently, the review of instruction tickets is mainly conducted manually by dispatchers, which heavily relies on their experience. Dispatchers need to manually compare the real-time status of the power grid, review equipment ledgers, and verify the correctness and logic of the information on the ticket item by item according to the "Dispatching Regulations" and "Implementation Rules." However, manual review of instruction tickets is inefficient and prone to errors, and usually requires multiple people to check the tickets to ensure their accuracy. Summary of the Invention

[0003] This invention provides a method and system for reviewing power grid dispatching operation instruction tickets, in order to solve the technical problems that manual review of power grid dispatching operation instruction tickets is inefficient and prone to errors.

[0004] To address the aforementioned technical problems, this invention provides a method for reviewing power grid dispatching operation instruction tickets, comprising the following steps:

[0005] S1. Obtain the instruction ticket to be reviewed;

[0006] S2. Extract the key information of the instruction ticket to form a structured instruction ticket;

[0007] S3. Determine whether the structured instruction ticket meets the preset format requirements. If it does not meet the requirements, proceed to step S4; if it does meet the requirements, proceed to step S5.

[0008] S4. Incorrect annotation format;

[0009] S5. Determine whether the structured instruction ticket includes two or more instruction tickets. If yes, proceed to step S6; otherwise, proceed to step S8.

[0010] S6. Determine whether the execution order of two or more instruction tickets meets the preset conditions and operating habits. If not, proceed to step S7; if so, proceed to step S8.

[0011] S7, Logical conflict in annotation;

[0012] S8. Obtain the real-time status of the equipment through the energy management system;

[0013] S9. Determine whether the real-time status of the device meets the execution conditions of the structured instruction ticket. If not, proceed to step S10; if so, proceed to step S11.

[0014] S10, Status conflict;

[0015] S11. Obtain the equipment ledger of the power grid;

[0016] S12. Determine whether the structured instruction ticket and the equipment information in the equipment ledger are consistent. If they are inconsistent, proceed to step S13; if they are consistent, proceed to step S14.

[0017] S13, Labeling mismatch;

[0018] S14. Generate an audit report based on the judgment results of steps S3, S6, S9 and S12.

[0019] Preferably, the method further includes the following step: dynamically updating the rule base, wherein the rule base includes the format requirements of the instruction ticket, the execution order requirements of the instruction ticket, operating habits, and the status requirements of the device when the instruction ticket is executed.

[0020] Preferably, the step of dynamically updating the rule base includes the following steps:

[0021] Obtain historical instruction tickets approved within the first preset time period of the target substation;

[0022] The historical instruction tickets are standardized to unify equipment identification and operating terminology;

[0023] Cluster analysis was performed on the historical instruction tickets to obtain typical patterns for each operation type;

[0024] Repeat the above steps at the second preset time.

[0025] Preferably, the preset conditions in step S6 are determined by a directed acyclic graph, which includes nodes and edges. Each instruction ticket represents a node, and the dependencies between instruction tickets are edges.

[0026] Preferably, after step S14, the following step is also included: S15, sending the audit report to the scheduling workstation.

[0027] Preferably, step S8 includes the following steps: connecting to the energy management system via the CIM / GID interface of the IEC61970 standard to obtain the real-time status of the equipment.

[0028] Preferably, the real-time status of the device includes the device operating status and power grid operating parameters.

[0029] Preferably, the equipment ledger is obtained through the production management system, and the equipment ledger includes the equipment name, equipment model, substation to which it belongs, and the allowed range of state transitions.

[0030] The present invention also provides a system for reviewing power grid dispatching operation instruction tickets. The system is used to execute the review method for power grid dispatching operation instruction tickets described in any of the preceding claims. The system includes the following modules:

[0031] The acquisition module is used to acquire instruction tickets pending review;

[0032] The extraction module is used to extract key information from the instruction ticket and form a structured instruction ticket;

[0033] The format verification module is used to determine whether the structured instruction ticket meets the preset format requirements;

[0034] The formatting annotation module is used to annotate formatting errors;

[0035] The multi-ticket association verification module is used to determine whether the structured instruction ticket includes two or more instruction tickets, and to determine whether the execution order of the two or more instruction tickets meets preset conditions and operating habits.

[0036] The multi-vote association annotation module is used to annotate logical conflicts;

[0037] The communication module is used to obtain the real-time status of the equipment through the energy management system;

[0038] A real-time status verification module is used to determine whether the real-time status of the device meets the execution conditions of the structured instruction ticket;

[0039] Real-time status annotation module, used to annotate status conflicts;

[0040] The communication module is also used to obtain the real-time status of the production management system;

[0041] The equipment ledger adaptation module is used to determine whether the structured instruction ticket and the equipment information in the equipment ledger are consistent.

[0042] The equipment ledger adaptation and annotation module is used to annotate adaptation errors;

[0043] The output module is used to generate audit reports.

[0044] Preferably, the system further includes a rule base module, which is used to perform the following steps: dynamically updating the rule base, wherein the rule base includes the format requirements of the instruction ticket, the execution order requirements of the instruction ticket, operating habits, and the device status requirements when the instruction ticket is executed.

[0045] This invention provides a method and system for reviewing power grid dispatch operation command tickets. By performing four layers of verification—format validation, multi-ticket correlation validation, real-time status validation, and equipment ledger adaptation validation—the system significantly improves the intelligence level of command ticket review. Whether it's a simple single command ticket or a complex multi-command ticket, this solution can be used for review. The average verification time for a single command ticket is reduced from approximately 30 minutes to approximately 3 minutes, the error rate due to inconsistent terminology is reduced by approximately 40%, and the detection rate of sequence errors and logical conflicts such as bus and main transformer state transitions is increased to approximately 99%. It also successfully intercepts high-risk operations such as asynchronous loop closures and protection malfunctions. This invention significantly reduces the cost of manual command ticket review and significantly improves the efficiency of command ticket review while ensuring the safe operation of the power grid. Attached Figure Description

[0046] Figure 1 This is a flowchart of a method for reviewing power grid dispatching operation instruction tickets according to an embodiment of the present invention. Detailed Implementation

[0047] To make the objectives, advantages, and features of the present invention clearer, the following detailed description of the method and system for reviewing power grid dispatching operation command tickets proposed by the present invention, in conjunction with the accompanying drawings, is provided. It should be noted that the drawings are all in a very simplified form and use non-precise proportions, and are only used to facilitate and clearly illustrate the objectives of the embodiments of the present invention.

[0048] In the description of this invention, the terms "first," "second," and other qualifiers are added for convenience of description and reference, and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with qualifiers such as "first" and "second" may explicitly or implicitly include one or more of that feature.

[0049] like Figure 1 As shown, the present invention provides a method for reviewing power grid dispatching operation instruction tickets, comprising the following steps:

[0050] S1. Obtain the instruction ticket to be reviewed; the dispatcher can enter the instruction ticket to be reviewed into the review system, which can be a computer capable of processing computer programs.

[0051] S2. Extract key information from the instruction ticket to form a structured instruction ticket. Key information from the instruction ticket can be extracted using Natural Language Processing (NLP) technology, including fields such as operation unit, operation task, operation item, and planned execution time, to form a structured instruction ticket model and avoid the impact of textual ambiguity on the verification results.

[0052] Taking the "Maple Leaf Hill Station #2 Busbar Overhaul" instruction ticket as an example, the structured instruction ticket formed by extracting key information can be represented by Table 1:

[0053] Table 1. Examples of Structured Instruction Tickets

[0054] S3. Determine whether the structured instruction ticket meets the preset format requirements. If not, proceed to step S4; if it does, proceed to step S5. This step can be called format verification: the format of the instruction ticket can be standardized and verified based on the "Implementation Rules for Power Grid Dispatch Operation Instruction Ticket Management" to ensure the standardization of the format and provide a unified data foundation for subsequent verification. Format verification can be divided into the following three steps:

[0055] The first step is to verify the number format. Check whether the instruction ticket number conforms to the structure of "6-digit year and month + 4-digit serial number", where the first 4 digits are the year and the last 2 digits are the month. The serial number starts from 0001 and increments to ensure that the number is unique and traceable.

[0056] The second step is to verify the time format. Check whether the planned execution time is in 24-hour format and conforms to the format of "year-month-day hour:minute:second" to avoid time ambiguity.

[0057] Step 3: Terminology Consistency Verification: Check whether the equipment state transition terminology is standard. The state sequence must follow the order of "Operation → Hot Standby → Cold Standby → Maintenance," and skipping intermediate states or using abbreviations is prohibited (e.g., "Hot Standby" must be corrected to "Hot Standby"). Example of format verification rules is shown in Table 2:

[0058] Table 2. Format Validation Rules

[0059] Taking the "Maple Leaf Hill Station #2 Busbar Transfer for Maintenance" order as an example:

[0060] Number verification: The instruction ticket number is “2024110001”, which conforms to the structure of “6-digit year and month (202411) + 4-digit serial number (0001)”, and the verification is successful; if the number is “20241101” (the serial number is only 2 digits), then it is marked “incorrect number format, the serial number needs to be supplemented to 4 digits”.

[0061] Time verification: The planned execution time is "2024-11-15 14:00:00", which conforms to the 24-hour system and standard format, and the verification passes; if the time is "2024-11-15 2:00 PM", then mark "Time format error, 24-hour system must be used".

[0062] Terminology verification: The operation item “#2 busbar changes from operation to hot standby” uses standard terminology and passes verification; if it is expressed as “#2 busbar changes from operation to cold standby” (skipping hot standby) or “#2 busbar changes from operation to hot standby” (abbreviation), it is marked as “Terminology error, standard state sequence or complete terminology must be used”.

[0063] S4. Error in annotation format; When an annotation format is incorrect, you can simply indicate the format error, or you can indicate the specific reason for the error, such as non-compliant numbering, and generate correction suggestions.

[0064] S5. Determine whether the structured instruction ticket includes two or more instruction tickets. If yes, proceed to step S6; otherwise, proceed to step S8. If the structured instruction ticket includes only one instruction ticket, proceed to step S8; if it includes more than one instruction ticket, proceed to step S6.

[0065] S6. Determine whether the execution order of two or more instruction tickets meets the preset conditions and operating habits. If not, proceed to step S7; if so, proceed to step S8. Preferably, the preset conditions in step S6 are determined by a directed acyclic graph (DAG). The DAG includes nodes and edges, with each instruction ticket representing a node, and the dependencies between instruction tickets represented by edges. This step can be called multi-ticket association verification: for instruction tickets with dependencies, the logical conflict between multiple tickets is resolved by verifying the execution order and state transmission logic. The preset conditions in this step can be determined by modeling a directed acyclic graph (DAG). The modeling process consists of the following three steps:

[0066] The first step is to define the dependencies and clarify the two types of multi-ticket dependencies: execution order dependency (a certain instruction ticket can only be started after another instruction ticket has been executed) and state transitivity dependency (the device state result of the preceding instruction ticket is a prerequisite for the execution of the subsequent instruction ticket).

[0067] The second step is to construct the DAG model. Each instruction ticket is defined as a "node" in the DAG. The node attributes include ticket number, operation object, post-operation device status, and planned execution time. If ticket X is a predecessor ticket of ticket Y, then a "directed edge" is constructed from X to Y. The edge attributes are labeled with the dependency type (execution order dependency / state transitive dependency).

[0068] The third step is topology sorting verification. This step verifies whether the multi-vote execution sequence to be reviewed conforms to the DAG dependency relationship using a topology sorting algorithm. First, the "in-degree" of all nodes (the number of edges pointing to that node, i.e., the number of preceding votes) is calculated. Nodes with an in-degree of 0 are sequentially added to the sorting result, while the node and its outgoing edges are deleted, and the in-degree of subsequent nodes is updated. If the sorting result contains all nodes and is consistent with the sequence to be reviewed, the verification passes. If there are no nodes with an in-degree of 0 or the sorting result is inconsistent with the sequence to be reviewed, it is marked as a logical conflict. The verification rules are shown in Table 3.

[0069] Table 3. Examples of rules for the execution order of multiple votes

[0070] Taking the "Maple Leaf Mountain Station #2 Busbar to Maintenance" task as an example, this task involves 3 instruction tickets. The constructed DAG model is as follows: "Ticket 1, Status after disconnecting the #2 busbar PT switch: PT switch disconnected" → "Ticket 2, Status after switching the #2 busbar to cold standby: Busbar cold standby" → "Ticket 3, Status after switching the #2 busbar to maintenance: Busbar maintenance". By performing topological sorting on this DAG model, the standard execution sequence is obtained as "Ticket 1 → Ticket 2 → Ticket 3". If the execution sequence of multiple tickets to be reviewed is "Ticket 2 → Ticket 1 → Ticket 3", the review system can mark "Ticket 1 is in the wrong order, Ticket 1 should be executed, Ticket 2 is actually executed", and prompt you to adjust the execution order.

[0071] S7. Mark logical conflicts; When marking logical conflicts, you can mark only the logical conflict, or you can mark specific reasons for the conflict, such as the execution order of the first and second tickets being reversed.

[0072] S8. Obtain the real-time status of the equipment through the Energy Management System (EMS). Preferably, the real-time status of the equipment is obtained by connecting to the EMS through the CIM / GID (Common Information Model / Generic Interface Definition) interface of the IEC 61970 standard (a series of international standards for application programming interfaces of energy management systems developed by the International Electrotechnical Commission). EMS includes SCADA (Supervisory Control And Data Acquisition), and EMS can also be called SCADA / EMS. The CIM / GID interface supports second-level refresh of real-time data. The core data obtained from the EMS in real time includes the equipment operating status (switch on / off status, bus / transformer load) and grid operating parameters (bus voltage, phase difference between the two systems, frequency).

[0073] S9. Determine whether the real-time status of the device meets the execution conditions of the structured instruction ticket. If not, proceed to step S10; if so, proceed to step S11. This step can be called EMS real-time status verification: by dynamically calling the real-time data of the EMS, verify whether the operation items comply with the current operating constraints of the power grid, avoiding the lag of static verification.

[0074] To ensure the power grid is in a safe state when executing the operations corresponding to the instruction ticket, the items that need to be verified include busbar maintenance verification (verifying whether the load is switched to another load), synchronization loop verification (verifying whether the voltage difference, phase difference, and frequency difference meet the preset conditions), and main transformer operation verification (verifying whether the load exceeds the limit). Examples of verification rules are shown in Table 4.

[0075] Table 4. Examples of Verification Rules

[0076] The acquired real-time data is compared with preset safety thresholds. If the thresholds are met, the operation is allowed; otherwise, it is marked as a state conflict. Synchronous loop closing is a high-risk operation for the power grid. It is necessary to determine whether the phase difference, voltage difference, and frequency difference between the two systems meet preset conditions to ensure that the operation is shock-free.

[0077] Example 1: Busbar maintenance and verification

[0078] Taking "Maple Leaf Mountain Station #2 busbar to maintenance" as an example, the system obtains the following data through EMS: #2 busbar rated capacity is 500MW, real-time active load is 0.5MW, and all associated feeder switches are in the open position. The calculated load percentage is (0.5 / 500%=0.1%), which does not exceed the preset threshold (0.1%), and the feeder switches are open, so it is determined that "load switching meets the requirements" and the maintenance operation is allowed. If the real-time load is 1MW (0.2%), the system will mark "load not switched" and prompt "the #2 busbar load needs to be transferred to the #1 busbar and then retried".

[0079] Example 2: Simultaneous loop closure check

[0080] Taking the "220kV Maple Leaf Mountain Substation #2 line loop closure" as an example, the system collects data in real time through EMS: left-side voltage 225kV, right-side voltage 218kV, left-side phase 120°, right-side phase 145°, left-side frequency 50.0Hz, right-side frequency 50.1Hz. Calculate each component: voltage difference percentage (|225-218| / 220%=3.18%) (≤5%), phase difference 25° (≤35°), frequency difference 0.1Hz (≤0.2Hz). If the condition is met, the system is deemed to "meet the conditions for synchronous loop closure," and operation is allowed. If the phase difference is 35°, the system is marked "Synchronous loop closure is risky," operation is prohibited, and an alarm is triggered.

[0081] S10. Mark status conflict; When marking status conflict, you can mark only the status conflict, or you can mark the specific conflict reason, such as bus load not being switched, and trigger a risk alarm.

[0082] S11. Obtain the equipment ledger of the power grid. Preferably, the equipment ledger is obtained through a production management system (PMS), and the equipment ledger includes the equipment name, equipment model, substation to which it belongs, and the allowed range of state transitions.

[0083] S12. Determine whether the structured instruction ticket and the equipment information in the equipment ledger are consistent. If they are inconsistent, proceed to step S13; if they are consistent, proceed to step S14. This step can be called equipment ledger adaptation verification: by connecting to the equipment ledger, verify the legality of the operation object and the feasibility of the state transition, and adapt to the equipment naming rules of different substations to ensure that the verification result is consistent with the actual situation on site.

[0084] S13. Mark adaptation error; When marking adaptation error, you can simply mark "adaptation error" or mark specific error reasons such as "equipment name does not match the ledger".

[0085] S14. Based on the judgment results of steps S3, S6, S9, and S12, generate an audit report. The audit report is used to visually present the audit results and may include information such as "error type, error location, correction suggestions, and risk level." For high-risk items, an audible and visual alarm can be triggered and simultaneously pushed to the dispatcher's workstation to ensure timely risk handling. The execution order of steps S1-S14 can be either as described above or not. For example, the execution order of steps S9 and S5 can be swapped, as can the execution order of steps S12 and S9.

[0086] This invention provides a method for reviewing power grid dispatch operation command tickets. By performing four layers of verification—format validation, multi-ticket correlation validation, real-time status validation, and equipment ledger adaptation validation—this method significantly improves the intelligence level of command ticket review. Whether it's a simple single command ticket or a complex multi-command ticket, this solution can be used for review. The average verification time for a single command ticket is reduced from approximately 30 minutes to approximately 3 minutes, the error rate due to inconsistent terminology is reduced by approximately 40%, and the detection rate of sequence errors and logical conflicts such as bus and main transformer state transitions is increased to approximately 99%. It also successfully intercepts high-risk operations such as asynchronous loop closure and protection malfunctions. This invention significantly reduces the cost of manual command ticket review and significantly improves the efficiency of command ticket review while ensuring the safe operation of the power grid.

[0087] Preferably, the method further includes the following step: S16, dynamically updating the rule base, wherein the rule base includes the format requirements of the instruction ticket, the execution order requirements of the instruction ticket, operating habits, and the equipment status requirements when the instruction ticket is executed. Dynamically updating the rule base can adapt to the naming rules and operating habits of different substations, and can improve the verification accuracy to over 98%.

[0088] Preferably, the step of dynamically updating the rule base, namely S16, includes the following steps:

[0089] S161. Obtain historical instruction tickets approved within the first preset time period of the target substation; you can filter valid instruction tickets of the target substation within the first preset time period, such as the past 3 years, from the historical instruction ticket database, and remove abnormal tickets that are invalid or have been modified more than 3 times.

[0090] S162. Standardize the historical instruction tickets to unify the identification of equipment and operation terminology; the operation item sequence can be extracted and standardized, for example, by replacing the equipment name with a common identifier and unifying the operation terminology, so as to avoid naming differences from affecting the clustering results.

[0091] S163. Perform cluster analysis on the historical instruction tickets to obtain typical patterns for each operation type. The K-means clustering algorithm can be used to cluster the preprocessed operation item sequence to identify typical operation patterns. The optimal number of clusters is determined by combining the "elbow rule" with the silhouette coefficient. The cluster centers are iteratively optimized using "operation step similarity" as the distance metric to finally obtain the typical patterns for each operation type (such as bus operation pattern and main transformer operation pattern).

[0092] S164. Repeat the above steps according to the second preset time. The typical operation patterns obtained from clustering can be combined with the equipment ledger to generate personalized rules for the substation and stored in the dynamic rule base. The second preset time can be one month, meaning that the operation ticket data for the past month will be automatically re-clustered monthly. If the compliance rate of a rule significantly decreases (e.g., from 95% to 80%), a rule update will be triggered to ensure that the rules are synchronized with on-site practices. The dynamic rule base update rules are shown in Table 5:

[0093] Table 5. Rules for updating the rule base

[0094] Taking the dynamic update of the busbar operation mode at Maple Leaf Hill Station as an example:

[0095] January-March 2024: Historical data clustering shows that the operation mode for busbar switching to maintenance is "automatic transfer from standby → circuit breaker disconnection → switch to cold standby", with a compliance rate of 95%. This rule has been incorporated into the dynamic rule base.

[0096] April 2024: Maple Mountain Station added bus #3, and the operation habit was adjusted to "disconnect switch → automatically switch off standby → switch to cold standby". The compliance rate of this mode in the operation tickets in April reached 92%.

[0097] May 2024: The system automatically re-clustered nearly a month's worth of data and found that the compliance rate of the original rule had dropped to 7%, while the compliance rate of the new pattern reached 92%. Therefore, the rule was updated to "When the busbar at Maple Mountain Station is transferred for maintenance, the associated switch must be disconnected first, and then the standby automatic transfer device must be deactivated" to ensure that the verification results are consistent with the new on-site practices.

[0098] Preferably, after step S14, the following step is also included: S15, sending the audit report to the dispatch workstation. If the audit system is set up at the dispatch workstation, step S15 is not required; if the audit system is not set up at the dispatch workstation, step S15 can be executed so that the dispatcher can view the audit report of the instruction ticket in a timely manner.

[0099] Based on the same technical concept as the above-described method for reviewing power grid dispatching operation instruction tickets, this embodiment provides a system for reviewing power grid dispatching operation instruction tickets. The system is used to execute the method for reviewing power grid dispatching operation instruction tickets described above, and includes the following modules:

[0100] The acquisition module is used to acquire instruction tickets pending review;

[0101] The extraction module is used to extract key information from the instruction ticket and form a structured instruction ticket;

[0102] The format verification module is used to determine whether the structured instruction ticket meets the preset format requirements;

[0103] The formatting annotation module is used to annotate formatting errors;

[0104] The multi-ticket association verification module is used to determine whether the structured instruction ticket includes two or more instruction tickets, and to determine whether the execution order of the two or more instruction tickets meets preset conditions and operating habits.

[0105] The multi-vote association annotation module is used to annotate logical conflicts;

[0106] The communication module is used to obtain the real-time status of the equipment through the energy management system;

[0107] A real-time status verification module is used to determine whether the real-time status of the device meets the execution conditions of the structured instruction ticket;

[0108] Real-time status annotation module, used to annotate status conflicts;

[0109] The communication module is also used to obtain the equipment ledger of the power grid;

[0110] The equipment ledger adaptation module is used to determine whether the structured instruction ticket and the equipment information in the equipment ledger are consistent.

[0111] The equipment ledger adaptation and annotation module is used to annotate adaptation errors;

[0112] The output module is used to generate audit reports.

[0113] This embodiment provides a power grid dispatching operation command ticket review system. Through four layers of verification—format validation, multi-ticket correlation validation, real-time status validation, and equipment ledger adaptation validation—the system significantly improves the intelligence level of command ticket review. Whether it's a simple single command ticket or a complex multi-command ticket, this solution can be used for review. The average verification time for a single command ticket is reduced from approximately 30 minutes to approximately 3 minutes, the error rate of inconsistent terminology is reduced by approximately 40%, and the detection rate of sequence errors and logical conflicts such as bus and main transformer status transitions is increased to approximately 99%. It also successfully intercepts high-risk operations such as asynchronous loop closure and protection malfunctions. This invention significantly reduces the cost of manual command ticket review and significantly improves the efficiency of command ticket review while ensuring the safe operation of the power grid.

[0114] Preferably, the system further includes a rule base module, which performs the following steps: dynamically updating the rule base, wherein the rule base includes the format requirements for instruction tickets, the execution order requirements for instruction tickets, operating habits, and the equipment status requirements when the instruction ticket is executed. Dynamically updating the rule base can adapt to the naming rules and operating habits of different substations, and can improve the verification accuracy to over 98%.

[0115] In summary, the present invention provides a method and system for reviewing power grid dispatch operation command tickets. By performing four layers of verification—format validation, multi-ticket correlation validation, real-time status validation, and equipment ledger adaptation validation—the system significantly improves the intelligence level of command ticket review. Whether it's a simple single command ticket or a complex multi-command ticket, this solution can be used for review. The average verification time for a single command ticket is reduced from approximately 30 minutes to approximately 3 minutes, the error rate of inconsistent terminology is reduced by approximately 40%, and the detection rate of sequence errors and logical conflicts such as bus and main transformer state transitions is increased to approximately 99%. Furthermore, it successfully intercepts high-risk operations such as asynchronous loop closure and protection misoperation. This invention significantly reduces the cost of manual command ticket review and significantly improves the efficiency of command ticket review while ensuring the safe operation of the power grid.

[0116] The above description is only a description of preferred embodiments of the present invention and is not intended to limit the scope of the present invention in any way. Any changes or modifications made by those skilled in the art based on the above disclosure shall fall within the protection scope of the present invention.

Claims

1. A method for reviewing power grid dispatching operation instruction tickets, characterized in that, Includes the following steps: S1. Obtain the instruction ticket to be reviewed; S2. Extract the key information of the instruction ticket to form a structured instruction ticket; S3. Determine whether the structured instruction ticket meets the preset format requirements. If it does not meet the requirements, proceed to step S4; if it does meet the requirements, proceed to step S5. S4. Incorrect annotation format; S5. Determine whether the structured instruction ticket includes two or more instruction tickets. If yes, proceed to step S6; otherwise, proceed to step S8. S6. Determine whether the execution order of two or more instruction tickets meets the preset conditions and operating habits. If not, proceed to step S7; if so, proceed to step S8. S7, Logical conflict in annotation; S8. Obtain the real-time status of the equipment through the energy management system; S9. Determine whether the real-time status of the device meets the execution conditions of the structured instruction ticket. If not, proceed to step S10; if so, proceed to step S11. S10, Status conflict; S11. Obtain the equipment ledger of the power grid; S12. Determine whether the structured instruction ticket and the equipment information in the equipment ledger are consistent. If they are inconsistent, proceed to step S13; if they are consistent, proceed to step S14. S13, Labeling mismatch; S14. Generate an audit report based on the judgment results of steps S3, S6, S9 and S12.

2. The method for reviewing power grid dispatching operation instruction tickets as described in claim 1, characterized in that, The method further includes the following steps: dynamically updating the rule base, wherein the rule base includes the format requirements of the instruction ticket, the execution order requirements of the instruction ticket, operating habits, and the status requirements of the device when the instruction ticket is executed.

3. The method for reviewing power grid dispatching operation instruction tickets as described in claim 2, characterized in that, The steps for dynamically updating the rule base include the following: Obtain historical instruction tickets approved within the first preset time period of the target substation; The historical instruction tickets are standardized to unify equipment identification and operating terminology; Cluster analysis was performed on the historical instruction tickets to obtain typical patterns for each operation type; Repeat the above steps at the second preset time.

4. The method for reviewing power grid dispatching operation instruction tickets as described in claim 1, characterized in that, The preset conditions in step S6 are determined by a directed acyclic graph, which includes nodes and edges. Each instruction ticket represents a node, and the dependencies between instruction tickets are edges.

5. The method for reviewing power grid dispatching operation instruction tickets as described in claim 1, characterized in that, Step S14 is followed by the following step: S15, sending the audit report to the scheduling workstation.

6. The method for reviewing power grid dispatching operation instruction tickets as described in claim 1, characterized in that, Step S8 includes the following steps: Connecting to the energy management system via the CIM / GID interface of the IEC61970 standard to obtain the real-time status of the equipment.

7. The method for reviewing power grid dispatching operation instruction tickets as described in claim 6, characterized in that, The real-time status of the equipment includes the equipment operating status and power grid operating parameters.

8. The method for reviewing power grid dispatching operation instruction tickets as described in claim 1, characterized in that, The equipment ledger is obtained through the production management system. The equipment ledger includes the equipment name, equipment model, substation to which it belongs, and the allowed range of state transitions.

9. A system for reviewing power grid dispatching operation instruction tickets, characterized in that, The system is used to execute the method for reviewing power grid dispatching operation instruction tickets according to any one of claims 1-8, and the system includes the following modules: The acquisition module is used to acquire instruction tickets pending review; The extraction module is used to extract key information from the instruction ticket and form a structured instruction ticket; The format verification module is used to determine whether the structured instruction ticket meets the preset format requirements; The formatting annotation module is used to annotate formatting errors; The multi-ticket association verification module is used to determine whether the structured instruction ticket includes two or more instruction tickets, and to determine whether the execution order of the two or more instruction tickets meets preset conditions and operating habits. The multi-vote association annotation module is used to annotate logical conflicts; The communication module is used to obtain the real-time status of the equipment through the energy management system; A real-time status verification module is used to determine whether the real-time status of the device meets the execution conditions of the structured instruction ticket; Real-time status annotation module, used to annotate status conflicts; The communication module is also used to obtain the equipment ledger of the power grid; The equipment ledger adaptation module is used to determine whether the structured instruction ticket and the equipment information in the equipment ledger are consistent. The equipment ledger adaptation and annotation module is used to annotate adaptation errors; The output module is used to generate audit reports.

10. The power grid dispatching operation instruction ticket verification system as described in claim 9, characterized in that, The system also includes a rule base module, which is used to perform the following steps: dynamically updating the rule base, wherein the rule base includes the format requirements of the instruction ticket, the execution order requirements of the instruction ticket, operating habits, and the status requirements of the device when the instruction ticket is executed.

Images