A method and system for generating power supply and utilization contracts based on robotic process automation

Abstract

The present invention discloses a method and system for generating power supply and use contracts based on robotic process automation, and belongs to the field of automatic contract generation. The present invention uses a contract text generation method that integrates unified regulation and personalized information in multiple content forms, and introduces a task insurance mechanism, a key element waiting mechanism, and a restart and recovery mechanism to ensure that the automatic contract generation process can proceed smoothly when encountering a failed task. The present invention can quickly generate various effective business contracts in the application scenario of the State Grid, greatly reducing manual operations and improving office efficiency.

Description

Technical Field

[0001] The present invention relates to the field of automatic contract generation, and in particular to a method and system for generating power supply and utilization contracts based on robotic process automation. Background Art

[0002] In the daily business of State Grid, there are a lot of businesses that need to collect data, draft corresponding contracts, and sign with customers. At the same time, as the business progresses, customers may have scenarios where they need to re-sign, re-sign, modify, or renew contracts. The general process of drafting a contract is the same, and the workload lies in filling in the data of different customers in the corresponding positions of the contract.

[0003] Based on the overall goal of "digital transformation and upgrading and reducing the burden on grassroots organizations", State Grid introduced RPA technology to solve tasks such as contract generation that involve a large amount of repetitive work. Summary of the invention

[0004] The present invention provides the following technical solutions to solve the above problems:

[0005] A method for generating a power supply and utilization contract based on robotic process automation comprises the following steps:

[0006] 1) Obtaining tasks

[0007] The RPA robot goes to the corresponding platform, automatically generates corresponding tasks based on the process information, uses the process number and / or user number as an identifier, and obtains the corresponding contract template from the contract template library;

[0008] 2) Task filtering

[0009] For the task generated in step 1), verify whether the task or contract already exists through the task insurance mechanism. If it does, ignore the task. Otherwise, execute step 3);

[0010] 3) Data Capture

[0011] The RPA robot automatically captures the information required to be filled in the contract template obtained in step 1) and ensures the smooth progress of the data capture process through the key element waiting mechanism, restart and recovery mechanism;

[0012] 4) Contract Generation

[0013] Fill the data captured in step 3) into the contract template to generate the target contract.

[0014] A power supply and use contract generation system based on robotic process automation, which consists of a control end and several execution ends, the control end includes a task acquisition module, a task acquisition module, a task allocation module, a task query module and a data display module; each execution end includes a data acquisition module, a data processing module, a data filling module, a data storage module and a task feedback module;

[0015] The task acquisition module is used to control the RPA robot to go to the corresponding platform, automatically generate the corresponding system centralized query task or manually built task according to the process information, use the process number and / or user number as an identifier, and obtain the corresponding contract template from the contract template library; the system centralized query task refers to the RPA robot logging into the platform query interface to simulate manual operation, configure the company name, business type and its corresponding voltage level, process link, and acceptance time range parameters, and centrally query the in-transit work order process number as the task source; determine whether there is a contract generation demand for the new installation or capacity expansion link of the high-voltage process corresponding to the in-transit work order process number. If so, generate the corresponding task and obtain the corresponding contract template from the contract template library; the manually built task refers to the RPA robot obtaining the contract demand according to manual instructions, establishing the process number and user number, generating the corresponding task, and obtaining the corresponding contract template from the contract template library;

[0016] The task filtering module is used to verify whether the task or contract already exists according to the task generated by the task acquisition module through the task insurance mechanism. If so, the task is ignored; otherwise, the task is sent to the task allocation module;

[0017] The task allocation module is used to receive tasks sent by the task filtering module, and the controller allocates the tasks to be executed to different execution terminals for processing through a load balancing strategy;

[0018] The task query module is used to query the generated tasks;

[0019] The data display module is used to display query results, as well as contract generation history statistics and execution status visualization reports of execution-end tasks;

[0020] The data acquisition module is used to automatically capture the information required to be filled in the contract template, and ensure the smooth progress of the data capture process through the key element waiting mechanism, restart and recovery mechanism;

[0021] A data processing module is used to pre-process the captured data variables, wherein the data variables include contract number, receiving transformer statistics, multiple transformer descriptions, substation information, power factor standard, transformer loss, line loss, metering point system table, reactive power consumption, contract validity period, property boundary point picture, and personalized design content;

[0022] A data filling module is used to map data variables to preset contract variable filling positions of the contract template to generate a target contract;

[0023] The data storage module is used to save the results of data collection, as well as the process owner and process number information;

[0024] The task feedback module is used to feed back the task execution results to the control end, including whether the contract is generated successfully and the storage location.

[0025] The beneficial effects of the present invention are as follows: compared with general existing methods, the present invention can quickly obtain the contract generation tasks required for each process stage in various application scenarios of the State Grid, and generate various valid business contracts, which greatly reduces manual operations and improves office efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 It is a flowchart of a method for generating a power supply and utilization contract based on robotic process automation according to an embodiment of the present invention;

[0027] Figure 2 It is a structural schematic diagram of a power supply and utilization contract generation system based on robotic process automation shown in an embodiment of the present invention. DETAILED DESCRIPTION

[0028] Example embodiments will be described more fully below with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0029] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the steps. For example, some steps may be decomposed, while some steps may be combined or partially combined, so the actual execution order may change according to the actual situation.

[0030] In view of the existing contract generation problems, an exemplary embodiment of the present invention discloses a method for generating a power supply and use contract based on robotic process automation, comprising the following steps:

[0031] 1) Obtaining tasks.

[0032] The RPA robot logs in to the platform query interface to simulate manual operation. For example, it goes to the marketing system work order query interface to simulate manual operation, configures the company name, business type and its corresponding voltage level, process link, and acceptance time range parameters, and centrally queries the in-transit work order process number as the task source; determines whether there is a contract generation demand for the high-voltage process new installation or capacity expansion link corresponding to the in-transit work order process number. If so, generates the corresponding task and obtains the corresponding contract template from the contract template library; this task is called a system centralized query task.

[0033] Alternatively, the RPA robot obtains contract requirements based on manual instructions, establishes a process number and user number, generates corresponding tasks, and obtains the corresponding contract template from the contract template library; the task is defined as a manually created task.

[0034] In this embodiment, the contract templates include a high-voltage power supply contract template and a temporary power supply contract template. Each template is provided with prefabricated contract variables, including single variables, conditional judgment variables and loop filling variables.

[0035] 2) Task filtering.

[0036] For the tasks generated in step 1), execute the task insurance mechanism:

[0037] The first step is to determine whether the task identification number exists in the historical contract task folder;

[0038] The second step is to check whether there is a contract file named with the identification number in the historical contract folder;

[0039] The third step is to regularly delete the historical contract task folders;

[0040] Tasks that meet the first and second steps will be filtered, that is, the task will be cancelled and will not be executed. When executing the task filtering process, if the task is a manually created task and the manual instruction requires the original contract to be overwritten, the task will not be filtered.

[0041] 3) Data acquisition.

[0042] According to the correct task obtained in step 2), the RPA robot automatically captures the information required to be filled in the contract template obtained in step 1), and ensures the smooth progress of the data capture process through the key element waiting mechanism, restart and recovery mechanism. Among them, the manually built task has the highest priority.

[0043] In this embodiment, the RPA robot logs in to the platform query interface, enters the process number, and obtains the original data page of electricity consumption information such as the power supply plan, billing plan, metering plan, power receiving equipment plan and transformer plan required for the electricity supply contract. The original data page adopts a frame architecture, and locates the target element of the web page data by traversing the access frame architecture, and stores the access path of the target element.

[0044] For web page data, the RPA robot marks the target elements to be obtained as key elements based on the process information. If the process is not smooth due to network problems, the RPA robot will wait for the key elements to appear or change before proceeding with the subsequent process. At the same time, the RPA robot will set a maximum waiting time for each wait to avoid permanent waiting in extreme cases. If the maximum waiting time is exceeded, the task will be judged as a process failure, and the mechanism will be defined as a key element waiting mechanism.

[0045] Tasks that fail due to process failure need to be restarted. To avoid the system being restricted due to multiple revisits in a short period of time, the RPA robot will gradually increase the failure restart interval based on congestion control theory, and restore the failure restart interval to the initial value after the system is accessed normally. At the same time, in order to quickly restore the task nodes, the number of cities and prefectures where tasks have been successfully executed and the number of specific successful tasks in the cities and prefectures will be recorded. Once recovered, the task after the last executed task will be quickly located to start executing the workflow. This mechanism is defined as a process restart and recovery mechanism.

[0046] If the RPA robot encounters a situation where it cannot run normally, it will report an error and make a record.

[0047] 4) Contract generation.

[0048] The RPA robot first pre-processes the data variables based on the data captured in step 3), and the data variables include contract number, receiving transformer statistics, multiple transformer descriptions, substation information, power factor standard, transformer loss, line loss, metering point system table, reactive power consumption, contract validity period, property boundary point picture, and personalized design content;

[0049] The contract number is concatenated using "user number + (number of historical contracts signed + 1)";

[0050] The receiving transformer statistics will integrate the receiving transformer information according to the change description and equipment identification, and then provide the quantity statistics and total capacity information of transformers of different specifications;

[0051] The description of multiple transformers has different description contents depending on whether the number of transformers is greater than 1;

[0052] Substation information consists of the substation name and substation voltage level;

[0053] The power factor standard value is determined based on industry classification information and approved capacity;

[0054] Transformer loss is spliced ​​using "equipment model-nameplate capacity / primary measured voltage";

[0055] Line loss is spliced ​​using line name and active line loss calculation value;

[0056] The metering point system table integrates the factory number and change description in the transformer solution information, and then gives the quantity and specification information of the current transformer and voltage transformer at different metering points;

[0057] Description of the reactive power usage metering method and comprehensive determination of the approved capacity;

[0058] The validity period of a contract is determined based on the type of contract;

[0059] The property boundary point picture is confirmed based on the property boundary point description and reservation rules;

[0060] The personalized design content includes the power grid company, signing location, power supply contact method, power supply locking method, meter reading cycle, meter reading date, power supplier contact method, number of contracts, special agreements, electricity fee settlement agreement, power supplier authorization letter, power user authorization letter, etc. The required number can be customized;

[0061] In addition, technicians in this field can also introduce other contract variables according to needs, such as property boundary point pictures, etc., and use string matching strategies to divide line descriptions and pole descriptions, and then use the image processing tool PIL to add text descriptions to the property boundary point pictures, including specifying text fonts, loading and editing picture objects, etc., and save the image after the operation is completed.

[0062] After that, map the data variables to the preset contract variable filling positions of the contract template.

[0063] In this embodiment, a contract text generation method that integrates unified rules and personalized information in multiple content forms is used to fill the content into the contract template. The contract generation can meet the filling generation of five types of contract data: the unified processing rules are derived from the contract filling instructions uniformly issued by Zhejiang State Grid Corporation, and the personalized content is derived from the demand collection results of different municipal companies and reviewed by professionals. The five types of contract data are:

[0064] First, fill in the category directly. For example, electricity classification, industry classification, user name;

[0065] Second, data integration. For example, the transformer table and transformer statistics will determine the state of the data, connect the relationship, and perform cluster statistics. For example, if some transformers have stopped running, they should not be added to the transformer statistics. At the same time, the transformer table needs to connect the transformer information and the electric energy meter information according to the metering point number, and then perform cluster statistics according to the different specifications and types of transformers at different metering points;

[0066] Third, rule judgment type. For example, transformer loss should be filled in only in the case of high supply and low metering measurement, otherwise fill in "\";

[0067] Fourth, image generation class. For example, to generate a property boundary point diagram, first determine what type of image to use based on the property boundary point description and reservation rules, then use string matching strategy to separate line description and pole description, and then use Python image processing tool PIL to add text description to the property boundary point image, including using ImageFont to specify text fonts, ImageDraw to load and edit image objects, and finally use numpy and cv2 libraries to save the image;

[0068] Fifth, personalized filling, such as special agreement, power supplier signature page information, meter reading settlement agreement, and unified authorization letter.

[0069] After the contract is completed, use the win32com library to control the operation "Word.Application" to update and ensure that the contract page number will not be incorrect after the data is filled in.

[0070] Corresponding to the aforementioned embodiment of a method for generating electricity supply and use contracts based on robotic process automation, the present application also provides an embodiment of a system for generating electricity supply and use contracts based on robotic process automation, which completes the construction of the entire chain from demand collection, contract generation, to task execution result push, greatly reducing the workload of account managers.

[0071] like Figure 2 As shown, the system consists of a control end and several execution ends. The control end includes a task acquisition module, a task acquisition module, a task allocation module, a task query module and a data display module; each execution end includes a data acquisition module, a data processing module, a data filling module, a data storage module and a task feedback module;

[0072] The task acquisition module supports two types of tasks: system centralized query and manual self-built. It is used to control the RPA robot to go to the corresponding platform, automatically generate corresponding system centralized query tasks or manual self-built tasks according to process information, use process number and / or user number as identification, and obtain the corresponding contract template from the contract template library;

[0073] The system centralized query task refers to the RPA robot logging into the platform query interface to simulate manual operation, configuring the company name, business type and its corresponding voltage level, process link, and acceptance time range parameters, and centrally querying the in-transit work order process number as the task source; judging whether there is a contract generation demand for the high-voltage process new installation or capacity expansion link corresponding to the in-transit work order process number, and if so, generating the corresponding task and obtaining the corresponding contract template from the contract template library;

[0074] The manually built tasks refer to the RPA robot obtaining contract requirements according to manual instructions, establishing process numbers and user numbers, generating corresponding tasks, and obtaining corresponding contract templates from the contract template library; in this embodiment, manually built tasks can be implemented based on the OA system of the Zhejiang Power Grid Department, using a task collection robot to log in to the mailbox regularly to receive self-built task emails, obtain the process number and OA recipient information to complete the automatic generation of contract tasks.

[0075] The task filtering module is used to verify whether the task or contract already exists based on the task generated by the task acquisition module through the task insurance mechanism. If so, the task is ignored; otherwise, the task is sent to the task allocation module. In this embodiment, the filtered tasks will directly enter the task completion status statistics pool of the control end and wait for the unified sending of OA email feedback results.

[0076] The task allocation module is used to receive tasks sent by the task filtering module, and the controller allocates the tasks to be executed to different execution terminals for processing through a load balancing strategy; among them, manually created tasks received through emails have a higher task execution priority.

[0077] The task query module is used to query the generated tasks.

[0078] The data display module is used to display query results, as well as contract generation history statistics and execution end task execution status visualization reports.

[0079] The data acquisition module is used to automatically capture the information required to be filled in the contract template, and ensure the smooth progress of the data capture process through the key element waiting mechanism, restart and recovery mechanism.

[0080] When executing data collection, enter the specific process number to obtain more than 60 items of original data under different sub-pages such as the metering scheme, power scheme, and transformer scheme required for the power supply contract. Among them, the marketing system webpage adopts the frame architecture, and some webpage elements exist in multi-layer nested frames and cannot be directly located. This embodiment uses the com interface provided by Microsoft to recursively traverse the access frame until the target element is located, and then add the access path of the frame to the Selector as one of the positioning basis information; when accessing the element content, use the COM interface to access the frame in sequence along the frame access path.

[0081] The data processing module is used to pre-process the data variables of the captured data. The data variables include contract number, receiving transformer statistics, multiple transformer descriptions, substation information, power factor standard, transformer loss, line loss, metering point system table, reactive power consumption, contract validity period, property boundary point picture, and personalized design content.

[0082] The data filling module is used to map data variables to the preset contract variable filling positions of the contract template to generate the target contract.

[0083] The data storage module is used to save the results of data collection, as well as the process manager and process number information.

[0084] The task feedback module is used to feed back the task execution results to the control end, including whether the contract is generated successfully and the storage location.

[0085] Regarding the system in the above embodiment, the specific manner in which each unit or module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0086] For the system embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The system embodiment described above is only schematic, and the data processing modules described therein may or may not be physically separated. In addition, the functional modules in the present invention may be integrated into a processing unit, or each module may exist physically separately, or two or more modules may be integrated into one unit. The above-mentioned integrated modules or units may be implemented in the form of hardware or in the form of software functional units, so as to select some or all of the modules according to actual needs to achieve the purpose of the present application scheme.

[0087] In order to verify the effect of the present invention, the present invention carried out a pilot verification work on the automatic generation of new installation (capacity increase) power supply and use contracts in a subsidiary of the State Grid. In the task acquisition stage, the RPA robot obtained the high-voltage new installation (capacity increase) in-transit processes in the process link of completion inspection. A total of 233 high-voltage business expansion processes that met the conditions, including 110 high-voltage new installation processes and 123 high-voltage capacity increase processes. Each process corresponds to a contract generation task.

[0088] It took a total of 19 hours and 14 minutes to complete all tasks, with an average time of 4 minutes and 57 seconds to generate each contract. Among them, it took an average of 3 minutes and 40 seconds to generate each new high-voltage installation contract, and an average of 6 minutes and 6 seconds to generate each high-voltage capacity expansion contract.

[0089] Finally, the contract generation results were evaluated. By analyzing the RPA program log, no error records were found in the program execution process. At the same time, 30 of the 233 automatically generated contracts were selected for manual inspection, and no generation errors were found. The contract generation accuracy rate was 100%.

[0090] The present invention describes specific embodiments to simplify the present invention. However, it should be recognized that the present invention is not limited to the described embodiments, and various modifications of the present invention are possible without departing from the basic principles, and these equivalent forms also fall within the scope defined by the appended claims of the present application.

Claims

1. A method for generating a power supply and use contract based on robotic process automation, characterized in that: The steps include: 1) Obtaining tasks The RPA robot goes to the corresponding platform, automatically generates corresponding tasks based on the process information, uses the process number and / or user number as an identifier, and obtains the corresponding contract template from the contract template library; In the task acquisition phase, the RPA robot goes to the corresponding platform to perform centralized system query tasks or manually create tasks. The system centralized query task refers to the RPA robot logging into the platform query interface to simulate manual operation, configuring the company name, business type and its corresponding voltage level, process link, and acceptance time range parameters, and centrally querying the in-transit work order process number as the task source; judging whether there is a contract generation demand for the high-voltage process new installation or capacity expansion link corresponding to the in-transit work order process number, and if so, generating the corresponding task and obtaining the corresponding contract template from the contract template library; The manual self-built task refers to the RPA robot obtaining the contract requirements according to the manual instructions, establishing the process number and user number, generating the corresponding task, and obtaining the corresponding contract template from the contract template library; 2) Task filtering For the task generated in step 1), verify whether the task or contract already exists through the task insurance mechanism. If it does, ignore the task; otherwise, execute step 3); 3) Data Capture The RPA robot automatically captures the information required to be filled in the contract template obtained in step 1) and ensures the smooth progress of the data capture process through the key element waiting mechanism, restart and recovery mechanism; Step 3) is as follows: The RPA robot logs in to the platform query interface, enters the process number, and obtains the original data page of electricity consumption information required for the electricity supply contract. The original data page adopts a frame structure, locates the target element of the web page data by traversing the access frame structure, and stores the access path of the target element; The electricity usage information includes the user's power supply plan, billing plan, metering plan, powered equipment plan, and transformer plan; The key element waiting mechanism, restart and recovery mechanism are used to ensure the smooth progress of the data capture process, specifically: Key element waiting mechanism: For web page data, the RPA robot marks the target element to be obtained as a key element based on the process information. If the process is not smooth due to network problems, the RPA robot will wait for the key element to appear or change before proceeding with the subsequent process. At the same time, the RPA robot will set a maximum waiting time for each wait to avoid permanent waiting in extreme cases. If the maximum waiting time is exceeded, the task will be judged as a process failure. Process restart and recovery mechanism: Tasks that fail in a process need to be restarted. To avoid multiple re-accesses to the system in a short period of time causing the system to restrict its access, the RPA robot will gradually increase the failure restart interval according to congestion control theory, and restore the failure restart interval to the initial value after the system is accessed normally. At the same time, in order to quickly restore the task node, the number of cities where tasks have been successfully executed and the number of specific successful tasks in the cities will be recorded. Once recovered, the task after the last executed task will be quickly located to start executing the workflow. 4) Contract Generation Fill the data captured in step 3) into the contract template to generate the target contract.

2. The method for generating a power supply and utilization contract based on robotic process automation according to claim 1, characterized in that: After completing the task filtering, the controller distributes the tasks to be executed to different execution terminals for processing through a load balancing strategy, and the artificially built tasks have the highest priority.

3. The method for generating a power supply and utilization contract based on robotic process automation according to claim 1, characterized in that: The mission insurance mechanism is specifically as follows: The first step is to determine whether the task identification number exists in the historical contract task folder; The second step is to check whether there is a contract file named with the identification number in the historical contract folder; The third step is to regularly delete the historical contract task folders; Tasks that satisfy the first and second steps will be filtered.

4. The method for generating a power supply and utilization contract based on robotic process automation according to claim 3, characterized in that: When executing the task filtering process, if the task is a manually created task and the manual instruction requires overwriting the original contract, the task will not be filtered.

5. The method for generating a power supply and utilization contract based on robotic process automation according to claim 1, characterized in that: Step 4) is as follows: 4.1) The RPA robot first pre-processes the data variables based on the data captured in step 3), including the contract number, receiving transformer statistics, multiple transformer descriptions, substation information, power factor standard, transformer loss, line loss, metering point system table, reactive power consumption, contract validity period, property boundary point image, and personalized design content; The contract number is concatenated using "user number + (number of historical contracts signed + 1)"; The receiving transformer statistics will integrate the receiving transformer information according to the change description and equipment identification, and then provide the quantity statistics and total capacity information of transformers of different specifications; The description of multiple transformers has different description contents depending on whether the number of transformers is greater than 1; Substation information consists of the substation name and substation voltage level; The power factor standard value is determined based on industry classification information and approved capacity; Transformer loss is spliced ​​using "equipment model-nameplate capacity / primary measured voltage"; Line loss is spliced ​​using line name and active line loss calculation value; The metering point system table integrates the factory number and change description in the transformer solution information, and then gives the quantity and specification information of the current transformer and voltage transformer at different metering points; Description of the reactive power usage metering method and comprehensive determination of the approved capacity; The validity period of a contract is determined based on the type of contract; The property boundary point picture is confirmed based on the property boundary point description and reservation rules; The personalized design content includes the power grid company, signing location, power supply contact method, power supply locking method, meter reading cycle, meter reading date, power supplier contact method, number of contracts, special agreements, electricity fee settlement agreement, power supplier authorization letter, power user authorization letter; 4.2) Map the data variables to the preset contract variable filling positions of the contract template.

6. The method for generating a power supply and utilization contract based on robotic process automation according to claim 5, characterized in that: The contract templates include a high-voltage power supply and use contract template and a temporary power supply and use contract template. Each template is provided with prefabricated contract variables, including single variables, conditional judgment variables and loop filling variables.

7. A power supply and use contract generation system based on robotic process automation, characterized in that: Used to implement the power supply and use contract generation method described in claim 2, the power supply and use contract generation system is composed of a control end and several execution ends, the control end includes a task acquisition module, a task acquisition module, a task allocation module, a task query module and a data display module; each execution end includes a data acquisition module, a data processing module, a data filling module, a data storage module and a task feedback module; The task acquisition module is used to control the RPA robot to go to the corresponding platform, automatically generate the corresponding system centralized query task or manually built task according to the process information, use the process number and / or user number as an identifier, and obtain the corresponding contract template from the contract template library; the system centralized query task refers to the RPA robot logging into the platform query interface to simulate manual operation, configure the company name, business type and its corresponding voltage level, process link, and acceptance time range parameters, and centrally query the in-transit work order process number as the task source; determine whether there is a contract generation demand for the new installation or capacity expansion link of the high-voltage process corresponding to the in-transit work order process number. If so, generate the corresponding task and obtain the corresponding contract template from the contract template library; the manually built task refers to the RPA robot obtaining the contract demand according to manual instructions, establishing the process number and user number, generating the corresponding task, and obtaining the corresponding contract template from the contract template library; The task filtering module is used to verify whether the task or contract already exists according to the task generated by the task acquisition module through the task insurance mechanism. If so, the task is ignored; otherwise, the task is sent to the task allocation module; The task allocation module is used to receive tasks sent by the task filtering module, and the controller allocates the tasks to be executed to different execution terminals for processing through a load balancing strategy; The task query module is used to query the generated tasks; The data display module is used to display query results, as well as contract generation history statistics and execution status visualization reports of execution-end tasks; The data acquisition module is used to automatically capture the information required to be filled in the contract template, and ensure the smooth progress of the data capture process through the key element waiting mechanism, restart and recovery mechanism; Specifically: The RPA robot logs in to the platform query interface, enters the process number, and obtains the original data page of electricity consumption information required for the electricity supply contract. The original data page adopts a frame structure, locates the target element of the web page data by traversing the access frame structure, and stores the access path of the target element; The electricity usage information includes the user's power supply plan, billing plan, metering plan, powered equipment plan, and transformer plan; The key element waiting mechanism, restart and recovery mechanism are used to ensure the smooth progress of the data capture process, specifically: Key element waiting mechanism: For web page data, the RPA robot marks the target element to be obtained as a key element based on the process information. If the process is not smooth due to network problems, the RPA robot will wait for the key element to appear or change before proceeding with the subsequent process. At the same time, the RPA robot will set a maximum waiting time for each wait to avoid permanent waiting in extreme cases. If the maximum waiting time is exceeded, the task will be judged as a process failure. Process restart and recovery mechanism: Tasks that fail in a process need to be restarted. To avoid multiple re-accesses to the system in a short period of time causing the system to restrict its access, the RPA robot will gradually increase the failure restart interval according to congestion control theory, and restore the failure restart interval to the initial value after the system is accessed normally. At the same time, in order to quickly restore the task node, the number of cities where tasks have been successfully executed and the number of specific successful tasks in the cities will be recorded. Once recovered, the task after the last executed task will be quickly located to start executing the workflow. A data processing module is used to pre-process the captured data variables, wherein the data variables include contract number, receiving transformer statistics, multiple transformer descriptions, substation information, power factor standard, transformer loss, line loss, metering point system table, reactive power consumption, contract validity period, property boundary point picture, and personalized design content; A data filling module is used to map data variables to preset contract variable filling positions of the contract template to generate a target contract; The data storage module is used to save the results of data collection, as well as the process owner and process number information; The task feedback module is used to feed back the task execution results to the control end, including whether the contract is generated successfully and the storage location.

Images