Distribution network graph model transaction checking method based on multi-source data

Abstract

The invention discloses a distribution network graph-model transaction checking method based on multi-source data, relates to the technical field of power distribution automation of power systems, and aims to solve the problems that the collaboration degree between businesses is low and graphs and models between systems are inconsistent. The method comprises the following steps: establishing a transaction management process, performing maintenance plan management, performing service linkage from four aspects of graph-model red-to-black management, and performing homologous maintenance transaction graph-model management, and realizing real-time monitoring and auxiliary operation on the whole process of the whole graph-model transaction service through technical means of service process reconstruction, data cross-system connection, key node automatic checking and the like. And the workload and the pressure of manually checking the equipment difference of the red and black images and whether the transaction equipment is accurate or not when a dispatcher checks the transaction of the images and the models are relieved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of power system distribution automation, and in particular to a distribution network map model change checking method based on multi-source data. BACKGROUND

[0002] As the core of the distribution network, the quality of the map model is crucial to the development of the distribution network business. However, there is a lack of strong correlation and automatic checking capability between the current distribution network map model change and the planned business. The timeliness and accuracy of the change still depend on offline manual review and confirmation, which may lead to inconsistent map and reality due to the delay of the change. In order to fully meet the needs of distribution network dispatching under the new situation, it is necessary to develop a practical distribution network map model change checking method, which adheres to the principle of "no change, no permission" for the distribution network maintenance plan involving map model change. The timely and accurate release of the change is considered as the "red line" for dispatching management, and the inconsistent map and reality caused by the delay of the change or the unclear equipment of the change is strictly prohibited.

[0003] In the prior art, it is difficult to accurately check the execution of the distribution network change equipment. The maintenance plan of the dispatching management system (OMS) and the change management process are both pure text in terms of the description of the change equipment range, and the description methods of different units are different. Therefore, the change equipment range cannot be accurately obtained or recognized through traditional methods every time, which may lead to the situations of missing, multiple or incorrect release of the equipment during the release of the map model change, and the accurate execution of the map model change cannot be quantified, resulting in the reduction of the quality of the map model. SUMMARY

[0004] The present application aims to provide a distribution network map model change checking method based on multi-source data, which can solve the problem of low coordination between businesses and inconsistent map models between systems, and improve the quality of the map model and the execution standard of the map model change.

[0005] In order to achieve the above-mentioned purpose, the present application provides the following technical solution: A distribution network map model change checking method based on multi-source data, comprising: adjusting the change equipment maintenance plan in the dispatching management system by using a map model marking tool, generating a change equipment list and a structured text, and pushing them to the dispatching management system; the dispatching management system automatically synchronously initiates a change management process according to the change equipment list, and establishes a first relationship between the change management process and the equipment maintenance list; actively detecting the incremental data of the map model change of the same source maintenance system, obtaining all the equipment information in the change map model file by using a map model analysis technology and storing it, and establishing a second relationship between the change management process and the change map model file; comparing and checking the change equipment list and the change map model file according to the first relationship and the second relationship, and determining whether the change equipment list meets the accuracy requirement; According to the first relationship and the second relationship, the transaction equipment list is compared and checked with the transaction graph model file to determine whether the transaction graph model file meets the specification requirement of the distribution network graph model; After the transaction management process is checked, the power distribution automation system is notified to import the red graph in the homologous transaction file, and the red graph is converted to a black graph, and the power distribution automation system returns the transaction graph model file to the dispatching management system for closed loop checking; The dispatching management system checks whether the maintenance plan is executed and completed, and the transaction graph model of the power distribution automation system is checked whether the red graph is converted to a black graph. When the two conditions are met, the transaction management process is archived. Otherwise, the checking result is pushed to the user for modification, and the checking is repeated until it is passed.

[0006] More specifically, according to the first relationship and the second relationship, the transaction equipment list is compared and checked with the transaction graph model file to determine whether the transaction equipment list meets the accuracy requirement, specifically including: The newly added equipment in the transaction equipment list can be found in the unique equipment record in the homologous transaction graph model file through complete matching of the Chinese name; The removed equipment in the transaction equipment list can be matched to the data in the homologous transaction graph model file through the ID or Chinese name; The renamed equipment in the transaction equipment list can be matched to the unique record in the homologous transaction graph model file through the ID and Chinese name; The cut and changed equipment in the transaction equipment list can find the connection relationship of the corresponding cut and changed equipment in the homologous transaction graph model file through the topological search algorithm, and the equipment is cut and changed from the A equipment node to the B equipment node according to the transaction business requirement; If the transaction equipment list passes the comparison and checking, it is determined that the transaction equipment accuracy requirement is met; otherwise, the specific data list and the unsatisfied condition are stored.

[0007] More specifically, according to the first relationship and the second relationship, the transaction equipment list is compared and checked with the transaction graph model file to determine whether the transaction graph model file meets the specification requirement of the distribution network graph model, specifically including: The graph model consistency check, the equipment uniqueness check, the equipment attribute integrity check, the model topology accuracy check, and the transaction graph model specification check; if the transaction graph model file does not meet the comparison and checking, the specific data and the unsatisfied condition are stored and prompted.

[0008] Compared with the prior art, the distribution network graph model transaction checking method based on multi-source data provided by the application has the following beneficial effects: The device transaction management process, the maintenance plan management, the isogenic maintenance transaction graph model management, and the red-black graph conversion management of the distribution system graph model are linked among businesses, all incremental device transactions are included in management and control, and the storage is orderly promoted, the actual position and the actual operation graph model of the field device are accurately reflected, the problems of inconsistent graph and actual situation, missing, and misissuing caused by untimely transaction or unclear transaction device are avoided, and high collaboration degree among businesses and among systems is ensured. BRIEF DESCRIPTION OF DRAWINGS

[0009] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings: Figure 1 A method flowchart provided for an embodiment of the application. DETAILED DESCRIPTION

[0010] To make the objects, technical solutions, and advantages of the embodiments of the application clearer, the technical solutions in the embodiments of the application will be described below in connection with the drawings of the embodiments of the application. Obviously, the described embodiments are some but not all of the embodiments of the application. Based on the embodiments in the application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the application.

[0011] The embodiment of the application provides a distribution network graph model transaction checking method based on multi-source data, and the main process of the method is described as follows.

[0012] Step S1: The transaction device maintenance plan in the dispatching management system is adjusted by using a graph model marking tool, a transaction device list and a structured text are generated and pushed to the dispatching management system, the dispatching management system automatically synchronously initiates a transaction management process according to the transaction device list, and a first relationship between the transaction management process and the device maintenance list is established.

[0013] Specifically, the transaction refers to the change of the power grid graph model data in the device operation and maintenance management system (PMS). When the operation and maintenance personnel report the weekly maintenance plan, when the maintenance work involves device transaction, the transaction description is changed from original manual input text to manual adjustment of the transaction device through calling the graph model marking tool to add, remove, rename, and change. The graph model marking tool is an existing tool, which marks the transaction device by selecting the corresponding transaction type through the device frame selection based on the latest SVG graph of the power distribution automation. The dispatching management system is an order management module of the device maintenance plan, and the maintenance plan and the transaction business have an inherent business logic association.

[0014] The abnormality management process is: process initiation → special responsibility audit → diagram model release → archiving. After completing the diagram model marking through the diagram model marking tool, sending to the next link, automatically generating an abnormality management process, and automatically filling in the abnormality device list and structured text. The one-to-one correspondence between the abnormality process and the maintenance plan can be associated to query the execution of the maintenance plan and the corresponding abnormality device list of the maintenance plan through the abnormality management process, which is used to check the abnormality device list in the weekly maintenance plan.

[0015] The first relationship is specifically that the time, feeder ID pushed by the device maintenance list to the dispatch management system are matched with the abnormality plan time, feeder ID of the abnormality management process. The matching rule is: the feeder ID is the same, and the time is within the same day, which is defined as complete matching.

[0016] Step S2: actively detecting the diagram model abnormality increment data of the same source maintenance system, obtaining all device information in the abnormality diagram model file by using diagram model analysis technology and storing, and establishing a second relationship between the abnormality management process and the abnormality diagram model file.

[0017] Among them, the same source maintenance system is the diagram model management module under the device operation and maintenance management system, collectively referred to as the same source maintenance system, which scans the diagram model file pushed by the same source system through a timing task. When the distribution network device needs to be expanded, renamed, cut, and retired, the operation and maintenance personnel initiates a diagram model maintenance application through the same source maintenance system, then draws the latest graph of the future state, and then the same source maintenance system automatically corresponds to the diagram model file. After the file is approved, the diagram model file is automatically pushed to the designated server path under the three areas by the dispatch management system. The device information includes the basic parameters of the device and the connection relationship between the devices.

[0018] The second relationship is specifically that the time, feeder ID pushed by the abnormality diagram model file to the dispatch management system are matched with the abnormality plan time, feeder ID of the abnormality management process. The matching rule is: the feeder ID is the same, and the time is within the same day, which is defined as complete matching.

[0019] The first relationship and the second relationship are the same except for the difference in matching objects. Through the first relationship and the second relationship, the abnormality device list and the abnormality diagram model file can be indirectly matched and associated through the abnormality management process.

[0020] Step S3: According to the first relationship and the second relationship, the abnormality device list and the abnormality diagram model file are compared and checked to determine whether the abnormality device list meets the accuracy requirement.

[0021] Specifically, the newly added, removed, renamed, and changed devices in the transaction list are automatically identified by the prefix tree and hash duplicate checking algorithm to determine whether they are updated in the red drawing as required. The detailed checking rules are as follows: The newly added device in the transaction device list can be found in the same source transaction drawing file through complete matching of the Chinese name. The removed device in the transaction device list can be matched to the data in the same source transaction drawing file through the ID or Chinese name. The renamed device in the transaction device list can be matched to the unique record in the same source transaction drawing file through the ID and Chinese name. The changed device in the transaction device list can be found in the same source transaction drawing file through the topological search algorithm, and the device is changed from A device node to B device node as required by the transaction service. If all the transaction device lists pass the above comparison and checking, it is determined that the transaction device accuracy requirement is met; otherwise, the specific data list and the unsatisfied conditions are stored.

[0022] Step S4: According to the first relationship and the second relationship, the transaction device list is compared and checked with the transaction drawing file to determine whether the transaction drawing file meets the specification requirement of the distribution network drawing file.

[0023] To determine whether the transaction drawing file meets the specification requirement of the distribution network drawing file, structured data comparison algorithm and undirected graph connected component algorithm based on breadth-first search can be used for automatic discrimination, including drawing file consistency check, device uniqueness check, device attribute integrity check, model topology accuracy check, and transaction drawing specification check. The specific discrimination rules are as follows: Drawing file consistency check: The correspondence between the graphic object and the model object is checked. It is required that all electrical devices in the graphic file have corresponding objects in the model file. The correspondence between the model object and the graphic object is checked. It is required that all electrical devices in the model file have corresponding objects in the graphic file. The device type and parameter in the model and the device attribute in the graphic file are checked for consistency.

[0024] Device uniqueness check: The full path name of the power device is not allowed to be the same. The distribution network full path name is the feeder naming / distribution station name / model name. It is determined whether there are duplicate ID devices in the graphic file. The distribution network device has station ID and feeder ID, but there is no association between the station ID and the feeder ID, which is prompted to violate the association of the unique distribution station.

[0025] Device attribute integrity check: check the necessary attribute value of the object cannot be empty, including device name, belonging to the organization, belonging to the feeder, etc.; check whether the associated attribute value of the object meets the specification type constraint requirement, such as device voltage level, maximum carrying capacity, belonging to the feeder, etc.

[0026] Model topology accuracy check: judge the isolated device which is not connected to other devices and topology nodes; check whether there is a self-loop situation after deep topology retrieval in the feeder; count the topology islands in the model file, and check whether there are isolated islands in the topology nodes in the statistical model file.

[0027] After the transaction graph module file passes the above rule check, it is determined that it meets the transaction graph module specification check; otherwise, the specific data and non-compliance conditions are stored and prompted.

[0028] Step S5: After the transaction management process check passes, the distribution automation system imports the red graph in the transaction graph module file and completes the red-to-black graph operation, and at the same time, the distribution automation system returns the transaction graph module file to the dispatching management system for closed-loop check.

[0029] Among them, the red graph is a graph that is newly drawn when the transaction occurs and has not completed the red-to-black future state graph; the black graph refers to the state graph that is formally put into operation and use after the red-to-black operation is completed.

[0030] Step S6: Check whether the maintenance plan of the dispatching management system is executed and completed, and whether the transaction graph module of the distribution automation system completes the red-to-black graph operation. When both conditions are met, the transaction management process is archived; otherwise, the check result is pushed to the user, and after the relevant problems are rectified, the check is rechecked until it passes. Used to ensure the specification of transaction business.

[0031] Although the present application has been described in connection with the specific features and embodiments thereof, it is evident that many modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the present specification and drawings are to be regarded simply as illustrative of the present application and are to be construed in accordance with the appended claims, with all modifications and variations being intended to fall within the scope of the present application. Obviously, those skilled in the art can make various modifications and changes to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and changes of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application also intends to include these modifications and changes.

Claims

1.A method for checking a change of a distribution network diagram based on multi-source data, characterized in that, The application relates to a method for synchronizing and verifying a same-source transaction management process and a same-source transaction file. The method comprises the following steps: adjusting a transaction equipment maintenance plan in a dispatch management system by using a graph model marking tool, generating a transaction equipment list and a structured text, and pushing the transaction equipment list and the structured text to the dispatch management system; the dispatch management system automatically synchronously initiates a transaction management process according to the transaction equipment list, and establishes a first relationship between the transaction management process and the equipment maintenance list; actively detecting graph model transaction increment data of a same-source maintenance system, obtaining all the equipment information in a transaction graph model file by using a graph model analysis technology, storing the equipment information, and establishing a second relationship between the transaction management process and the transaction graph model file; comparing and checking the transaction equipment list and the transaction graph model file according to the first relationship and the second relationship, and judging whether the transaction equipment list meets the accuracy requirement; comparing and checking the transaction equipment list and the transaction graph model file according to the first relationship and the second relationship, and judging whether the transaction graph model file meets the specification requirement of a distribution network graph model; after the transaction management process is checked, the method notifies a power distribution automation system to import a red graph in the same-source transaction file, and completes a red graph to black graph operation; meanwhile, the power distribution automation system returns the transaction graph model file to the dispatch management system for closed-loop checking; when both conditions are met, the transaction management process is archived; 2.The method of claim 1, wherein, otherwise, the checking result is pushed to a user for modification, and the checking is repeated until the checking is passed. The method comprises the following steps: a newly-added equipment in the transaction equipment list can be found in the same-source transaction graph model file through complete matching of a Chinese name; a removed equipment in the transaction equipment list can be matched to data in the same-source transaction graph model file through an ID or a Chinese name; a renamed equipment in the transaction equipment list can be matched to a unique record in the same-source transaction graph model file through an ID and a Chinese name; a cut and changed equipment in the transaction equipment list can be found in the same-source transaction graph model file through a topological search algorithm, and the equipment is cut and changed from an A equipment node to a B equipment node according to a transaction business requirement; 3.The method of claim 1, wherein, if the transaction equipment list passes the comparison and checking, it is determined that the transaction equipment list meets the accuracy requirement; otherwise, specific data and an unmet condition are stored. The method comprises the following steps: graph model consistency checking, equipment uniqueness checking, equipment attribute integrity checking, model topology accuracy checking, and transaction graph model specification checking; if the transaction graph model file does not meet the comparison and checking, specific data and an unmet condition are stored and prompted.

Images