A power grid engineering multi-specialty collaborative design method based on data fusion

Abstract

This invention discloses a multi-disciplinary collaborative design method for power grid engineering based on data fusion, relating to the field of collaborative design technology. The method includes: receiving professional design data and constraint data; performing object merging to generate an object library and a constraint library; reading the object library and constraint library to generate candidate object pairs, obtaining the relationships to be established, and generating a callable clearance ledger; receiving local design modifications, generating change domains, calculating penetration values, recalculating the clearance amount after local modifications, identifying review relationships, boundary-breaking relationships, existing abnormal relationships, and objects to be repaired; generating a change domain to accept changes and performing boundary-breaking propagation; obtaining a set of review relationships, a set of boundary-breaking relationships, a set of existing abnormal relationships, and a set of objects to be repaired; establishing a list of objects to be repaired, generating correction domains and correction content, locking the responsible professional, writing back to the object library, updating the callable clearance ledger, and triggering a correction closure check; improving the consistency, traceability, and closure of multi-disciplinary collaborative design.

Description

Technical Field

[0001] This invention relates to the field of collaborative design technology, and in particular to a multi-disciplinary collaborative design method for power grid engineering based on data fusion. Background Technology

[0002] Power grid engineering design typically involves disciplines such as primary, secondary, communication, civil engineering, fire protection, grounding, construction, and operation and maintenance. The design objects have multi-dimensional characteristics such as spatial location, connection endpoints, path boundaries, capacity attributes, and operational boundaries. In the conventional design process, the methods of establishing files for each discipline, conducting phased reviews, manual verification, and coordinating local drawings are often used to compare equipment layout, channel capacity, path laying, maintenance space, and construction occupation scope, so as to form a collaborative design result that meets the requirements of engineering specifications, equipment installation, and operation and maintenance.

[0003] However, conventional methods still have limitations. On the one hand, there are differences in the source format, coordinate benchmark, object coding and constraint expression of data from different disciplines. The correspondence between cross-disciplinary objects usually needs to be checked repeatedly in multiple rounds, which affects the continuity of the constraint relationship establishment. On the other hand, after local design modifications, the constraint relationships related to net distance, capacity, path and action space still mainly rely on manual tracking. It is difficult to continuously transmit and close the scope of the modification, the relationship to be reviewed and the object to be repaired, which affects the consistency of multi-disciplinary collaborative design. Summary of the Invention

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

[0005] Therefore, this invention provides a multi-disciplinary collaborative design method for power grid engineering based on data fusion to solve the problems of insufficient accuracy in the association of multi-source design data and difficulty in closing the loop on the impact of local modifications in existing technologies.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] This invention provides a multi-disciplinary collaborative design method for power grid engineering based on data fusion, comprising: receiving professional design data and constraint data, unifying engineering coordinate benchmarks, parsing object records, generating action boundaries, performing object merging, and generating an object library and a constraint library; reading the object library and constraint library, generating candidate object pairs, obtaining relationships to be established, marking relationship status, and generating a callable clearance ledger; receiving local design modifications, locating changed objects, generating change domains, reading the set of relationships to be judged and the set of existing abnormal relationships from the callable clearance ledger, calculating penetration values, recalculating clearance after local modifications, identifying verification relationships, boundary-breaking relationships, existing abnormal relationships, and objects to be repaired, generating a change domain and performing boundary-breaking propagation, and obtaining the set of verification relationships, the set of boundary-breaking relationships, the set of existing abnormal relationships, and the set of objects to be repaired; establishing a list of objects to be repaired based on the set of verification relationships, the set of boundary-breaking relationships, the set of existing abnormal relationships, and the set of objects to be repaired, determining the attributes to be modified, generating correction domains and correction content, locking the responsible professional, writing back to the object library, updating the callable clearance ledger, and triggering correction closure verification.

[0008] As a preferred embodiment of the multi-disciplinary collaborative design method for power grid engineering based on data fusion described in this invention, the generation of action boundaries includes: receiving professional design data and constraint data, establishing an original data list, performing coordinate transformation based on the original data list and station area surveying benchmarks, generating an engineering coordinate dataset; and parsing object records based on the engineering coordinate dataset to generate action boundaries.

[0009] As a preferred embodiment of the multi-disciplinary collaborative design method for power grid engineering based on data fusion described in this invention, the generation of the object library and constraint library includes: calculating the object matching accuracy based on engineering control points with the same name, performing object merging, and generating the object library; and performing type normalization, relationship classification, quantity classification, and trigger attribute matching based on constraint data and the object library to generate the constraint library.

[0010] As a preferred embodiment of the multi-disciplinary collaborative design method for power grid engineering based on data fusion described in this invention, the step of obtaining the relationship to be established includes: reading the object library and constraint library, performing field verification, reading constraint items, filtering and pairing the object set, and generating candidate object pairs; based on the candidate object pairs, performing trigger attribute verification and relationship type confirmation to obtain the relationship to be established and the constraint scope.

[0011] As a preferred embodiment of the multi-disciplinary collaborative design method for power grid engineering based on data fusion described in this invention, the generation of a callable gap ledger includes: calculating the actual quantity before modification, the required quantity before modification, and the gap quantity before modification according to the quantity category based on the relationship to be established, and marking the relationship status; writing the relationship status into the ledger record and performing ledger closure verification to generate a callable gap ledger.

[0012] As a preferred embodiment of the data fusion-based multi-disciplinary collaborative design method for power grid engineering described in this invention, the step of receiving local design modifications, locating the changed objects, and generating a change domain includes: receiving local design modifications, parsing and generating object records after local modifications, locating object records before modifications and changed object numbers by combining with an object library; and identifying differences in execution fields such as spatial outline, connection endpoints, path boundaries, attribute items, and action boundaries based on object records before modifications and object records after local modifications, thereby generating a set of changed attributes and a change domain.

[0013] As a preferred embodiment of the data fusion-based multi-disciplinary collaborative design method for power grid engineering described in this invention, the identification of verification relationships, boundary-breaking relationships, existing abnormal relationships, and objects to be repaired includes: reading the callable clearance ledger based on the changed object number and the set of changed attributes; generating a set of relationships to be judged and a set of existing abnormal relationships according to the relationship status; calculating the penetration value based on the change domain and the constraint domain; and filtering the penetrated relationships. Based on the penetrated relationships, recalculating the actual quantity after local modification, the demand quantity after local modification, and the clearance quantity after local modification, identifying the penetrated relationships as verification relationships or boundary-breaking relationships, and generating a set of verification relationships, a set of boundary-breaking relationships, and a set of objects to be repaired.

[0014] As a preferred embodiment of the multi-disciplinary collaborative design method for power grid engineering based on data fusion described in this invention, the step of generating the change domain and performing boundary-breaking propagation includes: generating the change domain based on the boundary-breaking relationship set and the set of objects to be repaired; taking the newly added objects to be repaired that have not yet participated in the propagation as the objects to be propagated in the next round; rereading the callable gap ledger and calculating the penetration value; updating the verification relationship set, the boundary-breaking relationship set, the existing abnormal relationship set, and the set of objects to be repaired, until no more new boundary-breaking relationships are generated.

[0015] As a preferred embodiment of the multi-disciplinary collaborative design method for power grid engineering based on data fusion described in this invention, the determination of the attribute to be modified includes: extracting object fields from the associated object library based on the set of boundary-breaking relationships, the set of verification relationships, the set of existing abnormal relationships, and the set of objects to be repaired; establishing a list of objects to be repaired; generating associated boundary-breaking relationships, associated verification relationships, and associated existing abnormal relationships; reading the associated boundary-breaking relationships and triggering attributes based on the list of objects to be repaired; determining the attribute to be modified; reading the maintenance relationship based on the callable gap ledger; and generating an adjustable base domain.

[0016] As a preferred embodiment of the data fusion-based multi-disciplinary collaborative design method for power grid engineering described in this invention, the write-back of the object library, updating the callable gap ledger, and triggering the correction closure check include: generating a boundary-breaking limit domain and a check-keeping domain based on the adjustable base domain, associated boundary-breaking relationships, and associated check-keeping relationships, and synthesizing a correction domain; generating single-object correction content or joint correction content based on the correction domain and associated existing anomaly relationships; locking the responsible specialty by combining the candidate responsible specialty and the specialty source; partially writing back the object library; updating the callable gap ledger; triggering the correction closure check; and generating a correction closure check record.

[0017] The beneficial effects of this invention are as follows: By generating a change domain, the set of relationships to be judged and the set of existing abnormal relationships are read from the callable gap ledger, the penetration value is calculated and the gap amount after local modification is recalculated, so as to achieve targeted identification of review relationships, boundary-breaking relationships, existing abnormal relationships and objects to be repaired, and to clarify the scope of influence of local modifications; by establishing a list of objects to be repaired, generating correction domains and correction content, locking the responsible profession and triggering the correction closure check, so as to form a continuous processing chain of design modification, responsibility assignment and constraint restoration, and improve the consistency, traceability and closure of multi-professional collaborative design. Attached Figure Description

[0018] 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.

[0019] Figure 1 This is a flowchart of a multi-disciplinary collaborative design method for power grid engineering based on data fusion.

[0020] Figure 2 A flowchart for generating a callable gap ledger.

[0021] Figure 3 The flowchart for performing boundary-breaking propagation.

[0022] Figure 4 A flowchart for generating corrected closure check records.

[0023] Figure 5 This is a change screening and identification image for representative scenarios.

[0024] Figure 6 This is a graph showing the changes in penetration values ​​from scenario Q1 to scenario Q8. Detailed Implementation

[0025] 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.

[0026] 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.

[0027] 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.

[0028] Reference Figures 1-6 This is one embodiment of the present invention, which provides a multi-disciplinary collaborative design method for power grid engineering based on data fusion, including the following steps:

[0029] S1. Receive professional design data and constraint data, unify engineering coordinate benchmarks, parse object records, generate action boundaries, perform object merging, and generate object and constraint libraries.

[0030] Receive professional design data and constraint data, establish an original data list, perform coordinate transformation based on the original data list and station area surveying benchmarks, and generate an engineering coordinate dataset; based on the engineering coordinate dataset, parse object records and generate action boundaries.

[0031] Furthermore, it receives primary design data, secondary design data, communication design data, civil engineering design data, fire protection design data, grounding design data, construction route data, operation and maintenance space data, and constraint data for power grid projects.

[0032] Specifically, primary design data includes the object name, object code, object type, spatial coordinates, external dimensions, connection endpoints, and attribute items of main transformers, circuit breakers, disconnecting switches, busbars, and structures; secondary design data includes the connection endpoints, path inflection points, and attribute items of protection cabinets, measurement and control cabinets, terminals, and secondary cables; communication design data includes the connection endpoints and path inflection points of communication equipment, optical cable paths, and communication channels; civil engineering design data includes the spatial coordinates, external dimensions, and elevations of foundations, buildings, roads, ditches, and structures; fire protection design data includes the spatial coordinates, external dimensions, and attribute items of oil tanks, firewalls, fire access routes, and fire protection facilities; grounding design data includes the grounding grid, grounding down conductors, grounding points, and grounding paths; construction path data includes transportation paths, hoisting paths, temporary occupation boundaries, and placement paths; operation and maintenance space data includes inspection passages, maintenance extraction spaces, operating spaces, and reserved space for expansion; constraint data includes constraint name, applicable object type, relationship type, quantity category, trigger attribute, required quantity, required quantity unit, required quantity source, and candidate responsible discipline.

[0033] Furthermore, the station area surveying benchmarks in the civil engineering design data are read as engineering coordinate benchmarks; the corresponding engineering control points in the design data of each discipline are read, including station area surveying benchmarks, building axis intersections, equipment foundation positioning points, and framework positioning points.

[0034] Based on the coordinate correspondence of the same-named engineering control points, the coordinate transformation parameters of each professional design data relative to the engineering coordinate datum are calculated. According to the coordinate transformation parameters, coordinate transformation is performed on the primary design data, secondary design data, communication design data, fire protection design data, grounding design data, construction path data, and operation and maintenance space data, so that the spatial coordinates, external dimension related points, connection endpoint coordinates, path inflection point coordinates, and action boundary coordinates in each professional design data fall into the same engineering coordinate datum. The transformed engineering coordinates form an engineering coordinate dataset.

[0035] Specifically, the coordinate transformation parameters include translation, rotation angle, and uniform scaling factor; based on no less than three engineering control points with the same name, the coordinate transformation parameters that minimize the sum of squared coordinate deviations of the control points after transformation are obtained, and abnormal control points are eliminated using the transformation residuals; when the number of remaining engineering control points with the same name after elimination is less than three, the corresponding professional design data is marked as data to be reviewed.

[0036] It should be noted that after the conversion, the source coordinates and engineering coordinates are retained in each data entry. Subsequent calculations will only use the engineering coordinates, while the source coordinates will be used for tracing.

[0037] Based on the same-named engineering control points, calculate the object matching accuracy, perform object merging, and generate an object library; based on constraint data and the object library, perform type normalization, relationship classification, quantity classification, and trigger attribute matching to generate a constraint library.

[0038] Furthermore, after unifying the engineering coordinate benchmark, the object records are analyzed according to the granularity of the engineering object.

[0039] Specifically, the system reads the object name, object code, object type, and professional origin of each object; generates a spatial outline based on spatial coordinates and outline dimensions (in this embodiment, the spatial outline is represented by a spatial bounding box); generates connection endpoints based on connection endpoint coordinates; generates path boundaries based on path vertices; generates attribute items based on capacity, voltage level, weight, interface type, load-bearing attributes, oil discharge direction, channel capacity, occupancy, and corresponding device code; and forms a version record based on version number and modification time.

[0040] It should be noted that if an object does not have connection endpoints, path boundaries, or attribute items, the corresponding field will be empty.

[0041] Furthermore, based on object records, construction path data and operation and maintenance space data are read to generate action boundaries for the corresponding objects.

[0042] It should be noted that the action boundary refers to the space occupied by transportation, hoisting, commissioning, maintenance, and expansion-reserved actions.

[0043] Specifically, for transportation operations, the inflection points, width, and height of the transportation path are read to form the transportation space occupied along the transportation path; for hoisting operations, the hoisting path, slewing radius, and height are read to form the hoisting space occupied; for commissioning operations, the commissioning operation surface and distance are read to form the commissioning space occupied; for maintenance operations, the maintenance extraction direction, extraction length, and maintenance width are read to form the maintenance space occupied; and for expansion and reservation operations, the reservation boundary and reservation height are read to form the expansion and reservation space.

[0044] The space occupied by transportation, hoisting, commissioning, maintenance, and expansion reserves are uniformly written into the action boundary field of the corresponding object record; if the object does not appear in the construction path data and operation and maintenance space data, the action boundary is empty and does not participate in the calculation of action space quantity.

[0045] Furthermore, to avoid duplicate filing of the same project object by different disciplines, the object matching accuracy is calculated based on the same-named project control points. The object matching accuracy is used to determine whether the records of objects from different disciplines are merged into the same project object.

[0046] It should be noted that the object matching accuracy is determined by three times the root mean square distance of the coordinate deviation of the corresponding engineering control points. The corresponding engineering control points are distributed at the station area surveying benchmark, the intersection of building axes, the equipment foundation positioning points, and the framework positioning points. The coordinate deviation can reflect the comprehensive offset of coordinate transformation error, surveying error, and professional modeling error. The three-fold coefficient is used to cover the normal fluctuation range of the deviation of the corresponding engineering control points within the engineering coordinate benchmark, so that the object merging judgment has a tolerance boundary. When the object codes are inconsistent, the object matching accuracy is used as the comparison limit of the spatial outline center distance. When the spatial outline center distance is not greater than the object matching accuracy, and the connection endpoints are consistent or the corresponding equipment codes are consistent, they are merged into the same engineering object.

[0047] Specifically, the object matching precision is expressed as:

[0048] ;

[0049] in, Indicates the precision of object matching. This indicates the number of engineering control points participating in the verification, and its value is an integer greater than or equal to three. Indicates the sequence number of the engineering control point. Indicates the first The engineering coordinates of each engineering control point in the first professional design data. Indicates the first The engineering coordinates of each engineering control point in the second professional design data. This represents the Euclidean distance between two engineering coordinates.

[0050] Furthermore, after obtaining the object matching accuracy, the object records are merged.

[0051] Specifically, when two object records have the same object type and the same object code, they are merged into the same project object; when the object codes are inconsistent, the connection endpoints are checked for consistency, and the spatial outline center distance between the two object records is calculated. If the connection endpoints are consistent and the spatial outline center distance is not greater than the object matching precision, they are merged into the same project object; when the connection endpoints are empty, the corresponding device code in the attribute item is read. If the corresponding device codes are consistent and the spatial outline center distance is not greater than the object matching precision, they are merged into the same project object; if none of the conditions are met, merging is not performed; after merging, an object number is generated for each project object, and the object number is unique in the object library.

[0052] It should be noted that, specifically, the calculation of the spatial outline center distance between two object records involves, based on the spatial outline, reading the minimum and maximum coordinate values ​​of the spatial outline along three coordinate directions under the engineering coordinate reference; taking the midpoint between the minimum and maximum coordinate values ​​in the same coordinate direction as the center coordinate of the direction, and using the center coordinates of the three directions together to form the center point of the spatial outline; calculating the Euclidean distance between the center points of the spatial outlines of the two object records, and using the Euclidean distance as the spatial outline center distance.

[0053] Furthermore, the merged project objects are written into an object library. Each object in the object library includes an object number, object name, object code, object type, professional origin, spatial outline, connection endpoints, path boundaries, attribute items, action boundaries, version number, and modification time.

[0054] It should be noted that the object number is used to generate relationship numbers, locate changed objects, and determine write-back object numbers; the changed object number represents the object number directly located by local design modifications, and the write-back object number represents the object number to be repaired that is included in the write-back scope in the revised content. Both the changed object number and the write-back object number belong to the object number in the object library; the spatial outline is used to generate clearance relationships, support relationships, oil drainage relationships, construction action relationships, and operation and maintenance action relationships; the connection endpoint is used to generate grounding relationships, communication relationships, and path relationships; the path boundary is used to generate path relationships and capacity relationships; the attribute item is used to determine the applicable conditions for the demand; and the action boundary is used to generate construction action relationships and operation and maintenance action relationships.

[0055] Furthermore, a constraint library is generated based on the constraint data. Specifically, the constraint name and applicable object type are read to ensure that the applicable object type is consistent with the object type in the object library; the relationship type is read, which includes net distance relationship, capacity relationship, path relationship, support relationship, oil drainage relationship, grounding relationship, communication relationship, construction action relationship, and operation and maintenance action relationship.

[0056] Read quantity classes, specifically, quantity classes include distance quantity, capacity quantity, path quantity, and action space quantity; read trigger attributes, specifically, trigger attributes include spatial outline, connection endpoints, path boundaries, attribute items, and action boundaries; read demand quantity, demand quantity unit, demand quantity source, and responsible professional candidate.

[0057] It should be noted that the required quantities are derived from collectable values ​​in the design specifications, equipment installation documents, manufacturer interface documents, construction organization documents, or operation and maintenance documents adopted in this project, such as minimum safety distance, minimum fire prevention distance, maximum allowable cable path length, available channel capacity, maintenance extraction space, and hoisting rotation space; among them, the path quantity is used to characterize the constraint that the actual path length must not exceed the allowable path length, which is the upper limit of the length allowed for cable path, communication optical cable path, grounding connection path, trench path, cable tray path, or pipe gallery path in the design specifications, equipment installation documents, or manufacturer interface documents.

[0058] The final constraint library includes each constraint item with constraint item number, constraint name, applicable object type, relationship type, quantity class, trigger attribute, required quantity, required quantity unit, required quantity source, and candidate responsible profession.

[0059] S2. Read the object library and constraint library, generate candidate object pairs, obtain the relationship to be created, mark the relationship status, and generate a callable gap ledger.

[0060] Read the object library and constraint library, perform field verification, read constraint items, filter and pair the object set, and generate candidate object pairs; based on the candidate object pairs, perform trigger attribute verification and relationship type confirmation, and obtain the relationship to be created and the scope of constraints.

[0061] Furthermore, the object library is read to extract the object number, object name, object code, object type, professional origin, spatial outline, connection endpoints, path boundaries, attribute items, action boundaries, version number, and modification time.

[0062] Furthermore, the constraint library is read to extract the constraint item number, constraint name, applicable object type, relationship type, quantity class, trigger attribute, required quantity, required quantity unit, required quantity source, and candidate responsible profession.

[0063] Furthermore, field verification is performed. Specifically, the object number, object type, professional source, version number, and modification time must exist; spatial outline, connection endpoints, path boundaries, attribute items, and action boundaries are allowed to be empty, and null values ​​are explicitly recorded; constraint item number, applicable object type, relationship type, quantity class, trigger attribute, required quantity, required quantity unit, required quantity source, and responsible professional candidate must exist; after passing the field verification, candidate object pairs are generated.

[0064] Furthermore, each constraint item in the constraint library is read one by one, and the applicable object type in the constraint item is used as the object filtering condition.

[0065] Specifically, when the applicable object type includes a first object type and a second object type, objects with the same object type as the first object type are selected from the object library to form a first object set; objects with the same object type as the second object type are selected from the object library to form a second object set.

[0066] Furthermore, objects in the first object set are paired with objects in the second object set according to their object numbers to form candidate object pairs.

[0067] It should be noted that candidate object pairs must meet the trigger attribute availability conditions. Specifically, when the trigger attribute is spatial outline, both objects must have spatial outline; when the trigger attribute is connection endpoint, at least one object must have connection endpoint; when the trigger attribute is path boundary, at least one object must have path boundary; when the trigger attribute is attribute item, at least one object must have corresponding attribute item; when the trigger attribute is action boundary, at least one object must have action boundary. Object pairs that do not meet the trigger attribute availability conditions are eliminated.

[0068] Furthermore, the type of execution relationship for candidate objects is confirmed.

[0069] Specifically, when the relationship type is a net distance relationship, the spatial outlines of the two objects are read, and a constraint scope consisting of the nearest boundary regions of the two spatial outlines is generated.

[0070] Specifically, the nearest boundary region is determined according to the smallest bounding box of the spatial outline under the engineering coordinate reference; when two spatial outlines are separate, the set of relative boundary surfaces with the smallest distance between the two spatial outlines is selected, and the coverage area of ​​the relative boundary surfaces and connecting line segments is used as the constraint domain; when two spatial outlines are in contact, intersecting or containing each other, the contact surface, intersecting area or containing overlapping area is used as the constraint domain, and the corresponding actual distance is recorded as zero; when there are multiple sets of relative boundary surfaces with the same distance, they are selected in descending order of boundary surface area, and when the areas are the same, they are selected in order of object number.

[0071] When the relationship type is capacity relationship, read the path boundary, channel capacity, and occupancy, and generate a constraint scope consisting of the spatial range corresponding to the path boundary and channel capacity.

[0072] When the relationship type is path relationship, read the connection endpoints and path boundaries to generate a constraint scope consisting of the connection endpoints and path boundaries.

[0073] When the relationship type is support relationship, the spatial outline of the supported object, the spatial outline of the supporting object, and the bearing attributes are read to generate a constraint scope jointly defined by the bottom projection of the supported object, the top boundary of the supporting object, and the bearing attributes.

[0074] When the relationship type is oil discharge relationship, the spatial outline of the oil-containing object, the spatial outline of the oil pool, and the oil discharge direction are read to generate a constraint domain consisting of the projected boundary of the oil-containing object, the boundary of the oil pool, and the coverage area of ​​the oil discharge direction.

[0075] When the relationship type is grounding relationship or communication relationship, read the connection endpoints and path boundaries to generate a constraint scope consisting of the connection endpoints, path boundaries and the spatial outline of the target object.

[0076] When the relationship type is a construction action relationship or an operation and maintenance action relationship, the action boundary and the spatial outline or path boundary of adjacent objects are read to generate a constraint scope jointly defined by the action boundary and the occupied area of ​​adjacent objects.

[0077] It should be noted that candidate objects that cannot generate constraint scopes are not written into the pending account relationship.

[0078] Based on the relationship to be established, calculate the actual quantity before modification, the required quantity before modification, and the remaining gap quantity before modification according to the quantity category, and mark the relationship status; based on the relationship status, write the ledger record and perform ledger closure verification to generate a callable gap ledger.

[0079] Furthermore, for the quantity class read from the account creation relationship, the actual quantity before modification and the required quantity before modification are generated according to the quantity class.

[0080] Specifically, when the quantity is a distance quantity, the actual distance between the two objects within the constraint scope is used as the actual quantity before modification, and the corresponding minimum allowable distance in the constraint library is used as the required quantity before modification.

[0081] When the quantity type is capacity, the available capacity of the channel is used as the actual quantity before modification, and the occupied capacity or reserved capacity is used as the required quantity before modification; the occupied capacity or reserved capacity comes from the attribute items in the object library or the required quantity in the constraint library.

[0082] When the quantity type is a path quantity, the path quantity is used to represent the constraint that the actual path length must not exceed the allowable path length. The allowable path length is used as the actual quantity before modification, and the actual path length corresponding to the path boundary is used as the demand quantity before modification. The clearance quantity before modification is equal to the allowable path length minus the actual path length. When the clearance quantity before modification is greater than zero, it means that the path still has margin. When the clearance quantity before modification is equal to zero, it means that the path just meets the upper limit of length. When the clearance quantity before modification is less than zero, it means that the actual path length exceeds the allowable path length.

[0083] When the quantity is an action space quantity, the available action space is used as the actual quantity before modification, and the space required by the action boundary is used as the required quantity before modification.

[0084] It should be noted that the actual quantity before modification and the required quantity before modification must use the same unit of demand; if the units are inconsistent, the unit conversion should be performed first based on the unit of demand before subsequent calculations.

[0085] Furthermore, for the pending account relationship between the actual quantity before modification and the required quantity before modification, calculate the remaining gap quantity before modification.

[0086] Specifically, the clearance amount before modification was expressed as:

[0087] ;

[0088] in, Representing relations The clearance amount before modification The superscript indicates the relationship number of the account to be created. This indicates the design before modification. Representing relations The actual quantity before modification. Representing relations The original demand quantity.

[0089] It should be noted that the pre-modification clearance amount uses the difference structure of the pre-modification actual amount minus the pre-modification demand amount. This is used to characterize the consumable margin of the account relationship to be established before the design modification, under the same demand unit. Net distance relationships, capacity relationships, path relationships, and motion space relationships can all be converted into a closed judgment that the actual amount is not less than the demand amount. Therefore, using the same difference direction can keep the relationship status markings of different quantity types consistent. For path quantities, the allowed path length is used as the pre-modification actual amount, and the actual path length is used as the pre-modification demand amount. This allows path quantities to have the same clearance judgment direction as distance quantities, capacity quantities, and motion space quantities. When the pre-modification clearance amount is greater than zero, the ledger record has a consumable margin. When the pre-modification clearance amount is equal to zero, the ledger record just meets the demand amount. When the pre-modification clearance amount is less than zero, the ledger record has already formed an existing abnormal relationship before the design modification.

[0090] It should be noted that the clearance value before modification is a real number; a clearance value greater than zero before modification indicates that the relationship has a consumable margin, a clearance value equal to zero before modification indicates that the relationship just meets the demand, and a clearance value less than zero before modification indicates that the relationship no longer meets the demand before the design modification.

[0091] Generate relation states, specifically, relation states include existing abnormal relations and consumable relations; relation states are used to distinguish whether the ledger records in the callable gap ledger have met the demand before the design modification; if the gap amount before modification is less than zero, the relation to be created is marked as an existing abnormal relation; if the gap amount before modification is greater than or equal to zero, the relation to be created is marked as a consumable relation.

[0092] Write the pending account relationships that have completed the relationship status marking into the callable gap ledger; each ledger record includes relationship number, starting object number, ending object number, relationship type, quantity class, trigger attribute, constraint scope, actual quantity before modification, required quantity before modification, gap quantity before modification, relationship status, required quantity unit, required quantity source, responsible professional candidate, version number, and modification time.

[0093] It should be noted that the relationship number is generated by concatenating the constraint item number, the starting object number, the ending object number, and the relationship type in sequence, to distinguish different relationships between the same pair of objects; the version number and modification time are inherited from the latest version record of the object record participating in the relationship, and are used to determine whether the ledger record needs to be updated when performing a partial write-back.

[0094] Furthermore, a ledger closure verification is performed on the callable gap ledger. The ledger closure verification is used to verify the closure consistency between ledger records and the object library, constraint library, dimensions, and versions during the callable gap ledger generation stage.

[0095] Specifically, the verification content includes: both the starting object number and the ending object number exist in the object library; the relationship type, quantity class, and triggering attribute all come from the constraint library; the constraint scope is jointly generated by the object library fields and the constraint library fields; the actual quantity before modification, the required quantity before modification, and the clearance quantity before modification have the same dimension; the source of the required quantity and the candidate responsible profession are inherited from the constraint library; and the version number and modification time can correspond to the object record participating in the relationship.

[0096] Retain ledger records that pass the ledger closure verification; reprocess ledger records that fail the ledger closure verification according to the failed content. Specifically, if the start object number, end object number, version number, or modification time fails the ledger closure verification, return to field verification for reprocessing; if the relation type, quantity class, trigger attribute, or constraint scope fails the ledger closure verification, return to trigger attribute validation and relation type confirmation for reprocessing; if the actual quantity before modification, the required quantity before modification, the remaining quantity before modification, or the unit of required quantity fails the ledger closure verification, return to calculate the actual quantity before modification, the required quantity before modification, and the remaining quantity before modification according to the quantity class for reprocessing.

[0097] Furthermore, a reprocessing flag is set for the same ledger record; if the same ledger record still fails the ledger closure verification after one reprocessing, a ledger exception record is generated, and the ledger record is no longer returned for reprocessing; the ledger exception record includes the relationship number, starting object number, ending object number, constraint item number, failed field, reason for failure, required quantity unit, version number, and modification time; the ledger exception record is not written to the callable gap ledger and is entered into the manual confirmation list; ledger records that have passed the ledger closure verification continue to be written to the callable gap ledger, and the callable gap ledger is generated from the ledger records that have passed the ledger closure verification.

[0098] S3. Receive partial design modifications, locate the changed objects, generate a change domain, read the set of relationships to be judged and the set of existing abnormal relationships from the callable gap ledger, calculate the penetration value, recalculate the gap amount after partial modification, identify the verification relationship, boundary breaking relationship, existing abnormal relationship and the object to be repaired, generate the change domain to accept and perform boundary breaking propagation, and obtain the set of verification relationship, the set of boundary breaking relationship, the set of existing abnormal relationship and the set of the object to be repaired.

[0099] Receive partial design modifications, parse and generate object records after partial modifications, combine with the object library to locate object records before modification and changed object numbers; based on object records before modification and object records after partial modifications, identify differences in execution fields such as spatial outline, connection endpoints, path boundaries, attribute items, and action boundaries, and generate a set of changed attributes and a change domain.

[0100] Furthermore, it can accept partial design modifications submitted by any discipline, including adjustments to object positions, external dimensions, connection endpoints, path vertices, attribute items, or action boundaries.

[0101] Furthermore, following the object parsing method used when generating the object library, the local design modifications are parsed to generate object records after the local modifications.

[0102] After partial modification, the object record includes the object name, object code, object type, professional origin, spatial outline, connection endpoints, path boundaries, attribute items, action boundaries, version number, and modification time.

[0103] Furthermore, the object code and object type in the partially modified object record are read, and an object record with the same object code and object type is searched in the object library. The found object record is then used as the object record before modification.

[0104] It should be noted that if the object encoding changes, the object matching precision is called, and the object records in the object library are matched based on the object type, connection endpoints, and spatial outline center distance, without regenerating new matching precision.

[0105] Furthermore, after the matching is completed, the object number that was matched in the object library is read, and the object number is determined as the change object number. The change object number represents the object library record number directly corresponding to the local design modification.

[0106] Furthermore, the object record before modification and the object record after partial modification are read, and the spatial outline, connection endpoints, path boundaries, attribute items, and action boundaries are compared item by item.

[0107] If the spatial outline changes, write the spatial outline to the changed attribute set; if the connection endpoints change, write the connection endpoints to the changed attribute set; if the path boundary changes, write the path boundary to the changed attribute set; if the attribute item changes, write the attribute item to the changed attribute set; if the action boundary changes, write the action boundary to the changed attribute set.

[0108] It should be noted that if a field is empty before modification and remains empty after partial modification, it will not be written to the change attribute set; if a field changes from empty to non-empty or from non-empty to empty, it will be written to the change attribute set; the change attribute set is used to read the trigger attributes in the callable gap ledger to ensure that only relationships related to this modification enter the pending process.

[0109] Furthermore, based on the changed object number, the object record before modification, the object record after partial modification, and the set of changed attributes, a change domain is generated. The change domain represents the comprehensive impact range of the partial design modification on space, connection, path, attribute, and action boundaries.

[0110] Specifically, the change domain is represented as:

[0111] ;

[0112] in, Representation Object Change domain, Indicates a change to the object number. Representation Object The original spatial outline Representation Object The spatial outline after partial modification, superscript This indicates that after partial design modifications, Representation Object The swept area is formed by moving from the original spatial outline to the partially modified spatial outline. This indicates that the object number has been changed. The path boundary perturbation set of the object, which is generated by the difference between the path boundary before modification and the path boundary after local modification. Representation Object The set of connection perturbations is generated by the differences between the connection endpoints before modification and the connection endpoints after local modification. Representation Object The set of attribute perturbations is generated by the differences between the attribute items before modification and the attribute items after local modification. Representation Object The set of action perturbations is generated by the difference between the action boundary before modification and the action boundary after local modification.

[0113] It should be noted that the change domain is a set of fractal perturbations, including spatial outline, swept region, path boundary perturbation set, connection perturbation set, attribute perturbation set, and action perturbation set. These correspond to fields in the object library that can trigger changes in constraint relationships. Different types of changes are stored separately in the change domain.

[0114] Local design modifications may only change the object's location, or they may change connection endpoints, path boundaries, attribute items, or action boundaries. The collection structure can organize the differences of different fields into the same change domain, allowing the callable gap ledger to read the corresponding changed parts according to the relationship type and trigger attribute, avoiding the omission of path relationships, capacity relationships, grounding relationships, communication relationships, construction action relationships, and operation and maintenance action relationships due to judgment based solely on the spatial outline. The change domain retains the spatial outline before modification, the spatial outline after local modification, and the swept area, and can simultaneously record the object's original occupied range, the occupied range after modification, and the range affected by the movement process, so that the penetration value calculation is performed separately according to the spatial outline, path boundary, connection endpoint, attribute item, and action boundary.

[0115] It should be noted that if the set of changed attributes does not contain a certain field, then the corresponding records in the changed domain will be empty.

[0116] Based on the changed object number and the set of changed attributes, the callable gap ledger is read, and a set of relationships to be judged and a set of existing abnormal relationships are generated according to the relationship status. Based on the change domain and the constraint scope, the penetration value is calculated, and the penetrated relationships are filtered. According to the penetrated relationships, the actual quantity after local modification, the demand quantity after local modification, and the gap quantity after local modification are recalculated. The penetrated relationships are identified as verification relationships or boundary-breaking relationships, and a set of verification relationships, a set of boundary-breaking relationships, and a set of objects to be repaired are generated.

[0117] Furthermore, based on the changed object number and the changed attribute set, the set of relationships to be judged and the set of existing abnormal relationships are read from the callable gap ledger.

[0118] Specifically, the reading rules are as follows: if the starting object number or ending object number in the ledger record is equal to the changed object number, the triggering attribute in the ledger record belongs to the changed attribute set, and the relationship state in the ledger record is a consumable relationship, then the ledger record is written as a relationship record to be judged into the relationship set to be judged; if the starting object number or ending object number in the ledger record is equal to the changed object number, the triggering attribute in the ledger record belongs to the changed attribute set, and the relationship state in the ledger record is an existing abnormal relationship, then the ledger record is written into the existing abnormal relationship set; if the triggering attribute in the ledger record does not belong to the changed attribute set, then it is not read.

[0119] It should be noted that local design modifications only trigger relevant relationships to avoid invalid propagation due to multiple relationships for the same object; the existing abnormal relationship set is not used as the starting point for normal gap propagation, but is used to generate associated existing abnormal relationships and correction content.

[0120] Furthermore, for each record of a relation to be judged in the set of relations to be judged, the constraint scope, relation type, and triggering attribute in the callable gap ledger are read, and the changed part that matches the relation type and triggering attribute is selected from the changed domain as the changed subdomain participating in the penetration calculation; the penetration value is used to characterize the proportion of the changed subdomain entering the constraint scope.

[0121] Specifically, the penetration value is expressed as:

[0122] ;

[0123] ;

[0124] in, Representing relations The penetration value of the modified subdomain ranges from zero to one. Representing relations The scope of the constraint Representation Object Relative Relationship Penetration indication, This represents the measure element within the constraint scope, and the measure element is determined according to the relation. The triggering attribute is determined as a position element, path length element, connection endpoint item, attribute item, or action boundary space element. Representation Object Changes in the domain and relationships Changes to subdomains that match the relationship type and triggering attribute. Representing relations The constraint scope uses a fractal measure. Representing relations In the scope of constraint and The corresponding metric element.

[0125] It should be noted that the changed subdomain is jointly defined by the relationship type of the relation to be judged and the triggering attribute; when the triggering attribute is the spatial outline, the changed subdomain takes the spatial outline change area formed by the spatial outline before modification, the spatial outline after partial modification, and the swept area, and calculates the penetration ratio according to the spatial volume; when the triggering attribute is the path boundary, the changed subdomain takes the path boundary disturbance set and calculates the penetration ratio according to the path length; when the triggering attribute is the connection endpoint, the changed subdomain takes the connection disturbance set and calculates the penetration ratio according to the number of connection endpoints; when the triggering attribute is the attribute item, the changed subdomain takes the attribute disturbance set and calculates the penetration ratio according to the number of attribute fields that have changed; when the triggering attribute is the action boundary, the changed subdomain takes the action disturbance set and calculates the penetration ratio according to the spatial volume occupied by the action boundary.

[0126] When the path boundary is a polyline path, the path length is calculated cumulatively based on the lengths of line segments between adjacent path inflection points under the engineering coordinate reference; connection endpoints are counted after deduplication based on endpoint numbers; attribute fields are counted after deduplication based on field items composed of attribute names and attribute values; action boundaries are calculated based on the changed space portions among transportation space, hoisting space, commissioning space, maintenance space, and expansion reserved space. The penetration value is the normalized proportion within the same pending relationship, used to determine whether the pending relationship enters the clearance recalculation process.

[0127] When the fractal measure value of the constraint scope is zero, the penetration value is not calculated, and the constraint scope is regenerated after returning to the relation type confirmation. When the penetration value is equal to zero, the relation record to be judged is marked as a non-penetrated relation. When the penetration value is greater than zero, the relation record to be judged is marked as a penetrated relation.

[0128] The penetration indicator uses 1 and zero to distinguish whether the metric element in the constraint scope belongs to the changed subdomain. It can convert spatial overlap, path disturbance, endpoint change, attribute change, and action boundary change into penetration judgment under the corresponding trigger attribute. When the trigger attribute is spatial outline, the constraint scope uses volume measurement; when the trigger attribute is path boundary, the constraint scope uses length measurement; when the trigger attribute is connection endpoint, the constraint scope uses connection endpoint count measurement; when the trigger attribute is attribute item, the constraint scope uses attribute field count measurement; when the trigger attribute is action boundary, the constraint scope uses the space volume measurement occupied by the action boundary. A penetration value of zero indicates that the changed subdomain has not entered the constraint scope; a penetration value greater than zero indicates that the changed subdomain has entered the constraint scope, and the pending relationship record enters the clearance recalculation process.

[0129] It should be noted that the penetration value is the normalized percentage within the same relationship to be judged.

[0130] Furthermore, for relationships that have been penetrated, the quantity class, relationship type, actual quantity before modification, required quantity before modification, and remaining quantity before modification in the callable gap ledger are read. Based on the object records after the partial modification, the actual quantity and required quantity after the partial modification are recalculated.

[0131] It should be noted that when the quantity is a distance quantity, the actual distance after local modification is calculated based on the spatial outline, connection endpoints, or support boundaries after local modification, and the minimum allowable distance after local modification is determined based on the source of the demand. When the quantity is a capacity quantity, the available capacity and the demand after local modification are calculated based on the path boundaries, channel capacity, and occupancy after local modification. When the quantity is a path quantity, the actual path length after local modification is calculated based on the connection endpoints and path boundaries after local modification, the allowable path length is read, and the allowable path length is used as the actual quantity after local modification. The actual path length after local modification is also used as the demand after local modification, so that the clearance after local modification is equal to the allowable path length minus the actual path length after local modification. When the quantity is a motion space quantity, the available motion space and the required motion space after local modification are calculated based on the motion boundaries and the occupied range of adjacent objects after local modification.

[0132] Furthermore, the locally modified clearance amount is generated, and the locally modified clearance amount is expressed as:

[0133] ;

[0134] in, Representing relations The clearance amount after local modification Representing relations The actual quantity after partial modification Representing relations The demand after partial modification.

[0135] It should be noted that the clearance amount after local modification adopts the difference structure of the clearance amount before modification, ensuring that the clearance amount before modification and the clearance amount after local modification have the same dimensions, the same discrimination direction, and the same relational state criteria. After local design modification, both the actual amount and the required amount may change with the spatial outline, connection endpoints, path boundaries, attribute items, or action boundaries. Subtracting the required amount after local modification from the actual amount after local modification can directly reflect the degree of consumption of consumable margin due to local design modification.

[0136] When the clearance after local modification is greater than or equal to the clearance before modification, the local design modification has not compressed the clearance of the relationship to be judged; when the clearance after local modification is greater than or equal to zero and less than the clearance before modification, although the relationship to be judged still meets the demand, a verification relationship that needs to be tracked has been formed; when the clearance after local modification is less than zero, the relationship to be judged has exceeded the demand and formed a boundary-breaking relationship; through comparison of the difference in the same direction, verification relationships and boundary-breaking relationships are continuously generated by the same discrimination rule.

[0137] It should be noted that a clearance greater than zero after local modification indicates that there is still a margin after the local design modification; a clearance equal to zero after local modification indicates that the local design modification just meets the demand; and a clearance less than zero after local modification indicates that the local design modification exceeds the demand.

[0138] Furthermore, the system reads the clearance amount before and after the local modification of the relationship to identify the relationship category.

[0139] Furthermore, the remaining gap amount before and after the local modification of the relationship is read to determine whether the penetrated relationship has entered the subsequent set.

[0140] Specifically, when the remaining gap after local modification is greater than or equal to the remaining gap before modification, the penetrated relationship is not written into the set of verification relationships, the set of boundary-breaking relationships, and the set of objects to be repaired, and does not enter the boundary-breaking propagation and correction process; when the remaining gap after local modification is greater than or equal to zero and less than the remaining gap before modification, the relationship is marked as a verification relationship and written into the set of verification relationships; when the remaining gap after local modification is less than zero, the relationship is marked as a boundary-breaking relationship and written into the set of boundary-breaking relationships, and at the same time, the other end of the boundary-breaking relationship is written into the set of objects to be repaired; if the changed object number is equal to the starting object number in the boundary-breaking relationship, then the other end object is the ending object number; if the changed object number is equal to the ending object number in the boundary-breaking relationship, then the other end object is the starting object number.

[0141] It should be noted that the already penetrated relationship that satisfies the condition that the clearance amount after local modification is greater than or equal to the clearance amount before modification is only retained in the callable clearance ledger as a ledger record for completing the penetration judgment. It does not form a relationship set and does not participate in the repair list, correction domain, correction content, or correction closure check.

[0142] Furthermore, for boundary-breaking relationships, a breakthrough degree is generated, which is expressed as:

[0143] ;

[0144] in, Representing relations The degree of breakthrough is defined as a value greater than zero and less than or equal to one. Representing relations The amount of clearance reduction.

[0145] It should be noted that the degree of breakthrough is measured by the ratio of the clearance reduction amount to the clearance amount before modification and the clearance reduction amount together, which measures the severity of the boundary relationship changing from a consumable relationship to a boundary relationship. The clearance reduction amount reflects the margin consumed by the local design modification, while the clearance amount before modification reflects the original margin of the relationship. The two together as the denominator can simultaneously reflect the original bearing capacity of the relationship and the impact caused by the local design modification.

[0146] The degree of breakthrough is calculated only when the clearance amount before the modification is greater than or equal to zero and the clearance amount after the local modification is less than zero. The denominator is greater than zero, and the numerical range is greater than zero and less than or equal to one. The closer the degree of breakthrough is to one, the stronger the boundary-breaking impact of the local design modification relative to the original consumable margin. When locking the candidate responsible discipline, the related boundary-breaking relationships with greater boundary-breaking impact can be dealt with first.

[0147] It should be noted that the breakthrough degree is only applied when the clearance amount before modification is greater than or equal to zero and the clearance amount after local modification is less than zero, so the denominator is greater than zero; the breakthrough degree is used to determine the professional responsibility between the boundary relationships of different quantity categories.

[0148] Based on the set of boundary-breaking relationships and the set of objects to be repaired, a change-bearing domain is generated. Objects to be repaired that have been added to the set of objects to be repaired but have not yet participated in the propagation are used as objects to be propagated in the next round. The callable gap ledger is reread and the penetration value is calculated. The set of review relationships, the set of boundary-breaking relationships, the set of existing abnormal relationships, and the set of objects to be repaired are updated until no more new boundary-breaking relationships are generated.

[0149] Furthermore, when a new boundary-breaking relationship is added to the boundary-breaking relationship set, a change domain is generated for the newly added object to the object to be repaired set, and the change continues to propagate.

[0150] Specifically, the domain of change acceptance is jointly generated by the constraint domain of the boundary breaking relationship and the spatial outline, connection endpoints, path boundaries, attribute items, and action boundaries of the object to be repaired in the object library.

[0151] When the quantity class is a distance quantity, it inherits the overlapping part of the constraint domain of the boundary breaking relationship of the change domain and the spatial outline of the object to be repaired; when the quantity class is a capacity quantity, it inherits the overlapping part of the constraint domain of the boundary breaking relationship of the change domain and the path boundary and capacity-related attribute items of the object to be repaired; when the quantity class is a path quantity, it inherits the overlapping part of the constraint domain of the boundary breaking relationship of the change domain and the connection endpoint and path boundary of the object to be repaired; when the quantity class is an action space quantity, it inherits the overlapping part of the constraint domain of the boundary breaking relationship of the change domain and the action boundary of the object to be repaired.

[0152] Furthermore, newly added objects to the set of objects to be repaired but not yet involved in propagation are taken as objects to be propagated in the next round. The ledger records that are connected to the objects to be propagated in the next round and trigger attribute matching to inherit the change domain are read from the callable gap ledger. The set of relationships to be judged and the set of existing abnormal relationships are distinguished according to the relationship status. Ledger records with the relationship status of consumable relationship are written as records to be judged in the set of relationships to be judged, and ledger records with the relationship status of existing abnormal relationship are written into the set of existing abnormal relationships.

[0153] Furthermore, for each record of a relationship to be judged in the newly added set of relationships to be judged, the penetration value calculation, the generation of residual gap after local modification, and the relationship category identification are repeatedly performed according to the rules of changing subdomains and classification measures.

[0154] It should be noted that the next round of propagation targets newly added to the set of objects to be repaired but not yet participating in the propagation; objects to be repaired that have already participated in the propagation will not be repeatedly used as objects to be propagated in the next round to avoid closed relationships causing a cycle; propagation will stop when no new boundary-breaking relationships are added in the current round of propagation.

[0155] Furthermore, after the propagation stops, organize the set of boundary-breaking relationships, the set of verification relationships, the set of existing abnormal relationships, and the set of objects to be repaired.

[0156] The set of boundary-breaking relationships includes relationship number, starting object number, ending object number, relationship type, quantity class, triggering attribute, constraint scope, actual quantity before modification, actual quantity after partial modification, required quantity before modification, required quantity after partial modification, remaining gap quantity before modification, remaining gap quantity after partial modification, degree of breakthrough, unit of required quantity, source of required quantity, candidate responsible profession, version number, and modification time.

[0157] The set of relationships to be reviewed includes the relationship number, starting object number, ending object number, relationship type, quantity class, trigger attribute, remaining gap before modification, remaining gap after partial modification, unit of demand, source of demand, version number, and modification time.

[0158] The existing abnormal relationship set includes relationship number, starting object number, ending object number, relationship type, quantity class, triggering attribute, constraint scope, actual quantity before modification, required quantity before modification, clearance quantity before modification, relationship status, required quantity unit, required quantity source, responsible professional candidate, version number, and modification time.

[0159] The set of objects to be repaired includes the object number, the trigger boundary violation relationship number, the object name, the object code, the object type, the professional source, the spatial outline, the connection endpoints, the path boundaries, the attribute items, the action boundaries, the version number, and the modification time.

[0160] It should be noted that the propagation is based on whether the changed subdomain penetrates the constraint scope and whether the clearance amount after local modification breaks the boundary, so that local modifications in the multi-disciplinary collaborative design of power grid engineering can automatically locate and verify relationships, boundary-breaking relationships, existing abnormal relationships and objects to be repaired.

[0161] S4. Based on the set of review relationships, the set of boundary-breaking relationships, the set of existing abnormal relationships, and the set of objects to be repaired, establish a list of objects to be repaired, determine the attributes to be modified, generate the correction domain and correction content, lock the responsible profession, write back to the object library, update the callable gap ledger, and trigger the correction closure verification.

[0162] Based on the set of boundary-breaking relationships, the set of review relationships, the set of existing abnormal relationships, and the set of objects to be repaired, the object fields are extracted from the associated object library to establish a list of objects to be repaired, and associated boundary-breaking relationships, associated review relationships, and associated existing abnormal relationships are generated. According to the list of objects to be repaired, the associated boundary-breaking relationships and trigger attributes are read to determine the attributes to be modified. Based on the callable gap ledger, the maintenance relationship is read to generate a tunable base domain.

[0163] Furthermore, it receives the set of boundary-breaking relationships, the set of review relationships, the set of existing abnormal relationships, and the set of objects to be repaired. It reads the object number to be repaired from the set of objects to be repaired and extracts the object name, object code, object type, professional source, spatial outline, connection endpoint, path boundary, attribute item, action boundary, version number, and modification time corresponding to the object number to be repaired from the object library.

[0164] Furthermore, read the relationships connected to the object number to be repaired in the boundary-breaking relationship set to form associated boundary-breaking relationships; read the relationships connected to the object number to be repaired in the review relationship set to form associated review relationships; read the relationships connected to the object number to be repaired in the existing abnormal relationship set to form associated existing abnormal relationships.

[0165] Furthermore, the object number, object name, object code, object type, professional source, related boundary crossing relationship, related review relationship, and related existing abnormal relationship are written into the repair list.

[0166] Furthermore, for each object in the repair list, read the trigger attribute from the associated boundary breaking relationship.

[0167] Specifically, when the triggering attribute is the spatial outline, the spatial outline is determined as the attribute to be modified; when the triggering attribute is the connection endpoint, the connection endpoint is determined as the attribute to be modified; when the triggering attribute is the path boundary, the path boundary is determined as the attribute to be modified; when the triggering attribute is the attribute item, the attribute item is determined as the attribute to be modified; and when the triggering attribute is the action boundary, the action boundary is determined as the attribute to be modified.

[0168] It should be noted that if the same object to be modified corresponds to multiple boundary-breaking relationships, and the multiple boundary-breaking relationships correspond to different trigger attributes, then all fields corresponding to the multiple trigger attributes will be written into the attribute to be modified.

[0169] Furthermore, the system reads the spatial outline, connection endpoints, path boundaries, attribute items, and action boundaries of the object to be repaired in the object library, and reads the relationships in the callable gap ledger that are directly connected to the object to be repaired but have not entered the set of boundary-breaking relationships to form a maintenance relationship.

[0170] Furthermore, an adjustable base domain is generated based on the preservation relation. The adjustable base domain is used to restrict the correction action from violating the preservation relation.

[0171] Specifically, when the attribute to be modified is a spatial outline, the location range that allows the clearance relationship, support relationship, oil drainage relationship, construction action relationship, and operation and maintenance action relationship to still meet the demand is retained, forming an adjustable base domain for the spatial outline; when the attribute to be modified is a connection endpoint, the endpoint range that allows the grounding relationship, communication relationship, and path relationship to still meet the demand is retained, forming an adjustable base domain for the connection endpoint; when the attribute to be modified is a path boundary, the path range that allows the path relationship and capacity relationship to still meet the demand is retained, forming an adjustable base domain for the path boundary; when the attribute to be modified is an attribute item, the attribute value range that allows the capacity relationship, support relationship, path relationship, or action relationship to still meet the demand is retained, forming an adjustable base domain for the attribute item; when the attribute to be modified is an action boundary, the action space range that allows the construction action relationship and operation and maintenance action relationship to still meet the demand is retained, forming an adjustable base domain for the action boundary.

[0172] Furthermore, the adjustable base domain is determined in reverse based on the maintenance relationship. Specifically, for each attribute to be modified of the object to be repaired, the maintenance relationships connected to the object to be repaired but not included in the set of boundary breaking relationships or the set of verification relationships are read. According to the quantity type, triggering attribute, demand quantity, and demand quantity unit of the maintenance relationship, the allowable value range that makes the corrected clearance quantity greater than or equal to zero is calculated in reverse. The intersection of all allowable value ranges corresponding to the same object to be repaired is taken to obtain the adjustable base domain.

[0173] Based on the adjustable base domain, the associated boundary breaking relationship, and the associated verification relationship, the boundary breaking limit domain and the verification maintenance domain are generated, and the correction domain is synthesized. Based on the correction domain and the associated existing abnormal relationship, the single object correction content or joint correction content is generated. Combining the responsible professional candidate and professional source, the responsible professional is locked, the object library is partially written back, the callable gap ledger is updated, the correction closure verification is triggered, and the correction closure verification record is generated.

[0174] Furthermore, the associated boundary-breaking relationships in the list of objects to be repaired are read, and boundary-breaking constraint domains are generated according to the quantity class of the associated boundary-breaking relationships. The boundary-breaking constraint domains are used to restore the relationships that have been broken, and together with the adjustable base domains, they limit the scope of implementable corrections for the objects to be repaired.

[0175] Specifically, when the quantity is a distance quantity, the spatial outline of the object at the other end of the boundary-breaking relationship is used as a reference to generate a position range that ensures the corrected actual distance is not less than the corrected required quantity; when the quantity is a capacity quantity, the channel range or capacity adjustment range that ensures the corrected available capacity is not less than the corrected required quantity is generated based on the path boundary, channel capacity, and occupancy; when the quantity is a path quantity, the path range that ensures the corrected actual path length does not exceed the allowed path length and the corrected clearance is greater than or equal to zero is generated based on the connection endpoints and path boundaries; when the quantity is a motion space quantity, the space range that ensures the corrected available motion space is not less than the corrected required quantity is generated based on the motion boundary and the occupancy range of adjacent objects.

[0176] Furthermore, the associated review relationships in the list of pending repairs are read, and a review retention field is generated according to the quantity category of the associated review relationship. The review retention field is used to prevent the continued compression of relationships that have not yet broken the boundary when correcting a boundary-breaking relationship.

[0177] Specifically, when the quantity is a distance quantity, the verification and retention domain is the position range where the corrected distance clearance no longer decreases; when the quantity is a capacity quantity, the verification and retention domain is the channel range or capacity range where the corrected available channel capacity no longer decreases; when the quantity is a path quantity, the verification and retention domain is the path range where the corrected actual path length does not exceed the allowed path length and the corrected path clearance is greater than or equal to zero; when the quantity is a motion space quantity, the verification and retention domain is the space range where the corrected available motion space no longer decreases.

[0178] It should be noted that if the object to be repaired does not have an associated verification relationship, no additional restriction range will be generated, and the correction domain will be limited only by the adjustable base domain and the boundary-breaking restriction domain.

[0179] Furthermore, for each object to be modified, the adjustable base domain, the boundary-breaking domain, and the verification and preservation domain are respectively assigned to the allowed value range of the same attribute to be modified, and the allowed value ranges under the same attribute to be modified are intersected to generate the correction domain.

[0180] Specifically, the correction domain is represented as:

[0181] ;

[0182] in, Object to be repaired The correction domain, The item number to be repaired. Object to be repaired The adjustable base domain, Object to be repaired The set of boundary-breaking relationships, Object to be repaired In relation Limiting the boundary of the restricted domain Object to be repaired The set of related verification relationships, For the relation number in the set of related verification relations, Object to be repaired In relation Under constraints, the verification field is preserved, and the symbol is preserved. This indicates finding the intersection within the allowed value range of the same attribute to be modified.

[0183] It should be noted that the correction domain is constructed using the intersection of the adjustable base domain, the boundary-breaking constraint domain, and the verification and preservation domain, which limits the common feasible range within which the object to be corrected can perform the correction content. Among them, the adjustable base domain is derived from the preservation relationship to avoid the correction action from destroying the relationship that has not yet entered the boundary-breaking relationship set; the boundary-breaking constraint domain is derived from the associated boundary-breaking relationship to ensure that the correction action can restore the relationship that has exceeded the demand; and the verification and preservation domain is derived from the associated verification relationship to prevent the correction action from continuing to compress the relationship that has been affected but has not yet broken the boundary.

[0184] The intersection structure enables the corrected content to simultaneously satisfy the constraints of maintaining relationships, associating boundary-breaking relationships, and associating review relationships, avoiding the occurrence of new boundary-breaking propagation caused by restoring only a single boundary-breaking relationship; when the correction domain is empty, the correction content of a single object is insufficient to restore the boundary-breaking relationship, and further joint correction content needs to be generated; when the correction domain is not empty, the object to be corrected has an executable correction scope, and can directly enter the responsibility professional locking, object library write-back, and callable gap ledger update process.

[0185] It should be noted that when the correction domain is empty, it means that modifying the object to be modified alone is insufficient to restore the boundary breach relationship; when the correction domain is not empty, it means that there is an executable correction range for the object to be modified.

[0186] The correction domain formula limits the correction range by the intersection of the adjustable base domain, the boundary-breaking domain, and the core-preserving domain, so that the correction action can simultaneously satisfy the requirements of restoring the boundary-breaking relationship and preserving the core relationship.

[0187] Furthermore, when the correction domain of the object to be repaired is not empty, single-object correction content is generated.

[0188] Specifically, the single-object correction content includes the object number to be corrected, object name, object code, attribute to be modified, correction domain, associated boundary breaking relationship, associated review relationship, associated existing abnormal relationship, actual quantity before modification, actual quantity after partial modification, required quantity before modification, required quantity after partial modification, required quantity unit, required quantity source, degree of breakthrough, version number, modification time, and write-back range.

[0189] When the correction domain of the object to be repaired is empty, read other objects directly connected to the object to be repaired from the set of boundary-breaking relationships, form a joint correction object group, and regenerate the adjustable base domain, boundary-breaking restriction domain, verification and preservation domain, and correction domain based on the joint correction object group; the joint correction object group expands from two objects to be repaired; when there are multiple feasible joint correction object groups, the joint correction object group with the fewest objects to be repaired is selected first; when the number of objects to be repaired is the same, the joint correction object group with the most associated boundary-breaking relationships is selected first; when the number of associated boundary-breaking relationships is still the same, the joint correction object group with the higher object number is selected.

[0190] The joint correction content includes the joint correction object group, the attributes to be modified for each object to be corrected, the joint correction domain, the associated boundary breaking relationship, the associated review relationship, the associated existing abnormal relationship, the source of the demand, and the write-back scope.

[0191] Furthermore, the source of the object to be repaired in the correction content is read, and the candidate responsible professions in the callable gap ledger are read for the related boundary breaking relationship.

[0192] Specifically, if the subject's major origin is a candidate for a responsible major, then the subject's major origin is determined as the responsible major; if the subject's major origin is not a candidate for a responsible major, then the candidate for a responsible major with the most associated boundary-breaking relationships is determined as the responsible major; if multiple candidates for a responsible major have the same number of associated boundary-breaking relationships, then the candidate for a responsible major corresponding to the associated boundary-breaking relationship with the greatest degree of breakthrough is determined as the responsible major.

[0193] It should be noted that when the joint revision involves multiple objects to be revised, the responsible specialty is locked according to the modification attributes of each object to be revised, and the responsible specialty, object number, and write-back scope are recorded in the joint revision.

[0194] Furthermore, after the responsible professional completes the correction, the object database is updated according to the write-back scope in the correction content; the object number to be repaired and the write-back scope in the correction content are read, the object number to be repaired included in the write-back scope is determined as the write-back object number, and the object database record corresponding to the write-back object number in the object database is determined as the write-back object.

[0195] Specifically, when the attribute to be modified is a spatial outline, update the spatial outline, version number, and modification time in the object library; when the attribute to be modified is a connection endpoint, update the connection endpoint, version number, and modification time; when the attribute to be modified is a path boundary, update the path boundary, version number, and modification time; when the attribute to be modified is an attribute item, update the attribute item, version number, and modification time; and when the attribute to be modified is an action boundary, update the action boundary, version number, and modification time.

[0196] It should be noted that object fields not included in the write-back scope will not be modified to avoid overwriting data already confirmed by other disciplines.

[0197] Furthermore, after completing the object library write-back, the ledger records directly linked to the write-back object number in the callable gap ledger are read, and based on the updated object library, the corrected actual quantity, corrected demand quantity, and corrected gap quantity are recalculated.

[0198] It should be noted that for ledger records with the quantity category of path quantity, the corrected actual path length and allowed path length corresponding to the corrected path boundary are read. The allowed path length is used as the corrected actual quantity, and the corrected actual path length is used as the corrected demand quantity, so that the corrected clearance quantity is equal to the allowed path length minus the corrected actual path length.

[0199] If the corrected gap is less than zero, and the ledger record's relation state before being written back to the object database is an existing abnormal relation, then the ledger record's relation state remains an existing abnormal relation, and the ledger record is written to the existing abnormal relation set. If the corrected gap is less than zero, and the ledger record belongs to the boundary-breaking relation set, then the ledger record continues to participate in the correction closure check as a boundary-breaking relation, and the ledger record is written to the unrecovered boundary-breaking relation set. If the corrected gap is greater than or equal to zero, then the ledger record is updated to a consumable relation, and if the ledger record belongs to the boundary-breaking relation set, the ledger record is written to the recovered boundary-breaking relation set.

[0200] Synchronously update the version number and modification time in the ledger record. Based on the updated ledger record, reread the write-back object number, trigger attribute, constraint scope, corrected actual quantity, corrected required quantity, and corrected clearance quantity. Based on the write-back object corresponding to the write-back object number, generate the corrected change domain. Re-determine whether the corrected change domain penetrates the constraint scope. Re-identify the review relationship, unrestored boundary violation relationship, newly added boundary violation relationship, and objects to be repaired.

[0201] If the newly added boundary-breaking relationship set is not empty, then the correction domain and correction content are generated based on the newly added boundary-breaking relationship set and the newly added object set to be repaired, and the object library and callable gap ledger are partially written back according to the correction content; if the newly added boundary-breaking relationship set is empty and the boundary-breaking relationship set is not restored to be empty, then the correction domain and correction content are generated based on the unrestored boundary-breaking relationship set and the object set to be repaired, and the object library and callable gap ledger are partially written back according to the correction content; if the newly added boundary-breaking relationship set is empty and the unrestored boundary-breaking relationship set is empty, then the correction closure check is deemed to have passed, and a correction closure check record is generated.

[0202] It should be noted that the correction closure check sets an upper limit for the number of closure rounds. A closure round represents the continuous processing of generating correction domains and correction content, partially writing back to the object library, updating the callable gap ledger, re-identifying review relationships, unrestored boundary-breaking relationships, newly added boundary-breaking relationships, and objects to be repaired. At the start of the correction closure check, the number of boundary-breaking relationship sets, review relationship sets, and objects to be repaired are read and summed to form the upper limit for the number of closure rounds. When the boundary-breaking relationship set, review relationship set, and objects to be repaired are all empty, the correction closure check is deemed to have passed, a correction closure check record is generated, and no round judgment is performed. When the number of closure rounds reaches the upper limit, or when the number of newly added boundary-breaking relationships, unrestored boundary-breaking relationships, and objects to be repaired generated in two consecutive rounds does not decrease, the generation of correction domains and correction content stops, a correction unclosed record is generated, and the unrestored boundary-breaking relationships, newly added boundary-breaking relationships, objects to be repaired, responsible specialty, upper limit for the number of closure rounds, actual number of closure rounds, and reason for stopping are written into the correction unclosed record.

[0203] The corrected closure verification record includes the write-back object number, the updated relationship number, the restored boundary-breaking relationship, the reviewed relationship, the existing abnormal relationship, the corrected closure status, the upper limit of the closure rounds, the actual closure rounds, the version number, and the modification time; the corrected closure status record is "closure passed"; when the set of unrestored boundary-breaking relationships is not empty or the set of newly added boundary-breaking relationships is not empty, a corrected unclosed record is generated; the corrected unclosed record includes the write-back object number, the updated relationship number, the unrestored boundary-breaking relationship, the newly added boundary-breaking relationship, the object to be repaired, the responsible specialty, the upper limit of the closure rounds, the actual closure rounds, the reason for stopping, the version number, and the modification time.

[0204] Furthermore, simulation experiments were used to verify the effectiveness of this embodiment. Specifically, the simulation test used a general-purpose computer as the running platform, with an eight-core processor, a memory capacity of 32 gigabytes, and a 64-bit operating environment. The simulation test materials included primary design data, secondary design data, civil engineering design data, fire protection design data, grounding design data, construction path data, operation and maintenance space data, and constraint data.

[0205] The primary design data includes main transformers, circuit breakers, disconnect switches, busbars, and structural components; the secondary design data includes protection cabinets, measurement and control cabinets, terminals, and secondary cables; the civil engineering design data includes foundations, roads, ditches, and structures; the fire protection design data includes oil tanks, firewalls, fire lanes, and fire protection facilities; the grounding design data includes grounding grids, grounding down conductors, grounding points, and grounding paths; the construction route data includes transportation routes, hoisting routes, and temporary occupation boundaries; and the operation and maintenance space data includes inspection passages, maintenance extraction spaces, operating spaces, and reserved space for future expansion.

[0206] The constraint data includes constraint name, applicable object type, relationship type, quantity class, triggering attribute, demand quantity, demand quantity unit, demand quantity source, and candidate responsible profession.

[0207] The simulation test uses the same engineering coordinate datum to complete the construction of the object library and constraint library, and generates a callable gap ledger. The object library contains 124 objects, and the callable gap ledger contains 342 relationship records.

[0208] It should be noted that the local design modification takes the main variable object as the object of change, and the modification content includes spatial outline translation, connection endpoint offset, and action boundary expansion. The simulation test sets eight local design modification intensity scenarios, which are numbered in ascending order of modification magnitude as scenario 1 Q1, scenario 2 Q2, scenario 3 Q3, scenario 4 Q4, scenario 5 Q5, scenario 6 Q6, scenario 7 Q7, and scenario 8 Q8. Scenario 6 Q6 is the local design modification intensity scenario number in the simulation test, which represents a local design modification intensity scenario with a spatial translation distance of 0.24 meters, a connection endpoint offset of 0.09 meters, and an action boundary expansion of 0.48 meters. Each local design modification intensity scenario is repeated 30 times, forming a total of 240 simulation records. The simulation test records can call the number of gap ledger relationships, the number of records associated with the changed object number, the number of trigger attribute matching relationships, the number of sets of relationships to be judged, the number of penetrated relationships, the number of sets of reviewed relationships, the number of sets of boundary-breaking relationships, and the average penetration value corresponding to different trigger attributes.

[0209] exist Figure 5 In this study, scenario Q6 is used as a representative scenario to verify the process of changing subdomain penetration screening and relationship orientation identification. Specifically, in scenario Q6, the main variable object undergoes spatial contour translation, connection endpoint offset, and action boundary expansion. The spatial translation distance is 0.24 meters, the connection endpoint offset is 0.09 meters, and the action boundary expansion is 0.48 meters. This can form obvious verification and boundary-breaking relationships without causing all relationships to directly enter the boundary-breaking state. It is suitable as a representative scenario to demonstrate the effect of changing domain penetration screening, gap recalculation, and relationship orientation identification. The callable gap ledger is read according to the changing object number and the changing attribute set. The callable gap ledger contains 342 relationship records. After reading the change object number, 185 relationship records are retained. After filtering by triggering attribute belonging to the changing attribute set, 118 relationship records are formed and enter the set of relationships to be judged.

[0210] Furthermore, the constraint scope, relation type, and triggering attribute corresponding to each relation in the set of relations to be judged are read. Change subdomains that match the relation type and triggering attribute are selected from the change domains. The penetration value formed by the change subdomains entering the constraint scope is calculated, and 118 penetrated relations are obtained. In thirty repeated simulations, the average number of verified relation sets is about 39, and the average number of initial boundary-breaking relations formed before the boundary-breaking propagation is about 79. Figure 5 In the process, the relationship record is read by association with the changed object number and the attribute matching is triggered to complete the preliminary screening; the sixth scenario Q6 corresponds to Figure 5 In the screening phase, the screening phase is presented in the following order: total number of available gap ledger relationships, number of read relationships, number of trigger attribute matching relationships, number of penetrated relationships, number of reviewed relationships, and number of initial boundary-breaking relationships. In the sixth scenario Q6, all 118 relationships in the set of relationships to be judged are penetrated by the corresponding changed subdomain, forming 118 penetrated relationships. Further, based on the gap amount after the local modification, they are divided into a set of reviewed relationships and a set of boundary-breaking relationships. This indicates that the local design modification did not trigger all ledger relationships. The scope of the impact of the local design modification can be clearly defined by the changed subdomain and the penetration value, and the set of reviewed relationships and the set of boundary-breaking relationships can be identified in a targeted manner.

[0211] exist Figure 6 In this study, eight local design modification intensity scenarios are used to verify the ability of penetration value to quantify the degree to which the changed subdomain enters the constraint domain. Specifically, the local design modification object is the main variable object, and the modification content includes spatial outline translation, connection endpoint offset, and action boundary expansion. The change domain is generated based on the object record before modification and the object record after local modification, and the set of relationships to be judged is read from the callable gap ledger based on the set of change attributes.

[0212] It should be noted that the eight local design modification intensity scenarios refer to eight sets of incremental local design modification inputs set in the simulation test. Each scenario uses the main variable object as the object of change, and the modification content includes spatial outline translation, connection endpoint offset, and action boundary expansion. The eight scenarios are arranged in ascending order of modification magnitude, with the spatial translation distance gradually increasing from 0.04 meters to 0.32 meters, the connection endpoint offset gradually increasing from 0.015 meters to 0.12 meters, and the action boundary expansion gradually increasing from 0.08 meters to 0.64 meters. This is used to observe the changes in penetration value, verification relationship, and boundary breach relationship with modification intensity. The eight scenarios correspond to scenario 1 (Q1) to scenario 8 (Q8) in ascending order of modification magnitude. Scenario 6 (Q6) corresponds to a spatial translation distance of 0.24 meters, a connection endpoint offset of 0.09 meters, and an action boundary expansion of 0.48 meters.

[0213] For each relation in the set of relations to be judged, read the constraint scope, relation type, and triggering attribute. Select the change subdomain from the change domain that matches the relation type and triggering attribute, and calculate the penetration value of the change subdomain into the constraint scope. Figure 6 Curve 1 corresponds to the spatial outline, curve 2 corresponds to the connection endpoint, and curve 3 corresponds to the action boundary; Figure 6 Using spatial translation distance as the abscissa, the continuous variation pattern of the first scenario Q1 to the eighth scenario Q8 is displayed. The first scenario Q1 to the eighth scenario Q8 correspond to spatial translation distances of 0.04 meters, 0.08 meters, 0.12 meters, 0.16 meters, 0.20 meters, 0.24 meters, 0.28 meters and 0.32 meters respectively; the sixth scenario Q6 is the sixth scenario point on the continuous variation curve.

[0214] It should be noted that as the spatial translation distance increases from 0.04 meters to 0.32 meters, the average penetration value corresponding to the spatial outline increases from 0.148 to 0.473, the average penetration value corresponding to the connection endpoints increases from 0.132 to 0.376, and the average penetration value corresponding to the action boundary increases from 0.130 to 0.426; under the sixth scenario Q6, the average penetration value corresponding to the spatial outline is 0.381, the average penetration value corresponding to the connection endpoints is 0.307, and the average penetration value corresponding to the action boundary is 0.342; the sixth scenario Q6 serves as... Figure 5 Representative scenarios of the screening process, and Figure 6 The sixth scenario point forms a corresponding relationship; all three curves increase with the increase of the intensity of local design modification, indicating that the degree to which the modified subdomains matched with the spatial outline, connection endpoints and action boundaries enter the constraint domain increases with the increase of the corresponding modification intensity; Figure 6 The penetration value proves that it can convert the degree of influence of local design modifications on the constraint domain into a recordable value, providing an objective basis for screening penetrated relationships, recalculating the clearance after local modifications, identifying and verifying relationships, and identifying boundary-breaking relationships.

[0215] In summary, this invention generates a change domain, reads the set of relationships to be judged and the set of existing abnormal relationships from the callable gap ledger, calculates the penetration value and recalculates the gap amount after local modification, thereby achieving targeted identification of review relationships, boundary-breaking relationships, existing abnormal relationships and objects to be repaired, and clarifying the scope of impact of local modifications; by establishing a list of objects to be repaired, generating a correction domain and correction content, locking the responsible discipline and triggering the correction closure check, the design modification, responsibility assignment and constraint restoration form a continuous processing chain, improving the consistency, traceability and closure of multi-discipline collaborative design.

[0216] 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 power grid engineering multi-specialty collaborative design method based on data fusion, characterized in that, include: Receive professional design data and constraint data, unify engineering coordinate benchmarks, parse object records, generate action boundaries, perform object merging, and generate object and constraint libraries; Read the object library and constraint library, generate candidate object pairs, obtain the relationship to be established, mark the relationship status, and generate a callable gap ledger; Receive partial design modifications, locate the changed objects, generate change domains, read the set of relationships to be judged and the set of existing abnormal relationships from the callable gap ledger, calculate the penetration value, recalculate the gap amount after partial modifications, identify the verification relationships, boundary-breaking relationships, existing abnormal relationships and objects to be repaired, generate the change domain to accept and perform boundary-breaking propagation, and obtain the set of verification relationships, the set of boundary-breaking relationships, the set of existing abnormal relationships and the set of objects to be repaired; Based on the set of review relationships, the set of boundary-breaking relationships, the set of existing abnormal relationships, and the set of objects to be repaired, a list of objects to be repaired is established, the attributes to be modified are determined, the correction domain and correction content are generated, the responsible profession is locked, the object library is written back, the callable gap ledger is updated, and the correction closure verification is triggered.

2. The data fusion based multi-disciplinary collaborative design method for power grid engineering of claim 1, wherein, The generated action boundary includes: Receive professional design data and constraint data, establish an original data list, and based on the original data list and station area surveying benchmarks, perform coordinate transformation to generate an engineering coordinate dataset; Based on the engineering coordinate dataset, object records are parsed to generate action boundaries.

3. The data fusion based multi-disciplinary collaborative design method for power grid engineering of claim 1, wherein, The generated object library and constraint library include: Based on the same-named engineering control points, calculate the object matching accuracy, perform object merging, and generate an object library; Based on constraint data and object library, type normalization, relation classification, quantity classification, and attribute matching are performed to generate constraint library.

4. The data fusion based multi-disciplinary collaborative design method for power grid engineering of claim 3, wherein, The process of obtaining the relationship to be created includes: Read the object library and constraint library, perform field verification, read constraint items, filter and match the object set, and generate candidate object pairs; Based on candidate object pairs, perform trigger attribute validation and relationship type confirmation to obtain the relationship to be created and the scope of constraints.

5. The multi-disciplinary collaborative design method for power grid engineering based on data fusion as described in claim 1 or 4, characterized in that, The generation of the callable gap ledger includes: Based on the pending account relationships, calculate the actual quantity before modification, the required quantity before modification, and the remaining quantity before modification according to the quantity category, and mark the relationship status. Based on the relational state, write ledger records and perform ledger closure verification to generate a callable gap ledger.

6. The multi-disciplinary collaborative design method for power grid engineering based on data fusion as described in claim 1, characterized in that, The process of receiving partial design modifications, locating the changed object, and generating the change domain includes: Receive partial design modifications, parse and generate object records after partial modifications, and combine with the object library to locate the object records before modification and the changed object number; Based on the object records before modification and the object records after partial modification, the differences in the execution fields of spatial outline, connection endpoints, path boundaries, attribute items, and action boundaries are identified, and a set of changed attributes and a change domain are generated.

7. The multi-disciplinary collaborative design method for power grid engineering based on data fusion as described in claim 6, characterized in that, The identification of verification relationships, boundary-breaking relationships, existing abnormal relationships, and objects to be repaired includes: Based on the changed object number and the set of changed attributes, read the callable gap ledger, generate a set of relationships to be judged and a set of existing abnormal relationships according to the relationship status, calculate the penetration value based on the change domain and the constraint scope, and filter the penetrated relationships; Based on the penetrated relationships, recalculate the actual quantity, the required quantity, and the remaining gap quantity after local modification. Identify the penetrated relationships as verification relationships or boundary-breaking relationships, and generate a set of verification relationships, a set of boundary-breaking relationships, and a set of objects to be repaired.

8. The multi-disciplinary collaborative design method for power grid engineering based on data fusion as described in claim 7, characterized in that, The generation of the change-receiving domain and the execution of boundary-breaking propagation include: Based on the set of boundary-breaking relationships and the set of objects to be repaired, a change-bearing domain is generated. Objects to be repaired that have been added to the set of objects to be repaired but have not yet participated in the propagation are used as objects to be propagated in the next round. The callable gap ledger is reread and the penetration value is calculated. The set of review relationships, the set of boundary-breaking relationships, the set of existing abnormal relationships, and the set of objects to be repaired are updated until no more new boundary-breaking relationships are generated.

9. The multi-disciplinary collaborative design method for power grid engineering based on data fusion as described in claim 8, characterized in that, The determination of the attribute to be modified includes: Based on the set of boundary-breaking relationships, the set of review relationships, the set of existing abnormal relationships, and the set of objects to be repaired, the object fields are extracted from the associated object library to establish a list of objects to be repaired, and associated boundary-breaking relationships, associated review relationships, and associated existing abnormal relationships are generated. Based on the list of items to be repaired, read the associated boundary breaking relationships and trigger attributes, determine the attributes to be modified, read the maintenance relationships based on the callable gap ledger, and generate a tunable base domain.

10. The multi-disciplinary collaborative design method for power grid engineering based on data fusion as described in claim 9, characterized in that, The write-back object library updates the callable gap ledger, triggering a correction closure check, including: Based on the adjustable base domain, the associated boundary breaking relationship, and the associated verification relationship, the boundary breaking domain and the verification preservation domain are generated, and the correction domain is synthesized. Based on the correction domain and associated existing anomaly relationships, generate single-object correction content or joint correction content, combine the responsible professional candidates and professional sources, lock the responsible professional, partially write back to the object library, update the callable gap ledger, trigger correction closure verification, and generate correction closure verification record.

Images