A relay protection measure ticket intelligent writing and mistake prevention checking system and method

Abstract

The application provides a relay protection measure ticket intelligent writing and mistake-proofing verification system and method, and belongs to the technical field of relay protection safety management and control. The system comprises a man-machine interface, a work ticket analysis module, a topology model library, a rule engine module, a measure ticket generation module, a real-time data acquisition interface, a mistake-proofing verification module and a storage archiving module. The system extracts target equipment and work types from work information, performs breadth-first search based on the connection relationship of the equipment in the topology model library, matches dangerous points and safety measures in combination with the rule library, instantiates executable rules for specific equipment identifiers, generates electronic measure tickets containing expected state sequences, acquires actual equipment states through primary and secondary equipment acquisition terminals and mobile intelligent terminals during execution, compares the actual equipment states with the expected states, and alarms and locks when the actual equipment states are inconsistent with the expected states. Meanwhile, operation logs are associated and stored. The application realizes dynamic generation and mistake-proofing closed-loop control of measure tickets, and improves the safety of relay protection operation.

Description

Technical Field

[0001] This application belongs to the field of relay protection safety management technology, specifically relating to a relay protection measure ticket intelligent writing and anti-misoperation verification system and method. Background Technology

[0002] Relay protection safety measures tickets are crucial for preventing misoperation and ensuring personal and equipment safety during the maintenance, calibration, and upgrade of secondary equipment in power systems. Currently, power companies generally use safety measures tickets based on paper templates or simple electronic forms. Before starting work, staff manually fill out hazard analysis and safety control measures according to the inspection regulations for relay protection and automatic safety devices and on-site operating procedures. These measures include setting up fences around the busbar protection panel to be inspected, turning on designated power switches, and hanging warning signs.

[0003] However, existing measures tickets have the following inherent defects: First, the content of the measures ticket is static and fixed, disconnected from the actual status of the equipment on site. For example, items recorded in the measures ticket such as "open xx switch" and "remove xx pressure plate" are only textual descriptions and cannot automatically sense the real-time status of primary and secondary equipment such as circuit breaker position, handcart position, and protection pressure plate status. Executors need to visually inspect each item and manually check the "execution status," which is very easy to cause omissions due to visual oversights or habitual violations. Second, temporary modifications and restorations rely on manual records. Temporary dismantling of secondary lines, removal of pressure plates, and modification of settings during maintenance rely solely on paper records and the principle of restoration by the dismantling party, lacking traceable electronic closed-loop management, and restoration omissions occur frequently.

[0004] Therefore, there is an urgent need for an intelligent writing and management system for relay protection measures tickets that can automatically sense the real-time status of equipment, dynamically link the content of the measures ticket with the status of on-site equipment, and conduct electronic closed-loop traceability of temporary modifications. Summary of the Invention

[0005] In a first aspect, embodiments of this application provide an intelligent writing and error-proofing verification system for relay protection measure tickets, comprising: The human-computer interaction interface is used to receive work information input by the user, and to display the generated electronic measure ticket content and execution verification results; The work order parsing module is used to extract the target equipment name and work type from the work information; A topology model library is used to store topology data on the electrical connection relationships and logical spacing relationships between primary and secondary equipment in a power system. The rule engine module is used to read preset hazard point text and safety control measure text from the built-in rule library, and match the text combination applicable to the current work scenario based on the target device name, working type and topology data, and then instantiate it into an executable rule for a specific device identifier. The measure ticket generation module is used to generate electronic measure tickets containing equipment identifiers and expected operation state sequences according to executable rules, and display them through a human-computer interaction interface; The real-time data acquisition interface is used to acquire the actual status data of relevant equipment in the power system in real time during the execution of electronic measures tickets; The error prevention and verification module is used to automatically compare the actual status data with the expected status of the current step in the electronic measures ticket when the user performs each step of the operation. If there is a discrepancy, an alarm will be issued through the human-computer interaction interface and the execution will be prohibited. The storage and archiving module is used to associate and store the content of the finally confirmed electronic measures ticket with the operation logs during the execution process.

[0006] Furthermore, the topology data stored in the topology model library includes the electrical connection relationships and logical membership relationships between bays, cabinets, circuit breakers, disconnect switches, protection pressure plates, current transformers, and voltage transformers at each voltage level. The logical membership relationships are stored in a graph structure, with devices as nodes and connections as edges.

[0007] Furthermore, the real-time data acquisition interface includes a primary equipment status acquisition terminal, a secondary equipment status acquisition terminal, and a mobile smart terminal; The primary equipment status acquisition terminal is connected to the substation monitoring system through the station control layer communication protocol. It is used to collect the opening and closing positions of circuit breakers, the opening and closing positions of disconnecting switches, and the working, testing, or maintenance positions of handcart-type switchgear in real time. The secondary equipment status acquisition terminal is connected to the protection device via hardwiring to collect the real-time status of the protection pressure plate, the operation or maintenance status of the protection device, and the on / off status of the test power circuit breaker. The mobile smart terminal connects to the anti-misoperation verification module via wireless communication, and is used to scan the device's electronic tag to read the device code in order to confirm the physical location of the current operation.

[0008] Secondly, embodiments of this application also provide a method for intelligent writing and error prevention verification of relay protection measure tickets applied to the system described in the first aspect, comprising the following steps: S1. Receive work information input by the user through the human-computer interaction interface, and extract the target equipment name and work type from the work information through the work ticket parsing module; S2. The rule engine module reads preset danger point text and safety control measure text from the built-in rule library, and matches the text combination applicable to the current working scenario based on the target device name, working type and topology data in the topology model library, and then instantiates it into an executable rule for a specific device identifier. S3. The measure ticket generation module generates electronic measure tickets containing equipment identifiers and expected operation state sequences based on executable rules, and displays them through a human-machine interface; S4. Respond to the user's confirmation command for the electronic measure ticket through the human-computer interaction interface and generate the final confirmed electronic measure ticket; S5. When performing each step of the final confirmed electronic measures ticket, the actual status data of the relevant equipment is obtained through the real-time data acquisition interface. The error prevention verification module automatically compares the actual status data with the expected status of the current step. If they match, execution is allowed. If they do not match, an alarm is issued and execution is prohibited. S6. The storage and archiving module associates and stores the content of the final executed measures ticket with the operation logs during the execution process.

[0009] Furthermore, the specific steps of step S2 are as follows: S21. Starting with the target device name, perform a breadth-first search in the topology data stored in the topology model library, with a search depth of N, to generate a set of neighboring running devices. ; This represents the device identifier of the i-th neighboring operating device found, where i = 1, 2, ..., k, and k is the total number of neighboring operating devices found. S22. Based on the target equipment name, working type, and set of nearby operating equipment, filter out hazard point texts and corresponding safety control measure texts related to the current work scenario from the rule base; S23. Replace the device placeholders in each selected safety control measure text with the specific device identifiers from the set of nearby operating devices, and add the expected operating status to generate executable rules for the specific device identifiers.

[0010] Furthermore, the danger points in step S22 include at least one or more of the following danger points: mistakenly entering the wrong interval, reverse voltage transmission, and forgetting to restore temporary modifications; The specific steps for generating the executable rule in step S23 are as follows: For dangerous points where the wrong interval is visited, the following executable rules are generated: If the device code scanned by the current mobile smart terminal is not equal to the device identifier specified in the current operation step, an interval error alarm will be triggered. For voltage backfeeding danger points, the following executable rules are generated: When the target equipment type is a current transformer and the working type is test, a prerequisite measure item is automatically generated in the electronic measure ticket. The prerequisite measure item is to disconnect the current and voltage circuits associated with the equipment under maintenance and the operating equipment, and the expected state of the prerequisite measure item is set to disconnected. For the risk of forgetting to undo temporary changes, the following executable rules are generated: The storage and archiving module is required to record temporarily disassembled secondary lines, removed pressure plates, and modified settings, and to generate a recovery checklist in step S5, which is then associated with the work order number.

[0011] Furthermore, the specific steps of step S3 are as follows: S31. The measure ticket generation module generates an electronic measure ticket containing equipment identification and expected operation state sequence according to executable rules, and displays it through the human-machine interface; S32. Respond to the user's editing operation on the electronic measure ticket through the human-computer interaction interface. The editing operation includes adding new operation steps, deleting existing operation steps, modifying the expected state in any operation step, and adjusting the execution order of operation steps. S33. The human-computer interaction interface records each editing operation and generates an editing record; the editing record includes at least the editing operation type, the content of the edited operation steps, the state before editing, the state after editing, the editing timestamp, and the editor's identifier; S34. The edited electronic procedure ticket is displayed as an electronic procedure ticket pending confirmation through the human-computer interaction interface, awaiting user confirmation.

[0012] Furthermore, the specific steps of step S5 are as follows: S51. Read the operation item of the current step to be executed from the finally confirmed electronic measure ticket, and obtain the device identifier and expected status in the operation item; S52. Obtain the actual status of the device identifier through the real-time data acquisition interface; If the real-time status equals the expected status, a verification pass signal is returned through the human-computer interaction interface, allowing the user to confirm the execution of this step, and recording the executor, execution timestamp, pre-operation status, and post-operation status; If the real-time status is not equal to the expected status, an alarm message will be issued through the human-machine interface, displaying the difference between the expected status and the actual status, and prohibiting the execution of the current step and all subsequent steps until the lockout is manually released. S53. After the current step is completed, the next step will be executed automatically. Steps S51 to S52 will be repeated until all steps are completed.

[0013] Furthermore, in step S5, after each operation step has been verified and the user has confirmed the execution, the following steps are also included: The error prevention and verification module generates operation logs corresponding to the operation steps in real time and transmits the operation logs to the storage and archiving module in real time. The operation log includes at least the executor's identifier, execution timestamp, pre-operation status, post-operation status, device identifier and expected status of the current operation step, and associated electronic work order number.

[0014] Furthermore, the specific steps of step S6 are as follows: S61. The storage and archiving module generates a unique checksum for each received operation log using a hash algorithm; S62. The storage and archiving module associates the raw data of the operation log with a unique check code and stores it in the database for audit traceability.

[0015] As can be seen from the above technical solutions, this application has the following advantages: The intelligent writing and error-proof verification system and method for relay protection measures tickets provided in this application can automatically match dangerous points and safety measures based on work order information and equipment topology, generating targeted electronic measures tickets, improving ticketing efficiency and accuracy, and changing the inefficient mode of traditional manual filling; it obtains the actual status of equipment through a real-time data acquisition interface, ensuring that the expected status is compared with the actual status before each operation, and alarms and lockouts are triggered if there is a discrepancy, effectively preventing safety accidents such as misoperation and wrong interval operation; it forcibly records the temporarily disassembled secondary lines, pressure plates, and settings for forgetting to restore temporary modifications, and generates a restoration checklist during the execution phase, realizing electronic closed-loop traceability; it records the operation log throughout the process and uses a hash algorithm to generate a unique verification code for storage, ensuring that the data is tamper-proof and facilitating post-event auditing and accountability. Attached Figure Description

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

[0017] Figure 1 This is a schematic diagram of the intelligent writing and error prevention verification system for relay protection measures tickets of the present invention.

[0018] Figure 2 This is a flowchart illustrating the intelligent writing and error prevention verification method for relay protection measure tickets according to the present invention. Detailed Implementation

[0019] The various embodiments of this disclosure will be described more fully in the following detailed description of the intelligent writing and error prevention verification system for relay protection measures tickets. This disclosure may have various embodiments, and adjustments and changes may be made therein. However, it should be understood that there is no intention to limit the various embodiments of this disclosure to the specific embodiments disclosed herein, but rather this disclosure should be understood to cover all adjustments, equivalents, and / or alternatives falling within the spirit and scope of the various embodiments of this disclosure.

[0020] This embodiment provides an intelligent writing and error prevention verification system for relay protection measures tickets. It automatically generates electronic measures tickets based on a topology and rule engine, compares the status in real time to prevent errors, and can trace temporary changes.

[0021] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0022] Please see Figure 1 The diagram shown is a schematic of a relay protection measure ticket intelligent writing and anti-misoperation verification system in a specific embodiment. The system includes: The human-computer interaction interface is used to receive work information input by the user, and to display the generated electronic measure ticket content and execution verification results; The work order parsing module is used to extract the target equipment name and work type from the work information; A topology model library is used to store topology data on the electrical connection relationships and logical spacing relationships between primary and secondary equipment in a power system. The rule engine module is used to read preset hazard point text and safety control measure text from the built-in rule library, and match the text combination applicable to the current work scenario based on the target device name, working type and topology data, and then instantiate it into an executable rule for a specific device identifier. The measure ticket generation module is used to generate electronic measure tickets containing equipment identifiers and expected operation state sequences according to executable rules, and display them through a human-computer interaction interface; The real-time data acquisition interface is used to acquire the actual status data of relevant equipment in the power system in real time during the execution of electronic measures tickets; The error prevention and verification module is used to automatically compare the actual status data with the expected status of the current step in the electronic measures ticket when the user performs each step of the operation. If there is a discrepancy, an alarm will be issued through the human-computer interaction interface and the execution will be prohibited. The storage and archiving module is used to associate and store the content of the finally confirmed electronic measures ticket with the operation logs during the execution process; It should be noted that the human-computer interaction interface receives work information and outputs key results, improving user experience and interaction efficiency; the work ticket parsing module automatically extracts target equipment and work type as key elements, reducing repetitive manual data entry and providing raw data for automated processing; the topology model library stores the electrical and logical connection relationships between devices, enabling the system to perform spatial awareness; the rule engine module transforms static safety procedures into dynamic executable rules, instantiating rules according to the current scenario, solving the problem of matching general rules with specific equipment; the measure ticket generation module transforms abstract rules into electronic measure tickets with specific and orderly operation step lists, and displays them to the user; the real-time data acquisition interface connects primary and secondary equipment and mobile terminals to obtain physical world status data in real time, enabling the system to perceive the real situation on site; the error prevention verification module performs logical judgment at the moment of operation execution, and if it does not meet the ticket requirements, it immediately alarms and locks, effectively preventing misoperation; the storage and archiving module is responsible for data storage throughout the entire lifecycle, associating measure tickets with operation logs to provide a basis for auditing, review, and accident investigation.

[0023] This embodiment achieves intelligent generation of measure tickets through topology search and rule matching; prevents misoperation through real-time status comparison and locking mechanism; and achieves closed-loop management by forcibly recording temporary changes and generating a recovery list.

[0024] Taking the verification of the 220kV busbar protection cabinet I as an example.

[0025] Assume the user inputs the following work information through the human-computer interaction interface: the work location is the 220kV busbar protection cabinet I, the work content is verification, and the planned work time is from 13:00 to 17:00 on May 2, 2026.

[0026] The work order parsing module extracts the target equipment name as 220kV busbar protection cabinet I and the work type as verification.

[0027] The topology data stored in the topology model library shows that the bus protection cabinet I is adjacent to the 220kV xx line protection panel and the 220kV xx line protection panel, and is electrically connected to the bus PT circuit and CT circuit.

[0028] The rule engine module starts with the 220kV busbar protection I cabinet and performs a breadth-first search (e.g., depth N=2) to generate a set of neighboring operating equipment: Neighbors={220kV xx line protection panel, 220kV xx line protection panel, busbar PT circuit, busbar CT circuit}. Pre-defined danger points for incorrect interval operation in the rule base are matched to adjacent operating equipment and instantiated as executable rules: Before operating the 220kV busbar protection I cabinet, a mobile smart terminal must scan the equipment's electronic tag to confirm that the equipment code matches the 220kV busbar protection I cabinet; otherwise, an interval error alarm is triggered. Danger points for voltage backfeeding are matched to the busbar CT circuit and instantiated as a preemptive measure: Disconnect the current and voltage circuits between the busbar CT circuit and the protection I cabinet; expected state = disconnected.

[0029] The emergency response ticket generation module converts the above rules into an operation sequence, generating an electronic emergency response ticket containing the following operation items (i.e., numbered sequentially): 1. Scan the electronic tag of the 220kV busbar protection cabinet I to confirm its location; 2. Disconnect the current and voltage circuits of the busbar CT circuit; 3. ... (the remaining operation items). After user confirmation, the module executes the operation, comparing the actual status of the equipment at each step to ensure safety.

[0030] Furthermore, as a refinement and extension of the specific implementation methods of the above embodiments, in order to fully illustrate the specific implementation process of this embodiment, another intelligent writing and error prevention verification system for relay protection measures tickets is provided. This system includes: The human-computer interaction interface is used to receive work information input by the user, and to display the generated electronic measure ticket content and execution verification results; The human-computer interaction interface includes: The work information input unit is used to receive work information submitted by the user in the form of text input or voice input. The work information includes at least the work location, work content, planned work time and work team information. The measure ticket display unit is used to display the operation sequence in the electronic measure ticket in the form of a list or step card, and to highlight the step to be executed. The verification result feedback unit is used to receive the comparison results from the anti-misoperation verification module. When the verification passes, it displays a pass indicator; when the verification fails, it displays alarm information and details comparing the expected state with the actual state. The work order parsing module is used to extract the target equipment name and work type from the work information; The work order parsing module includes: The natural language processing unit is used to perform word segmentation and entity recognition on work information, and extract the target equipment name from the work location field, the work type from the work content field, and the start and end times from the planned work time field. The structured output unit is used to encapsulate the extracted target device name, work type, and start and end times into structured data objects, and provide them to the rule engine module and the storage and archiving module. A topology model library is used to store topology data on the electrical connection relationships and logical spacing relationships between primary and secondary equipment in a power system. The topology data stored in the topology model library includes the electrical connection relationships and logical membership relationships between bays, cabinets, circuit breakers, disconnect switches, protection pressure plates, current transformers, and voltage transformers at each voltage level. The logical membership relationships are stored in a graph structure, with devices as nodes and connections as edges; The rule engine module is used to read preset hazard point text and safety control measure text from the built-in rule library, and match the text combination applicable to the current work scenario based on the target device name, working type and topology data, and then instantiate it into an executable rule for a specific device identifier. The rules engine module also includes: The rule base management unit is used to store, update, and retrieve preset hazard texts and safety control measure texts. Each hazard text is associated with at least one safety control measure text. The hazard texts include: wrong interval, AC / DC circuit short circuit to ground, voltage backfeeding, temporary modification forgotten to be restored, hot plugging and unplugging plugs, electric shock when connecting or disconnecting power supply, crossing the barrier, and improper coordination of protection transmission. The topology search unit is used to perform a breadth-first search in the topology model library, starting from the target device name, to generate a list of nearby running device identifiers, and provide it to the rule base management unit for matching; The rule instantiation unit is used to replace the device placeholders in the matched safety control measure text with the specific device identifiers in the list of adjacent running device identifiers, and to supplement the expected operating status to generate an executable rule instance. The measure ticket generation module is used to generate electronic measure tickets containing equipment identifiers and expected operation state sequences according to executable rules, and display them through a human-computer interaction interface; The measure ticket generation module includes: The operation sequence construction unit is used to receive executable rule instances generated by the rule engine module, and convert each rule instance into an operation item. Each operation item includes the device identifier Dev_ID, the expected state Expected_State, and the operation sequence number Seq_No. The sorting and encapsulation unit is used to sort all operation items in ascending order according to their operation sequence number Seq_No, forming an operation sequence, and encapsulate it into an electronic measure ticket data object; the electronic measure ticket data object also includes a unique ticket number, a generation timestamp, and an associated electronic work ticket number; The display interface unit is used to output the electronic measure ticket data object to the human-computer interaction interface for display. The real-time data acquisition interface is used to acquire the actual status data of relevant equipment in the power system in real time during the execution of electronic measures tickets; Real-time data acquisition interfaces include primary equipment status acquisition terminals, secondary equipment status acquisition terminals, and mobile smart terminals; The primary equipment status acquisition terminal is connected to the substation monitoring system through the station control layer communication protocol. It is used to collect the opening and closing positions of circuit breakers, the opening and closing positions of disconnecting switches, and the working, testing, or maintenance positions of handcart-type switchgear in real time. The secondary equipment status acquisition terminal is connected to the protection device via hardwiring to collect the real-time status of the protection pressure plate, the operation or maintenance status of the protection device, and the on / off status of the test power circuit breaker. The mobile smart terminal connects to the anti-misoperation verification module via wireless communication, and is used to scan the device's electronic tag to read the device code in order to confirm the physical location of the current operation; The error prevention and verification module is used to automatically compare the actual status data with the expected status of the current step in the electronic measures ticket when the user performs each step of the operation. If there is a discrepancy, an alarm will be issued through the human-computer interaction interface and the execution will be prohibited. The error prevention and verification module includes: The step reading unit is used to read the operation items of the current step to be executed sequentially from the finally confirmed electronic measure ticket, and obtain the device identifier Dev_ID_Current and expected state Expected_State_Current in the operation item; The status acquisition unit is used to acquire the actual status (Actual_State) of the device identifier Dev_ID_Current through the real-time data acquisition interface. The comparison and judgment unit is used to compare the actual state Actual_State with the expected state Expected_State_Current. If they are equal, a verification pass signal is output; if they are not equal, a verification failure signal is output and difference information is generated. The execution control unit is used to output based on the result of the comparison and judgment unit: If the verification passes, the user is allowed to confirm the execution and the storage and archiving module is notified to record the operation log. If the verification fails, an alarm will be issued through the human-computer interaction interface, and the execution of the current step and all subsequent steps will be prohibited. The storage and archiving module is used to associate and store the content of the finally confirmed electronic measures ticket with the operation logs during the execution process; The storage and archiving module includes: The log receiving unit is used to receive the operation log generated by the anti-misoperation verification module after each operation is completed. The operation log includes at least the executor identifier, execution timestamp Time_Stamp, pre-operation state State_Before, post-operation state State_After, device identifier and expected state of the current operation step, and associated electronic work ticket number. The hash calculation unit is used to perform the SHA-256 hash algorithm on the complete content string Log_Content of each operation log and generate a unique verification code Hash_Code=SHA-256(Log_Content); The system uses a dual storage unit to associate the raw data of the operation log with the unique verification code and store it in a relational database. At the same time, the unique verification code is simultaneously uploaded to the blockchain evidence storage platform or an independent hash evidence storage server. The query verification unit is used to respond to the query command input by the user, retrieve the corresponding operation log and verification code according to the electronic work order number, and verify the authenticity and integrity of the log by recalculating the hash value.

[0031] like Figure 2 As shown, the following are embodiments of the intelligent writing and anti-misoperation verification method for relay protection measures tickets provided in this disclosure. This method and the intelligent writing and anti-misoperation verification system for relay protection measures tickets in the above embodiments belong to the same inventive concept. For details not described in detail in the embodiments of the intelligent writing and anti-misoperation verification method for relay protection measures tickets, please refer to the embodiments of the intelligent writing and anti-misoperation verification system for relay protection measures tickets described above.

[0032] The method includes the following steps: S1. Receive work information input by the user through the human-computer interaction interface, and extract the target equipment name and work type from the work information through the work ticket parsing module; It should be noted that this step obtains basic work parameters to ensure that the subsequently generated measures tickets are highly relevant to the work tasks; S2. The rule engine module reads preset danger point text and safety control measure text from the built-in rule library, and matches the text combination applicable to the current working scenario based on the target device name, working type and topology data in the topology model library, and then instantiates it into an executable rule for a specific device identifier. It should be noted that this step automatically analyzes the danger points in the current work scenario through topology data and rule base, and generates specific and executable operation instructions to avoid manually omitting safety measures. S3. The measure ticket generation module generates electronic measure tickets containing equipment identifiers and expected operation state sequences based on executable rules, and displays them through a human-machine interface; It should be noted that this step converts the generated rules into a visual electronic ticket for staff to preview and confirm, thereby improving invoicing efficiency. S4. Respond to the user's confirmation command for the electronic measure ticket through the human-computer interaction interface and generate the final confirmed electronic measure ticket; It should be noted that this step ensures that the generated tickets are subject to final manual confirmation before they become effective, thus ensuring both the efficiency and accuracy of ticket generation. S5. When performing each step of the final confirmed electronic measures ticket, the actual status data of the relevant equipment is obtained through the real-time data acquisition interface. The error prevention verification module automatically compares the actual status data with the expected status of the current step. If they match, execution is allowed. If they do not match, an alarm is issued and execution is prohibited. It should be noted that this step involves real-time monitoring of the device status during execution, and operation is only permitted if the status remains consistent, effectively preventing accidental operation. S6. The storage and archiving module associates and stores the final executed measures ticket content with the operation logs during the execution process; It should be noted that this step will store the completed tickets and operation logs to ensure subsequent auditing and traceability.

[0033] This embodiment centers on the target device, constructs a set of nearby operating devices through breadth-first search, and matches hazardous points. An executable rule engine automatically generates rules for specific devices. During execution, real-time data acquisition interfaces are used to obtain circuit breaker, pressure plate, and physical location information, which is rigorously compared with the expected state. If discrepancies are found, an alarm is immediately triggered, and subsequent operations are prohibited to prevent misoperation. Furthermore, by forcibly recording temporary changes and generating a recovery list, and using a hash algorithm to associate and store the entire operation log, the auditability and traceability of the operation process are ensured, improving the safety and control level of relay protection operations.

[0034] Furthermore, as a refinement and extension of the specific implementation of the above embodiments, in order to fully illustrate the specific implementation process of this embodiment, another method for intelligent writing and error prevention verification of relay protection measure tickets is provided. This method includes the following steps: S1. Receive work information input by the user through the human-computer interaction interface, and extract the target equipment name and work type from the work information through the work ticket parsing module; The specific steps of step S1 are as follows: S11. Receive work information input by the user through a human-computer interaction interface, wherein the work information is in the form of a structured form or natural language text; If the work information is natural language text, the work ticket parsing module calls the natural language processing unit to perform word segmentation and entity recognition on the work information, and extracts the target equipment name in the work location field, the work type in the work content field, and the start and end time in the planned work time field. If the work information is a structured form, the value of the corresponding field in the form can be read directly through the work ticket parsing module; S12. The work order parsing module encapsulates the extracted target device name, work type, and start and end time into a structured data object and provides it to the rule engine module and the storage and archiving module. S2. The rule engine module reads preset danger point text and safety control measure text from the built-in rule library, and matches the text combination applicable to the current working scenario based on the target device name, working type and topology data in the topology model library, and then instantiates it into an executable rule for a specific device identifier. The specific steps of step S2 are as follows: S21. Starting with the target device name, perform a breadth-first search in the topology data stored in the topology model library, with a search depth of N, to generate a set of neighboring running devices. ; This represents the device identifier of the i-th neighboring operating device found, where i = 1, 2, ..., k, and k is the total number of neighboring operating devices found. It should be noted that the search depth N in step S21 can be set according to the actual substation scale. In a specific embodiment, N is 2, that is, searching for adjacent operating equipment that is directly connected to the target equipment (i.e., depth 1) and indirectly connected through an intermediate device (i.e., depth 2). For example, if the target equipment is "#1 generator-transformer group protection device", depth 1 searches to obtain its cabinet and the current transformer circuit directly connected; depth 2 searches to obtain the #1 main transformer protection panel associated with the current transformer circuit. The value of depth N can be configured by the system or specified by the user according to the topology complexity of the field equipment. Generally, N=2 to 3 is taken to cover the main associated equipment without generating too many irrelevant items. S22. Based on the target equipment name, working type, and set of nearby operating equipment, filter out hazard point texts and corresponding safety control measure texts related to the current work scenario from the rule base; S23. Replace the device placeholders in each selected safety control measure text with the specific device identifiers from the set of adjacent operating devices, and supplement the expected operating status to generate executable rules for the specific device identifiers; The danger points in step S22 include at least one or more of the following danger points: mistakenly entering the wrong interval, reverse voltage transmission, and forgetting to restore temporary modifications; The specific steps for generating the executable rule in step S23 are as follows: For dangerous points where the wrong interval is visited, the following executable rules are generated: If the device code scanned by the current mobile smart terminal is not equal to the device identifier specified in the current operation step, an interval error alarm will be triggered. For voltage backfeeding danger points, the following executable rules are generated: When the target equipment type is a current transformer and the working type is test, a prerequisite measure item is automatically generated in the electronic measure ticket. The prerequisite measure item is to disconnect the current and voltage circuits associated with the equipment under maintenance and the operating equipment, and the expected state of the prerequisite measure item is set to disconnected. For the risk of forgetting to undo temporary changes, the following executable rules are generated: The storage and archiving module is required to record temporarily disassembled secondary lines, removed pressure plates, and modified setpoints, and to generate a recovery checklist in step S5, and associate the recovery checklist with the work order number. S3. The measure ticket generation module generates electronic measure tickets containing equipment identifiers and expected operation state sequences based on executable rules, and displays them through a human-machine interface; The specific steps of step S3 are as follows: S31. The measure ticket generation module generates an electronic measure ticket containing equipment identification and expected operation state sequence according to executable rules, and displays it through the human-machine interface; S32. Respond to the user's editing operation on the electronic measure ticket through the human-computer interaction interface. The editing operation includes adding new operation steps, deleting existing operation steps, modifying the expected state in any operation step, and adjusting the execution order of operation steps. S33. The human-computer interaction interface records each editing operation and generates an editing record; the editing record includes at least the editing operation type, the content of the edited operation steps, the state before editing, the state after editing, the editing timestamp, and the editor's identifier; S34. The edited electronic procedure ticket is displayed as an electronic procedure ticket pending confirmation through the human-computer interaction interface, awaiting user confirmation; S4. Respond to the user's confirmation command for the electronic measure ticket through the human-computer interaction interface and generate the final confirmed electronic measure ticket; The specific steps of step S4 are as follows: S41. Display the electronic measure ticket to be confirmed generated in step S3 through the human-computer interaction interface. The display content includes a list of operation sequences and the expected status of each operation item. S42. Respond to the user's confirmation command through the human-computer interaction interface; the confirmation command includes two modes: full confirmation or item-by-item confirmation; S43. If the user chooses to confirm each item, then each operation item will be displayed in turn and the user will be required to confirm it individually until all operation items have been confirmed. S44. In response to the final confirmation instruction, mark the status of the current electronic measures ticket as confirmed, generate a unique ticket number, and associate the unique ticket number with the operation sequence; S45. Provide the confirmed electronic measure ticket content and unique ticket number to the error prevention verification module; S5. When performing each step of the final confirmed electronic measures ticket, the actual status data of the relevant equipment is obtained through the real-time data acquisition interface. The error prevention verification module automatically compares the actual status data with the expected status of the current step. If they match, execution is allowed. If they do not match, an alarm is issued and execution is prohibited. The specific steps of step S5 are as follows: S51. Read the operation item of the current step to be executed from the finally confirmed electronic measure ticket, and obtain the device identifier Dev_ID_Current and expected state Expected_State_Current from the operation item; S52. Obtain the actual state (Actual_State) of the device identifier Dev_ID_Current through the real-time data acquisition interface; If the real-time state Actual_State equals the expected state Expected_State_Current, a verification pass signal is returned through the human-computer interaction interface, allowing the user to confirm the execution of this step, and recording the executor, execution timestamp, state before operation, and state after operation; If the real-time state Actual_State is not equal to the expected state Expected_State_Current, an alarm message will be issued through the human-computer interaction interface, displaying the difference between the expected state and the actual state, and prohibiting the execution of the current step and all subsequent steps until the lockout is manually released. S53. After the current step is completed, the next step will be executed automatically. Steps S51 to S52 will be repeated until all steps are completed. Step S5, after each operation step has been verified and the user has confirmed the execution, also includes the following steps: The error prevention and verification module generates operation logs corresponding to the operation steps in real time and transmits the operation logs to the storage and archiving module in real time. The operation log includes at least the executor identifier, execution timestamp (Time_Stamp), pre-operation state (State_Before), post-operation state (State_After), device identifier and expected state of the current operation step, and associated electronic work order number. S6. The storage and archiving module associates and stores the final executed measures ticket content with the operation logs during the execution process; The specific steps of step S6 are as follows: S61. The storage and archiving module generates a unique checksum for each received operation log using a hash algorithm; S62. The storage and archiving module associates the raw data of the operation log with a unique check code and stores it in the database for audit traceability.

[0035] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0036] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A smart writing and error-proofing verification system for relay protection measure tickets, characterized in that, include: The human-computer interaction interface is used to receive work information input by the user, and to display the generated electronic measure ticket content and execution verification results; The work order parsing module is used to extract the target equipment name and work type from the work information; A topology model library is used to store topology data on the electrical connection relationships and logical spacing relationships between primary and secondary equipment in a power system. The rule engine module is used to read preset hazard point text and safety control measure text from the built-in rule library, and match the text combination applicable to the current work scenario based on the target device name, working type and topology data, and then instantiate it into an executable rule for a specific device identifier. The measure ticket generation module is used to generate electronic measure tickets containing equipment identifiers and expected operation state sequences according to executable rules, and display them through a human-computer interaction interface; The real-time data acquisition interface is used to acquire the actual status data of relevant equipment in the power system in real time during the execution of electronic measures tickets; The error prevention and verification module is used to automatically compare the actual status data with the expected status of the current step in the electronic measures ticket when the user performs each step of the operation. If there is a discrepancy, an alarm will be issued through the human-computer interaction interface and the execution will be prohibited. The storage and archiving module is used to associate and store the content of the finally confirmed electronic measures ticket with the operation logs during the execution process.

2. The intelligent writing and error-proofing verification system for relay protection measure tickets according to claim 1, characterized in that, The topology data stored in the topology model library includes the electrical connection relationships and logical membership relationships between bays, cabinets, circuit breakers, disconnect switches, protection pressure plates, current transformers, and voltage transformers at each voltage level. The logical membership relationships are stored in a graph structure, with devices as nodes and connections as edges.

3. The intelligent writing and error-proofing verification system for relay protection measure tickets according to claim 1, characterized in that, Real-time data acquisition interfaces include primary equipment status acquisition terminals, secondary equipment status acquisition terminals, and mobile smart terminals; The primary equipment status acquisition terminal is connected to the substation monitoring system through the station control layer communication protocol. It is used to collect the opening and closing positions of circuit breakers, the opening and closing positions of disconnecting switches, and the working, testing, or maintenance positions of handcart-type switchgear in real time. The secondary equipment status acquisition terminal is connected to the protection device via hardwiring to collect the real-time status of the protection pressure plate, the operation or maintenance status of the protection device, and the on / off status of the test power circuit breaker. The mobile smart terminal connects to the anti-misoperation verification module via wireless communication, and is used to scan the device's electronic tag to read the device code in order to confirm the physical location of the current operation.

4. A method for intelligent writing and error prevention verification of relay protection measure tickets applied to the system described in any one of claims 1 to 3, characterized in that, Includes the following steps: S1. Receive work information input by the user through the human-computer interaction interface, and extract the target equipment name and work type from the work information through the work ticket parsing module; S2. The rule engine module reads preset danger point text and safety control measure text from the built-in rule library, and matches the text combination applicable to the current working scenario based on the target device name, working type and topology data in the topology model library, and then instantiates it into an executable rule for a specific device identifier. S3. The measure ticket generation module generates electronic measure tickets containing equipment identifiers and expected operation state sequences based on executable rules, and displays them through a human-machine interface; S4. Respond to the user's confirmation command for the electronic measure ticket through the human-computer interaction interface and generate the final confirmed electronic measure ticket; S5. When performing each step of the final confirmed electronic measures ticket, the actual status data of the relevant equipment is obtained through the real-time data acquisition interface. The error prevention verification module automatically compares the actual status data with the expected status of the current step. If they match, execution is allowed. If they do not match, an alarm is issued and execution is prohibited. S6. The storage and archiving module associates and stores the content of the final executed measures ticket with the operation logs during the execution process.

5. The intelligent writing and error-proofing verification method for relay protection measure tickets according to claim 4, characterized in that, The specific steps of step S2 are as follows: S21. Starting with the target device name, perform a breadth-first search in the topology data stored in the topology model library, with a search depth of N, to generate a set of neighboring running devices. ; This represents the device identifier of the i-th neighboring operating device found, where i = 1, 2, ..., k, and k is the total number of neighboring operating devices found. S22. Based on the target equipment name, working type, and set of nearby operating equipment, filter out hazard point texts and corresponding safety control measure texts related to the current working scenario from the rule base; S23. Replace the device placeholders in each selected safety control measure text with the specific device identifiers from the set of nearby operating devices, and add the expected operating status to generate executable rules for the specific device identifiers.

6. The intelligent writing and error-proofing verification method for relay protection measure tickets according to claim 5, characterized in that, The danger points in step S22 include at least one or more of the following danger points: mistakenly entering the wrong interval, reverse voltage transmission, and forgetting to restore temporary modifications; The specific steps for generating the executable rule in step S23 are as follows: For dangerous points where the wrong interval is visited, the following executable rules are generated: If the device code scanned by the current mobile smart terminal is not equal to the device identifier specified in the current operation step, an interval error alarm will be triggered. For voltage backfeeding danger points, the following executable rules are generated: When the target equipment type is a current transformer and the working type is test, a preliminary measure item is automatically generated in the electronic measure ticket. The preliminary measure item is to disconnect the current and voltage circuits associated with the equipment under maintenance and the operating equipment, and the expected state of the preliminary measure item is set to disconnected. For the risk of forgetting to undo temporary changes, the following executable rules are generated: The storage and archiving module is required to record temporarily disassembled secondary lines, removed pressure plates, and modified settings, and to generate a recovery checklist in step S5, which is then associated with the work order number.

7. The intelligent writing and error-proofing verification method for relay protection measure tickets according to claim 4, characterized in that, The specific steps of step S3 are as follows: S31. The measure ticket generation module generates an electronic measure ticket containing equipment identification and expected operation state sequence according to executable rules, and displays it through the human-machine interface; S32. Respond to the user's editing operation on the electronic measure ticket through the human-computer interaction interface. The editing operation includes adding new operation steps, deleting existing operation steps, modifying the expected state in any operation step, and adjusting the execution order of operation steps. S33. The human-computer interaction interface records each editing operation and generates an editing record; the editing record includes at least the editing operation type, the content of the edited operation steps, the state before editing, the state after editing, the editing timestamp, and the editor's identifier; S34. The edited electronic procedure ticket is displayed as an electronic procedure ticket pending confirmation through the human-computer interaction interface, awaiting user confirmation.

8. The intelligent writing and error-proofing verification method for relay protection measure tickets according to claim 4, characterized in that, The specific steps of step S5 are as follows: S51. Read the operation item of the current step to be executed from the finally confirmed electronic measure ticket, and obtain the device identifier and expected status in the operation item; S52. Obtain the actual status of the device identifier through the real-time data acquisition interface; If the real-time status equals the expected status, a verification pass signal is returned through the human-computer interaction interface, allowing the user to confirm the execution of this step, and recording the executor, execution timestamp, pre-operation status, and post-operation status; If the real-time status is not equal to the expected status, an alarm message will be issued through the human-machine interface, displaying the difference between the expected status and the actual status, and prohibiting the execution of the current step and all subsequent steps until the lockout is manually released. S53. After the current step is completed, the next step will be executed automatically. Steps S51 to S52 will be repeated until all steps are completed.

9. The intelligent writing and error-proofing verification method for relay protection measure tickets according to claim 4, characterized in that, Step S5, after each operation step has been verified and the user has confirmed the execution, also includes the following steps: The error prevention and verification module generates operation logs corresponding to the operation steps in real time and transmits the operation logs to the storage and archiving module in real time. The operation log includes at least the executor's identifier, execution timestamp, pre-operation status, post-operation status, device identifier and expected status of the current operation step, and associated electronic work order number.

10. The intelligent writing and error-proofing verification method for relay protection measure tickets according to claim 4, characterized in that, The specific steps of step S6 are as follows: S61. The storage and archiving module generates a unique checksum for each received operation log using a hash algorithm; S62. The storage and archiving module associates the raw data of the operation log with a unique check code and stores it in the database for audit traceability.

Images