Power grid model multi-user parallel maintenance method and system

Abstract

The invention discloses a multi-user parallel maintenance method and system for a power grid model. The method comprises the following steps: acquiring maintained model branches from an offline maintenance library to form a to-be-published model range; using the latest running real-time library backup file to restore and generate an intermediate maintenance library; the latest running real-time library backup file is generated by carrying out backup on the running real-time library after the last successful release and contains the power grid model data in the complete running real-time library; the object having the reference relationship with all the model branch objects in the model range is a reference object, and if the reference object does not exist in the intermediate maintenance library, the model branch where the reference object is located is added into the model range to be published to form a corrected model range; according to the corrected model range, corresponding model branches are extracted from the offline maintenance library and combined into an intermediate maintenance library; and the power grid model is verified and published on the intermediate maintenance library, and the operation real-time library after successful publishing is backed up to generate the latest operation real-time library backup file, so that the maintenance efficiency and accuracy of the power grid model are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of power grid dispatching automation systems, and in particular relates to a multi-user parallel maintenance method and system for a power grid model. Background Art

[0002] In the power grid dispatching automation system, the power grid model is stored in an offline maintenance library. The power grid model includes power grid physical object models such as regions, loads, intervals, plants, reference voltages, equipment, and measurements, as well as reference and inclusion relationships between objects. The relationships between physical objects include symbiotic inclusion and non-symbiotic reference relationships. Physical objects in symbiotic relationships form a hierarchical tree structure, and branches at each level may be associated through non-symbiotic reference relationships.

[0003] Operations and maintenance personnel need to promptly modify the grid model in the offline maintenance library based on changes in the grid structure. Modifications to the offline maintenance library include adding and deleting grid model objects, updating attribute fields, and setting relationship fields. The modified model is verified for correctness and integrity before being published to the online real-time database to ensure consistency between the real-time database grid model and the actual grid.

[0004] In existing technologies, operators verify and publish models based on the entire repository, with no ability to select the scope of model verification and release. When multiple operators participate in maintenance, they must wait until all have completed their modifications to the offline maintenance repository before unified verification and release. If a model maintained by a particular operator is incomplete or contains parameter errors, verification will fail and the operator must make modifications before re-verification and release. This maintenance approach suffers from low parallelism, resulting in low operator efficiency and failing to meet the model maintenance requirements of modern power grids.

[0005] There are also improved maintenance methods that require pre-setting user permissions and maintenance scopes, pre-splitting the maintenance model, and performing model modifications and verification on the split models. This can lead to problems with model modifications, such as not being able to see related models and parameters modified by other users in a timely manner, and model conflicts when publishing models to the real-time database. Summary of the Invention

[0006] In order to solve the deficiencies in the prior art, the present invention provides a method and system for multi-user parallel maintenance of a power grid model, so as to improve the efficiency and accuracy of power grid model maintenance.

[0007] The present invention adopts the following technical solutions.

[0008] The present invention proposes a multi-user parallel maintenance method for a power grid model. The power grid model is divided into multiple model branches according to a hierarchical structure. There is a symbiotic relationship between objects in the same model branch, and there is a reference relationship between objects in different model branches. Operation and maintenance personnel maintain the model branches in the power grid model in an offline maintenance library. The method includes:

[0009] Obtain the maintained model branches from the offline maintenance library to form the model range to be released;

[0010] Use the latest real-time database backup file to restore and generate the intermediate maintenance database; the latest real-time database backup file is generated by backing up the real-time database after the most recent successful release and contains the complete power grid model data in the real-time database;

[0011] The object that has a reference relationship with the objects of all model branches within the model scope is regarded as the reference object. If the reference object does not exist in the intermediate maintenance library, the model branch where the reference object is located is added to the model scope to be released to form the revised model scope;

[0012] According to the revised model range, the corresponding model branch is extracted from the offline maintenance library and merged into the intermediate maintenance library; the power grid model is verified and published on the intermediate maintenance library, and the running real-time library after successful publication is backed up to generate the latest running real-time library backup file.

[0013] Preferably, the model branches after maintenance are obtained from the offline maintenance library to form the model range to be released, including:

[0014] The operation and maintenance personnel maintain the model branches in the power grid model in the offline maintenance library, using the top-level object of each model branch to represent the model branch and marking the maintenance type on the top-level object of the model branch; the maintenance types include: addition, modification and deletion;

[0015] Traversing the top-level objects of each model branch in the offline maintenance library, the operation and maintenance personnel select the model branches to be released from the top-level objects marked with the maintenance type to form the model range to be released.

[0016] Preferably, the following rules are used to mark the maintenance type on the top-level objects of the model branch:

[0017] 1) When adding a new model branch in the offline maintenance library, mark the maintenance type of the model branch as "new" on the top-level object;

[0018] 2) When deleting a model branch in the offline maintenance library, mark the model branch maintenance type as "delete" on the top-level object;

[0019] 3) If an object in an existing model branch of the offline maintenance library is modified, or a lower-level object other than the top-level object is added / deleted on an existing model branch, the model branch maintenance type is marked as "modified" on the top-level object;

[0020] 4) For a model branch that has been marked as "new", when modifying an object on the model branch, the maintenance type mark on the top-level object remains "new". When deleting the model branch, the maintenance type mark on the top-level object is cleared.

[0021] 5) For the model branch marked as "modify", delete the model branch and change the maintenance type mark on the top-level object to "delete";

[0022] 6) When the power grid model is successfully published, clear the maintenance type mark on the top-level object of the published model branch in the offline maintenance library.

[0023] Preferably, the model scope to be released is composed of model branches corresponding to the top-level objects marked with the maintenance type, including:

[0024] Construct a maintenance type mark table, including: the table ID of the table where the top-level object is located, the primary key of the top-level object, the maintenance type, and the check mark;

[0025] The operation and maintenance personnel select the model branches marked as "No" from the maintenance type mark table to form the model range to be released.

[0026] Preferably, when multiple operation and maintenance personnel determine the model range in parallel and submit verification and release requests, the multiple model ranges are added to the end of the queue in the order of the time when the verification and release requests are submitted, and the model ranges are serially taken out of the queue during verification and release.

[0027] Preferably, the intermediate maintenance library is restored using the real-time library backup file generated after the most recent successful model release; wherein the real-time library backup file contains the complete power grid model data in the real-time library, including:

[0028] Check whether the last model release was successful. If successful, the power grid models of the current intermediate maintenance library and the running real-time library are the same. Use the current intermediate maintenance library and no restoration is required. If failed, there are differences between the power grid models of the current intermediate maintenance library and the running real-time library. Use the real-time library backup file generated after the most recent successful model release to restore the intermediate maintenance library.

[0029] Preferably, an object that has a reference relationship with objects in all model branches within the model scope is used as a reference object. If the reference object does not exist in the intermediate maintenance library, the model branch where the reference object is located is added to the model scope to be released, forming a revised model scope, including:

[0030] Based on the model range to be released, the offline maintenance library is traversed according to the maintenance mark, and objects with symbiotic relationships in all model branches within the model range are extracted from the offline maintenance library;

[0031] The object that has a reference relationship with the extracted object is used as the reference object, and the primary key of the reference object is extracted; if the primary key does not exist in the intermediate maintenance library, it is determined whether the model branch where the reference object is located is within the model scope. If the model branch corresponding to the reference object does not exist within the model scope, the model branch where the reference object is located is added to the model scope to be released to form a revised model scope.

[0032] Preferably, based on the model range to be released, the offline maintenance library is traversed according to the maintenance mark, and objects with symbiotic relationships in all model branches within the model range are extracted from the offline maintenance library, including:

[0033] For the model branches marked as "new" and "modified" within the model scope, first traverse the top-level objects of each model branch to obtain the sub-objects that have a symbiotic relationship with the top-level object; then traverse each sub-object to obtain the sub-objects that have a symbiotic relationship with the sub-object; recursively traverse until the leaf object; extract all the traversed objects;

[0034] Extracts the top-level objects of a model branch that has been marked as "deleted" for model-wide maintenance.

[0035] Preferably, extracting corresponding model branches from the offline maintenance library and merging them into the intermediate maintenance library according to the revised model range includes:

[0036] For model branches marked as "new" and "modified", check whether the primary keys of all objects contained in the model branch exist in the intermediate maintenance library. Objects whose primary keys do not exist are added to the intermediate maintenance library. The primary keys, attribute field values, and reference field values ​​of the newly added objects in the intermediate maintenance library are kept consistent with the corresponding field values ​​in the offline maintenance library. For objects whose primary keys exist, compare the attribute field values ​​and reference field values ​​of the objects in the offline maintenance library and the intermediate maintenance library to see if they are the same. If they are different, use the attribute field values ​​and reference field values ​​in the offline maintenance library to overwrite the corresponding field values ​​in the intermediate maintenance library.

[0037] Delete all model branches marked as "delete" in the intermediate maintenance repository.

[0038] The present invention also proposes a multi-user parallel maintenance system for a power grid model, the system comprising:

[0039] Model scope division module, intermediate maintenance library construction module, model scope modification module and verification and release module;

[0040] The model range division module is used to obtain the maintained model branches from the offline maintenance library to form the model range to be released;

[0041] The intermediate maintenance library construction module is used to restore the intermediate maintenance library using the latest real-time library backup file. The latest real-time library backup file is a backup of the real-time library generated after the most recent successful release and contains the complete power grid model data in the real-time library.

[0042] The model scope correction module is used to take objects that have a reference relationship with objects in all model branches within the model scope as reference objects. If the referenced object does not exist in the intermediate maintenance library, the model branch where the referenced object is located is added to the model scope to be released to form the corrected model scope.

[0043] The verification and release module is used to extract the corresponding model branches from the offline maintenance library and merge them into the intermediate maintenance library according to the revised model range; verify and release the power grid model on the intermediate maintenance library, and back up the running real-time library after successful release to generate the latest running real-time library backup file.

[0044] Preferably, the model range partitioning module includes: a marking unit and a selection unit;

[0045] The marking unit is used by operation and maintenance personnel to maintain the model branches in the power grid model in the offline maintenance library. The top-level object of each model branch represents the model branch, and the maintenance type is marked on the top-level object of the model branch. The maintenance types include: addition, modification and deletion.

[0046] The selection unit is used to traverse the top-level objects of each model branch in the offline maintenance library. The operation and maintenance personnel select the model branches to be released from the top-level objects marked with the maintenance type to form the model range to be released.

[0047] Preferably, the intermediate maintenance library construction module includes a detection unit and a generation unit. The detection unit is used to detect whether the last model release was successful. If successful, the power grid models of the current intermediate maintenance library and the running real-time library are the same, and the current intermediate maintenance library is used without restoration. If failed, there are differences between the power grid models of the current intermediate maintenance library and the running real-time library. The running real-time library backup file generated after the most recent successful model release is used to restore the generated intermediate maintenance library.

[0048] Preferably, the model range correction module includes a first traversal unit, a second traversal unit and a correction unit;

[0049] The first traversal unit is used to traverse the offline maintenance library based on the model range to be released and the maintenance mark, and extract objects with symbiotic relationships in all model branches within the model range from the offline maintenance library;

[0050] The second traversal unit is used to take an object that has a reference relationship with the object extracted by the first traversal unit as a reference object and extract a primary key of the reference object;

[0051] The correction unit is used to determine whether the model branch where the referenced object is located is within the model scope if the primary key extracted by the second traversal unit does not exist in the intermediate maintenance library. If the model branch corresponding to the referenced object does not exist within the model scope, the model branch where the referenced object is located is added to the model scope to be released to form a corrected model scope.

[0052] Preferably, the verification and release module includes a merging unit and a verification and release unit;

[0053] The merge unit is used to check whether the primary keys of all objects contained in the model branches marked as "new" and "modified" exist in the intermediate maintenance library, and add objects whose primary keys do not exist to the intermediate maintenance library. The primary keys, attribute field values, and reference field values ​​of the newly added objects in the intermediate maintenance library are consistent with the corresponding field values ​​in the offline maintenance library. For objects with existing primary keys, the attribute field values ​​and reference field values ​​of the objects in the offline maintenance library and the intermediate maintenance library are compared to see if they are the same. If they are different, the attribute field values ​​and reference field values ​​in the offline maintenance library are used to overwrite the corresponding field values ​​in the intermediate maintenance library. All model branches marked as "delete" are deleted in the intermediate maintenance library.

[0054] The verification and release unit is used to verify and release the power grid model on the intermediate maintenance library, and to back up the real-time library after successful release to generate the latest real-time library backup file.

[0055] The present invention proposes a terminal, comprising a processor and a storage medium; the storage medium is used for storing instructions; and the processor is used for operating according to the instructions to execute steps of a method.

[0056] A computer-readable storage medium stores a computer program thereon, which implements the steps of the method when executed by a processor.

[0057] The beneficial effects of the present invention are as follows: compared with the prior art, the present invention provides a method for parallel maintenance of a power grid model by multiple users, wherein the offline maintenance library model is split into multiple hierarchical tree-like model branches according to the hierarchical relationship of the power grid model. The user only needs to select the top-level objects of the model branches to form a model range, and the objects included in the model range can be traversed from the top-level objects according to the model hierarchical relationship; an intermediate maintenance library is added between the offline maintenance library and the real-time library, and each user verifies and publishes a local model in the intermediate maintenance library, without affecting each other, thereby improving the pass rate of model verification and publication; the models of the selected range in the offline maintenance library are merged into the intermediate maintenance library, and a boundary conflict check mechanism is adopted to ensure the accuracy of the model merging; the local power grid model in the intermediate maintenance library is published and submitted, and the granularity of the model publication is finer than the existing full library and full power grid model publication. The models maintained by the users in the offline maintenance library are divided into relatively independent model ranges according to the hierarchical branches and merged into the intermediate maintenance library for verification and publication. The results maintained by each user no longer affect each other, achieving the effect of multi-user parallel modification and parallel submission, effectively improving the parallelism of multi-user maintenance, improving the work efficiency of users, and ensuring the consistency of the power grid model of the power dispatching automation system with the real power grid. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 Flowchart of the multi-user parallel maintenance method for a power grid model proposed in an embodiment of the present invention;

[0059] Figure 2 Schematic diagram of hierarchical branches of a power grid model in an embodiment of the present invention;

[0060] Figure 3 It is a structural block diagram of the multi-user parallel maintenance system of the power grid model described in the embodiment. DETAILED DESCRIPTION

[0061] To make the objectives, technical solutions, and advantages of the present invention more clear, the technical solutions of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. The embodiments described in this application are only part of the embodiments of the present invention, not all of them. Based on the spirit of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0062] Currently, multiple users concurrently modify model data in an offline maintenance repository. For example, User A modified but did not complete the "Plant Station 1" model branch, while User B completed the "Plant Station 2" model branch. Before User B could publish the modified model branch, they needed to verify the model's integrity and correctness in the offline maintenance repository. This operation was performed on all model branches in the offline maintenance repository. Because User A was modifying the "Plant Station 1" model branch, verification of the model branch User B wanted to publish failed. User B had to wait until User A completed the "Plant Station 1" model branch before verifying and publishing the model. This meant that only after all model branches had been modified could users verify and publish the model branch across the entire offline repository. This affected each other's model branch modifications, reducing maintenance parallelism and efficiency. Furthermore, all modified model branches were published together, potentially exposing unwanted model branches to the release, preventing the selective, sequential release of model branches. Furthermore, verification and publishing were performed across all model branches in the offline repository, making it impossible to verify and publish individual model branches.

[0063] In view of the above problems, the present invention proposes a multi-user parallel maintenance method for a power grid model. Figure 1 Shown, including:

[0064] Obtain the maintained model branches from the offline maintenance library to form the model range to be released;

[0065] Use the latest real-time database backup file to restore and generate the intermediate maintenance database; the latest real-time database backup file is generated by backing up the real-time database after the most recent successful release and contains the complete power grid model data in the real-time database;

[0066] The object that has a reference relationship with the objects of all model branches within the model scope is regarded as the reference object. If the reference object does not exist in the intermediate maintenance library, the model branch where the reference object is located is added to the model scope to be released to form the revised model scope;

[0067] According to the revised model range, the corresponding model branch is extracted from the offline maintenance library and merged into the intermediate maintenance library; the power grid model is verified and published on the intermediate maintenance library, and the running real-time library after successful publication is backed up to generate the latest running real-time library backup file.

[0068] like Figure 1 As shown, the method includes:

[0069] In step 1, the operation and maintenance personnel maintain the model branches in the power grid model in the offline maintenance library, use the top-level object of each model branch to represent the model branch, and mark the maintenance type on the top-level object of the model branch.

[0070] In the embodiment of the present invention, the power grid model is divided into multiple model branches according to the hierarchical structure. The upper and lower layer objects of each model branch are in a symbiotic relationship. The top layer object of each model branch represents the model branch, such as Figure 2 The power grid model shown contains five model branches, represented by the top-level objects "Plant 1," "Plant 2," "Line 1-2," "Basic Voltage Level 1," and "Basic Voltage Level 2." The upper and lower objects in the model branches have a symbiotic relationship in a hierarchical tree structure. The upper-level object contains multiple lower-level objects. For example, "Plant 1" includes multiple lower-level sub-objects in a 1:n symbiotic relationship: "Voltage Level 1," "Voltage Level 2," and "Transformer 1." Each lower-level object also contains a lower-level sub-object, and so on, until the leaf object, which does not contain the next lower-level sub-object. Objects within different model branches may also have a 1:1 reference relationship. For example, "Voltage Level 1" references "Basic Voltage Level 1." The existence of this reference relationship leads to possible correlation between the various model branches, resulting in a chain effect during model verification and release.

[0071] In actual engineering, each user is responsible for the maintenance of the power grid model in a region. For example, by county, users in County A maintain "Plant Station 1" in County A, and users in County B maintain "Plant Station 2" in County B. Therefore, a model branch (such as a plant station) is generally maintained by one user. Therefore, in the method proposed by the present invention, multiple users can maintain the various model branches in the power grid model in parallel in the offline maintenance library, and form the maintained model branches into the model range to be released. Subsequent verification and release are limited to the model range, avoiding the mutual influence caused by parallel maintenance by multiple users, improving the maintenance parallelism, and also avoiding the situation where the model branches that do not want to be released are accidentally released, thereby improving the protection of the power grid model; and the subsequent model branch merging is also carried out based on the model range. Compared with subsequent verification and release, the maintenance of model branches takes the longest time, so the parallel maintenance of model branches significantly improves the system work efficiency and highlights the parallel operation characteristics of the system.

[0072] The present invention proposes to use the top-level object of a model branch to represent the model branch, which reduces the complexity of the user selecting the modified model branch. Moreover, since the objects within the same model branch are in a symbiotic relationship, when maintaining the model branch, deleting the top-level object automatically deletes all objects in the model branch, and merging the top-level object automatically merges all objects in the model branch. Therefore, representing the model branch based on the top-level object can ensure the integrity and convenience of model branch maintenance.

[0073] Specifically, maintenance types include: adding, deleting, and modifying. When the operation and maintenance personnel modify the power grid model in the offline maintenance library, they use the following rules to mark the maintenance type on the top-level object of the model branch:

[0074] 1) When adding a new model branch in the offline maintenance library, mark the maintenance type of the model branch as "new" on the top-level object;

[0075] 2) When deleting a model branch in the offline maintenance library, mark the model branch maintenance type as "delete" on the top-level object;

[0076] 3) If an object in an existing model branch of the offline maintenance library is modified, or a lower-level object other than the top-level object is added / deleted on an existing model branch, the model branch maintenance type is marked as "modified" on the top-level object;

[0077] 4) For a model branch that has been marked as "new", when modifying an object on the model branch, the maintenance type mark on the top-level object remains "new". When deleting the model branch, the maintenance type mark on the top-level object is cleared.

[0078] 5) For the model branch marked as "modify", delete the model branch and change the maintenance type mark on the top-level object to "delete";

[0079] 6) When the power grid model is successfully published, clear the maintenance type mark on the top-level object of the published model branch in the offline maintenance library.

[0080] like Figure 2 As shown, the user performs modification and maintenance operations in the offline maintenance library. Assuming that the model branch represented by "Plant Station 1" is newly added to the offline maintenance library, the maintenance type of the model branch represented by "Plant Station 1" is marked as "Add"; assuming that the model branch represented by "Plant Station 1" already exists, and the user deletes the model branch represented by "Plant Station 1" during maintenance, the maintenance type of the model branch represented by "Plant Station 1" is marked as "Delete"; assuming that the model branch represented by "Plant Station 1" already exists, and the user modifies the field value of the "Plant Station 1" object or sub-object during maintenance, or adds or deletes objects under the "Plant Station 1" model branch, these situations are all marked with the maintenance type of the model branch represented by "Plant Station 1" as "Modify".

[0081] Maintenance types are marked on the top-level objects of model branches. This is done automatically by the program based on user-initiated maintenance requests, eliminating the need for manual labeling. In this embodiment, a "Maintenance Type Marking Table" (as shown in Table 1) is added to the offline maintenance library. When the offline maintenance library receives a maintenance request from a maintenance person, it marks it in the "Maintenance Type Marking Table" according to the maintenance rules. After the selected model branch is successfully released, the maintenance type mark corresponding to the model branch is cleared.

[0082] Table 1 Maintenance type marking table

[0083] The ID of the top-level table Primary key of the top-level object Maintenance Type Checkmark 12 120001 New yes 13 130001 Revise no 14 140006 delete no

[0084] In the embodiment, Table 1 is used to record the maintenance type mark of the top-level object of the maintained model branch, so that the operation and maintenance personnel can intuitively see the maintenance status of the power grid model in the offline maintenance library.

[0085] Step 2: traverse the top-level objects of each model branch in the offline maintenance library. The operation and maintenance personnel select the model branches to be released from the top-level objects marked with the maintenance type to form the model range to be released.

[0086] Specifically, step 2 includes: constructing a maintenance type mark table, including: the table ID of the table where the top-level object is located, the primary key of the top-level object, the maintenance type, and the selection mark; the operation and maintenance personnel select the model branches with the selection mark as no from the maintenance type mark table to form the model range to be released.

[0087] In the embodiment, the contents of Table 1 are displayed on the operation and maintenance tool interface, that is, the top-level table and the primary key of the top-level object marked with the maintenance type. The operation and maintenance personnel only need to check the top-level object corresponding to the model branch they want to participate in the release on the operation and maintenance tool interface to automatically generate the model range to be released, which is convenient and quick to operate.

[0088] In addition, to save resources and avoid cross-errors, Table 1 also adds a mark to indicate whether the top-level object is selected. When multiple operation and maintenance personnel select different model branches in parallel, they can observe the mark to prevent the same model branch from being repeatedly selected by multiple operation and maintenance personnel.

[0089] In this embodiment of the present invention, a model scope describes a maintenance subset of the power grid model in the offline maintenance repository, consisting of one or more modified model branches. With a model branch as the smallest unit of a model scope, and because maintenance types are tagged for top-level objects, operations and maintenance personnel only need to select objects in the top-level table of a model branch. Based on the power grid model hierarchy, they can traverse the top-level objects to obtain the objects included in the model scope, simplifying the selection of model objects to be published.

[0090] Table 2 is a schematic representation of a model range, including one newly added model branch, two modified model branches, and one deleted model branch.

[0091] Table 2 Model range representation

[0092]

[0093]

[0094] Furthermore, when multiple operation and maintenance personnel determine the model scope in parallel and submit verification and release requests, they will add multiple model scopes to the end of the queue in the order of the time when the verification and release requests were submitted. During verification and release, the model scopes are serially taken out of the queue. Since each model scope defines a non-repeating model branch, serial operation can reduce the time consumption of verification and release while saving resources.

[0095] Step 3: Use the latest real-time database backup file to restore and generate the intermediate maintenance database; wherein, the latest real-time database backup file is generated by backing up the real-time database after the most recent successful release and contains the complete power grid model data in the real-time database.

[0096] The real-time database backup file is a disk file generated by backing up the power grid model data in the real-time database. It contains the complete power grid model data. The power grid model data stored in the real-time database backup file can be restored to the intermediate maintenance database through the real-time database restoration mechanism.

[0097] Specifically, check whether the last model release was successful. If successful, the power grid models of the current intermediate maintenance library and the running real-time library are the same, and the current intermediate maintenance library is used without restoration. If failed, there are differences between the power grid models of the intermediate maintenance library and the running real-time library, and the real-time library backup file generated after the most recent successful model release is used to restore the intermediate maintenance library.

[0098] The intermediate maintenance library is located between the offline maintenance library and the real-time library. It is used to merge the model branches selected from the offline maintenance library when publishing the model, and to verify and publish based on the merged power grid model in the intermediate maintenance library. Before the merge, the power grid model in the intermediate maintenance library is the same as that in the real-time library, but different after the merge. This achieves isolation of the model content being modified by other users in the offline maintenance library during verification and publishing, reducing mutual impact.

[0099] Before merging the offline maintenance library's model branch into the intermediate maintenance library, it is necessary to ensure that the power grid model in the intermediate maintenance library is the same as the latest power grid model in the real-time library. Therefore, initially, the intermediate maintenance library is generated using the latest verified and published real-time library backup file, including:

[0100] In the embodiment, whether the intermediate maintenance library needs to be rebuilt is determined based on the last verification and release situation. If the last verification and release is successful, then the intermediate maintenance library model is the same as the running real-time library model, and there is no need to rebuild the intermediate maintenance library. If the last verification or release fails, then the intermediate maintenance library model retains the release failure model branch merged at the time of the last release, which is different from the running real-time library. This release needs to use the running real-time library backup file generated by the backup after the most recent successful release to rebuild the intermediate maintenance library. By detecting the last verification and release situation to determine whether the intermediate maintenance library needs to be rebuilt, unnecessary reconstruction of the intermediate maintenance library can be reduced. In the case of multiple verification or release failures, the running real-time library backup file generated by the backup after the most recent successful release is used as the source for rebuilding the intermediate maintenance library. Compared with backing up the running real-time library as the source for rebuilding the intermediate maintenance library every time a reconstruction is performed, the number of backups of the running real-time library can be reduced, the backup file reuse rate can be increased, and the reconstruction efficiency can be improved.

[0101] Moreover, since the intermediate maintenance library contains the latest power grid model that is the same as the real-time library, a single model branch can be verified and published in the intermediate maintenance library. That is, when only a single model branch is selected to be added to the intermediate maintenance library according to the model range, the single model branch can be merged with the power grid model already existing in the intermediate maintenance library, thereby realizing verification and publication based on the entire power grid model, which is impossible to achieve with existing technologies.

[0102] Step 4: The object that has a reference relationship with the objects in all model branches within the model scope is used as the reference object. If the reference object does not exist in the intermediate maintenance library, the model branch where the reference object is located is added to the model scope to be released to form the revised model scope.

[0103] Specifically, step 4 includes:

[0104] In step 4.1, a model range to be published is taken from the head of the queue in a first-in-first-out order. The offline maintenance library is traversed according to the maintenance tag, and objects on all model branches within the model range are obtained from the offline maintenance library, including:

[0105] Step 4.1.1: For the model branches marked as "new" and "modified" within the model scope, first traverse the top-level objects of each model branch to obtain the child objects that have a symbiotic relationship with the top-level object; then traverse each child object to obtain the child objects that have a symbiotic relationship with the child object; recursively traverse until the leaf object; extract all the traversed objects and record the primary keys and field values ​​of all the traversed objects.

[0106] by Figure 2Taking the model shown as an example, assuming that the model branch maintenance mark represented by "Plant Station 1" is "New", the model branch represented by "Plant Station 1" is stored in the offline maintenance library as shown in Table 3 below.

[0107] Table 3 Schematic diagram of the offline maintenance library "plant station 1" branch storage

[0108]

[0109]

[0110] From the offline maintenance library, traverse the objects contained in the "Plant 1" model branch. The steps are as follows:

[0111] Starting from the top-level object "Plant 1", query the plant table based on the primary key 120001 of "Plant 1", obtain the "Plant 1" object, and record the values ​​of each field of the object;

[0112] Read the two symbiotic relationship fields of the "Plant Station 1" object, namely "Includes Voltage Level" and "Includes Transformer", and obtain the primary keys of the sub-objects contained in "Plant Station 1", namely Voltage Level [110001, 110002] and Transformer [200001]. Query the two tables to obtain the objects corresponding to these primary keys, namely "Voltage Level 1", "Voltage Level 2", and "Transformer 1", and record the values ​​of each field of the objects;

[0113] Read the symbiotic relationship field ("Include Interval") of the "Voltage Level 1" and "Voltage Level 2" objects, and obtain the primary keys of the interval sub-objects contained in the two voltage level objects, namely, Interval [190001, 190002] and Interval [190003, 190004]. Query the interval table to obtain the objects corresponding to these primary keys, namely, Interval 1 to Interval 4, and record the values ​​of each field in the objects.

[0114] Read the symbiotic relationship field of the "Transformer 1" object, namely "Includes Transformer Volume", and obtain the primary key of the sub-object contained in "Transformer 1", namely Transformer Volume [220001]. Query the transformer volume table to obtain the object corresponding to the primary key, namely "Transformer Volume 1", and record the values ​​of each field of the object.

[0115] For the objects in the above interval table, by traversing its child objects according to its symbiotic relationship field, we can obtain the "circuit breaker 1" and "circuit breaker 2" objects contained in the "interval 1" object;

[0116] Transformer volumes and circuit breakers no longer contain symbiotic relationship fields, are leaf objects, and traversal is terminated.

[0117] In step 4.1.2, for the model branch whose maintenance mark in the model scope is "deleted", extract the top-level object of the model branch and record the primary key of the top-level object.

[0118] The model branch marked as "deleted" in the model-wide maintenance has been deleted in the offline maintenance library. You only need to record the primary key of the top-level object of the deleted model branch. When merging the model branch into the intermediate maintenance library, you can recursively delete the objects on the entire model branch through the recorded primary key of the top-level object.

[0119] After the first traversal is completed in step 4.1, all model objects contained in all model branches within the model range can be obtained.

[0120] The first traversal implemented in step 4.1 is based on the traversal of the symbiotic relationship, so it can ensure that the complete local hierarchical tree-like model branch is obtained. However, the objects contained in the model branch may have a reference relationship with the objects on other model branches. If the referenced objects on other model branches are newly added and do not exist in the intermediate maintenance library, in order to ensure the integrity of the model branch when it is merged into the intermediate maintenance library, the model scope needs to be adjusted to include the model branch where the newly added objects with the reference relationship are located. Therefore, based on the first traversal, the boundary of the model scope is checked.

[0121] In step 4.2, obtain the primary key of the referenced object that has a reference relationship with the object obtained in step 4.1, and check whether the primary key of the referenced object exists in the intermediate maintenance library; if the primary key exists, it indicates that there is no problem of not being able to find the referenced object when the model branch is subsequently merged into the intermediate maintenance library, that is, the current model scope is appropriate; if the primary key does not exist, it indicates that the referenced object is newly added in the offline maintenance library, and check whether the model branch where the referenced object is located is within the model scope; if it is not within the model scope, add the model branch where the referenced object is located to the model scope; if it is within the model scope, keep the model scope unchanged.

[0122] Specifically, for each object within the model scope obtained by the first traversal, the reference fields contained in the object are traversed to obtain the primary key of the referenced object associated with the object. The primary key is then checked in the intermediate maintenance repository described in step 3 to determine whether it exists. If not, it indicates that the referenced object is newly added to the offline maintenance repository. The model branch containing the newly added object is further queried. If the model branch is not within the scope of the currently released model, the operator is informed that the model scope boundary check has failed and that the operator needs to add the model branch containing the referenced object to the maintenance scope. If the check passes, proceed to step 5.

[0123] by Figure 2 Taking the model shown as an example, it is assumed that during a certain maintenance, the "Plant Station 1" and "Plant Station 2" branches are marked as "Modified" and the "Line 1-2" branch is marked as "Newly Added", that is, the "Plant Station 1" and "Plant Station 2" branches already exist in the intermediate maintenance library, and the "Line 1-2" branch does not exist in the intermediate maintenance library.

[0124] Assume that the O&M personnel select a release model scope that only includes the "Plant 1" branch. The O&M personnel traverse the objects contained in the "Plant 1" branch within the model scope to obtain referenced objects, including "Line 1-2," "Basic Voltage Level 1," and "Basic Voltage Level 2." The personnel then check whether these three objects exist in the intermediate maintenance repository. Since "Line 1-2" does not exist in the intermediate maintenance repository and the model scope does not include the branch containing "Line 1-2," the boundary check fails, prompting the O&M personnel to select the "Line 1-2" branch.

[0125] Assume that the user follows the prompts and selects "Plant Station 1" and "Line 1-2" as the model scope. For the "Plant Station 1" branch, the referenced object "Line 1-2" doesn't exist in the intermediate maintenance library. However, because the model scope includes the "Line 1-2" branch, it will be added to the intermediate maintenance library during the merge, ensuring the correctness of the reference relationship. For the "Line 1-2" branch, the referenced objects include "Plant Station 1" and "Plant Station 2." These objects exist in the intermediate maintenance library, and the boundary check passes.

[0126] Step 5: Extract the corresponding model branches according to the revised model range and merge them into the intermediate maintenance library.

[0127] Specifically, step 5 includes:

[0128] Step 5.1: For model branches whose maintenance mark is "new" and "modified", check whether the primary keys of all objects contained in the model branch exist in the intermediate maintenance library, and add objects whose primary keys do not exist to the intermediate maintenance library. The primary keys, attribute field values, and reference field values ​​of each newly added object in the intermediate maintenance library are consistent with those in the offline maintenance library. If the primary key exists, compare the attribute field values ​​and reference field values ​​of the objects in the offline maintenance library and the intermediate maintenance library to see if they are the same. If they are different, use the attribute field values ​​and reference field values ​​in the offline maintenance library to overwrite the corresponding field values ​​in the intermediate maintenance library.

[0129] Furthermore, recursively traverse each child object contained in the top-level object, use the child object as the new top-level object, and repeat the above merging operation until the child object is a leaf node and no longer contains child objects.

[0130] Step 5.2: Delete all model branches marked as "delete" in the intermediate maintenance library.

[0131] Specifically, for each model branch to be deleted, traverse from the top-level object, delete the top-level object and all sub-objects it contains in the intermediate maintenance library, use the sub-object as the new top-level object, and repeat the above deletion operation until all objects on the model branch are deleted.

[0132] The merged intermediate maintenance library model is based on the power grid model in the current real-time library, and merges the local power grid model modified by the operation and maintenance personnel in the offline maintenance library. The merged power grid model is the power grid model that the operation and maintenance personnel want to submit to the real-time library. The merged model excludes the content modified by other operation and maintenance personnel, reducing the mutual influence between operation and maintenance personnel. Verification and release based on the merged model can improve the success rate of model verification and release, improve the efficiency of user parallel maintenance, and the granularity of model release is also finer.

[0133] Compared to the existing offline maintenance repository verification and publishing method, the multi-user parallel maintenance method proposed in this paper adds an intermediate maintenance repository, reduces user interaction, and improves multi-user maintenance efficiency. Modifications and model range selection are performed in parallel in the offline maintenance repository, while merging to the intermediate maintenance repository, verification, and publishing are performed serially. Verification and publishing are both time-efficient, and the serialization process has a relatively minimal impact on multi-user parallel maintenance.

[0134] Step 6: Perform model verification and release operations on the intermediate maintenance library, and back up the running real-time library after successful release to generate the latest running real-time library backup file.

[0135] The correctness and integrity of the model are verified on the merged intermediate maintenance library. If the verification fails, the release is terminated and the error message is prompted to the operation and maintenance personnel. If the verification passes, the intermediate maintenance library model is published and submitted to the real-time library, and the power grid model in the real-time library is backed up to generate the latest power grid model backup file for rebuilding the intermediate maintenance library when the model is subsequently released.

[0136] The method proposed in the present invention realizes multi-user parallel operation of power grid models. According to the hierarchical relationship of the power grid model, the offline maintenance library model is split into multiple hierarchical tree-like model branches. Users only need to select the top-level objects of the model branches to form the model scope. According to the model hierarchical relationship, the objects included in the model scope can be traversed from the top-level objects. An intermediate maintenance library is added between the offline maintenance library and the real-time library. Each user verifies and publishes a local model in the intermediate maintenance library. Users do not affect each other, thereby improving the pass rate of model verification and publication. The models of the selected range in the offline maintenance library are merged into the intermediate maintenance library. A boundary conflict check mechanism is adopted to ensure the accuracy of model merging. The local power grid model in the intermediate maintenance library is published and submitted. Compared with the existing full library and full power grid model publishing, the granularity of model publishing is finer. The models maintained by users in the offline maintenance library are divided into relatively independent model scopes according to the hierarchical branches and merged into the intermediate maintenance library for verification and publication. The results maintained by each user no longer affect each other, achieving the effect of multi-user parallel modification and parallel submission, effectively improving the parallelism of multi-user maintenance, improving user work efficiency, and ensuring the consistency of the power grid model of the power dispatching automation system with the actual power grid.

[0137] The present invention also proposes a multi-user parallel maintenance system for a power grid model, such as Figure 3 Shown, including:

[0138] Model scope division module, intermediate maintenance library construction module, model scope modification module and verification and release module;

[0139] The model range division module is used to obtain the maintained model branches from the offline maintenance library to form the model range to be released;

[0140] The intermediate maintenance library construction module is used to restore the intermediate maintenance library using the latest real-time library backup file. The latest real-time library backup file is a backup of the real-time library generated after the most recent successful release and contains the complete power grid model data in the real-time library.

[0141] The model scope correction module is used to take objects that have a reference relationship with objects in all model branches within the model scope as reference objects. If the referenced object does not exist in the intermediate maintenance library, the model branch where the referenced object is located is added to the model scope to be released to form the corrected model scope.

[0142] The verification and release module is used to extract the corresponding model branches from the offline maintenance library and merge them into the intermediate maintenance library according to the revised model range; verify and release the power grid model on the intermediate maintenance library, and back up the running real-time library after successful release to generate the latest running real-time library backup file.

[0143] The model range partitioning module includes: marking unit and selection unit;

[0144] The marking unit is used by operation and maintenance personnel to maintain the model branches in the power grid model in the offline maintenance library. The top-level object of each model branch represents the model branch, and the maintenance type is marked on the top-level object of the model branch. The maintenance types include: addition, modification and deletion.

[0145] The selection unit is used to traverse the top-level objects of each model branch in the offline maintenance library. The operation and maintenance personnel select the model branches to be released from the top-level objects marked with the maintenance type to form the model range to be released.

[0146] The intermediate maintenance library construction module includes a detection unit and a generation unit. The detection unit is used to detect whether the latest verification and release is successful. If the detection unit detects that the latest verification and release is successful, the power grid models of the current intermediate maintenance library and the running real-time library are the same, and the current intermediate maintenance library is used without restoration; if the detection unit detects that the latest verification and release is unsuccessful, there are differences in the power grid models of the intermediate maintenance library and the running real-time library, and the generation unit uses the running real-time library backup file generated after the most recent successful release of the model to restore the intermediate maintenance library.

[0147] The model range correction module includes a first traversal unit, a second traversal unit and a correction unit;

[0148] The first traversal unit is used to traverse the offline maintenance library based on the model range to be released and the maintenance mark, and extract objects with symbiotic relationships in all model branches within the model range from the offline maintenance library;

[0149] The second traversal unit is used to take an object that has a reference relationship with the object extracted by the first traversal unit as a reference object and extract a primary key of the reference object;

[0150] The correction unit is used to determine whether the model branch where the referenced object is located is within the model scope if the primary key extracted by the second traversal unit does not exist in the intermediate maintenance library. If the model branch corresponding to the referenced object does not exist within the model scope, the model branch where the referenced object is located is added to the model scope to be released to form a corrected model scope.

[0151] The verification and release module includes a merging unit and a verification and release unit;

[0152] The merge unit is used to check whether the primary keys of all objects contained in the model branches marked as "new" and "modified" exist in the intermediate maintenance library, and add objects whose primary keys do not exist to the intermediate maintenance library. The primary keys, attribute field values, and reference field values ​​of the newly added objects in the intermediate maintenance library are consistent with the corresponding field values ​​in the offline maintenance library. For objects with existing primary keys, the attribute field values ​​and reference field values ​​of the objects in the offline maintenance library and the intermediate maintenance library are compared to see if they are the same. If they are different, the attribute field values ​​and reference field values ​​in the offline maintenance library are used to overwrite the corresponding field values ​​in the intermediate maintenance library. All model branches marked as "delete" are deleted in the intermediate maintenance library.

[0153] The verification and release unit is used to verify and release the power grid model on the intermediate maintenance library, and to back up the real-time library after successful release to generate the latest real-time library backup file.

[0154] The present disclosure may be a system, method and / or computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present disclosure.

[0155] A computer-readable storage medium can be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium can be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination thereof. As used herein, a computer-readable storage medium is not to be construed as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through an electrical wire.

[0156] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in the computer-readable storage medium in each computing / processing device.

[0157] The computer program instructions for performing the operations of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, and conventional procedural programming languages ​​such as "C" language or similar programming languages. Computer-readable program instructions may be executed entirely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., utilizing an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be personalized by utilizing the state information of the computer-readable program instructions. The electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present disclosure.

[0158] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered by the scope of protection of the claims of the present invention.

Claims

1. A multi-user parallel maintenance method for a power grid model, wherein the power grid model is divided into multiple model branches according to a hierarchical structure, objects within the same model branch have a symbiotic relationship, and objects in different model branches have a reference relationship. Operation and maintenance personnel maintain the model branches in the power grid model in an offline maintenance library; characterized in that: Methods include: Obtain the maintained model branches from the offline maintenance library to form the model range to be released; Use the latest real-time database backup file to restore and generate the intermediate maintenance database; the latest real-time database backup file is generated by backing up the real-time database after the most recent successful release and contains the complete power grid model data in the real-time database; The object that has a reference relationship with the objects of all model branches within the model scope is regarded as the reference object. If the reference object does not exist in the intermediate maintenance library, the model branch where the reference object is located is added to the model scope to be released to form the revised model scope; According to the revised model range, the corresponding model branch is extracted from the offline maintenance library and merged into the intermediate maintenance library; the power grid model is verified and published on the intermediate maintenance library, and the running real-time library after successful publication is backed up to generate the latest running real-time library backup file.

2. The multi-user parallel maintenance method for a power grid model according to claim 1, characterized in that: Obtain the maintained model branches from the offline maintenance library to form the model range to be released, including: The operation and maintenance personnel maintain the model branches in the power grid model in the offline maintenance library, using the top-level object of each model branch to represent the model branch and marking the maintenance type on the top-level object of the model branch; the maintenance types include: addition, modification and deletion; Traversing the top-level objects of each model branch in the offline maintenance library, the operation and maintenance personnel select the model branches to be released from the top-level objects marked with the maintenance type to form the model range to be released.

3. The multi-user parallel maintenance method for a power grid model according to claim 2, characterized in that: The maintenance type is marked on the top-level objects of a model branch using the following rules: 1) When adding a new model branch in the offline maintenance library, mark the maintenance type of the model branch as "new" on the top-level object; 2) When deleting a model branch in the offline maintenance library, mark the model branch maintenance type as "delete" on the top-level object; 3) If an object in an existing model branch in the offline maintenance library is modified, or if a lower-level object other than the top-level object is added or deleted on an existing model branch, the model branch maintenance type is marked as "modified" on the top-level object; 4) For a model branch marked as "New", when modifying an object on the model branch, the maintenance type mark on the top-level object remains "New". When deleting the model branch, the maintenance type mark on the top-level object is cleared. 5) For the model branch marked as "modify", delete the model branch and change the maintenance type mark on the top-level object to "delete"; 6) When the power grid model is successfully published, clear the maintenance type mark on the top-level object of the published model branch in the offline maintenance library.

4. The multi-user parallel maintenance method for a power grid model according to claim 2, characterized in that: The model scope to be released is composed of the model branches corresponding to the top-level objects marked with the maintenance type, including: Construct a maintenance type mark table, including: the table ID of the table where the top-level object is located, the primary key of the top-level object, the maintenance type, and the check mark; The operation and maintenance personnel select the model branches marked as "No" from the maintenance type mark table to form the model range to be released.

5. The multi-user parallel maintenance method for a power grid model according to claim 2, characterized in that: When multiple operation and maintenance personnel determine the model scope in parallel and submit verification and release requests, the multiple model scopes are added to the end of the queue in the order of the time when the verification and release requests were submitted. The model scopes are serially taken out of the queue during verification and release.

6. The multi-user parallel maintenance method for a power grid model according to claim 1, characterized in that: Use the latest real-time database backup file to restore and generate the intermediate maintenance database. The latest real-time database backup file is generated by backing up the real-time database after the most recent successful release and contains the complete power grid model data in the real-time database, including: Check whether the last model release was successful. If successful, the power grid models of the current intermediate maintenance library and the running real-time library are the same. Use the current intermediate maintenance library and no restoration is required. If failed, there are differences between the power grid models of the current intermediate maintenance library and the running real-time library. Use the real-time library backup file generated after the most recent successful model release to restore the intermediate maintenance library.

7. The multi-user parallel maintenance method for a power grid model according to claim 2, characterized in that: The object that has a reference relationship with the objects of all model branches within the model scope is regarded as a reference object. If the reference object does not exist in the intermediate maintenance library, the model branch where the reference object is located is added to the model scope to be released, forming a revised model scope, including: Based on the model range to be released, the offline maintenance library is traversed according to the maintenance mark, and objects with symbiotic relationships in all model branches within the model range are extracted from the offline maintenance library; The object that has a reference relationship with the extracted object is used as the reference object, and the primary key of the reference object is extracted; if the primary key does not exist in the intermediate maintenance library, it is determined whether the model branch where the reference object is located is within the model scope. If the model branch corresponding to the reference object does not exist within the model scope, the model branch where the reference object is located is added to the model scope to be released to form a revised model scope.

8. The multi-user parallel maintenance method for a power grid model according to claim 2, characterized in that: Based on the model scope to be released, the offline maintenance library is traversed according to the maintenance tag, and objects with symbiotic relationships in all model branches within the model scope are extracted from the offline maintenance library, including: For model branches marked as "new" and "modified" within the model scope, first traverse the top-level objects of each model branch to obtain the sub-objects that have a symbiotic relationship with the top-level object; then traverse each sub-object to obtain the sub-objects that have a symbiotic relationship with the sub-object; recursively traverse until the leaf object; extract all traversed objects; Extracts the top-level objects of a model branch that has a model-wide maintenance flag set to "delete." 9. The multi-user parallel maintenance method for a power grid model according to claim 2, characterized in that: According to the revised model range, the corresponding model branch is extracted from the offline maintenance library and merged into the intermediate maintenance library, including: For model branches marked as "New" and "Modified," the system checks whether the primary keys of all objects in the model branch exist in the intermediate maintenance repository. Objects whose primary keys do not exist are added to the intermediate maintenance repository. The primary keys, attribute field values, and reference field values ​​of the newly added objects in the intermediate maintenance repository are kept consistent with the corresponding field values ​​in the offline maintenance repository. For objects whose primary keys exist, the system compares the attribute field values ​​and reference field values ​​of the objects in the offline and intermediate maintenance repositories to see if they are the same. If they are different, the attribute field values ​​and reference field values ​​in the offline maintenance repositories are used to overwrite the corresponding field values ​​in the intermediate maintenance repositories. Delete all model branches marked as "delete" in the intermediate maintenance repository.

10. A multi-user parallel maintenance system for a power grid model, characterized in that: The system includes: Model scope division module, intermediate maintenance library construction module, model scope modification module and verification and release module; The model range division module is used to obtain the maintained model branches from the offline maintenance library to form the model range to be released; The intermediate maintenance library construction module is used to restore the intermediate maintenance library using the latest real-time library backup file. The latest real-time library backup file is a backup of the real-time library generated after the most recent successful release and contains the complete power grid model data in the real-time library. The model scope correction module is used to take objects that have a reference relationship with objects in all model branches within the model scope as reference objects. If the referenced object does not exist in the intermediate maintenance library, the model branch where the referenced object is located is added to the model scope to be released to form the corrected model scope. The verification and release module is used to extract the corresponding model branches from the offline maintenance library and merge them into the intermediate maintenance library according to the revised model range; verify and release the power grid model on the intermediate maintenance library, and back up the running real-time library after successful release to generate the latest running real-time library backup file.

11. The power grid model multi-user parallel maintenance system according to claim 10, characterized in that: The model range partitioning module includes: marking unit and selection unit; The marking unit is used by operation and maintenance personnel to maintain the model branches in the power grid model in the offline maintenance library. The top-level object of each model branch represents the model branch, and the maintenance type is marked on the top-level object of the model branch. The maintenance types include: addition, modification and deletion. The selection unit is used to traverse the top-level objects of each model branch in the offline maintenance library. The operation and maintenance personnel select the model branches to be released from the top-level objects marked with the maintenance type to form the model range to be released.

12. The power grid model multi-user parallel maintenance system according to claim 10, characterized in that: The intermediate maintenance library construction module includes a detection unit and a generation unit. The detection unit is used to detect whether the last published model is successful. If successful, the power grid model of the current intermediate maintenance library and the running real-time library is the same. The current intermediate maintenance library is used and no restoration is required. If it fails, there is a difference between the power grid model of the current intermediate maintenance library and the real-time library. Use the real-time library backup file generated after the most recent successful model release to restore the intermediate maintenance library.

13. The power grid model multi-user parallel maintenance system according to claim 10, characterized in that: The model range correction module includes a first traversal unit, a second traversal unit and a correction unit; The first traversal unit is used to traverse the offline maintenance library based on the model range to be released and the maintenance mark, and extract objects with symbiotic relationships in all model branches within the model range from the offline maintenance library; The second traversal unit is used to take an object that has a reference relationship with the object extracted by the first traversal unit as a reference object and extract a primary key of the reference object; The correction unit is used to determine whether the model branch where the referenced object is located is within the model scope if the primary key extracted by the second traversal unit does not exist in the intermediate maintenance library. If the model branch corresponding to the referenced object does not exist within the model scope, the model branch where the referenced object is located is added to the model scope to be released to form a corrected model scope.

14. The power grid model multi-user parallel maintenance system according to claim 10, characterized in that: The verification and release module includes a merging unit and a verification and release unit; The merge unit is used to check whether the primary keys of all objects contained in the model branch marked as "New" and "Modified" exist in the intermediate maintenance repository. Objects whose primary keys do not exist are added to the intermediate maintenance repository. The primary keys, attribute field values, and reference field values ​​of the newly added objects in the intermediate maintenance repository are kept consistent with the corresponding field values ​​in the offline maintenance repository. For objects whose primary keys exist, the merge unit compares the attribute field values ​​and reference field values ​​of the objects in the offline and intermediate maintenance repositories to see if they are the same. If they are different, the attribute field values ​​and reference field values ​​in the offline maintenance repository are used to overwrite the corresponding field values ​​in the intermediate maintenance repository. Delete all model branches marked as "delete" in the intermediate maintenance library; The verification and release unit is used to verify and release the power grid model on the intermediate maintenance library, and to back up the real-time library after successful release to generate the latest real-time library backup file.

15. A terminal comprising a processor and a storage medium; characterized in that: The storage medium is used to store instructions; The processor is configured to operate according to the instructions to execute the steps of the method according to any one of claims 1 to 9.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images