A substation intelligent design system based on topological relations

Abstract

The application discloses a transformer substation intelligent design system based on a topological relation and relates to the technical field of electric power engineering. The system comprises an influence checking module, a same-source object in a three-diagram atlas correlation record is subjected to consistency review, a topological change event record is generated, a local engineering range is determined with the same-source identification in the topological change event record as the center, a topological constraint check is performed on the local engineering range, and a local influence domain check record is generated; a maintenance correction module, according to the local influence domain check record, a topological maintenance correction is performed on the local engineering range with layout conflicts, the spatial layout relationship is adjusted under the condition that the electrical connection sequence, the port corresponding relationship and the period attribute relationship remain unchanged, and a transformer substation intelligent achievement set is output. The application unifies object correlation through composite topological engineering atlas and constrains local layout adjustment through topological maintenance correction, thereby improving multi-atlas synchronous consistency, traceability and engineering implementability.

Description

Technical Field

[0001] This invention relates to the field of power engineering technology, and in particular to an intelligent substation design system based on topology relationships. Background Technology

[0002] As power grid construction moves towards high reliability, standardization, and digital collaboration, the compilation of substation engineering deliverables is gradually shifting from traditional two-dimensional drafting, manual verification, and professional transfer methods to intelligent processing methods based on engineering data modeling, rule-driven constraints, and deliverable linkage. Existing substation engineering auxiliary technologies can typically generate electrical main wiring diagrams, general layout diagrams, and some 3D models based on typical bays, equipment libraries, graphic element libraries, and layout templates. They also improve the reuse efficiency of engineering deliverables by standardizing equipment parameters, typical wiring schemes, and layout rules. In new construction, expansion, and phased construction projects, there are not only electrical connection relationships between engineering objects, but also spatial occupancy relationships, equipment parameter inheritance relationships, phase succession relationships, and common source mapping relationships between multiple types of drawings.

[0003] Existing technologies still rely heavily on element association and template-based calling at the drawing level for engineering data organization. There is a lack of unified topological representation among electrical bays, equipment, ports, and space occupants, making it difficult to form stable common-source associations between electrical logic diagrams, spatial layout diagrams, and engineering configuration data. This can easily lead to problems such as unclear scope of impact of local modifications, incomplete drawing synchronization, and omission of phase connection relationships. Existing layout optimization usually focuses more on layout compactness, floor space, and drawing generation efficiency, and does not adequately consider the maintenance mechanism of electrical connection sequence, port correspondence, and phase attribute relationships. Local spatial conflict corrections may cause implicit changes in electrical logic or phase succession relationships, thereby affecting the traceability and feasibility of engineering results. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a substation intelligent design system based on topology to solve the problem that insufficient topological association of substation engineering objects makes it difficult to coordinate and maintain the synchronization of multiple maps and the local layout correction.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: This invention provides a substation intelligent design system based on topology relationships, comprising: a topology benchmark module, which acquires basic substation engineering data and performs topology benchmark processing to determine engineering boundaries, rule constraints, phase attributes, and bay configuration sources, generating engineering topology benchmark records; a graph fusion module, which performs anchoring instantiation processing based on the engineering topology benchmark records, mapping electrical bay objects, equipment objects, port objects, and space occupancy objects to engineering topology objects with common source identifiers, and performs topology fusion on the electrical connection relationships, spatial constraint relationships, equipment attribute relationships, and phase attribute relationships between engineering topology objects to generate a composite topology engineering graph; and a projection association module, which verifies the connection closure status, equipment attribute acceptance status, and graph projection of each engineering topology object in the composite topology engineering graph. The system generates a projectable topology engineering map based on the projection conditions. Through logical projection and layout projection, this map is transformed into an electrical logic map and a spatial layout map, respectively. A three-map association record is generated based on the source identifier. The influence verification module performs consistency checks on the source objects in the three-map association record, generating a topology change event record. Using the source identifier in the topology change event record as the center, it determines the local engineering scope, performs topology constraint verification on the local engineering scope, and generates a local influence domain verification record. The preservation correction module performs topology preservation correction on the local engineering scope with layout conflicts based on the local influence domain verification record. While maintaining the electrical connection sequence, port correspondence, and period attribute relationship, it adjusts the spatial layout relationship and outputs the substation intelligent result set.

[0007] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps for generating the engineering topology benchmark record are as follows: The site range, construction scale, voltage level and engineering rule source in the basic data of substation engineering are coupled with boundary constraints to determine the engineering boundary and corresponding rule constraints. The available range of the engineering boundary is corrected according to the layout requirements and bay access requirements corresponding to the voltage level, and a boundary constraint benchmark record is generated. Based on the boundary constraint benchmark record, the construction period information and wiring configuration requirements in the substation project basic data are analyzed for period continuity. The period attributes are determined under the corresponding project boundary, and the sources of callable bay configurations, the releasable reserved range, and the restricted configuration range are determined based on the period attributes, generating the period bay continuity record. The topology benchmark is bound to the boundary constraint benchmark record and the period interval acceptance record. The engineering boundary, rule constraint, period attribute and interval configuration source are written into the benchmark relationship under the same boundary to generate the engineering topology benchmark record.

[0008] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps of anchoring and instantiating electrical bay objects, equipment objects, port objects, and space occupant objects according to the engineering topology benchmark record and mapping them to engineering topology objects with the same source identifier are as follows: Based on the phase attributes and interval configuration sources under the same boundary in the engineering topology baseline record, the phase availability screening and boundary adaptation correction are performed on the interval configuration sources to determine the target electrical interval objects and their assembleable equipment objects, port objects and space occupancy objects, and generate interval assembly candidate records. Based on the candidate records for bay assembly and the corresponding rule constraints, the target electrical bay object is hierarchically assembled with the assembleable equipment objects, port objects, and space occupant objects, and a common-source identifier is configured to generate an anchored bay topology record.

[0009] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps for generating the composite topology engineering map are as follows: Using the same source identifier in the anchored interval topology record as an index, the port connection relationship between electrical interval objects is identified, and the electrical connection relationship is determined by combining the access direction of the port object and the device object to which it belongs. The device object and the rule constraint are processed to determine the attribute value of the device object. The attribute values ​​of the equipment object are attached to the corresponding engineering topology object, and the boundary range of the space occupant object is mapped to the rule constraints in the engineering topology baseline record to obtain the equipment attribute relationship and spatial constraint relationship; The period attribute relationships of each engineering topology object are determined according to the period attribute in the engineering topology benchmark record, and the electrical connection relationship, spatial constraint relationship, equipment attribute relationship and period attribute relationship are written into the same topology structure to generate a composite topology engineering map.

[0010] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps for forming a projectable topology engineering map are as follows: Track the connection status of port objects along the electrical connection relationships in the composite topology engineering map, and mark the engineering topology objects that belong to the inlet end, outlet end and adjacent objects that satisfy the closed connection relationship as connection closure objects, forming a connection closure verification record; The device attribute relationships corresponding to each connection closure object in the connection closure verification record are compared with the rule constraints and interval configuration sources under the same boundary, and the projection conditions are checked. Engineering topology objects with object identification, connection affiliation, attribute acceptance, and spatial constraint acceptance are written into the projectable mapping relationship to form a projectable topology engineering map.

[0011] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps for generating three-graph association records according to common source identifiers are as follows: Read the engineering topology objects that have been written with projectable mapping relationships in the projectable topology engineering map, and write the electrical connection relationships corresponding to the engineering topology objects into the logical projection sequence according to the same source identifier, and write the spatial constraint relationships corresponding to the engineering topology objects into the layout projection sequence to generate map projection task records; According to the map projection task record, wiring element projection and spatial boundary projection processing are performed on the logic projection sequence and the layout projection sequence respectively, converting electrical connection relationships into electrical logic objects and spatial constraint relationships into spatial layout objects, generating electrical logic map and spatial layout map; Engineering topology objects, electrical logic objects, and spatial layout objects with consistent source identifiers are defined as source objects. The correspondence between source objects and projectable topology engineering maps, electrical logic maps, and spatial layout maps is established, and a three-map association record is generated.

[0012] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps for generating topology change event records are as follows: Using the same-source objects in the three-map association records as the verification objects, the connection, boundary, and phase assignments of engineering topology objects, electrical logic objects, and spatial layout objects are aligned according to the same-source identifier to form a same-source verification benchmark record; Consistency judgment is performed on the same source verification benchmark records, and the differences are marked as inconsistencies between electrical connection relationship and connection attribution, spatial constraint relationship and boundary attribution, and period attribute relationship and period attribution. Asynchronous differences caused by changes in the position displayed on the map are excluded, and the same source difference judgment record is formed. Based on the difference type, source map, and affected object in the same source difference determination record, determine the synchronization direction and processing priority corresponding to the difference item, and generate a topology change event record.

[0013] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps for generating local influence domain verification records are as follows: Starting from the source identifier and difference type in the topology change event record, the corresponding source object is locked in the three-map association record, and the associated object is extended along the electrical connection relationship, spatial constraint relationship and phase attribute relationship in the composite topology engineering map. The connected affected object, the boundary affected object and the phase affected object are included in the same local project scope, and a local project scope record is generated. Perform topology constraint verification on the corresponding affected objects in the local project scope record, check the connection status, spatial boundary status and phase status between each affected object, identify the same source objects that meet the synchronization conditions and the same source objects that have layout conflicts, and generate local influence domain verification records.

[0014] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps for outputting the substation intelligent result set are as follows: Locate the source objects with layout conflicts from the local influence domain verification record, and solidify the electrical connection sequence, port correspondence and period attribute relationship of the source objects as topology preservation conditions to generate conflict preservation constraint records. Based on the conflict-preserving constraint record, the boundary attribution, location attribution and adjacent constraint relationship of the spatial layout objects are adjusted within the local engineering scope. The adjusted spatial layout relationship is then substituted back to the projectable topology engineering map, electrical logic map and spatial layout map for consistency confirmation, generating a topology-preserving correction record. Based on the topology-preserving correction record, the projectable topology engineering map, electrical logic map, and spatial layout map are updated synchronously to generate a synchronous update map. The synchronous update map is then confirmed for period continuity and version tracking is performed, and the substation intelligent achievement set is output.

[0015] As a preferred embodiment of the substation intelligent design system based on topology relationships described in this invention, the specific steps for confirming the period continuity and version tracking of the synchronously updated map are as follows: Based on the phase attribute relationships in the synchronously updated map, identify the current phase affiliation of the local project scope, filter phase comparison objects that have a succession relationship with the current phase affiliation, and verify the port succession, spatial boundary continuation and reserved area occupancy status to generate phase connection records; Compare the version differences between the projectable topology engineering diagram, electrical logic diagram and spatial layout diagram before and after the topology-preserving modification, and write the corresponding difference items according to object changes, relationship changes and period changes to generate version trace records; The synchronized updated map, period connection record, and version trace record will be collected according to the same source identifier, and the period connection record and version trace record will be associated with the corresponding map position to generate the substation intelligent result set.

[0016] The beneficial effects of this invention are as follows: By generating a composite topology engineering map, electrical connections, spatial constraints, equipment attributes, and phase attributes are uniformly written into the same source topology structure, realizing a stable association between engineering objects in the topology layer, electrical logic layer, and spatial layout layer, reducing the risk of incomplete synchronization of multiple types of results and inconsistent attribution relationships; through topology-preserving correction, the electrical connection sequence, port correspondence, and phase attribute relationship are solidified during the local layout conflict handling process, realizing the synergy between spatial layout adjustment and the preservation of key topology relationships, avoiding implicit changes in electrical logic and phase inheritance relationships caused by local corrections, and improving the consistency, traceability, and engineering feasibility of result updates. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of a substation intelligent design system based on topology.

[0019] Figure 2 A flowchart for generating composite topology engineering maps.

[0020] Figure 3 A flowchart for generating the association record of the three spectra.

[0021] Figure 4 A flowchart for generating a smart achievement set for substations. Detailed Implementation

[0022] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0023] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0024] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0025] Reference Figures 1-4 This is one embodiment of the present invention, which provides a substation intelligent design system based on topology relationships, including the following steps: The topology baseline module acquires basic data of the substation project and performs topology baseline processing to determine the project boundaries, rule constraints, phase attributes and bay configuration sources, and generates project topology baseline records.

[0026] The substation engineering basic data, including site range, construction scale, voltage level, and engineering rule sources, are subjected to boundary constraint coupling processing to determine the engineering boundary and corresponding rule constraints. The available range of the engineering boundary is then corrected according to the layout requirements and bay access requirements corresponding to the voltage level, and a boundary constraint benchmark record is generated.

[0027] It should be noted that when performing topology benchmarking processing on the basic data of substation projects, the site range, construction scale, voltage level, source of engineering rules, construction period information, wiring configuration requirements and equipment parameter data are collected through the engineering data entry interface and engineering data import interface.

[0028] The site scope is formed by land boundary data, control point data within the station, and non-layout area data. The land boundary data is obtained by parsing the imported site boundary coordinates and the overall plan map. The control point data within the station is obtained by entering engineering coordinate points. The non-layout area data is obtained by parsing the prohibited areas and occupied areas marked on the overall plan map. The construction scale is formed by capacity configuration data, outgoing line scale data, bay quantity data, and reserved scale data. The capacity configuration data, outgoing line scale data, and bay quantity data are obtained by aligning the fields of the engineering requirements and wiring configuration requirements. The reserved scale data is obtained by organizing the area information marked with reserved in the engineering requirements. The wiring configuration requirements are formed by the fields related to wiring configuration in the engineering data import interface. The construction period information is formed by the period field in the engineering data entry interface and the period range marking in the engineering data import interface. The equipment parameter data is formed by the equipment parameter records obtained from the engineering data import interface and establishes a corresponding relationship with the equipment category.

[0029] Voltage levels are formed by wiring configuration requirements and equipment parameter data. The voltage level field in the wiring configuration requirements is checked against the rated voltage field in the equipment parameter data. Voltage levels that match are written into the voltage level data, while those that do not match are written into the items to be reviewed and retained as basic review fields in the boundary constraint benchmark record. The basic review fields are associated with the corresponding wiring configuration requirements and equipment parameter data. Voltage levels that do not match do not participate in the boundary constraint coupling process. The source of engineering rules is formed by specification source identifiers, enterprise rule source identifiers, and equipment parameter source identifiers. Applicable relationships are established between each source identifier and voltage level, equipment category, and bay category to form callable rule sources.

[0030] When performing boundary constraint coupling processing, the land boundary data, station control point data, and non-layout range data are converted to the same engineering coordinate reference. The station site boundary is formed according to the line segment connection relationship of the land boundary, and the non-layout range is deducted from the station site boundary to obtain the basic boundary range that can participate in the boundary calculation. According to the capacity configuration data, outgoing line scale data, and bay quantity data in the construction scale, the engineering occupancy requirements are formed within the basic boundary range. The engineering occupancy requirements are linked with the voltage level data, and according to the bay type, bay quantity, and bay access direction in the wiring configuration requirements, as well as the equipment type and equipment configuration requirements in the equipment parameter data, the equipment layout requirements and bay access requirements under the corresponding voltage level are compiled. The bay quantity, equipment layout requirements, and bay access requirements are written into the corresponding basic boundary range to obtain the initial engineering boundary. The applicability relationship of the engineering rule sources is screened: the rule sources whose applicable voltage level, equipment type, and bay type are consistent with the initial engineering boundary are written into the candidate rule set. The spatial distance requirements, wiring access requirements, equipment layout requirements, and reserved occupancy requirements are extracted from the candidate rule set, and each rule requirement is linked to the corresponding initial engineering boundary to determine the engineering boundary and the corresponding rule constraints.

[0031] When modifying the available range of the project boundary, the layout requirements and bay access requirements corresponding to the voltage level are used as the basis for modification. Ranges within the project boundary that do not meet spatial distance requirements are marked as distance-restricted ranges; ranges that cannot form bay access paths are marked as access-restricted ranges; and ranges that do not meet equipment layout requirements are marked as layout-restricted ranges. The available range of the boundary is obtained after deducting the distance-restricted range, access-restricted range, and layout-restricted range from the project boundary. Ranges with reserved scale data participate in the reservation verification. If the reserved occupancy requirements are met and bay access requirements are maintained, the corresponding range is retained within the available range of the boundary. If the reserved occupancy requirements and bay access requirements are not met, the corresponding range is written into the restricted reserved range. The project boundary, rule constraints, available range of the boundary, distance-restricted range, access-restricted range, layout-restricted range, and restricted reserved range are written into the same boundary relationship to generate a boundary constraint benchmark record.

[0032] Based on the boundary constraint benchmark record, the construction period information and wiring configuration requirements in the substation project basic data are analyzed for period continuity. The period attributes are determined under the corresponding project boundary, and the sources of callable bay configurations, the releasable reserved range, and the restricted configuration range are determined based on the period attributes, generating the period bay continuity record.

[0033] It should be noted that when performing phase succession analysis, the original fields representing different construction phases in the construction phase information are merged to form a phase affiliation key; the original fields representing the project scope corresponding to each construction phase in the construction phase information are merged to form a phase range key; and the original fields representing the reserved occupancy status in the construction phase information are merged to form a reserved status key. Phase entries lacking either the phase affiliation key or the phase range key are not included in this succession analysis, and the missing items are written into the supplementary field of the phase interval succession record.

[0034] Overlay the scope corresponding to the period range key with the project boundary, and cross-check the overlay result with the boundary available scope and the restricted reserved scope to obtain the candidate acceptance scope. Write the restricted scope into the restricted configuration scope. Merge the original fields representing the wiring form, bay type, bay quantity, and bay access direction in the wiring configuration requirements to form a wiring configuration group. Compare the wiring configuration group with the candidate acceptance scope: if the candidate acceptance scope meets the rule constraints, bay quantity acceptance requirements, and bay access direction requirements, it is marked as the period available scope; if the candidate acceptance scope is restricted by the rule constraints, the boundary available scope, and the restricted reserved scope, it is written into the restricted configuration scope. Determine the period attributes under the project boundary based on the period belonging key, period available scope, restricted configuration scope, and reserved status key.

[0035] Based on the period attribute, configuration records that meet the constraints of wiring type, interval category, number of intervals, interval access direction, and rules are filtered from the interval configuration sources associated with the wiring configuration requirements to determine the callable interval configuration sources; the occupancy of the candidate acceptance range corresponding to the reserved status key is checked, and the range that is not occupied by the wiring configuration group accepted this time and maintains the continuity of interval access is marked as the releasable reserved range; the range that cannot accept the wiring configuration group and cannot be released is marked as the restricted configuration range; the period attribute, callable interval configuration source, releasable reserved range, restricted configuration range, and fields to be supplemented are written into the same acceptance relationship to generate the period interval acceptance record.

[0036] The topology benchmark is bound to the boundary constraint benchmark record and the period interval acceptance record. The engineering boundary, rule constraint, period attribute and interval configuration source are written into the benchmark relationship under the same boundary to generate the engineering topology benchmark record.

[0037] It should be noted that when binding the topology baseline of the boundary constraint baseline record and the period interval acceptance record, the engineering boundary in the boundary constraint baseline record is used as the belonging object. The period attribute in the period interval acceptance record is matched with the engineering boundary for range correspondence: if the range corresponding to the period attribute falls within the engineering boundary and does not fall within the restricted configuration range, the corresponding period attribute is written into the boundary attribution relationship of the engineering boundary; if the range corresponding to the period attribute does not fall within the engineering boundary or overlaps with the restricted configuration range, it is not written into the valid boundary attribution relationship, and the reason for the range inconsistency is recorded.

[0038] After the boundary attribution relationship is confirmed, the engineering boundary and rule constraints in the boundary constraint benchmark record are merged with the period attributes and callable interval configuration sources in the period interval inheritance record for the same boundary. When there are multiple period attributes under the same engineering boundary, the corresponding boundary attribution relationship is written according to the period attribution key formed by the construction period information to avoid the interval configuration sources of different periods from overlapping each other. The engineering boundary, rule constraints, period attributes, interval configuration sources, reasons for inconsistency in scope, basic review fields and boundary attribution relationship are written into the same topology benchmark to generate an engineering topology benchmark record.

[0039] The topology fusion module performs anchoring instantiation processing based on the engineering topology baseline record, maps electrical bay objects, equipment objects, port objects, and space occupant objects to engineering topology objects with the same source identifier, and performs topology fusion on the electrical connection relationship, spatial constraint relationship, equipment attribute relationship and phase attribute relationship between engineering topology objects to generate a composite topology engineering map.

[0040] Based on the phase attributes and interval configuration sources under the same boundary in the engineering topology baseline record, the phase availability screening and boundary adaptation correction are performed on the interval configuration sources to determine the target electrical interval objects and their assembleable equipment objects, port objects and space occupancy objects, and generate interval assembly candidate records.

[0041] It should be noted that, under the same boundary attribution relationship in the engineering topology baseline record, the period attribute, engineering boundary, rule constraint and interval configuration source are retrieved; the callable configuration record in the interval configuration source is configured and decomposed, the corresponding interval category is written into the electrical interval candidate, the equipment configuration associated with the interval category is written into the equipment candidate, the access location associated with the equipment configuration is written into the port candidate, and the layout occupancy range associated with the interval category and equipment configuration is written into the space occupancy candidate.

[0042] The electrical bay candidates are screened for availability by period. The applicable period corresponding to the electrical bay candidate is compared with the period attribute in the engineering topology baseline record. Electrical bay candidates whose applicable period and period attribute are consistent and do not fall within the restricted configuration range are retained. Electrical bay candidates that do not meet any of the conditions of period attribute, restricted configuration range and rule constraint are written into the candidate exclusion items of the bay assembly candidate record.

[0043] Boundary adaptation correction is performed on the retained electrical bay candidates, and the space occupancy candidates are superimposed and verified with the engineering boundary, the boundary availability range, and rule constraints. If any of the following conditions are met: the space occupancy candidate exceeds the engineering boundary, falls into a restricted configuration range, or does not meet the rule constraints, the assemblable range of the space occupancy candidate is reduced according to the engineering boundary and rule constraints, and the access positions of the equipment candidate and the port candidate are simultaneously verified to ensure that they still correspond. The electrical bay candidates that pass the phase availability screening and boundary adaptation correction are determined as target electrical bay objects. The equipment candidates, port candidates, and space occupancy candidates that maintain configuration association and access correspondence with the target electrical bay objects are determined as assemblable equipment objects, port objects, and space occupancy objects, respectively, and bay assembly candidate records are generated.

[0044] It should also be noted that the availability screening and boundary adaptation correction are not just for result judgment, but are performed item by item according to the candidate assembly relationship. The candidate assembly relationship records the applicable period, boundary affiliation and access direction of the electrical bay candidate, the equipment affiliation of the equipment candidate, the port affiliation of the port candidate, and the occupied boundary of the space occupancy candidate.

[0045] When comparing applicable periods, the period attribute in the engineering topology baseline record is used as the baseline field. Candidate assembly relationships that are consistent with the applicable period and the period attribute and whose space occupancy candidates do not fall into the restricted configuration range are used as available items for the period. If any of the following conditions are met, such as inconsistent applicable periods, falling into the restricted configuration range, or missing boundary attribution, candidate exclusion items are formed, and the reason for exclusion is recorded.

[0046] When performing boundary adaptation correction on space occupancy candidates, the assemblable boundary is determined based on the project boundary, the available boundary range, and the restricted configuration range. The assemblable boundary is the spatial range within the available boundary range that still belongs to the same project boundary after deducting the restricted configuration range. If the occupied boundary of a space occupancy candidate falls entirely within the assemblable boundary, the occupied boundary is retained. If part of the occupied boundary extends beyond the assemblable boundary, the excess part is trimmed into the assemblable boundary, and it is verified whether the trimmed occupied boundary can still support the corresponding device candidate and port candidate. If any of the following conditions are met: the occupied boundary is entirely outside the assemblable boundary, the trimmed boundary cannot support the corresponding device candidate, or the port candidate cannot form a connection relationship with adjacent objects according to the access direction, a candidate exclusion item is formed.

[0047] After boundary adaptation correction, verify the correspondence between the electrical bay candidate to which the equipment candidate belongs, the equipment candidate to which the port candidate belongs, the access direction of the port candidate, and the boundary affiliation of the space occupant candidate. Candidate assembly relationships with consistent correspondence are used to determine the target electrical bay object and its assembleable equipment objects, port objects, and space occupant objects.

[0048] Based on the candidate records for bay assembly and the corresponding rule constraints, the target electrical bay object is hierarchically assembled with the assembleable equipment objects, port objects, and space occupant objects, and a common-source identifier is configured to generate an anchored bay topology record.

[0049] It should be noted that when performing hierarchical assembly based on the bay assembly candidate record, the target electrical bay object is used as the assembly master node. Assembleable equipment objects are attached to the target electrical bay object according to the configuration association in the bay assembly candidate record; assembleable port objects are attached to the corresponding equipment objects according to their access location and the equipment objects they belong to; and assembleable space occupant objects are attached to the target electrical bay object and the corresponding equipment objects according to their layout occupancy range and boundary attribution, thus forming a hierarchical assembly relationship between bays, equipment, ports, and space occupants.

[0050] When verifying the rule constraints of hierarchical assembly relationships, the target electrical bay object is compared with the bay category requirements in the rule constraints, the equipment object is compared with the equipment configuration requirements in the rule constraints, the port object is compared with the access direction and port quantity requirements in the rule constraints, and the space occupancy object is compared with the boundary available range and spatial distance requirements in the rule constraints. Objects that meet the corresponding rule constraints are retained in the hierarchical assembly relationship; objects that do not meet the corresponding rule constraints are removed from the hierarchical assembly relationship, and the reason for removal is written into the assembly exclusion field.

[0051] After the hierarchical assembly relationship is verified by rule constraints, a common source identifier is generated according to the boundary attribution relationship, period attribute and interval configuration source in the engineering topology benchmark record; equipment objects, port objects and space occupant objects under the same target electrical interval object inherit the common source identifier of the target electrical interval object, and retain their respective object attribution fields under the common source identifier.

[0052] Write the target electrical bay object, assemblable device object, port object, space occupant object, hierarchical assembly relationship, common source identifier and assembly exclusion field into the same record to generate an anchored bay topology record.

[0053] Using the same source identifier in the anchored interval topology record as an index, the port connection relationship between electrical interval objects is identified, and the electrical connection relationship is determined by combining the access direction of the port object and the device object to which it belongs. The device object and the rule constraint are processed to determine the attribute value of the device object.

[0054] It should be noted that when determining electrical connection relationships, the same-source identifier in the anchored bay topology record is used as an index to group electrical bay objects belonging to the same boundary and the same period attribute into the same connection judgment range. The access position, access direction, and associated equipment object of the port object under each electrical bay object are read. According to the wiring access order in the bay configuration source, the access position of the port object is checked for continuity, and adjacent access positions are confirmed in combination with the wiring access requirements in the rule constraints. Candidate connection relationships are established for port objects with corresponding adjacent access positions, mutually continuous access directions, and associated equipment objects that meet the same bay configuration source. When the port object corresponding to the candidate connection relationship is not marked by the assembly exclusion field and does not violate the wiring access requirements in the rule constraints, the candidate connection relationship is determined as a port connection relationship. The connection start point, connection end point, port affiliation, and equipment affiliation between electrical bay objects are recorded according to the port connection relationship to form an electrical connection relationship.

[0055] When processing equipment attribute acceptance, the equipment objects in the anchored interval topology record are matched with the equipment configuration requirements in the rule constraints. The electrical interval object to which the equipment object belongs, the period attribute, and the interval configuration source are used as acceptance conditions. When the equipment object meets the corresponding acceptance conditions, the configuration value corresponding to the equipment object is read from the interval configuration source and checked against the equipment configuration requirements in the rule constraints. If the configuration value matches, it is written into the attribute value of the equipment object. If the equipment object does not meet the acceptance conditions or the configuration value is inconsistent with the rule constraints, the equipment object is written into the attribute supplement field.

[0056] The attribute values ​​of the device object are attached to the corresponding engineering topology object, and the boundary range of the space occupant object is mapped to the rule constraints in the engineering topology baseline record to obtain the device attribute relationship and spatial constraint relationship.

[0057] It should be noted that when forming equipment attribute relationships, the target electrical bay object, equipment object, port object, and space occupant object with configured source identifiers in the anchored bay topology record are used as the object source of the engineering topology object. The engineering topology object corresponding to the equipment object is found according to the source identifier and object affiliation field. The equipment object attribute values ​​obtained from the previous attribute inheritance process are written into the attribute inheritance field of the corresponding engineering topology object. Attribute values ​​with the same source identifier and the same object affiliation form a valid attachment relationship. Equipment objects with inconsistent source identifiers, inconsistent object affiliations, or those in the attribute pending supplement field do not participate in this attachment and are written into the attribute attachment exception field. Based on the valid attachment relationship, the equipment object, attribute value, source identifier, and object affiliation field are written into the same relationship item to form the equipment attribute relationship.

[0058] When forming spatial constraint relationships, the boundary range corresponding to the spatial occupant object is obtained according to the same source identifier, and the rule constraints under the same boundary are obtained from the engineering topology benchmark record. The boundary range of the spatial occupant object is checked against the boundary availability range, spatial distance requirements and equipment layout requirements in the rule constraints. The boundary range that meets the boundary availability range, spatial distance requirements and equipment layout requirements is written into the spatial availability relationship item, and the boundary range that does not meet the corresponding rule constraints is written into the spatial restriction relationship item, and the corresponding restriction reasons are recorded. The spatial constraint relationship is formed according to the spatial availability relationship item, the spatial restriction relationship item, the same source identifier and the boundary attribution field.

[0059] The period attribute relationships of each engineering topology object are determined according to the period attribute in the engineering topology benchmark record, and the electrical connection relationship, spatial constraint relationship, equipment attribute relationship and period attribute relationship are written into the same topology structure to generate a composite topology engineering map.

[0060] It should be noted that when calibrating the period attribute relationship, the source identifier and boundary attribution field of the engineering topology object are used as indexes to search for the period attribute under the same boundary attribution in the engineering topology baseline record, and the period attribute is correspondingly linked to the engineering topology object; when the engineering topology object falls within the period available range and corresponds to an available interval configuration source, the engineering topology object is written into the corresponding period attribute relationship; if the engineering topology object falls within any of the following situations: falling within a restricted configuration range or not corresponding to an available interval configuration source, the engineering topology object is written into the period restricted field, and the reason for the restriction is recorded.

[0061] When forming a composite topology engineering map, the same-source identifier is used as the merging index. Electrical connection relationships, spatial constraint relationships, equipment attribute relationships, and phase attribute relationships are written into the same topology structure. During the writing process, port attribution is checked for electrical connection relationships under the same engineering topology object, boundary attribution is checked for spatial constraint relationships, object attribution is checked for equipment attribute relationships, and phase attribution is checked for phase attribute relationships. Relationship items with consistent attribution are retained in the same topology structure, while relationship items with inconsistent attribution are written into the relationship exception field and do not participate in this map fusion.

[0062] Write the merged engineering topology objects, source identifiers, electrical connection relationships, spatial constraint relationships, equipment attribute relationships, phase attribute relationships, and relationship anomaly fields into the graph record to generate a composite topology engineering graph; attribute attachment anomaly fields are incorporated into the relationship anomaly fields when forming the composite topology engineering graph.

[0063] It should also be noted that the same topology structure is not limited to a specific database type, but rather is a node relationship structure established with a common source identifier as a unified index. It includes object node records, relationship attachment records, and attribute field records. The object node records are used to write the engineering topology object, object type, common source identifier, boundary affiliation, and phase affiliation. The relationship attachment records are used to write the electrical connection relationship, spatial constraint relationship, and phase attribute relationship between engineering topology objects. The attribute field records are used to write the attribute values, port affiliation, occupied boundary, available space relationship items, and space-restricted relationship items of the device object.

[0064] When writing electrical connection relationships, the corresponding engineering topology object is found using the same source identifier, and the start point, end point, port affiliation, and equipment affiliation are written into the relationship attachment record. When writing spatial constraint relationships, the occupied boundary, boundary affiliation, adjacent constraint relationship, available space relationship item, and restricted space relationship item of the space occupant object are written into the relationship attachment record under the same source identifier. When writing equipment attribute relationships, the attribute values ​​of the equipment object, equipment affiliation, and port affiliation are written into the attribute field record. When writing period attribute relationships, the period attribute, interval configuration source, reserved range, and restricted configuration range are written into the attribute field record under the corresponding same source identifier.

[0065] Object node records, relationship attachment records, and attribute field records with the same source identifier establish mutual reference relationships; if the source identifier does not exist, a new object node record is created first, and then the corresponding relationship and attribute are written; if the source identifier already exists, the newly added relationship and attribute are attached to the existing object node record, and the source relationship marker is retained.

[0066] The projection association module verifies the connection closure status, equipment attribute acceptance status, and map projection conditions of each engineering topology object in the composite topology engineering map, forming a projectable topology engineering map. Through logical projection and layout projection, the projectable topology engineering map is converted into an electrical logic map and a spatial layout map, respectively, and a three-map association record is generated according to the same source identifier.

[0067] The connection status of port objects is traced along the electrical connection relationships in the composite topology engineering map. The engineering topology objects that belong to the entrance end, exit end and adjacent objects and satisfy the closed connection relationship are marked as connection closure objects, forming a connection closure verification record.

[0068] It should be noted that when performing connection closure verification, the same-source identifier of the engineering topology object is used as the tracking index. The start point, end point, port affiliation, and device affiliation of the corresponding port object are retrieved from the electrical connection relationship. The port object corresponding to the start point is marked as the entry end, and the port object corresponding to the end point is marked as the exit end. The affiliation of the adjacent objects directly connected to the current engineering topology object is determined based on the port affiliation and device affiliation. Electrical connection relationships in the relationship anomaly field do not participate in this connection closure verification, and the corresponding same-source identifier is written into the connection anomaly item.

[0069] When determining the closure continuity of an engineering topology object, it is checked whether the entry end has a continuity relationship from the previous engineering topology object, whether the exit end has a continuity relationship pointing to the next engineering topology object, and whether the entry end, exit end, and adjacent objects belong to the same boundary and the same period attribute. When the entry end, exit end, and adjacent objects all satisfy the closure continuity relationship, the corresponding engineering topology object is marked as a closed connection object. Engineering topology objects with missing entry ends, missing exit ends, inconsistent adjacent object affiliations, or inconsistent boundary affiliations are written into the connection unclosed item, and the reason for the unclosed status is recorded. The closed connection object, the connection unclosed item, the connection anomaly item, and the reason for the unclosed status are written into the same verification relationship to form a connection closure verification record.

[0070] The device attribute relationships corresponding to each connection closure object in the connection closure verification record are compared with the rule constraints and interval configuration sources under the same boundary, and the projection conditions are checked. Engineering topology objects with object identification, connection affiliation, attribute acceptance, and spatial constraint acceptance are written into the projectable mapping relationship to form a projectable topology engineering map.

[0071] It should be noted that connection closure objects are selected from the connection closure verification record, and the corresponding equipment attribute relationships, spatial constraint relationships, and electrical connection relationships are retrieved from the composite topology engineering map according to the same source identifier. The equipment attribute relationships corresponding to the connection closure objects are compared with the rule constraints under the same boundary. If the attribute values ​​meet the equipment configuration requirements and the electrical bay object and bay configuration source are consistent, the corresponding engineering topology object is marked as an attribute acceptance valid object. If the attribute values ​​are missing, the attribute values ​​are inconsistent with the rule constraints, or the bay configuration source is inconsistent, the corresponding engineering topology object is written into the attribute acceptance anomaly item.

[0072] When verifying the projection conditions of valid attribute-accepted objects, check whether the engineering topology objects have object identifiers formed by the same source identifier, check whether the electrical connection relationships have connection attribution confirmed by connection closure verification records, check whether the equipment attribute relationships have completed attribute acceptance, and check whether the spatial constraint relationships have spatial constraint acceptance under the corresponding boundary attribution. Engineering topology objects that have object identifiers, connection attribution, attribute acceptance, and spatial constraint acceptance and whose attribution is consistent are written into the projectable mapping relationship. Engineering topology objects with attribute acceptance anomalies, unclosed connection items, spatially restricted relationship items, basic verification fields, and inconsistent attribution are not written into the projectable mapping relationship, and the corresponding anomalies, items to be verified, and reasons for inconsistent attribution are recorded as exclusion reasons.

[0073] The projectable mapping relationship, corresponding source identifier, connection affiliation, attribute acceptance status, spatial constraint acceptance status, and exclusion reason are written into the same map record to form a projectable topology engineering map.

[0074] Read the engineering topology objects that have been written with projectable mapping relationships in the projectable topology engineering map, write the electrical connection relationships corresponding to the engineering topology objects into the logical projection sequence according to the same source identifier, write the spatial constraint relationships corresponding to the engineering topology objects into the layout projection sequence, and generate the map projection task record.

[0075] It should be noted that in the projectable topology engineering map, the engineering topology objects are located according to the projectable mapping relationship, and the electrical connection relationship and spatial constraint relationship corresponding to the engineering topology object are checked with the same source identifier. If the connection attribution in the electrical connection relationship is consistent with the object attribution of the engineering topology object, and no exclusion reason is written, the connection start point, connection end point, port attribution, and equipment attribution in the electrical connection relationship are written into the logical projection sequence. If the boundary attribution in the spatial constraint relationship is consistent with the boundary attribution of the engineering topology object, and the spatial constraint acceptance status is valid, the boundary range, available spatial relationship item, and restricted spatial relationship item in the spatial constraint relationship are written into the layout projection sequence.

[0076] The logical projection sequence maintains the electrical connection order according to the same source identifier and port connection relationship, while the layout projection sequence maintains the spatial constraint correspondence according to the same source identifier and boundary attribution. If there are engineering topology objects with missing same source identifiers, inconsistent connection attribution, inconsistent boundary attribution, or uncleared exclusion reasons, they are not written into the logical projection sequence and the layout projection sequence. The corresponding object attribution and the reason for not writing are written into the projection postponement field. The same source identifier, engineering topology object, logical projection sequence, layout projection sequence, and projection postponement field are written into the same task relationship to generate a map projection task record.

[0077] According to the map projection task record, wiring element projection and spatial boundary projection processing are performed on the logic projection sequence and the layout projection sequence respectively, converting electrical connection relationships into electrical logic objects and spatial constraint relationships into spatial layout objects, generating electrical logic map and spatial layout map.

[0078] It should be noted that during projection processing, the start point, end point, port affiliation, and device affiliation in the logical projection sequence are used as the basis for projecting wiring elements. Using the same-source identifier as the merging index, the start point is converted into the connection start point of the electrical logic object, the end point is converted into the connection end point of the electrical logic object, and the port affiliation and device affiliation are written into the connection attributes of the electrical logic object. Logical projection sequences with complete and consistent start and end points, port affiliation, and device affiliation are written into the electrical logic diagram. Logical projection sequences with projection delay fields, missing port affiliations, or inconsistent device affiliations do not participate in this wiring element projection, and the reason for not projecting is recorded.

[0079] The boundary range, available spatial relation items, and restricted spatial relation items in the layout projection sequence are used as the basis for spatial boundary projection. Using the same source identifier as the merging index, the boundary range is transformed into the occupied boundary of the spatial layout object. The available spatial relation items are written into the deployable attribute of the spatial layout object, and the restricted spatial relation items are written into the restricted attribute of the spatial layout object. The layout projection sequence with consistent boundary range and boundary attribution and valid spatial constraint acceptance status is written into the spatial layout map. The layout projection sequence with inconsistent boundary attribution, invalid spatial constraint acceptance status, and projection postponement fields does not participate in this spatial boundary projection, and the reason for not projecting is recorded. The electrical logic object, spatial layout object, same source identifier, and reason for not projecting are written into the corresponding map record to generate the electrical logic map and spatial layout map. At the same time, the element display coordinates, annotation positions, and map avoidance positions of the electrical logic object and spatial layout object in the drawing are written into the object display field.

[0080] It should also be noted that the element display coordinates, label positions, and drawing avoidance positions in the object display field are not arbitrarily written, but are determined based on the attribution relationships in the logical projection sequence and the layout projection sequence: When generating element display coordinates for electrical logic objects, the connection start point, connection end point, port attribution, and equipment attribution under the same source identifier are used as the positioning basis; first, the arrangement order of electrical logic objects is determined according to the connection direction from the connection start point to the connection end point, then the connection end position is determined according to the port attribution, and electrical logic objects with the same equipment attribution are written into the same element arrangement group; if there are element overlaps, connection path intersections, and label occlusions within the element arrangement group, the element display coordinates, label positions, and drawing avoidance positions are adjusted without changing the connection start point, connection end point, port attribution, and equipment attribution; if the connection relationship still cannot be kept clear after adjustment, the corresponding logical projection sequence is written into the projection delay field, and the reason for not projecting is recorded.

[0081] When generating element display coordinates for spatial arrangement objects, the positioning is based on the boundary range, boundary attribution, available spatial relationship items, and restricted spatial relationship items in the arrangement projection sequence. Within the range where boundary attribution is consistent, the arrangeable range is determined. The arrangeable range is the range within the boundary range that still satisfies the available spatial relationship items after deducting the restricted spatial relationship items. If the occupied boundary of a spatial arrangement object falls entirely within the arrangeable range, the corresponding element display coordinates are retained. If the occupied boundary portion exceeds the arrangeable range, the display coordinates corresponding to the excess portion are adjusted to the arrangeable range, and it is verified whether the adjusted occupied boundary still satisfies the spatial constraint acceptance state. If any of the following conditions are met: inconsistent boundary attribution, the adjusted occupied boundary still falling within the restricted spatial relationship items, or overlap with other spatial arrangement objects after adjustment, the corresponding arrangement projection sequence is written to the projection delay field, and the reason for not projecting is recorded.

[0082] Engineering topology objects, electrical logic objects, and spatial layout objects with consistent source identifiers are defined as source objects. The correspondence between source objects and projectable topology engineering maps, electrical logic maps, and spatial layout maps is established, and a three-map association record is generated.

[0083] It should be noted that, in the projectable topology engineering map, engineering topology objects with projectable mapping relationships already written are retrieved; in the electrical logic map, electrical logic objects transformed from logical projection sequences are retrieved; and in the spatial layout map, spatial layout objects transformed from layout projection sequences are retrieved. Using the same-source identifier as the merging index, engineering topology objects, electrical logic objects, and spatial layout objects with the same source identifier are grouped into the same association group. If an association group contains engineering topology objects, electrical logic objects, and spatial layout objects simultaneously, and no reason for non-projection is recorded, the association group is marked as a same-source object. If any object is missing from the association group, or if there is a reason for non-projection, the association group is written to the association to be supplemented field, and the type of missing object and the reason to be supplemented are recorded.

[0084] When establishing correspondences, the engineering topology object among the source objects is used as the base object. The connection start point, connection end point, port affiliation, and equipment affiliation of the electrical logic object are written into the logical association item of the base object. The occupied boundary, deployable attributes, and restricted attributes of the spatial layout object are written into the layout association item of the base object. Both the logical association item and the layout association item retain the same source identifier and maintain consistency in object affiliation, connection affiliation, and boundary affiliation. The source identifier, engineering topology object, electrical logic object, spatial layout object, logical association item, layout association item, fields to be supplemented, and reasons for supplementation are written into the same association record to generate a three-graph association record.

[0085] The impact verification module performs consistency verification on the same-source objects in the three-map association records, generates topology change event records, and determines the local engineering scope with the same-source identifier in the topology change event records as the center. It then performs topology constraint verification on the local engineering scope and generates local impact domain verification records.

[0086] Using the same-source objects in the three-map association records as the verification objects, the connection attribution, boundary attribution, and phase attribution of engineering topology objects, electrical logic objects, and spatial layout objects are aligned according to the same-source identifier to form a same-source verification benchmark record.

[0087] It should be noted that, in the three-map association record, the association group that has been marked as the same source object is selected, and the same source identifier is used as the verification index. The engineering topology object, electrical logic object and spatial layout object in the association group are loaded into the same verification row; the object ownership, connection ownership, boundary ownership and period attributes of the engineering topology object are extracted; the connection start point, connection end point, port ownership and equipment ownership of the electrical logic object are extracted, and the connection ownership is sorted according to the port ownership and equipment ownership; the occupied boundary, deployable attribute and restricted attribute of the spatial layout object are extracted, and the boundary ownership is sorted according to the boundary ownership corresponding to the occupied boundary; when the electrical logic object and the spatial layout object do not carry the period ownership separately, the period attribute corresponding to the engineering topology object is inherited according to the same source identifier; objects whose same source identifier inheritance fails are written into the period to be supplemented field.

[0088] When aligning verification fields, the connection attribution of engineering topology objects and the connection attribution of electrical logic objects are written into the same connection verification field; the boundary attribution of engineering topology objects and the boundary attribution of spatial layout objects are written into the same boundary verification field; and the period attribute of engineering topology objects, the period attribution inherited by electrical logic objects, and the period attribution inherited by spatial layout objects are written into the same period verification field. The connection verification field, boundary verification field, and period verification field all retain the same source identifier, object attribution, and source map marker. Same source objects with associated fields to be supplemented, reasons for supplementation, and period fields to be supplemented do not enter the consistency judgment and are written into the supplementary verification items. The same source identifier, engineering topology objects, electrical logic objects, spatial layout objects, connection verification fields, boundary verification fields, period verification fields, and supplementary verification items are written into the same record to form a same source verification baseline record.

[0089] Consistency judgment is performed on the same source verification benchmark records, and discrepancies are identified in electrical connection relationships and connection attribution, spatial constraint relationships and boundary attribution, and period attribute relationships and period attribution. Asynchronous differences caused by changes in the position displayed on the map are excluded, and a same source difference judgment record is formed.

[0090] It should be noted that when performing consistency checks on the same-source verification benchmark records, the same-source identifier is used as the index to read the connection verification field, boundary verification field, and period verification field respectively. In the connection verification field, if the electrical connection relationship corresponding to the engineering topology object is consistent with the connection attribution organized by the electrical logic object, the connection verification is deemed to have passed. If the start point, end point, port attribution, and equipment attribution in the electrical connection relationship are inconsistent with the connection attribution, the corresponding same-source identifier is marked as a connection difference item. In the boundary verification field, if the spatial constraint relationship corresponding to the engineering topology object is consistent with the boundary attribution organized by the spatial layout object, the boundary verification is deemed to have passed. If the boundary range, available space relationship item, and restricted space relationship item in the spatial constraint relationship are inconsistent with the boundary attribution, the corresponding same-source identifier is marked as a boundary difference item. In the period verification field, if the period attribute relationship corresponding to the engineering topology object is consistent with the period attribution inherited by the electrical logic object and the spatial layout object, the period verification is deemed to have passed. If the period attribute relationship is inconsistent with the period attribution, the corresponding same-source identifier is marked as a period difference item.

[0091] When excluding asynchronous differences, only the display positions of objects from the same source whose electrical connection relationships, spatial constraint relationships, and period attribute relationships have not changed are checked. The display positions are derived from the object display fields formed when the electrical logic diagram and spatial layout diagram are projected. These object display fields only record the display coordinates, label positions, and drawing avoidance positions of the elements, and do not change the start point, end point, port affiliation, equipment affiliation, boundary range, or period affiliation.

[0092] If the only change in the object display field of the same source object is that the connection review field, boundary review field, and period review field remain consistent, the corresponding change will be marked as an asynchronous difference and excluded. If the change in the object display field is accompanied by at least one of the connection difference, boundary difference, and period difference, the corresponding difference will be retained and will not be excluded as an asynchronous difference. The connection difference, boundary difference, period difference, asynchronous difference, source map marker, and difference reason will be written into the same judgment relationship to form a same source difference judgment record.

[0093] Based on the difference type, source map, and affected object in the same source difference determination record, determine the synchronization direction and processing priority corresponding to the difference item, and generate a topology change event record.

[0094] It should be noted that, using the same source identifier as the summary index, connection difference items, boundary difference items, and period difference items under the same affected object are merged separately; records that have been marked as asynchronous differences are not included in the topology change event record.

[0095] Read the difference type, source map, and affected object of the merged difference items. When the source map is marked as a projectable topology engineering map, write the synchronization direction as the projectable topology engineering map pointing to the electrical logic map and the spatial layout map; when the source map is marked as an electrical logic map, write the synchronization direction as the electrical logic map pointing to the projectable topology engineering map, and then from the projectable topology engineering map to the spatial layout map; when the source map is marked as a spatial layout map, write the synchronization direction as the spatial layout map pointing to the projectable topology engineering map, and then from the projectable topology engineering map to the electrical logic map.

[0096] When determining processing priorities, period difference items are written before connection difference items, and connection difference items are written before boundary difference items. When the same difference type involves multiple affected objects, connection difference items are sorted according to the start point to the end point of the electrical connection relationship, boundary difference items are sorted according to the adjacent order of the boundary of the spatial layout objects, and period difference items are sorted according to the belonging relationship of the period attribute in the engineering topology benchmark record.

[0097] When there are differences with the same source identifier and the same synchronization direction, the differences are merged into one topology change event; when there are differences with the same source identifier but different synchronization directions, they are split into multiple topology change events according to processing priority; the source identifier, difference type, source map, affected object, synchronization direction, processing priority and difference reason are written into the same event record to generate a topology change event record.

[0098] Starting from the source identifier and difference type in the topology change event record, the corresponding source object is locked in the three-map association record, and the associated objects are extended along the electrical connection relationship, spatial constraint relationship and phase attribute relationship in the composite topology engineering map. The connected affected objects, boundary affected objects and phase affected objects are included in the same local project scope, and a local project scope record is generated.

[0099] It should be noted that the source identifier and difference type in the topology change event record are used as the starting point for positioning. The source objects with the same source identifier are searched in the three-map association record. The engineering topology objects, electrical logic objects and spatial layout objects in the source objects are written into the local range seed objects.

[0100] If the difference type in the topology change event record is a connection difference item, then starting from the engineering topology object corresponding to the local range seed object, search for engineering topology objects with a connection start point, connection end point, port affiliation, and equipment affiliation in the electrical connection relationship of the composite topology engineering map, and mark the found engineering topology objects as the objects affected by the connection.

[0101] If the difference type is a boundary difference item, then in the spatial constraint relationship of the composite topology engineering graph, search for engineering topology objects that have the same boundary affiliation, spatial availability relationship item, and spatial restriction relationship item as the local range seed object, and mark the found engineering topology objects as boundary affected objects.

[0102] If the difference type is a period difference item, then in the period attribute relationship of the composite topology engineering map, look for the interval configuration source that has the same period attribute and can be called as the local range seed object, and be able to mark the found engineering topology object as the period affected object by checking the reserved range occupation through the engineering topology object.

[0103] When merging objects affected by connection, boundary, and period, duplicates are removed using the same-source identifier and object attribution field. Engineering topology objects that exist simultaneously in the three-map association record and the composite topology engineering map are retained. Objects in the association pending supplement field, relationship abnormal field, and projection postponement field are not written to the local engineering scope, and the reason for exclusion is written to the local scope exclusion field.

[0104] When there is overlap between connected affected objects, boundary affected objects, and period affected objects, the primary impact is determined according to the order of period affected objects, connected affected objects, and boundary affected objects, and the remaining impact types are retained as additional impact markers; the local scope seed object, connected affected objects, boundary affected objects, period affected objects, primary impact attribution, additional impact markers, and local scope exclusion fields are written into the same scope relation to generate a local project scope record.

[0105] Perform topology constraint verification on the corresponding affected objects in the local project scope record, check the connection status, spatial boundary status and phase status between each affected object, identify the same source objects that meet the synchronization conditions and the same source objects that have layout conflicts, and generate local influence domain verification records.

[0106] It should be noted that when verifying the connection acceptance status, the electrical connection relationship corresponding to the affected object is checked against the logical association item in the three-map association record: if the connection start point, connection end point, port affiliation, and device affiliation in the electrical connection relationship can all be found to have the same source correspondence in the logical association item, and the connection direction is consistent with the synchronization direction in the topology change event record, it is marked as connection acceptance passed; if there are missing ports, inconsistent device affiliation, or inconsistent connection direction with the synchronization direction, it is marked as connection acceptance abnormal.

[0107] When verifying the state of the spatial boundary, the spatial constraint relationship corresponding to the object affected by the boundary is checked against the arrangement association item in the three-map association record: if the occupied boundary of the spatial occupant falls into the available spatial relationship item, does not fall into the restricted spatial relationship item, and meets the rule constraints under the same boundary, it is marked as the spatial boundary has passed; if the occupied boundary exceeds the available boundary range, falls into the restricted spatial relationship item, or overlaps with the adjacent spatial arrangement object, it is marked as an arrangement conflict.

[0108] When verifying the acceptance status of a phase, the phase attribute relationship of the affected objects is compared with the phase attributes, callable interval configuration sources, and restricted configuration range in the engineering topology baseline record: if the phase attributes are consistent, the interval configuration source is callable and does not fall within the restricted configuration range, the phase acceptance is marked as successful; if the phase attributes are inconsistent, the interval configuration source is not callable and falls within the restricted configuration range, the phase acceptance is marked as abnormal.

[0109] Same-source objects that pass the connection acceptance state, spatial boundary state, and period acceptance state are marked as same-source objects that meet the synchronization conditions; same-source objects that pass the connection acceptance state and period acceptance state but are marked as having a layout conflict in the spatial boundary state are marked as same-source objects with layout conflicts; same-source objects with connection acceptance anomalies and period acceptance anomalies do not enter the topology-preserving correction and are written into the synchronization-restricted field; same-source objects that meet the synchronization conditions, same-source objects with layout conflicts, synchronization-restricted fields, connection acceptance states, spatial boundary states, period acceptance states, and corresponding verification reasons are written into the same verification relationship to generate a local influence domain verification record; objects in the local range exclusion field do not enter the topology constraint verification, and the exclusion reasons are continued to be written into the local influence domain verification record.

[0110] The maintenance correction module performs topology-preserving correction on local engineering areas with layout conflicts based on the local influence domain verification records. It adjusts the spatial layout relationship while keeping the electrical connection sequence, port correspondence, and period attribute relationship unchanged, and outputs the substation intelligent result set.

[0111] Locate the co-originating objects with layout conflicts from the local influence domain verification records, and solidify the electrical connection sequence, port correspondence, and period attribute relationship of the co-originating objects as topology preservation conditions to generate conflict preservation constraint records.

[0112] It should be noted that, from the local influence domain verification record, objects with layout conflicts are read from the same source, and the corresponding engineering topology objects, electrical logic objects, and spatial layout objects are retrieved from the three-map association record according to the same source identifier; for objects with layout conflicts, the start point, end point, adjacent object affiliation, and equipment affiliation are read along the electrical connection relationship in the composite topology engineering map, and the electrical connection sequence is organized according to the connection direction from the start point to the end point; the port affiliation and equipment affiliation are read from the logical association item in the three-map association record, and the port affiliation is bound to the corresponding equipment affiliation to form a port correspondence relationship; the phase attribute, callable interval configuration source, and restricted configuration range corresponding to the same source object are read from the phase attribute relationship in the composite topology engineering map to form a phase attribute relationship.

[0113] When writing hold conditions for electrical connection sequence, port correspondence, and period attribute relationships, the electrical connection sequence is written to the connection hold field, the port correspondence is written to the port hold field, and the period attribute relationship is written to the period hold field. For source objects with connection acceptance anomalies, period acceptance anomalies, or synchronization restriction fields, hold conditions are not written, and the exclusion reasons are written to the conflict hold constraint record. Source objects with layout conflicts, their connection hold fields, port hold fields, period hold fields, and exclusion reasons are written to the same constraint relationship to generate a conflict hold constraint record.

[0114] Based on the conflict-preserving constraint record, the boundary attribution, location attribution, and adjacent constraint relationships of spatial layout objects are adjusted within the local engineering scope. The adjusted spatial layout relationships are then substituted back to the projectable topology engineering map, electrical logic map, and spatial layout map for consistency confirmation, generating a topology-preserving correction record.

[0115] It should be noted that the conflict-preserving constraint record is used to read the same-origin objects with layout conflicts, connection preservation fields, port preservation fields, and period preservation fields. Within the local project scope, the occupied boundary, boundary attribution, location attribution, and adjacent constraint relationship of the corresponding spatial layout objects are retrieved. The boundary-affected objects in the local project scope record are used as the adjustment scope. Combined with the corresponding boundary available scope, space available relationship items, space restricted relationship items, and adjacent constraint relationships, the adjustable space scope is determined. Within the adjustable space scope, the spatial layout objects are processed by boundary translation, occupied boundary reduction, and release of non-preserving adjacent constraints to form multiple candidate spatial layout adjustment schemes.

[0116] When performing translation within the boundary, the boundary affiliation of the spatial arrangement object remains unchanged. Based on the spatial distance requirements in the rule constraints, the adjacent direction in the adjacent constraint relationship, and the acceptable range in the spatial availability relationship item, translation candidates under different location affiliations are generated. After the translation candidate is adjusted, the occupied boundary no longer forms a layout conflict with the spatial restricted relationship item and adjacent spatial arrangement objects. If continuing to translate in the same direction will exceed the boundary availability range, destroy the adjacent constraint relationship, change the connection retention field, change the port retention field, or change the period retention field, the generation of translation candidates in that direction is stopped.

[0117] When performing occupancy boundary reduction processing, while maintaining the port correspondence, equipment ownership, and period attribute relationship unchanged, reduction candidates are generated for the occupancy boundary side that does not carry port connection relationships. After the reduction candidate is adjusted, the occupancy boundary no longer falls into the space-constrained relationship item, and if further reduction will result in any of the following situations being met: equipment layout requirements not being met, port connection relationships being compressed, occupancy boundary being empty, or period attribute relationship changing, the generation of reduction candidates on that side is stopped.

[0118] When performing non-preserving adjacency constraint release processing, release candidates are only generated for adjacency constraints for which connection preservation, port preservation, and period preservation fields have not been written. Release candidates can remove the overlapping relationship between adjacent spatial arrangement objects. If continuing to release will result in any of the following situations being met: adjacency constraint relationship cannot be inherited, boundary ownership is inconsistent, or spatial boundary is discontinuous, the generation of release candidates for that adjacency constraint relationship will be stopped.

[0119] When verifying the validity of candidate spatial layout adjustment schemes, the adjusted occupied boundaries are superimposed and verified with the available boundary range, spatial constraint relationship items, and the occupied boundaries of adjacent spatial layout objects. The adjusted boundary attribution, location attribution, and adjacent constraint relationship are verified with the connection retention field, port retention field, and period retention field. Candidate spatial layout adjustment schemes with empty adjusted occupied boundaries, exceeding the available boundary range, falling into spatial constraint relationship items, changing the connection retention field, changing the port retention field, or changing the period retention field are written into the candidate exclusion items, and the corresponding exclusion reasons are recorded. Candidate spatial layout adjustment schemes not written into the candidate exclusion items participate in the calculation of topology retention correction values.

[0120] The expression for calculating the topology-preserving correction value is: ; in, Indicates the first Topology preservation correction value for each candidate spatial arrangement adjustment scheme Indicates the first The spatial conflict residual rate of each candidate spatial layout adjustment scheme is defined as the ratio of the area of ​​the conflict area after merging the area of ​​the occupied boundary that exceeds the usable range of the boundary, the area that falls into the range corresponding to the spatial restricted relationship item, and the area that overlaps with the adjacent spatial layout object. Indicates the first The boundary adjustment rate of each candidate spatial layout adjustment scheme is the ratio of the difference between the combined area of ​​the occupied boundary and the overlapping area before and after the adjustment to the combined area of ​​the occupied boundary before and after the adjustment. Candidate spatial layout adjustment schemes with a combined area of ​​the occupied boundary before and after the adjustment being zero are written into the candidate exclusion items and are not included in the boundary adjustment rate calculation.

[0121] Indicates the first The rate of change of adjacent constraints for each candidate spatial layout adjustment scheme is the ratio of the number of different relationships in the set of adjacent constraints before and after the adjustment to the number of merged relationships in the set of adjacent constraints before and after the adjustment. When the set of adjacent constraints before and after the adjustment is empty, the rate of change of adjacent constraints is recorded as zero. When there is only one side of the set of adjacent constraints before and after the adjustment, it is calculated according to the ratio of the number of different relationships to the number of merged relationships. Indicates the first The topology maintenance violation flag for each candidate spatial layout adjustment scheme is set to 0 when the connection maintenance field, port maintenance field, and period maintenance field all remain unchanged, and 1 when any maintenance field is changed. The topology maintenance violation flag is used to record the violation status of the candidate spatial layout adjustment scheme on the topology maintenance condition, and serves as the basis for screening and eliminating candidate schemes and leaving traces of the reasons. This represents the denominator correction amount, used to correct for zero denominators in the calculation process. It is a dimensionless correction amount that is greater than 0 and much less than 1, such as 0.0000001.

[0122] Topology preservation conditions refer to the following: the connection start point, connection end point, and adjacent object affiliation in the connection preservation field remain unchanged; the port affiliation and device affiliation correspondence in the port preservation field remain unchanged; and the period attribute, interval configuration source, and restricted configuration range affiliation in the period preservation field remain unchanged.

[0123] Based on the topology preservation condition, candidate spatial arrangement adjustment schemes that are not written into the candidate exclusion items are screened. Candidate spatial arrangement adjustment schemes that violate the topology preservation condition and are marked as 1 are written into the candidate exclusion items, and the corresponding violation field is written with the exclusion reason. Among the candidate spatial arrangement adjustment schemes that violate the topology preservation condition and are not written into the candidate exclusion items, the scheme with the smallest topology preservation correction value is selected as the target spatial arrangement adjustment scheme. If there are no candidate spatial arrangement adjustment schemes that violate the topology preservation condition and are not written into the candidate exclusion items, the corresponding same-source object is written into the correction restriction field, and the reason for failure is recorded.

[0124] Substitute the boundary attribution, location attribution, and adjacent constraint relationships corresponding to the target spatial layout adjustment scheme back to the projectable topology engineering map, electrical logic map, and spatial layout map for consistency verification. If all three types of maps pass the verification, write the target spatial layout adjustment scheme, topology preservation correction value, topology preservation conditions, and consistency verification results of the three maps into the topology preservation correction record. If there are fields with restricted correction, inconsistent source identifiers, changed connection preservation fields, changed port preservation fields, or changed period preservation fields, do not write valid correction results, and record the reasons for failure.

[0125] It should also be noted that the expression is in this form in order to incorporate spatial conflict residues, boundary adjustment ranges, and changes in adjacent constraints into the same correction evaluation value, while using topology preservation conditions as the scheme selection boundary; thus, the target scheme is not simply the one with the minimum spatial movement, but rather the one with the minimum local layout correction cost without changing electrical connections, port correspondences, and phase attributes.

[0126] Based on the topology-preserving correction record, the projectable topology engineering map, electrical logic map, and spatial layout map are updated synchronously to generate a synchronous update map. The synchronous update map is then confirmed for period continuity and version tracking is performed, and the substation intelligent achievement set is output.

[0127] It should be noted that when performing synchronous updates based on the topology-preserving correction record, the adjusted spatial layout relationships, topology preservation conditions, three-map consistency confirmation results, and reasons for failure are read from the topology-preserving correction record. If the three-map consistency confirmation result is successful, the adjusted boundary attribution, location attribution, and adjacent constraint relationships are written into the spatial layout map. The corresponding boundary attribution and period attributes are written back to the projectable topology engineering map according to the same-source identifier. The connection start point, connection end point, port attribution, and equipment attribution in the electrical logic map remain unchanged according to the topology preservation conditions. If the three-map consistency confirmation result fails, the synchronous writing of the corresponding same-source objects is not performed, and the reason for failure is written into the synchronous not-written field.

[0128] After the synchronization is completed, the updated objects in the projectable topology engineering map, electrical logic map, and spatial layout map are merged according to the same source identifier to form a synchronization update map. The synchronization update map records the same source identifier, updated boundary attribution, location attribution, adjacent constraint relationship, period attribute relationship, unchanged electrical logic relationship, and fields not written in the synchronization, and serves as input for period connection confirmation and version tracking. After period connection confirmation and version tracking, the synchronization update map and the corresponding processing records are used together to output the substation intelligent achievement set.

[0129] Based on the phase attribute relationships in the synchronously updated map, the current phase affiliation of the local project scope is identified, and phase comparison objects with the current phase affiliation are selected. The port affiliation, spatial boundary continuation and reserved area occupancy status are verified, and a phase connection record is generated.

[0130] It should be noted that when confirming the phase connection of the synchronous update map, the phase attribute relationship, updated boundary attribution, location attribution, adjacent constraint relationship and unchanged electrical logic relationship of the updated object are read according to the same source identifier; the phase attribute relationship corresponding to the updated object within the local project scope is marked as the current phase attribution, and the phase attribute relationship of other updated objects under the same boundary attribution in the synchronous update map is used as the phase connection verification object; reserved range occupancy verification, port acceptance verification and spatial boundary continuation verification are performed on the phase connection verification objects under the same boundary attribution, and the phase connection verification objects that can form an acceptance with the current phase attribution in all three verifications are marked as phase comparison objects.

[0131] When verifying the connection between the current period's attribution and the period's reference object, the port acceptance status is checked based on the unchanged electrical logic relationship, the spatial boundary continuity status is checked based on the updated boundary attribution, location attribution, and adjacent constraint relationship, and the reserved range occupancy status is checked based on the period attribute relationship. If the port acceptance status can complete the connection start point, connection end point, and port attribution verification along the unchanged electrical logic relationship, and the spatial boundary continuity status can complete the boundary attribution acceptance verification, location attribution acceptance verification, and adjacent constraint relationship acceptance verification along the updated boundary attribution, location attribution, and adjacent constraint relationship, and does not occupy the restricted configuration range, it is written into the period connection record. If the boundary attribution acceptance verification is inconsistent, the location attribution cannot form a continuous acceptance according to the adjacent constraint relationship, the adjacent constraint relationship is missing, or the object pointed to by the adjacent constraint relationship is inconsistent with the period reference object, it is marked as a spatial boundary discontinuity. If there is a port acceptance interruption, spatial boundary discontinuity, or reserved range occupancy, it is written into the period connection exception field, and the corresponding same-source identifier and exception reason are recorded.

[0132] Compare the version differences between the projectable topology engineering diagram, electrical logic diagram, and spatial layout diagram before and after the topology-preserving modification, and write the corresponding difference items according to object changes, relationship changes, and period changes to generate version trace records.

[0133] It should be noted that, using the same-source identifier as the comparison index, the projectable topology engineering map, electrical logic map, and spatial layout map before topology preservation correction are read, and the updated objects with the same-source identifier in the synchronous update map are read to form the map state before correction and the map state after correction; the engineering topology objects in the projectable topology engineering map are compared, and if the boundary attribution, phase attribute, and projectable mapping relationship have changed, the object change difference item is written; the electrical logic objects in the electrical logic map are compared, and if the connection start point, connection end point, port attribution, and equipment attribution are consistent, the connection preservation item is written, and if there are inconsistencies, the relationship change difference item is written; the spatial layout objects in the spatial layout map are compared, and if the boundary attribution, location attribution, and adjacent constraint relationship have changed, the spatial relationship change difference item is written.

[0134] Compare the period connection records and period connection exception fields. If there are changes in period attribute relationships, period reference objects, port acceptance status, space boundary continuation status, and reserved range occupancy status, write the period change difference item. The same source objects corresponding to the fields that are not written in the synchronization do not participate in the effective version difference writing, and the reason for not writing is retained in the version trace record.

[0135] Write the same source identifier, source map, map status before correction, map status after correction, object change difference items, relationship change difference items, period change difference items, connection retention items, and reasons for not writing into the same logging relationship to generate a version logging record.

[0136] The synchronized updated map, period connection record, and version trace record will be collected according to the same source identifier, and the period connection record and version trace record will be associated with the corresponding map position to generate the substation intelligent result set.

[0137] It should be noted that, using the same source identifier as the aggregation index, the synchronous update map, period connection record, and version trace record are read, and the updated objects, period connection status, and version difference items under the same same source identifier are written into the same result aggregation relationship; if there are same source objects in the synchronous update map that have not been written with fields in the synchronous update map, they are not written into valid result items, and the reason for not writing is retained as a result restricted item; if there are same source objects in the period connection record that have period connection abnormal fields, they are written into the result review item, and the corresponding abnormal reason is associated.

[0138] When performing map location association, the corresponding projectable topology engineering map record, electrical logic map record, and spatial layout map record in the synchronously updated map are searched according to the same source identifier. The period connection record is associated with the corresponding period attribute relationship and spatial layout map record, and the version trace record is associated with the map record where object changes, relationship changes, and period changes have occurred.

[0139] The updated map, period connection record, version record, restricted items, review items and corresponding map positions are written into the same result record to generate a substation intelligent result set.

[0140] In summary, this invention achieves stable associations between engineering objects at the topology, electrical logic, and spatial layout layers by generating a composite topology engineering map and uniformly writing electrical connections, spatial constraints, equipment attributes, and phase attributes into a homogeneous topology structure, thereby reducing the risk of incomplete synchronization and inconsistent attribution relationships among multiple types of results. Furthermore, through topology-preserving correction, the electrical connection sequence, port correspondence, and phase attribute relationships are solidified during local layout conflict resolution, achieving synergy between spatial layout adjustments and the preservation of key topology relationships. This avoids implicit changes in electrical logic and phase inheritance relationships caused by local corrections, improving the consistency, traceability, and feasibility of results updates.

[0141] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A substation intelligent design system based on topology relationships, characterized in that, include: The topology baseline module acquires basic data of the substation project and performs topology baseline processing to determine the project boundaries, rule constraints, phase attributes and bay configuration sources, and generates project topology baseline records. The topology fusion module performs anchoring instantiation processing based on the engineering topology baseline record, maps electrical bay objects, equipment objects, port objects, and space occupancy objects to engineering topology objects with the same source identifier, and performs topology fusion on the electrical connection relationship, spatial constraint relationship, equipment attribute relationship and phase attribute relationship between engineering topology objects to generate a composite topology engineering map; The projection association module verifies the connection closure status, equipment attribute acceptance status, and map projection conditions of each engineering topology object in the composite topology engineering map, forms a projectable topology engineering map, and converts the projectable topology engineering map into an electrical logic map and a spatial layout map respectively through logical projection and layout projection, and generates a three-map association record according to the same source identifier. The impact verification module performs consistency verification on the same source objects in the three-map association record, generates a topology change event record, and determines the local engineering scope with the same source identifier in the topology change event record as the center, performs topology constraint verification on the local engineering scope, and generates a local impact domain verification record. The specific steps for generating the topology change event record are as follows: Using the same-source objects in the three-map association records as the verification objects, the connection, boundary, and phase assignments of engineering topology objects, electrical logic objects, and spatial layout objects are aligned according to the same-source identifier to form a same-source verification benchmark record; Consistency judgment is performed on the same source verification benchmark records, and the differences are marked as inconsistencies between electrical connection relationship and connection attribution, spatial constraint relationship and boundary attribution, and period attribute relationship and period attribution. Asynchronous differences caused by changes in the position displayed on the map are excluded, and the same source difference judgment record is formed. Based on the difference type, source map and affected objects in the same source difference determination record, determine the synchronization direction and processing priority corresponding to the difference item, and generate a topology change event record; The specific steps for generating the local influence domain verification record are as follows: Starting from the source identifier and difference type in the topology change event record, the corresponding source object is locked in the three-map association record, and the associated object is extended along the electrical connection relationship, spatial constraint relationship and phase attribute relationship in the composite topology engineering map. The connected affected object, the boundary affected object and the phase affected object are included in the same local project scope, and a local project scope record is generated. Perform topology constraint verification on the corresponding affected objects in the local project scope record, check the connection status, spatial boundary status and phase status between each affected object, identify the same source objects that meet the synchronization conditions and the same source objects that have layout conflicts, and generate local influence domain verification records. The maintenance correction module performs topology-preserving correction on local engineering areas with layout conflicts based on the local influence domain verification records. It adjusts the spatial layout relationship while keeping the electrical connection sequence, port correspondence, and period attribute relationship unchanged, and outputs the substation intelligent result set. The specific steps for generating the intelligent results set of the output substation are as follows: Locate the source objects with layout conflicts from the local influence domain verification record, and solidify the electrical connection sequence, port correspondence and period attribute relationship of the source objects as topology preservation conditions to generate conflict preservation constraint records. Based on the conflict-preserving constraint record, the boundary attribution, location attribution and adjacent constraint relationship of the spatial layout objects are adjusted within the local engineering scope. The adjusted spatial layout relationship is then substituted back to the projectable topology engineering map, electrical logic map and spatial layout map for consistency confirmation, generating a topology-preserving correction record. Based on the topology-preserving correction record, the projectable topology engineering map, electrical logic map, and spatial layout map are updated synchronously to generate a synchronous update map. The synchronous update map is then confirmed for period continuity and version tracking is performed, and the substation intelligent achievement set is output.

2. The substation intelligent design system based on topology as described in claim 1, characterized in that, The specific steps for generating the engineering topology baseline record are as follows: The site range, construction scale, voltage level and engineering rule source in the basic data of substation engineering are coupled with boundary constraints to determine the engineering boundary and corresponding rule constraints. The available range of the engineering boundary is corrected according to the layout requirements and bay access requirements corresponding to the voltage level, and a boundary constraint benchmark record is generated. Based on the boundary constraint benchmark record, the construction period information and wiring configuration requirements in the substation project basic data are analyzed for period continuity. The period attributes are determined under the corresponding project boundary, and the sources of callable bay configurations, the releasable reserved range, and the restricted configuration range are determined based on the period attributes, generating the period bay continuity record. The topology benchmark is bound to the boundary constraint benchmark record and the period interval acceptance record. The engineering boundary, rule constraint, period attribute and interval configuration source are written into the benchmark relationship under the same boundary to generate the engineering topology benchmark record.

3. The substation intelligent design system based on topology as described in claim 2, characterized in that, The anchoring instantiation process based on the engineering topology baseline record maps electrical bay objects, equipment objects, port objects, and space placeholder objects to engineering topology objects with the same source identifier. The specific steps are as follows: Based on the phase attributes and interval configuration sources under the same boundary in the engineering topology baseline record, the phase availability screening and boundary adaptation correction are performed on the interval configuration sources to determine the target electrical interval objects and their assembleable equipment objects, port objects and space occupancy objects, and generate interval assembly candidate records. Based on the candidate records for bay assembly and the corresponding rule constraints, the target electrical bay object is hierarchically assembled with the assembleable equipment objects, port objects, and space occupant objects, and a common-source identifier is configured to generate an anchored bay topology record.

4. The substation intelligent design system based on topology as described in claim 3, characterized in that, The specific steps for generating the composite topology engineering map are as follows: Using the same source identifier in the anchored interval topology record as an index, the port connection relationship between electrical interval objects is identified, and the electrical connection relationship is determined by combining the access direction of the port object and the device object to which it belongs. The device object and the rule constraint are processed to determine the attribute value of the device object. The attribute values ​​of the equipment object are attached to the corresponding engineering topology object, and the boundary range of the space occupant object is mapped to the rule constraints in the engineering topology baseline record to obtain the equipment attribute relationship and spatial constraint relationship; The period attribute relationships of each engineering topology object are determined according to the period attribute in the engineering topology benchmark record, and the electrical connection relationship, spatial constraint relationship, equipment attribute relationship and period attribute relationship are written into the same topology structure to generate a composite topology engineering map.

5. The substation intelligent design system based on topology as described in claim 4, characterized in that, The specific steps for forming a projectable topology engineering map are as follows: Track the connection status of port objects along the electrical connection relationships in the composite topology engineering map, and mark the engineering topology objects that belong to the inlet end, outlet end and adjacent objects that satisfy the closed connection relationship as connection closure objects, forming a connection closure verification record; The device attribute relationships corresponding to each connection closure object in the connection closure verification record are compared with the rule constraints and interval configuration sources under the same boundary, and the projection conditions are checked. Engineering topology objects with object identification, connection affiliation, attribute acceptance, and spatial constraint acceptance are written into the projectable mapping relationship to form a projectable topology engineering map.

6. The substation intelligent design system based on topology as described in claim 1 or 5, characterized in that, The specific steps for generating the three-graph association records according to the homology identifier are as follows: Read the engineering topology objects that have been written with projectable mapping relationships in the projectable topology engineering map, and write the electrical connection relationships corresponding to the engineering topology objects into the logical projection sequence according to the same source identifier, and write the spatial constraint relationships corresponding to the engineering topology objects into the layout projection sequence to generate map projection task records; According to the map projection task record, wiring element projection and spatial boundary projection processing are performed on the logic projection sequence and the layout projection sequence respectively, converting electrical connection relationships into electrical logic objects and spatial constraint relationships into spatial layout objects, generating electrical logic map and spatial layout map; Engineering topology objects, electrical logic objects, and spatial layout objects with consistent source identifiers are defined as source objects. The correspondence between source objects and projectable topology engineering maps, electrical logic maps, and spatial layout maps is established, and a three-map association record is generated.

7. The substation intelligent design system based on topology as described in claim 1, characterized in that, The specific steps for confirming the continuity of the synchronized updated graph and performing version tracking are as follows: Based on the phase attribute relationships in the synchronously updated map, identify the current phase affiliation of the local project scope, filter phase comparison objects that have a succession relationship with the current phase affiliation, and verify the port succession, spatial boundary continuation and reserved area occupancy status to generate phase connection records; Compare the version differences between the projectable topology engineering diagram, electrical logic diagram and spatial layout diagram before and after the topology-preserving modification, and write the corresponding difference items according to object changes, relationship changes and period changes to generate version trace records; The synchronized updated map, period connection record, and version trace record will be collected according to the same source identifier, and the period connection record and version trace record will be associated with the corresponding map position to generate the substation intelligent result set.

Images