A substation operation ticket generation and checking method based on a multi-level device operation rule library

Abstract

This invention discloses a method for generating and verifying substation operation tickets based on a multi-level equipment operation rule library, belonging to the field of power system automation technology. The method constructs a three-layer progressive rule expert library: a basic equipment operation rule layer, an equipment set bay operation configuration layer, and a combined general typical operation layer. It uses a seven-dimensional weighted matching algorithm to select the optimal matching rule from the rule library and employs modular reasoning to automatically assemble the basic rules into a sequence of operation ticket steps according to template arrangement logic. Simultaneously, a three-level association model is established from the pressure plate to the protection device to the bay equipment. During the operation ticket verification stage, a three-level progressive logic is adopted, including primary equipment anti-misoperation interlocking, pressure plate status anti-misoperation interlocking, and comprehensive anti-misoperation interlocking, to perform pre-simulated dynamic verification of each step. After a change in the primary equipment state, it automatically triggers the linkage insertion and verification of secondary pressure plate operations. This invention improves the reusability of operation rules and the flexibility of ticket generation, achieving collaborative anti-misoperation of primary and secondary equipment operations.

Description

Technical Field

[0001] This invention relates to the field of power system automation technology, and in particular to a method for generating and verifying substation operation tickets based on a multi-level equipment operation rule base. Background Technology

[0002] Substation switching operations are a crucial link in ensuring the safe operation of the power grid. Operation tickets, as the core document guiding on-site operators in switching equipment states, directly impact the safety of power grid operation due to their generation quality and verification accuracy. With the continuous expansion of the power grid and the large-scale integration of renewable energy, substation operations are becoming increasingly complex, placing higher demands on the intelligent generation and error prevention verification of operation tickets.

[0003] Existing operation ticket generation systems typically employ a fixed template matching method, where a complete operation ticket template is created for each specific operation task. This approach has a fixed granularity in rule organization and lacks hierarchical abstraction from the smallest equipment unit to combined operations. When conditions such as wiring method, equipment model, or voltage level change, existing templates struggle to adapt adaptively, requiring manual re-creation. This results in a large number of templates and high maintenance costs. Furthermore, there is a lack of logical reusability between templates; basic operation steps for the same equipment are repeatedly defined in different operation tasks. Once the operation specifications are updated, all templates involving that equipment must be modified one by one, easily leading to omissions and inconsistencies. In addition, existing systems lack an intelligent matching mechanism based on multi-dimensional conditions, failing to perform rule filtering and optimal matching based on multiple dimensions such as field equipment type, principle, model, wiring method, bay type, voltage level, and topology characteristics. This results in insufficient accuracy and applicability of the generated operation tickets. Meanwhile, in the existing error prevention system, the operation verification of primary equipment and the operation verification of secondary protection pressure plate are often independent of each other. After the status of primary equipment changes, the required status of secondary protection pressure plate is not automatically verified. The rules for putting on and taking off protection pressure plate lack correlation modeling with the operating status of primary equipment and the status of protection device, resulting in a structural blind spot in error prevention verification where primary equipment has been operated but secondary equipment has not followed up. Summary of the Invention

[0004] The purpose of this invention is to provide a method for generating and verifying substation operation tickets based on a multi-level equipment operation rule library, in order to solve the problems of insufficient flexibility and accuracy of ticket generation caused by the single rule granularity, low reuse rate, and lack of multi-dimensional intelligent matching in the existing operation ticket generation system, as well as the problems of disconnect between primary equipment operation and secondary protection pressure plate operation and structural blind spots in anti-misoperation verification.

[0005] To achieve the above objectives, this invention provides a method for generating and verifying substation operation tickets based on a multi-level equipment operation rule library, comprising: constructing a multi-level equipment operation rule expert library, wherein the multi-level equipment operation rule expert library adopts a three-layer progressive structure of a basic equipment operation rule layer, an equipment set bay operation configuration layer, and a combined general typical operation layer; wherein, the basic equipment operation rule layer defines basic operation rules for each type of equipment, including equipment type, equipment principle, equipment model, applicable conditions, operation step sequence, preconditions, and postconditions, based on the smallest equipment unit; the equipment set bay operation configuration layer groups the equipment within a bay according to bay type, wiring method, and topology characteristics, based on substation diagram data and equipment ledger data. A set of devices is formed, and the devices in the set reference the corresponding rules in the basic operation rule layer. The combined general typical operation layer uses the set of devices as the operation unit and defines a step arrangement sequence for each typical operation type. The step arrangement sequence includes a target device set reference, a basic operation rule reference, an operation direction, a prerequisite step dependency, and a conditional branch logic. The system receives and parses scheduling instructions, extracts target substation, target equipment, operation type, and target status information, and matches it with equipment modeling data to generate structured equipment operation tasks. Based on the structured equipment operation tasks, the system extracts field conditions from seven dimensions: equipment type, equipment principle, equipment model, wiring method, bay type, voltage level, and topology features. The system compares the on-site condition values ​​with the corresponding dimensional condition values ​​of the template rules in the combined general typical operation layer dimension by dimension and calculates the weighted matching degree. The template rule with the highest matching degree and not lower than a preset threshold is selected as the optimal matching rule. Based on the step arrangement sequence of the optimal matching rule, the corresponding operation step sequences are sequentially read from the equipment basic operation rule layer. The abstract equipment identifier is replaced with the actual equipment name, and the conditional branch logic is processed according to the current operating mode to assemble and generate the operation ticket step sequence. The operation ticket step sequence undergoes primary and secondary collaborative dynamic error prevention verification. This error prevention verification includes: before executing each step, superimposing the operation effect of the current step onto the equipment simulation state for pre-rehearsal, and based on the expected state obtained from the pre-rehearsal... The system calculates the anti-misoperation interlocking conditions for primary equipment. For steps involving pressure plate operation, it obtains the associated status information through the three-level association chain of pressure plate, protection device, and bay equipment, and calculates the pressure plate status anti-misoperation interlocking conditions. The primary equipment anti-misoperation interlocking conditions and the pressure plate status anti-misoperation interlocking conditions are logically merged to form a comprehensive anti-misoperation interlocking signal. When the comprehensive anti-misoperation interlocking signal is true, the current step is prohibited from execution. When it is false, the expected state is confirmed as the formal simulation state and used as the verification input for the next step. After the simulation state of the primary equipment operation step is updated, a reverse query is performed along the association chain from the bay equipment to the protection device to the pressure plate. When a pressure plate that needs to be linked is found, the insertion position of the linked step is determined according to the nature of the operation, and anti-misoperation verification is performed on the newly inserted step.

[0006] As a preferred technical solution of the present invention, the weighted matching degree is calculated as follows: for each dimension, when the rule condition value is null or equal to the field condition value, the matching degree of that dimension is 1; otherwise, it is 0. The seven dimensions are divided into high-weighted recombination, medium-weighted recombination, and low-weighted recombination. The high-weighted recombination includes equipment type, equipment principle, and equipment model, with a weight value of 3. The medium-weighted recombination includes wiring method and bay type, with a weight value of 2. The low-weighted recombination includes voltage level and topology characteristics, with a weight value of 1. The total matching degree is the weighted sum of the matching degree of each dimension and its corresponding weight. The normalized matching degree is the total matching degree divided by the sum of the weights of all dimensions.

[0007] As a preferred technical solution of the present invention, the data structure of each operation command in the basic operation rule layer of the equipment includes a step number, an operation object identifier, an operation action type, an operation command text, a confirmation requirement, and safety precautions. The operation action types include closing, opening, engaging, disengaging, connecting, disconnecting, and checking and confirming.

[0008] As a preferred technical solution of the present invention, the method further includes constructing a protection pressure plate operation rule library, specifically: establishing a protection device model and a pressure plate model, associating the pressure plate model with the protection device model, and then associating the protection device model with the bay equipment model to form a three-level association chain from pressure plate to protection device to bay equipment; configuring the pressure plate target state when protection is engaged and the pressure plate target state when protection is disengaged for each pressure plate.

[0009] As a preferred technical solution of the present invention, the calculation method of the primary equipment anti-misoperation interlocking condition is as follows: obtain the expected energized state and expected grounding state of each device in the primary equipment set after the current step pre-rehearsal; if any device simultaneously satisfies the expected grounding state as connected and the expected energized state as energized, then the primary equipment anti-misoperation interlocking condition is true.

[0010] As a preferred embodiment of the present invention, the pressure plate state anti-misoperation interlocking conditions include pressure plate engagement interlocking conditions and pressure plate disengagement interlocking conditions. The pressure plate engagement interlocking condition is: when the associated equipment is under maintenance or the protection device is in an abnormal state, the pressure plate is prohibited from being engaged. The pressure plate disengagement interlocking condition is: when the associated equipment is in operation or the protection device is in an abnormal state, the pressure plate is prohibited from being disengaged.

[0011] As a preferred embodiment of the present invention, the calculation method of the integrated anti-misoperation interlocking signal is as follows: when the operation object of the current step is a primary device, the integrated anti-misoperation interlocking signal is equal to the primary device anti-misoperation interlocking condition; when the operation object of the current step is a protective pressure plate and the operation direction is "engagement", the integrated anti-misoperation interlocking signal is equal to the logical OR of the primary device anti-misoperation interlocking condition and the pressure plate engagement interlocking condition; when the operation object of the current step is a protective pressure plate and the operation direction is "exit", the integrated anti-misoperation interlocking signal is equal to the logical OR of the primary device anti-misoperation interlocking condition and the pressure plate exit interlocking condition.

[0012] As a preferred technical solution of the present invention, the step of determining the insertion position of the linkage step according to the nature of the operation is as follows: for power supply or connection type operations, the secondary pressure plate connection step generated by the linkage is inserted before the current primary equipment operation step; for power outage or exit type operations, the secondary pressure plate exit step generated by the linkage is inserted after the current primary equipment operation step; the reclosing pressure plate is after the primary equipment operation step during power supply operation and before the primary equipment operation step during power outage operation.

[0013] As a preferred technical solution of the present invention, each step in the operation ticket step sequence is marked with verification status information. The values ​​of the verification status information include pass, lock, and linkage, and the source rule number corresponding to the step is recorded.

[0014] As a preferred embodiment of the present invention, the method further includes an execution feedback and status update step: after the operation ticket is confirmed to enter the execution stage, an execution feedback signal is received after each step of the operation is actually executed, the equipment simulation status is updated to the actual status and used as the input for the error prevention verification of subsequent steps; if the equipment status after actual execution does not match the expected subsequent status, an exception handling process is triggered, and the comprehensive error prevention interlocking conditions are recalculated for subsequent steps; after all steps of the operation ticket are executed, the entire operation process is recorded and written into the operation log and the historical operation ticket database.

[0015] This invention constructs a three-layer progressive rule system: a basic equipment operation rule layer, a device set interval operation configuration layer, and a combined general typical operation layer. This refines the definition granularity of operation rules to the smallest equipment unit, allowing basic rules to be reused across different interval configurations and typical operation tasks. When new equipment is added or operation specifications are updated, only the basic rules at the corresponding level need to be modified; the upper-level combined rules automatically inherit the changes, reducing rule maintenance costs. Simultaneously, a seven-dimensional weighted matching algorithm filters rules from multiple dimensions, including equipment type, equipment principle, equipment model, wiring method, interval type, voltage level, and topology characteristics, improving the adaptability and matching accuracy of operation ticket generation to different field conditions. Furthermore, by establishing a three-level association model from the pressure plate to the protection device to the interval equipment, combined with a three-level progressive anti-misoperation interlocking logic and a primary and secondary collaborative linkage mechanism, the secondary pressure plate operation is automatically triggered for linkage verification after a change in the state of the primary equipment operation step. This ensures consistency between the primary equipment operation and the secondary protection pressure plate operation throughout the entire operation ticket generation and verification process, reducing blind spots in anti-misoperation caused by disconnection between primary and secondary operations. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the overall process of the method according to an embodiment of the present invention. Detailed Implementation

[0017] The technical solution of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that the following embodiments are only used to further explain and illustrate the present invention and do not constitute a limitation on the scope of protection of the present invention. Equivalent substitutions or conventional modifications made by those skilled in the art based on the spirit and principles of the present invention should all be included within the scope of protection of the present invention.

[0018] like Figure 1 As shown, this invention provides a method for generating and verifying substation operation tickets based on a multi-level equipment operation rule base. The overall implementation architecture of this method is divided into four functional layers: a data acquisition layer, a rule modeling layer, a reasoning generation layer, and a mis-verification layer. The data acquisition layer is at the bottom and is responsible for acquiring and aggregating various types of raw data. The rule modeling layer is built on top of the data acquisition layer and is responsible for constructing a multi-level rule expert base and a protection pressure plate operation rule base, while also undertaking the function of substation equipment modeling management. The reasoning generation layer relies on the rule data and equipment models output by the rule modeling layer to complete the automated reasoning from scheduling instructions to the operation ticket step sequence. The mis-verification layer performs step-by-step safety verification on the operation ticket after it is generated and realizes dynamic linkage between primary and secondary equipment operations. The above four layers are connected through a data bus to ensure the consistency of equipment attributes, topology relationships, and real-time operating status across each layer.

[0019] In the data acquisition layer, the system simultaneously acquires multiple data sources from the substation automation system, dispatch automation system, and protection information management system. Specifically, the substation primary wiring diagram provides equipment node information, topological connection relationships, and bay division information, serving as the foundational topological input for subsequent equipment modeling and rule matching. Real-time equipment status data is accessed via data streams, covering the open / closed status of each switch, the open / closed status of each disconnector, the connection / removal status of each ground line, and information such as bus voltage and line energization status. Real-time protection switch status data is also accessed via data streams, including the current engaged / disengaged status of each switch and the operating status of the corresponding protection device. Equipment ledgers are provided in static data form, recording the inherent attributes of each piece of equipment, such as model, operating principle, and rated parameters. Typical operation ticket databases and historical operation ticket databases store a large number of existing operation ticket instances, serving as data loops for rule extraction, verification reference, and subsequent rule optimization. Substation operation specification text data originates from the operation procedures issued by dispatching agencies at all levels, providing a basis for the standardized expression of operation commands. After aggregation, all of the above data types are uniformly transmitted to the rule modeling layer as the data foundation for rule construction and inference generation.

[0020] The core work of the rule modeling layer includes three parallel components: the construction of a multi-level expert library for equipment operation rules, the construction of a protection pressure plate operation rule library, and substation equipment modeling management. These three components have a close data dependency—equipment modeling management provides the rule expert library and the pressure plate operation rule library with unified equipment attributes, bay topology, and primary and secondary correlation data, ensuring that operation ticket generation and error prevention verification are based on the same equipment model and the same operating state.

[0021] The multi-level equipment operation rule expert database is constructed using a three-layer progressive structure: "equipment basic operation rule layer - equipment set interval operation configuration layer - combined general typical operation layer".

[0022] To construct the basic operation rules layer for equipment, the typical and historical operation tickets of the substation are first analyzed step by step. Each step of the operation ticket is categorized according to equipment type, and the granularity of the operation is refined to the smallest equipment unit. That is, a single circuit breaker, a single isolating switch, a single main transformer, a single grounding switch, etc., are used as basic objects to extract the standard operation step command sequence for each type of equipment under different operating modes. Based on this, each type of smallest unit equipment is standardized and defined to form the basic operation rules for equipment. Each rule contains the following attribute fields: Rule Number, used to uniquely identify the rule across all layers of the system; Equipment Type field, with values ​​such as circuit breaker, isolating switch, grounding switch, main transformer, etc.; Equipment Principle field, recording the equipment operation method, such as spring operation, electromagnetic operation, hydraulic operation, etc.; Equipment Model field, recording the specific equipment model identifier; Applicable Condition field, describing the current state of the equipment required to execute the rule, such as "execute the opening operation when the current state of the equipment is closed"; Operation Step Sequence field, a list of operation commands strictly arranged in chronological order; Precondition field, defining the set of equipment state conditions that must be met before executing the operation; Post-State field, describing the expected state that the equipment should reach after the operation is completed.

[0023] Each operation command in the sequence of operation steps has the following data structure: step number, operation object identifier, operation action type, operation command text, confirmation requirements, and safety precautions. The operation action types include closing, opening, engaging, disengaging, connecting, disconnecting, and inspection / confirmation. In an optional implementation, an "operation time limit" field can be added to the operation command to record the permitted operation time for that step, used to assist in judging the rationality of the operation sequence during the verification phase. Through this minimally granular rule definition method, the basic operation rules for the same equipment can be reused by different interval configurations and different typical operation tasks. When updating the rules, only the rule definition of the corresponding equipment in the basic layer needs to be modified. The interval configurations and typical templates referencing the rule in the upper layer automatically inherit the changed content, thus avoiding the maintenance difficulty of modifying all operation ticket templates involving the equipment one by one in the traditional method.

[0024] For the construction of the equipment set bay operation configuration layer, the first step is to perform topology parsing based on the substation diagram data acquired by the data acquisition layer to identify the boundaries of each bay and the list of equipment it contains. Then, the equipment ledger data is read to obtain the model, principle, rated parameters, and other attribute information of each piece of equipment, and these are matched and associated with the corresponding equipment in the diagram data. Based on this, the equipment within each bay is grouped and associated according to three aspects: bay type, wiring method, and topology characteristics, forming an equipment set. Bay types include line bays, main transformer bays, bus bays, capacitor bays, etc.; wiring methods include single busbar, double busbar, one and a half circuit breakers, etc.; and topology characteristics describe the positional relationship of the equipment in the primary wiring topology, such as the connection position between the equipment and the busbar, and the series and parallel relationships between equipment.

[0025] The data structure of a device set is defined as follows: device set number, bay identifier, bay type, wiring method, voltage level, device member list, and topology feature description. Each entry in the device member list contains a device identifier, device type, and a reference to a basic operating rule. This reference points to the corresponding rule number in the basic operating rule layer, thus establishing a link from the device set level to the basic rule level. It is worth noting that the same physical device may be included in different device set definitions under different operating modes or topology configurations. The system uses the operating mode identifier to distinguish the reference context of the same device in different device sets, thereby adapting to scenarios such as wiring method switching.

[0026] The construction of the combined general typical operation layer is supported by basic equipment operation rules and equipment set interval operation configurations. A general typical operation task template is created for each typical operation type. Typical operation types cover various major operation scenarios in the daily operation and maintenance of substations, such as line outages, line energization, main transformer outages, main transformer energization, bus switching, switching to maintenance, and switching to standby. For each operation type, the template defines the orchestration logic for the involved equipment operation steps. The orchestration logic uses equipment sets as operation units, specifying the operation sequence, operation direction, and sequential constraints between equipment sets.

[0027] The data structure of a general typical operation task template includes: task template number, operation type, applicable voltage level range, applicable wiring method range, and step arrangement sequence. Each entry in the step arrangement sequence includes a step number, target device set or device reference, reference to the basic operation rule to be invoked, operation direction, dependencies of preceding steps, and conditional branching logic. The conditional branching logic is used to handle the differences in operation steps under different operating modes. For example, when the bus operation mode is dual-bus operation, a specific step is executed, while when the operation mode is single-bus operation, the step is skipped. In an optional implementation, the conditional branching logic can also support nested conditions, that is, setting sub-conditional branches within a conditional branch to adapt to more complex combinations of operating modes. Through the above three-layer progressive rule system, the organization of operation rules is similar to a building block structure—basic operation rules are basic building blocks, device set configurations combine building blocks into functional units, and general typical templates arrange functional units into a complete operation sequence according to assembly drawings.

[0028] In constructing the protection switch operation rule base, the system completes the correlation modeling based on the substation protection device ledger and switch ledger data. The data structure of the protection device model includes fields such as protection device number, protection model, protection type, bay identifier, and associated primary equipment identifier. The protection type value covers line protection, main transformer protection, bus protection, etc. The data structure of the switch model includes fields such as switch number, switch name, switch type, and associated protection device number. The switch type is divided into outlet switch, function switch, signal switch, etc. By associating the switch model with the protection device model, and then associating the protection device model with the bay equipment model, a three-level correlation chain of "switching switch - protection device - bay equipment" is established. This correlation chain allows the system to trace the state information of the other two levels of objects along the correlation path from the state change of any level of object, providing a data channel for subsequent collaborative error prevention verification.

[0029] After completing the correlation modeling, the system configures operation rules for each pressure plate under each protection device. The data structure of each pressure plate operation rule includes: rule number, pressure plate number, protection device number, target pressure plate state when protection is engaged, target pressure plate state when protection is deactivated, and special condition description. The target pressure plate state when protection is engaged refers to the state (engaged or deactivated) that the pressure plate should be in when the protection device is engaged; the same applies to the target pressure plate state when protection is deactivated. The special condition description field is used to record exception rules under specific operating modes, such as situations where a certain functional pressure plate must always remain in the deactivated state under a specific line operating mode. The system collects the current state of each pressure plate in real time, compares it with the target state defined in the pressure plate operation rule, and performs multi-dimensional closed-loop verification in conjunction with the real-time operating mode information of the primary power grid. The verification dimensions include the consistency between the current state of the pressure plate and the target state of the rule, the consistency between the state of the protection device and the operating state of the associated primary equipment, and the logical consistency of the state combinations among multiple pressure plates under the same protection device. The verification results are presented in real-time alarm mode, and pressure plates with abnormal states are marked with corresponding abnormal prompt information.

[0030] After completing the construction of the rule modeling layer, the system enters the workflow of the inference generation layer. When maintenance personnel receive a dispatch instruction, they input the instruction text into the system, and the inference generation layer parses and processes the instruction text. During the parsing process, the system uses natural language processing and keyword extraction technologies to extract key information from the instruction text, such as the target substation name, target equipment name or identifier, operation type, and target status. Subsequently, the extracted key information is correlated and matched with the graphical data in equipment modeling management to locate the specific bay and equipment object, forming a structured equipment operation task. The data structure of the structured equipment operation task includes task number, substation identifier, bay identifier, target equipment identifier, operation type, target status, and current operating mode.

[0031] After obtaining the structured equipment operation task, the system executes a seven-dimensional weighted matching algorithm for rule filtering. The system extracts the field condition values ​​for seven matching dimensions from the task information and equipment modeling data, denoted as follows: (Equipment type) (Equipment Principle) (Equipment model) (Wiring method) (Interval type) (Voltage level) (Topological features). Simultaneously, the corresponding seven-dimensional condition values ​​are read from each template rule of the combined general typical operation layer. to For each dimension Calculate the single-dimensional matching degree When the rule conditions Null value (indicating that the dimension is not restricted) or and on-site conditions When they are equal, ;otherwise .

[0032] After calculating the matching degree for each dimension, three sets of differentiated weights are set according to the importance of the dimensions: the high-weighted recombination includes three dimensions: equipment type, equipment principle, and equipment model, and its weight value is... The weighted reorganization includes two dimensions: connection method and interval type, and its weight value... The low-weighted reassembly includes two dimensions: voltage level and topological features, and its weight values ​​are... Overall matching degree The calculation formula is: ; Normalized matching degree The calculation formula is: ; The denominator is the sum of all dimension weights, which is calculated by substituting the weight values. The system iterates through all template rules in the general typical operation layer, calculates the normalized matching degree for each rule, and selects the rule with the highest normalized matching degree as the optimal matching rule, while requiring that the highest matching degree is not lower than a preset threshold. In a specific implementation scenario, The threshold can be set to 0.8. Those skilled in the art can adjust this threshold according to the actual substation equipment coverage and the completeness of the rule base. If multiple rules have the same matching degree, they will be sorted again according to the priority field defined by the rule itself and the best one will be selected. If the matching degree of all rules is lower than the threshold, the system will issue an alarm prompt, requiring manual intervention to confirm or expand the rule base.

[0033] After obtaining the optimal matching general typical operation template, the system enters the modular reasoning and assembly stage. The system processes each step sequentially according to the logical sequence of steps in the template: for each step, based on its specified target device set or device reference and the reference to the invoked basic operation rule, the system reads the corresponding operation step sequence from the device's basic operation rule layer. During the reading process, the system replaces the abstract device identifier in the operation command with the specific name and number of the actual device. During replacement, the system maps the device type placeholder in the operation command text to the full name of the actual device based on the device attribute information recorded in the device modeling management; for example, it replaces "Break [Circuit Breaker]" in the basic operation rule with "Break 220kV Line A 501 Switch". Simultaneously, the system processes the conditional branch logic in the template based on the current power grid operation mode information, selecting the operation path matching the current operation mode at the location where a branch exists, and skipping inapplicable steps.

[0034] After all steps are completed, the system numbers and arranges the operation commands for each step according to the global time sequence, generating a complete operation ticket step sequence. This sequence is an ordered list, and each entry contains a global step number, operation command text, operation object identifier, operation action type, confirmation requirements, safety precautions, and source rule number. The source rule number records the number of the basic operation rule of the device corresponding to this step, providing a basis for subsequent rule traceability and maintenance.

[0035] After the operation ticket step sequence is generated, the system enters the error prevention and verification layer to perform primary and secondary collaborative dynamic error prevention and verification. The error prevention and verification adopts a three-level progressive interlocking logic.

[0036] The first level is the primary equipment anti-misoperation interlock verification. During the execution of the operation ticket, before each step of the operation, the system does not only check the existing equipment status before the operation, but first performs a pre-calculation of the equipment simulation status based on the operation content of the current step to obtain the expected status of each piece of equipment after the step is executed, and then makes an interlock determination based on the expected status. Specifically, based on the current simulation status, the system overlays the operation effect of the current step to be executed onto the equipment status model to generate a primary equipment set. Each device The expected energized state and expected grounding state after performing this step. Primary equipment anti-misoperation interlocking conditions. The judgment logic is: if the set If any device will be simultaneously grounded and energized after the current step is executed, then... The formal expression is: ; Taking the typical dangerous operation of connecting a grounding switch while the line is energized as an example, before the operation, the line is in an energized state and the grounding wire is disconnected. At this time, the system performs a pre-operation simulation of the current step "connecting the grounding switch" and calculates that after this step is executed, the expected state of the grounding wire will change to connected while the energized state will remain energized. Both conditions are met simultaneously. If the calculation result is True, the system will intercept it and generate a security alert before this step is actually executed. When this occurs, the system prohibits the execution of the current operation step. In an optional implementation, the primary equipment anti-misoperation interlocking verification can also be extended to cover the judgment of other dangerous operation scenarios, such as opening and closing disconnect switches under load, asynchronous parallel operation, etc. Its judgment logic is similar to the Boolean logic structure of the above-mentioned expected state assessment, both adopting the method of pre-simulation followed by judgment, only requiring the addition of corresponding state criteria.

[0037] The second level is the check for the pressure plate status to prevent misoperation and interlocking. For steps involving pressure plate operation, the system obtains relevant status information through a three-level linkage chain of "pressure plate - protection device - interval equipment". Assume a protective pressure plate... The corresponding associated devices are The protection device status is Pressure plate locking conditions Defined as: when associated devices Under maintenance or under protection When the system is in an abnormal state, the pressure plate must not be engaged. Its formal expression is: ; Pressure plate release locking condition Defined as: when associated devices In operation or under protection When in an abnormal state, it is forbidden to remove the pressure plate. Its formal expression is: ; The two interlocking conditions mentioned above are invoked in the scenarios of plate engagement and plate disengagement, respectively, to ensure that the plate engagement direction is coordinated with the operating status of the associated equipment and the working status of the protection device.

[0038] The third level is the comprehensive anti-misoperation interlocking logic. Based on the type of operation object in the current operation step, the system selects the corresponding interlocking decision branch to generate a comprehensive anti-misoperation interlocking signal. When the current step operates on a primary device, this step does not involve the operation of the protection pressure plate; the system only calculates the anti-misoperation interlocking conditions for the primary device. When the current operation involves a protective pressure plate, the system calculates the corresponding anti-misoperation interlocking conditions based on the pressure plate's operation direction, and makes a comprehensive judgment by combining these conditions with the primary equipment's anti-misoperation interlocking conditions. (Entry into the operational scenario) or (Exiting the operation scenario). The above branch decision ensures that when the system processes different types of operation steps, it only calculates the locking condition for objects with valid associations, avoiding invalid calculations due to mismatch between the operation object type and the locking condition.

[0039] when When this happens, the system prohibits the execution of the current operation step, abandons the expected state obtained from the previous rehearsal, and maintains the simulation state unchanged. Each step in the operation ticket must be checked by the comprehensive anti-misoperation interlocking logic before execution. After the check is passed, the system confirms the expected state obtained from the previous rehearsal as the formal simulation state, and uses the updated simulation state as the input for the next operation rehearsal and check, thereby realizing a progressively dynamic anti-misoperation check. This mechanism ensures the continuity of equipment state transmission between adjacent operation steps and avoids potential safety hazards in intermediate processes that may be missed due to a one-time check using a static initial state.

[0040] During the step-by-step verification process, the system simultaneously executes a primary and secondary collaborative linkage mechanism. For each primary equipment operation step, the system automatically performs a reverse query along the "interval equipment—protection device—pressure plate" association chain to determine whether the change in the state of the primary equipment involved in the step requires a change in the engaged or disengaged state of its associated protection device, and then determines whether a linkage adjustment of the target state of the corresponding pressure plate is needed. If the query result indicates that there is a pressure plate that requires linkage operation, the system dynamically determines the insertion position of the linkage step in the operation ticket sequence based on the action attributes of the pressure plate and the operation nature of the primary equipment. For energizing or connecting operations, the secondary protection switch activation step generated by the linkage is inserted before the current primary equipment operation step to ensure that the associated protection is already in the activated state when the primary equipment is closed and energized, avoiding the dangerous window of unprotected energized operation of the line. For de-energizing or de-energizing operations, the secondary protection switch de-energizing step generated by the linkage is inserted after the current primary equipment operation step. During energizing operations, the reclosing switch is inserted after the primary equipment operation step; during de-energizing operations, it is inserted before the primary equipment operation step, ensuring that the protection is always effectively covered during the primary equipment de-energizing process. The protection switch is only deactivated after the de-energizing operation is completed and the equipment is confirmed to be in a non-operating state. The above timing direction judgment follows the safety principle of the power system: "Protection must be activated before energizing, and protection can only be deactivated after de-energizing." The system performs a second-level switch status anti-misoperation interlocking check and a third-level comprehensive anti-misoperation interlocking check on the newly inserted secondary protection switch operation step. After the check is passed, it is included in the formal arrangement of the operation ticket step sequence. This linkage mechanism ensures that the primary equipment operation and the secondary protection pressure plate operation in the operation ticket sequence are always consistent in both timing and status, eliminating the blind spot caused by the failure of the secondary operation to follow up after the completion of the first operation in the traditional method.

[0041] After all steps have been verified and processed, the system outputs a final operation ticket that has undergone error prevention verification and primary / secondary linkage correction. Each step in the final operation ticket is marked with verification status information, with values ​​of "passed," "locked," or "linked," and the corresponding source rule number is recorded for maintenance personnel to perform final confirmation before execution.

[0042] After the operation ticket is confirmed by the maintenance personnel, it enters the actual execution phase. During the execution phase, after each step of the operation is actually performed, the system receives an execution feedback signal, updates the simulation state of the corresponding equipment to the actual state, and uses the actual state as the input for error prevention verification of subsequent steps. If the equipment state after actual execution does not match the expected subsequent state, the system triggers an exception handling process, recalculates the comprehensive error prevention interlocking conditions for subsequent steps, and adjusts the execution sequence of subsequent steps or inserts additional safety confirmation steps if necessary. After all steps of the operation ticket are executed, the system writes the entire process record of this operation to the operation log and the historical operation ticket database, forming a data closed loop from operation execution results to rule base optimization, providing feedback data for the continuous improvement of the rule base and the improvement of the accuracy of subsequent operation ticket generation.

[0043] In the above implementation, the construction of a three-layer progressive expert database for equipment operation rules, in conjunction with a seven-dimensional weighted matching algorithm, solves the problems of single rule granularity, low rule reuse rate, and insufficient flexibility in ticket generation in traditional operation ticket generation methods. The three-level association model and the three-level progressive anti-misoperation interlocking logic work together to address the disconnect between primary equipment operation and secondary protection plate operation, and the structural blind spots in anti-misoperation verification. These two aspects, through a unified equipment modeling and management data base, achieve data connectivity and functional synergy, together forming a complete closed-loop technical system from intelligent operation ticket generation to dynamic anti-misoperation verification.

[0044] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for generating and verifying substation operation tickets based on a multi-level equipment operation rule base, characterized in that, include: A multi-level equipment operation rule expert database is constructed, employing a three-tiered progressive structure: a basic equipment operation rule layer, an equipment set interval operation configuration layer, and a combined general typical operation layer. The basic equipment operation rule layer defines basic operation rules for each type of equipment, based on the smallest equipment unit, including equipment type, principle, model, applicable conditions, operation step sequence, preconditions, and postconditions. The equipment set interval operation configuration layer, based on substation diagram data and equipment ledger data, groups and associates equipment within an interval according to interval type, wiring method, and topology characteristics to form equipment sets. Equipment members within these sets reference the corresponding rules in the basic equipment operation rule layer. The combined general typical operation layer uses equipment sets as operation units, defining a step arrangement sequence for each typical operation type. This step arrangement sequence includes a target equipment set reference, a basic operation rule reference, operation direction, prerequisite step dependencies, and conditional branch logic. Receive and parse dispatch instructions, extract target substation, target equipment, operation type and target status information, associate and match them with equipment modeling data, and generate structured equipment operation tasks; Based on the structured equipment operation tasks, field condition values ​​are extracted from seven dimensions: equipment type, equipment principle, equipment model, wiring method, bay type, voltage level, and topology features. The field condition values ​​are compared dimension by dimension with the corresponding dimension condition values ​​of the template rules in the combined general typical operation layer, and the weighted matching degree is calculated. The template rule with the highest matching degree and not lower than the preset threshold is selected as the optimal matching rule. According to the step arrangement sequence of the optimal matching rule, the corresponding operation step sequence is read from the device basic operation rule layer in sequence, the abstract device identifier is replaced with the actual device name, and the condition branch logic is processed according to the current operation mode to assemble and generate the operation ticket step sequence. The operation ticket step sequence is subjected to primary and secondary collaborative dynamic anti-misoperation verification. The anti-misoperation verification includes: before each step is executed, the operation effect of the current step is superimposed on the equipment simulation state for pre-playing, and the primary equipment anti-misoperation interlocking condition is calculated based on the expected state obtained from the pre-playing; for steps involving pressure plate operation, the associated state information is obtained through the three-level association chain of pressure plate, protection device and bay equipment, and the pressure plate state anti-misoperation interlocking condition is calculated; the primary equipment anti-misoperation interlocking condition and the pressure plate state anti-misoperation interlocking condition are logically merged to form a comprehensive anti-misoperation interlocking signal. When the comprehensive anti-misoperation interlocking signal is true, the current step is prohibited from execution. When it is false, the expected state is confirmed as the formal simulation state and used as the verification input for the next step; after the simulation state of the primary equipment operation step is updated, a reverse query is performed along the association chain from the bay equipment to the protection device to the pressure plate. When a pressure plate that needs to be linked is found, the insertion position of the linked step is determined according to the operation nature and the anti-misoperation verification is performed on the newly inserted step.

2. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, The weighted matching degree is calculated as follows: for each dimension, when the rule condition value is null or equal to the field condition value, the matching degree of that dimension is 1; otherwise, it is 0. The seven dimensions are divided into high-weighted recombination, medium-weighted recombination, and low-weighted recombination. The high-weighted recombination includes equipment type, equipment principle, and equipment model, with a weight of 3. The medium-weighted recombination includes wiring method and bay type, with a weight of 2. The low-weighted recombination includes voltage level and topology characteristics, with a weight of 1. The total matching degree is the weighted sum of the matching degree of each dimension and its corresponding weight, and the normalized matching degree is the total matching degree divided by the sum of the weights of all dimensions.

3. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, The data structure of each operation command in the basic operation rule layer of the equipment includes step number, operation object identifier, operation action type, operation command text, confirmation requirements and safety precautions. The operation action types include closing, opening, engaging, disengaging, connecting, disconnecting and checking confirmation.

4. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, The method also includes constructing a protection pressure plate operation rule library, specifically: establishing a protection device model and a pressure plate model, associating the pressure plate model with the protection device model, and then associating the protection device model with the bay equipment model to form a three-level association chain from pressure plate to protection device to bay equipment; configuring the pressure plate target state when protection is engaged and the pressure plate target state when protection is disengaged for each pressure plate.

5. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, The calculation method for the primary equipment anti-misoperation interlocking condition is as follows: obtain the expected energized state and expected grounding state of each device in the primary equipment set after the current step pre-simulation. If any device simultaneously satisfies the expected grounding state as connected and the expected energized state as energized, then the primary equipment anti-misoperation interlocking condition is true.

6. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, The pressure plate status anti-misoperation interlocking conditions include pressure plate engagement interlocking conditions and pressure plate disengagement interlocking conditions. The pressure plate engagement interlocking condition is: when the associated equipment is under maintenance or the protection device is in an abnormal state, the pressure plate is prohibited from being engaged. The pressure plate disengagement interlocking condition is: when the associated equipment is in operation or the protection device is in an abnormal state, the pressure plate is prohibited from being disengaged.

7. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, The calculation method for the integrated anti-misoperation interlocking signal is as follows: when the operation object of the current step is a primary device, the integrated anti-misoperation interlocking signal is equal to the primary device anti-misoperation interlocking condition; when the operation object of the current step is a protective pressure plate and the operation direction is "engagement", the integrated anti-misoperation interlocking signal is equal to the logical OR of the primary device anti-misoperation interlocking condition and the pressure plate engagement interlocking condition; when the operation object of the current step is a protective pressure plate and the operation direction is "exit", the integrated anti-misoperation interlocking signal is equal to the logical OR of the primary device anti-misoperation interlocking condition and the pressure plate exit interlocking condition.

8. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, The specific method for determining the insertion position of the linkage step based on the nature of the operation is as follows: for power-on or connection-type operations, the secondary pressure plate connection step generated by the linkage is inserted before the current primary equipment operation step; for power-off or exit-type operations, the secondary pressure plate exit step generated by the linkage is inserted after the current primary equipment operation step; the reclosing pressure plate is inserted after the primary equipment operation step during power-on operations and before the primary equipment operation step during power-off operations.

9. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, Each step in the operation ticket sequence is marked with verification status information. The values ​​of the verification status information include pass, lock, and linkage. At the same time, the source rule number corresponding to the step is recorded.

10. The method for generating and verifying substation operation tickets according to claim 1, characterized in that, The method further includes execution feedback and status update steps: after the operation ticket is confirmed to enter the execution stage, an execution feedback signal is received after each step of the operation is actually executed, the equipment simulation status is updated to the actual status and used as the input for the error prevention verification of subsequent steps; if the equipment status after actual execution does not match the expected subsequent status, the exception handling process is triggered, and the comprehensive error prevention interlocking conditions are recalculated for subsequent steps; after all steps of the operation ticket are executed, the entire operation process is recorded and written to the operation log and historical operation ticket database.

Images