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

Smart grid information system account updating method and device combining RPA and AI Download PDF

Info

Publication number
CN112150102A
CN112150102A CN202010883960.2A CN202010883960A CN112150102A CN 112150102 A CN112150102 A CN 112150102A CN 202010883960 A CN202010883960 A CN 202010883960A CN 112150102 A CN112150102 A CN 112150102A
Authority
CN
China
Prior art keywords
account data
information system
identifier
grid information
engineering project
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010883960.2A
Other languages
Chinese (zh)
Inventor
汪冠春
胡一川
褚瑞
李玮
张翼
房冬冬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Benying Network Technology Co Ltd
Beijing Laiye Network Technology Co Ltd
Original Assignee
Beijing Benying Network Technology Co Ltd
Beijing Laiye Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Benying Network Technology Co Ltd, Beijing Laiye Network Technology Co Ltd filed Critical Beijing Benying Network Technology Co Ltd
Priority to CN202010883960.2A priority Critical patent/CN112150102A/en
Publication of CN112150102A publication Critical patent/CN112150102A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23Updating
    • G06F16/2358Change logging, detection, and notification
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/275Synchronous replication
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00Pattern recognition
    • G06F18/20Analysing
    • G06F18/22Matching criteria, e.g. proximity measures
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/06Energy or water supply

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Tourism & Hospitality (AREA)
  • Health & Medical Sciences (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Evolutionary Biology (AREA)
  • Water Supply & Treatment (AREA)
  • General Health & Medical Sciences (AREA)
  • Public Health (AREA)
  • Evolutionary Computation (AREA)
  • Primary Health Care (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Bioinformatics & Computational Biology (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Computing Systems (AREA)
  • Artificial Intelligence (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application provides an updating method and device for an intelligent power grid information system account by combining RPA and AI, wherein the method comprises 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. Therefore, by matching the account data in the account data file with the old account data, when the account data and the old account data are not matched, the account data in the account data file is automatically updated to the power grid information system, the whole process does not need manual participation, and the synchronization efficiency and the accuracy are improved.

Description

Smart grid information system account updating method and device combining RPA and AI
Technical Field
The application relates to the technical field of power grids, in particular to an updating method and device for an intelligent power grid information system account by combining RPA and AI.
Background
Robot Process Automation (RPA) is a new type of artificial intelligent virtual Process Automation robot, used to simulate human operation on computer and automatically execute Process tasks according to rules, and RPA can be widely applied to various fields requiring Process Automation, such as power grid field.
Artificial Intelligence (AI) is a technical science that studies and develops theories, methods, techniques and application systems for simulating, extending and expanding human Intelligence.
In the field of power grid electronic transfer service, it is usually necessary to synchronize the account data into the power grid information system. Currently, manual entry systems are mainly used. Because manual operation is more in the process of recording the system, the efficiency is low, and the accuracy cannot be guaranteed.
Disclosure of Invention
The application provides an updating method and device for an intelligent power grid information system account by combining RPA and AI. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a smart grid information system account updating method in combination with an RPA and an AI, including:
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.
According to the method for updating the smart grid information system account by combining the RPA and the AI, first account data in an account data file is obtained, wherein the first account data comprises a device identifier corresponding to the first account data and an affiliated engineering project identifier; 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. Therefore, by matching the account data in the account data file with the old account data, when the account data and the old account data are not matched, the account data in the account data file is automatically updated to the power grid information system, the whole process does not need manual participation, and the synchronization efficiency and the accuracy are improved.
In a possible implementation manner of the embodiment of the first aspect of the present application, the acquiring second account data corresponding to the device identifier and the engineering project identifier specifically includes:
and acquiring second account data corresponding to the equipment identifier and the engineering project identifier from the robot process automation RPA system.
In a possible implementation manner of the embodiment of the first aspect of the present application, the acquiring second account data corresponding to the device identifier and the engineering project identifier specifically includes:
and acquiring second account data corresponding to the equipment identifier and the engineering project identifier from the power grid information system.
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:
and deleting the historical account 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 is not matched with the second account data, updating the account data corresponding to the device identifier and the engineering project identifier in the power grid information system specifically includes:
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.
In a possible implementation manner of the embodiment of the first aspect of the present application, when the first account data is not matched with the second account data, updating the account data corresponding to the device identifier and the engineering project identifier in the power grid information system specifically includes:
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.
In a possible implementation manner of the embodiment of the first aspect of the present application, the acquiring first account data in the account data file specifically includes:
and acquiring first account data from the account 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:
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.
In a second aspect, an embodiment of the present application provides an apparatus for updating a smart grid information system account in combination with an RPA and an AI, including:
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.
According to the intelligent power grid information system account updating device combining the RPA and the AI, first account data in an account data file are obtained, wherein the first account data comprise equipment identifications corresponding to the first account data and project identifications belonging to the equipment identifications; 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. Therefore, by matching the account data in the account data file with the old account data, when the account data and the old account data are not matched, the account data in the account data file is automatically updated to the power grid information system, the whole process does not need manual participation, and the synchronization efficiency and the accuracy are improved.
In a possible implementation manner of the embodiment of the second aspect of the present application, 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.
In a possible implementation manner of the embodiment of the second aspect of the present application, 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.
In one possible implementation manner of the embodiment of the second aspect of the present application, the apparatus may further include:
and the deleting module is used for deleting the historical account data in the robot process automation RPA system.
In a possible implementation manner of the embodiment of the second aspect of the present application, 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.
In a possible implementation manner of the embodiment of the second aspect of the present application, 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.
In a possible implementation manner of the embodiment of the second aspect of the present application, the first obtaining module is specifically configured to:
and acquiring first account data from the account data file at a preset frequency.
In one possible implementation manner of the embodiment of the second aspect of the present application, the apparatus may further include:
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.
In a third aspect, an embodiment of the present application provides a computing device, where the device includes:
a memory storing executable program code;
a processor coupled to the memory;
the processor calls the executable program code stored in the memory to execute the smart grid information system account updating method combining the RPA and the AI according to the first aspect.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the method for updating a smart grid information system account in combination with RPA and AI as described in the first aspect.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application and are not to be construed as limiting the application.
Fig. 1 is a schematic flowchart of an update method of an intelligent grid information system account combining an RPA and an AI according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of another method for updating a smart grid information system account by combining an RPA and an AI according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart of another method for updating a smart grid information system account by combining an RPA and an AI according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart of another method for updating a smart grid information system account by combining an RPA and an AI according to an embodiment of the present disclosure;
fig. 5 is a schematic flowchart of another method for updating a smart grid information system account by combining an RPA and an AI according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an apparatus for updating a smart grid information system account in combination with an RPA and an AI according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of a computing device according to an embodiment of the present application.
Detailed Description
The technical solution in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the described embodiments are merely a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without inventive step, are within the scope of the present disclosure.
It should be noted that the terms "comprises" and "comprising," and any variations thereof, in the examples and figures herein, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
In the field of power grid electronic transfer service, it is usually necessary to synchronize the account data into the power grid information system. Currently, manual entry systems are mainly used. Because manual operation is more in the process of recording the system, the efficiency is low, and the accuracy cannot be guaranteed.
To solve the problem, the embodiment of the present application provides an updating method for a smart grid information system account in combination with an RPA and an AI, so as to implement automatic synchronization of updated account data into a grid information system.
RPA is a business process automation technology based on software robots and Artificial Intelligence (AI). The operation of a human on a computer is simulated through specific 'robot software', and the flow task is automatically executed according to the rule.
Fig. 1 is a schematic flowchart of an update method of an intelligent grid information system account combining an RPA and an AI according to an embodiment of the present disclosure.
The intelligent power grid information system account updating method combining the RPA and the AI can be executed by the RPA robot, so that data in an account data file and account data synchronized to a power grid information system are automatically matched, and when the data are not matched, the account data in the account data file are updated to the power grid information system, and the changed account data are automatically synchronized to the power grid information system.
As shown in fig. 1, the method for updating the smart grid information system account by combining RPA and AI includes:
step 101, obtaining first account data in an account data file, wherein the first account data comprises an equipment identifier corresponding to the first account data and an engineering project identifier to which the first account data belongs.
In the electronic transfer process in the field of power grids, related personnel need to enter equipment account information. In this embodiment, the account data of the account data file is the device account information recorded in the electronic handover process. That is, in the electronic transfer process, one or more pieces of account data entered are put into the account data file. The account data file can be an Excel form file, or other form files.
In the concrete implementation, a template of the account data can be preset, and in the electronic transfer process, when account information needs to be entered, related personnel can enter the account data in the template of the account data.
In this embodiment, the account data in the account data file includes values for a plurality of fields, such as device model, manufacturer of the manufacturing device, technical parameters, installation location of the device, maintenance personnel information, and the like. Since the account data in the account data file is generated during the electronic transfer process of the engineering project, the account data generated during the electronic transfer process may further include the affiliated engineering project identification, such as project number.
In this embodiment, the RPA system may log in the system where the account data file is located, then obtain account data in the account data file, which is referred to as first account data, and store the obtained first account data in the local cache. The first account data comprises equipment identification corresponding to the first account data and the affiliated engineering project identification. The device identifier may be a model, an installation location, or the like of the device, or another identifier capable of uniquely identifying the uniqueness of the device in the engineering project.
And 102, acquiring second account data corresponding to the equipment identifier and the engineering project identifier.
Since the equipment identifier and the engineering project identifier can uniquely identify one piece of account data, the old account data can be queried to obtain the account data corresponding to the equipment identifier and the engineering project identifier, which is referred to as second account data for easy distinction.
Here, the old account data is account data corresponding to each engineering project, and may be understood as account data corresponding to each engineering project in the grid information system. In a specific implementation, the RPA system may first obtain, according to the engineering item identifier included in the first account data, account data corresponding to the engineering item identifier from old account data, and then search, from the account data corresponding to the engineering item identifier, account data corresponding to the device identifier included in the first account data, that is, second account data.
And 103, 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.
After acquiring first account data and second account data, can compare first account data and second account data, if first account data and second account data mismatch, show that first account data has changed relative second account data, then usable first account data is updated in the electric wire netting information system, the account data that corresponds with equipment identification and engineering project identification.
Specifically, in the power grid information system, the RPA system first finds out the account data corresponding to the engineering project identifier, then finds out the account data corresponding to the device identifier included in the first account data from the account data corresponding to the engineering project identifier, and then updates the account data corresponding to the device identifier and the engineering project identifier found out corresponding to the first account data.
And when updating, the first account data can be used for covering account data corresponding to the equipment identifier and the engineering project identifier in the power grid information system.
It should be noted that, when there are multiple pieces of account data in the account data file, the RPA system may obtain all the account data in the account data file, and cache the data locally, and then perform the above operations on the cached account data one by one, so as to determine whether each piece of account data recorded in the account data file changes compared with the account data in the grid information system.
In the embodiment of the application, first account data in an account data file is acquired, wherein the first account data comprises an equipment 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. Therefore, by matching the account data in the account data file with the old account data, when the account data and the old account data are not matched, the account data in the account data file is automatically updated to the power grid information system, the whole process does not need manual participation, and the synchronization efficiency and the accuracy are improved.
In practical application, if the RPA system logs in the grid information system each time to obtain the second account data, the synchronization efficiency is obviously affected. Based on this, in one embodiment of the present application, the RPA system may locally store the account data synchronized with the grid information system, and then locally acquire the second account data, and match the first account data with the second account data. Fig. 2 is a schematic flow chart of another method for updating a smart grid information system account with RPA and AI according to an embodiment of the present disclosure.
As shown in fig. 2, the method includes:
step 201, obtaining first account data in an account data file, wherein the first account data includes an equipment identifier corresponding to the first account data and an engineering project identifier to which the first account data belongs.
In this embodiment, step 201 is similar to step 101, and therefore is not described herein again.
Step 202, acquiring second account data corresponding to the equipment identifier and the engineering project identifier from the RPA system.
In this embodiment, the RPA system acquires, for the first time, the account data in the account data file from the system in which the account data file is located, stores the account data in the local area, and synchronizes all the account data in the acquired account data file to the grid information system. Then, each time the account data in the account data file is acquired, whether the local account data needs to be updated or not can be judged, if so, the local account data is updated, and the account data needing to be updated is synchronously updated to the power grid information system. Thus, the RPA system stores the same ledger data as the grid information system.
Then, the RPA system may first obtain the account data corresponding to the engineering project identifier included in the first account data from the local, and then find out the account data corresponding to the device identifier included in the first account data, that is, the second account data.
And step 203, 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.
In this embodiment, the RPA system compares the first account data with the second account data obtained from the local. And when the first account data and the second account data are not matched, updating the account data corresponding to the equipment identifier and the engineering project identifier in the power grid information system by using the first account data.
Specifically, in the power grid information system, the RPA system first finds out the account data corresponding to the engineering project identifier, then finds out the account data corresponding to the device identifier included in the first account data from the account data corresponding to the engineering project identifier, and then updates the account data corresponding to the device identifier and the engineering project identifier found out corresponding to the first account data.
For subsequent continuation of the determination locally at the RPA system, the RPA system updates the second account data obtained locally with the first account data, so that the RPA system has the same account data as the grid information system.
When the first account data is matched with the second account data, the RPA system does not need to log in the power grid information system, and does not need to update the account data in the power grid information system.
For example, if the account data file includes 10 pieces of account data, the RPA system obtains the 10 pieces of account data and caches the 10 pieces of account data locally, and if the 10 pieces of account data are judged not to be local, the 10 pieces of account data are synchronized to the grid information system and stored in the locally maintained account data file which is the same as the grid information system. After 1 minute, the RPA system acquires 11 pieces of account data from the account data file, and through comparison with 10 pieces of locally stored account data, finds that 1 piece of account data has changed, and then can update the 1 piece of account data into the power grid information system and into a locally maintained account data file which is the same as the power grid information system.
If the data file of the machine account has a plurality of pieces of machine account data, the RPA system can judge all the machine account data in the machine account data and then synchronize the machine account data needing to be updated into the power grid information system during specific implementation. Of course, after each piece of account data is judged, if the data needs to be synchronized into the power grid information system, the data is updated into the power grid information system, and then another piece of account data in the account data file is judged until the judgment of all the account data in the account data file is completed.
In the embodiment of the application, when the second account data corresponding to the device identifier and the engineering project identifier is obtained, the second account data corresponding to the device identifier and the engineering project identifier can be obtained from the RPA system. Therefore, the RPA system matches the local corresponding account data with the account data in the account data file, and updates the corresponding account data in the power grid information system when the local corresponding account data is not matched with the account data, so that the second data does not need to be acquired from the power grid information system every time, and the updating efficiency or the synchronization efficiency is improved.
In practical application, if the RPA system maintains the same account data as the grid information system, when the amount of the account data is large, it obviously occupies a large amount of memory of the RPA system. In view of the memory aspect of the RPA system, in one embodiment of the present application, the second account data may be obtained from the grid information system when the second account data is obtained.
In this embodiment, the account data of the equipment used in each engineering project is synchronized into the power grid information system, that is, the account data of the equipment used in each engineering project is stored in the power grid information system.
Specifically, the RPA system acquires first account data in the account data file from a system where the account data file is located, caches the first account data locally, logs in a power grid information system, acquires second account data corresponding to the equipment identifier and the engineering project identifier from the power grid information system according to the equipment identifier and the engineering project identifier included in the first account data, and caches the second account data locally. And then, the RPA system compares the locally cached first account data with the second account data, and if the locally cached first account data and the second account data are not matched, the first account data is utilized to update the second account data in the power grid information system.
If the data file of the account has a plurality of pieces of first account data, the RPA system can cache the plurality of pieces of first account data in the data file of the account to the local, then determine the equipment identifier and the affiliated project identifier included in each piece of first account data, then obtain a plurality of pieces of second account data from the power grid information system, and cache the second account data to the local. And then, comparing the first account data with the second account data, wherein the equipment identifier and the engineering project identifier are the same, determining the second account data needing to be updated, and then updating the corresponding second account data in the power grid information system according to the first account data.
Of course, the RPA system may also obtain corresponding second account data from the grid information system for a certain first account data, and when the two are not matched, update the corresponding second account data in the grid information system according to the first account data. Then, repeating the above operation for the next piece of first account data until all the first account data are traversed.
In the embodiment of the application, when the second account data corresponding to the equipment identifier and the engineering project identifier is obtained, the second account data corresponding to the equipment identifier and the engineering project identifier can be obtained from the power grid information system. Therefore, the RPA system acquires the second account data from the power grid information system, and the occupation of the memory of the RPA system can be reduced.
In an embodiment of the present application, in order to improve the updating accuracy, when second account data corresponding to the device identifier and the engineering project identifier is obtained, the second account data is obtained from the grid information system, and then before the first account data in the account data file is obtained, the historical account data in the RPA system is deleted, that is, the RPA system deletes the locally cached historical account data. The historical account data can be understood as the first account data in the account data file last acquired by the RPA system.
In the embodiment of the application, when the second account data corresponding to the equipment identifier and the engineering project identifier is obtained, the second account data is obtained from the power grid information system, and before the first account data in the account data file is obtained, the historical account data in the RPA system is deleted. Therefore, the memory is saved, the traversal of the traversed historical account data can be avoided, and the accuracy of updating the account data to the system is improved.
In practical application, a new device may be added in an engineering project, and for the first account data of the new device, the corresponding second account data cannot be obtained from the power grid information system. To solve the problem, the following description is made with reference to fig. 3, and fig. 3 is a schematic flow chart of another method for updating a smart grid information system account with RPA and AI provided in the embodiment of the present application.
As shown in fig. 3, the method includes:
step 301, obtaining first account data in an account data file, where the first account data includes an equipment identifier corresponding to the first account data and an engineering project identifier to which the first account data belongs.
Step 302, acquiring second account data corresponding to the equipment identifier and the engineering project identifier.
In this embodiment, steps 301 to 302 are similar to steps 101 to 102, and therefore are not described herein again.
And 303, 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.
In practical application, equipment may be newly added in an engineering project, and thus, in an electronic transfer process, the entered account data cannot be queried in a power grid information system obviously.
And if the second account data is searched from the power grid information system, the RPA system searches the account data corresponding to the engineering project identifier in the power grid information system according to the fact that the first account data comprises the engineering project identifier, then searches the account data corresponding to the engineering project identifier according to the equipment identifier included in the first account data, and if the account data corresponding to the equipment identifier which is not searched, namely the second account data is empty, the first account data is added into an account data list corresponding to the engineering project identifier in the power grid information system.
If the RPA system stores the account data which is the same as the power grid information system, the account data corresponding to the engineering project identifier is searched according to the engineering project identifier, and then the account data corresponding to the equipment identifier is searched in the account data corresponding to the engineering project identifier according to the equipment identifier. And if the account data corresponding to the equipment identifier is not found, namely the second account data is empty, adding the first account data into an account data list corresponding to the engineering project identifier in the power grid information system, and adding the first account data into an account data list corresponding to the engineering project identifier stored in the RPA system.
In the embodiment of the application, when the second account data is empty, the first account data is added to the account data list corresponding to the engineering project identifier in the power grid information system, so that when the first account data is for the newly added equipment, the first account data is added to the account data list corresponding to the engineering project identifier in the power grid information system, the account data of the newly added equipment is automatically synchronized to the power grid information system, and the synchronization accuracy and efficiency are improved.
To improve the updating accuracy, in one embodiment of the present application, if the second account data is not empty, the updating can be determined by comparing the values of the corresponding fields of the first account data and the second account data. Fig. 4 is a schematic flow chart of another method for updating a smart grid information system account with RPA and AI according to an embodiment of the present disclosure.
As shown in fig. 4, the method includes:
step 401, obtaining first account data in an account data file, where the first account data includes an equipment identifier corresponding to the first account data and an engineering project identifier to which the first account data belongs.
And 402, acquiring second account data corresponding to the equipment identifier and the engineering project identifier.
In this embodiment, steps 401 to 402 are similar to steps 101 to 102, and thus are not described herein again.
Step 403, 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.
In this embodiment, the account data may include values of a plurality of fields, and the values of corresponding fields in the first account data and the second account data may be compared to determine whether there is any inconsistency between the values of one or more of the fields. And when the first value of any field in the first account data is not matched with the second value of the field in the second account data, updating the value of the field in the power grid information system to the first value of the field in the first account data.
For example, the account data includes the device model, the device manufacturer, the technical parameters, the installation position information, and the like, and then the device model, the device manufacturer, the technical parameters, and the installation position of the first account data can be respectively compared with the device model, the device manufacturer, the technical parameters, and the installation position information in the second account data. And when the installation position A in the first account data is not matched with the installation position B in the second account data, updating the installation position B in the account data corresponding to the equipment identifier and the engineering project identifier included in the first account data in the power grid information system to be the installation position A.
It should be noted that, as application needs, when a certain field is added to the first account data, the value of the field may be added to the account data corresponding to the equipment identifier and the engineering project identifier in the grid information system.
In the embodiment of the application, when a first value of any field in the first account data is not matched with a second value of any field in the second account data, the value of any field in the power grid information system is updated by using the first value. Therefore, when the value of a field in the first account data is not matched with the value of the field in the second account data, the value of the field in the corresponding account data in the power grid information system is updated by using the value of the field in the first account data, so that the changed value of the field is automatically updated to the telecommunication information system, and the updating accuracy is improved.
To improve the timeliness of the update, in one embodiment of the present application, the first account data can be obtained from the account data file at a predetermined frequency. For example, the account data in the account data file is acquired every 1 minute and cached locally, so as to compare the account data with the corresponding second account data.
The preset frequency may be set according to needs, and this embodiment does not limit this.
In the embodiment of the application, when the first account data in the account data file is acquired, the first account data is acquired from the account data file at a preset frequency, so that the updating timeliness is improved.
In order to facilitate subsequent tracing, in an embodiment of the present application, when the first account data matches with the second account data, the first account data may be stored in the backup file, and a matching result may be recorded. Fig. 5 is a schematic flow chart of another method for updating a smart grid information system account with RPA and AI according to an embodiment of the present disclosure.
As shown in fig. 5, the method includes:
step 501, obtaining first account data in an account data file, wherein the first account data includes an equipment identifier corresponding to the first account data and an engineering project identifier to which the first account data belongs.
Step 502, acquiring second account data corresponding to the equipment identifier and the engineering project identifier.
Step 503, 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.
In this embodiment, steps 501 to 503 are similar to steps 101 to 103, and therefore are not described herein again.
Step 504, when the first account data is matched with 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 indicates that the first account data matches the second account data, and the first account data is stored in the backup file. The backup file can be stored in the RPA system or the power grid information system.
In a 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 matched with the corresponding second account data can be stored in the backup file, and the matching result corresponding to each account data is recorded.
In the embodiment of the application, when the first account data is matched with the second account data, the first account data is stored in the backup file, and the matching result is recorded. Therefore, even if updating is not needed, the backup file recorded by the first account data can be conveniently traced.
In order to implement the above embodiments, the present application further provides a schematic structural diagram of an update device of an intelligent grid information system account, which combines an RPA and an AI. Fig. 6 is a schematic structural diagram of an apparatus for updating a smart grid information system account, which is provided in an embodiment of the present application and combines RPA and AI.
As shown in fig. 6, the smart grid information system account updating apparatus 600 combining RPA and AI includes: a first acquisition module 610, a second acquisition module 620, and an update module 630.
The first obtaining module 610 is configured to obtain first account data in an account data file, where the first account data includes an equipment identifier corresponding to the first account data and an engineering project identifier to which the first account data belongs;
a second obtaining module 620, configured to obtain second account data corresponding to the equipment identifier and the engineering project identifier;
and an updating module 630, configured to update the account data corresponding to the device 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.
In a possible implementation manner of the embodiment of the present application, the second obtaining module 620 is specifically configured to:
and acquiring second account data corresponding to the equipment identifier and the engineering project identifier from the RPA system.
In a possible implementation manner of the embodiment of the present application, the second obtaining module 620 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.
In a possible implementation manner of the embodiment of the present application, the apparatus may further include:
and the deleting module is used for deleting the historical account data in the robot process automation RPA system.
In a possible implementation manner of the embodiment of the present application, the update module 630 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.
In a possible implementation manner of the embodiment of the present application, the update module 630 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.
In a possible implementation manner of the embodiment of the present application, the first obtaining module 610 is specifically configured to:
and acquiring first account data from the account data file at a preset frequency.
In a possible implementation manner of the embodiment of the present application, the apparatus may further include:
and the storage module is used for storing the first account data into the backup file and recording the matching result when the first account data is matched with the second account data.
The above device embodiment corresponds to the method embodiment, and has the same technical effect as the method embodiment, and for the specific description, refer to the method embodiment. The device embodiment is obtained based on the method embodiment, and for specific description, reference may be made to the method embodiment section, which is not described herein again.
According to the intelligent power grid information system account updating device combining the RPA and the AI, first account data in an account data file are obtained, wherein the first account data comprise equipment identifications corresponding to the first account data and project identifications belonging to the equipment identifications; 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. Therefore, by matching the account data in the account data file with the old account data, when the account data and the old account data are not matched, the account data in the account data file is automatically updated to the power grid information system, the whole process does not need manual participation, and the synchronization efficiency and the accuracy are improved.
Fig. 7 is a schematic structural diagram of a computing device according to an embodiment of the present application. As shown in fig. 7, the computing device may include:
a memory 701 in which executable program code is stored;
a processor 702 coupled to the memory 701;
the processor 702 calls the executable program code stored in the memory 701 to execute the method for updating the smart grid information system account in combination with the RPA and the AI according to any embodiment of the present application.
The embodiment of the computing device and the embodiment of the method are based on the same inventive concept, and the relevant points can be referred to each other. The above embodiment of the computing device corresponds to the embodiment of the method, and has the same technical effect as the embodiment of the method, and for the specific description, reference is made to the embodiment of the method.
The embodiment of the application discloses a computer-readable storage medium which stores a computer program, wherein the computer program enables a computer to execute the method for updating the smart grid information system account in combination with RPA and AI provided by any embodiment of the application.
In various embodiments of the present application, it should be understood that the size of the serial number of each process described above does not mean that the execution sequence is necessarily sequential, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated units, if implemented as software functional units and sold or used as a stand-alone product, may be stored in a computer accessible memory. Based on such understanding, the technical solution of the present application, which is a part of or contributes to the prior art in essence, or all or part of the technical solution, may be embodied in the form of a software product, stored in a memory, including several requests for causing a computer device (which may be a personal computer, a server, a network device, or the like, and may specifically be a processor in the computer device) to execute part or all of the steps of the above-described method of the embodiments of the present application.
The storage medium embodiment and the method embodiment are based on the same inventive concept, and the relevant points can be referred to each other. The storage medium embodiment corresponds to the method embodiment, and has the same technical effect as the method embodiment, and for a detailed description, reference is made to the method embodiment.
Those of ordinary skill in the art will understand that: the figures are merely schematic representations of one embodiment, and the blocks or processes in the figures are not necessarily required to practice the present application.
Those of ordinary skill in the art will understand that: modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, or may be located in one or more devices different from the embodiments with corresponding changes. The modules of the above embodiments may be combined into one module, or 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, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding 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.
CN202010883960.2A 2020-08-28 2020-08-28 Smart grid information system account updating method and device combining RPA and AI Pending CN112150102A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010883960.2A CN112150102A (en) 2020-08-28 2020-08-28 Smart grid information system account updating method and device combining RPA and AI

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010883960.2A CN112150102A (en) 2020-08-28 2020-08-28 Smart grid information system account updating method and device combining RPA and AI

Publications (1)

Publication Number Publication Date
CN112150102A true CN112150102A (en) 2020-12-29

Family

ID=73889505

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010883960.2A Pending CN112150102A (en) 2020-08-28 2020-08-28 Smart grid information system account updating method and device combining RPA and AI

Country Status (1)

Country Link
CN (1) CN112150102A (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106202425A (en) * 2016-07-12 2016-12-07 国网北京市电力公司 Data processing method and device and mobile terminal
CN108536770A (en) * 2018-03-22 2018-09-14 广东电网有限责任公司佛山供电局 A kind of distribution looped network account automatic generation method based on Distributing Network GIS model
CN109242254A (en) * 2018-08-08 2019-01-18 北京市安全生产信息中心 A kind of enterprise's account approaches to IM and device, readable storage medium storing program for executing
US20190266057A1 (en) * 2018-02-27 2019-08-29 Veritas Technologies Llc Systems and methods for performing a database backup for repairless restore

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106202425A (en) * 2016-07-12 2016-12-07 国网北京市电力公司 Data processing method and device and mobile terminal
US20190266057A1 (en) * 2018-02-27 2019-08-29 Veritas Technologies Llc Systems and methods for performing a database backup for repairless restore
CN108536770A (en) * 2018-03-22 2018-09-14 广东电网有限责任公司佛山供电局 A kind of distribution looped network account automatic generation method based on Distributing Network GIS model
CN109242254A (en) * 2018-08-08 2019-01-18 北京市安全生产信息中心 A kind of enterprise's account approaches to IM and device, readable storage medium storing program for executing

Similar Documents

Publication Publication Date Title
CN104423960A (en) Continuous project integration method and continuous project integration system
CN108153784A (en) Synchrodata treating method and apparatus
CN107016019B (en) Database index creation method and device
CN106934048A (en) Online data moving method, agent node
CN109472044A (en) A kind of cable calculation amount method, system and medium based on BIM
CN106682017B (en) Database updating method and device
CN111917834A (en) Data synchronization method and device, storage medium and computer equipment
CN111726249B (en) Configuration file processing method and device of network equipment
CN110083504B (en) Running state monitoring method and device for distributed tasks
CN109165865B (en) Main distribution integrated model checking method and system based on boundary switch connectivity analysis
CN112764874B (en) Virtual machine server information acquisition method based on CMDB configuration management system
CN111209652B (en) Method and device for constructing time sequence of static equipment model of power system
CN112395360A (en) Data synchronization method, device, apparatus and medium based on non-relational database
CN112150102A (en) Smart grid information system account updating method and device combining RPA and AI
CN114595286A (en) Data synchronization method and device, electronic equipment and storage medium
CN108900347B (en) Cluster initialization configuration method, device, system, equipment and readable storage medium
CN113793063A (en) Method and device for detecting conflict of power distribution network planning project schemes
CN105373804A (en) A human body part positioning method and system based on multi-dimensional space quick clustering
CN109684331A (en) A kind of object storage meta data management device and method based on Kudu
CN112463786B (en) Data synchronization method, system, server and storage medium
CN113239074B (en) Physical port positioning method, physical port positioning device, electronic equipment and storage medium
CN115599793A (en) Method, device and storage medium for updating data
CN115658402A (en) Test case management method and device, electronic equipment and readable storage medium
CN101426220A (en) Method, apparatus and system for base station cutover
CN112000671A (en) Block chain-based database table processing method, device and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination