CN113793063A

CN113793063A - Method and device for detecting conflict of power distribution network planning project schemes

Info

Publication number: CN113793063A
Application number: CN202111142120.1A
Authority: CN
Inventors: 李俊辉
Original assignee: Guangdong Power Grid Co Ltd; Dongguan Power Supply Bureau of Guangdong Power Grid Co Ltd
Current assignee: Guangdong Power Grid Co Ltd; Dongguan Power Supply Bureau of Guangdong Power Grid Co Ltd
Priority date: 2021-09-28
Filing date: 2021-09-28
Publication date: 2021-12-14

Abstract

The invention discloses a method and a device for detecting a scheme conflict of a power distribution network planning project, wherein the method comprises the following steps: acquiring version directory information of a target power project; searching the version directory information in a pre-generated dependency relationship graph to judge whether the target power item has a dependency item; if the dependent item exists, acquiring item information of the dependent item, wherein the item information comprises a production state, warehousing information and boundary access equipment information; and judging whether the target power item conflicts with the dependent item or not according to the item information of the dependent item. The invention can realize the automation of the planning work of the power distribution network, effectively and comprehensively plan the planning project and reduce the dependence on manpower in the scheme conflict detection work of the planning project of the power distribution network.

Description

Method and device for detecting conflict of power distribution network planning project schemes

Technical Field

The embodiment of the application relates to a power distribution network data processing technology, in particular to a method and a device for detecting a power distribution network planning project scheme conflict.

Background

In an electric power system, there are associations and dependencies between planning project solutions, for example, implementation of a certain project usually needs to be based on a rack implemented by other projects, and when the planning project based on a certain project cannot be implemented or the solution changes for some reason, it may cause that the subsequent project solution cannot be implemented. Because the power distribution network planning lacks the support of a power project planning and analyzing system, the planning project is not effectively integrated, and whether project conflict exists in the project searching and analyzing process depending on manual work during the project planning, the automation of the power distribution network planning work needs to be realized urgently.

Disclosure of Invention

The application provides a method and a device for detecting conflict of a power distribution network planning project scheme, which are used for solving the problems that planning projects are not effectively planned overall and project conflict detection depends on manpower in the prior art.

In a first aspect, an embodiment of the present application provides a method for detecting a power distribution network planning project scheme conflict, where the method includes:

acquiring version directory information of a target power project;

searching the version directory information in a pre-generated dependency relationship graph to judge whether the target power item has a dependency item;

if the dependent item exists, acquiring item information of the dependent item, wherein the item information comprises a production state, warehousing information and boundary access equipment information;

and judging whether the target power item conflicts with the dependent item or not according to the item information of the dependent item.

In a second aspect, an embodiment of the present application further provides a device for detecting a power distribution network planning project scheme conflict, where the device includes:

the version directory information acquisition module is used for acquiring version directory information of the target power project;

the dependent item judging module is used for searching the version directory information in a pre-generated dependent relationship graph so as to judge whether the target power item has a dependent item;

the system comprises an item information acquisition module, a boundary access device information acquisition module and a boundary access device information acquisition module, wherein the item information acquisition module is used for acquiring item information of a dependent item if the dependent item exists, and the item information comprises a production state, warehousing information and boundary access device information;

and the item conflict judging module is used for judging whether the conflict exists between the target power item and the dependent item according to the item information of the dependent item.

In a third aspect, an embodiment of the present application further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the above method when executing the program.

In a fourth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the method described above.

The application has the following beneficial effects:

the version directory information of the target power project is obtained, the version directory information of the target power project is searched in a pre-generated dependency relationship graph to judge whether the target power project has a dependency project, if the dependency project exists, the project information of the dependency project is obtained, the project information comprises a production state, warehousing information and boundary access equipment information, and whether the target power project and the dependency project conflict or not is judged according to the project information of the dependency project, so that automation of planning work of the power distribution network is realized, the planning project is effectively integrated, and the dependence on workers in the scheme detection work of the power distribution network planning project is reduced.

Drawings

Fig. 1 is a flowchart of an embodiment of a method for detecting a power distribution network planning project scheme conflict according to an embodiment of the present application;

FIG. 2 is a schematic diagram of power project version management according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a process for creating an initial version of an annual planning project according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a dependency graph according to an embodiment of the present application;

fig. 5 is a schematic diagram of an example scenario of detecting a conflict of a power distribution network planning project scheme according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a dependency graph removal project according to an embodiment of the present application;

fig. 7 is a schematic diagram of a dependency graph editing project according to an embodiment of the present application;

FIG. 8 is a diagram of an updated dependency graph according to an embodiment of the present application;

fig. 9 is a block diagram of a structure of an embodiment of an apparatus for detecting a power distribution network planning project scheme conflict according to a second embodiment of the present application;

fig. 10 is a schematic structural diagram of an electronic device according to a third embodiment of the present application.

Detailed Description

The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures.

Example one

Fig. 1 is a flowchart of an embodiment of a method for detecting a power distribution network planning project scheme conflict according to an embodiment of the present application.

According to the embodiment, through version management of projects, the version directory information is used as a project identifier, the dependency relationship among the version directory information is established in the dependency relationship map according to the dependency condition among the projects displayed by the project topology map, the version directory information of each power project, the version directory information of the dependent project and the boundary access equipment number are recorded in the project index data table, when the target power project needs to be added or deleted, and the like, automatic detection of a power distribution network planning project scheme is achieved by using the project topology map, the dependency relationship map and the project index data table, and timely and automatic updating of the relation among the projects is achieved when the power project changes.

As shown in fig. 1, the present embodiment may include the following steps:

and step 110, obtaining version catalog information of the target power item.

In this step, a new planning general diagram version can be formed by establishing power project version management with a single project as a unit and influencing the planning general diagram after a planning project is implemented. Referring to a schematic diagram of power project version management in fig. 2, in a power grid system, a planning scheme generally takes years as a creation unit, the planning scheme of each year includes a plurality of planning projects, and each planning project uniquely corresponds to one version directory information.

Referring to the initial version creation process of the annual plan project of fig. 3, all annual plan scenarios may be created from the base year and the target year, forming a preliminary version chain. Each planning item corresponds to one version directory information, the planning items in the annual scheme correspond to a group of interval internal codes, the item numbers in the annual items are sequentially increased in the interval, and the item numbers determine the sequence in the corresponding annual planning. For example, to plan an annual grid for 2022 years, the current situation may be selected as the end of the last year (the end of the 2021 year), where 2021 year is the reference year and 2022 year is the target year. The specific creating process comprises the following steps: inserting records in an annual scheme sheet according to the starting year and the target year; records are inserted in the version chain, forming a base chain of annual solutions only.

In a specific implementation, the target power project may be a planning project newly added into the planning scheme, or may be a project which originally exists in the planning scheme and needs to be deleted or modified. When the target power item enters the version chain, the target power item can obtain the version directory information which belongs to the unique correspondence of the target power item.

In one embodiment, before step 110, the following steps may be further included:

receiving a new project request sent by a client, wherein the new project request comprises a project name and a planning year of a target power project;

determining version catalog information of the target power project in the dependency relationship map according to the planning year, and adding the version catalog information in the dependency relationship map, wherein the version catalog information comprises the planning year and a project number of the target power project under the planning year;

determining a dependent item corresponding to a target power item from a preset item topological graph, and obtaining version directory information of the dependent item, wherein the preset item topological graph is used for describing access relations among a plurality of items and recording the version directory information of each item;

and establishing a dependency relationship between the version directory information of the target power item and the version directory information of the dependent item in the dependency relationship map.

In implementation, referring to the schematic diagram of the dependency graph in fig. 4, the process of establishing and updating the dependency graph is as follows: the current year section can be frozen to extract the section of the current power grid resource center at the end of the reference year, namely when the 2021-2024 year is planned annually, 2020 year is taken as the reference year, the data of the time node at the end of the 2020 year in the resource library is extracted, and the dependency graph is updated on the basis of the data of the reference year. After the projects belonging to the same planning year are overlapped, several new planning general diagram versions are formed according to the planning year, the planning year is used as the main version number of the planning general diagram, each project produced in a certain planning year has the project number, and the project number and the main version are combined to be used as a sub-version of the year and are identified through sub-version indexes.

The interconnection between equipment elements in the power system is required to be effective, and a completely isolated power grid element or a subset of elements is generally not allowed to exist, so that the power grid planning project scheme needs to establish a connection relationship with elements outside the project scope, and the project in which the elements outside the project scope are located is called a dependent project of a target power project.

When determining the dependent items of the target power item and obtaining the version directory information of the dependent items, a preset item topological graph can be utilized. The project topological graph records the access relation among a plurality of projects, and can comprise version directory information of the projects and electrical component equipment information of the projects. The dependent item corresponding to the target power item can be directly found through the item topological graph, and the version catalog information of the dependent item is directly obtained from the item topological graph. In the current technology, determining the dependency relationship between power items through a topological algorithm is a relatively mature technology, and will not be described in detail here.

After the version directory information of the target power item and the version directory information of the dependent items thereof are determined, the dependency relationship can be established in the dependency relationship map. As shown in fig. 4, the planning items under the main version of each year are represented by circles and reference numerals, and the connecting lines between the item version directory information represent the dependency relationships between the items.

The dependency relationships of some items in FIG. 4 can be expressed as follows:

(1) the item with the version directory information of 2021.1 needs to be accessed to boundary access equipment on the existing power grid diagram, namely the item depends on the section of the existing power grid; the project with the version directory information of 2022.1 needs to be accessed to the power grid element created by the project with the version directory information of 2021.1, and the project depends on the project with the version directory information of 2021.1;

(2) the project with the version directory information of 2024.4 is connected with the existing power grid element and the power grid element created by the project with the version directory information of 2023.4, namely the project depends on the existing power grid section and the project with the version directory information of 2023.4;

(3) the item with the version directory information of 2021.5 depends on the item with the version directory information of 2021.4 put into production in the same year;

(4) the item with version directory information of 2021.4 depends on the item with version directory information of 2021.3 through manual setting logic;

(5) the item of version directory information 2021.5 is dependent on the item of version directory information 2021.4 by a manual setup logic.

In the above process, referring to fig. 4, by introducing the plan view version chain management, when a new project request is received, the power project is identified by the version directory information, the version directory information of the target power project is added to the dependency relationship map, and the dependency relationship between the target power project and the version directory of the dependent project is established, so that the dependency relationship between the projects is clearly shown, and the efficiency of detecting conflicts between the projects can be well improved.

In one embodiment, for determining the version directory information of the target power item in the dependency graph according to the planned year in the above steps, the following steps may be included:

searching whether a planning year of the target power project exists in the dependency relationship map;

if the current project number exists, adding the project number according to a certain sequence according to the existing project number under the planning year, and using the project number as the project number of the target power project;

if not, the planned year is added, and the project number is added according to a certain sequence as the project number of the target power project.

In implementation, the expression form of the version directory information may be a planning year combined with an item number, and such an expression form may directly represent the planning year of the item, for example, the planning year of a certain power item is 2021, and the item number is 3 in 2021, then the version directory information of the power item may be represented as 2021.3.

The target power project can be a non-first power project under the planning year of the target power project, the main version of the planning year is established in the dependency relationship map at the moment, the corresponding planning year can be found, the maximum value of the current project number under the planning year is found, one can be added on the basis of the maximum value of the number, and finally the version directory information of the target power project is determined. For example, referring to fig. 4, assuming that the planned year of the target power project is 2024, and currently in 2024, the maximum item number is 5, when the target power project is added to the planned plan in 2024, the item number is 6.

The target power project may also be the first power project under the planning year of the target power project, and at this time, the planning scheme of the planning year is not established by the dependency relationship map, so that the planning year cannot be found by the dependency relationship map. The main version of the planned year may be established in the dependency graph according to the planned year, and then corresponds to the first power project under the planned year, where the number of the target power project may be 1.

And step 120, searching version directory information in a pre-generated dependency relationship graph to judge whether the target power item has a dependency item.

In this step, the dependency relationship between the version directory information of the target power item and the version directory information of the dependent item is recorded in the dependency relationship map, and in the case that the version directory information of the target power item has been determined, the version directory information of the dependent item corresponding to the target power item can be found through the dependency relationship map. Referring to fig. 4, for example, for the power item with item number 3 in 2023, the power item with item number 2 in 2023 can be found by the connection relationship of fig. 4.

And step 130, if the dependent item exists, acquiring item information of the dependent item, wherein the item information comprises a production state, warehousing information and boundary access equipment information.

In the step, the target power item is searched in the dependency relationship map according to the version directory information of the target power item, so that the target power item is determined to have a dependent item, and the version directory information of the dependent item is obtained. When the project information of the electric power project is input and stored, the project information can be corresponding to the version catalog information, and the version catalog information of the dependent project obtained from the dependency relationship map can be matched with the project information of the dependent project, so that the project information of the dependent project is obtained.

In addition, the elements or devices that are present in the dependent item and that have an electrical connection with the target power item are referred to as adjacent border elements, i.e. border access devices. Whether the border access device is available is a necessary condition for determining whether the target power item can be executed according to the scheme.

In one embodiment, step 130 may further include the steps of:

step 130-1, according to the version directory information of the dependent item, searching in a preset item index data table to determine the number of the boundary access device, where the item index data table is used to record the version directory information of each power item, the version directory information of the dependent item, and the number of the boundary access device.

In this step, the version directory information of each power item, the version directory information of the dependent item that depends on, and the boundary access device number may be recorded by creating an item index data table. Referring to the item index data table in table 1 below, for example, in the item index data table in which the relationship between the item indexes recorded in table 1 corresponds to the partial dependency relationship established by the dependency relationship map in fig. 4, as compared with the dependency relationship map in fig. 4, in addition to the version directory information of the dependency item of the target power item, the boundary access device number corresponding to the dependency item may also be found, so as to provide further information for information search of the dependency item.

Annual major edition	Item sub-version indexing	Dependent item sub-version indexing	Border access device numbering
				2021	2021.1	2020	GISID001
2021	2021.2	2020	GISID002
				2021	2021.3	2020	GISID003
2021	2021.4	2020	GISID004
				2021	2021.5	2021.4	GISID005
2022	2022.1	2021.1	GISID006
				2022	2022.2	2020	GISID007
2022	2022.3	2020	GISID008
				2022	2022.4	2022.3	null
2022	2022.4	2021.4	GISID010
				2022	2022.5	2022.4	null
2023	2023.2	2022.2	GISID012
				2023	2023.3	2023.2	GISID013
2023	2023.4	2020	GISID014
				2024	2024.4	2020	GISID015
2024	2024.4	2023.4	GISID016

TABLE 1

And step 130-2, searching corresponding boundary access equipment information in a preset project topological graph according to the boundary access equipment number.

In this step, when the corresponding boundary access device number is determined from the item index data table, the boundary access device corresponding to the boundary access device number may be searched in the preset item topology map, and information of the boundary access device, such as the number of topology connection ports of the power grid elements such as lines and devices, the specific situation of the connected ports, the specific situation of the connectable ports, and the like, may be acquired from the preset item topology map.

And step 130-3, searching the production state and the warehousing information of the dependent item in a pre-generated item library according to the version directory information of the dependent item, wherein the item library is used for storing the production state and the warehousing information of the item marked by the version directory information.

In this step, the project library generated in advance stores the production status and warehousing information of the power project identified by the version directory information, and may further include information such as a corresponding project name.

By the version directory information of the dependent item, the detailed information of the dependent item, such as the production state, the warehousing information and the like, can be found in the item library corresponding to the version directory information.

And if a certain electric power project is already put into operation, the project is allowed to be put into operation after completion of acceptance of the electric power project and network access approval. After the equipment is put into operation, production (operation, maintenance, shutdown, etc.) can be formally carried out, and scheduling management and the like can be received.

For the warehousing information of the project, in the power system, if a certain power project is warehoused, it means that the power project enters a year project library of a certain year, that is, there is a specific planned year, and if the project is not warehoused, the power project may be invalidated in the planning process, removed from the year project library, or enter the year project library of which the year has not yet been established.

Step 140, determining whether the target power item and the dependent item conflict or not according to the item information of the dependent item.

In this step, the reasons for conflicts between items are mainly resource conflicts and logical conflicts. For resource conflict, it refers to conflict caused by competing for occupation or editing a certain resource between two or more items, for example, the number of topological connection ports of a power grid element such as a line, a device, etc. is limited (except for a bus section, general distribution network elements are all dual-port elements), and the topological connection of a single port has uniqueness and exclusivity, if one end of a certain element has access to other elements, the port of the element cannot be accessed to other elements any more, and conflict occurs when a plurality of items attempt to access the same port of a certain element; similarly, if an item deletes the component itself, other items may attempt to occupy the port of the deleted component. In addition, overhead lines, cable corridors, etc. are also resource conflicts, and multiple projects attempting to occupy corridor channels may also create conflicts.

For the logic conflicts among a plurality of projects, resource occupation conflicts may not exist among some project schemes, but some logic problems may be generated after the projects are overlapped, for example, the rack structure problems such as atypical wiring, a first segment of looped network and the like may be generated after a plurality of rack improvement projects are overlapped, and the problems of heavy overload of lines, branches, equipment and the like may also be generated.

In addition, the dependency relationship between project schemes can be divided into dependency caused by avoiding resource conflict and dependency caused by logical relationship between projects according to the conflict cause between projects.

For resource dependence, the dependence relationship between the projects can be automatically identified and established through the occupation conditions of boundary access equipment and channel resources between the projects.

For the logic dependence, the dependence between some projects is difficult to be automatically identified by the algorithm logic temporarily, for example, the dependence relationship related to the grid structure analysis and the load change analysis is usually obtained only after a large amount of calculations such as large-scale grid diagnosis and identification, load change analysis, load prediction and the like are performed, the algorithm difficulty is high, and the dependence relationship between the projects can be set manually.

In one embodiment, step 140 may further comprise:

and if the dependent item is judged to be put into production according to the production state, judging whether the dependent item and the target power item have access conditions or not according to the boundary access equipment information, and if the dependent item and the target power item do not have the access conditions, judging that the target power item conflicts with the dependent item.

In this step, according to the production state of the dependent item searched from the item library, if the dependent item is determined to have been produced, whether the item scheme has a conflict is determined by the boundary access device.

In the process of planning a project and drawing a project topological graph, the connection condition of a target power project and an element outside the project range can be recorded, and when judging whether the dependent project and the target power project have access conditions according to the boundary access equipment information, whether the boundary access equipment of the target power project is available or not is checked, wherein the check includes checking whether the element is still on the graph or not, whether the element can also provide a port for accessing the target power project or not, and the like.

In one implementation, when a project topological graph is drawn, a boundary access device record list of each planning project can be established, when scheme conflict detection is needed, only whether the boundary access device of a target power project is available is needed to be checked, if the boundary access device is unavailable, the current scheme cannot be implemented according to the original plan, and a user needs to be prompted that a scheme conflict is generated currently.

In one embodiment, the warehousing information includes a planned warehousing time, and step 140 may further include the steps of:

if the dependent project is judged not to be put into production according to the production state, judging whether the planned warehousing time of the dependent project is earlier than the planned warehousing time of the target power project or not according to the planned warehousing time;

if not, the target power item and the dependent item are judged to have conflict.

In this step, if it is determined that the dependent item is not put into production according to the production state, the determination is made according to the planned warehousing time, for example, the planned warehousing time of the target power item is 2022 years, and the planned warehousing time of the dependent item is 2023 years, which means that if the item is advanced according to the original planned time, the target power item is completed but the dependent item is not started yet, and the target power item cannot normally operate, and therefore, when the planned warehousing time of the dependent item is later than the planned warehousing time of the target power item, it is determined that the target power item and the dependent item are in conflict.

Correspondingly, when the planned warehousing time of the dependent project is earlier than that of the target power project, namely although the dependent project does not start to be put into production, the dependent project is built earlier than the target power project according to normal project planning, at this time, no conflict exists in the warehousing time of the project, and whether the dependent project and the target power project have access conditions or not can be judged according to the boundary access equipment information, so that the judgment whether the conflict exists between the dependent project and the target power project or not can be completed.

In addition, aiming at conflicts of other power grid resources, in the process of drawing the scheme, by maintaining the corresponding conditions of cable wire laying and cable channel occupation of each project, including which pipe ditches need to be occupied by cables, the line number scale requirement of the occupied pipe ditches and the like, whether enough residual resources exist in the cable pipe ditches needing to be occupied by the target power project to meet the requirement of the project can be judged when the scheme conflict is required to be checked, and if the requirement cannot be met, the conflict condition of the current scheme is prompted to a user.

For other project scheme conflicts which are difficult to automatically detect by a system algorithm, the prompt of the project scheme conflict can be triggered by manually setting the dependency relationship at the project level.

In a specific implementation, referring to a schematic diagram of an example of a scenario for detecting a conflict of a power distribution network planning project scheme in fig. 5, a dependency relationship between projects is generated in a drawing process, a planning project is selected from a planning reserve project library and enters an annual project library, that is, a planning year of a target power project is determined, all the dependency projects of the target power project are found, one or more dependency projects of the target power project may be possible, and then the dependency projects are detected one by one to determine whether a project conflict exists.

When the detection is carried out, whether the dependent item is put into production is judged, if the dependent item is put into production, whether the access boundary equipment has the access condition is judged, if the access condition is met, whether other dependent items exist is judged, then the detection of the other dependent items is carried out, and if the access condition is not met, the user is reminded that the current dependent items conflict.

If the item is not put into production, judging whether the dependent item is listed in a year item library of the same year or earlier year than the target power item, if so, judging whether the access boundary equipment has an access condition, if so, judging whether other dependent items exist and then entering detection of the other dependent items, and if not, reminding a user that the current dependent item conflicts. And if the dependent items are not put in storage, reminding the user that the items with the dependence on the target power item are not put in storage.

In one embodiment, the method may further include the steps of:

when a deletion request for the target power item is received, the version directory information of the target power item is deleted in the dependency graph, and the dependency associated with the version directory information of the target power item is deleted.

In this step, an operation that requires deletion of the target power item may occur due to a planning change, capital, or the like, and when a deletion request for the target power item is received, the deletion request may include version directory information of the target power item, delete the version directory information in the dependency relationship map, and delete a dependency relationship between a dependent item and a depended item of the version directory information.

Meanwhile, the item index data table can be updated.

In the power system, in addition to the conflict detection when a power item is newly added, item conflicts are likely to occur when items are deleted, modified, and the year of the project is adjusted, and therefore, the conflict detection is also required. Because the dependence among the projects is unidirectional along with the year, the project of the next year is newly added, deleted and modified, the project of the previous year is generally not influenced, the project of the same production year generally does not allow a plurality of projects to repeatedly transform the same equipment in the same year, and the projects with conflicts can not be simultaneously warehoused because the projects are overlapped according to the warehousing sequence in the version chain management, so the projects of the same year generally do not have conflicts at the system level.

In a specific implementation, the following 4 scenarios can be referred to for generating project conflicts:

(1) adding a project plan in the previous year may result in the conflict between projects in the following year and the added projects, as shown in table 2 below:

serial number	Annual major edition	Sub-version index	Dependent associative sub-version indexing	Border access device numbering
					1	2021	2021.1	2020	GISID001
2	2021	2021.2	2020	GISID002
					3	2021	2021.3	2020	GISID003
4	2021	2021.4	2020	GISID004
					5	2021	2021.5	2021.4	GISID005
6	2022	2022.1	2021.1	GISID006
					7	2022	2022.2	2020	GISID007
8	2022	2022.3	2020	GISID008
					9	2022	2022.4	2022.3	null
10	2022	2022.4	2021.4	GISID010
					11	2022	2022.5	2022.4	null
12	2023	2023.2	2022.2	GISID012
					13	2023	2023.3	2023.2	GISID013
14	2023	2023.4	2020	GISID014
					15	2024	2024.4	2020	GISID015
16	2024	2024.4	2023.4	GISID016
					17	2021	2021.1.1 (New)	2021.1	GISID006

TABLE 2

Assuming that a lot of projects are currently drawn on the project topological graph and the dependency shown in table 2 is formed, a newly added project with version directory information of 2021.1.1 (refer to row 17) needs to be added to the total graph of version 2021, the newly-built cable line of the project is connected to the 604 switch (GISID006) in the newly-built drop box with version directory information of 2021.1 project (refer to row 1), but the drop box switch is already occupied by 2022.1 projects in the next 2022 years in the existing plan (refer to row 6), and at this time, a project conflict may be generated, and the user needs to be reminded to check and process the conflict.

(2) Deleting or modifying an item schema in a previous year results in a conflict in a subsequent year depending on the item that was deleted or modified, as shown in table 3 below:

serial number	Annual major edition	Sub-version index	Dependent associative sub-version indexing	Border access device numbering
					1	2021	2021.1	2020	GISID001
2	2021	2021.2	2020	GISID002
					3	2021	2021.3	2020	GISID003
4	2021	2021.4	2020	GISID004
					5	2021	2021.5	2021.4	GISID005
6	2022	2022.1	2021.1	GISID006
					7	2022	2022.2	2020	GISID007
8	2022	2022.3	2020	GISID008
					9	2022	2022.4	2022.3	null
10	2022	2022.4	2021.4	GISID010
					11	2022	2022.5	2022.4	null
12	2023	2023.2	2022.2	GISID012
					13	2023	2023.3	2023.2	GISID013
14	2023	2023.4	2020	GISID014
					15	2024	2024.4	2020	GISID015
16	2024	2024.4	2023.4	GISID016

TABLE 3

As shown in table 3 above, the entry whose version directory information is 2022.1 (refer to line 6) depends on the entry whose version directory information is 2021.1 (refer to line 1), and if the entry of 2021.1 is deleted, the entry of 2022.1 cannot be implemented, and a conflict occurs.

On the other hand, the reason why the item with the version directory information of 2022.1 depends on the item with the version directory information of 2021.1 is that the former needs to access a certain newly-built switch (GISID006) of the latter, and if the switch (GISID006) is already accessed by other lines after the project plan of the front end is modified, 2022.1 projects in the following years may also lose the condition of accessing the switch, and a project conflict occurs.

In one implementation, when items need to be removed, conflicting relationships can also be displayed in the dependency graph, and relationship adjustments between items are implemented. Referring to the dependency relationship graph item removal schematic diagram of fig. 6, first, whether version directory information of a target power item exists is searched in the dependency relationship graph, if the target power item is not depended on by another power item, the version directory information of the target power item is directly removed from the dependency relationship graph, if the target power item is depended on, it means that other items will be affected after the target power item is deleted, and a conflict prompt is sent at this time. In addition, a version change table can be established to record the change condition of the item.

(3) The production years for a project plan are advanced as shown in table 4 below:

serial number	Annual major edition	Sub-version index	Dependent associative sub-version indexing	Border accessDevice numbering
					1	2021	2021.1	2020	GISID001
2	2021	2021.2	2020	GISID002
					3	2021	2021.3	2020	GISID003
4	2021	2021.4	2020	GISID004
					5	2021	2021.5	2021.4	GISID005
6	2022	2022.1	2021.1	GISID006
					7	2022	2022.2	2020	GISID007
8	2022	2022.3	2020	GISID008
					9	2022	2022.4	2022.3	null
10	2022	2022.4	2021.4	GISID010
					11	2022	2022.5	2022.4	null
12	2023	2023.2	2022.2	GISID012
					13	2023	2023.3	2023.2	GISID013
14	2023	2023.4	2020	GISID014
					15	2024	2024.4	2020	GISID015
16	2024	2024.4	2023.4	GISID016

TABLE 4

As shown in table 4 above, the item with version directory information of 2023.2 (refer to row 12) is implemented at 2023 years before the project is implemented by 2021 years, but it is not put into production in 2021 years depending on item 2022.2 (refer to row 7), and then a conflict occurs between items.

(4) After the estimated production period of a project plan, the following table 5 shows:

TABLE 5

As shown in table 5 above, the item with version directory information of 2023.2 (refer to row 12) is implemented at 2023 years, if the item is to be postponed to 2024 years, but the item 2023.3 (refer to row 13) dependent on 2023.2 is implemented at 2023 year, the element access condition from the dependent item 2023.2 is lost, and conflict occurs between items.

In one implementation, when a project needs to be edited and adjusted due to a conflict or other reasons, the project diagram may be edited with reference to the dependency relationship graph in fig. 7, and if it is determined that the dependency relationship graph does not have the version directory information of the target power project by searching, the version directory information is obtained first and added to the dependency relationship graph, and then editing is started. And if the version directory information of the target power item is found to exist in the dependency relationship map, directly starting to edit the item. In addition, by establishing a version change table, the situation of insertion change of the item and the like can be recorded.

When the scheme is implemented, in a power grid system, scheme inheritance exists among power items. The inheritance of a planning project generally has the following three scenarios:

(1) after an item is newly added, edited and deleted in the previous year, the latest information of the item needs to be synchronously updated (or propagated) to the edge general graph of the subsequent year, for example, an item is newly added to the item general graph in the previous year 2021, the graph of the item automatically appears on the general graph in the

same year

2022, 2023, 2024. On the premise that no scheme conflict exists, the project scheme with conflict cannot be automatically transmitted, and a user needs to modify and confirm;

(2) after a project adjusts the production period, the project associated with the project may conflict, and it is necessary to adjust the production period of the target power project to be adjusted and the associated project with the conflict at the same time, and transmit the adjusted project information to the distribution summary chart of the following year;

(3) in a power grid system, a power grid annual rolling plan is generally developed once every year, project plan results which are input in the previous round of planning are inherited and reused, plan plans comprising 2020, 2021 and 2022 are completed in 2020 years of the previous year (plan of at least 3 years is made in the general annual rolling plan), if the rolling plan of 2021 year is developed now, plan plans of 2021 and 2022 years planned in 2020 need of inheritance and reuse in principle, but it is impossible to inherit and reuse the original 2021 of the previous round,

the old planning project plan of 2022 completely empties redo. After the actual power grid transformation in 2020, the actual state of the power grid may not be completely consistent with the planned 2020 state, which may result in 2021,

the old project plan of 2022 may create conflicts. For example, an electric room is originally planned to be newly built in 2020, but actually, because the electric room cannot be built on a field site, all projects needing to access the newly built electric room in the subsequent 2021 and 2022 years have conflicts, and the projects cannot be inherited and reused.

For the first and second scenarios, the technical difficulty at present is to implement the technical implementation of data migration, reconstruction of version chains and the like of project schemes on main version planning general diagrams of different years on the basis of perfecting scheme conflict detection, and the present application is not developed in detail.

For scenarios where the third scheme inherits, the following process can be used:

(1) removing the implemented project from the planning project library, and if any project is not implemented or not put into operation (whether the electronic handover is implemented is taken as a judgment basis), migrating the corresponding project to the next-year version of the graph;

(2) the original 2020 standard section needs to be changed into a 2021 section for latest electronic handover; checking all items of which the dependent associated sub-version indexes are 2020 current in an item index data table, and if the boundary access equipment is still available in the latest 2021 section, continuing to inherit and use the items; if the boundary access equipment is unavailable, a scheme conflict may exist, and a user needs to be prompted to check and confirm;

(3) the serial number of the project scheme equipment in the original planning state is regenerated after project production and electronic handover, which can also cause that part of serial numbers of boundary access equipment maintained in the original project index data sheet are invalid, and the invalid serial number of the boundary access equipment needs to be updated to realize inheritance and reuse of the planning scheme;

(4) for the items for manually setting the item association relationship, for example, all items which depend on 2020 and 2021 major versions need to be checked and confirmed manually.

An example of the inheritance process for the third inheritance scenario above is as follows:

assuming that the rolling planning revision of the next year (2022 years) is now to be carried out based on the completion of the original revision of the 2021 year and the planned projects of the 2021 year all being put into operation as scheduled, the projects which were planned to be put into production in the 2021 year in the original project library should be moved out of the planning project library as shown in the following table 6:

TABLE 6

When a new year revision is carried out, the planning reference year is adjusted to 2021, the current situation is required to be updated to the latest current situation along the layout after electronic handover at the end of 2021 year along the layout, all items with 'dependent associated sub-version index' of 2020 in the item index data sheet need to check the boundary access equipment number, whether the element has access conditions in the current situation along the layout in the latest 2021 year is judged, if the element can still be accessed, the corresponding item scheme can still be inherited and reused, and the 'dependent associated sub-version index' of the element is updated to 2021 year; if the component does not have the access condition and the corresponding project plan cannot be inherited, the user needs to be prompted to verify and confirm, as shown in table 7 below:

TABLE 7

As shown in table 7 above, since the border access device number in the original plan state is definitely replaced by the formal device number after the original 2021.1 and 2021.4 projects are delivered, the associated 2022.1 and 2022.4 projects need to inherit the original plan and cannot find the corresponding border access device, and at this time, the user is required to confirm and modify the two plans before the plans can be used for annual planning in the next year.

In addition, the dependency graph may be updated according to the adjusted dependency between the projects of the next year, and for comparison before and after the update, reference may be made to fig. 4 and fig. 8, where fig. 8 is a schematic diagram of the dependency graph updated on the basis of fig. 4.

In the embodiment of the invention, the version directory information of the target power project is obtained, the version directory information of the target power project is searched in the pre-generated dependency relationship map to judge whether the target power project has a dependent project, if the dependent project exists, the project information of the dependent project is obtained, the project information comprises a production state, warehousing information and boundary access equipment information, and whether the target power project and the dependent project conflict or not is judged according to the project information of the dependent project, so that the automation of the planning work of the power distribution network is realized, the planning project is effectively integrated, and the dependence on manpower in the scheme detection work of the power distribution network planning project is reduced.

Example two

Fig. 9 is a device for detecting a power distribution network planning project scheme conflict according to a second embodiment of the present invention, where the device includes:

a version directory information obtaining module 910, configured to obtain version directory information of the target power item;

a dependent item determining module 920, configured to search the version directory information in a pre-generated dependency relationship map to determine whether a dependent item exists in the target power item;

an item information obtaining module 930, configured to obtain item information of a dependent item if the dependent item exists, where the item information includes a production state, warehousing information, and boundary access device information;

and an item conflict judging module 940, configured to judge whether a conflict exists between the target power item and the dependent item according to the item information of the dependent item.

In one embodiment, the apparatus further comprises:

the system comprises a new project request receiving module, a new project request receiving module and a new project scheduling module, wherein the new project request receiving module is used for receiving a new project request sent by a client, and the new project request comprises a project name and a planning year of a target power project;

the version directory information determining module is used for determining the version directory information of the target power project in the dependency relationship map according to the planning year;

the version directory information adding module is used for adding the version directory information in the dependency relationship map, wherein the version directory information comprises the planning year and the project number of the target power project under the planning year;

the dependent item determining module is used for determining a dependent item corresponding to the target power item from a preset item topological graph, and obtaining version directory information of the dependent item, wherein the preset item topological graph is used for describing access relations among a plurality of items and recording the version directory information of each item;

and the dependency relationship establishing module is used for establishing a dependency relationship between the version directory information of the target power item and the version directory information of the dependency item in the dependency relationship map.

In an embodiment, the version directory information determining module is specifically configured to:

if the current project number exists, adding a project number according to a certain sequence according to the existing project number under the planning year, and using the project number as the project number of the target power project;

and if the target power project does not exist, the planning year is added, and project numbers are added according to a certain sequence to serve as the project numbers of the target power project.

In one embodiment, the project information acquisition module 930 includes the following sub-modules:

the boundary access equipment number determining submodule is used for searching in a preset item index data table according to the version directory information of the dependent items so as to determine the number of the boundary access equipment, and the item index data table is used for recording the version directory information of each power item, the version directory information of the dependent items and the number of the boundary access equipment;

the boundary access equipment information searching submodule is used for searching corresponding boundary access equipment information in the preset project topological graph according to the boundary access equipment number;

and the commissioning status and warehousing information searching submodule is used for searching the commissioning status and warehousing information of the dependent item in a pre-generated item library according to the version directory information of the dependent item, and the item library is used for storing the commissioning status and the warehousing information of the item identified by the version directory information.

In one embodiment, the apparatus further comprises:

and the deleting module is used for deleting the version directory information of the target power item in the dependency relationship map and deleting the dependency relationship associated with the version directory information of the target power item when a deleting request for the target power item is received.

In one embodiment, the item conflict determination module 940 may be configured to:

and if the dependent item is judged to be put into production according to the production state, judging whether the dependent item and the target power item have access conditions or not according to the boundary access equipment information, and if the dependent item and the target power item do not have the access conditions, judging that the target power item and the dependent item are in conflict.

In an embodiment, the warehousing information includes a planned warehousing time, and the project conflict determination module 940 is further configured to:

if not, determining that the target power item conflicts with the dependent item.

It is noted that the device for detecting a power distribution network planning project scheme conflict provided in the embodiment of the present application can execute the method for detecting a power distribution network planning project scheme conflict provided in the embodiment of the present application, and has functional modules corresponding to the execution method and beneficial effects.

EXAMPLE III

Fig. 10 is a schematic structural diagram of an electronic device according to a third embodiment of the present application, as shown in fig. 10, the electronic device includes a processor 1010, a memory 1020, an input device 1030, and an output device 1040; the number of the processors 1010 in the electronic device may be one or more, and one processor 1010 is taken as an example in fig. 10; the processor 1010, the memory 1020, the input device 1030, and the output device 1040 in the electronic apparatus may be connected by a bus or other means, and fig. 10 illustrates an example of connection by a bus.

Memory 1020, which is a computer-readable storage medium, may be used to store software programs, computer-executable programs, and modules, such as program instruction modules corresponding to method embodiments in the embodiments of the present application. The processor 1010 executes various functional applications and data processing of the electronic device by executing software programs, instructions and modules stored in the memory 1020, thereby implementing the above-described method.

The memory 1020 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 1020 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 1020 may further include memory located remotely from the processor 1010, which may be connected to an electronic device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The input device 1030 is operable to receive input numeric or character information and generate key signal inputs related to user settings and function controls of an electronic apparatus. Output device 1040 may include a display device such as a display screen.

Example four

A storage medium containing computer-executable instructions for performing the method in the method embodiments when executed by a computer processor is also provided.

From the above description of the embodiments, it is obvious for those skilled in the art that the present application can be implemented by software and necessary general hardware, and certainly can be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods described in the embodiments of the present application.

It should be noted that, in the embodiment of the foregoing apparatus, the modules and modules included in the apparatus are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional modules are only used for distinguishing one functional module from another, and are not used for limiting the protection scope of the application.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims

1. A method for detecting a scheme conflict of a power distribution network planning project is characterized by comprising the following steps:

acquiring version directory information of a target power project;

2. The method according to claim 1, wherein before the obtaining of the version directory information of the target power item, the method further comprises:

determining a dependent item corresponding to the target power item from a preset item topological graph, and obtaining version directory information of the dependent item, wherein the preset item topological graph is used for describing access relations among a plurality of items and recording the version directory information of each item;

establishing a dependency relationship between the version directory information of the target power item and the version directory information of the dependent item in the dependency relationship graph.

3. The method of claim 2, wherein determining version inventory information for the target power project in the dependency graph according to the projected year comprises:

4. The method according to claim 3, wherein the obtaining item information of the dependent item if the dependent item exists comprises:

according to the version directory information of the dependent items, searching in a preset item index data table to determine the number of the boundary access equipment, wherein the item index data table is used for recording the version directory information of each power item, the version directory information of the dependent items and the number of the boundary access equipment;

searching corresponding boundary access equipment information in the preset project topological graph according to the boundary access equipment number;

and searching the production state and the warehousing information of the dependent item in a pre-generated item library according to the version directory information of the dependent item, wherein the item library is used for storing the production state and the warehousing information of the item which takes the version directory information as a mark.

5. The method according to any one of claims 1-4, further comprising:

when a deletion request for the target power item is received, deleting the version directory information of the target power item in the dependency relationship map, and deleting the dependency relationship associated with the version directory information of the target power item.

6. The method according to any one of claims 1 to 4, wherein the determining whether the target power item and the dependent item have a conflict according to the item information of the dependent item includes:

7. The method of any of claims 1-4, wherein the binned information comprises a planned binning time;

the determining, according to the item information of the dependent item, whether there is a conflict between the target power item and the dependent item, further includes:

8. A device for detecting a scheme conflict of a power distribution network planning project is characterized by comprising:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-7 when executing the program.

10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.