Cooperative generation and closed-loop checking method, system and equipment for operation tickets of primary and secondary equipment of power system, and storage medium

Abstract

The invention discloses a cooperative generation and closed-loop checking method, system and device for primary and secondary device operation tickets of an electric power system and a storage medium, and the cooperative generation and closed-loop checking method for the primary and secondary device operation tickets comprises the steps: constructing a primary device ticket forming rule tree, and according to a dynamic binding relationship between a primary device rule and a secondary device rule chain, establishing a secondary device ticket forming rule tree; according to the method, intelligent alternate generation of primary and secondary operation steps is realized, and in the invoicing process, consistency checking of primary and secondary equipment state logic is synchronously carried out: through a forward reasoning and reverse tracking mechanism, whether a primary and secondary equipment state mapping relation before and after each step of operation is correct is judged in real time, and an alarm is given for an inconsistent condition. Therefore, self-verification of safety logic is completed while the operation order is generated, a complete closed loop of generation-simulation-check is formed, and the accuracy of the operation order and the safety of field operation are remarkably improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of power system automation, and in particular to a method, system and device for collaborative generation and closed-loop checking of power system primary and secondary equipment operation tickets, and a storage medium. BACKGROUND

[0002] In power system operation and maintenance, switching operation is a core business, and operation tickets are instructions for ensuring operation safety. In actual power grid operation, primary equipment operation and secondary equipment protection operation need to be strictly interleaved according to logical order. Existing operation ticket automatic generation systems have significant defects: first, most systems mainly focus on primary equipment operation logic, and secondary equipment operation steps rely on manual experience for addition, which is tedious and prone to errors or omissions; second, there is a lack of automatic modeling and checking capability for deep coupling relationship between primary equipment state and secondary equipment state, which cannot predict potential operation risks caused by improper protection coordination at the ticket generation stage. It is difficult for operation personnel to ensure that each generated operation ticket is completely self-consistent in logic, especially the verification of the synergy of primary and secondary steps in complex operations still requires a large amount of manpower, which has become a technical bottleneck restricting the improvement of power grid operation efficiency and safety level. SUMMARY

[0003] The present application aims to provide a method for collaborative generation and closed-loop checking of primary and secondary equipment operation tickets, which can deeply integrate primary and secondary equipment operation logic to realize collaborative generation and real-time safety checking of operation tickets in a unified framework. Another object of the present application is to provide a system, device and storage medium for collaborative generation and closed-loop checking of primary and secondary equipment operation tickets of a power system.

[0004] The technical solution of the present application is as follows: According to the relationship among operation terms, equipment states and equipment semantics, a primary equipment ticket generation rule tree is established, a primary equipment operation ticket is generated, and primary equipment operation steps are determined; Based on the binding relationship between predefined primary equipment rules and secondary equipment rules, during the traversal of the primary equipment ticket generation rule tree, a secondary equipment rule chain associated with the primary equipment ticket generation rule is dynamically triggered and executed in sequence, and secondary equipment operation steps are generated; The secondary equipment operation steps are inserted into the specified logical position of the corresponding primary equipment operation step sequence to form a primary and secondary mixed operation ticket; While generating and simulating the execution of the primary and secondary mixed operation ticket steps, the safety checking of each step is performed according to the predefined primary and secondary equipment state mapping relationship.

[0005] Further, the safety checking includes forward reasoning checking and backward tracking checking.

[0006] Further, the forward reasoning check is that when the operation is a primary device operation, the primary device target state after the forward reasoning operation is checked according to the mapping relationship to check whether the corresponding secondary device state meets the secondary device expected state corresponding to the primary device target state.

[0007] Further, the reverse tracking check is that when the operation is a secondary device signal operation, the affected secondary device state is tracked in reverse, and it is checked whether it leads to a conflict with the current primary device state.

[0008] Further, the steps of the forward reasoning check are as follows: Reasoning the primary device target state after the operation according to the primary device operation term, the current device state and the device topology relationship; Based on the mapping relationship library of the primary device state and the secondary device state, it is judged whether the corresponding secondary device state is needed for the primary device target state; If the corresponding secondary device state is needed, it is checked whether the related secondary device signal in the current system is consistent with the secondary device expected state according to the instantiated secondary device state logic rule; if not, an alarm information is output.

[0009] Further, the steps of the reverse tracking check are as follows: Traverse the secondary device state definition library to obtain all state logic rules containing the current operation signal; Based on the current secondary signal, the secondary device state is calculated, the primary device and its state which should be matched are reversely mapped, and the actual primary device state is judged; If the matched primary device state is consistent with the actual primary device state, the secondary device state is recalculated based on the secondary signal after the operation; It is judged whether the secondary device state after reasoning is consistent with the actual primary device state, and if not, an alarm is generated.

[0010] Further, the secondary device state adopts a hierarchical structure, and the top-level secondary device state can be combined by the logic relationship of the lower-level secondary device sub-state or the atomic-level secondary device signal; the logic relationship includes "and", "or", "not" relationship; the atomic-level secondary device signal definition includes search string, signal search range and signal expected value.

[0011] The power system primary and secondary device operation ticket collaborative generation and closed-loop check system provided by the application comprises The ticket generation rule management module is used for defining and maintaining the primary device ticket generation rule tree and the secondary device rule chain; The secondary device state management module is used for defining and maintaining the secondary device state logic and the primary and secondary device state mapping relationship; a billing engine module for performing rule matching, step generation, state simulation and security check; a check reasoning module for performing forward reasoning and reverse tracking of secondary equipment state.

[0012] The computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the above method when executing the computer program.

[0013] The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the steps of the above method.

[0014] Advantages: Compared with the prior art, the present application has the following advantages: 1. The present application can deeply integrate primary and secondary equipment operation logic, and realize an integrated solution of operation ticket collaborative generation and real-time security check in a unified framework; 2. The present application constructs intelligent rule driving and state reasoning engine, ensures that each step generated is strictly verified by primary and secondary collaborative logic, and makes the reliable operation instruction set of the security check result, which can significantly reduce the risk of misoperation; 3. The check of the present application is based on forward reasoning and reverse tracking mechanism, which can real-time judge whether the mapping relationship of primary and secondary equipment states before and after each operation is correct, and give an alarm for inconsistent conditions, so as to complete self-verification of safety logic while generating operation ticket, form a complete closed loop of "generation-simulation-check", and significantly improve the accuracy of operation ticket and the safety of on-site operation. DETAILED DESCRIPTION

[0015] The collaborative generation and closed-loop check method of the operation ticket of the primary and secondary equipment of the power system comprises the following steps: constructing a primary equipment ticket generation rule tree, and associating operation terms, equipment states and equipment semantic relationships in the rule; based on the pre-defined rule binding relationship, dynamically triggering and executing the sequentially arranged secondary equipment rule chain associated therewith in the traversal process of the primary equipment rule tree, and generating secondary equipment operation steps; inserting the secondary equipment operation steps into the specified logical position of the corresponding primary equipment operation step sequence, completing the primary and secondary operation ticket collaborative interlacing, and forming a complete primary and secondary mixed operation ticket; generating and simulating the operation ticket steps, and checking the operation of each step according to the pre-defined primary and secondary equipment state mapping relationship.

[0016] The safety check includes forward reasoning check and reverse tracking check. The forward reasoning check: when the operation is a primary device operation, the primary device state after the operation is reasoned, and it is checked whether the corresponding secondary device state logic meets the requirement according to the mapping relationship. The reverse tracking check: when the operation is a secondary device signal operation, the affected secondary device state is tracked reversely, and it is checked whether it leads to a conflict with the current primary device state.

[0017] The forward reasoning check procedure is as follows: Reasoning the primary device target state after the operation according to the primary device operation term, the current device state and the device topology relationship; Judging whether the target state needs a specific secondary device state according to the corresponding relationship library of the primary device state and the secondary device state; If so, checking whether all related secondary device signals in the current system are consistent with the expected state according to the instantiated secondary device state logic rule; If not, outputting an alarm information.

[0018] The reverse tracking check procedure is as follows: Traversing the secondary device state definition library to obtain all state logic rules containing the current operation signal; Calculating the secondary device state based on the current secondary signal, reversely mapping the primary device and its state which should be matched, and judging the actual primary device state; If the matched primary device state is consistent with the actual primary device state, recalculating the secondary device state based on the secondary signal after the operation; Judging whether the reasoned secondary device state is consistent with the actual primary device state, and generating an alarm if not.

[0019] The emphasis of the forward and reverse check: the forward check emphasizes that after the primary device state changes, the corresponding secondary device state must maintain the preset mapping relationship; the reverse check focuses on whether the secondary device state change leads to a conflict with the primary device state. The operation ticket finally generated is not only a step sequence, but also a reliable operation instruction set with complete safety check results, which can significantly reduce the risk of misoperation.

[0020] The secondary device state is defined in a hierarchical structure: The top-level secondary device state can be combined by the lower-level secondary device sub-state or the atomic-level secondary device signal through logical relationship; the logical relationship includes "and", "or" and "not" relationship; The atomic-level secondary device signal definition includes search string, signal search range and signal expected value.

[0021] The power system primary and secondary equipment operation ticket collaborative generation and closed-loop checking system comprises A ticket rule management module is used for defining and maintaining a primary equipment ticket rule tree and a secondary equipment rule chain. A secondary equipment state management module is used for defining and maintaining secondary equipment state logic and a primary and secondary equipment state mapping relationship. A ticket generation engine module is used for performing rule matching, step generation, state simulation and safety checking. A checking reasoning module is used for performing forward reasoning and reverse tracking of the secondary equipment state.

[0022] The computer device comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, and the processor implements the steps of the above method when executing the computer program.

[0023] The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the steps of the above method. Embodiments

[0024] System construction and rule definition 1. Primary equipment rule framework construction.

[0025] Operation term library: such as "pull open", "close", "cold standby switching operation".

[0026] Device semantic relationship library: such as "bus side knife switch", "line side knife switch".

[0027] Tree rule framework: First-level rule: switch cold standby switching operation.

[0028] Second-level rule (associated with switch cold standby switching operation): line protection input (output step: yes), switch cold standby switching hot standby (output step: no), switch hot standby switching operation (output step: no).

[0029] Third-level rule (associated with switch cold standby switching hot standby): close control box aviation plug (output step: yes), bus side knife switch (output step: yes), line side knife switch (output step: yes) Third-level rule (associated with switch hot standby switching operation): close switch (output step: yes), check switch mechanical position close position (output step: yes).

[0030] 2. Secondary equipment rule and binding relationship definition: allow users to define two kinds of secondary equipment rules and bind to primary rules.

[0031] Rule Sec_Rule_1 (modeled equipment rule): Search range: Same interval; search string: Line protection put in soft press plate; rule description: Put in <secdevname / > ; bind to primary rule: Line protection put in, binding order: 1.

[0032] Rule Sec_Rule_2 (specialized rule): Rule description: On-site inspection of switch mechanical position indication in closed position; bind to primary rule: Inspection of switch mechanical position closed position; binding order: 1.

[0033] Rule Sec_Rule_3 (specialized rule): Rule description: Close DL1 switch terminal box XX aviation plug; bind to primary rule: Close control box aviation plug, binding order: 1.

[0034] 3, primary and secondary equipment state checking model construction.

[0035] Define secondary equipment signal search rule: Signal 1: Line protection put in soft press plate (search string: Line protection put in soft press plate, range: Same interval); Signal 2: Line protection device is running normally (search string: Line protection device is running normally, range: Same interval); Signal 3: Control circuit is broken (search string: Control circuit is broken, range: Same interval).

[0036] Define secondary equipment state: State: Line protection put in (logic: Or); first set of line protection put in (substate, logic: And, additional string: First set), consisting of: Signal 1, Signal 2; Second set of line protection put in (substate, logic: And, additional string: Second set); consisting of: Signal 1, Signal 2.

[0037] State: Control circuit is normal (logic: Not); Signal 3.

[0038] Define primary and secondary state mapping: Primary state: Line running <=> Secondary state: Line protection put in, control circuit is normal. Embodiment

[0039] Billing and checking process, taking "switch DL1 from cold standby to running" as an example: Input and matching: User issues "cold standby to running" instruction to switch DL1, and the system matches to the primary rule switch cold standby to running.

[0040] Traverse the rule tree once (depth first) and trigger the secondary rule chain: Enter the rule branch "Line protection put in".

[0041] Inference Sec_Rule_1: Before the inference "Put in line protection put in soft platen", the secondary device state is line protection exit, there is no corresponding primary device state, stop continuing to check; execute Sec_Rule_1: generate step "Put in line protection put in soft platen".

[0042] Continue to traverse: Enter the rule branch "Switch cold standby to hot standby".

[0043] Process the subordinate rule "Close the control box aviation plug". Execute Sec_Rule_3: generate step "Close DL1 switch terminal box XX aviation plug".

[0044] Process the subordinate rule "Close the bus blade". After the inference "Close DL1 bus blade", the primary device state is not defined, stop continuing to check. Generate primary step: "Close DL1 bus blade".

[0045] Process the subordinate rule "Close the line side blade". After the inference "Close DL1 line side blade", the primary device state is "hot standby", at this time there is no corresponding secondary device state, stop continuing to check. Generate primary step: "Close DL1 line side blade".

[0046] Continue to traverse: Enter the rule branch "Switch hot standby to running".

[0047] Process its subordinate rule "Close DL1 switch". After the inference "Close DL1 switch", the primary device state is "line running", at this time the corresponding secondary device state is "line protection put in" and "control loop normal". According to the secondary device state calculation rule, search for the secondary signal and calculate the secondary device state, which meets the inferred primary device state, and the check passes. Generate primary step: "Close DL1 switch".

[0048] Process its subordinate rule "Check the switch mechanical position close position". Execute Sec_Rule_2: generate step "On-site check the switch mechanical position indication in close position". Embodiment

[0049] Output and presentation The finally generated objectified operation ticket, in addition to the regular steps, also has the check conclusion, for example: Step 1: Put in line protection put in soft platen (remote operation) [check: pass]; Step 2: Close DL1 switch terminal box XX aviation plug (on-site operation) [check: pass]; Step 3: Close DL1 bus-pole switch (remote operation) [Check: Pass]; Step 4: Close DL1 line-pole switch (remote operation) [Check: Pass]; Step 5: Close DL1 switch (remote operation) [Check: Pass]; Step 6: Check the mechanical position indicator of the switch at the site (on-site operation) [Check: Pass].

Claims

1. A method for collaborative generation and closed-loop verification of operation tickets for primary and secondary equipment in a power system, characterized in that, The method comprises the following steps: According to the operation terms, device state and device semantic relationship, a primary device ticketing rule tree is established, a primary device operation ticket is generated, and a primary device operation step is determined; Based on the binding relationship between the predefined primary device rule and the secondary device rule, during the traversal of the primary device ticketing rule tree, the sequentially arranged secondary device rule chain associated with the primary device ticketing rule is dynamically triggered and executed to generate a secondary device operation step; The secondary device operation step is inserted into a specified logical position of the corresponding primary device operation step sequence to form a primary-secondary mixed operation ticket; During the generation and simulation execution of the primary-secondary mixed operation ticket step, according to the predefined primary-secondary device state mapping relationship, the safety check of each operation step is performed.

2. The method of claim 1, wherein the method further comprises: The safety check includes forward reasoning check and reverse tracking check.

3. The method of claim 2, wherein the method further comprises: The forward reasoning check is to forward reason the primary device target state after the operation, and check whether the corresponding secondary device state meets the secondary device expected state corresponding to the primary device target state according to the mapping relationship when the operation is a primary device operation.

4. The method of claim 2, wherein the method further comprises: The reverse tracking check is to reverse track the affected secondary device state and check whether it leads to a conflict with the current primary device state when the operation is a secondary device signal operation.

5. The method of claim 3, wherein the method further comprises: The steps of the forward reasoning check are as follows: According to the primary device operation terms, the current device state and the device topology relationship, the primary device target state after the operation is reasoned; Based on the mapping relationship library of the primary device state and the secondary device state, it is judged whether the primary device target state needs corresponding secondary device state cooperation; If the corresponding secondary device state cooperation is needed, the related secondary device signal in the current system is checked according to the instantiated secondary device state logical rule whether it is consistent with the secondary device expected state; If not, an alarm information is output.

6. The method of claim 4, wherein the method further comprises: The steps of the reverse tracking check are as follows: All state logical rules containing the current operation signal are obtained by traversing the secondary device state definition library; Based on the current secondary signal, the secondary device state is calculated, the primary device and its state that should be matched are reversely mapped, and the actual primary device state is judged; If the matched primary device state is consistent with the actual primary device state, the secondary device state is recalculated based on the operation signal; It is judged whether the reasoned secondary device state is consistent with the actual primary device state, and if not, an alarm is generated.

7. The method for collaborative generation and closed-loop verification of operation tickets for primary and secondary equipment in a power system according to claim 6, characterized in that, The secondary device state adopts a hierarchical structure, and the top-level secondary device state can be combined by the lower-level secondary device sub-state or the atomic-level secondary device signal through logical relationship; the logical relationship includes "and", "or", "not" relationship; the atomic-level secondary device signal definition includes search string, signal search range and signal expected value.

8. A collaborative generation and closed loop review system for power system primary and secondary equipment work orders, comprising: a work order generation module; a work order review module; a work order approval module; and a work order execution module. The method comprises A ticketing rule management module for defining and maintaining the primary device ticketing rule tree and the secondary device rule chain; A secondary device state management module for defining and maintaining the secondary device state logic and the primary-secondary device state mapping relationship; A ticketing engine module for performing rule matching, step generation, state simulation and safety check. The checking and reasoning module is configured to perform forward reasoning and reverse tracking of the secondary device state.

9. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The computer program, when executed by the processor, implements the steps of the method of any one of claims 1 to 7.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program, when executed by the processor, implements the steps of the method of any one of claims 1 to 7.