Auxiliary ticketing methods, devices, computer equipment, and storage media

Abstract

This application relates to an auxiliary ticketing method, apparatus, computer device, storage medium, and computer program product. The method includes: acquiring an operation ticket type dataset and an operation ticket basic information set; generating a new operation ticket task and entering basic information using the operation ticket type dataset and the operation ticket basic information set to obtain an initial operation ticket set; matching an operation ticket template based on the operation ticket type dataset and the initial operation ticket set; and entering operation steps based on the operation ticket template to generate an operation ticket set. This method can free up manpower and improve work efficiency.

Description

Technical Field

[0001] This application relates to the field of power system technology, and in particular to an auxiliary ticketing method, apparatus, computer equipment, storage medium and computer program product. Background Technology

[0002] Each day, the first-floor work team needs to prepare operation tickets for the next day's power outage plan one day in advance. On average, each power outage plan operation ticket requires between ten and forty tickets. Manually filling out the operation tickets is time-consuming and labor-intensive. When the workload is large, it can take three to four hours to fill out the operation tickets. This process involves a large amount of manual work and is repetitive and standardized, resulting in high labor costs and making it difficult to guarantee work efficiency and operational accuracy. Summary of the Invention

[0003] Therefore, it is necessary to provide an auxiliary ticketing method, device, computer equipment, computer-readable storage medium, and computer program product that can liberate manpower and improve work efficiency in response to the above-mentioned technical problems.

[0004] Firstly, this application provides an auxiliary ticketing method, including:

[0005] Obtain the dataset of operation ticket types and the basic information set of operation tickets;

[0006] New operation ticket tasks are generated by using the operation ticket type dataset and the operation ticket basic information set, and basic information is entered to obtain the initial operation ticket set;

[0007] Match operation ticket templates based on the operation ticket type dataset and the initial operation ticket set;

[0008] The operation steps are entered based on the operation ticket template to generate an operation ticket set.

[0009] In one embodiment, the process of generating a new operation ticket task and entering basic information using an operation ticket type dataset and an operation ticket basic information set, to obtain an initial operation ticket set includes:

[0010] When the operation ticket type dataset is cable type, the basic information to be entered includes the address of the disconnecting device, the number of the disconnecting device, the start status and the end status.

[0011] When the operation ticket type dataset is a mother row class, the basic information to be entered includes the serial number and the corresponding operation task;

[0012] When the operation ticket type dataset is an overhead type, the basic information to be entered includes the operation type, the switch address, and the switch number.

[0013] When the operation ticket type dataset is of the low-pressure type, the corresponding content format is obtained according to the operation type;

[0014] When the operation ticket type dataset is classified as low-pressure container splitting and merging, the basic information to be entered includes the serial number and the corresponding operation task.

[0015] In one embodiment, when the operation ticket type dataset is of the overhead type, the basic information entered, including operation type, switch address, and switch number, also includes:

[0016] When the operation ticket type dataset is a drop-out circuit breaker, obtain the corresponding content format according to the operation type.

[0017] In one embodiment, matching an operation ticket template based on the operation ticket type dataset and the initial operation ticket set includes:

[0018] When the operation ticket type dataset is cable type and busbar type, the template file path is determined based on the equipment type, and the operation ticket template is determined based on the start state and end state;

[0019] When the operation ticket type dataset is of the overhead type, the operation ticket template is determined based on the equipment type;

[0020] When the operation ticket type dataset is divided into low-pressure class and low-pressure whole cabinet separation and combination class, the operation ticket template is determined based on the operation type.

[0021] In one embodiment, when the operation ticket type dataset is of the overhead type, determining the operation ticket template based on the equipment type further includes:

[0022] When the operation ticket type dataset is a drop-out circuit breaker, the operation ticket template is determined based on the operation type.

[0023] In one embodiment, after inputting operation steps based on the operation ticket template and generating an operation ticket set, the method further includes:

[0024] Save the operation ticket set and send it back to the robotic process automation management platform.

[0025] Secondly, this application also provides an auxiliary ticketing device, comprising:

[0026] The module for obtaining the operation ticket type dataset and the operation ticket basic information set is used to obtain the operation ticket type dataset and the operation ticket basic information set.

[0027] The basic information entry module is used to generate new operation ticket tasks and enter basic information from the operation ticket type dataset and the operation ticket basic information set to obtain the initial operation ticket set;

[0028] The operation ticket template matching module is used to match operation ticket templates based on the operation ticket type dataset and the initial operation ticket set;

[0029] The operation ticket set generation module is used to generate operation ticket sets based on the operation steps entered in the operation ticket template.

[0030] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0031] Obtain the dataset of operation ticket types and the basic information set of operation tickets;

[0032] New operation ticket tasks are generated by using the operation ticket type dataset and the operation ticket basic information set, and basic information is entered to obtain the initial operation ticket set;

[0033] Match operation ticket templates based on the operation ticket type dataset and the initial operation ticket set;

[0034] The operation steps are entered based on the operation ticket template to generate an operation ticket set.

[0035] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0036] Obtain the dataset of operation ticket types and the basic information set of operation tickets;

[0037] New operation ticket tasks are generated by using the operation ticket type dataset and the operation ticket basic information set, and basic information is entered to obtain the initial operation ticket set;

[0038] Match operation ticket templates based on the operation ticket type dataset and the initial operation ticket set;

[0039] The operation steps are entered based on the operation ticket template to generate an operation ticket set.

[0040] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0041] Obtain the dataset of operation ticket types and the basic information set of operation tickets;

[0042] New operation ticket tasks are generated by using the operation ticket type dataset and the operation ticket basic information set, and basic information is entered to obtain the initial operation ticket set;

[0043] Match operation ticket templates based on the operation ticket type dataset and the initial operation ticket set;

[0044] The operation steps are entered based on the operation ticket template to generate an operation ticket set.

[0045] The aforementioned auxiliary ticketing method, device, computer equipment, storage medium, and computer program products acquire an operation ticket type dataset and an operation ticket basic information set; generate new operation ticket tasks and input basic information using the operation ticket type dataset and operation ticket basic information set to obtain an initial operation ticket set; match operation ticket templates based on the operation ticket type dataset and initial operation ticket set; and input operation steps based on the operation ticket templates to generate an operation ticket set. Only the logical sequence of switching operations within the entire power outage plan needs to be considered. By utilizing RPA (Robotic Process Automation) robots to complete the repetitive task of adding and filling in operation tickets, manpower can be freed up, and work efficiency improved. Attached Figure Description

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

[0047] Figure 1 This is a schematic diagram of the core capabilities of an RPA robot in one embodiment;

[0048] Figure 2 This is a schematic diagram illustrating the process of the central control robot dynamically allocating tasks and execution resources in one embodiment;

[0049] Figure 3 This is a schematic diagram of the structure for implementing multiple deployment types of RPA robots in one embodiment;

[0050] Figure 4 This is a schematic diagram illustrating the capabilities of an RPA robot in a conventional technique, as shown in one embodiment.

[0051] Figure 5 This is a flowchart illustrating an auxiliary ticketing method in one embodiment;

[0052] Figure 6 This is a schematic diagram of the interface for adding a distribution network operation ticket in one embodiment;

[0053] Figures 7(a), 7(b), and 7(c) are schematic diagrams of the interface for filling in the new distribution network operation ticket in one embodiment;

[0054] Figures 8(a), 8(b), and 8(c) are schematic diagrams of the interface for entering operation steps in one embodiment;

[0055] Figures 9(a) and 9(b) are schematic diagrams of the interface for entering operation steps according to a template in one embodiment;

[0056] Figure 10 This is a schematic diagram of the interface for saving operation tickets in one embodiment;

[0057] Figure 11 This is a schematic diagram of the interface for writing content when the operation ticket type dataset is cable, as shown in one embodiment.

[0058] Figure 12 This is a schematic diagram of the interface for writing content when the operation ticket type dataset is an empty class in one embodiment;

[0059] Figure 13 This is a schematic diagram of the interface for entering basic information of RPA operation tickets in one embodiment, where the operation ticket type dataset is cable type and busbar type;

[0060] Figure 14 This is a schematic diagram illustrating the path of the template file selected in one embodiment when "whether it is a communication cabinet", "whether it is a circuit breaker cabinet" and "whether it is a remote control cabinet" are both "yes";

[0061] Figure 15 This is a schematic diagram illustrating the path to the template file when "whether it is a communication cabinet" is "yes", "whether it is a circuit breaker cabinet" is "yes" and "whether it is a remote control cabinet" is "no" in one embodiment;

[0062] Figure 16 This is a schematic diagram illustrating the path of the template file selected in one embodiment when "whether it is a communication cabinet" is "yes", "whether it is a circuit breaker cabinet" is "no" and "whether it is a remote control cabinet" is "yes".

[0063] Figure 17 This is a schematic diagram illustrating the path to the template file when "whether it is a communication cabinet" is "yes", "whether it is a circuit breaker cabinet" is "no", and "whether it is a remote control cabinet" is "no" in one embodiment.

[0064] Figure 18 This is a schematic diagram illustrating the path of the template file selected in one embodiment when "whether it is a communication cabinet" is "no", "whether it is a circuit breaker cabinet" is "yes" and "whether it is a remote control cabinet" is "yes";

[0065] Figure 19 This is a schematic diagram illustrating the path to the template file when "whether it is a communication cabinet" is "no", "whether it is a circuit breaker cabinet" is "yes" and "whether it is a remote control cabinet" is "no" in one embodiment;

[0066] Figure 20 This is a schematic diagram illustrating the path to the template file when "whether it is a communication cabinet" is "no", "whether it is a circuit breaker cabinet" is "no", and "whether it is a remote control cabinet" is "yes" in one embodiment.

[0067] Figure 21This is a schematic diagram illustrating the path to the template file when "whether it is a communication cabinet", "whether it is a circuit breaker cabinet", and "whether it is a remote control cabinet" are both "no" in one embodiment.

[0068] Figure 22 This is a schematic diagram of the interface for selecting a template based on the current row content of the attachment when the operation ticket type dataset is an empty class in one embodiment;

[0069] Figure 23 This is a schematic diagram of the interface for an RPA robot to determine the filling of a stop operation ticket in one embodiment;

[0070] Figure 24 This is a flowchart illustrating the product requirements for an auxiliary ticketing tool in one embodiment;

[0071] Figure 25 This is a flowchart illustrating an auxiliary ticketing method in another embodiment;

[0072] Figure 26 This is a schematic diagram of an auxiliary ticketing device in one embodiment;

[0073] Figure 27 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0074] YWRPA (Robotic Process Automation) robots are primarily designed to automate repetitive, manual, and repetitive business operations. By automating these processes, robots reduce human intervention, lower labor costs, and improve efficiency and accuracy. For cross-system operations, they enable non-embedded processing, allowing for smooth data flow and ensuring consistency and accuracy. Steadily advancing lean management through system informatization continuously deepens value creation in business processes, reduces the burden on frontline employees, and provides strong technical support.

[0075] YWRPA robots can simulate human behavior, reducing labor costs; perform batch automatic processing, reducing errors and improving efficiency; recognize images and documents, improving production efficiency; and perform configurable process operation, enabling 24 / 7 uninterrupted operation.

[0076] With the popularization of RPA robots, YWRPA, through extensive technical review and scenario implementation, and combined with current application status, has summarized and sorted out 15 core capabilities in 4 categories for RPA, including system operation, auxiliary function, offline capability, and system service. The service list of system operation includes information entry, information extraction, work order processing, simulated key operation, and attachment upload and download. The service list of auxiliary function includes result notification (voice), statistical analysis and process monitoring, anomaly warning and information notification. The service list of offline capability includes Word operation, Excel operation, text operation, text validation, and document comparison. The service list of system service includes log tracking and permission management.

[0077] In traditional technologies, given the high market demand for automation and the large user base, maximizing efficiency with limited YWPRA hardware and software resources has become a primary concern. Through continuous exploration and verification, such as... Figure 1 As shown, the core capabilities of RPA robots have been illustrated using queue and resource pool technologies within an enterprise-level robot architecture. Traditional RPA robots possess task queue and execution resource management functions, providing a management module based on a unified task queue and execution resource pool, such as... Figure 2 As shown, the execution control robot dynamically allocates tasks and execution resources. The steps include user-initiated tasks, queuing tasks, allocating resources, locking resources, executing the process, and releasing resources. This fully utilizes the 24 / 7 availability of execution resources to maximize resource utilization; it can implement multiple deployment types, such as... Figure 3 As shown, the offline zone supports local deployment of external network processes, the core service zone supports unified deployment of public business servers, and the personalized service zone supports authorized deployment for grassroots training and development sharing; for example Figure 4 As shown, the capabilities of RPA robots in traditional technologies include supporting OCR (Optical Character Recognition) recognition and information push.

[0078] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0079] In one embodiment, such as Figure 5 As shown, an auxiliary ticketing method is provided. This embodiment illustrates the method applied to a terminal. It is understood that this method can also be applied to a server, or to a system including both a terminal and a server, and implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0080] Step 502: Obtain the operation ticket type dataset and the operation ticket basic information set.

[0081] Specifically, the robot receives the basic information entry form for the operation ticket sent by the business.

[0082] Step 504: Generate new operation ticket tasks and enter basic information using the operation ticket type dataset and operation ticket basic information set to obtain the initial operation ticket set.

[0083] For example, the robot adds operation tickets to multiple sheet types of operation ticket information in the operation ticket basic information entry table, that is, it generates new operation ticket tasks through the operation ticket type dataset and the operation ticket basic information set.

[0084] Specifically, the robot opens and logs into the power grid management platform, enters its account and password, clicks the "Login" button, selects "All Applications" after logging in, and then clicks "Power Grid Management Platform Asset Domain".

[0085] Furthermore, such as Figure 6 As shown in Figures 7(a), 7(b), and 7(c), adding a new distribution network operation ticket involves entering the "Distribution Network Operation Ticket" module by default and clicking the "Add" button. The filling rules include: in the "Type" column, selecting "Operation performed according to dispatch order" or "Operation performed according to the unit's task" under "Command Source" in Attachment 1 of the system; selecting "No" under "Handwritten ticket supplement"; in the "Location" column, after clicking identifier 702, entering the content in the search box of the pop-up window according to "Address Search Content" in Attachment 1 of the system, selecting the search result, and clicking the "OK" button when the currently searched device appears in the selected devices on the right. Attachment 1 contains the operation ticket type dataset and the basic information set of the operation ticket.

[0086] Step 506: Match operation ticket templates based on the operation ticket type dataset and the initial operation ticket set.

[0087] Specifically, there are currently five types of operation tickets: cable, busbar, overhead, low voltage (single switch, ground wire, generator car, knife switch), and low voltage cabinet switching. The overhead type also includes drop-out fuses.

[0088] Step 508: Enter the operation steps based on the operation ticket template to generate an operation ticket set.

[0089] For example, the operation steps are entered according to the template, that is, the operation steps are entered based on the operation ticket template.

[0090] Specifically, when the operation ticket type is cable, overhead, low voltage (single switch, ground wire, generator car, disconnector), or drop-out fuse, open the corresponding template and enter the operation steps one by one into the page. For example, as shown in Figures 8(a), 8(b), and 8(c), if the current template has N operation steps, click "+", enter N-1 in the "Insert Rows Forward" field, and press Enter to successfully add the row number. Further, enter the operation steps according to the template, where the content in 《》 corresponds to the current row field in System Attachment 1. Example operation step 1 is shown in Figure 9(a), so enter operation step 1 in the system page as shown in Figure 9(b).

[0091] Specifically, when the operation ticket type is busbar type or low-voltage cabinet combination type, the operation steps corresponding to the template for the same "serial number" and the same "location search content" are appended, and then entered into the page one by one. For example, if the current template has N operation steps and there are M rows of data with the same "serial number" and the same "location search content", then the final number of operation steps entered is M*N. The operation steps and screenshots are the same as those for the cable type mentioned above.

[0092] Furthermore, the input of special operation steps is explained. When the operation ticket type is cable or busbar, if the content of the "Listing Start Status" / "Listing End Status" column in the basic information is "None", then the operation steps that have "Listing Start Status" or "Listing End Status" in the operation ticket template selected in the current information row will not be entered.

[0093] For example, such as Figure 10 As shown, after entering the operation steps, click the "Save" button.

[0094] The aforementioned auxiliary ticketing method involves acquiring an operation ticket type dataset and an operation ticket basic information set; generating a new operation ticket task and entering basic information using the operation ticket type dataset and the operation ticket basic information set to obtain an initial operation ticket set; matching operation ticket templates based on the operation ticket type dataset and the initial operation ticket set; and entering operation steps based on the operation ticket template to generate an operation ticket set. The operation ticket addition and filling steps are implemented using RPA, including entering basic information, matching the corresponding operation ticket template based on the basic information of the operation ticket, filling in the operation steps of the operation ticket, and saving. In this way, users only need to focus on the logical sequence of the switching operations in the entire power outage plan, while the RPA robot will complete the repetitive operation ticket addition and filling work, freeing up manpower for the power supply bureau, improving work efficiency, and achieving one-click ticketing, automatic ticketing, unified templates, and a single table for comprehensive operation ticket management.

[0095] In an exemplary embodiment, a new operation ticket task is generated and basic information is entered through an operation ticket type dataset and an operation ticket basic information set. The initial operation ticket set is obtained by: If the operation ticket type dataset is for cables, the basic information entered includes the address of the switching device, the switching device number, the start status, and the end status; if the operation ticket type dataset is for busbars, the basic information entered includes the sequence number and the corresponding operation task; if the operation ticket type dataset is for overhead lines, the basic information entered includes the operation type, the disconnector address, and the disconnector number; if the operation ticket type dataset is for low-voltage systems, the corresponding content format is obtained according to the operation type; if the operation ticket type dataset is for low-voltage switchgear assembly / disassembly systems, the basic information entered includes the sequence number and the corresponding operation task.

[0096] For example, select the corresponding filling rule based on the current operation ticket addition type.

[0097] Specifically, when the operation ticket type dataset is cable type, the format for writing the content is: change the "Switch Address" and "Switch Number" switch cable side from "Live Indicator Start State" to "Live Indicator End State". For example... Figure 11 As shown, the example is "the switch of the 812 cable at the 01 end of the 10kV F28 Moumouyuan Phase III Comprehensive Building to the #3 transformer of this building is changed from operation to maintenance".

[0098] Specifically, when the operation ticket type dataset is a parent row type, the content written is the content of the "operation task" field corresponding to the current "serial number".

[0099] Specifically, when the operation ticket type dataset is of the overhead type, the format for writing the content is "Operation Type", "Knife Switch Address", "Knife Switch Number", "Knife Switch", such as... Figure 12 As shown, the example is "Pull open the 10kV F24 dry #04 pole 04T01 disconnect switch".

[0100] Specifically, when the operation ticket type dataset is low voltage (single switch, ground wire, generator car, disconnector), the corresponding content format is obtained according to the "operation type".

[0101] For example, when the generator truck is connected, the corresponding content format is: "Transformer Name" 0.4kV "Switch Name" low-voltage outgoing line downstream section is switched to low-voltage generator truck power supply; when the generator truck is disconnected, the corresponding content format is: "Transformer Name" 0.4kV "Switch Name" low-voltage outgoing line downstream section is disconnected from low-voltage generator truck power supply; when a ground wire is installed, the corresponding content format is: "Install one set of ground wires on the load side of the "Switch Name" outgoing line of the "Transformer Name" low-voltage switchgear; when the ground wire is removed, the corresponding content format is: "Remove the "Transformer Name" low-voltage switchgear." One set of low-voltage grounding wires on the load side of the "Switch Name" outgoing line; When the switch is closed, the corresponding content format is: Switch name on the load side of the "Transformer Name" low-voltage cabinet is switched from hot standby to operation; When the switch is open, the corresponding content format is: Switch name on the load side of the "Transformer Name" low-voltage cabinet is switched from operation to hot standby; When the disconnect switch is closed, the corresponding content format is: Switch name on the load side of the "Transformer Name" and "Switch Name" is switched from hot standby to operation; When the disconnect switch is disconnected, the corresponding content format is: Switch name on the load side of the "Transformer Name" and "Switch Name" is switched from operation to hot standby.

[0102] Specifically, when the operation ticket type dataset is a low-pressure container splitting and merging category, the content written is the content of the "operation task" field corresponding to the current "serial number".

[0103] In this embodiment, an initial set of operation tickets is generated based on the different types of operation tickets and their basic information to complete the initial operation ticket filling, which facilitates matching the corresponding templates for operation tickets and improves the efficiency of operation ticket filling.

[0104] In an exemplary embodiment, when the operation ticket type dataset is of the overhead type, entering basic information including operation type, switch address and switch number also includes: when the operation ticket type dataset is of the drop-out fuse, obtaining the corresponding content format according to the operation type.

[0105] Specifically, when the operation ticket type dataset is a drop-out fuse, the corresponding content format is obtained according to the "operation type"; when the drop-out fuse is closed, the corresponding content format is: closed "drop-out fuse address" "drop-out fuse number" drop-out fuse; when the drop-out fuse is opened, the corresponding content format is: opened "drop-out fuse address" "drop-out fuse number" drop-out fuse.

[0106] In this embodiment, the case of drop-out fuses is described, which more comprehensively considers the different situations that may be included in the operation ticket type.

[0107] In an exemplary embodiment, matching an operation ticket template based on an operation ticket type dataset and an initial operation ticket set includes: when the operation ticket type dataset is cable type and busbar type, determining the template file path based on the equipment type, and determining the operation ticket template based on the start state and end state; when the operation ticket type dataset is overhead type, determining the operation ticket template based on the equipment type; when the operation ticket type dataset is low voltage type and low voltage cabinet combination type, determining the operation ticket template based on the operation type.

[0108] For example, the rules for selecting a template based on the type of operation ticket include:

[0109] When the operation ticket type is cable or busbar, there are currently three types of equipment: switch cabinet, tie cabinet, and circuit breaker cabinet. The system selects the template based on the current line content of Appendix 1 "Cable" Sheet, as follows: Figure 13 As shown. Specifically, as Figure 14 As shown, when "Is it a connecting cabinet?", "Is it a circuit breaker cabinet?", and "Is it a remote control cabinet?" are all "Yes", select the template file path as "Typical Operation Ticket Template\Cable\Connecting Cabinet\Circuit Breaker Cabinet\Remote Control Cabinet", and select the operation ticket template according to the "Starting Status" and "Ending Status"; for example... Figure 15 As shown, when "Is it a connecting cabinet?" is "Yes", "Is it a circuit breaker cabinet?" is "Yes", and "Is it a remote control cabinet?" is "No", select the template file path as "Typical Operation Ticket Template\Cable\Connecting Cabinet\Circuit Breaker Cabinet\Non-Remote Control", and select the operation ticket template according to the "Starting Status" and "Ending Status"; for example... Figure 16 As shown, when "Is it a connecting cabinet?" is "Yes", "Is it a circuit breaker cabinet?" is "No", and "Is it a remote control cabinet?" is "Yes", select the template file path as "Typical Operation Ticket Template\Cable\Connecting Cabinet\Non-Remote Control Cabinet", and select the operation ticket template according to the "Starting Status" and "Ending Status"; for example... Figure 17 As shown, when "Is it a connecting cabinet?" is "Yes", "Is it a circuit breaker cabinet?" is "No", and "Is it a remote control cabinet?" is "No", select the template file path as "Typical Operation Ticket Template\Cable\Connecting Cabinet\Non-Remote Control Cabinet", and select the operation ticket template according to the "Starting Status" and "Ending Status"; for example... Figure 18 As shown, when "Is it a communication cabinet?" is "No", "Is it a circuit breaker cabinet?" is "Yes", and "Is it a remote control cabinet?" is "Yes", select the template file path as "Typical Operation Ticket Template\Cable\Circuit Breaker Cabinet\Remote Control Cabinet", and select the operation ticket template according to the "Starting Status" and "Ending Status"; for example... Figure 19As shown, when "Whether it is a communication cabinet" is "No", "Whether it is a circuit breaker cabinet" is "Yes", and "Whether it is a remote control cabinet" is "No", select the template file path as "Typical Operation Ticket Template\Cable\Circuit Breaker Cabinet\Non-Remote Control", and select the operation ticket template according to the "Starting Status" and "Ending Status"; for example... Figure 20 As shown, when "Is it a contact cabinet?", "Is it a circuit breaker cabinet?", "Is it a remote control cabinet?", and "Is it a remote control cabinet?", the template file path is selected as "Typical Operation Ticket Template\Cable\Switchgear\Remote Control Cabinet", and the operation ticket template is selected according to the "Starting State" and "Ending State"; for example... Figure 21 As shown, when "whether it is a communication cabinet" is "no", "whether it is a circuit breaker cabinet" is "no", and "whether it is a remote control cabinet" is "no", select the template file path as "typical operation ticket template\cable\switch cabinet\non-remote control", and select the operation ticket template according to the "starting state" and "ending state".

[0110] When the operation ticket type is overhead, there are currently three types of equipment: overhead on both sides, overhead on one side with cable on the other, and overhead on one side with pole-mounted switch on the other. Select the template according to the current line content of Appendix 1, "Overhead" Sheet, as follows: Figure 22 As shown. Specifically, when "Both sides overhead" is "Yes" and "Operation type" is "Open", the template file path is "Operation Ticket Typical Template\Overhead\Both sides overhead\Open.xlsx"; when "Both sides overhead" is "Yes" and "Operation type" is "Close", the template file path is "Operation Ticket Typical Template\Overhead\Both sides overhead\Close.xlsx"; when "One side overhead, one side cable" is "Yes" and "Operation type" is "Open", the template file path is "Operation Ticket Typical Template\Overhead\One side overhead, one side cable\Open.xlsx"; when "One side overhead, one side cable" is "Yes ... If "Operation Type" is "Close" and "Operation Ticket Typical Template\Overhead\One Side Overhead, One Side Cable\Close.xlsx" is selected; if "One Side Overhead, One Side Pole Switch" is "Yes" and "Operation Type" is "Open", the template file path is selected as "Operation Ticket Typical Template\Overhead\One Side Overhead, One Side Pole Switch\Open.xlsx"; if "One Side Overhead, One Side Pole Switch" is "Yes" and "Operation Type" is "Close", the template file path is selected as "Operation Ticket Typical Template\Overhead\One Side Overhead, One Side Pole Switch\Close.xlsx".

[0111] When the operation ticket type is low voltage (single switch, ground wire, generator cart, disconnector) or low voltage cabinet switching, select the template file path as "Operation Ticket Typical Template\Low Voltage\Operation Type".xlsx according to the "Operation Type" content of the current line of the corresponding Sheet; optionally, if the "Operation Type" content is "Generator Cart Access", then select the template file path as "Operation Ticket Typical Template\Low Voltage\Generator Cart Access.xlsx".

[0112] In this embodiment, corresponding operation ticket templates are matched for different operation ticket types, which helps to further improve the efficiency of filling out operation tickets.

[0113] In an exemplary embodiment, when the operation ticket type dataset is of the overhead type, determining the operation ticket template based on the equipment type further includes: when the operation ticket type dataset is of the drop-out fuse type, determining the operation ticket template based on the operation type.

[0114] Specifically, when the operation ticket type dataset is drop-out fuse, the template file path is selected as "Operation Ticket Typical Template\Drop-out Fuse\"Operation Type" Drop-out Fuse.xlsx" based on the "Operation Type" content of the current line of the corresponding sheet. Optionally, if the "Operation Type" content is "Close", the template file path is "Operation Ticket Typical Template\Drop-out Fuse\Close Drop-out Fuse.xlsx".

[0115] Furthermore, such as Figure 23 As shown, if the operation ticket template contains the following parentheses, which contain 14 empty characters, including one Chinese character that occupies 2 characters, the RPA robot will determine to stop filling out the operation ticket.

[0116] In this embodiment, the inclusion of drop-out fuses is beneficial for further improving the practicality of automatic operation ticket filling and reducing labor costs.

[0117] In an exemplary embodiment, after inputting operation steps based on the operation ticket template and generating an operation ticket set, the method further includes: saving the operation ticket set and sending the operation ticket set back to the robotic process automation management platform.

[0118] For example, the operation ticket set results are returned, including adding "Status" and "Remarks" columns to each sheet in Appendix 1 as a result file. The "Status" column is filled with either "Success" or "Failure," and the "Remarks" column is left blank for "Success" and includes the reason for the process error for "Failure." Furthermore, the result file is named "Operation Ticket Filling Log yyyyMMdd," where yyyyMMdd is the current date. Further, after execution, the result file is uploaded back to the RPA automation management platform for business personnel to download and view.

[0119] In this embodiment, the operation ticket set results are returned and transmitted back to the robotic process automation management platform, which can be downloaded and viewed by business personnel, making their work more convenient.

[0120] In one embodiment, such as Figure 24 As shown, the product requirements for the auxiliary ticketing tool include logging into the asset domain of the power grid management platform, adding a new operation ticket (basic information entry), matching typical operation ticket templates, and adding a new operation ticket (operation steps entry).

[0121] In one embodiment, such as Figure 25 As shown, an auxiliary ticketing method is provided, including:

[0122] Step 2502: Obtain the operation ticket type dataset and the operation ticket basic information set.

[0123] Step 2504: If the operation ticket type dataset is cable type, enter the basic information including the address of the switching device, the number of the switching device, the start status, and the end status.

[0124] Step 2506: If the operation ticket type dataset is of the mother row type, enter the basic information including the serial number and the corresponding operation task.

[0125] Step 2508: If the operation ticket type dataset is of the overhead type, enter the basic information including operation type, switch address and switch number; if the operation ticket type dataset is of the drop-out fuse type, obtain the corresponding content format according to the operation type.

[0126] Step 2510: If the operation ticket type dataset is of the low-pressure type, obtain the corresponding content format according to the operation type.

[0127] Step 2512: If the operation ticket type dataset is of the low-pressure full container splitting and merging type, enter the basic information including the serial number and the corresponding operation task.

[0128] Step 2514: If the operation ticket type dataset is cable type and busbar type, determine the template file path based on the equipment type, and determine the operation ticket template based on the start state and end state.

[0129] Step 2516: If the operation ticket type dataset is of the overhead type, determine the operation ticket template based on the equipment type; if the operation ticket type dataset is of the drop-out fuse type, determine the operation ticket template based on the operation type.

[0130] Step 2518: When the operation ticket type dataset is divided into low-pressure type and low-pressure whole cabinet separation and combination type, determine the operation ticket template based on the operation type.

[0131] Step 2520: Enter the operation steps based on the operation ticket template to generate an operation ticket set.

[0132] Step 2522: Save the operation ticket set and send it back to the Robotic Process Automation Management Platform.

[0133] In this embodiment, the robot logs into the power grid management platform's asset domain name and enters basic information for each operation ticket. Each operation ticket is matched with and imported from a corresponding operation ticket template based on basic information such as the operation task, cabinet number, and whether it has remote control functions. Modifying the equipment name completes the filling process, achieving one-click, automatic, standardized, and comprehensive operation ticket issuance. For example, what would have been 4 minutes manually for each project can now be completed in 2 minutes by the robot, saving 84 hours.

[0134] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0135] Based on the same inventive concept, this application also provides an auxiliary ticketing device for implementing the auxiliary ticketing method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more auxiliary ticketing device embodiments provided below can be found in the limitations of the auxiliary ticketing method described above, and will not be repeated here.

[0136] In one exemplary embodiment, such as Figure 26 As shown, an auxiliary ticketing device is provided, including: an operation ticket type dataset and operation ticket basic information set acquisition module 2602, a basic information input module 2604, an operation ticket template matching module 2606, and an operation ticket set generation module 2608, wherein:

[0137] The module 2602 for acquiring operation ticket type dataset and operation ticket basic information set is used to acquire operation ticket type dataset and operation ticket basic information set.

[0138] The basic information entry module 2604 is used to generate new operation ticket tasks and enter basic information through the operation ticket type dataset and the operation ticket basic information set, and obtain the initial operation ticket set.

[0139] The operation ticket template matching module 2606 is used to match operation ticket templates based on the operation ticket type dataset and the initial operation ticket set.

[0140] The operation ticket set generation module 2608 is used to generate operation ticket sets based on the operation steps entered in the operation ticket template.

[0141] In one embodiment, the basic information entry module 2604 includes:

[0142] The basic information entry module for cable types is used to enter basic information, including the address of the switching device, the number of the switching device, the start status, and the end status, when the operation ticket type dataset is cable type.

[0143] The Mother Row Basic Information Input Module is used to input basic information, including the serial number and the corresponding operation task, when the operation ticket type dataset is Mother Row.

[0144] The overhead type basic information input module is used to input basic information, including operation type, switch address and switch number, when the operation ticket type dataset is overhead type.

[0145] The low-voltage basic information entry module is used to obtain the corresponding content format according to the operation type when the operation ticket type dataset is low-voltage.

[0146] The Low-Voltage Cabinet Combination and Disbinding Basic Information Input Module is used to input basic information, including the serial number and the corresponding operation task, when the operation ticket type dataset is of the Low-Voltage Cabinet Combination and Disbinding category.

[0147] In one embodiment, the overhead basic information input module further includes:

[0148] The basic information input module for drop-out fuses is used to obtain the corresponding content format according to the operation type when the operation ticket type dataset is drop-out fuses.

[0149] In one embodiment, the operation ticket template matching module 2606 includes:

[0150] The cable and busbar type template matching module is used to determine the template file path based on the equipment type and the operation ticket template based on the start and end states when the operation ticket type dataset is cable and busbar type.

[0151] The overhead type template matching module is used to determine the operation ticket template based on the equipment type when the operation ticket type dataset is of the overhead type.

[0152] The low-voltage and low-voltage cabinet separation / combination template matching module is used to determine the operation ticket template based on the operation type when the operation ticket type dataset is divided into low-voltage and low-voltage cabinet separation / combination categories.

[0153] In one embodiment, the overhead template matching module further includes:

[0154] When the operation ticket type dataset is a drop-out circuit breaker, the operation ticket template is determined based on the operation type.

[0155] In one embodiment, the device further includes:

[0156] The operation ticket set saving module is used to save the operation ticket set and send it back to the robotic process automation management platform.

[0157] Each module in the aforementioned ticketing auxiliary device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0158] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 27 As shown, the computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements an auxiliary ticketing method. The display unit is used to form a visually visible image and can be a display screen, projection device, or virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0159] Those skilled in the art will understand that Figure 27 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0160] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0161] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0162] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0163] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0164] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0165] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0166] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for assisting in ticket issuance, characterized in that, The method includes: Obtain the dataset of operation ticket types and the basic information set of operation tickets; When the operation ticket type dataset is cable type, the basic information to be entered includes the address of the disconnecting device, the number of the disconnecting device, the start status, and the end status; When the operation ticket type dataset is a mother row class, the basic information to be entered includes the serial number and the corresponding operation task; When the operation ticket type dataset is an overhead type, the basic information entered includes the operation type, the switch address, and the switch number. When the operation ticket type dataset is a drop-out fuse, the corresponding content format is obtained according to the operation type. When the operation ticket type dataset is of the low-pressure type, the corresponding content format is obtained according to the operation type; When the operation ticket type dataset is of the low-voltage cabinet splitting and merging type, the basic information to be entered includes the serial number and the corresponding operation task; When the operation ticket type dataset is cable type and busbar type, the template file path is determined based on the equipment type, and the operation ticket template is determined based on the start state and end state; In the case where the operation ticket type dataset is of the overhead type, the operation ticket template is determined based on the equipment type; When the operation ticket type dataset is divided into low-voltage category and low-voltage cabinet separation and combination category, the operation ticket template is determined based on the operation type; Based on the operation ticket template, the operation steps are entered to generate an operation ticket set.

2. The method according to claim 1, characterized in that, In the case where the operation ticket type dataset is an empty class, determining the operation ticket template based on the equipment type also includes: When the operation ticket type dataset is a drop-out fuse, the operation ticket template is determined based on the operation type.

3. The method according to claim 1, characterized in that, After the step of inputting the operation ticket based on the operation ticket template and generating the operation ticket set, the method further includes: Save the operation ticket set and send it back to the robotic process automation management platform.

4. An auxiliary ticket issuing device, characterized in that, The device includes: The module for obtaining the operation ticket type dataset and the operation ticket basic information set is used to obtain the operation ticket type dataset and the operation ticket basic information set. The basic information input module is used to input basic information, including the address of the switching device, the number of the switching device, the start status, and the end status, when the operation ticket type dataset is for cables; when the operation ticket type dataset is for busbars, it inputs basic information including the serial number and the corresponding operation task; when the operation ticket type dataset is for overhead lines, it inputs basic information including the operation type, the switch address, and the switch number; wherein, when the operation ticket type dataset is for drop-out fuses, the corresponding content format is obtained according to the operation type; when the operation ticket type dataset is for low-voltage systems, the corresponding content format is obtained according to the operation type; and when the operation ticket type dataset is for low-voltage switchgear switching, it inputs basic information including the serial number and the corresponding operation task. The operation ticket template matching module is used to determine the template file path based on the equipment type and the operation ticket template based on the start and end states when the operation ticket type dataset is cable type and busbar type; to determine the operation ticket template based on the equipment type when the operation ticket type dataset is overhead type; and to determine the operation ticket template based on the operation type when the operation ticket type dataset is low voltage type and low voltage cabinet combination type. The operation ticket set generation module is used to generate an operation ticket set based on the operation ticket template by inputting operation steps.

5. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 3.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 3.

7. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 3.

Images