Monitoring confirmation system and method, device, electronic equipment and storage medium thereof

Abstract

The application discloses a monitoring and confirming system and a monitoring and confirming method, device, electronic equipment and storage medium thereof. The system comprises a law enforcement recorder terminal, a typical operation ticket library management platform, a backup monitoring terminal and a data interaction server. The law enforcement recorder is arranged at a work site, collects and uploads operation audio and video; the operation ticket platform is provided with a standard ticket library, and can match and issue corresponding operation tickets according to work tasks; the backup monitoring terminal synchronously receives on-site audio and video and standard operation tickets, and checks and confirms each operation node item by item; and the data interaction server serves as a hub, completes data interaction and instruction forwarding of each device, stores operation data in a classified manner and realizes whole-process traceability. The system integrates standard tickets, on-site video collection, remote monitoring and verification and whole-process data storage functions, controls operation nodes from the aspects of pre-standard constraints, real-time monitoring during operation and post-source traceability control, timely deals with illegal operation, and thus prevents electrical misoperation.

Description

Technical Field

[0001] This application relates to the field of electrical operation technology, and more specifically, to a monitoring and verification system, method, apparatus, electronic device, and storage medium thereof. Background Technology

[0002] Electrical misoperation is a common safety hazard in power system operation and has always been highly valued by the industry. Currently, the main methods for preventing electrical misoperation include three categories: electrical safety devices, operation ticket systems, and on-site monitoring systems. Electrical safety devices, through mechanical or electrical interlocking, physically prevent typical misoperations such as opening or closing disconnect switches under load, accidentally opening or closing circuit breakers, and closing switches with grounding wires connected. Operation ticket systems record operational tasks, steps, and precautions in written or electronic form, providing operators with a process reference. On-site monitoring systems assign dedicated personnel to supervise and verify operations at the site to ensure they are performed according to regulations. While these methods have played a certain basic role in power production practice, their implementation methods are independent, and effective information sharing has not been established.

[0003] In practice, operation tickets are typically handwritten by operators or adjusted based on experience, on-site monitoring is mainly conducted by a single person, and audio-visual recording equipment, if used, is mostly used as a tool for post-event evidence collection. There is a lack of data interaction and status linkage among these three elements. Because no correlation mapping is established between the operation ticket content, the on-site monitoring status, and the audio-visual recordings of the operation process, monitoring personnel find it difficult to obtain the current execution node of the operation ticket in real time. Furthermore, after an abnormal operation occurs, it is difficult to compare the operational behavior with the steps on the ticket for retrospective analysis, creating information barriers between the subsystems. This situation makes it difficult for existing prevention and control measures to achieve a system-wide synergistic effect. The effectiveness of prevention and control relies more on the individual experience of operators and the attention of on-site monitoring personnel, thus limiting overall reliability.

[0004] Therefore, in the field of electrical misoperation prevention and control, integrating operation ticket guidance, process monitoring and multiple monitoring into one, and realizing data linkage and status synchronization between various prevention and control links through information interaction server, is one of the technical directions of concern in this field. However, a mature technical solution that can effectively avoid electrical misoperation has not yet been formed. Summary of the Invention

[0005] In view of this, this application provides a monitoring and verification system, method, apparatus, electronic device and storage medium thereof, for avoiding electrical misoperation by monitoring and verifying electrical operation nodes.

[0006] To achieve the above objectives, the following solution is proposed:

[0007] A monitoring and verification system is used to monitor and verify electrical operation nodes. The monitoring and verification system includes...

[0008] The law enforcement recorder terminal is deployed at the electrical operation site to collect and upload audio and video data of the entire electrical operation process;

[0009] The typical operation ticket library management platform has built-in standardized typical operation tickets, which are used to match and retrieve the corresponding typical operation tickets according to the on-site operation tasks;

[0010] The backup monitoring terminal includes a primary monitoring terminal and a secondary monitoring terminal, used to receive audio and video data from the law enforcement recorder terminal and operation ticket information issued by the typical operation ticket library management platform, and to confirm the operation node;

[0011] The data interaction server is used to realize information interaction, data storage and instruction forwarding between the law enforcement recorder terminal, the typical operation ticket management platform and the backup monitoring terminal, and to classify, store and manage the operation data in a traceable manner.

[0012] Optionally, the law enforcement recorder terminal is also equipped with an operation node sensing module, which is used to link with the operation ticket nodes issued by the typical operation ticket library management platform. When the operation reaches the preset node, an alert is issued, and the subsequent operation process can only continue after confirmation by the backup monitoring terminal.

[0013] Optionally, the typical operation ticket management platform includes five modules: operation task, pre-operation preparation, operation steps, post-operation inspection, and hazard prevention. Each operation step is marked with key control points, operation specifications, and prohibited operation requirements. It also supports personalized fine-tuning according to the actual working conditions on site, and the fine-tuning records are automatically saved.

[0014] Optionally, the backup monitoring terminal is further equipped with an anomaly recognition module, which is used to analyze the operation screen collected by the law enforcement recorder terminal in real time, identify the operation actions that do not match the typical operation ticket, and issue an early warning to the law enforcement recorder terminal.

[0015] Optionally, the law enforcement recorder terminal is also equipped with a violation warning module, which is used to receive warning information issued by the backup monitoring terminal and prompt the operator in the form of sound and light, while pausing the current operation process.

[0016] A monitoring and verification method, implemented based on the monitoring and verification system described above, optionally includes the following steps:

[0017] Operation task input and ticket matching: Key information of on-site electrical operation tasks is entered into the typical operation ticket management platform. The platform automatically matches and generates corresponding standardized typical operation tickets, which are then sent to the law enforcement recorder terminal and the backup monitoring terminal after review.

[0018] Pre-operation preparation and monitoring: After the operator arrives at the operation site with the law enforcement recorder terminal, completes the equipment status check and safety measures arrangement, the law enforcement recorder terminal starts audio and video acquisition, and the primary monitoring end and the secondary monitoring end confirm that the monitoring is in place;

[0019] Full-process operation and node verification: The operator performs the operation according to the typical operation ticket steps displayed on the law enforcement recorder terminal. After each preset operation node is completed, the law enforcement recorder terminal issues a reminder, the operator confirms the device status, the first-level monitoring terminal verifies and confirms on-site, and the confirmation information is synchronized to the second-level monitoring terminal and the data interaction server. Without confirmation, the next operation node cannot be entered.

[0020] Abnormal Intervention and Emergency Handling: When the operation behavior is inconsistent with the typical operation ticket, the backup monitoring terminal issues an early warning, the law enforcement recorder terminal receives the early warning and suspends the operation process, and resumes operation after the abnormality is eliminated and the monitoring terminal confirms it;

[0021] Post-operation inspection and data retention: After the operator completes all operation steps, the post-operation inspection is performed according to the typical operation ticket. The first-level monitoring terminal and the second-level monitoring terminal check and confirm in turn. The law enforcement recorder terminal stops collecting data and uploads the audio and video data, operation record, and monitoring confirmation record to the data interaction server for classified storage.

[0022] Ticket database update and case study accumulation: Regularly analyze the operation records and anomaly records in the data interaction server, and update the typical operation ticket database with typical cases and optimized operation processes.

[0023] Optionally, the step of issuing the document after review includes the following steps:

[0024] The shift supervisor or shift leader reviews the standardized typical operation tickets generated on the typical operation ticket management platform.

[0025] After approval, the typical operation ticket management platform distributes the standardized typical operation ticket to the law enforcement recorder terminal and the backup monitoring terminal through the data interaction server.

[0026] Optionally, the preset operation nodes include at least one of the following: equipment power outage, voltage testing, grounding wire connection, disconnection switch operation, circuit breaker operation, and equipment power supply. Each key operation node requires confirmation from both the primary monitoring terminal and the operator, and the law enforcement recorder terminal captures close-up images of the operation process of the key operation nodes.

[0027] Optionally, in the entire process of operation and node verification, if an unsuccessful operation or an abnormal event occurs during the operation, the data interaction server will include the relevant data of the abnormal event as a typical case in the typical operation ticket database, and simultaneously push the corresponding risk prevention and control prompts to the law enforcement recorder terminal and the backup monitoring terminal when matching subsequent operation tickets.

[0028] Optionally, in the entire process operation and node verification, the operator confirming the equipment status includes:

[0029] The current device number can be obtained by scanning the device's QR code or RFID tag using the law enforcement recorder terminal;

[0030] Compare the current device number with the target device number recorded in the typical operation ticket;

[0031] If the comparison is consistent, the device status is confirmed; if the comparison is inconsistent, the abnormal intervention and emergency handling steps are triggered.

[0032] Optionally, the statement that the operation behavior does not conform to the typical operation ticket includes at least one of the following:

[0033] The equipment number of the operation target does not match the target equipment number recorded in the typical operation ticket;

[0034] The execution order of the operation steps is inconsistent with the order of steps recorded on the typical operation ticket;

[0035] The operation action does not match the preset standard action corresponding to the typical operation ticket.

[0036] Optionally, the recovery operation after anomaly elimination and monitoring confirmation includes the following steps:

[0037] After troubleshooting the anomaly, the operator reports the cause of the anomaly to the primary monitoring terminal and the secondary monitoring terminal.

[0038] After the primary monitoring terminal and the secondary monitoring terminal confirm that the anomaly has been eliminated, they send a recovery command to the law enforcement recorder terminal.

[0039] After receiving the recovery command, the law enforcement recorder terminal continues to execute subsequent operation procedures.

[0040] Optionally, the law enforcement recorder terminal issues a reminder, including the following steps:

[0041] Upon reaching a preset operation node, the law enforcement recorder terminal will announce the operation content, key control points, and prohibited operation requirements of the current operation node through voice broadcast and / or display on the screen.

[0042] A monitoring and verification device, implemented based on the monitoring and verification system described above, includes:

[0043] The ticket matching module is configured to perform operation task input and ticket matching: key information of on-site electrical operation tasks is entered into the typical operation ticket management platform, the platform automatically matches and generates corresponding standardized typical operation tickets, and after review, they are sent to the law enforcement recorder terminal and the backup monitoring terminal.

[0044] The pre-operation preparation module is configured to perform pre-operation preparation and monitoring in place: after the operator arrives at the operation site with the law enforcement recorder terminal, completes the equipment status check and safety measures arrangement, the law enforcement recorder terminal starts audio and video acquisition, and the first-level monitoring end and the second-level monitoring end confirm that the monitoring is in place;

[0045] The operation and node verification module is configured to perform full-process operation and node verification: the operator performs the operation according to the typical operation ticket steps displayed on the law enforcement recorder terminal. After each preset operation node is completed, the law enforcement recorder terminal issues a reminder, the operator confirms the device status, the first-level monitoring terminal verifies and confirms on-site, and the confirmation information is synchronized to the second-level monitoring terminal and the data interaction server. If no confirmation is made, the next operation node cannot be entered.

[0046] The abnormal intervention module is configured for abnormal intervention and emergency handling: when the operation behavior does not conform to the typical operation ticket, the backup monitoring terminal issues an early warning, the law enforcement recorder terminal receives the early warning and suspends the operation process, and resumes the operation after the abnormality is eliminated and the monitoring terminal confirms it.

[0047] The inspection and data retention module is configured to perform post-operation inspection and data retention: After the operator completes all operation steps, the operator performs post-operation inspection according to the typical operation ticket. The first-level monitoring terminal and the second-level monitoring terminal check and confirm in turn. The law enforcement recorder terminal stops collecting data and uploads the audio and video data, operation records, and monitoring confirmation records to the data interaction server for classified storage.

[0048] The update and sedimentation processing module is configured to perform ticket database updates and case sedimentation: periodically analyze the operation records and exception records in the data interaction server, and update the typical operation ticket database with typical cases and optimized operation processes.

[0049] An electronic device includes at least one processor and a memory connected to the processor, wherein:

[0050] The memory is used to store computer programs or instructions;

[0051] The processor is used to execute the computer program or instructions to enable the electronic device to implement the monitoring and verification method as described in any of the preceding claims.

[0052] A computer-readable storage medium is applied to an electronic device, the storage medium carrying one or more computer programs that can be executed by the electronic device to enable the electronic device to perform the monitoring and verification method as described above.

[0053] As can be seen from the above technical solution, this application discloses a monitoring and confirmation system and its monitoring and confirmation method, device, electronic equipment, and storage medium. This system is used to monitor and confirm electrical operation nodes, specifically including a law enforcement recorder terminal, a typical operation ticket database management platform, a backup monitoring terminal, and a data interaction server. The law enforcement recorder terminal is deployed at the electrical operation site to collect and upload audio and video data of the entire electrical operation process; the typical operation ticket database management platform has built-in standardized typical operation tickets, used to match and retrieve corresponding typical operation tickets according to the on-site operation task; the backup monitoring terminal receives audio and video data from the law enforcement recorder terminal and operation ticket information issued by the typical operation ticket database management platform, and confirms the operation node; the data interaction server realizes information interaction, data storage, and instruction forwarding between the law enforcement recorder terminal, the typical operation ticket database management platform, and the backup monitoring terminal, and performs classified storage and traceable management of the operation data. In summary, the entire system relies on a unified architecture of standardized tickets, on-site audio and video acquisition, remote node verification, and full-process evidence storage and traceability to comprehensively manage all key nodes of electrical operations. Through pre-operational standard constraints, real-time monitoring and verification during operation, and post-operational traceability and control, it effectively identifies and prevents various non-standard operating behaviors, ultimately achieving the goal of effectively avoiding electrical misoperation. Attached Figure Description

[0054] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the 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.

[0055] Figure 1 This is a block diagram of a monitoring and verification system according to an embodiment of this application;

[0056] Figure 2 This is a flowchart of a monitoring and verification method according to an embodiment of this application;

[0057] Figure 3 This is a schematic diagram of node control for the operation of the high-voltage switchgear circuit breaker in an embodiment of this application;

[0058] Figure 4 This is a block diagram of a monitoring and verification device according to an embodiment of this application;

[0059] Figure 5 This is a block diagram of an electronic device according to an embodiment of this application. Detailed Implementation

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

[0061] Currently, there is no comprehensive collaborative prevention and control system that covers pre-operation preparation, full-process monitoring of operations, and post-operation traceability. This prevents the establishment of a structural link between operation ticket steps, audio / video recordings, and monitoring confirmation information, thus hindering the prevention of electrical misoperations through proactive process interruption. Therefore, this application provides a monitoring and confirmation scheme for electrical operation nodes to avoid electrical misoperations. This embodiment uses the tripping operation of a 10kV high-voltage switchgear circuit breaker in a thermal power plant as an example to illustrate the monitoring and confirmation system and method of this invention in detail.

[0062] Figure 1 This is a block diagram of a monitoring and verification system according to an embodiment of this application.

[0063] like Figure 1 As shown, the monitoring and confirmation system provided in this application is used to monitor and confirm electrical operation nodes. Specifically, it includes a law enforcement recorder terminal 100, a typical operation ticket management platform 200, a backup monitoring terminal 300, and a data interaction server 400. The components interact with each other and forward instructions through the data interaction server, forming an integrated prevention and control system encompassing operation guidance, process monitoring, multiple monitoring mechanisms, and data closure.

[0064] The law enforcement recorder terminal connects to the data interaction server via a communication link, uploading the collected audio and video data to the server. The typical operation ticket management platform distributes the generated standardized typical operation tickets to the law enforcement recorder terminal and the backup monitoring terminal through the data interaction server 400. The backup monitoring terminal includes a primary on-site monitoring terminal and a secondary remote monitoring terminal. Both receive audio and video streams and operation ticket information from the law enforcement recorder terminal through the data interaction server and send confirmation or warning commands to the law enforcement recorder terminal. The data interaction server acts as an information hub, realizing data forwarding, classified storage, and command routing between the terminals.

[0065] The law enforcement recorder terminal is deployed at the electrical operation site to collect and upload audio and video data of the entire electrical operation process. In one specific embodiment, the law enforcement recorder terminal adopts an industrial-grade portable recorder equipped with a high-definition camera, microphone, and positioning module. It has a built-in 4G / 5G communication module and can establish real-time data connections with a typical operation ticket management platform and backup monitoring terminals through a data interaction server. The display screen of the law enforcement recorder terminal is used to show the operator the current operation ticket steps, key control points, and prohibited operation requirements, while the camera is used to record the operator's operation behavior and equipment status throughout the process.

[0066] The law enforcement recorder terminal is also equipped with an operation node sensing module, which is linked to operation ticket nodes issued by the typical operation ticket database management platform. When an operation reaches a preset node, the operation node sensing module triggers the law enforcement recorder terminal to issue an audible and visual alert. The alert may include the current node name, operation content, and precautions. After completing the operation at this node, the operator must confirm it on the law enforcement recorder terminal, and this confirmation must be verified by the backup monitoring terminal before unlocking the next operation node, thereby achieving node-based mandatory control of the operation process.

[0067] The law enforcement recorder terminal is also equipped with a violation warning module, which is used to receive warning information from the backup monitoring terminal. When the anomaly identification module detects that the operation behavior does not match the typical operation ticket, the warning information is forwarded to the law enforcement recorder terminal through the data interaction server. The violation warning module issues a prompt to the operator in the form of sound and light, and at the same time triggers the pause mechanism to suspend the current operation process until the anomaly is eliminated and confirmed by the monitoring terminal.

[0068] The typical operation ticket management platform has built-in standardized typical operation tickets, used to match and retrieve corresponding typical operation tickets according to on-site operation tasks. In one specific embodiment of this application, the typical operation ticket management platform is deployed on the production management server of a thermal power plant, and has built-in standardized typical operation tickets covering different voltage levels such as 10kV, 35kV, and 220kV, and various operation types such as circuit breaker operation, disconnector operation, and power outage maintenance operation. Each typical operation ticket includes five modules: operation task, pre-operation preparation, operation steps, post-operation inspection, and hazard control. Each operation step is marked with key control points, operation specifications, and prohibited operation requirements. The platform supports personalized fine-tuning according to the actual on-site working conditions, such as adjusting specific operation parameters according to equipment model differences, and the fine-tuning records are automatically saved for traceability.

[0069] After receiving the operation task entry information, the typical operation ticket management platform retrieves the corresponding operation ticket template from the ticket database using a keyword matching algorithm. It then automatically generates a standardized typical operation ticket containing the specific equipment number, operation sequence, and hazard warnings for the operation. After review, the generated operation ticket is distributed to the law enforcement recorder terminal and backup monitoring terminal via the data interaction server, achieving multi-terminal synchronization of operation guidance information.

[0070] The backup monitoring terminal includes a primary monitoring terminal and a secondary monitoring terminal. These are used to receive audio and video data from the law enforcement recorder terminal and operation ticket information issued by the typical operation ticket database management platform, and to confirm the operation nodes. The primary monitoring terminal is deployed at the operation site, for example, using a tablet computer carried and used by on-site monitoring personnel. It can view the audio and video streams uploaded by the law enforcement recorder terminal and the current execution node of the operation ticket in real time, verify each step of the operator's operation on-site, and click confirm on the terminal after confirmation. The secondary monitoring terminal is deployed in the remote monitoring center, for example, using a central control room monitoring host, and is monitored by remote monitoring personnel. It also receives audio and video data from the law enforcement recorder terminal and operation ticket information, remotely monitors the on-site operation, and can perform further verification based on the confirmation from the primary monitoring terminal.

[0071] The backup monitoring terminal also includes an anomaly detection module for real-time analysis of the operation screen captured by the law enforcement recorder terminal. In one specific implementation, the anomaly detection module uses image recognition algorithms to analyze the device number, operation actions, and operator position in the operation screen in real time, comparing the analysis results with the target device number and preset standard actions recorded in the typical operation ticket. When it detects that the device number of the operation object is inconsistent with the target device number, the operation step sequence is incorrect, or the operation actions do not conform to the standard, the anomaly detection module immediately issues an early warning. The warning information is synchronized to the violation warning module of the law enforcement recorder terminal via the data interaction server, triggering audible and visual prompts and process suspension.

[0072] The data interaction server is used to realize information exchange, data storage, and instruction forwarding between law enforcement recorder terminals, the typical operation ticket database management platform, and backup monitoring terminals, and to classify, store, and manage the operation data traceably. Specifically, the data interaction server is deployed in the power plant's computer room, adopts a cloud storage model, and includes an edge computing and information interaction module, an encrypted storage and traceability module, and an offline cache synchronization module. The edge computing and information interaction module is responsible for real-time data forwarding and instruction routing between terminals; the encrypted storage and traceability module classifies and encrypts the collected audio and video data, operation ticket records, and monitoring confirmation records for storage, with a storage period of no less than three years, and supports retrieval by keywords such as operation time, operator, and operating equipment; the offline cache synchronization module temporarily caches the data to be uploaded by each terminal when the network is interrupted, and automatically synchronizes it to the server after the network is restored, ensuring data integrity.

[0073] As can be seen from the above technical solution, this embodiment provides a monitoring and confirmation system for monitoring and confirming electrical operation nodes. Specifically, it includes a law enforcement recorder terminal, a typical operation ticket management platform, a backup monitoring terminal, and a data interaction server. The law enforcement recorder terminal is deployed at the electrical operation site to collect and upload audio and video data of the entire electrical operation process. The typical operation ticket management platform has built-in standardized typical operation tickets, used to match and retrieve corresponding typical operation tickets according to the on-site operation task. The backup monitoring terminal receives audio and video data from the law enforcement recorder terminal and operation ticket information issued by the typical operation ticket management platform, and confirms the operation node. The data interaction server enables information exchange, data storage, and instruction forwarding between the law enforcement recorder terminal, the typical operation ticket management platform, and the backup monitoring terminal, and performs classified storage and traceable management of the operation data. In summary, the entire system relies on a unified architecture of standardized tickets, on-site audio and video acquisition, remote node verification, and full-process evidence storage and traceability to comprehensively manage all key nodes of electrical operations. Through pre-operational standard constraints, real-time monitoring and verification during operation, and post-operational traceability and control, it effectively identifies and prevents various non-standard operating behaviors, ultimately achieving the goal of effectively avoiding electrical misoperation.

[0074] Figure 2 This is a flowchart of a monitoring and verification method according to an embodiment of this application.

[0075] like Figure 2 As shown, the monitoring and confirmation method provided in this embodiment is applied to the aforementioned monitoring and confirmation system for monitoring and confirming electrical operation nodes. This application takes the tripping operation of a 10kV high-voltage switchgear circuit breaker in a thermal power plant as an example to describe the monitoring and confirmation method in detail. The method specifically includes the following steps:

[0076] S1. Perform operation tasks to input and match tickets in the database.

[0077] The key information of the on-site electrical operation task is entered into the typical operation ticket management platform. The platform automatically matches and generates the corresponding standardized typical operation ticket, which is then issued to the law enforcement recorder terminal and the backup monitoring terminal after review.

[0078] For example, the operator enters the operation task "#1 Unit 10kV Section A Cabinet Circuit Breaker Tripping" into the typical operation ticket management platform. The platform automatically matches the standardized typical operation ticket for 10kV high-voltage switchgear circuit breaker tripping based on the task keywords. The generated operation ticket includes modules such as operation task, pre-operation preparation, equipment number verification, circuit breaker monitoring and control device status check, pressing the tripping button, checking the circuit breaker tripping position indication, verifying the remote signaling status of the monitoring and control device, post-operation inspection, and hazard prevention. After being reviewed and approved by the shift leader, the operation ticket is distributed to the operator's law enforcement recorder terminal, the tablet computer at the on-site primary monitoring terminal, and the monitoring host at the secondary monitoring terminal in the central control room via the data interaction server.

[0079] S2. Ensure thorough preparation and monitoring before execution.

[0080] After the operator arrives at the operation site with the law enforcement recorder terminal, completes the equipment status check and safety measures setup, the law enforcement recorder terminal starts audio and video recording, and the primary and secondary monitoring terminals confirm that the monitoring is in place.

[0081] Specifically, the operator, carrying a body camera terminal, arrives at the 10kV high-voltage room, activates the camera's audio and video capture and positioning functions, and completes on-site safety measures, including setting up fencing and hanging warning signs. After verifying that the high-voltage switchgear equipment number matches the target equipment number recorded on the operation ticket, a first-level monitoring personnel arrives on-site and confirms monitoring is in place on a tablet computer, while a second-level monitoring personnel confirms remote monitoring is in place on the central control room's monitoring host. Upon receiving confirmation from both ends, the body camera terminal issues a prompt indicating that operation preparation is complete and operation can begin.

[0082] S3. Perform full-process operations and node verification.

[0083] Operators follow the typical operation ticket steps displayed on the law enforcement recorder terminal. After each preset operation node is completed, the law enforcement recorder terminal issues a reminder, and the operator confirms the equipment status. The first-level monitoring terminal verifies and confirms the status on-site, and the confirmation information is synchronized to the second-level monitoring terminal and the data interaction server. Without confirmation, the operator cannot proceed to the next operation node.

[0084] Specifically, upon completion of each preset operation node, the operation node sensing module triggers an audio-visual alert on the law enforcement recorder terminal, displaying the current node's content and an announcement of the next node. The operator scans the QR code or RFID tag on the high-voltage cabinet using the law enforcement recorder terminal to obtain the current equipment number and compares it with the target equipment number recorded on the operation ticket. If the comparison matches, the operator clicks "confirm." The first-level monitoring personnel verify the operation content and equipment status on-site and then click "confirm" on a tablet computer. The confirmation information is synchronized to the second-level monitoring host and server database via a data interaction server. If any step fails to confirm, the law enforcement recorder terminal locks the entry point for the next operation, preventing the operator from continuing with subsequent steps.

[0085] The key operational step is pressing the trip button. At this step, the law enforcement recorder automatically switches to close-up recording mode, with the high-definition camera focusing on the operator's hand movements and the circuit breaker control panel, recording this crucial action in high-definition close-up to clearly reconstruct the operational details for later review. This key step requires verification by both the operator and the primary monitoring personnel on-site. The primary monitoring personnel then perform a confirmation operation on a tablet computer before unlocking the device to proceed to the next step.

[0086] S4. Implement abnormal intervention and emergency handling.

[0087] When the operation does not conform to the typical operation ticket, the backup monitoring terminal issues an early warning. The law enforcement recorder terminal receives the early warning and suspends the operation process. The operation will resume after the anomaly is eliminated and the monitoring terminal confirms the error.

[0088] Specifically, if an operator mistakenly selects the adjacent cabinet B as the target device, and the equipment number of cabinet B obtained by the law enforcement recorder terminal does not match the target equipment number of cabinet A recorded on the operation ticket, the anomaly identification module, upon detecting the mismatch, immediately issues a red audible and visual warning simultaneously to the primary monitoring terminal, the secondary monitoring terminal, and the law enforcement recorder terminal via the data interaction server. The secondary monitoring personnel in the control room issue an intervention command to the operator via voice intercom, stating "Incorrect equipment operation." Upon receiving the warning, the violation warning module of the law enforcement recorder terminal displays an anomaly message on the screen and locks the operation process, suspending subsequent operations. After verifying and confirming that the correct target device is cabinet A, the operator reports the cause of the anomaly to the primary and secondary monitoring terminals. The primary and secondary monitoring personnel then confirm on their respective terminals that the anomaly has been resolved and send a recovery command to the law enforcement recorder terminal. Upon receiving the command, the law enforcement recorder terminal unlocks, and the operator continues with the subsequent operation process.

[0089] S5. Post-operation checks and data retention.

[0090] After the operator completes all the operation steps, the operation is checked according to the typical operation ticket. The first-level monitoring terminal and the second-level monitoring terminal check and confirm in turn. The law enforcement recorder terminal stops collecting data and uploads the audio and video data, operation record and monitoring confirmation record to the data interaction server for classified storage.

[0091] Specifically, after completing all the circuit breaker tripping steps, the operator performs a check according to the post-operation inspection module on the operation ticket: confirming that the circuit breaker in cabinet A is tripped, the monitoring and control device is functioning normally, and there are no abnormal alarms. The first-level monitoring personnel verify the information on-site and click "Operation Qualified" on the tablet computer. The second-level monitoring personnel verify the information remotely and click "Operation Qualified" on the monitoring host. The operator then disables the audio and video capture function of the law enforcement recorder terminal. The law enforcement recorder terminal uploads and categorizes the audio and video data recorded throughout the operation, the confirmation records of each operation node, and the verification records of the first and second-level monitoring personnel through the data interaction server, archiving them according to the directory structure "#1 Unit - 10kV Section - Operation Date," achieving full traceability.

[0092] If an attempted misoperation or abnormal event occurs during the operation, such as the misidentification of the device number in step 4, the data interaction server will include the relevant audio and video data of the abnormal event, the device number comparison record, and the abnormal handling process as typical cases in the typical operation ticket database. When matching 10kV circuit breaker tripping operation tickets subsequently, the typical operation ticket database management platform will automatically add a risk prevention prompt of "Double-person double-checking of device number + QR code confirmation" to the "Hazard Prevention" module of the operation ticket, and simultaneously push it to the law enforcement recorder terminal and the backup monitoring terminal, prompting the operator and monitoring personnel to pay close attention.

[0093] S6. Update the ticket database and consolidate case studies.

[0094] Regularly analyze the operation records and anomaly records in the data interaction server, and update the typical operation ticket database with typical cases and optimized operation processes.

[0095] Every month, the power plant's safety management department conducts statistical analysis of stored operation and anomaly records through a data exchange server to identify high-frequency anomaly types and operational weaknesses. The analysis conclusions of this "equipment number misidentification" anomaly case, the optimized verification process, and the newly added prevention and control requirements are incrementally updated and written into the corresponding 10kV circuit breaker tripping operation ticket template in the typical operation ticket database. The updated ticket database version is automatically synchronized to all terminals, achieving dynamic optimization and continuous iteration of the typical operation ticket database.

[0096] The above operations, in sequence, consist of six steps: task entry and ticket database matching, pre-operation preparation and monitoring, full-process operation and node verification, anomaly intervention and emergency handling, post-operation inspection and data retention, and ticket database update and case accumulation, forming a closed-loop management process. Guided by the law enforcement recorder terminal, operators sequentially perform operations such as verifying equipment number, checking device status, switching off, and confirming location. Node control during the operation is as follows: Figure 3 As shown.

[0097] Each node requires on-site verification and confirmation by the primary on-site monitoring terminal and remote review and confirmation by the secondary remote monitoring terminal. At key nodes, the law enforcement recorder terminal captures close-up shots of the operation process. The anomaly detection module analyzes the operation screen in real time, triggering an alert and pausing the process upon detecting an anomaly, thus establishing a closed-loop node control mechanism for operation, confirmation, monitoring, alerting, and recovery.

[0098] As can be seen from the above technical solution, this embodiment provides a monitoring and confirmation method. This method is applied to the aforementioned monitoring and confirmation system and specifically includes: inputting operation tasks and matching them with the ticket database; ensuring pre-operation preparation and monitoring; verifying the entire process and each node; intervening in abnormalities and handling emergencies; checking and storing data after operation; updating the ticket database and accumulating case studies. Through the above operations, this application achieves comprehensive control over all key nodes of electrical operations. By implementing pre-operation standard constraints, real-time monitoring and verification during operation, and post-operation traceability and control, it effectively identifies and prevents various non-standard operating behaviors, ultimately achieving the goal of effectively avoiding electrical misoperations.

[0099] Although the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous.

[0100] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0101] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer.

[0102] Figure 4 This is a block diagram of a monitoring and verification device according to an embodiment of this application.

[0103] like Figure 4 As shown, the monitoring and confirmation device provided in this embodiment is applied to the aforementioned monitoring and confirmation system for monitoring and confirming electrical operation nodes. Specifically, it includes a ticket entry matching module 10, a pre-operation preparation module 20, an operation and node verification module 30, an anomaly intervention module 40, an inspection and data retention module 50, and an update and data processing module 60. This application uses the tripping operation of a 10kV high-voltage switchgear circuit breaker in a thermal power plant as an example to describe in detail the functions of each working module of the monitoring and confirmation device.

[0104] The ticket entry and matching module is used to perform the operation task of entering and matching tickets in the database.

[0105] The key information of the on-site electrical operation task is entered into the typical operation ticket management platform. The platform automatically matches and generates the corresponding standardized typical operation ticket, which is then issued to the law enforcement recorder terminal and the backup monitoring terminal after review.

[0106] The pre-operation preparation module is used to ensure that pre-operation preparation and monitoring are in place.

[0107] After the operator arrives at the operation site with the law enforcement recorder terminal, completes the equipment status check and safety measures setup, the law enforcement recorder terminal starts audio and video recording, and the primary and secondary monitoring terminals confirm that the monitoring is in place.

[0108] The operation and node verification module is used to perform full-process operation and node verification.

[0109] Operators follow the typical operation ticket steps displayed on the law enforcement recorder terminal. After each preset operation node is completed, the law enforcement recorder terminal issues a reminder, and the operator confirms the equipment status. The first-level monitoring terminal verifies and confirms the status on-site, and the confirmation information is synchronized to the second-level monitoring terminal and the data interaction server. Without confirmation, the operator cannot proceed to the next operation node.

[0110] The abnormal intervention module is used to perform abnormal interventions and emergency handling.

[0111] When the operation does not conform to the typical operation ticket, the backup monitoring terminal issues an early warning. The law enforcement recorder terminal receives the early warning and suspends the operation process. The operation will resume after the anomaly is eliminated and the monitoring terminal confirms the error.

[0112] The inspection and data retention module is used for inspection and data retention after the operation is performed.

[0113] After the operator completes all the operation steps, the operation is checked according to the typical operation ticket. The first-level monitoring terminal and the second-level monitoring terminal check and confirm in turn. The law enforcement recorder terminal stops collecting data and uploads the audio and video data, operation record and monitoring confirmation record to the data interaction server for classified storage.

[0114] The update and sedimentation processing module is used to perform ticket database updates and case sedimentation.

[0115] Regularly analyze the operation records and anomaly records in the data interaction server, and update the typical operation ticket database with typical cases and optimized operation processes.

[0116] As can be seen from the above technical solution, this embodiment provides a monitoring and confirmation device. This device is applied to the aforementioned monitoring and confirmation system, specifically for performing tasks such as inputting operation tasks and matching ticket databases; ensuring pre-operation preparation and monitoring; verifying the entire operation process and key nodes; intervening in abnormalities and handling emergencies; checking and retaining data after operation; updating the ticket database and accumulating case studies. Through the above operations, this application achieves comprehensive control over all key nodes of electrical operations. By implementing pre-operation standard constraints, real-time monitoring and verification during operation, and post-operation traceability and control, it effectively identifies and prevents various non-standard operating behaviors, ultimately achieving the goal of effectively avoiding electrical misoperations.

[0117] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0118] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0119] Figure 5 This is a block diagram of an electronic device according to an embodiment of this application.

[0120] The following is for reference. Figure 5 This document illustrates a structural diagram suitable for implementing the electronic device in the embodiments of this disclosure. The terminal device in the embodiments of this disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. This electronic device is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this disclosure.

[0121] The electronic device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from an input device 506 into a random access memory (RAM) 503. The RAM also stores various programs and data required for the operation of the electronic device. The processing unit, ROM, and RAM are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0122] Typically, the following devices can be connected to the I / O interface: input devices including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows the electronic device to communicate wirelessly or wiredly with other devices to exchange data. Although electronic devices with various devices are shown in the figures, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0123] This application also provides an embodiment of a computer-readable storage medium.

[0124] The aforementioned computer-readable storage medium is used in electronic devices and carries one or more computer programs. When these programs are executed by the electronic device, they enable the device to perform tasks such as inputting and matching data with the ticket database; ensuring proper pre-operation preparation and monitoring; conducting full-process operation and node verification; intervening in abnormalities and handling emergencies; conducting post-operation checks and data retention; and updating the ticket database and accumulating case studies. Through these operations, this application achieves comprehensive control over all key nodes of electrical operations. By implementing pre-operation standard constraints, real-time monitoring and verification during operation, and post-operation traceability and control, it effectively identifies and prevents various non-standard operating behaviors, ultimately achieving the goal of effectively avoiding electrical misoperation.

[0125] It should be noted that the computer-readable medium described above in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0126] In this disclosure, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0127] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0128] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0129] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0130] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

Claims

1. A monitoring and confirmation system for monitoring and confirming electrical operation nodes, characterized in that, The monitoring and confirmation system includes The law enforcement recorder terminal is deployed at the electrical operation site to collect and upload audio and video data of the entire electrical operation process; The typical operation ticket library management platform has built-in standardized typical operation tickets, which are used to match and retrieve the corresponding typical operation tickets according to the on-site operation tasks. The backup monitoring terminal includes a primary monitoring terminal and a secondary monitoring terminal, used to receive audio and video data from the law enforcement recorder terminal and operation ticket information issued by the typical operation ticket library management platform, and to confirm the operation node; The data interaction server is used to realize information interaction, data storage and instruction forwarding between the law enforcement recorder terminal, the typical operation ticket management platform and the backup monitoring terminal, and to classify, store and manage the operation data in a traceable manner.

2. The monitoring and confirmation system as described in claim 1, characterized in that, The law enforcement recorder terminal is also equipped with an operation node sensing module, which is used to link with the operation ticket nodes issued by the typical operation ticket library management platform. When the operation reaches the preset node, an alert is issued, and the subsequent operation process can only continue after confirmation by the backup monitoring terminal.

3. The monitoring and confirmation system as described in claim 1, characterized in that, The typical operation ticket management platform includes five modules: operation task, pre-operation preparation, operation steps, post-operation inspection, and hazard prevention. Each operation step is marked with key control points, operation specifications, and prohibited operation requirements. It also supports personalized fine-tuning according to the actual working conditions on site, and the fine-tuning records are automatically saved.

4. The monitoring and confirmation system as described in claim 1, characterized in that, The backup monitoring terminal is also equipped with an anomaly recognition module, which is used to analyze the operation screen collected by the law enforcement recorder terminal in real time, identify the operation actions that do not match the typical operation ticket, and issue an early warning to the law enforcement recorder terminal.

5. The monitoring and confirmation system as described in claim 1, characterized in that, The law enforcement recorder terminal is also equipped with a violation warning module, which is used to receive warning information issued by the backup monitoring terminal and prompt the operator in the form of sound and light, while pausing the current operation process.

6. A monitoring and confirmation method, implemented based on the monitoring and confirmation system as described in any one of claims 1 to 5, characterized in that, Including the following steps: Operation task input and ticket matching: Key information of on-site electrical operation tasks is entered into the typical operation ticket management platform. The platform automatically matches and generates corresponding standardized typical operation tickets, which are then sent to the law enforcement recorder terminal and the backup monitoring terminal after review. Pre-operation preparation and monitoring: After the operator arrives at the operation site with the law enforcement recorder terminal, completes the equipment status check and safety measures arrangement, the law enforcement recorder terminal starts audio and video acquisition, and the primary monitoring end and the secondary monitoring end confirm that the monitoring is in place; Full-process operation and node verification: The operator performs the operation according to the typical operation ticket steps displayed on the law enforcement recorder terminal. After each preset operation node is completed, the law enforcement recorder terminal issues a reminder, the operator confirms the device status, the first-level monitoring terminal verifies and confirms on-site, and the confirmation information is synchronized to the second-level monitoring terminal and the data interaction server. Without confirmation, the next operation node cannot be entered. Abnormal Intervention and Emergency Handling: When the operation behavior is inconsistent with the typical operation ticket, the backup monitoring terminal issues an early warning, the law enforcement recorder terminal receives the early warning and suspends the operation process, and resumes operation after the abnormality is eliminated and the monitoring terminal confirms it; Post-operation inspection and data retention: After the operator completes all operation steps, the post-operation inspection is performed according to the typical operation ticket. The first-level monitoring terminal and the second-level monitoring terminal check and confirm in turn. The law enforcement recorder terminal stops collecting data and uploads the audio and video data, operation record, and monitoring confirmation record to the data interaction server for classified storage. Ticket database update and case study accumulation: Regularly analyze the operation records and anomaly records in the data interaction server, and update the typical operation ticket database with typical cases and optimized operation processes.

7. The monitoring and confirmation method as described in claim 6, characterized in that, The process of issuing the document after review includes the following steps: The shift supervisor or shift leader reviews the standardized typical operation tickets generated on the typical operation ticket management platform. After approval, the typical operation ticket management platform distributes the standardized typical operation ticket to the law enforcement recorder terminal and the backup monitoring terminal through the data interaction server.

8. The monitoring and confirmation method as described in claim 6, characterized in that, The preset operation nodes include at least one of the following: equipment power outage, voltage testing, grounding wire connection, disconnect switch operation, circuit breaker operation, and equipment power supply. Each key operation node requires confirmation from both the primary monitoring terminal and the operator, and the law enforcement recorder terminal captures close-up images of the operation process of the key operation nodes.

9. The monitoring and confirmation method as described in claim 6, characterized in that, In the entire process of operation and node verification, if an unsuccessful operation or an abnormal event occurs during the operation, the data interaction server will include the relevant data of the abnormal event as a typical case in the typical operation ticket database. When matching operation tickets in the future, the corresponding risk prevention and control prompts will be pushed to the law enforcement recorder terminal and the backup monitoring terminal simultaneously.

10. The monitoring and confirmation method as described in claim 6, characterized in that, In the entire process operation and node verification, the operator confirms the equipment status, including: The current device number can be obtained by scanning the device's QR code or RFID tag using the law enforcement recorder terminal; Compare the current device number with the target device number recorded in the typical operation ticket; If the comparison is consistent, the device status is confirmed; if the comparison is inconsistent, the abnormal intervention and emergency handling steps are triggered.

11. The monitoring and confirmation method as described in claim 6, characterized in that, The statement that the operation behavior is inconsistent with the typical operation ticket includes at least one of the following: The equipment number of the operation target does not match the target equipment number recorded in the typical operation ticket; The execution order of the operation steps is inconsistent with the order of steps recorded on the typical operation ticket; The operation action does not match the preset standard action corresponding to the typical operation ticket.

12. The monitoring and confirmation method as described in claim 6, characterized in that, The recovery operation after anomaly elimination and monitoring confirmation includes the following steps: After troubleshooting the anomaly, the operator reports the cause of the anomaly to the primary monitoring terminal and the secondary monitoring terminal. After the primary monitoring terminal and the secondary monitoring terminal confirm that the anomaly has been eliminated, they send a recovery command to the law enforcement recorder terminal. After receiving the recovery command, the law enforcement recorder terminal continues to execute subsequent operation procedures.

13. The monitoring and confirmation method according to claim 6, characterized in that, The law enforcement recorder terminal issues a reminder, including the following steps: Upon reaching a preset operation node, the law enforcement recorder terminal will announce the operation content, key control points, and prohibited operation requirements of the current operation node through voice broadcast and / or display on the screen.

14. A monitoring and confirmation device, implemented based on the monitoring and confirmation system as described in any one of claims 1 to 5, characterized in that, include: The ticket matching module is configured to perform operation task input and ticket matching: key information of on-site electrical operation tasks is entered into the typical operation ticket management platform, the platform automatically matches and generates corresponding standardized typical operation tickets, and after review, they are sent to the law enforcement recorder terminal and the backup monitoring terminal. The pre-operation preparation module is configured to perform pre-operation preparation and monitoring in place: after the operator arrives at the operation site with the law enforcement recorder terminal, completes the equipment status check and safety measures arrangement, the law enforcement recorder terminal starts audio and video acquisition, and the first-level monitoring end and the second-level monitoring end confirm that the monitoring is in place; The operation and node verification module is configured to perform full-process operation and node verification: the operator performs the operation according to the typical operation ticket steps displayed on the law enforcement recorder terminal. After each preset operation node is completed, the law enforcement recorder terminal issues a reminder, the operator confirms the device status, the first-level monitoring terminal verifies and confirms on-site, and the confirmation information is synchronized to the second-level monitoring terminal and the data interaction server. If no confirmation is made, the next operation node cannot be entered. The abnormal intervention module is configured for abnormal intervention and emergency handling: when the operation behavior does not conform to the typical operation ticket, the backup monitoring terminal issues an early warning, the law enforcement recorder terminal receives the early warning and suspends the operation process, and resumes the operation after the abnormality is eliminated and the monitoring terminal confirms it. The inspection and data retention module is configured to perform post-operation inspection and data retention: After the operator completes all operation steps, the operator performs post-operation inspection according to the typical operation ticket. The first-level monitoring terminal and the second-level monitoring terminal check and confirm in turn. The law enforcement recorder terminal stops collecting data and uploads the audio and video data, operation records, and monitoring confirmation records to the data interaction server for classified storage. The update and sedimentation processing module is configured to perform ticket database updates and case sedimentation: periodically analyze the operation records and exception records in the data interaction server, and update the typical operation ticket database with typical cases and optimized operation processes.

15. An electronic device, characterized in that, The electronic device includes at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs or instructions; The processor is used to execute the computer program or instructions to enable the electronic device to implement the monitoring and verification method as described in any one of claims 6 to 13.

16. A computer-readable storage medium for use in electronic devices, characterized in that, The storage medium carries one or more computer programs that can be executed by the electronic device, thereby enabling the electronic device to implement the monitoring and confirmation method as described in any one of claims 6 to 13.

Images