Architectural engineering design collaborative management and control system and method based on organizational structure

Abstract

The invention relates to the technical field of collaborative management, and discloses a building engineering design collaborative management and control system and method based on an organizational structure, which are suitable for enterprise collaborative design scenes of dynamic multi-level organizational structures including companies, branch companies, business departments and the like. The method comprises the following steps: acquiring design change request data to generate a change feature vector; performing breadth-first propagation from a change object by using a graph traversal algorithm, and adaptively identifying an influenced design element set and influence path description along an organization level; an affected department and a potential conflict data element list are inquired in an associated mode, and collaborative management of cross-level organization units is supported. According to the method, conflict risk pre-judgment and visual presentation are carried out before change submission, so that the technical problems that a traditional method cannot pre-judge conflict risks, influence range recognition is incomplete and version conflict resolution efficiency is low are solved, and the method can adapt to collaborative management demand changes caused by company level fission.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of construction engineering design collaborative management, and more particularly to a construction engineering design collaborative management system and method based on an organizational structure. BACKGROUND

[0002] In the field of construction engineering design, large-scale construction projects usually involve collaborative design work of multiple professional departments such as structure, heating, electricity, water supply and drainage. With the expansion of construction engineering enterprises, the organizational structure of the enterprise presents the characteristics of dynamic multi-level, forming a tree-like hierarchical structure from the group company to the branch company, the business department, the design institute and the professional department, and this hierarchical structure will undergo hierarchical fission and adjustment due to factors such as business development, organizational restructuring and project demand. When a designer of a certain professional initiates a design change, the change will affect the design data of other professional departments through the reference dependency relationship between design elements, and these affected departments may belong to different hierarchical organizational units, such as design institutes under different branch companies or professional departments under different business departments. Designers of each professional department may be editing based on the current version, and each department is often distributed in different geographical locations, with time differences in work.

[0003] The existing construction engineering design change management technology mainly adopts a change notification mechanism, that is, after the design change is submitted to the version control system, a change notification is sent to the relevant departments, and the designers of each department judge the impact of the change on the design work of the department, and version comparison and conflict resolution are performed manually.

[0004] However, the above existing technology has the following defects: the traditional design change management only notifies the relevant departments after the change is submitted, and cannot predict the conflict risk before the change is initiated, resulting in frequent version conflicts between the change and other ongoing design work; the identification of the influence range of the change depends on the judgment of human experience, and the indirectly affected professional departments are easily missed; the cross-regional collaboration team cannot communicate and coordinate in real time due to the time difference, and the version conflict resolution depends on manual comparison and manual merging, which is low in efficiency and prone to errors. The above problems seriously affect the efficiency and quality of cross-department collaborative design. SUMMARY

[0005] The present application provides a construction engineering design collaborative management system and method based on an organizational structure, which solves the technical problems of inability to predict conflict risks before the change is initiated, incomplete identification of the influence range of the change and low efficiency of version conflict resolution in related technologies.

[0006] The present application discloses a construction engineering design collaborative management method based on an organizational structure, comprising the following steps:

[0007] Obtain the design change request data to be initiated, extract the change object identifier, change parameter type and change magnitude value, and generate a change feature vector;

[0008] Obtain the reference dependency data between various professional design elements and the changed object, and use the graph traversal algorithm to perform breadth-first propagation from the changed object along the dependency edges to generate a set of design elements containing direct and indirect influences and a description of the influence path of each element.

[0009] The system retrieves the identification of the relevant professional department for each affected design element, obtains the current editing lock status and editor information for each affected design element, and generates a list of affected departments and a list of potentially conflicting data elements.

[0010] The impact urgency score of each affected department is calculated based on the magnitude of the change and the length of the impact path. The semantic correlation between each affected design element and the changed content is calculated based on the list of potential conflict data elements, and a conflict risk level label is generated.

[0011] The conflict risk level is mapped onto the spatial layout data to generate a heat map of change conflict risk, and a graded early warning priority queue is generated according to the impact urgency score.

[0012] The change conflict risk heatmap and the tiered early warning priority queue are output to the change initiator's interface, allowing them to decide whether to submit the change immediately.

[0013] Furthermore, the method of using a graph traversal algorithm to perform breadth-first propagation from the changed object along the dependency edges to generate a set of design elements containing direct and indirect influences, as well as a description of the influence path of each element, includes:

[0014] Query the reference dependency database to find the directed graph structure starting from the changed object. Nodes in the directed graph represent design elements, and directed edges represent the reference dependencies between elements.

[0015] The breadth-first traversal algorithm starts from the node of the changed object and propagates outward layer by layer along the reference dependency edge. The nodes reached in the first layer of traversal are the design elements that are directly affected, while the nodes reached in the second layer and deeper layers are the design elements that are indirectly affected.

[0016] During the traversal, the influence path of each affected design element is recorded. The influence path is the sequence of dependency edges from the changed object to the affected design element.

[0017] When the traversal level exceeds a preset traversal depth threshold, propagation to deeper levels stops. The traversal depth threshold is determined based on the scale and professional complexity of the architectural engineering design project.

[0018] Furthermore, the calculation of the impact urgency score for each affected department based on the magnitude of the change and the length of the impact path includes:

[0019] The change magnitude values ​​are normalized according to parameter type. The original change magnitude value is divided by the typical upper limit of the change magnitude of that parameter type to obtain the normalized dimensionless change magnitude value.

[0020] The urgency score of each affected design element is calculated using the urgency score function. The score is directly proportional to the normalized change magnitude and inversely proportional to the sum of the influence path length and one.

[0021] If the same affected department contains multiple affected design elements, the maximum urgency score of all affected design elements within that affected department shall be taken as the impact urgency score of that affected department.

[0022] Furthermore, the step of calculating the semantic correlation between each affected design element and the changed content based on the potential conflict data element list, and generating conflict risk level labels, includes:

[0023] Get the set of parameter type tags involved in the changed content and the set of parameter type tags involved in the edited content;

[0024] The semantic relevance is calculated using a set similarity coefficient, whereby the semantic relevance is equal to the ratio of the number of elements in the intersection of two sets of parameter type labels to the number of elements in the union of the two sets of parameter type labels.

[0025] When the semantic relevance exceeds a preset threshold, it is marked as a high-risk conflict; otherwise, it is marked as a low-risk conflict. The preset threshold ranges from zero to one.

[0026] Furthermore, the step of mapping conflict risk level labels onto spatial layout data to generate a heatmap of change conflict risks includes:

[0027] Obtain the spatial location attributes of each design element within the scope of the change's impact, including floor, area, and coordinates;

[0028] The conflict risk level is mapped to the corresponding spatial location, and a visual heat map of change conflict risk is generated using a color coding method. High-risk areas are marked with the first color, and low-risk areas are marked with the second color.

[0029] Furthermore, it also includes:

[0030] After receiving the submission confirmation instruction from the initiator of the change, a change warning notification is pushed to each affected department in the tiered warning priority queue. The notification content includes a summary of the change, the impact path, and a suggested response time limit.

[0031] The recommended response time limit is inversely proportional to the impact urgency score, equal to the baseline response time limit divided by the sum of the impact urgency score and the smallest positive number to prevent division by zero. Departments with higher urgency scores have shorter recommended response times.

[0032] Furthermore, it also includes:

[0033] Obtain the design data version updates submitted by each affected department in response to the changes, extract the modification records and modification area identifiers for each version, and generate a version change mapping table;

[0034] Traverse the version change mapping table, perform an intersection operation on the modification area sets of any two versions, and identify version pairs with overlapping modification areas;

[0035] For version pairs with overlapping modification areas, the specific modification content of the overlapping areas is extracted, and the semantic equivalence judgment algorithm is used to analyze whether there is a substantial conflict between the modifications, generating a conflict classification result.

[0036] Furthermore, the step of using a semantic equivalence judgment algorithm to analyze whether there is a substantial conflict in the modification includes:

[0037] If the modifications to the same parameter in two versions are identical within the allowable range of numerical error, they are considered semantically equivalent and belong to non-substantive conflicts.

[0038] If the modifications in the two versions are merely formatting adjustments or comment changes, they are considered semantically equivalent and thus not subject to substantial conflict.

[0039] If the two versions have numerical contradictions in their modification results for the same parameter, they are judged to be semantically inequivalent, which constitutes a substantial conflict.

[0040] The allowable error range of the numerical value is determined according to the parameter type. For size parameters, it is an integer multiple of the design accuracy; for angle parameters, it is a preset angle error value; and for scale parameters, it is a preset percentage of the parameter value.

[0041] Furthermore, it also includes:

[0042] For non-substantive conflicts, a predefined merge rule library is retrieved, and the corresponding merge rule is matched according to the conflict type to execute automatic merge, generate the merged version, and record the merge log.

[0043] The merging rules include rules based on the latest submission and rules based on the higher numerical precision.

[0044] The method for determining the numerical precision based on the higher precision is as follows: compare the number of significant digits in the numerical parameters of the two versions, and the version with more significant digits is determined to have higher numerical precision; if the number of significant digits is the same, then compare the number of digits after the decimal point, and the version with more decimal digits is determined to have higher numerical precision.

[0045] For substantive conflicts, a conflict details report is generated and sent to the relevant designers for manual adjudication. The conflict details report includes the design element identifier of the conflict location, the parameter fields involved in the conflict, and a comparison of the modifications in each version.

[0046] This invention also discloses a collaborative management and control system for architectural engineering design based on organizational structure, used to execute the above-mentioned collaborative management and control method for architectural engineering design based on organizational structure, comprising:

[0047] The organizational structure management module is used to maintain a dynamic, multi-level, tree-like organizational structure that includes companies, branches, business units, and professional departments. It supports adding, splitting, merging, and adjusting the hierarchy of organizational units, and updates the hierarchical relationship data in real time when the organizational structure undergoes fission.

[0048] The change request processing module is used to acquire design change request data and generate change feature vectors;

[0049] The impact scope analysis module is used to perform a graph traversal algorithm based on reference dependency data and organizational hierarchy relationship data to generate a set of affected design elements and their corresponding cross-level organizational unit information;

[0050] The conflict risk assessment module is used to calculate the impact urgency score and semantic relevance and generate conflict risk level labels.

[0051] The visualization and early warning module is used to generate a heatmap of change conflict risks and a tiered early warning priority queue, and output them to the user interface.

[0052] The version conflict resolution module is used to detect version conflicts and perform semantic equivalence judgment and automatic merging.

[0053] The beneficial effects of this invention are as follows: This invention employs a breadth-first propagation traversal algorithm based on a dependency graph to automatically identify the scope of change impact. It can adaptively track the propagation path of impact across levels and organizational units along a dynamic multi-level organizational structure (company, branch, business unit, etc.). It uses a change conflict risk heatmap to visualize conflict risks before change submission, introduces an impact urgency scoring mechanism and a tiered early warning priority queue to achieve differentiated notification responses, and uses a semantic equivalence judgment algorithm to distinguish between substantive and non-substantive conflicts and automatically merges non-substantive conflicts. This solves the technical problems in traditional architectural engineering design change management methods, such as the inability to predict conflict risks before change initiation, reliance on manual experience in identifying the scope of change impact which may overlook indirectly affected professional departments, and low efficiency in resolving version conflicts in cross-time zone collaboration. It achieves the technical effects of improving the completeness of change impact scope identification, enabling advance prediction of conflict risks, and enhancing the efficiency of cross-departmental and cross-level collaborative design. Furthermore, the organizational structure association mechanism of this invention can adapt to enterprise hierarchical fission and dynamic adjustments. When the organizational structure is split, merged, or reorganized, the system can automatically update the impact scope analysis and notification routing strategy. Attached Figure Description

[0054] Figure 1 This is an overall flowchart of the method of the present invention;

[0055] Figure 2 This is a sub-flowchart of step 400 of the present invention, which calculates the impact of urgency score and semantic relevance.

[0056] Figure 3 This is a sub-flowchart of step 900 of the present invention, which involves detecting version conflicts.

[0057] Figure 4 This is a sub-flowchart of step 1000, conflict handling, of the present invention; Detailed Implementation

[0058] In the field of architectural engineering design, when a designer initiates a design change (such as adjusting the height of a structural beam), the change affects the design data of multiple professional departments through reference dependencies. Designers in each professional department may be editing based on the current version, and these departments are often located in different geographical locations with different working hours. Traditional design change management only notifies relevant departments after the change is submitted, making it impossible to anticipate conflict risks before initiation. This leads to frequent version conflicts between changes and other ongoing design work. Identifying the scope of change impact relies on manual experience, which can easily overlook indirectly affected professional departments. Cross-regional collaborative teams cannot communicate and coordinate in real time due to time differences, and version conflict resolution relies on manual comparison and merging, which is inefficient and prone to errors, seriously affecting cross-departmental collaboration efficiency.

[0059] The implementation of this method relies on a collaborative management and control system environment for architectural engineering design. This environment includes a design data storage server, a database of design element reference dependencies, user terminal devices, and network communication facilities. The reference dependencies between various professional design elements are stored in the database in a directed graph structure, where nodes represent design elements and directed edges represent the reference dependencies between elements.

[0060] The method of this embodiment includes the following steps;

[0061] Step 100: Obtain the design change request data to be initiated, extract the change object identifier, change parameter type and change magnitude value, and generate a change feature vector.

[0062] Specifically, when a designer initiates a design change operation on the terminal interface, the system parses the unique identifier of the changed object (such as the design element number), the types of parameters involved in the change (such as dimensional parameters, material parameters, location parameters, etc.), and the magnitude of the change (such as the amount of dimensional change) from the change request data. The system encodes the above information into a change feature vector, which is used for subsequent impact range analysis and conflict risk assessment.

[0063] Furthermore, the encoding method for the change feature vector is as follows: the change object identifier is encoded as an integer index value, the parameter type is encoded as a predefined type code (such as size parameter encoded as 1, material parameter encoded as 2, and position parameter encoded as 3), and the change magnitude value is directly used as a numerical component. The three are concatenated in sequence to form the change feature vector.

[0064] In a commercial complex architectural design project, structural engineer Zhang initiated a design change request on the terminal interface, proposing to adjust the beam height of the main beam BM-3F-001 in the third-floor area from 600mm to 700mm. The original data extracted by the system from the change request is shown in the table below:

[0065] Table 1. Original data for the change request;

[0066]

[0067] The system maps the changed object identifier "BM-3F-001" to the design element index library, obtaining the integer index value 1024; it encodes the dimensional parameter type as 1; and the change magnitude of 100mm is directly used as a numerical component. The system generates the change feature vector as follows: .

[0068] Step 200: Obtain the reference dependency data between each professional design element and the changed object, and use the graph traversal algorithm to perform breadth-first propagation from the changed object along the dependency edges to generate a set of design elements containing direct and indirect influences and a description of the influence path of each element.

[0069] Specifically, the system queries the dependency database for the directed graph structure starting from the changed object. Using a breadth-first search algorithm, it propagates outwards layer by layer along the dependency edges, starting from the changed object node. Nodes reached in the first layer are directly affected design elements, while nodes reached in the second and deeper layers are indirectly affected design elements. During the traversal, the influence path of each affected design element is recorded, i.e., the sequence of dependency edges traversed from the changed object to the affected design element. After the traversal is complete, a set of affected design elements and corresponding influence path description data are generated.

[0070] The aforementioned breadth-first traversal algorithm takes as input the node identifiers of the changed object and the directed graph of reference dependencies, and outputs as the set of affected design elements and the sequence of influence paths from the changed object to each affected design element.

[0071] In this embodiment of the application, in order to avoid performance problems caused by infinite depth traversal, a threshold can be set for the traversal depth. When the traversal level exceeds the threshold, the propagation to a deeper level will stop, and the "exceeding the tracking depth" mark will be marked in the description of the affected path.

[0072] Furthermore, the traversal depth threshold is determined based on the scale and professional complexity of the architectural engineering design project, ranging from 3 to 10 layers. For general architectural engineering design projects, the traversal depth threshold can be set to 5 layers, which can cover the dependency propagation links of most cross-disciplinary design elements.

[0073] The system starts with the main beam BM-3F-001, queries the directed graph structure from the dependency database, and performs a breadth-first traversal, with a traversal depth threshold set to 5 levels. The traversal results show that this main beam change will affect the ductwork layout for HVAC systems, the cable tray routing for electrical systems, and the pipe elevations for plumbing systems. The affected design elements and their impact paths are shown in the table below:

[0074] Table 2. Affected Design Elements and Impact Paths

[0075]

[0076] As shown in Table 2, although the change was initiated by the Structural Design Institute under the Architectural Design Division, the affected design elements all belong to the various professional departments under the Mechanical and Electrical Design Division, reflecting the characteristics of cross-divisional impact propagation. Step 300: Based on the set of affected design elements, query the professional department identifier to which each affected design element belongs, and obtain the current editing lock status and editor information of each affected design element, generating a list of affected departments and a list of potential conflicting data elements that are currently being edited.

[0077] Specifically, based on the identifiers of each affected design element in the set of affected design elements, the system queries the affiliation table between design elements and professional departments, as well as the organizational structure hierarchy table, to obtain the identifier of the professional department to which each affected design element belongs and its superior organizational unit (such as business unit, branch office, etc.), and summarizes and generates a list of affected departments containing organizational hierarchy information. Simultaneously, the system queries the edit lock status records of each affected design element, identifies affected design elements currently being edited and locked by other designers, extracts the corresponding editor identifier and lock time information, and generates a list of potentially conflicting data elements.

[0078] The system queries the design element ownership table and organizational structure hierarchy table, and the generated list of affected departments includes: HVAC Design Department, Electrical Design Department, and Water Supply and Drainage Design Department under the Mechanical and Electrical Design Division. This result indicates that this change involves cross-divisional collaboration and requires coordination between the Architectural Design Division and the Mechanical and Electrical Design Division. Simultaneously, the system queries the edit lock status of each affected design element and finds that air conditioning duct AC-3F-002 and cable tray CB-3F-003 are currently in an edit lock state, as shown in the table below:

[0079] Table 3 List of potential conflict data elements

[0080]

[0081] Step 400: Based on the magnitude of the change and the length of the impact path, calculate the impact urgency score for each affected department; based on the list of potential conflict data elements, calculate the semantic correlation between each affected design element and the changed content, and generate conflict risk level labels.

[0082] Step 401: The system obtains the change magnitude value in Step 100 and the impact path length of each affected design element in Step 200, and calculates the urgency score of each affected department using the impact urgency scoring function.

[0083] Because the change magnitude values ​​of different parameter types have different dimensions (e.g., the unit for dimensional parameters is millimeters, and the unit for angular parameters is degrees), the system first normalizes the change magnitude values ​​according to parameter type to eliminate the influence of dimensional differences on the calculation. Specifically, the system pre-sets a typical change magnitude range for each parameter type, and divides the original change magnitude value by the upper limit of the typical change magnitude for that parameter type to obtain the normalized dimensionless change magnitude value. Its value ranges from 0 to 1.

[0084] The input to the aforementioned impact urgency scoring function is the normalized change magnitude value. And affecting path length The output is the urgency score. The calculation formula is:

[0085]

[0086] in This is the normalized change value. To account for the impact path length (i.e., the number of dependent edges traversed from the changed object to the affected design element), 1 is added to the denominator to handle cases where the impact directly affects the design element (path length is 0). The impact urgency scoring function reflects a relationship where the score is directly proportional to the magnitude of the change and inversely proportional to the impact path length; that is, the greater the magnitude of the change and the shorter the impact path, the higher the urgency score. For cases where the same affected department contains multiple affected design elements, the maximum urgency score of all affected design elements within that department is taken as the impact urgency score for that affected department.

[0087] Furthermore, due to The value range is [0,1]. It is a non-negative integer, therefore affecting the urgency score. The value range is (0, 1). (When directly affecting design elements) ,when When it increases Gradually decrease.

[0088] Step 402: The system obtains the currently edited content area information of each affected design element in the potential conflict data element list and calculates the correlation degree with the semantic features of the changed content. If the edited area and the area affected by the change have semantic overlap (such as both involving the dimensional parameters of a structural component), it is marked as a high-risk conflict; if the edited area and the area affected by the change do not have semantic overlap (such as involving independent parameters of different components), it is marked as a low-risk conflict.

[0089] Furthermore, the parameter type tag set is obtained as follows: the system extracts the parameter field names contained in each design element from the metadata records of the design data, maps the parameter field names to a predefined parameter type classification system, and generates the parameter type tag set corresponding to that design element. The parameter type tag set involved in the change content... Obtain the set of parameter type tags involved in the edited content from the changed parameter type parsed in step 100. Retrieved from the edit field information in the edit-locked record.

[0090] The aforementioned semantic relevance calculation uses the Jaccard similarity coefficient, whose input is the set of parameter type tags involved in the changed content. The set of parameter type tags involved in editing content The output is a semantic relevance score. The calculation formula is:

[0091]

[0092] in This indicates the number of elements in the intersection of two sets. This represents the number of elements in the union of two sets. When When the risk exceeds a preset threshold, it is marked as a high-risk conflict; otherwise, it is marked as a low-risk conflict.

[0093] Furthermore, due to the Jaccard similarity coefficient The value range of is [0,1]. When When represents two sets that have no intersection, when This indicates that the two sets are completely identical. The preset threshold value ranges from (0,1), and in the context of collaborative architectural engineering design, the preset threshold can be set to a value between 0.3 and 0.5. and When all are empty sets (i.e.) ),Will Assigning a value of 0 directly marks it as a low-risk conflict.

[0094] The system first normalizes the change range values. The typical upper limit for the change range of dimensional parameters is preset to 500mm. The original change range of 100mm is calculated after normalization. .

[0095] For each affected design element, the system determines the impact path length. Calculate the impact of urgency score Air conditioning duct AC-3F-002 belongs to the first layer and directly affects the design elements, impacting the path length. ,score Cable tray CB-3F-003 belongs to the first layer and directly affects the design elements, influencing the path length. ,score Water supply pipe WP-3F-004 belongs to the second layer of indirect influence design elements, affecting the path length. ,score Each affected department will be assigned the highest score for the affected design element within its department. The urgency score for the HVAC design department is 0.2, for the electrical design department it is 0.2, and for the plumbing design department it is 0.1.

[0096] For potentially conflicting data elements, the system calculates semantic relevance. This includes the set of parameter type tags involved in the changed content. Dimensional parameters, elevation parameters Air conditioning duct AC-3F-002: The set of parameter types and tags involved in the currently edited content. Dimensional parameters, elevation parameters ,calculate The value exceeds the preset threshold of 0.4, and is marked as a high-risk conflict. The current editing content for cable tray CB-3F-003 involves the following parameter type tag set. Material parameters ,calculate If the value is below the threshold, it is marked as a low-risk conflict.

[0097] Table 4. Conflict Risk Assessment Results;

[0098]

[0099] Step 500: Map the conflict risk level label to the spatial layout data of the scope of impact of the change, generate a heat map of the conflict risk of the change, and generate a graded early warning priority queue according to the impact urgency score.

[0100] Specifically, the system acquires the spatial location attributes (such as floor, area, and coordinates) of each design element within the scope of the change's impact, maps the conflict risk level labels generated in step 400 to the corresponding spatial locations, and generates a visual change conflict risk heatmap using a color coding method (e.g., red for high risk and yellow for low risk). Simultaneously, the system sorts the affected departments from highest to lowest according to their impact urgency scores, generating a tiered early warning priority queue.

[0101] Step 600: Output the change conflict risk heatmap, high-risk area details, and graded warning priority queue to the change initiator's interface, so that they can decide whether to submit the change immediately or coordinate with relevant personnel in the high-risk area first.

[0102] Specifically, the system renders the change conflict risk heatmap generated in step 500 onto the user interface of the change initiator, and lists detailed information about high-risk areas, including the design elements involved, the current editor, and a summary of the edited content. The change initiator can then determine whether it is an appropriate time to submit the change, or choose to first coordinate and communicate with the relevant designers in the high-risk areas.

[0103] Based on step 600, the following steps are also included:

[0104] Step 700: After obtaining the submission confirmation instruction from the initiator of the change, push the change warning notification to each affected department in the hierarchical warning priority queue. The notification content includes a summary of the change, the impact path, and the suggested response time limit.

[0105] Specifically, once the initiator of the change confirms and submits the change, the system pushes warning notification messages to relevant personnel in each affected department in sequence according to the priority queue of the tiered warning system. The notification content includes a summary description of the change operation, an explanation of the impact path of the affected design elements in the affected department, and a suggested response time limit calculated based on the urgency score of the impact.

[0106] Furthermore, it is recommended to score the response time and the urgency of the impact. They are inversely proportional, and the calculation formula is:

[0107]

[0108] in As a suggested response timeframe, The baseline response time (e.g., 24 hours). To prevent extremely small positive numbers from being divided by zero, the value should be between 0.01 and 0.1. Departments with higher urgency scores are advised to have shorter response times.

[0109] Furthermore, due to The value range is (0,1]. The value range is [0.01, 0.1], therefore The range of values ​​is approximately In cross-time zone collaboration scenarios, the system suggests a response time limit based on the difference between the affected department's time zone and the change submission time. The calculation has been adjusted to start from the next working period of the affected department, ensuring that the response time limit calculation takes into account the actual available working time.

[0110] Step 800: Obtain the design data version updates submitted by each affected department in response to the changes, extract the modification records and modification area identifiers for each version, and generate a version change mapping table.

[0111] Specifically, the system monitors version update submissions from designers in affected departments, extracts modification records from the version control system relative to the baseline version for each version, identifies specific modification areas (such as modified design element identifiers, modified parameter fields, etc.), and generates a version change mapping table. The version change mapping table records information such as the submitter, submission time, and set of modified areas for each version.

[0112] Step 900: Based on the version change mapping table, detect version pairs with overlapping modification areas, extract the specific modification content of the overlapping areas, use the semantic equivalence judgment algorithm to analyze whether there is a substantial conflict between the modifications, and generate conflict classification results.

[0113] Step 901: The system traverses the version change mapping table, performs an intersection operation on the modification area sets of any two versions, and identifies version pairs with overlapping modification areas.

[0114] Step 902: For version pairs with overlapping modification areas, the system extracts the specific modification content of each version within the overlapping area and uses a semantic equivalence judgment algorithm to analyze whether the modifications of the two versions contradict each other at the semantic level.

[0115] It should be noted that the above semantic equivalence judgment algorithm is performed according to the following rules:

[0116] If the modifications to the same parameter in two versions are identical within the allowable range of numerical error, they are considered semantically equivalent and belong to non-substantive conflicts.

[0117] If the modifications in the two versions are changes that do not affect the substantive design content, such as format adjustments or annotation modifications, they are considered semantically equivalent and are considered non-substantive conflicts.

[0118] If the two versions have numerical contradictions in their modifications to the same parameter, they are considered semantically inequivalent and constitute a substantial conflict.

[0119] Furthermore, the allowable error range for numerical values ​​is determined based on the parameter type: for dimensional parameters, the error range is an integer multiple of the design precision of that dimensional parameter (e.g., if the design precision is 1 mm, the error range can be set to 1 to 5 mm); for angular parameters, the error range is 0.1 degrees to 1 degree; for proportional parameters, the error range is 0.1% to 1% of the parameter value. When the absolute value of the difference between two modified values ​​is less than the corresponding error range, they are determined to be the same within the allowable error range for numerical values.

[0120] During the collaborative response phase following the change submission, HVAC designer Li and plumbing designer Chen adjusted the design elements they were responsible for and submitted version updates. The system extracted the modification records for each version from the version control system and generated the following version change mapping table:

[0121] Table 5 Version Change Mapping Table;

[0122]

[0123] The system traverses the version change mapping table and performs an intersection operation on the modification areas of V2.1 and V2.2. It finds that both versions modified the "installation elevation" parameter of AC-3F-002, identifying them as a version pair with overlapping modification areas. The system extracts the specific modifications in the overlapping areas: V2.1 modifies the installation elevation to 3100mm, and V2.2 modifies it to 3102mm. Using a semantic equivalence judgment algorithm, the difference between the modification values ​​of the two versions is... The design accuracy of the dimensional parameters is 1mm, and the preset error range is 5mm. The difference of 2mm is less than the error range, so it is determined that the values ​​are the same within the allowable error range and belong to non-substantial conflict.

[0124] Step 1000: For non-substantive conflicts, perform automatic merging using predefined merging rules, generate the merged version and record the merging log; for substantive conflicts, generate a conflict details report, mark the conflict location and the content of each version, and push it to the relevant designers for manual adjudication.

[0125] Step 1001: For version pairs determined to be non-substantial conflicts in Step 900, the system retrieves a predefined merge rule library and matches the corresponding merge rule based on the conflict type. Merge rules include strategies such as "based on the latest commit," "based on the commit with higher numerical precision," and "retain both and mark them." The system automatically executes the version merge operation according to the matched merge rules, generating a unified merged version and recording the merge time, merge basis, and the content of each version before the merge in the merge log.

[0126] Furthermore, the "higher numerical precision" rule is determined as follows: compare the number of significant digits in the numerical parameters of the two versions, and the version with more significant digits is determined to have higher numerical precision; if the number of significant digits is the same, then compare the number of digits after the decimal point, and the version with more decimal digits is determined to have higher numerical precision.

[0127] Step 1002: For version pairs determined to be in substantial conflict in Step 900, the system generates a conflict details report. The report includes the design element identifier of the conflict location, the parameter fields involved in the conflict, a comparison of the modifications in each version, and the information of the submitters for each version. The system pushes the conflict details report to the collaborative work interface of the relevant designers, who then manually decide on the final adopted version.

[0128] For non-substantive conflicts in the installation elevation parameters of AC-3F-002, the system matches the rule "the higher numerical precision prevails" from the merge rule base. The modified value 3100mm in V2.1 has 4 significant digits, and the modified value 3102mm in V2.2 also has 4 significant digits; the number of significant digits is the same. Further comparison of the decimal places shows that both are integers, and since the number of decimal places is the same, the rule "the latest submission prevails" applies, and the modified value 3102mm in V2.2 is adopted. The system automatically performs the merge operation, generating the merged version V2.3. The merge log is shown in the table below:

[0129] Table 6 Automatic Log Merging;

[0130]

[0131] If, during subsequent collaboration, HVAC designer Li modifies the cross-sectional width of duct AC-3F-002 to 400mm, while electrical designer Wang modifies the same duct's cross-sectional width to 320mm due to cable tray layout requirements, the difference between the two modified values ​​is 80mm, exceeding the 5mm error range for dimensional parameters. This is deemed semantically inequitable and constitutes a substantial conflict. The system generates a conflict details report and pushes it to the collaboration interface of Li and Wang, where they negotiate and determine the final adopted cross-sectional width value.

[0132] According to this implementation, because a breadth-first propagation traversal algorithm for the dependency graph is adopted, the design elements that directly and indirectly affect the change are automatically identified along the dependency edges starting from the changed object. This overcomes the problem that traditional methods rely on human experience to judge the scope of influence and are prone to overlooking factors that indirectly affect professional departments, thus solving the technical problem of incomplete identification of the scope of change influence.

[0133] Because it uses a heatmap to visualize the overlap between the current editing state and the area affected by the change, and outputs the conflict risk assessment results to the change initiator's interface before the change is submitted, it overcomes the passive factor of traditional methods that can only discover conflicts after the change is submitted. It also solves the technical problem of not being able to predict conflict risks before initiation, enabling the change initiator to intuitively understand the distribution of conflict risks and make reasonable decisions before submission.

[0134] Because an urgency scoring mechanism and a tiered early warning priority queue are introduced, the urgency score of each affected department is calculated based on the magnitude of the change and the length of the impact path, and notifications are pushed out in sequence. This overcomes the problem of untimely response from key departments caused by indiscriminate notifications in traditional methods, and ensures that key affected departments can receive notifications first and respond in a timely manner.

[0135] Because it uses a semantic equivalence judgment algorithm to distinguish between substantive and non-substantive conflicts, and uses predefined merging rules to automatically merge non-substantive conflicts such as format adjustments and numerical equivalence, it overcomes the inefficiency of traditional methods that rely entirely on manual comparison and manual merging, and solves the technical problem of low efficiency in resolving version conflicts in cross-time zone collaboration.

[0136] Furthermore, because the organizational structure hierarchy is stored in a tree structure and supports dynamic configuration, when the enterprise's organizational structure undergoes fission adjustments (such as branch office splitting, business unit mergers, or professional department reorganization), the system can update the hierarchical relationship data in real time, automatically adapt to the new organizational structure, perform impact scope analysis and notification routing, without the need to reconfigure system parameters, and has good dynamic adaptability to organizational structure.

Claims

1. A method for collaborative management and control of architectural engineering design based on organizational structure, characterized in that, The method comprises the following steps: Obtain design change request data to be initiated, extract change object identifier, change parameter type and change amplitude value, and generate change feature vector; Obtain reference dependency relationship data between each professional design element and the change object, and use a graph traversal algorithm to perform breadth-first propagation along the dependency edges from the change object to generate a design element set containing direct and indirect influences and influence path descriptions of each element; Associate query the professional department identifier to which each affected design element belongs, and obtain the current editing lock state and editing personnel information of each affected design element, and generate an affected department list and a potential conflict data element list; Calculate the influence urgency score of each affected department based on the change amplitude and the influence path length, calculate the semantic correlation degree of each affected design element and the change content based on the potential conflict data element list, and generate conflict risk level labels; Map the conflict risk level labels to the spatial layout data to generate a change conflict risk heat map, and generate a hierarchical warning priority queue according to the influence urgency score; Output the change conflict risk heat map and the hierarchical warning priority queue to the change initiator interface for decision whether to immediately submit the change.

2. The organization structure-based building engineering design collaborative management and control method according to claim 1, characterized in that, The method comprises the following steps: Query the directed graph structure with the change object as the starting point from the reference dependency relationship database, wherein the nodes in the directed graph represent design elements, and the directed edges represent the reference dependency relationship between the elements; Use a breadth-first traversal algorithm to start from the change object node and propagate layer by layer outward along the reference dependency edges, wherein the nodes reached by the first layer of traversal are the directly affected design elements, and the nodes reached by the second layer and deeper layers of traversal are the indirectly affected design elements; Record the influence path of each affected design element in the traversal process, wherein the influence path is the sequence of dependency edges from the change object to the affected design element; Stop the propagation to deeper layers when the traversal level exceeds a preset traversal depth threshold, wherein the traversal depth threshold is determined according to the scale and professional complexity of the architectural engineering design project.

3. The organization structure-based building engineering design collaborative management and control method according to claim 1, characterized in that, The method comprises the following steps: Normalize the change amplitude value according to the parameter type, divide the original change amplitude value by the typical change amplitude upper limit value of the parameter type, and obtain the normalized dimensionless change amplitude value; Calculate the urgency score of each affected design element using an influence urgency score function, wherein the score is proportional to the normalized change amplitude value and inversely proportional to the sum of the influence path length plus one; For the case that a same affected department contains multiple affected design elements, take the maximum value of the urgency scores of all the affected design elements in the affected department as the influence urgency score of the affected department.

4. The organization structure-based building engineering design collaborative management and control method according to claim 1, characterized in that, The method comprises the following steps: The parameter type label set involved in the change content and the parameter type label set involved in the editing content are acquired; A semantic correlation degree is calculated by using a set similarity coefficient, and the semantic correlation degree is equal to a ratio of a number of elements in an intersection of the two parameter type label sets to a number of elements in a union of the two parameter type label sets; When the semantic correlation degree exceeds a preset threshold value, the conflict is marked as a high-risk conflict, otherwise, the conflict is marked as a low-risk conflict, and the preset threshold value is in a range of zero to one.

5. The organization structure-based building engineering design collaborative management and control method according to claim 1, characterized in that, The conflict risk level marking is mapped onto the spatial layout data to generate a change conflict risk heat map, including: Spatial position attributes of each design element in the change influence range are acquired, and the spatial position attributes include a floor, an area, and a coordinate; The conflict risk level marking is mapped to a corresponding spatial position, and a visual change conflict risk heat map is generated by using color coding, and a high-risk area is identified by using a first color, and a low-risk area is identified by using a second color.

6. The organization structure-based building engineering design collaborative management and control method according to claim 1, characterized in that, Further comprising: After a submission confirmation instruction of a change initiator is acquired, a change early warning notice is pushed to each affected department in a hierarchical early warning priority queue, and the notice content includes a change summary, an influence path, and a recommended response time limit; The recommended response time limit is in an inverse proportional relationship with the influence emergency degree score, and is equal to a baseline response time limit divided by a sum of the influence emergency degree score and a very small positive number to prevent division by zero, and the higher the emergency degree score of a department, the shorter the recommended response time limit.

7. The organization structure-based building engineering design collaborative management and control method according to claim 6, characterized in that, Further comprising: A version change mapping table is generated by acquiring design data version updates submitted by each affected department in response to the change, extracting modification records and modification area identifications of each version, and extracting specific modification contents of the overlapping area for the version pair with the overlapping modification area, and analyzing whether the modification has a substantial conflict by using a semantic equivalence judgment algorithm to generate a conflict classification result. The semantic equivalence judgment algorithm includes: If modification results of the same parameter of two versions are the same within a numerical allowable error range, it is determined that the semantic equivalence belongs to a non-substantial conflict; 8. The organization structure-based building engineering design collaborative management and control method according to claim 7, characterized in that, If the modification of two versions belongs to format adjustment or comment modification, it is determined that the semantic equivalence belongs to a non-substantial conflict; If the modification results of the same parameter of two versions have numerical contradictions, it is determined that the semantic equivalence does not belong to a substantial conflict; The numerical allowable error range is determined according to the parameter type, and for a size parameter, it is an integer multiple of design accuracy, for an angle parameter, it is a preset angle error value, and for a proportion parameter, it is a preset percentage of the parameter value. Further comprising: For a non-substantial conflict, a predefined merging rule library is acquired, a corresponding merging rule is matched according to the conflict type to perform automatic merging, a merged version is generated, and a merging log is recorded; 9. The organization structure-based building engineering design collaborative management and control method according to claim 7, characterized in that, The merging rule includes a rule of taking the latest submission as a reference and a rule of taking the one with higher numerical accuracy as a reference. ​ ​ The judgment mode of the rule of higher numerical precision is: comparing the effective number of digits of the numerical parameters in the two versions, the version with more effective number of digits is judged as higher numerical precision; if the effective number of digits is the same, then compare the number of decimal places, the version with more decimal places is judged as higher numerical precision; For substantial conflicts, a conflict detail report is generated and pushed to the relevant designers for manual adjudication, including the design element identification of the conflict location, the parameter fields involved in the conflict, and the modification content comparison of each version.

10. A collaborative management system for building engineering design based on organization structure, for performing the collaborative management method for building engineering design based on organization structure as claimed in any one of claims 1-9, characterized in that, Comprise: The organizational structure management module is used for maintaining a dynamic multi-level organizational structure tree structure including a company, a branch, a department, and a professional department, supporting the addition, splitting, merging, and level adjustment operations of organizational units, and updating the level relationship data in real time when the organizational structure splits; The change request processing module is used for obtaining design change request data and generating a change feature vector; The influence range analysis module is used for executing a graph traversal algorithm based on the reference dependency relationship data and the organizational structure level relationship data, generating an affected design element set and cross-level organizational unit information belonging to the affected design element set; The conflict risk assessment module is used for calculating the impact urgency score and the semantic correlation degree and generating a conflict risk level label; The visual warning module is used for generating a change conflict risk heat map and a hierarchical warning priority queue and outputting to a user interface; The version conflict resolution module is used for detecting version conflicts and performing semantic equivalence judgment and automatic merging processing.

Images