Electric power overhaul electronic operation ticket processing method and system

Abstract

The invention provides an electric power overhaul electronic operation ticket processing method and system. The problems that existing operation ticket operation is not standard and low in efficiency, and production safety cannot be guaranteed are solved. The method comprises the steps that after a typical operation template in the electric power overhaul process is imported, operation content is obtained, a corresponding operation work order is generated according to the specific operation content, operation steps are executed according to the operation work order passing multi-level auditing, meanwhile, ticket reading processing is conducted on the operation in the execution process, and an operation record file is generated after all the operations are completed. In addition, a practice module is also provided and is used for carrying out simulation practice on the typical operation. Through the standardized operation process, the operation efficiency in the electric power overhaul process is improved, and the production safety is guaranteed.

Description

Technical Field

[0001] The present invention relates to the field of electric power maintenance, and in particular to a method and system for processing an electric power maintenance electronic operation ticket. Background Art

[0002] At present, the grid dispatching tasks are heavy and the maintenance projects are large. It is difficult for dispatchers to meet the work requirements of various dispatching tasks at this stage. With the continuous application of electronic technologies such as mobile Internet to power networks, the implementation of network-based power operation ticket issuance business is promoted to improve the quality and efficiency of power dispatching and enhance the level of grid operation management.

[0003] In the power system, maintenance work is an indispensable part to ensure the safe operation and maintenance of power equipment. Traditional power maintenance work often relies on paper operation tickets. This method is not only inefficient and prone to errors, but also difficult to track and manage. With the development of information technology, electronic operation tickets for power maintenance have emerged. It not only improves work efficiency and reduces the possibility of human errors, but also provides possibilities for intelligent management and operation and maintenance of power systems. Traditionally, paper operation tickets are used in the power maintenance process. These operation tickets are used to record the power outage operation steps and related safety measures of power equipment. However, this traditional method has some obvious limitations: (1) Error-prone: manual filling is prone to typos or omissions of key information; (2) Low efficiency: manual transmission and review processes are time-consuming, affecting the progress of maintenance; (3) Inconvenient management: It is difficult to effectively archive and retrieve, which is not conducive to historical data analysis; (4) Poor security: paper documents are easily lost or damaged, and information security cannot be guaranteed. In summary, handwritten operation tickets are often affected by the different experience, knowledge level, experience and habits of the operator, and they also require high concentration. Not only is there a high possibility of issuing wrong invoices, but also the planning of operation tickets cannot be unified. Therefore, the method of building an operation ticket rule library based on manual records is not only inefficient but also prone to errors. In addition, the operation ticket rules cannot be updated quickly, and cannot effectively support the operation ticket business and meet the requirements of power grid business.

[0004] At the same time, during the power maintenance of the substation, there are also situations where the terminal equipment carried by the operator has poor network signal or poor network quality. These unstable communication situations can easily cause the system used for power maintenance to respond untimely. At this time, the user may click to send requests continuously in a short period of time, resulting in duplicate business data received by the system, which in turn causes the system to respond multiple times. Summary of the invention

[0005] The present invention provides a method and system for processing an electronic operation ticket for power maintenance, so as to solve the problems that the existing operation ticket operation is non-standard, inefficient, unable to ensure production safety and unable to cope with high-concurrency scenarios.

[0006] In a first aspect, the present invention provides a power maintenance electronic operation ticket processing system, which specifically includes the following modules:

[0007] Typical operation ticket template import module, used to import typical operation ticket templates;

[0008] An operation ticket generation module, used to obtain the operation content, and generate an operation work order according to the operation content and the typical operation ticket template; wherein the operation work order includes the operation ticket and necessary personnel information;

[0009] An approval module, used for approving the operation work order;

[0010] The vote counting module is used to count the current operation steps when executing the operation steps in the operation ticket;

[0011] The operation ticket printing module is used to generate a record file of the operation ticket operation after completing all the operation steps in the operation ticket.

[0012] Preferably, a power maintenance electronic operation ticket processing system further includes:

[0013] Simulation exercise module for practicing typical substation operations.

[0014] Preferably, in the typical operation ticket template import module, the typical operation ticket template includes typical operation ticket task information and typical operation ticket project information.

[0015] Preferably, the typical operation ticket task information includes task objectives, task units, substation names, task writers, task scheduling reviewers, task notes and operation task information.

[0016] More preferably, the operation task information includes the name of each sub-operation task, the name of the device used corresponding to each sub-operation task, and the associated operation items of each sub-operation task (in this application, the "operation item" represents a specific operation step).

[0017] Preferably, the typical operation ticket item information includes the operation item serial number, the operation item name, the equipment used, whether a picture is required, and the operation item remarks; wherein the associated operation items are represented by operation sequence numbers with a chronological order.

[0018] Preferably, in the operation ticket generation module, the operation content includes the task objective, the task unit and the substation name.

[0019] Preferably, the necessary personnel information includes necessary personnel information such as sender information, recipient information, operator information, guardian information, etc.

[0020] Preferably, in the process of generating an operation ticket by the operation ticket generation module, after obtaining the same operation content multiple times (in this application, the "multiple times" means at least twice) in succession, multiple (in this application, the "multiple" means at least two) operation ticket generation requests are generated, and the processing of multiple operation ticket generation requests specifically includes the following submodules:

[0021] The first operation ticket generation submodule is used to obtain multiple operation ticket generation requests (in this application, each request is assigned a thread for processing the request) and generate a Redis-based distributed lock;

[0022] The second operation ticket generation submodule is used to lock a thread T with the distributed lock. After the thread Ta is locked, the thread Ta queries the database to see whether the operation ticket corresponding to the request Ra (in this application, the "corresponding" means the operation ticket generated according to the request Ra) exists. If not, the operation ticket corresponding to the request Ra is stored in the database and the distributed lock is released; otherwise, other threads are directly executed and the distributed lock is released;

[0023] The third operation ticket generation submodule is used to repeatedly execute the second operation ticket generation submodule until all threads are executed.

[0024] Preferably, in the approval module, the approval includes three levels of approval: site level, company level, and owner level.

[0025] Preferably, the simulation exercise module specifically includes the following submodules:

[0026] The operation data acquisition submodule is used to obtain operation item information according to the typical operation template selected by the user;

[0027] The operation sequence verification submodule is used to match and verify the operation items after the user's sorting is completed with the operation items in the typical operation template, and complete the practice operation after the user's sorting is completely correct.

[0028] In a second aspect, the present invention further provides a method for processing an electronic operation ticket for power maintenance, which specifically comprises the following steps:

[0029] Step S1, importing a typical operation ticket template;

[0030] Step S2: obtaining the operation content, and generating an operation work order according to the operation content and the typical operation ticket template; wherein the operation work order includes the operation ticket and necessary personnel information;

[0031] Step S3: Approve the operation work order. If it is approved, the operation ticket execution phase is carried out. Otherwise, the operation ticket is regenerated.

[0032] Preferably, in step S1, the typical operation ticket template includes typical operation ticket task information and typical operation ticket project information.

[0033] Preferably, the typical operation ticket task information includes task objectives, task units, substation names, task writers, task scheduling reviewers, task notes and operation task information.

[0034] More preferably, the operation task information includes the name of each sub-operation task, the name of the device to be used corresponding to each sub-operation task, and the associated operation item of each sub-operation task.

[0035] Preferably, the typical operation ticket item information includes the operation item serial number, the operation item name, the equipment used, whether a picture is required, and the operation item remarks; wherein the associated operation items are represented by operation sequence numbers with a chronological order.

[0036] Preferably, in step S2, the operation content includes the task objective, task unit and substation name; the necessary personnel information includes the necessary personnel information such as sender information, recipient information, operator information, guardian information, etc.

[0037] Preferably, in step S2, in the process of generating the operation worksheet, after obtaining the same operation content multiple times in succession, multiple operation worksheet generation requests are generated, and the processing of the multiple operation worksheet generation requests specifically includes the following steps:

[0038] Step S201: Obtain multiple operation work order generation requests and generate a Redis-based distributed lock;

[0039] Step S202: Lock a thread T with the distributed lock. After thread Ta is locked, thread Ta queries the database to see whether the operation work order corresponding to request Ra exists. If not, the operation work order corresponding to request Ra is stored in the database and the distributed lock is released. Otherwise, other threads are directly executed and the distributed lock is released.

[0040] Step 203: Repeat step S202 until all threads are executed.

[0041] Preferably, in step S3, the approval includes three levels of approval: site level, company level, and owner level.

[0042] In a third aspect, the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a method for processing an electronic operation ticket for electric power maintenance as described in any one of the second aspects of the present application.

[0043] In a fourth aspect, the present invention further provides an electronic device, comprising: a memory storing a computer program; and a processor communicatively connected to the memory, for executing a method for processing an electronic operation ticket for electric power maintenance as described in any one of the second aspects of the present application when the computer program is called.

[0044] Compared with the prior art, the present invention has the following obvious outstanding substantive features and significant advantages:

[0045] The present invention provides a method and system for processing electronic operation tickets for power maintenance, which solves the problems of existing operation tickets being non-standard, inefficient, unable to guarantee production safety, and unable to cope with high-concurrency scenarios. After importing a typical operation template in the power maintenance process, the content of the operation is obtained, and a corresponding operation work order is generated according to the specific operation content. The operation steps are executed according to the operation work order that has passed multiple levels of review. At the same time, the operations in the execution process are processed, and an operation record file is generated after all operations are completed. In addition, the scenario of sending multiple identical requests in succession is processed to ensure normal operation in high-concurrency scenarios. Through the above-mentioned standardized operation process, the operation efficiency in the power maintenance process is improved and the safety of production is guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The accompanying drawings, which constitute part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention. In the accompanying drawings:

[0047] Figure 1 It is a structural schematic diagram of an electric power maintenance electronic operation ticket processing system according to a preferred embodiment of the present invention.

[0048] Figure 2 It is a schematic diagram of the processing flow of multiple consecutive identical requests in an electric power maintenance electronic operation ticket processing system in a preferred embodiment of the present invention.

[0049] Figure 3 It is a schematic diagram of the processing flow of multiple consecutive identical requests in an electric power maintenance electronic operation ticket processing system in a preferred embodiment of the present invention.

[0050] Figure 4 It is a flow chart of a method for processing an electronic operation ticket for electric power maintenance according to a preferred embodiment of the present invention. DETAILED DESCRIPTION

[0051] The present invention provides a method and system for processing an electronic operation ticket for power maintenance. In order to make the purpose, technical solution and effect of the present invention clearer and more specific, the present invention is further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0052] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0053] Embodiment 1:

[0054] like Figure 1-Figure 3 As shown, the electric power maintenance electronic operation ticket processing system described in this embodiment specifically includes the following modules:

[0055] Typical operation ticket template import module, used to import typical operation ticket templates.

[0056] Among them, the typical operation ticket template includes typical operation ticket task information and typical operation ticket project information; as shown in Table 1-1 and Table 1-2, the typical operation ticket task information includes task objectives, task units, substation names, task writers, task scheduling reviewers, task notes and operation task information.

[0057] Table 1-1 Typical operation ticket task information table

[0058]

[0059] Table 1-2 Typical operation ticket task information table (continued from Table 1-1)

[0060]

[0061] As shown in Table 1-2, the operation task information includes the name of each sub-operation task, the name of the device used corresponding to each sub-operation task, and the associated operation item of each sub-operation task.

[0062] Optionally, the typical operation ticket item information includes the operation item serial number, the operation item name, the equipment used, whether a picture is required, and the operation item remarks; wherein the associated operation items are represented by operation sequence numbers with a chronological order, as shown in Table 2.

[0063] Table 2 Typical operation project information table

[0064]

[0065] In summary, when the substation numbered 09 of the 35kV user station of the D1C-108#~116# plot of the external transmission performs the operation of stopping the 10kV one / two section sectionalizing switch, the names of the operation tasks are respectively 10kV one / two section sectionalizing from operation to hot standby, 10kV one / two section sectionalizing from hot standby to cold standby and 10kV one / two section sectionalizing from cold standby to switch maintenance. When performing the operation task of changing the 10kV one / two section sectionalizing from operation to hot standby, the equipment to be operated is the 10kV one / two section sectionalizing equipment, and the specific operation items are 1,2, that is, the first step is to open the 10kV one / two section sectionalizing switch; the second step is to check that the 10kV one / two section sectionalizing switch is in the open position. At this time, the 10kV one / two section sectionalizing is changed from operation to hot standby. And so on, until all operation tasks and their associated operation items are completed, and finally the operation of stopping the 10 kV first / second section sectional switch of the substation numbered 09 of the 35 kV user station of the D1C-108#~116# block is realized.

[0066] The operation ticket generation module is used to obtain the operation content and generate an operation work order according to the operation content and the typical operation ticket template; wherein the operation work order includes the operation ticket and necessary personnel information; wherein the necessary personnel information includes necessary personnel information such as the sender information, the recipient information, the operator information, and the guardian information.

[0067] Among them, in the process of generating the operation ticket by the operation ticket generation module, after obtaining the same operation content multiple times in succession, multiple operation ticket generation requests are generated. The processing of multiple operation ticket generation requests specifically includes the following submodules:

[0068] The first operation ticket generation submodule is used to obtain multiple operation ticket generation requests and generate a Redis-based distributed lock.

[0069] The second operation ticket generation submodule is used to lock a thread T with the distributed lock. After the thread Ta is locked, the thread Ta queries the database to see whether the operation ticket corresponding to the request Ra exists. If not, the operation ticket corresponding to the request Ra is stored in the database and the distributed lock is released; otherwise, other threads are directly executed and the distributed lock is released.

[0070] The third operation ticket generation submodule is used to repeatedly execute the second operation ticket generation submodule until all threads are executed.

[0071] In the above process, if Figure 2-Figure 3 As shown, since a Redis distributed lock is set, only one thread can process the request corresponding to the thread at a time ( Figure 2 , Figure 3 Request 1 and Request 2 shown in the figure are the same request. For the convenience of distinction, they are named Request 1 and Request 2 for processing. Other threads need to finish processing the thread, generate the required operation ticket, store the operation ticket in the database and release the Redis distributed lock before they can process the request. In addition, for different threads with the same request, in the subsequent execution process, since the previously generated operation ticket is retrieved in the database, it directly returns to other threads. Therefore, when the user generates an operation ticket, if the same request is sent multiple times, only one request is executed, that is, only one operation ticket is generated for each operation request.

[0072] The approval module is used to approve the operation work order; wherein the approval includes three levels of approval: site level, company level, and owner level.

[0073] The vote counting module is used to count the current operation steps when executing the operation steps in the operation ticket.

[0074] The operation ticket printing module is used to generate a record file of the operation ticket operation after completing all the operation steps in the operation ticket.

[0075] Optionally, the electric power maintenance electronic operation ticket processing system described in this embodiment further includes: a simulation practice module for practicing typical substation operations; wherein the operation content includes task objectives, task units and substation names.

[0076] The simulation exercise module specifically includes the following submodules:

[0077] The operation data acquisition submodule is used to obtain operation item information according to the typical operation template selected by the user.

[0078] The operation sequence verification submodule is used to match and verify the operation items after the user's sorting is completed with the operation items in the typical operation template, and complete the practice operation after the user's sorting is completely correct.

[0079] The following is a general flow of the system described in this embodiment during operation, and the steps are as follows:

[0080] Step 1. Import typical operation ticket template

[0081] When the system described in this embodiment is running, it is first necessary to enter the site information and equipment information involved into the system before importing the typical operation template of power maintenance into the system. In the process of importing the typical operation template into the system, the system automatically matches the information according to the site information, equipment information, etc., organizes the typical operation task information and the operation item information under the task in a tree structure and stores it in the database. In the specific implementation of the system, after the typical operation template is imported into the system, the system administrator will also review the typical operation template. After confirmation, subsequent operations can be carried out; if there are any modifications to the approved typical operation template, the status will be updated to the unreviewed status, and the administrator needs to submit it for review again before the work order can be dispatched normally.

[0082] Step 2: Create and review the work order

[0083] Click Add to initiate the invoicing process, fill in the work order content, sender, recipient, operator, guardian and other necessary information, then submit the work order and enter the approval process. Among them, the operator and guardian need to be assigned corresponding roles in the system management first, and they cannot be the same person in one operation ticket. The operator and guardian are optional when adding a work order. If they are not determined, they can also be specified in the subsequent multi-level approval process of the work order, as long as the designation is completed before the final approval is completed; the operation supports fuzzy query, and after selection, there will be a prompt to inform that the details of the operation appear at the bottom of the page for viewing.

[0084] There are three levels of approval: 1) On-site level: On-site person in charge (station manager); 2) Company level: (full-time operation); 3) Owner (equipment manager / supervisor). The persons in charge at each level log in to the system in turn to approve the work order. After the work order is reviewed, the operator and guardian will receive a task reminder.

[0085] Step 3: Mobile voting execution

[0086] The operator and guardian log in to the mobile terminal, click on the work order to be executed, and start the face comparison. After the match is successful, the system officially enters the vote counting stage. The system brings out the task steps and prominently displays the current step. It supports voice broadcast. The operator and guardian take photos of the operation site as required and gradually complete all steps. Finally, the on-site person in charge (for the determined task unit, the on-site person in charge is fixed, so there is no need to fill in the on-site person in charge when filling out the work order) operates and confirms the execution status. The operation ticket can be printed online or exported as a PDF file for offline archiving.

[0087] Step 4. Simulation practice

[0088] Click Add to start the simulation exercise, select a typical operation template, obtain the task and operation item data, left-click the operation item and drag it to sort. After all the operation items under the operation task are sorted, click Finish, and the system will automatically match the submitted operation order for verification. Finally, after all the sorting is correct, the submission of this exercise can be completed.

[0089] Embodiment 2:

[0090] like Figure 4 As shown, the method for processing an electric maintenance electronic operation ticket described in this embodiment specifically includes the following methods:

[0091] Step S1, importing a typical operation ticket template; wherein the typical operation ticket template includes typical operation ticket task information and typical operation ticket project information.

[0092] The typical operation ticket task information includes task objectives, task units, substation names, task writers, task scheduling reviewers, task notes and operation task information.

[0093] The operation task information includes the name of each sub-operation task, the name of the device used corresponding to each sub-operation task, and the associated operation item of each sub-operation task.

[0094] The typical operation ticket item information includes the operation item serial number, the operation item name, the equipment used, whether a picture is required, and the operation item remarks; wherein the associated operation items are represented by operation sequence numbers with a chronological order.

[0095] Step S2, obtain the operation content, and generate an operation work order according to the operation content and the typical operation ticket template; wherein the operation work order includes the operation ticket and necessary personnel information; wherein the operation content includes the task objective, task unit and substation name; the necessary personnel information includes the necessary personnel information such as the sender information, the recipient information, the operator information, the guardian information, etc.

[0096] In the process of generating an operation ticket, when the same operation content is obtained multiple times in succession, multiple operation ticket generation requests are generated. The processing of multiple operation ticket generation requests specifically includes the following steps:

[0097] Step S201: Obtain multiple operation work order generation requests and generate a Redis-based distributed lock.

[0098] Step S202: Lock a thread T with the distributed lock. After the thread Ta is locked, the thread Ta queries the database to see whether the operation work order corresponding to the request Ra exists. If not, the operation work order corresponding to the request Ra is stored in the database and the distributed lock is released; otherwise, other threads are directly executed and the distributed lock is released.

[0099] Step 203: Repeat step S202 until all threads are executed.

[0100] Step S3: Approve the operation work order. If the approval is qualified, the operation ticket execution stage is carried out. Otherwise, the operation ticket is regenerated. The approval includes three levels of approval: site level, company level, and owner level.

[0101] The specific embodiments of the present invention are described in detail above, but they are only examples, and the present invention is not limited to the specific embodiments described above. For those skilled in the art, any equivalent modifications and substitutions made to the present invention are also within the scope of the present invention. Therefore, the equalization changes and modifications made without departing from the spirit and scope of the present invention should be included in the scope of the present invention.

Claims

1. A method for processing an electronic operation ticket for power maintenance, characterized in that: The specific steps include: Step S1, importing a typical operation ticket template; Step S2: obtaining the operation content, and generating an operation work order according to the operation content and the typical operation ticket template; wherein the operation work order includes the operation ticket and necessary personnel information; Step S3: Approve the operation work order. If the approval is qualified, the operation ticket execution phase is carried out. Otherwise, the operation ticket is regenerated; Wherein, in step S1, the typical operation ticket template includes typical operation ticket task information and typical operation ticket project information.

2. A method for processing an electronic operation ticket for power maintenance according to claim 1, characterized in that: The typical operation ticket task information includes the task objective, task unit, substation name, task writer, task scheduling reviewer, task notes and operation task information; the typical operation ticket item information includes the operation item serial number, operation item name, equipment used, whether pictures are required and operation item notes; wherein the associated operation items are represented by operation sequence numbers with a chronological order.

3. A method for processing an electronic operation ticket for power maintenance according to claim 2, characterized in that: The operation task information includes the name of each sub-operation task, the name of the device corresponding to each sub-operation task, and the associated operation item of each sub-operation task.

4. A method for processing an electronic operation ticket for power maintenance according to claim 1, characterized in that: In step S2, the operation content includes the task target, task unit and substation name; the necessary personnel information includes the necessary personnel information of the sender, the recipient, the operator and the guardian.

5. A method for processing an electronic operation ticket for power maintenance according to claim 1, characterized in that: In step S2, in the process of generating the operation worksheet, after obtaining the same operation content multiple times in succession, multiple operation worksheet generation requests are generated. The processing of the multiple operation worksheet generation requests specifically includes the following steps: Step S201: Obtain multiple operation work order generation requests and generate a Redis-based distributed lock; Step S202: The distributed lock is used to lock a thread T. After the thread Ta is locked, the thread Ta queries the database to see whether the operation work order corresponding to the request Ra exists. If not, the operation work order corresponding to the request Ra is stored in the database and the distributed lock is released. Otherwise, other threads are directly executed and the distributed lock is released. Step 203: Repeat step S202 until all threads are executed.

6. A method for processing an electric power maintenance electronic operation ticket according to claim 1, characterized in that: In step S3, the approval includes three levels of approval: site level, company level, and owner level.

7. A device for processing electronic operation tickets for power maintenance, characterized in that: The modules include: Typical operation ticket template import module, used to import typical operation ticket templates; An operation ticket generation module, used to obtain the operation content, and generate an operation work order according to the operation content and the typical operation ticket template; wherein the operation work order includes the operation ticket and necessary personnel information; An approval module, used for approving the operation work order; The vote counting module is used to count the current operation steps when executing the operation steps in the operation ticket; The operation ticket printing module is used to generate a record file of the operation ticket operation after completing all the operation steps in the operation ticket.

8. The device for processing an electronic operation ticket for power maintenance according to claim 8, characterized in that: Also includes: Simulation exercise module for practicing typical substation operations.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements a method for processing an electronic operation ticket for power maintenance as described in any one of claims 1-7.

10. An electronic device, characterized in that: It includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements a method for processing an electronic operation ticket for electric power maintenance as described in any one of claims 1 to 7.

Images