Multi-design-platform-oriented BIM component data collaborative management system and application method

Abstract

The invention discloses a BIM component data collaborative management system oriented to multiple design platforms and an application method. The system comprises a data layer which comprises a permission module, a standard specification library, a component rule library, a component extension library, a component instance library, a material library, a BIM model unit library and a BIM model library; the application layer provides platform adapters which are in one-to-one correspondence with the design platforms and are integrated on the design platform clients, and users of the design platforms access the data layer according to access permissions and the corresponding platform adapters; the platform adapter calls native data and an application programming interface of a component of the corresponding design platform, and converts the native data and the application programming interface into a prefabricated standardized data format and an API interface respectively; the application layer further comprises a component extension module, an attribute coding module, an instance storage module and an inspection module. According to the method, the current state of data dispersion and different standard execution in traditional multi-platform collaboration is changed, and homologous production and consistent management and control of full-project data are realized at the component level.

Description

Technical Field

[0001] This invention relates to the field of BIM technology, specifically to a BIM component data collaborative management system and application method for multiple design platforms. Background Technology

[0002] In the implementation of BIM in large-scale engineering projects, it is often necessary to integrate multiple design platforms such as Revit, Bentley, and 3DE / Catia. Due to differences in component data definition methods, data structures, and storage formats across different platforms, and the incompatibility of their application programming interfaces and file formats, serious data heterogeneity problems arise. Existing technical solutions typically only provide component databases for a single platform, failing to provide a unified component data source for multi-platform collaborative design. This leads to semantic loss, version inconsistencies, and inconsistent standard implementation during cross-platform data exchange.

[0003] At the data management level, traditional Excel spreadsheets or database management methods suffer from the following technical bottlenecks: First, core standard data such as component coding rules and attribute rules are fixed, making it unable to adapt to the dynamic addition of new component types during project execution, and lacking a collaborative mechanism for online application, review, automatic coding, and synchronization to various design ends. Second, the massive amount of component instance data (up to hundreds of millions of records) lacks centralized and unified structured storage and management, resulting in low data query and statistical efficiency, and the global unique identifier for components is prone to duplication. Finally, reusable model unit files and component standard rule libraries are independent of each other, making it difficult for designers to quickly and accurately find and call model resources that conform to the current project standards, resulting in low model reuse rates.

[0004] Therefore, how to build an integrated technical system that can connect to multiple platforms, support dynamic standard expansion, and achieve unified data management has become a key technical challenge in promoting the deep collaborative application of BIM technology in large and complex engineering projects. Summary of the Invention

[0005] In view of this, the present invention provides a BIM component data collaborative management system and application method for multiple design platforms, which can solve the above-mentioned technical problems.

[0006] To solve the above-mentioned technical problems, the present invention is implemented as follows.

[0007] A BIM component data collaborative management system for multiple design platforms includes: The data layer includes a permission module, a standard specification library, a component rule library, a component extension library, a component instance library, a material library, a BIM model unit library, and a BIM model library. The system includes several modules: a permissions module for configuring access permissions for each user on each design platform; a standards and specifications library for managing fixed table data in BIM specifications; a component rule library for storing atomic component rules; a component extension library for temporarily storing dynamically added component rules based on BIM specifications and user access permissions; a component instance library for storing all attribute values ​​extracted from instantiated components; a material library for managing all material images; a BIM model unit library for managing reusable component unit models; and a BIM model library for storing all BIM models. Several component units can be combined to form a component, and several components can be combined to form a BIM model. Application Layer: Provides platform adapters integrated into the design platform client, one-to-one with the design platform. Users of each design platform access the data layer according to their access permissions and the corresponding platform adapter. The platform adapter calls the native data and application programming interface of the corresponding design platform's components and converts them into pre-made standardized data formats and API interfaces. The application layer also includes component extension modules, attribute encoding modules, instance storage modules, and inspection modules.

[0008] Preferably, after each module in the data layer is initialized according to the BIM specifications, the standard specification library and the component rule library together constitute the standard data source of the project; the BIM model unit library and the material library serve as reusable resource libraries bound to the BIM specifications, providing unified resources for modeling on various design platforms. When a user encounters a new component type not covered by the standard data source while designing through the design platform, the component extension library adds a temporary component rule and automatically pushes the new temporary component rule to the reviewers pre-assigned by profession to trigger the review process; after the review is approved, the new temporary component rule is uploaded to the component rule library and deleted from the component extension library. The component instance library stores the attribute values ​​of instantiated components, centrally stores the attribute values ​​of instantiated components, and manages the uniqueness of instantiated components; wherein, the attribute values ​​of instantiated components are obtained by the platform adapter corresponding to the design platform after converting the instantiated components designed in the design platform into a pre-made standardized data format; The component rule base performs compliance checks on the attribute values ​​of instantiated components in the component instance library based on the stored component rules, triggering the deletion of attribute values ​​of instantiated components whose verification results are unqualified; it also performs collaborative checks on BIM models in the BIM model library based on the stored component rules. The access control module controls the access and execution permissions of users in each role in real time.

[0009] Preferably, the standard specification library manages the fixed tabular data in the BIM specification, wherein the standard specification library stores the tabular data related to attributes, codes and BIM management in the BIM specification in the form of database tables; The component rule base stores atomic component rules. The component rule base stores all component rules related to a component in the form of a database table. The component rules represent the classification rules, modeling methods, modeling accuracy, and additional attribute rules that the component should follow in the BIM modeling process.

[0010] Preferably, during the modeling process using a BIM component data collaborative management system for multiple design platforms, when a component rule library lacks a suitable component rule for the component unit model to be built, an authorized user extends the BIM specification to create a new temporary component rule and uploads the temporary component rule to the component extension library. After detecting the addition of a temporary component rule in the component extension library, the new temporary component rule is automatically pushed to the pre-assigned reviewers according to their professions for review. After the review is approved, the new temporary component rule is uploaded to the component rule library, and at the same time, the new temporary component rule is deleted from the component extension library.

[0011] Preferably, the authorized user extends the BIM specification to form new temporary component rules. The extension method is as follows: the component extension module reuses existing data that is applicable to the new temporary component rules from the component rules in the component rule library; generates new temporary component rules based on the BIM specification, design information, and reused data; checks the new temporary component rules; after passing the check, stores them in the component extension library; and triggers a message that a new temporary component rule has been added to the component extension library.

[0012] Preferably, the newly added temporary component rules are automatically pushed to pre-assigned reviewers for review. After the review is approved, the reviewers determine the major category, intermediate category, and minor category to which the component corresponding to the newly added temporary component rule belongs, and generate a component classification code for the newly added temporary component rule. The component classification code includes, in order, the major category code, the intermediate category code, and the minor category code. The determination method for major category codes, intermediate category codes, and minor category codes is as follows: Query the category name in the component rule library. If the category to which the newly added temporary component rule belongs exists, obtain the category code corresponding to the category. Otherwise, add 1 to the category code with the largest value among the existing category codes and use it as the category code corresponding to the category to which the newly added temporary component rule belongs. The major category name of the major category to which the newly added temporary component rule belongs and the minor category name of the minor category to which it belongs are combined. If the combination to which the newly added temporary component rule belongs exists, the minor category code corresponding to the minor category is obtained; otherwise, the value of the largest minor category code corresponding to the major category of the combination is incremented by 1, and this value is used as the minor category code corresponding to the minor category to which the newly added temporary component rule belongs. Add 1 to the value of the largest minor class code corresponding to the middle class of the combination, and use it as the minor class code corresponding to the minor class to which the newly added temporary component rule belongs.

[0013] Preferably, the component instance library stores the attribute values ​​of instantiated components. The attribute values ​​of instantiated components are obtained by adding and encoding attributes to the components that make up the BIM model after the BIM model is created in the design platform, and then the instance entry module extracts the attribute values ​​of each instantiated component.

[0014] Preferably, the access permissions configured in the permission module include functional permissions, professional permissions, bid section permissions, and secondary sub-project permissions. Functional permissions are used to control the functions of the design platform that users can use; professional permissions are used to allocate professional-related data to each user; and bid section permissions are used to assign a bid section to each user, allowing the user to access data related to that bid section.

[0015] Preferably, the methods for instantiating components and storing them in the library include: Invalid components are filtered out, and the remaining components are used as components to be instantiated in the database. The information of the components to be instantiated in the database is extracted, including business key attributes and technical attributes in the general attributes. Among them, the general attributes include globally unique identifiers (GUIDs), sub-projects, component major categories, component minor categories, and component subcategories; the technical attributes include system type, geometric dimensions, and materials. The extracted information is mapped according to the target database table structure to form a data table; The model file name of the BIM model to which the component to be instantiated belongs and the component's globally unique identifier are used as joint search keywords to search the component instance library. If the joint search keywords are found, the component to be instantiated is marked as a component not to be instantiated; otherwise, the component to be instantiated is marked as a component to be instantiated. Integrate all the data tables corresponding to the instantiated components that need to be added to the database to form a dataset; upload the dataset in batches with one click to the component instance library; Next, a uniqueness check is performed on the joint search keywords in the component instance library. If there is an instantiated component that does not meet the uniqueness requirements, its global unique identifier is modified in the design platform until the uniqueness check of the joint search keywords in the component instance library passes.

[0016] A method for collaborative application of BIM component data across multiple design platforms, using the aforementioned collaborative management system for BIM component data across multiple design platforms, includes: Step S1: Based on the project's BIM specifications, initialize the standard specification library, component rule library, BIM model unit library, and material library, and input basic standard data and resources; Step S2: Based on their own permissions, the modelers query and download the required component unit models from the BIM model unit library to the local design platform for loading and instantiation, thus completing geometric modeling; according to the component rules in the component rule library, they add attributes to the instantiated components and encode the components according to the coding rules specified in the BIM specifications; and according to the rule association, they obtain material images from the material library and attach them to the components. When the modeling process finds that the component rule library lacks applicable component rules, the modeler uses the component extension module to extend it to form new temporary component rules that conform to BIM specifications, and uploads the temporary component rules to the component extension library. The status of the temporary component is set to pending review, and the component extension module automatically creates and distributes review tasks. Simultaneously, model units corresponding to the temporary component rules are created and submitted to the BIM model unit library for associated storage. After the review is approved, the newly added temporary component rules are automatically coded, uploaded to the component rule library, and deleted from the component extension library. Step S3: The attribute encoding module adds attributes to the components. After the components have been modeled and attribute-added, the instance storage module calls the platform adapter corresponding to the design platform to extract the attributes of the instantiated components, converts the extracted attributes into a pre-made standardized data format, performs uniqueness verification on the globally unique identifiers in the extracted attributes, and stores the attributes of the instantiated components in the component instance library after the verification is passed; the BIM model file corresponding to the BIM model is stored in the BIM model library. The inspection module performs compliance checks on the component instance attributes in the design platform based on the component rule base. If problems are found, modifications are made in the design platform until no problems are found before updating the attributes to the component instance base and updating the model file to the BIM model base.

[0017] The present invention provides a computer-readable storage medium storing a plurality of instructions; the plurality of instructions are used by a processor to load and execute the method as described above.

[0018] The present invention provides an electronic device, characterized in that the electronic device comprises: A processor is used to execute multiple instructions; Memory, used to store multiple instructions; The plurality of instructions are to be stored in the memory and loaded and executed by the processor as described above.

[0019] Beneficial effects: This architecture enables a multi-platform BIM collaborative work mode based on a unified data source. By constructing a data management system centered on a "unified backend data service layer" and equipping different BIM design platforms (such as Revit, Bentley, and 3DE / Catia) with dedicated "platform adapters," each design end interacts with the backend service layer through these adapters. This ensures that operations such as modeling, attribute assignment, and component coding all utilize the same standard data in real time. Simultaneously, instance data generated by the design is also centrally managed in a "component instance library" through the adapters. This architecture fundamentally changes the situation of fragmented data and inconsistent standard implementation in traditional multi-platform collaboration, achieving for the first time, the same source production and consistent control of project data at the component level.

[0020] A dynamic management mechanism for online collaborative expansion of component rules has been established: a "Component Expansion Library" is set up as an online temporary storage repository, and a "Review Process" reviews component rule data before adding it to the library, ensuring the accuracy of the component rule data. Designers can instantly initiate new rule requests in the BIM design platform; after the request is submitted, the system automatically prompts the relevant reviewers, and after manual review and approval, automatically completes the coding generation and synchronizes it with the rule library. This mechanism enables the project component rule library to be safely and orderly expanded and updated dynamically along with the project implementation, ensuring the timeliness and standardization of standards and solving the pain point of standards lagging behind project needs.

[0021] The systematic functional design significantly improves collaboration efficiency and data reliability: Regarding improved design efficiency, the strong association between the "BIM Model Unit Library," "Material Library," and "Component Rule Library" transforms resource retrieval from inefficient filename searching to precise matching based on rule codes. This allows designers to quickly reuse standardized resources, greatly reducing repetitive modeling work. Global uniqueness checks are performed in the "Component Instance Library" to ensure the uniqueness of each component.

[0022] The entire system forms a complete technical closed loop from standard setting, modeling application, data collection to compliance checks (such as consistency verification), providing an efficient, stable and reliable integrated support platform for the digital collaborative construction of large and complex projects. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of the architecture of the BIM component data collaborative management system for multiple design platforms according to the present invention.

[0024] Figure 2Application process for BIM component data collaborative management system.

[0025] Figure 3 This is a schematic diagram of the interface of the BIM component data collaborative management system (component rule base).

[0026] Figure 4 This is a schematic diagram of the interface of the BIM component data collaborative management system (component extension library).

[0027] Figure 5 This is a schematic diagram of the interface of the BIM component data collaborative management system (component instance library).

[0028] Figure 6 This is a schematic diagram of the component rule extension module interface.

[0029] Figure 7 This is a schematic diagram of the instance import module interface.

[0030] Figure 8 This is a schematic diagram of the model unit library interface.

[0031] Figure 9 This is a schematic diagram of the material library interface. Detailed Implementation

[0032] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0033] like Figure 1 As shown, this invention proposes a BIM component data collaborative management system for multiple design platforms, comprising: The data layer includes a permission module, a standard specification library, a component rule library, a component extension library, a component instance library, a material library, a BIM model unit library, and a BIM model library. The system includes several modules: a permissions module for configuring access permissions for each user on each design platform; a standards and specifications library for managing fixed table data in BIM specifications; a component rule library for storing atomic component rules; a component extension library for temporarily storing dynamically added component rules based on BIM specifications and user access permissions; a component instance library for storing all attribute values ​​extracted from instantiated components; a material library for managing all material images; a BIM model unit library for managing reusable component unit models; and a BIM model library for storing all BIM models. Several component units can be combined to form a component, and several components can be combined to form a BIM model. Application Layer: This layer provides platform adapters integrated into the design platform client, each corresponding to a specific design platform. Users of each design platform access the data layer based on their access permissions and the corresponding platform adapter. The platform adapter calls the native data and application programming interfaces of the corresponding design platform's components, converting them into pre-defined standardized data formats and API interfaces. The application layer also includes component extension modules, attribute encoding modules, instance storage modules, and inspection modules. After initialization according to BIM specifications, the standard specification library and component rule library together constitute the project's standard data source. The BIM model unit library and material library serve as reusable resource libraries bound to BIM specifications, providing unified resources for modeling across various design platforms. When a user encounters a new component type not covered by the standard data source while designing through the design platform, the component extension library adds a temporary component rule and automatically pushes the new temporary component rule to the reviewers pre-assigned by profession to trigger the review process; after the review is approved, the new temporary component rule is uploaded to the component rule library and deleted from the component extension library. The component instance library stores the attribute values ​​of instantiated components, centrally stores the attribute values ​​of instantiated components, and manages the uniqueness of instantiated components; wherein, the attribute values ​​of instantiated components are obtained by the platform adapter corresponding to the design platform after converting the instantiated components designed in the design platform into a pre-made standardized data format; The component rule base performs compliance checks on the attribute values ​​of instantiated components in the component instance library based on the stored component rules, triggering the deletion of attribute values ​​of instantiated components whose verification results are unqualified; it also performs collaborative checks on BIM models in the BIM model library based on the stored component rules. The access control module controls the access and execution permissions of users in each role in real time.

[0034] The standards and specifications library manages the fixed tabular data in BIM specifications. Specifically, it stores the tabular data related to attributes, codes, and BIM management in the form of database tables. This type of tabular data is relatively fixed; once a project is initialized, it generally does not require modification during application.

[0035] The component rule base stores atomic component rules. This rule base is a database table that stores all component-related rules. Component rules represent the classification rules, modeling methods, modeling accuracy, and additional attribute rules that components should follow during the BIM modeling process, such as... Figure 3 As shown.

[0036] In this invention, the standard specification library includes tables for specialties, stages, sections, functional areas, and functional systems. The data in the standard specification library is generally fixed and can be directly entered from the specifications. The component rule library includes specialties, major component categories, intermediate component categories, minor component categories, feature values ​​(rules), feature values, classification codes, modeling methods, family name rules, family names, family type rules, family type names, modeling accuracy, design attributes, construction attributes, uploader, upload time, status, and reviewer. Initial entry is performed according to the table data in the standard specification library. After entry, classification codes are generated according to the coding rules, and dynamically expanded during BIM implementation.

[0037] Furthermore, during modeling using a BIM component data collaborative management system for multiple design platforms, when a component rule library lacks a suitable component rule for the component unit model to be built, authorized users can extend the BIM specification to create new temporary component rules and upload these temporary rules to the component extension library, such as... Figure 4 As shown. After detecting the addition of a temporary component rule in the component extension library, the new temporary component rule is automatically pushed to the pre-assigned reviewers according to their specialties for review; after the review is approved, the new temporary component rule is uploaded to the component rule library, and at the same time, the new temporary component rule is deleted from the component extension library.

[0038] In this invention, the new temporary component rules are managed through a component extension table, which includes the following: specialty, major component category, intermediate component category, minor component category, feature value (rule), feature value, classification code, modeling method, family name rule, family name, family type rule, family type name, modeling accuracy, design attributes, construction attributes, uploader, upload time, status, reviewer, etc.

[0039] Furthermore, the authorized user extends and forms new temporary component rules based on BIM specifications. The extension method is as follows: the authorized user extends and forms new temporary component rules based on BIM specifications. The extension module reuses existing data applicable to the new temporary component rules from the component rule library; generates new temporary component rules based on BIM specifications, design information, and reused data; checks the new temporary component rules; after passing the check, stores them in the component extension library; and triggers a message that a new temporary component rule has been added to the component extension library. The component extension module interface is as follows. Figure 6 As shown.

[0040] In this invention, for each selected component, its general attribute information is extracted, including key parameters such as specialty, component category, component subcategory, component minor category, and feature values. The BIM component data collaborative management system verifies whether these attributes are completely filled in, and records error information for components with incomplete attributes. The BIM component data collaborative management system compares the component classification information with the component rule base to identify component types that do not exist in the rule base. For component types that already exist in the rule base, the system skips processing; for new component types, the BIM component data collaborative management system marks them as objects that need to be expanded. All component information that needs to be expanded is collected, including the component's complete classification, feature values, reviewer information, etc. The system performs deduplication to ensure that only one expansion record is generated for the same component type.

[0041] During the expansion process, a component expansion management interface is created and initialized, and the collected expansion data is passed to the interface layer. The interface will display information about all components that need to be expanded. In addition to automatically retrieving the rule data to be expanded from the model, two main data entry methods are provided, allowing users to choose the most suitable method based on their actual situation: (1) Batch import of Excel templates Users first download the standard Excel template provided by the BIM Component Data Collaborative Management System. This template has all necessary fields and formatting requirements pre-defined. Following the examples in the template, users fill in the component's classification information (profession, major category, intermediate category, minor category, etc.) and specific data such as component type and specifications, line by line. After completion, users can use the import function in the system menu to batch upload the data to the BIM Component Data Collaborative Management System.

[0042] (2) Interface input For small amounts of data or special cases, users can manually enter data directly in the component extension module interface. Clicking the "Add Row" button will provide a blank record row, and the user needs to fill in the data field by field. This method is suitable for fine-grained data maintenance of individual components.

[0043] When a new component is similar to an existing component, the copy function can be used. First, find similar component records using search criteria, then create a new record using the copy function, and modify the differences in the original record. This method ensures data standardization while improving data entry efficiency.

[0044] After the user completes the basic information entry, they can select the component row that requires additional data rules and choose the "Get Rules" function via the right-click menu. The BIM component data collaborative management system will automatically match the corresponding rules from the rule library, including family naming rules, family type naming rules, modeling accuracy requirements, attribute settings, etc. The system will automatically fill in these technical parameters according to the component classification to ensure compliance with industry standards.

[0045] After data entry is complete, click the "Check" function. The system will execute several strict validation rules, including format checks, rule compliance checks, data integrity checks, uniqueness checks, and business logic checks. The validation results will be displayed visually using color coding: red indicates a conflict with the official database, yellow indicates an existing record in the user database, blue indicates a null value issue, green suggests standardization recommendations, and pink marks duplicate records.

[0046] Based on the color-coded prompts provided in the inspection results, users need to address each problematic data item one by one. For formatting issues, the automatic standardization function can be enabled, and the system will automatically correct punctuation, spaces, and other formatting problems. For business rule issues, the data content needs to be manually adjusted according to system prompts. After corrections are completed, the inspection needs to be re-run until all verification items pass. All verified component information is saved to an extended table in the database, and the component status is automatically set to "Submitted," entering the pending review state. The system will provide feedback indicating successful submission, confirming that the data has entered the review process.

[0047] System administrators can view all pending component extension requests through the component extension library in the management backend. Based on the component's professional category and the reviewers' job responsibilities, administrators assign appropriate reviewers to each request. The system records the review assignment information and automatically notifies the relevant reviewers to process the review task promptly.

[0048] Furthermore, the newly added temporary component rules are automatically pushed to pre-assigned reviewers for review. After the review is approved, the reviewers determine the major category, intermediate category, and minor category to which the component corresponding to the newly added temporary component rule belongs, and generate a component classification code for the newly added temporary component rule. The component classification code includes, in order, the major category code, the intermediate category code, and the minor category code. The determination method for major category codes, intermediate category codes, and minor category codes is as follows: Query the category name in the component rule library. If the category to which the newly added temporary component rule belongs exists, obtain the category code corresponding to the category. Otherwise, add 1 to the category code with the largest value among the existing category codes and use it as the category code corresponding to the category to which the newly added temporary component rule belongs. The major category name of the major category to which the newly added temporary component rule belongs and the minor category name of the minor category to which it belongs are combined. If the combination to which the newly added temporary component rule belongs exists, the minor category code corresponding to the minor category is obtained; otherwise, the value of the largest minor category code corresponding to the major category of the combination is incremented by 1, and this value is used as the minor category code corresponding to the minor category to which the newly added temporary component rule belongs. Add 1 to the value of the largest minor class code corresponding to the middle class of the combination, and use it as the minor class code corresponding to the minor class to which the newly added temporary component rule belongs.

[0049] In this invention, the auditor reviews the newly expanded components in the component extension library and generates a component classification code after confirming that there are no errors. The component classification code rule is {major category code}.{intermediate category code}.{minor category code}, and each category code is a 3-digit number, padded with leading zeros if less than 3 digits. The component classification code is generated according to the following steps.

[0050] (1) Extended categories If the "major category" of the new extended component cannot be found in the component rule base table, the maximum value of the existing major category code is retrieved, and 1 is added to it (e.g., if the existing maximum is "002", the new code is "003", a fixed 3-digit number, padded with 0 if necessary). The intermediate and minor category codes are 001 by default. The major, intermediate, and minor category codes are connected with "." to form the classification code of the new component. The currently selected data record is written to the component classification table.

[0051] (2) Extended Class If a "major category" can be found in the component rule base table, but a "major category + sub-category" combination cannot be found, query the component classification table to obtain the existing major category code; query the maximum value of the existing sub-category codes under this major category and add 1; the sub-category code is "001"; generate a new category full code by {existing major category code}.{new sub-category code}.001; and write the currently selected data record into the component classification table.

[0052] (3) Extended subclasses The "major category + intermediate category" combination can be found in the component rule base table, but the "minor category" cannot be found. Retrieve the existing codes corresponding to the "major category + intermediate category" from the component rule base table; generate a new "minor category code": query the maximum value of the existing minor category codes under the "major category + intermediate category" and increment it by 1; Generate a new category full code according to the rule {existing major category code}.{existing intermediate category code}.{new minor category code}; write the currently selected data record into the component classification table.

[0053] Fixed encoding length: The codes for major, intermediate, and minor categories are all 3 digits. If the codes are less than 3 digits, leading zeros are added to ensure a consistent encoding format. This invention employs a unique incremental logic. All new codes are generated based on "the existing maximum code + 1", thus avoiding code duplication. Real-time database synchronization: New category information (major category, intermediate category, minor category, corresponding code) generated by the extension is written to the component classification table in real time, ensuring that subsequent components of the same type can be directly matched without repeated extension.

[0054] Add the approved components to the database. Delete the records in the component extension library and add the approved records to the component rule library.

[0055] The component instance library stores the attribute values ​​of instantiated components. These attribute values ​​are obtained after the BIM model is created in the design platform, by adding and encoding attributes to the components that make up the BIM model, and then the instance entry module extracts the attribute values ​​of each instantiated component. For example... Figure 5 As shown.

[0056] This invention provides a specific embodiment for extracting all attribute values ​​from instantiated components and storing them in a component instance library.

[0057] Instantiated components are added to the library through the instance addition module, such as... Figure 7 As shown, the attribute information specified in the project is extracted from the components and uploaded to the instance database table in the component instance library. After being uploaded, a duplicate check of the GUID is performed to ensure that the GUID of each component in the entire model is unique.

[0058] The access permissions configured in the permission module include functional permissions, professional permissions, bid section permissions, and secondary sub-project permissions. Functional permissions are used to control the functions of the design platform that users can use; professional permissions are used to assign professional-related data to each user; and bid section permissions are used to assign a bid section to each user, allowing the user to access the data related to that bid section.

[0059] The methods for instantiating components and storing them in the library include: Invalid components are filtered out, and the remaining components are used as components to be instantiated in the database. The information of the components to be instantiated in the database is extracted, including business key attributes and technical attributes in the general attributes. Among them, the general attributes include globally unique identifiers (GUIDs), sub-projects, component major categories, component minor categories, and component subcategories; the technical attributes include system type, geometric dimensions, and materials. The extracted information is mapped according to the target database table structure to form a data table; The model file name of the BIM model to which the component to be instantiated belongs and the component's globally unique identifier are used as joint search keywords to search the component instance library. If the joint search keywords are found, the component to be instantiated is marked as a component not to be instantiated; otherwise, the component to be instantiated is marked as a component to be instantiated. Integrate all the data tables corresponding to the instantiated components that need to be added to the database to form a dataset; upload the dataset in batches with one click to the component instance library; Next, a uniqueness check is performed on the joint search keywords in the component instance library. If there is an instantiated component that does not meet the uniqueness requirements, its global unique identifier is modified in the design platform until the uniqueness check of the joint search keywords in the component instance library passes.

[0060] (1) Component element selection filtering The system filters out unsupported or meaningless element types (such as views, drawings, annotations, etc.) based on preset filtering conditions; it checks whether each component has a valid type definition to ensure that the necessary classification information can be obtained. Any component that fails the filter will be recorded in the error list with a detailed explanation of the reason for the filter, for the user to review later.

[0061] (2) Component data extraction Comprehensive information collection is performed on each filtered component. Parameter data is collected from two dimensions: first, key business attributes (GUID, sub-project, component category, component sub-category, and component minor category, etc.) are extracted from a predefined list of "general attributes"; second, the technical attributes of the component (such as system type, geometric dimensions, and materials) are obtained.

[0062] (3) Data standardization All extracted component data are standardized and mapped according to the target database table structure. The program automatically records operation metadata, including model file information, creator, timestamp, processing status, etc., to form a complete instance dataset.

[0063] (4) Batch warehousing and result feedback After user confirmation, the system performs batch data import operations on the prepared standardized data through the established database connection. Data consistency is ensured throughout the process via transactions. Upon completion, the system displays a detailed results summary interface, including total processing time, the number of successfully imported components, a list of filtered components and the reasons for filtering, any errors or warnings encountered, and allows users to perform further operations or view detailed error diagnosis reports, ensuring transparency and traceability of the operation process.

[0064] (5) After the instance is entered into the database, a GUID duplication check should be performed on all instance data to ensure that the GUID of each component is unique. If there is a duplication, the GUID attribute of the relevant component should be modified in the design platform until the GUID of the entered data is no longer duplicated.

[0065] This invention provides a specific embodiment for extracting component coding information from a model and performing compliance checks. The coding check is implemented through a checking module, which verifies selected components from multiple dimensions to ensure that the attributes and coding of each component meet project specification requirements. After the check is completed, a detailed check report is output to guide users in correcting problematic components.

[0066] The specific implementation method for attribute encoding inspection is as follows: (1) Load the coding rule library and component instance library data from the backend database. Parse the project information according to the model file name and query the corresponding basic coding dictionary such as the project three-level structure table, professional table, and stage table. Load the component classification rule library and preload the component instance data corresponding to the model to prepare for subsequent consistency checks.

[0067] (2) Inspection of the standardization of component coding Perform a coding compliance check on each filtered component. Extract all necessary common attribute values ​​from the component (including sub-item project, specialty, system classification, component major category, component minor category, component sub-category, etc.). Verify attribute completeness to ensure all necessary attributes are filled in and conform to specifications. Check if the component's globally unique identifier exists and is formatted correctly. Regenerate standard codes based on the extracted attributes and compare them segment by segment with the component's existing codes to verify the correctness of the coding format and content.

[0068] (3) Data consistency and repeatability verification Perform consistency verification between the component data and the backend instance library, checking whether the component attributes, encoding values, and globally unique identifiers are consistent with the records in the instance library. Perform a globally unique identifier duplication check to ensure that the globally unique identifier of each component in the entire model is unique; if duplicate identifiers are found, record the conflicting component information.

[0069] (4) Summary of inspection results and identification of problems All inspection results are summarized and statistically analyzed, categorized, and the quantity and detailed information of each type of problematic component are recorded. All problematic components are highlighted in the model, providing a visual location function. A detailed inspection report is generated. For problems discovered during the inspection, the attributes and codes of the relevant components are modified in the design platform until the inspection is passed.

[0070] The steps of creating the model, adding attribute codes to the components, and adding materials in this invention are as follows: Launch the model unit management module interface. On the left, model units are managed in a structured tree format, categorized into three levels: specialty, major component category, and minor component category. Selecting a node in the structured tree displays the model unit's information in a table on the right, including file name, file address, image address, status, and thumbnail.

[0071] Select the model unit to load into the current model: First, set the save path for the model unit and thumbnail, download it to the set directory, and then load it into the design platform.

[0072] The loaded model units are instantiated and arranged to complete the model creation.

[0073] Add attributes and codes to the created model according to project standards.

[0074] Add material attributes to each component in the model, select appropriate material images based on the component's classification information and attach them to the material attributes. Switch to material rendering mode in the design platform to see the material display effect of the component.

[0075] The material library manages all material images, such as Figure 9 As shown, the material library stores material images used uniformly throughout the project. Before adding materials to the BIM model, prepare the material images, name them according to the standard naming rules, and submit them to the management for review before adding them to the library. When project members open the model on the design platform, they should download all material images from the material library and store them in the default material path of the design platform. This ensures that the material effects can be viewed correctly after opening the model.

[0076] BIM model unit library manages reusable component unit models, such as Figure 8 As shown. For component unit models, reusable component unit models and corresponding thumbnails are created for different design platforms. For Revit, these are family files; for Bentley, they are unit files; and for Catia, they are .part files. These files are named in the format "Component Class_Component Subclass". One component in the component rule base corresponds to one row of data. Selecting a row of data in the component rule base retrieves information such as profession, family name, family type name, and classification code. Then, the file and thumbnail to be uploaded are selected, and the file is uploaded to the specified file directory on the server. Simultaneously, relevant data is recorded in the family library file information record table.

[0077] The BIM model library stores all BIM models. After the component codes and instantiated components are stored in the component instance library, the files corresponding to all BIM models are stored in the BIM model library.

[0078] This invention also provides a method for collaborative application of BIM component data across multiple design platforms, such as... Figure 2 Using the BIM component data collaborative management system as described above, the method includes: Step S1: Based on the project's BIM specifications, initialize the standard specification library, component rule library, BIM model unit library, and material library, and input basic standard data and resources; Step S2: Based on their own permissions, the modelers query and download the required component unit models from the BIM model unit library to the local design platform for loading and instantiation, thus completing geometric modeling; according to the component rules in the component rule library, they add attributes to the instantiated components and encode the components according to the coding rules specified in the BIM specifications; and according to the rule association, they obtain material images from the material library and attach them to the components. When the modeling process finds that the component rule library lacks applicable component rules, the modeler uses the component extension module to extend it to form new temporary component rules that conform to BIM specifications, and uploads the temporary component rules to the component extension library. The status of the temporary component is set to pending review, and the component extension module automatically creates and distributes review tasks. Simultaneously, the component corresponding to the temporary component rule is created and submitted to the BIM model unit library for associated storage. After the review is approved, the newly added temporary component rule is automatically coded, uploaded to the component rule library, and deleted from the component extension library. Step S3: The attribute encoding module adds attributes to the components. After the components have been modeled and attribute-added, the instance storage module calls the platform adapter corresponding to the design platform to extract the attributes of the instantiated components, converts the extracted attributes into a pre-made standardized data format, performs uniqueness verification on the globally unique identifiers in the extracted attributes, and stores the attributes of the instantiated components in the component instance library after the verification is passed; the BIM model file corresponding to the BIM model is stored in the BIM model library. The inspection module performs compliance checks on the component instance attributes in the design platform based on the component rule base. If problems are found, modifications are made in the design platform until no problems are found before updating the attributes to the component instance base and updating the model file to the BIM model base.

[0079] The specific embodiments described above only illustrate the design principles of the present invention. The shapes and names of the components in this description may differ and are not limited. Therefore, those skilled in the art can modify or make equivalent substitutions to the technical solutions described in the foregoing embodiments; and these modifications and substitutions do not depart from the inventive spirit and technical solutions of the present invention, and should all fall within the protection scope of the present invention.

Claims

1. A BIM component data collaborative management system for multiple design platforms, characterized in that, include: The data layer includes a permission module, a standard specification library, a component rule library, a component extension library, a component instance library, a material library, a BIM model unit library, and a BIM model library. The system includes several modules: a permissions module for configuring access permissions for each user on each design platform; a standards and specifications library for managing fixed table data in BIM specifications; a component rule library for storing atomic component rules; a component extension library for temporarily storing dynamically added component rules based on BIM specifications and user access permissions; a component instance library for storing all attribute values ​​extracted from instantiated components; a material library for managing all material images; a BIM model unit library for managing reusable component unit models; and a BIM model library for storing all BIM models. Several component units can be combined to form a component, and several components can be combined to form a BIM model. Application Layer: Provides platform adapters integrated into the design platform client, one-to-one with the design platform. Users of each design platform access the data layer according to their access permissions and the corresponding platform adapter. The platform adapter calls the native data and application programming interface of the corresponding design platform's components and converts them into pre-made standardized data formats and API interfaces. The application layer also includes component extension modules, attribute encoding modules, instance storage modules, and inspection modules.

2. The system as described in claim 1, characterized in that, After each module in the data layer is initialized according to the BIM specifications, the standard specification library and the component rule library together constitute the standard data source of the project; the BIM model unit library and material library serve as reusable resource libraries bound to the BIM specifications, providing unified resources for modeling on various design platforms. When a user encounters a new component type not covered by the standard data source while designing through the design platform, the component extension library adds a temporary component rule and automatically pushes the new temporary component rule to the reviewers pre-assigned by profession to trigger the review process; after the review is approved, the new temporary component rule is uploaded to the component rule library and deleted from the component extension library. The component instance library stores the attribute values ​​of instantiated components, centrally stores the attribute values ​​of instantiated components, and manages the uniqueness of instantiated components; wherein, the attribute values ​​of instantiated components are obtained by the platform adapter corresponding to the design platform after converting the instantiated components designed in the design platform into a pre-made standardized data format; The component rule base performs compliance checks on the attribute values ​​of instantiated components in the component instance library based on the stored component rules, triggering the deletion of attribute values ​​of instantiated components whose verification results are unqualified; it also performs collaborative checks on BIM models in the BIM model library based on the stored component rules. The access control module controls the access and execution permissions of users in each role in real time.

3. The system as described in claim 2, characterized in that, The Standards and Specifications Library manages the fixed tabular data in BIM specifications. Specifically, the Standards and Specifications Library stores the tabular data related to attributes, codes, and BIM management in BIM specifications in the form of database tables. The component rule base stores atomic component rules. The component rule base stores all component rules related to a component in the form of a database table. The component rules represent the classification rules, modeling methods, modeling accuracy, and additional attribute rules that the component should follow in the BIM modeling process.

4. The system as described in claim 2, characterized in that, When using a BIM component data collaborative management system for multiple design platforms for modeling, if the component rule library lacks a suitable component rule for the component unit model to be built, authorized users can extend the BIM specification to create new temporary component rules and upload them to the component extension library. After detecting the addition of a temporary component rule in the component extension library, the new temporary component rule is automatically pushed to the pre-assigned reviewers according to their professions for review. After the review is approved, the new temporary component rule is uploaded to the component rule library, and at the same time, the new temporary component rule is deleted from the component extension library.

5. The system as described in claim 4, characterized in that, The authorized user extends the BIM specification to form new temporary component rules. The extension method is as follows: the component extension module reuses existing data that is applicable to the new temporary component rules from the component rules in the component rule library; generates new temporary component rules based on the BIM specification, design information, and reused data; checks the new temporary component rules; after passing the check, stores them in the component extension library; and triggers a message that a new temporary component rule has been added to the component extension library.

6. The system as described in claim 5, characterized in that, The newly added temporary component rules are automatically pushed to pre-assigned reviewers based on their specialties for review. After the review is approved, the reviewers determine the major category, intermediate category, and minor category to which the newly added temporary component rule belongs, and generate a component classification code for the newly added temporary component rule. The component classification code includes the major category code, intermediate category code, and minor category code in sequence. The determination method for major category codes, intermediate category codes, and minor category codes is as follows: Query the category name in the component rule library. If the category to which the newly added temporary component rule belongs exists, obtain the category code corresponding to the category. Otherwise, add 1 to the category code with the largest value among the existing category codes and use it as the category code corresponding to the category to which the newly added temporary component rule belongs. The major category name of the major category to which the newly added temporary component rule belongs and the minor category name of the minor category to which it belongs are combined. If the combination to which the newly added temporary component rule belongs exists, the minor category code corresponding to the minor category is obtained; otherwise, the value of the largest minor category code corresponding to the major category of the combination is incremented by 1, and this value is used as the minor category code corresponding to the minor category to which the newly added temporary component rule belongs. Add 1 to the value of the largest minor class code corresponding to the middle class of the combination, and use it as the minor class code corresponding to the minor class to which the newly added temporary component rule belongs.

7. The system as described in claim 6, characterized in that, The component instance library stores the attribute values ​​of instantiated components. The attribute values ​​of instantiated components are obtained by adding and encoding attributes to the components that make up the BIM model after the BIM model is created in the design platform, and then the instance entry module extracts the attribute values ​​of each instantiated component.

8. The system as described in any one of claims 1-7, characterized in that, The access permissions configured in the permission module include functional permissions, professional permissions, bid section permissions, and secondary sub-project permissions. Functional permissions are used to control the functions of the design platform that users can use; professional permissions are used to assign professional-related data to each user; and bid section permissions are used to assign a bid section to each user, allowing the user to access the data related to that bid section.

9. The system as described in claim 8, characterized in that, The methods for instantiating components and storing them in the library include: Invalid components are filtered out, and the remaining components are used as components to be instantiated in the database. The information of the components to be instantiated in the database is extracted, including business key attributes and technical attributes in the general attributes. Among them, the general attributes include globally unique identifiers (GUIDs), sub-projects, component major categories, component minor categories, and component subcategories; the technical attributes include system type, geometric dimensions, and materials. The extracted information is mapped according to the target database table structure to form a data table; The model file name of the BIM model to which the component to be instantiated belongs and the component's globally unique identifier are used as joint search keywords to search the component instance library. If the joint search keywords are found, the component to be instantiated is marked as a component not to be instantiated; otherwise, the component to be instantiated is marked as a component to be instantiated. Integrate all the data tables corresponding to the instantiated components that need to be added to the database to form a dataset; upload the dataset in batches with one click to the component instance library; Next, a uniqueness check is performed on the joint search keywords in the component instance library. If there is an instantiated component that does not meet the uniqueness requirements, its global unique identifier is modified in the design platform until the uniqueness check of the joint search keywords in the component instance library passes.

10. A method for collaborative application of BIM component data across multiple design platforms, based on the system as described in any one of claims 1 to 9, characterized in that, The method includes: Step S1: Based on the project's BIM specifications, initialize the standard specification library, component rule library, BIM model unit library, and material library, and input basic standard data and resources; Step S2: Based on their own permissions, the modelers query and download the required component unit models from the BIM model unit library to the local design platform for loading and instantiation, thus completing geometric modeling; according to the component rules in the component rule library, they add attributes to the instantiated components and encode the components according to the coding rules specified in the BIM specifications; and according to the rule association, they obtain material images from the material library and attach them to the components. When the modeling process finds that the component rule library lacks applicable component rules, the modeler uses the component extension module to extend it to form new temporary component rules that conform to BIM specifications, and uploads the temporary component rules to the component extension library. The status of the temporary component is set to pending review, and the component extension module automatically creates and distributes review tasks. Simultaneously, model units corresponding to the temporary component rules are created and submitted to the BIM model unit library for associated storage. After the review is approved, the newly added temporary component rules are automatically coded, uploaded to the component rule library, and deleted from the component extension library. Step S3: The attribute encoding module adds attributes to the components. After the components have been modeled and attribute-added, the instance storage module calls the platform adapter corresponding to the design platform to extract the attributes of the instantiated components, converts the extracted attributes into a pre-made standardized data format, performs uniqueness verification on the globally unique identifiers in the extracted attributes, and stores the attributes of the instantiated components in the component instance library after the verification is passed; the BIM model file corresponding to the BIM model is stored in the BIM model library. The inspection module performs compliance checks on the component instance attributes in the design platform based on the component rule base. If problems are found, modifications are made in the design platform until no problems are found before updating the attributes to the component instance base and updating the model file to the BIM model base.

Images