BIM-based shared parameter binding method, electronic device and medium

Abstract

This application provides a BIM-based method, electronic device, and medium for binding shared parameters, relating to the field of Building Information Modeling (BIM) technology. The method includes: acquiring shared parameters to be bound; performing multi-dimensional conflict detection based on the shared parameters, including project parameter conflict detection, category-level conflict detection, family parameter conflict detection, and parameter data type mismatch detection; determining if a conflict has been detected; acquiring the priority of the detected conflict; acquiring the corresponding resolution information based on the priority; resolving the conflict based on the resolution information; and binding the shared parameters. This application's embodiment can automatically perform multi-dimensional conflict detection before binding shared parameters and resolve conflicts based on the detection results, effectively reducing user workload while being fast, efficient, and less prone to omissions, thus improving binding efficiency and ensuring the accuracy of shared parameter binding.

Description

Technical Field

[0001] This application relates to the field of building information modeling technology, and more specifically, to a BIM-based method for binding shared parameters, electronic equipment, and media. Background Technology

[0002] In BIM design practice for building engineering projects, shared parameters are the core mechanism for BIM platforms such as Autodesk Revit to achieve unified management of parameter information across projects and families. Shared parameters use a shared parameter file (SPF) to uniformly define the parameter's name, data type, and unique identifier (GUID), and then bind it to a specific category in the project, enabling different families and projects to share consistent parameter definitions.

[0003] However, in actual BIM projects, when binding shared parameters to project categories, data corruption often occurs due to duplicate parameters under the same family category or parameters with the same name whose attribute values ​​are overwritten. To avoid these problems, users can only manually check and modify parameters that may cause data corruption before binding. The process of checking and modifying is labor-intensive, time-consuming, and prone to omissions, ultimately resulting in low binding efficiency and difficulty in ensuring the accuracy of shared parameter binding. Summary of the Invention

[0004] This application provides a BIM-based method, electronic device, and medium for binding shared parameters. This addresses the problems of existing methods that rely on manual checking and handling of binding conflicts, resulting in high workload, long processing times, and a high risk of omissions, leading to low binding efficiency and difficulty in ensuring the accuracy of shared parameter binding. To achieve this objective, this application provides the following solutions.

[0005] According to one aspect of the embodiments of this application, a BIM-based shared parameter binding method is provided, the method comprising: Obtain the shared parameters to be bound, and perform multi-dimensional conflict detection based on the shared parameters. The multi-dimensional conflict detection includes project parameter conflict detection, category-level conflict detection, family parameter conflict detection, and parameter data type mismatch detection. Once a conflict is detected, the priority of the detected conflict is obtained, and the resolution information corresponding to the conflict is obtained based on the priority. The conflict is resolved and the shared parameters are bound based on the resolution information.

[0006] In one possible implementation, the project parameter conflict detection includes: Traverse the project parameter set under the target category in the BIM project and compare the parameter names of the project parameters in the project parameter set with those of the shared parameters; If the shared parameter contains the same parameter name as the project parameter, then a project parameter conflict is determined to exist.

[0007] In one possible implementation, the category-level conflict detection includes: Traverse the existing binding information in the target category of the BIM project, whereby the binding information includes the binding method of the parameters; If, based on the binding information and the binding method of the shared parameter, it is determined that there exists a shared parameter with the same name as the parameter but a different binding method, then it is determined that a conflict of the same name for instance / type parameter has been detected.

[0008] In one possible implementation, the family parameter conflict detection includes: Scan the parameter definition set corresponding to the target category in the BIM project, and compare the family parameter definition information of each family parameter in the parameter definition set with the shared parameter; If the shared parameters conflict with the family parameter definition information, then a family parameter conflict is detected.

[0009] In one possible implementation, the parameter data type mismatch detection includes: Based on the detection results of the project parameter conflict detection and the family parameter conflict detection, obtain the matching objects that have the same parameter name as the shared parameters. The matching objects include project parameters and family parameters. Identify the first object among the shared parameters that has the same parameter name as the object to be matched; If the data type of the first object is different from that of the object to be matched, then it is determined that a parameter data type mismatch has been detected.

[0010] In one possible implementation, obtaining the priority of the detected conflict includes: The priority of a conflict is determined based on its impact on the integrity of the BIM model, and the priority includes critical, high, medium and low.

[0011] In one possible implementation, obtaining the resolution information corresponding to the conflict based on the priority includes: Configure a set of resolvable options for each conflict based on its priority; The conflict and the set of resolvable options are displayed based on the priority order, and the resolution information corresponding to the conflict is obtained. The resolution information is generated based on the set of resolvable options.

[0012] In one possible implementation, the method, wherein resolving conflicts and binding the shared parameters based on the resolution information, includes: The conflict is resolved based on the resolution options corresponding to the aforementioned resolution information; Once the conflict resolution is confirmed, a binding operation sequence is generated, and the shared parameters are bound to the target category of the BIM project based on the binding operation sequence.

[0013] According to one aspect of the embodiments of this application, an electronic device is provided, including a processor and a memory, wherein the processor is communicatively connected to the memory, the memory stores program data, and the program data is used to execute the method described above.

[0014] According to one aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored, characterized in that the computer program, when executed by a processor, implements the steps of the method described above.

[0015] The beneficial effects of the technical solutions provided in this application are: The BIM-based shared parameter binding method provided in this application includes: acquiring shared parameters to be bound; performing multi-dimensional conflict detection based on the shared parameters, whereby multi-dimensional conflict detection includes at least one of project parameter conflict detection, category-level conflict detection, family parameter conflict detection, and parameter data type mismatch detection; determining that a conflict has been detected; acquiring the priority of the detected conflict; acquiring the corresponding resolution information based on the priority; and resolving the conflict and binding the shared parameters according to the resolution information. This application's embodiment can automatically perform multi-dimensional conflict detection before binding shared parameters and resolve conflicts based on the detection results, effectively reducing user workload while being fast, efficient, and less prone to omissions, thus improving binding efficiency and ensuring the accuracy of shared parameter binding. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0017] Figure 1 A flowchart illustrating the BIM-based shared parameter binding method provided in this application embodiment; Figure 2 The execution flowchart of the BIM-based shared parameter binding method provided in the embodiments of this application; Figure 3 A flowchart for project parameter conflict detection provided in this application embodiment; Figure 4 A flowchart for category-level conflict detection provided in this application embodiment; Figure 5A flowchart for family parameter conflict detection provided in an embodiment of this application; Figure 6 A flowchart for detecting parameter data type mismatch provided in this application embodiment; Figure 7 A schematic diagram illustrating the default resolution strategies and sets of resolvable options configured for different priorities in embodiments of this application; Figure 8 A flowchart for conflict resolution provided in the embodiments of this application; Figure 9 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0018] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions of the embodiments of this application.

[0019] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the terms “comprising” and “including” as used in embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, operation, element, and / or component, but do not exclude implementation as other features, information, data, step, operation, element, component, and / or combinations thereof supported by the art. It should be understood that when we say that an element is “connected” or “coupled” to another element, the one element can be directly connected or coupled to the other element, or it can mean that the one element and the other element establish a connection relationship through an intermediate element. Furthermore, “connected” or “coupled” as used herein can include wireless connection or wireless coupling. The term “and / or” as used herein indicates at least one of the items defined by the term; for example, “A and / or B” indicates implementation as “A,” or implementation as “A,” or implementation as “A and B.”

[0020] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0021] The technical solutions of this application and their effects are described below through several exemplary embodiments. It should be noted that the following embodiments can be referenced, borrowed from, or combined with each other. Identical terms, similar features, and similar implementation steps in different embodiments will not be repeated.

[0022] It should be noted that the collection, storage, use, processing, transmission, provision, and disclosure of data or user information involved in the technical solution of this application all comply with relevant laws and regulations and do not violate public order and good morals. The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, and displayed data) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use, and processing of related data must comply with relevant laws, regulations, and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse. In addition, certain software, components, models, and other existing industry solutions may be mentioned in the embodiments of this application. These should be considered exemplary, and their purpose is merely to illustrate the feasibility of implementing the technical solution of this application, but does not mean that the applicant has already used or necessarily used such solutions.

[0023] The BIM-based shared parameter binding method, electronic device, and medium provided in this application aim to solve at least one technical problem existing in the prior art.

[0024] Optionally, the object executing the BIM-based shared parameter binding method of this application can be a mobile phone, computer, server, cloud platform, or other terminal that can be used for shared parameter binding in BIM projects.

[0025] In one embodiment, the method of this application can be used in a BIM-based shared parameter binding system. This system may include: a multi-dimensional conflict detection module, used to perform project parameter conflict detection, category-level binding conflict detection, family parameter conflict detection, and parameter data type mismatch detection before the shared parameters are bound to a BIM project category, generating conflict detection results; a conflict priority classification module, used to classify conflicts into four priorities—critical, high, medium, and low—based on the degree of impact of the conflicts in the conflict detection results on the integrity of the BIM model data; a hierarchical resolution strategy configuration module, used to configure independent default resolution strategies and a set of resolvable options according to the conflict priorities; and an ordered conflict resolution module, used to sort conflicts from high to low priority, sequentially display the conflicts and their corresponding resolution options for the user to choose from, receive the user's selection of a resolution strategy for each conflict, process multiple priority conflicts of the same parameter according to the principle of conflict independence, generate the final parameter binding operation sequence according to the resolution strategies, and execute it.

[0026] Optionally, such as Figures 1-8 As shown, the BIM-based shared parameter binding method of this application includes: S101: Obtain the shared parameters to be bound and perform multi-dimensional conflict detection based on the shared parameters.

[0027] Optionally, a list of shared parameters input by the user can be obtained, and the shared parameters to be bound can be obtained from this list. Alternatively, the correspondence between different categories and shared parameters can be pre-stored. Upon receiving an instruction to bind a shared parameter to a certain category, the target category in the instruction can be obtained, and the shared parameters to be bound can be determined based on the target category and the correspondence.

[0028] Alternatively, a file uploaded by the user containing shared parameters can be obtained, the shared parameters to be bound can be obtained based on the file, and the target category to be bound can be determined according to the received binding instructions.

[0029] Optionally, a binding compatibility pre-check can be performed before conducting multi-dimensional conflict detection. This pre-check can include verifying whether the shared parameter is compatible with the target category to be bound in the BIM project, whether the shared parameter can be used for binding, and other compatibility-related checks. If incompatibility issues are identified after the pre-check, the shared parameter can be marked as conflicting for subsequent processing.

[0030] Optionally, multi-dimensional conflict detection includes project parameter conflict detection, category-level conflict detection, family parameter conflict detection, and parameter data type mismatch detection. After obtaining the shared parameters, each of these checks can be performed, or one or more checks can be executed based on user instructions, configuration information, shared parameter types, or other conditions.

[0031] Optionally, project parameter conflict detection includes: traversing the project parameter set under the target category in the BIM project, comparing the parameter names of the project parameters in the project parameter set with those of the shared parameters; if the shared parameters contain the parameter names of the project parameters, then a project parameter conflict is determined to exist.

[0032] In one embodiment, for project parameter conflict detection, the project parameter set under the target category in the BIM project can be traversed. The parameter names of each project parameter and the shared parameter to be bound in the project parameter set are compared. If a project parameter with the same name as a shared parameter exists, a project parameter conflict is determined. The purpose of this detection is to identify shared parameters with duplicate names, preventing shared parameters from directly overwriting project parameters with the same name during binding, thus avoiding the loss of existing data values. If the parameter names are the same, regardless of whether the data types of the two (shared parameter and project parameter) are consistent, it is determined to be a project parameter conflict.

[0033] Optionally, category-level conflict detection includes: traversing the existing binding information in the target category of the BIM project, the binding information including the binding method of the parameter; if it is determined from the binding information and the binding method of the shared parameter that there is a shared parameter with the same name as the parameter in the target category but with a different binding method, then it is determined that a conflict of the same name of instance / type parameter has been detected.

[0034] In one embodiment, for category-level binding conflict detection, the parameter binding iterator of the BIM platform API can be used to traverse the existing binding information on the target category and check whether there are parameters with the same name but different binding methods on the target category. Binding methods include instance binding and type binding. If two objects with the same parameter name (shared parameters, parameters on the target category) have inconsistent binding methods, it is determined to be an instance / type parameter conflict. The purpose of this detection is to ensure that the binding methods of parameters with the same name are consistent, avoiding data access anomalies caused by mismatched instance / type binding methods.

[0035] Optionally, family parameter conflict detection includes: scanning the parameter definition set corresponding to the target category in the BIM project, comparing the family parameter definition information of each family parameter in the parameter definition set with the shared parameters; if there is a conflict between the shared parameters and the family parameter definition information, then a family parameter conflict is determined to have been detected. Specifically, the existence of a family parameter conflict can be detected by checking whether the parameter definition of the shared parameters conflicts with the family parameter definition information.

[0036] In one embodiment, the parameter definition set of families (a type of component attached to a target category) already loaded into the BIM project can be scanned. This set includes the family parameter definition information for each loaded family under the target category, including the parameter name, parameter unique identifier (GUID), and data type. Each family parameter definition is compared with the parameter to be bound. This comparison includes the parameter name, parameter unique identifier (GUID), and data type. If the comparison results indicate the existence of a family parameter with the same name as a shared parameter but a different definition, it is considered a conflict of parameter names for the same family type. Project parameters exist at the project-wide level, while family parameters exist within a specific family.

[0037] Optionally, the parameter data type mismatch detection includes: obtaining a target object with the same parameter name as the shared parameter based on the detection results of project parameter conflict detection and family parameter conflict detection. The target object includes project parameters and family parameters; determining the first object among the shared parameters with the same parameter name as the target object (i.e., the shared parameter with the same name is called the first object); if the data type of the first object is different from that of the target object, then it is determined that a parameter data type mismatch has been detected.

[0038] In one embodiment, for project parameters and shared parameters with the same name confirmed in a project parameter conflict, if the data type of the shared parameter is inconsistent with the data type of the project parameter (including different base types, or the same base type but different spec identifiers in ForgeTypeId), a parameter data type mismatch conflict message is generated. Similarly, for family parameters and shared parameters with the same name confirmed in a family parameter conflict, if the data type of the shared parameter is inconsistent with the data type of the family parameter with the same name, a parameter data type mismatch conflict message is also generated. This detection is independent of the project parameter conflict detection; its purpose is to identify definition differences at the data type level and provide users with a decision-making basis for whether type conversion is allowed.

[0039] S102: Determine that a conflict has been detected, obtain the priority of the detected conflict, and obtain the resolution information corresponding to the conflict based on the priority.

[0040] Optionally, after the conflict detection in the above four dimensions is completed, all detected conflicts can be statistically analyzed, and the priority of each conflict can be set according to its type. Obtaining the priority of detected conflicts includes determining the priority of conflicts based on their impact on the integrity of the BIM model, with priorities categorized as critical, high-level, medium-level, and low-level.

[0041] Optionally, detected project parameter conflicts can be classified as critical, instance / type name conflict parameters can be classified as high priority, family parameter conflicts can be classified as medium priority, and parameter data type mismatch can be classified as low priority.

[0042] In one embodiment, detected conflicts can be categorized into four priorities based on their impact on the integrity of BIM model data: (1) Critical: Project parameter conflicts caused by identical parameter names. If such conflicts are directly overwritten, the data values ​​stored in the project parameters will be lost, causing irreversible damage to the data integrity of the BIM model, and the impact is the highest.

[0043] (2) High: Instance / type parameter name conflict. This type of conflict leads to inconsistent parameter binding methods, resulting in abnormal data access and affecting the normal use of the model, but it will not directly cause data loss.

[0044] (3) Medium: Conflict of parameters with the same name in the same family type. In this type of conflict, the parameter definitions of the family parameter and the shared parameter are inconsistent, which may lead to data conflicts between the family parameter and the shared parameter, but the impact is limited to the specific family type.

[0045] (4) Low: Parameter data type mismatch. This type of conflict only affects data precision or format, and does not directly affect the integrity of model data, so the impact is the lowest.

[0046] Optionally, retrieving conflict resolution information based on priority includes: configuring a set of resolvable options for each conflict according to its priority; displaying conflicts and the set of resolvable options in priority order; and retrieving the corresponding resolution information, which is generated based on the set of resolvable options. When configuring the set of resolvable options, a default resolution strategy can also be configured for each conflict. This default strategy corresponds to a resolution option in the set of resolvable options and can be used to provide a reference for users when selecting a resolution option.

[0047] Optionally, for different conflicts, if the conflicts have the same priority, the same default resolution strategy and set of resolvable options can be configured.

[0048] In one embodiment, an independent default resolution strategy and a user-selectable set of resolution options can be configured for each priority level: (1) Critical level conflict: The default resolution strategy is Skip, and the user-selectable set of resolution options is Skip, Overwrite, and Rename.

[0049] (2) Advanced conflict: The default resolution strategy is to rename. The user-selectable set of resolution options is to skip, rename, use instance binding, and use type binding.

[0050] (3) Intermediate conflict: The default resolution strategy is Skip. The user-selectable set of resolution options is Skip and OverwriteFamily.

[0051] (4) Low-level conflicts: The default resolution strategy is forced type conversion (ForceConvert), and the user-selectable set of resolution options is skip and forced type conversion.

[0052] Users can select a solution option from the set of solvable options, and the conflict corresponding to that set of solvable options will be handled based on the user's selection.

[0053] S103: Resolve conflicts and bind shared parameters based on the resolution information.

[0054] Optionally, resolving conflicts and binding shared parameters based on the resolution information includes: resolving conflicts based on the resolution options corresponding to the resolution information; determining that the conflict resolution is complete, generating a binding operation sequence, and binding the shared parameters to the target category of the BIM project based on the binding operation sequence.

[0055] Optionally, conflicts can be sorted in descending order of priority, and the conflicts and their corresponding resolution options can be displayed sequentially for the user to choose from. After the user selects a resolution strategy for each conflict, the resolution result is recorded and the process moves to the next conflict. For situations where the same parameter triggers multiple priority conflicts (e.g., a parameter satisfies both project parameter conflicts and data type mismatch conflicts), the "conflict independence" principle can be adopted: each conflict is recorded independently, numbered independently, and displayed independently in priority order. When a user selects "skip" for a high-priority conflict of the same parameter, the binding operation for that parameter is skipped entirely, and low-priority conflicts are automatically marked as "skipped" and are no longer displayed to the user or subjected to any operation. Only when the user selects a non-skip strategy (such as "overwrite" or "rename") for a high-priority conflict of the same parameter will the low-priority conflicts of that parameter continue to be displayed for the user to handle. This mechanism ensures that different priority conflict resolution strategies for the same parameter do not contradict each other—the resolution decision of the highest priority conflict determines whether that parameter continues to participate in the subsequent conflict resolution process.

[0056] Optionally, to save workload, a batch application function for resolution strategies can also be provided. When a user selects the same resolution strategy for multiple conflicts of the same type (e.g., selecting override for multiple project parameter conflicts), the resolution strategy is automatically applied to all remaining conflicts of the same type. After all conflicts are resolved, the final parameter binding operation sequence is generated and executed according to the resolution strategy, thereby completing the binding of all shared parameters.

[0057] The method of this application will be further explained below through specific embodiments of the parameter binding method of this application.

[0058] In one embodiment, in a scenario where 50 shared parameters are bound to the "pipe fittings" category in a HVAC design project, the specific steps for binding the shared parameters are as follows: Step S1: Multi-dimensional conflict detection In this HVAC design project, 50 shared parameters (including pipe diameter, medium type, insulation thickness, valve model, etc.) need to be bound to the "Pipe Fittings" category of the Revit project. Before performing the binding operation, conflict detection in four dimensions is automatically performed.

[0059] (1) Project parameter conflict detection: Traverse the existing parameter set under the "Pipe Accessories" category in the project, and compare the parameter names of each project parameter in the parameter set with the 50 shared parameters to be bound. Detection revealed 3 parameters with the same name: parameter "Pipe Diameter" (existing project parameter data type is length), parameter "Media Type" (existing project parameter data type is text), and parameter "Insulation Thickness" (existing project parameter data type is length). These 3 parameters already exist in the project and have stored design data values. This step only determines whether there is a name conflict based on the parameter name, and does not involve the determination of data type—even if the data types of parameters with the same name are completely identical, as long as the name is the same, it is determined to be a project parameter conflict, because the overwrite binding operation may still result in the loss of data values.

[0060] (2) Category-level binding conflict detection: The existing binding information in the "Pipe Fittings" category can be traversed using the ParameterBindings iterator of the Revit API to check whether the binding method of each shared parameter to be bound is consistent with that of the bound parameter. Two instances / type name conflicts were found: the existing parameter "Valve Model" is bound as a type parameter, but the binding method of the shared parameter "Valve Model" to be bound is an instance parameter; the existing parameter "Installation Method" is bound as an instance parameter, but the binding method of the shared parameter "Installation Method" to be bound is a type parameter.

[0061] (3) Family parameter conflict detection: Scan the parameter definition set of all pipe accessory families (valve, flange, filter, etc.) loaded under the "Pipe Accessories" category in the project. The parameter definition information of each family in this set includes parameter name, parameter unique identifier (GUID), and data type. Compare the parameter definition information in each family with the parameter definition information of the shared parameter to be bound. The detection found no cases where the parameter names are the same but the parameter definitions are different.

[0062] (4) Parameter data type mismatch detection: Obtain parameter pairs with the same name confirmed in the above three detection dimensions (including existing parameters and shared parameters in the project), and further compare their data types. For the parameter "pipe diameter" confirmed in the project parameter conflict, the detection also shows that there is a parameter type mismatch: the data type of the shared parameter "pipe diameter" is defined as length in SPF, but although the existing parameter with the same name in the project is also of length type, its specific parameter definition format is different (such as the spec identifier in ForgeTypeId is different). For the two parameters with the same name, "medium type" and "insulation thickness", their data types are consistent with the existing parameters, and no data type mismatch conflict occurs. For the parameters with the same name confirmed in the family parameter conflict (there is no family parameter conflict in this embodiment), the data type comparison will also be performed.

[0063] Step S2: Conflict Priority Classification Based on the degree of impact of the conflicts on the integrity of the BIM model data, the six detected conflicts were divided into four priorities: - Critical: Three project parameters conflict (pipe diameter, medium type, insulation thickness) because these parameters already contain design data values, and directly overwriting them will result in data loss.

[0064] - High: Conflicts in parameters with the same name for two instances / types (valve model, installation method) and inconsistent binding methods will lead to abnormal data access.

[0065] - Medium: 0 family type parameter name conflicts.

[0066] - Low: 1 parameter type mismatch conflict (difference in pipe diameter spec identifier).

[0067] Note: The "pipe diameter" parameter triggers both a critical-level conflict (parameters with the same name) and a low-level conflict (data type mismatch). You can generate two separate conflict records for this parameter and assign them to different priorities.

[0068] Step S3: Configure Tiered Solution Strategy Load the pre-configured default resolution strategy and user-selectable resolution option set for each priority level: - Critical level conflicts: The default strategy is to skip, and the optional strategies are to skip, overwrite, and rename.

[0069] - Advanced conflict: The default strategy is Rename, and the optional strategies are Skip, Rename, Use Instance Binding, and Use Type Binding.

[0070] - Low-level conflicts: The default strategy is forced type conversion (ForceConvert), and the optional strategies are skip and forced type conversion.

[0071] Step S4: Orderly Conflict Resolution Conflicts are sorted by priority from highest to lowest and presented to the user for processing in sequence. For cases where the same parameter triggers multiple priority conflicts (e.g., "pipe diameter" has both critical and low-priority conflicts), the conflict independence principle is followed: high-priority conflicts are displayed first, and their resolution decisions determine whether low-priority conflicts continue to be displayed. Specifically: (1) First, address the three critical level conflicts: - "Pipe Diameter" parameter conflict: The user chooses to skip this option, leaving the existing parameter and data values ​​unchanged. Because the critical-level conflict of "Pipe Diameter" is selected as "skipped", the binding operation of this parameter is skipped entirely. Its lower-level conflicts (data type mismatch) are automatically marked as "skipped" and are no longer displayed to the user, nor is a forced type conversion operation performed.

[0072] - "Media type" parameter conflict: User opted to override because the parameter needs to be updated to a new definition.

[0073] - "Insulation thickness" parameter conflict: The user chooses to skip this option and retain the existing data.

[0074] (2) Then handle the two high-level conflicts: - "Valve Model" parameter conflict (to be bound as an instance parameter, already exists as a type parameter): The user selected to use instance binding, so the binding method is changed to instance parameter binding.

[0075] - "Installation Method" parameter conflict (to be bound as a type parameter, already exists as an instance parameter): The user selected to use type binding, so the binding method is changed to type parameter binding.

[0076] (3) Finally, handle low-level conflicts: Since the low-level conflict of "pipe diameter" (key level selected to skip) has been automatically marked as "skipped", there are no low-level conflicts that the user needs to handle in this step. If other parameters have low-level conflicts and their high-priority conflicts are not selected to "skip", they will be displayed normally for the user to handle.

[0077] After all conflicts are resolved, the system generates the final binding operation sequence according to the resolution strategy: skip the binding of "pipe diameter" and "insulation thickness", override the binding of "medium type", modify "valve model" to instance binding, modify "installation method" to type binding, skip the data type mismatch conflict of "pipe diameter" along with the critical level "skip", and directly perform binding on the remaining 44 non-conflicting shared parameters.

[0078] In the end, 47 parameters were successfully bound (2 were skipped and 1 was overwritten), with no data corruption.

[0079] In one embodiment, in a fire protection design project where 30 shared parameters are bound to the "sprinkler system" category, the binding method adopted for this binding requirement includes: Step S1: Multi-dimensional conflict detection In this fire protection design project, 30 shared parameters (including sprinkler flow rate, working pressure, response time, installation height, etc.) need to be bound to the "Sprinkler Unit" category of the Revit project. Before binding, the following tests must be performed: (1) Parameter conflict detection: After traversing the existing parameters under the "spraying device" category, no conflicting parameters with the same name were found.

[0080] (2) Category-level binding conflict detection: Existing bindings on the "Sprinkler Unit" category were detected by Revit API, and no instance / type name conflict was found.

[0081] (3) Parameter conflict detection: Scan the parameter definition set (including parameter name, GUID and data type information of each family) of the sprinkler family (including standard sprinkler head, sidewall sprinkler head, concealed sprinkler head, etc.) that has been loaded into the "sprinkler device" category in the project. The detection found that there were five family types with conflicting parameters with the same name: There are five parameters in the sprinkler family: "sprinkler flow rate", "working pressure", "response time", "installation height" and "K coefficient", but the definition of these parameters is inconsistent with the parameter definition of the shared parameters to be bound (e.g., the family parameter is a custom parameter within the family, not defined through the shared parameter mechanism, and lacks a unified GUID identifier).

[0082] (4) Parameter data type mismatch detection: The system compares the data types of the same-named parameters confirmed in the family parameter conflict and finds no additional data type mismatch conflicts.

[0083] Step S2: Conflict Priority Classification The five detected conflicts were classified as Medium: conflicts involving parameters with the same name in the same family type.

[0084] Step S3: Configure Tiered Solution Strategy Load the default strategy Skip for intermediate conflicts and the optional strategy OverwriteFamily.

[0085] Step S4: Orderly Conflict Resolution Five intermediate-level conflicts are presented to the user for handling. The user selects to override all family parameters, replacing the parameter definitions of custom parameters within the five families with the parameter definitions of shared parameters, thereby standardizing the parameter definitions.

[0086] After all conflicts are resolved, the system generates the final binding operation sequence: for the 5 conflicting parameters, family parameter overriding is performed first, followed by project binding; for the remaining 25 conflict-free parameters, binding is performed directly.

[0087] Ultimately, 30 parameters were successfully bound, and 5 family parameters were replaced by project-shared parameters, achieving uniformity and standardization in parameter definition.

[0088] In one embodiment, this application is applied to a scenario in a comprehensive electromechanical project involving the batch binding of parameters from three disciplines: HVAC, water supply and drainage, and electrical engineering. In this project, the user needs to bind a total of 120 shared parameters to the corresponding categories of the three disciplines. The system performs multi-dimensional conflict detection on the 120 parameters, identifying 15 conflicts: 4 critical, 3 high-level, 5 medium-level, and 3 low-level.

[0089] Two parameters simultaneously triggered critical-level and low-level conflicts (i.e., the parameter names are the same but the data types do not match). The system generates an independent conflict record for each parameter, and assigns the priority to critical-level and low-level respectively.

[0090] Users handle conflicts sequentially according to priority. For critical conflicts, three are skipped and one is overridden. The two low-level conflicts for which "skip" was selected are automatically marked as "skipped." For high-level conflicts, two are bound using instances and one is renamed. For mid-level conflicts, five family parameters are overridden. For low-level conflicts, one is forcibly type-casted (the other two low-level conflicts are automatically skipped due to their higher priority). After all conflicts are resolved, the system generates and executes the binding operation sequence, ultimately successfully binding 115 parameters, skipping three, overriding one, and renaming one, with no data corruption.

[0091] The BIM-based shared parameter binding method provided in this application has the following advantages compared to existing technologies: 1. Systematically detect parameter binding conflicts in four dimensions to avoid omissions: Through project parameter conflict detection, category-level binding conflict detection, family parameter conflict detection, and parameter data type mismatch detection, it comprehensively covers the types of conflicts that may occur in BIM parameter binding scenarios, ensuring that no potential conflicts are missed.

[0092] 2. A four-level classification based on the impact on data integrity ensures that critical conflicts are prioritized: This application establishes for the first time a four-level priority system based on the degree of impact on model data integrity in a BIM parameter binding scenario. Critical conflicts (project parameter conflicts) will lead to irreversible data loss if directly overridden, therefore they have the highest priority; low-level conflicts (type mismatch) only affect accuracy, and have the lowest priority. This hierarchical approach ensures that the most critical data security issues are addressed first.

[0093] 3. Independent solution strategy set for each level, balancing automation efficiency and user control: Each priority level is configured with an independent default solution strategy. Critical levels are skipped by default (to avoid data loss), while lower levels are forced to convert by default (allowing for precision adjustment), balancing automation efficiency and user control over critical operations. A complete set of optional solutions is also provided, allowing users to flexibly choose according to their actual needs.

[0094] 4. Avoid data corruption and loss caused by blind binding: Through systematic conflict detection and hierarchical resolution before binding, data corruption caused by direct binding or blind overwriting is avoided, ensuring the security and integrity of BIM model data.

[0095] 5. Batch resolution strategy improves operational efficiency: Supports applying the same resolution strategy to similar conflicts in batches, avoiding users having to handle a large number of similar conflicts one by one, and improving the overall efficiency of parameter binding operations while ensuring data security.

[0096] 6. The principle of conflict independence avoids strategic contradictions in multi-priority conflicts: When the same parameter triggers multiple priorities of conflict at the same time, the principle of conflict independence and the cascading skip mechanism ensure that the decision to resolve high-priority conflicts automatically determines the presentation and handling of low-priority conflicts, thus eliminating contradictions between strategies of different priorities from a mechanism perspective.

[0097] In one alternative embodiment, an electronic device is provided, such as Figure 9 As shown, Figure 9 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0098] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0099] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the figure, but this does not indicate that there is only one bus or one type of bus.

[0100] The memory 4003 may be ROM (Read-Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read-Only Memory), CD-ROM (Compact Disc Read-Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer, without limitation herein.

[0101] The memory 4003 stores computer programs that execute embodiments of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the computer programs stored in the memory 4003 to implement the steps shown in the foregoing method embodiments.

[0102] Among them, electronic devices can be any electronic product that can interact with an object, such as personal computers, tablets, smartphones, personal digital assistants (PDAs), game consoles, interactive network television (IPTV), smart wearable devices, etc.

[0103] The electronic device may also include network devices and / or object devices. The network devices include, but are not limited to, a single network server, a server group consisting of multiple network servers, or a cloud consisting of a large number of hosts or network servers for cloud computing.

[0104] The networks in which the electronic devices are located include, but are not limited to, the Internet, wide area networks, metropolitan area networks, local area networks, and virtual private networks (VPNs).

[0105] Based on the same inventive concept, this application also proposes a computer-readable storage medium.

[0106] In this embodiment, a computer-readable storage medium stores a computer program that is used to perform the methods described in the above embodiments.

[0107] The computer-readable storage medium may include, but is not limited to, floppy disks, optical disks, CD-ROMs (compact disc-read-only memory), magneto-optical disks, ROMs (read-only memory), RAMs (random access memory), EPROMs (erasable programmable read-only memory), EEPROMs (electrically erasable programmable read-only memory), magnetic cards or optical cards, flash memory, or other types of media / machine-readable media suitable for storing machine-executable instructions. The computer-readable storage medium may be a product not connected to a computer device or a component used in a computer device.

[0108] The terms "first," "second," "third," "fourth," "1," "2," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown in the illustrations or text descriptions.

[0109] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0110] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. A BIM-based method for binding shared parameters, characterized in that, The method includes: Obtain the shared parameters to be bound, and perform multi-dimensional conflict detection based on the shared parameters. The multi-dimensional conflict detection includes project parameter conflict detection, category-level conflict detection, family parameter conflict detection, and parameter data type mismatch detection. Once a conflict is detected, the priority of the detected conflict is obtained, and the resolution information corresponding to the conflict is obtained based on the priority. The conflict is resolved and the shared parameters are bound based on the resolution information.

2. The BIM-based shared parameter binding method according to claim 1, characterized in that, The project parameter conflict detection includes: Traverse the project parameter set under the target category in the BIM project and compare the parameter names of the project parameters in the project parameter set with those of the shared parameters; If the shared parameter contains the same parameter name as the project parameter, then a project parameter conflict is determined to exist.

3. The BIM-based shared parameter binding method according to claim 1, characterized in that, The category-level conflict detection includes: Traverse the existing binding information in the target category of the BIM project, whereby the binding information includes the binding method of the parameters; If, based on the binding information and the binding method of the shared parameter, it is determined that there exists a shared parameter with the same name as the parameter but a different binding method, then it is determined that a conflict of the same name for instance / type parameter has been detected.

4. The BIM-based shared parameter binding method according to claim 1, characterized in that, The family parameter conflict detection includes: Scan the parameter definition set corresponding to the target category in the BIM project, and compare the family parameter definition information of each family parameter in the parameter definition set with the shared parameter; If the shared parameters conflict with the family parameter definition information, then a family parameter conflict is detected.

5. The BIM-based shared parameter binding method according to claim 1, characterized in that, The parameter data type mismatch detection includes: Based on the detection results of the project parameter conflict detection and the family parameter conflict detection, obtain the matching objects that have the same parameter name as the shared parameters. The matching objects include project parameters and family parameters. Identify the first object among the shared parameters that has the same parameter name as the object to be matched; If the data type of the first object is different from that of the object to be matched, then it is determined that a parameter data type mismatch has been detected.

6. The BIM-based shared parameter binding method according to claim 1, characterized in that, The process of obtaining the priority of detected conflicts includes: The priority of a conflict is determined based on its impact on the integrity of the BIM model, and the priority includes critical, high, medium and low.

7. The BIM-based shared parameter binding method according to claim 1, characterized in that, Based on the priority, the resolution information corresponding to the conflict is obtained, including: Configure a set of resolvable options for each conflict based on its priority; The conflict and the set of resolvable options are displayed based on the priority order, and the resolution information corresponding to the conflict is obtained. The resolution information is generated based on the set of resolvable options.

8. The BIM-based shared parameter binding method according to claim 1, characterized in that, The step of resolving conflicts and binding the shared parameters based on the resolution information includes: The conflict is resolved based on the resolution options corresponding to the aforementioned resolution information; Once the conflict resolution is confirmed, a binding operation sequence is generated, and the shared parameters are bound to the target category of the BIM project based on the binding operation sequence.

9. An electronic device, characterized in that, The method includes a processor and a memory, the processor being communicatively connected to the memory, the memory storing program data, and the program data being used to execute the method as described in any one of claims 1-8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-8.

Images