CN112150102A - Smart grid information system account updating method and device combining RPA and AI - Google Patents

Abstract

The present application proposes a method and device for updating a smart grid information system ledger by combining RPA and AI, wherein the method includes: acquiring first ledger data in a ledger data file, wherein the first ledger data includes the first ledger data. The equipment identification corresponding to the data of one account and the identification of the project to which it belongs; obtain the data of the second account corresponding to the identification of the equipment and the identification of the project; when the data of the first account does not match the data of the second account, the grid information In the system, the ledger data corresponding to the equipment identification and project identification are updated. Therefore, by matching the account data in the account data file with the old account data, when the two do not match, the account data in the account data file is automatically updated to the power grid information system, and the whole process No manual participation is required, which improves synchronization efficiency and accuracy.

Description

A smart grid information system ledger update method and device combining RPA and AI

technical field

The present application relates to the field of power grid technology, and in particular, to a method and device for updating an account of a smart grid information system combining RPA and AI.

Background technique

Robotic Process Automation (RPA) is a new type of artificial intelligence virtual process automation robot, which is used to simulate human operations on computers and automatically execute process tasks according to rules. RPA can be widely used in various processes that require The field of automation, such as the power grid field.

Artificial Intelligence (AI) is a technical science that studies and develops theories, methods, technologies and application systems for simulating, extending and expanding human intelligence.

In the electronic handover business in the power grid field, it is usually necessary to synchronize the ledger data to the power grid information system. At present, it is mainly through the manual entry system. Since there are many manual operations in the process of entering the system, it is not only inefficient, but also the accuracy cannot be guaranteed.

SUMMARY OF THE INVENTION

The present application provides a smart grid information system ledger update method and device combining RPA and AI. The specific technical solutions are as follows:

In a first aspect, an embodiment of the present application provides a method for updating an account of a smart grid information system that combines RPA and AI, including:

Obtain the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the project identification to which it belongs;

Obtain the second account data corresponding to the equipment identification and the engineering project identification;

When the first account data does not match the second account data, the account data corresponding to the equipment identification and the engineering item identification in the power grid information system are updated.

The method for updating the ledger of the smart grid information system combining RPA and AI according to the embodiment of the present application, obtains the first ledger data in the ledger data file, wherein the first ledger data includes the equipment corresponding to the first ledger data Identification and the identification of the engineering project it belongs to; obtain the second account data corresponding to the equipment identification and the engineering project identification; when the first account data does not match the second account data The ledger data corresponding to the project ID is updated. Therefore, by matching the account data in the account data file with the old account data, when the two do not match, the account data in the account data file is automatically updated to the power grid information system, and the whole process No manual participation is required, which improves synchronization efficiency and accuracy.

In a possible implementation manner of the embodiment of the first aspect of the present application, the acquiring the second ledger data corresponding to the equipment identifier and the engineering item identifier specifically includes:

Acquire second ledger data corresponding to the equipment identifier and the engineering item identifier from the robotic process automation RPA system.

In a possible implementation manner of the embodiment of the first aspect of the present application, the acquiring the second ledger data corresponding to the equipment identifier and the engineering item identifier specifically includes:

From the power grid information system, acquire the second account data corresponding to the equipment identification and the engineering item identification.

In a possible implementation manner of the embodiment of the first aspect of the present application, before acquiring the first account data in the account data file, the method further includes:

Delete the historical ledger data in the RPA system.

In a possible implementation manner of the embodiment of the first aspect of the present application, when the first account data and the second account data do not match, the power grid information system, the equipment identifier and the device identifier are not matched. The ledger data corresponding to the project identifier is updated, specifically including:

When the second ledger data is empty, the first ledger data is added to the ledger data list corresponding to the engineering project identifier in the power grid information system.

In a possible implementation manner of the embodiment of the first aspect of the present application, when the first account data and the second account data do not match, the power grid information system, the equipment identifier and the device identifier are not matched. The ledger data corresponding to the project identifier is updated, specifically including:

When the first value of any field in the first account data does not match the second value of any field in the second account data, the first value is used to update the The value of any of the fields in the power grid information system.

In a possible implementation manner of the embodiment of the first aspect of the present application, the acquiring the first account data in the account data file specifically includes:

The first ledger data is obtained from the ledger data file at a preset frequency.

In a possible implementation manner of the embodiment of the first aspect of the present application, the method further includes:

When the first account data matches the second account data, the first account data is stored in a backup file, and the matching result is recorded.

In the second aspect, an embodiment of the present application provides a smart grid information system account update device that combines RPA and AI, including:

The first acquisition module is used to acquire the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the engineering project identification to which it belongs;

The second acquisition module is used to acquire the second account data corresponding to the equipment identification and the engineering project identification;

The updating module is configured to update the account data corresponding to the equipment identification and the engineering item identification in the power grid information system when the first account data does not match the second account data.

The smart grid information system ledger updating device combining RPA and AI according to the embodiment of the present application obtains the first ledger data in the ledger data file, wherein the first ledger data includes the equipment corresponding to the first ledger data Identification and the identification of the engineering project it belongs to; obtain the second account data corresponding to the equipment identification and the engineering project identification; when the first account data does not match the second account data The ledger data corresponding to the project ID is updated. Therefore, by matching the account data in the account data file with the old account data, when the two do not match, the account data in the account data file is automatically updated to the power grid information system, and the whole process No manual participation is required, which improves synchronization efficiency and accuracy.

In a possible implementation manner of the embodiment of the second aspect of the present application, the second acquisition module is specifically used for:

Acquire second ledger data corresponding to the equipment identification and the engineering item identification from the RPA system.

In a possible implementation manner of the embodiment of the second aspect of the present application, the second acquisition module is specifically used for:

From the power grid information system, acquire the second account data corresponding to the equipment identification and the engineering item identification.

In a possible implementation manner of the embodiment of the second aspect of the present application, the apparatus may further include:

The delete module is used to delete the historical ledger data in the Robotic Process Automation RPA system.

In a possible implementation manner of the embodiment of the second aspect of the present application, the updating module is specifically used for:

When the second ledger data is empty, the first ledger data is added to the ledger data list corresponding to the engineering project identifier in the power grid information system.

In a possible implementation manner of the embodiment of the second aspect of the present application, the updating module is specifically used for:

When the first value of any field in the first account data does not match the second value of any field in the second account data, the first value is used to update the The value of any of the fields in the power grid information system.

In a possible implementation manner of the embodiment of the second aspect of the present application, the first acquisition module is specifically used for:

The first ledger data is obtained from the ledger data file at a preset frequency.

In a possible implementation manner of the embodiment of the second aspect of the present application, the apparatus may further include:

A storage module, configured to store the first account data in a backup file when the first account data matches the second account data, and record the matching result.

In a third aspect, an embodiment of the present application provides a computing device, where the device includes:

memory in which executable program code is stored;

a processor coupled to the memory;

Wherein, the processor invokes the executable program code stored in the memory to execute the method for updating the ledger of the smart grid information system combining RPA and AI as described in the first aspect above.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, characterized in that, when the program is executed by a processor, the intelligent combination of RPA and AI as described in the first aspect above is realized. A method for updating the ledger of the power grid information system.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not limiting of the present application.

Description of drawings

The accompanying drawings are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the description, serve to explain the principles of the present application, and do not constitute an improper limitation of the present application.

1 is a schematic flowchart of a method for updating an account in a smart grid information system combining RPA and AI provided by an embodiment of the present application;

2 is a schematic flowchart of another method for updating an account of a smart grid information system combining RPA and AI provided by an embodiment of the present application;

3 is a schematic flowchart of another method for updating an account of a smart grid information system combining RPA and AI provided by an embodiment of the present application;

4 is a schematic flowchart of another method for updating an account of a smart grid information system combining RPA and AI provided by an embodiment of the present application;

5 is a schematic flowchart of another method for updating an account of a smart grid information system combining RPA and AI provided by an embodiment of the present application;

6 is a schematic structural diagram of a smart grid information system account update device combining RPA and AI provided by an embodiment of the application;

FIG. 7 is a schematic structural diagram of a computing device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the protection scope of the present application.

It should be noted that the terms "comprising" and "having" in the embodiments of the present application and the accompanying drawings and any modifications thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the steps or units listed, but optionally also includes steps or units not listed, or optionally also includes For other steps or units inherent to these processes, methods, products or devices.

In the electronic handover business in the power grid field, it is usually necessary to synchronize the ledger data to the power grid information system. At present, it is mainly through the manual entry system. Since there are many manual operations in the process of entering the system, it is not only inefficient, but also the accuracy cannot be guaranteed.

In response to this problem, the embodiments of the present application provide a method for updating an account of a smart grid information system that combines RPA and AI, so as to automatically synchronize updated account data to the grid information system.

RPA is a business process automation technology based on software robots and artificial intelligence (AI). Through a specific "robot software", the operation of a human on the computer is simulated, and the process tasks are automatically executed according to the rules.

FIG. 1 is a schematic flowchart of a method for updating an account of a smart grid information system that combines RPA and AI according to an embodiment of the present application.

The smart grid information system ledger update method combining RPA and AI according to the embodiment of the present application can be executed by an RPA robot to automatically match the data in the ledger data file with the ledger data that has been synchronized to the grid information system. When it does not match, the ledger data in the ledger data file is updated to the power grid information system, so as to automatically synchronize the changed ledger data to the power grid information system.

As shown in Figure 1, the smart grid information system ledger update method combining RPA and AI includes:

Step 101: Acquire the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the engineering item identification to which the first account data belongs.

In the process of electronic handover in the power grid field, relevant personnel need to enter equipment account information. In this embodiment, the ledger data of the ledger data file is the equipment ledger information entered in the electronic handover process. That is to say, in the process of electronic handover, one or more pieces of ledger data entered are put into the ledger data file. Wherein, the ledger data file may be an Excel table file, or other table files and the like.

In the specific implementation, the template of the ledger data can be preset. During the electronic handover process, when the ledger information needs to be entered, the relevant personnel can enter the ledger data in the template of the ledger data.

In this embodiment, the account data in the account data file includes values of multiple fields, such as equipment model, manufacturer of the production equipment, technical parameters, installation location of the equipment, maintenance personnel information, and so on. Since the ledger data in the ledger data file is generated during the electronic handover process of the engineering project, the ledger data generated during the electronic handover process may also include the identification of the engineering project to which it belongs, such as the project number.

In this embodiment, the RPA system can log in to the system where the ledger data file is located, and then acquire the ledger data in the ledger data file, which is referred to as the first ledger data here, and store the acquired first ledger data in the local cache middle. Wherein, the first account data includes the equipment identification corresponding to the first account data and the engineering item identification to which it belongs. Wherein, the equipment identifier may be the model of the equipment, or the installation location, etc., or other identifiers that can uniquely identify the uniqueness of the equipment in the engineering project.

Step 102: Acquire second ledger data corresponding to the equipment identification and the engineering item identification.

Since the equipment ID and the project ID can uniquely identify a piece of ledger data, the old ledger data can be queried to obtain the ledger data corresponding to the equipment ID and the project ID. For the convenience of distinction, it is called the second one here. account data.

The old ledger data here is the ledger data corresponding to each engineering item, which can be understood as the ledger data corresponding to each engineering item in the power grid information system. In specific implementation, the RPA system can first obtain the ledger data corresponding to the project identifier from the old ledger data according to the project identifier included in the first ledger data, and then obtain the ledger data corresponding to the project identifier from the old ledger data. In the data, look for the ledger data corresponding to the equipment identification included in the first ledger data, that is, the second ledger data.

Step 103, when the first account data does not match the second account data, update the account data corresponding to the equipment identification and the engineering item identification in the power grid information system.

After obtaining the first account data and the second account data, you can compare the first account data with the second account data. If the first account data does not match the second account data, it means that the first account If the account data has changed relative to the second account data, the first account data can be used to update the account data corresponding to the equipment identification and the engineering item identification in the power grid information system.

Specifically, in the power grid information system, the RPA system first finds out the ledger data corresponding to the identification of the engineering project, and then finds out the equipment identification included in the first ledger data from the ledger data corresponding to the identification of the engineering project. The corresponding ledger data is then updated using the first ledger data corresponding to the ledger data corresponding to the equipment identification and the project identification.

When updating, the first ledger data can be used to cover the ledger data corresponding to the equipment identification and the engineering item identification in the power grid information system.

It should be noted that when there are multiple pieces of ledger data in the ledger data file, the RPA system can obtain all ledger data in the ledger data file, cache it locally, and then perform the above operations on the cached ledger data one by one. Therefore, it can be determined whether each piece of account data recorded in the account data file has changed compared with the account data in the power grid information system.

In the embodiment of the present application, by acquiring the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the identification of the engineering project to which it belongs; The second account data corresponding to the project identification; when the first account data does not match the second account data, the account data corresponding to the equipment identification and the project identification in the power grid information system are updated. Therefore, by matching the account data in the account data file with the old account data, when the two do not match, the account data in the account data file is automatically updated to the power grid information system, and the whole process No manual participation is required, which improves synchronization efficiency and accuracy.

In practical applications, if the RPA system logs into the power grid information system every time to obtain the second account data, it will obviously affect the synchronization efficiency. Based on this, in an embodiment of the present application, the RPA system can locally store the account data synchronized with the power grid information system, and then obtain the second account data locally, and compare the first account data with the second account data to match. The following description will be made with reference to FIG. 2 , which is a schematic flowchart of another method for updating an account of a smart grid information system combining RPA and AI provided by an embodiment of the present application.

As shown in Figure 2, the method includes:

Step 201: Acquire the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the identification of the engineering project to which the first account data belongs.

In this embodiment, step 201 is similar to the above-mentioned step 101, and thus will not be repeated here.

Step 202: Acquire the second ledger data corresponding to the equipment identification and the engineering item identification from the RPA system.

In this embodiment, for the first time, the RPA system obtains the ledger data in the ledger data file from the system where the ledger data file is located and stores it locally, and synchronizes all ledger data in the acquired ledger data file to the power grid information system . After that, every time the ledger data in the ledger data file is obtained, it can be judged whether the local ledger data needs to be updated, if necessary, update the local ledger data, and update the ledger data that needs to be updated to the grid information synchronously. in the system. Thus, the RPA system stores the same ledger data as the grid information system.

Then, the RPA system can first obtain the ledger data corresponding to the project identifier included in the first ledger data locally, and then find the ledger data corresponding to the equipment identifier included in the first ledger data, that is, the first ledger data. Second account data.

Step 203, when the first account data does not match the second account data, update the account data corresponding to the equipment identification and the project identification in the power grid information system.

In this embodiment, the RPA system compares the first account data with the second account data obtained locally. When the two do not match, the first account data is used to update the account data in the power grid information system corresponding to the equipment identification and the project identification.

Specifically, in the power grid information system, the RPA system first finds out the ledger data corresponding to the identification of the engineering project, and then finds out the equipment identification included in the first ledger data from the ledger data corresponding to the identification of the engineering project. The corresponding ledger data is then updated using the first ledger data corresponding to the ledger data corresponding to the equipment identification and the project identification.

In order to continue to make judgments locally in the RPA system, the RPA system uses the first account data to update the second account data obtained locally, so that the RPA system has the same account data as the power grid information system.

When the first account data matches the second account data, the RPA system does not need to log in to the power grid information system, nor does it need to update the account data in the power grid information system.

For example, assuming that the ledger data file contains 10 ledger data, the RPA system obtains the 10 ledger data and caches them locally. After judging that the 10 ledger data does not exist locally, the 10 ledger data are stored locally. Synchronized to the power grid information system and stored in the same ledger data file maintained locally as the power grid information system. After 1 minute, the RPA system obtains 11 ledger data from the ledger data file. After comparing it with the 10 ledger data stored locally, it is found that one ledger data has changed, then this one can be changed. The account data is updated to the power grid information system, and updated to the same account data file maintained locally as the power grid information system.

If there are multiple ledger data in the ledger data file, in the specific implementation, the RPA system can judge all ledger data in the ledger data, and then synchronize the ledger data that needs to be updated to the power grid information system. Of course, after judging each piece of ledger data, if it needs to be synchronized to the power grid information system, after updating it to the power grid information system, another ledger data in the ledger data file can be judged until the ledger is completed. Judgment of all ledger data in the data file.

In the embodiment of the present application, when acquiring the second ledger data corresponding to the equipment identification and the engineering project identification, the second ledger data corresponding to the equipment identification and the engineering project identification can be acquired from the RPA system. As a result, the RPA system matches the ledger data in the ledger data file with the local corresponding ledger data. When it does not match, the corresponding ledger data in the power grid information system is updated, so that there is no need to retrieve data from the power grid every time. The second data is acquired in the information system, thereby improving update efficiency or synchronization efficiency.

In practical applications, if the RPA system maintains the same ledger data as the power grid information system, when the number of ledger data is relatively large, it will obviously occupy a large amount of memory of the RPA system. Considering the memory of the RPA system, in an embodiment of the present application, when acquiring the second account data, the second account data can be obtained from the power grid information system.

In this embodiment, the ledger data of the equipment used in each engineering project is synchronized to the power grid information system, that is, the ledger data of the equipment used in each engineering project is stored in the grid information system.

Specifically, the RPA system obtains the first account data in the account data file from the system where the account data file is located, caches it locally, and logs into the power grid information system. Engineering item identification, obtains the second account data corresponding to the equipment identification and engineering item identification from the power grid information system, and caches it locally. Then, the RPA system compares the locally cached first account data with the second account data, and if the two do not match, uses the first account data to update the second account data in the power grid information system.

If there are multiple pieces of first account data in the account data file, the RPA system can cache the multiple pieces of first account data in the account data file locally, and then determine the device ID and The identification of the project to which it belongs, and then multiple pieces of second account data are obtained from the power grid information system and cached locally. Then, compare the first account data with the same equipment identification and engineering item identification with the second account data to determine the second account data that needs to be updated, and then, according to the first account data, the corresponding data in the power grid information system The second ledger data is updated.

Of course, for a certain first account data, the RPA system can obtain the corresponding second account data from the power grid information system. When the two do not match, update the corresponding second account data in the power grid information system according to the first account data. Second account data. Then, for the next first account data, repeat the above operation until all the first account data is traversed.

In the embodiment of the present application, when acquiring the second ledger data corresponding to the equipment identification and the engineering project identification, the second ledger data corresponding to the equipment identification and the engineering project identification can be obtained from the power grid information system. Thus, the RPA system obtains the second account data from the power grid information system, thereby reducing the occupation of the memory of the RPA system.

In an embodiment of the present application, in order to improve the accuracy of the update, when acquiring the second account data corresponding to the equipment identification and the engineering project identification, the second account data is obtained from the power grid information system, then the second account data is obtained from the power grid information system. Before the first account data in the data file, delete the historical account data in the RPA system, that is, the RPA system deletes the locally cached historical account data. The historical ledger data here can be understood as the first ledger data in the ledger data file obtained by the RPA system most recently.

In the embodiment of the present application, when acquiring the second account data corresponding to the equipment identification and the engineering project identification, the second account data is obtained from the power grid information system, and before the first account data in the account data file is acquired , delete the historical ledger data in the RPA system. Therefore, not only memory is saved, but also historical account data that has been traversed can be avoided to be traversed again, thereby improving the accuracy of updating the account data to the system.

In practical applications, new equipment may be added to the project, so for the first account data of the newly added equipment, the corresponding second account data cannot be obtained from the power grid information system. This problem is described below with reference to FIG. 3 . FIG. 3 is a schematic flowchart of another method for updating an account of a smart grid information system combining RPA and AI provided by an embodiment of the present application.

As shown in Figure 3, the method includes:

Step 301: Acquire the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the identification of the engineering project to which the first account data belongs.

Step 302: Acquire second ledger data corresponding to the equipment identifier and the project item identifier.

In this embodiment, steps 301 to 302 are similar to the above-mentioned steps 101 to 102, and thus are not repeated here.

Step 303, when the second account data is empty, add the first account data to the account data list corresponding to the project identifier in the power grid information system.

In practical applications, new equipment may be added to the engineering project, so in the process of electronic handover, the ledger data entered for this can obviously not be queried in the power grid information system.

If the second account data is searched from the power grid information system, the RPA system searches for the account data corresponding to the project identification in the power grid information system according to the first account data including the identification of the engineering project, and then according to the first account The equipment identification included in the data is searched in the ledger data corresponding to the project identification. If the ledger data corresponding to the equipment identification is not found, that is, the second ledger data is empty, then the first ledger data is added to It is in the ledger data list corresponding to the project identification in the power grid information system.

If the RPA system stores the same ledger data as the power grid information system, then firstly search for the ledger data corresponding to the engineering project identification according to the project identification, and then search for the ledger data corresponding to the engineering project identification according to the equipment identification Ledger data corresponding to the device ID. If the ledger data corresponding to the equipment ID is not found, that is, the second ledger data is empty, add the first ledger data to the ledger data list corresponding to the project ID in the power grid information system, and add it to The RPA system stores the ledger data list corresponding to the project ID.

In the embodiment of the present application, when the second account data is empty, the first account data is added to the account data list corresponding to the project identifier in the power grid information system, so that when the first account data is for the newly added account equipment, add it to the ledger data list corresponding to the project identification in the power grid information system, so as to realize the automatic synchronization of the ledger data of the newly added equipment to the power grid information system, and improve the accuracy and efficiency of synchronization.

In order to improve the accuracy of the update, in an embodiment of the present application, if the second account data is not empty, the value of the corresponding fields of the first account data and the second account data can be compared to determine whether to to update. The following description will be made with reference to FIG. 4 , which is a schematic flowchart of another method for updating an account of a smart grid information system combining RPA and AI provided by an embodiment of the present application.

As shown in Figure 4, the method includes:

Step 401: Acquire the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the engineering item identification to which the first account data belongs.

Step 402: Acquire second ledger data corresponding to the equipment identifier and the project item identifier.

In this embodiment, steps 401 to 402 are similar to the above-mentioned steps 101 to 102, and thus are not repeated here.

Step 403, when the first value of any field in the first account data does not match the second value of any field in the second account data, use the first value to update any field in the power grid information system value of .

In this embodiment, the ledger data may include values of multiple fields, and the first ledger data may be compared with the values of the corresponding fields in the second ledger data to determine whether there are values of one or more fields inconsistent. When the first value of any field in the first account data does not match the second value of the field in the second account data, update the value of the field in the power grid information system to the first account The first value of this field in the data.

For example, if the ledger data includes equipment model, equipment manufacturer, technical parameters, and installation location information, etc., then the equipment model, equipment manufacturer, technical parameters, and installation location of the first ledger data can be compared with those in the second ledger data, respectively. The equipment model, equipment manufacturer, technical parameters, and installation location information are compared. When the installation position A in the first account data does not match the installation position B in the second account data, the grid information system, the equipment identification and the project identification corresponding to the first account data in the account data The installation location B is updated to the installation location A.

It should be noted that, according to the needs of the application, when a field is added to the first account data, the value of the field can be added to the account data corresponding to the equipment identification and project identification in the power grid information system. .

In the embodiment of the present application, when the first value of any field in the first account data does not match the second value of any field in the second account data, the first value is used to update the data in the power grid information system. The value of any field. Therefore, when the value of a field in the first account data does not match the value of the field in the second account data, the value of the field in the first account data is used to update the corresponding account data in the power grid information system. The value of the field is automatically updated to the telecommunication information system, thereby improving the update accuracy.

In order to improve the timeliness of updating, in an embodiment of the present application, the first account data can be acquired from the account data file at a preset frequency. For example, the ledger data in the ledger data file is obtained every 1 minute, and the ledger data is cached locally to compare it with the corresponding second ledger data.

The preset frequency may be set as required, which is not limited in this embodiment.

In the embodiment of the present application, when acquiring the first account data in the account data file, the first account data is obtained from the account data file at a preset frequency, thereby improving the timeliness of updating.

In order to facilitate subsequent tracing, in an embodiment of the present application, when the first account data matches the second account data, the first account data may be stored in a backup file, and the matching result is recorded. The following description will be made with reference to FIG. 5 , which is a schematic flowchart of another method for updating an account of a smart grid information system combining RPA and AI provided by an embodiment of the present application.

As shown in Figure 5, the method includes:

Step 501: Acquire the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the identification of the engineering project to which the first account data belongs.

Step 502: Acquire second ledger data corresponding to the equipment identifier and the project item identifier.

Step 503, when the first account data does not match the second account data, update the account data corresponding to the equipment identification and the engineering item identification in the power grid information system.

In this embodiment, steps 501 to 503 are similar to the above-mentioned steps 101 to 103, and thus are not repeated here.

Step 504, when the first account data matches the second account data, the first account data is stored in the backup file, and the matching result is recorded.

In this embodiment, when the value of each field in the first account data matches the value of the corresponding field in the second account data, it means that the first account data matches the second account data, and the first account data into the backup file. Among them, the backup files can be stored in the RPA system or in the power grid information system.

In the specific implementation, if there are multiple pieces of first account data in the account data file, after traversing all the first account data, the first account data that matches the corresponding second account data can be stored in the into the backup file, and record the matching result corresponding to each ledger data.

In the embodiment of the present application, when the first account data matches the second account data, the first account data is stored in the backup file, and the matching result is recorded. Therefore, even if no update is required, the backup file of the first ledger data is recorded, which can facilitate subsequent traceability.

In order to realize the above embodiments, the present application also proposes a schematic structural diagram of a smart grid information system ledger update device combining RPA and AI. FIG. 6 is a schematic structural diagram of a smart grid information system account update device combining RPA and AI provided by an embodiment of the present application.

As shown in FIG. 6 , the smart grid information system account update device 600 combining RPA and AI includes: a first acquisition module 610 , a second acquisition module 620 and an update module 630 .

The first acquisition module 610 is used to acquire the first account data in the account data file, wherein the first account data includes the equipment identification corresponding to the first account data and the engineering project identification to which it belongs;

The second acquisition module 620 is used to acquire the second account data corresponding to the equipment identification and the engineering project identification;

The updating module 630 is configured to update the account data corresponding to the equipment identification and the project identification in the power grid information system when the first account data does not match the second account data.

In a possible implementation manner of the embodiment of the present application, the above-mentioned second obtaining module 620 is specifically used for:

Obtain the second ledger data corresponding to the equipment identification and the engineering item identification from the RPA system.

In a possible implementation manner of the embodiment of the present application, the above-mentioned second obtaining module 620 is specifically used for:

From the power grid information system, obtain the second account data corresponding to the equipment identification and the engineering item identification.

In a possible implementation manner of the embodiment of the present application, the apparatus may further include:

The delete module is used to delete the historical ledger data in the Robotic Process Automation RPA system.

In a possible implementation manner of the embodiment of the present application, the above-mentioned update module 630 is specifically used for:

When the second ledger data is empty, the first ledger data is added to the ledger data list corresponding to the project identifier in the power grid information system.

In a possible implementation manner of the embodiment of the present application, the above-mentioned update module 630 is specifically used for:

When the first value of any field in the first account data does not match the second value of any field in the second account data, use the first value to update the value of any field in the power grid information system .

In a possible implementation manner of the embodiment of the present application, the above-mentioned first obtaining module 610 is specifically used for:

Get the first ledger data from the ledger data file at a preset frequency.

In a possible implementation manner of the embodiment of the present application, the apparatus may further include:

The storage module is used to store the first account data in the backup file when the first account data matches the second account data, and record the matching result.

The above apparatus embodiments correspond to the method embodiments, and have the same technical effects as the method embodiments. For specific descriptions, refer to the method embodiments. The apparatus embodiment is obtained based on the method embodiment, and the specific description can refer to the method embodiment section, which will not be repeated here.

The smart grid information system ledger updating device combining RPA and AI according to the embodiment of the present application obtains the first ledger data in the ledger data file, wherein the first ledger data includes the equipment corresponding to the first ledger data Identification and the identification of the engineering project it belongs to; obtain the second account data corresponding to the equipment identification and the engineering project identification; when the first account data does not match the second account data The ledger data corresponding to the project ID is updated. Therefore, by matching the account data in the account data file with the old account data, when the two do not match, the account data in the account data file is automatically updated to the power grid information system, and the whole process No manual participation is required, which improves synchronization efficiency and accuracy.

FIG. 7 is a schematic structural diagram of a computing device provided by an embodiment of the present application. As shown in Figure 7, the computing device may include:

a memory 701 storing executable program code;

a processor 702 coupled to the memory 701;

The processor 702 invokes the executable program code stored in the memory 701 to execute the method for updating the ledger of the smart grid information system combining RPA and AI provided by any embodiment of the present application.

This computing device embodiment and the above-mentioned method embodiment are obtained based on the same inventive concept, and relevant parts can be referred to each other. The above computing device embodiments correspond to the method embodiments, and have the same technical effects as the method embodiments. For details, refer to the method embodiments.

The embodiment of the present application discloses a computer-readable storage medium, which stores a computer program, wherein the computer program causes a computer to execute the method for updating the ledger of a smart grid information system combining RPA and AI provided by any embodiment of the present application.

In the various embodiments of the present application, it should be understood that the size of the sequence numbers of the above-mentioned processes does not imply an inevitable sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be implemented in the present application. The implementation of the examples constitutes no limitation.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The above-mentioned integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the whole or part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a memory , including several requests to cause a computer device (which may be a personal computer, a server, or a network device, etc., specifically a processor in the computer device) to execute some or all of the steps of the above methods in the various embodiments of the present application.

This storage medium embodiment and the above-mentioned method embodiment are obtained based on the same inventive concept, and the relevant parts can be referred to each other. The above-mentioned storage medium embodiments correspond to the method embodiments, and have the same technical effects as the method embodiments. For details, refer to the method embodiments.

Those of ordinary skill in the art can understand that the accompanying drawing is only a schematic diagram of an embodiment, and the modules or processes in the accompanying drawing are not necessarily necessary to implement the present application.

Those skilled in the art may understand that: the modules in the apparatus in the embodiment may be distributed in the apparatus in the embodiment according to the description of the embodiment, and may also be located in one or more apparatuses different from this embodiment with corresponding changes. The modules in the foregoing embodiments may be combined into one module, or may be further split into multiple sub-modules.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be The technical solutions described in the foregoing embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the present application.

Claims (18)

1. An updating method of an intelligent power grid information system account combining RPA and AI is characterized by comprising the following steps:

acquiring first account data in an account data file, wherein the first account data comprises a device identifier corresponding to the first account data and an engineering project identifier to which the first account data belongs;

acquiring second account data corresponding to the equipment identifier and the engineering project identifier;

and when the first account data is not matched with the second account data, updating the account data corresponding to the equipment identifier and the engineering project identifier in the power grid information system.

2. The method according to claim 1, wherein the obtaining second account data corresponding to the equipment identifier and the engineering project identifier specifically comprises:

and acquiring second account data corresponding to the equipment identifier and the engineering project identifier from the robot process automation RPA system.

3. The method according to claim 1, wherein the obtaining second account data corresponding to the equipment identifier and the engineering project identifier specifically comprises:

and acquiring second account data corresponding to the equipment identifier and the engineering project identifier from the power grid information system.

4. The method of claim 3, wherein prior to said obtaining the first account data in the account data file, further comprising:

and deleting the historical account data in the RPA system.

5. The method as claimed in claim 1, wherein the updating the account data corresponding to the equipment identifier and the engineering project identifier in the grid information system when the first account data does not match the second account data specifically comprises:

and when the second account data is empty, adding the first account data to an account data list corresponding to the engineering project identifier in the power grid information system.

6. The method as claimed in claim 1, wherein the updating the account data corresponding to the equipment identifier and the engineering project identifier in the grid information system when the first account data does not match the second account data specifically comprises:

and when the first value of any field in the first account data is not matched with the second value of any field in the second account data, updating the value of any field in the power grid information system by using the first value.

7. The method according to any one of claims 1-6, wherein said obtaining first account data in an account data file specifically comprises:

and acquiring first account data from the account data file at a preset frequency.

8. The method of any of claims 1-6, further comprising:

and when the first account data is matched with the second account data, storing the first account data into a backup file, and recording a matching result.

9. An updating device for an intelligent power grid information system account in combination with RPA and AI, comprising:

the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring first account data in an account data file, and the first account data comprises equipment identification corresponding to the first account data and engineering project identification to which the first account data belongs;

the second acquisition module is used for acquiring second account data corresponding to the equipment identifier and the engineering project identifier;

and the updating module is used for updating the account data corresponding to the equipment identifier and the engineering project identifier in the power grid information system when the first account data is not matched with the second account data.

10. The apparatus of claim 9, wherein the second obtaining module is specifically configured to:

and acquiring second account data corresponding to the equipment identifier and the engineering project identifier from the RPA system.

11. The apparatus of claim 9, wherein the second obtaining module is specifically configured to:

and acquiring second account data corresponding to the equipment identifier and the engineering project identifier from the power grid information system.

12. The apparatus of claim 11, further comprising:

and the deleting module is used for deleting the historical account data in the robot process automation RPA system.

13. The apparatus of claim 9, wherein the update module is specifically configured to:

and when the second account data is empty, adding the first account data to an account data list corresponding to the engineering project identifier in the power grid information system.

14. The apparatus of claim 9, wherein the update module is specifically configured to:

and when the first value of any field in the first account data is not matched with the second value of any field in the second account data, updating the value of any field in the power grid information system by using the first value.

15. The apparatus of any one of claims 9-14, wherein the first obtaining module is specifically configured to:

and acquiring first account data from the account data file at a preset frequency.

16. The apparatus of any of claims 9-14, further comprising:

and the storage module is used for storing the first account data into a backup file and recording a matching result when the first account data is matched with the second account data.

17. A computing device, the device comprising:

a memory storing executable program code;

a processor coupled to the memory;

wherein the processor invokes executable program code stored in the memory to perform the smart grid information system (RPA) ledger update method in combination with an AI according to any of claims 1-8.

18. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the smart grid information system ledger updating method in combination with RPA and AI according to any one of claims 1-8.

Images