A method and system for constructing a BIM component library across software

Abstract

The application discloses a kind of cross software BIM component library construction method, establishes the data structure standard of component, constructs the component library plug-in corresponding to the modeling interface of different BIM software;Component library plug-in is analyzed to generate the component of data structure standard representation and uploaded to component library back-end server;Component library plug-in downloads the component of data structure standard representation after review and shelving from component library back-end server to local, restores component in BIM software.The application can be applicable to different BIM software, the component generated by different BIM software is represented by data structure standard, and uploaded to cloud component library back-end server, and component can also be downloaded from component library back-end server and restored to local BIM software.

Description

Technical Field

[0001] This invention relates to the field of information technology in the construction industry, specifically to a method for constructing a cross-software BIM component library, and also to a system for constructing a cross-software BIM component library. Background Technology

[0002] Currently, BIM technology has undergone significant development, and each company has established its own BIM technology system. However, due to differences in the construction phases and business scopes targeted by each company, the selection of BIM software within these systems varies greatly. Even within the same company, different specialties may use different software, resulting in a wide variety of BIM component resource formats that are not universally applicable.

[0003] Moreover, with the changing demands of the industry, the demand for BIM software has become more diversified, and the demand for domestic BIM software and domestic BIM components has become increasingly prominent.

[0004] Based on current technology, there are two methods to use BIM component resources across software, or to build a domestic BIM resource library using existing component resources: One method is to transfer components through the export and import of intermediate formats such as IFC, but this results in the loss of a large amount of data, loss of parametric functionality, and makes the components uneditable. The other method is to remodel and build the library for the current software, but this requires a significant amount of time and labor costs. Summary of the Invention

[0005] The purpose of this invention is to address the aforementioned problems in the prior art by providing a method for constructing a cross-software BIM component library, and also to provide a system for constructing a cross-software BIM component library, which can solve the problem of not being able to use BIM components across software.

[0006] The above-mentioned objectives of the present invention are achieved through the following technical means:

[0007] A method for building a cross-software BIM component library includes the following steps:

[0008] Step S1: Establish the data structure standard for the component. The data structure standard includes: component name, specialty, component category, two-dimensional thumbnail, three-dimensional thumbnail, original file of the component to be transformed, and creation logic.

[0009] Step S2: Establish the mapping relationship between the creation logic of the data structure standard components and the modeling interfaces of various BIM software, and build component library plugins corresponding to the modeling interfaces of different BIM software.

[0010] Step S3: Build a cloud-based component library backend server, set up a web-based component library management backend on the component library backend server, and install the component library plugin in the BIM software.

[0011] Step S4: Select a component in the BIM software with the component library plugin installed. The component library plugin analyzes the component's creation logic, captures the 3D and 2D thumbnails of the component in the BIM software, generates the component's name, specialty, and component category, and generates a component represented by the data structure standard. Upload the component represented by the data structure standard to the component library backend server. The web-based component library management backend reviews and lists the uploaded components.

[0012] Step S5: The component library plugin downloads the components, which have been reviewed and uploaded to the backend server of the component library, to the local machine according to the data structure standard representation. Through the mapping relationship in step S2 above, it queries the modeling interface and operation sequence of the corresponding BIM software, calls the modeling interface of the BIM software according to the operation sequence, and restores the components in the BIM software.

[0013] As described above, the creation logic includes component sketches, outlines, geometric component generation methods, generation parameters, component creation order, and Boolean operation logic; it also includes vertex coordinates, normals, triangles, UV coordinates, geometric transformation matrices, material identifiers, colors, textures, mappings, physical properties, and parameter information for generating components.

[0014] As mentioned above, the modeling interface includes interfaces for creating components, legends, sketch constraints, parameters, and materials.

[0015] As described in step S4 above, the components represented by the data structure standard are converted into CDI format and uploaded to the component library backend server.

[0016] As mentioned above, the component library management backend is used to review, upload, remove, and statistically analyze components whose data structure standards are uploaded to the component library backend server.

[0017] A cross-software BIM component library construction system includes a component library backend server located in the cloud, a web-based component library management backend hosted on the component library backend server, and a component library plugin installed on the BIM software.

[0018] The component library plugin is used to establish data structure standards for components. These standards include: component name, specialty, component category, 2D thumbnail, 3D thumbnail, original component file to be converted, and creation logic. It establishes a mapping relationship between the creation logic of components with the corresponding modeling interfaces of various BIM software, analyzes the component creation logic, extracts the 3D and 2D thumbnails of the components in the BIM software, generates the component name, specialty, and component category, and constructs the component represented by the data structure standards. It also uploads the components represented by the data structure standards to the component library backend server. Furthermore, it downloads the reviewed and uploaded components represented by the data structure standards from the component library backend server to the local machine, queries the corresponding BIM software modeling interface and operation sequence through the mapping relationship, calls the BIM software modeling interface according to the operation sequence, and reconstructs the component in the BIM software.

[0019] The component library backend server is used to receive and save components with data structure standard representations sent by component library plugins, and to send components with data structure standard representations that have been reviewed and put on the shelves to component library plugins.

[0020] The component library management backend is used to review, upload, remove, and statistically analyze components whose data structure is represented by a standard and uploaded to the component library backend server.

[0021] Compared with the prior art, the present invention has the following advantages:

[0022] 1. This invention can be applied to different BIM software, representing the components generated by different BIM software according to the data structure standard and uploading them to the cloud component library backend server. Alternatively, components can be downloaded from the component library backend server and restored to the local BIM software.

[0023] 2. This invention only requires generating the corresponding component in one BIM software, and then it can be restored to the corresponding component in other BIM software, which greatly reduces the time and effort of manual drawing.

[0024] 3. Components representing data structure standards can be effectively managed through the component library management backend. Attached Figure Description

[0025] Figure 1 This is a flowchart illustrating a specific implementation of Embodiment 1 of the present invention. Detailed Implementation

[0026] The technical solutions of the present invention will be clearly and completely described below with reference to specific embodiments. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0027] Example 1:

[0028] A method for building a cross-software BIM component library, with the following specific implementation steps:

[0029] Step S1: Establish the data structure standard for components. The data structure standard for components includes: component name, discipline, component category, 2D thumbnail, 3D thumbnail, original file of the component to be converted (component storage data saved in BIM software), and creation logic.

[0030] The creation logic includes component sketches, outlines, geometric component generation methods (including extrusion, lofting, rotation, sweeping, blending, etc.), generation parameters, component creation order, and Boolean operation logic; it also includes vertex coordinates, normals, triangles, UV coordinates, geometric transformation matrices, material identifiers, colors, textures, mappings, physical properties, and parameter information for generated components. This data structure standard is the format for generating components, ensuring the foundation and prerequisite for complete component conversion. Parsing diverse and heterogeneous data and forming components with a unified data structure standard also provides the possibility of editing models through multiple methods in the future.

[0031] Step S2: Establish a mapping relationship between the creation logic of standard data structure components and the corresponding modeling interfaces of various BIM software. Construct component library plugins corresponding to the modeling interfaces of different BIM software. These modeling interfaces include interfaces for component creation methods, legend creation methods, sketch constraint creation methods, parameter creation methods, and material creation methods. The completeness and correctness of this mapping ensure that components based on the CDI format standard data structure are correctly shaped and parametrically driven when converted to components in the corresponding BIM software.

[0032] Step S3: Establish a component library system, which includes: a cloud-based component library backend server for storing CDI format components and providing interfaces for uploading, downloading, and querying components; a web-based component library management backend, hosted on the cloud-based component library backend server, for managing component approval, uploading, delisting, statistics, and other management operations; and various component library plugins based on specific BIM software for parsing, uploading, displaying, querying, downloading, and placing components.

[0033] Step S4: Upload Component. On any BIM software with the component library plugin described in Step S3 installed, select the applicable component and click the upload button. The component library plugin will then analyze the component's creation logic. This creation logic includes: component sketch, outline, geometric component generation methods (including extrusion, loft, rotation, sweep, blend, etc.), generation parameters, component creation order, and Boolean operation logic; it also includes the vertex coordinates, normals, triangular faces, UV coordinates, geometric transformation matrix, material identifiers, colors, textures, maps, physical properties, and parameter information of the generated component. It automatically captures the component's 3D and 2D thumbnails in the BIM software. The component library plugin generates the component's name, discipline, and component category, and combines the component name, discipline, component category, 2D thumbnail, 3D thumbnail, the original file of the converted component, and the creation logic to form the component's corresponding data structure standard described in Step S1.

[0034] The components, represented by the data structure standard, are converted into CDI format for storage, forming the CDI standard format for local component saving. It is noteworthy that in the cross-software BIM component library system construction method provided by this invention, the CDI format is often used for the local caching function of the component library system and for copying and transferring media via hardware facilities. The flow of CDI format components within the component library system is often in the form of structured data streams, rather than files.

[0035] Using the interface provided by the component library backend server described in step S3 above, the components are saved to the component library backend server in the cloud. The web-based component library management backend reviews and lists the uploaded components, and pushes the reviewed and listed components to the component library plugins of various BIM software through the component library backend server.

[0036] Step S5: Using Components. On any BIM software with the component library plugin described in Step S3 installed, uploaded and approved CDI format components can be found. Clicking the download button will cause the component library plugin to download the selected CDI format component from the cloud-based component library backend server to the local machine via the interface provided by the component library backend server described in Step S3. The plugin will then read the downloaded CDI format component name, specialty, component category, 2D thumbnail, 3D thumbnail, the original file of the converted component, and the creation logic. Through the mapping relationship described in Step S2, the plugin will retrieve the modeling interface and operation sequence of the corresponding BIM software (these modeling interfaces may be one-to-many or many-to-one. That is, the creation logic of a standard data format may correspond to a combination of multiple modeling interfaces in the corresponding BIM software, or multiple standard data format creation logics may correspond to a single modeling interface in the corresponding BIM software). These modeling interfaces will be called in the operation sequence to re-simulate the component creation behavior, thereby achieving the goal of restoring the component in the current BIM software.

[0037] Example 2:

[0038] A cross-software BIM component library construction device includes a component library backend server set in the cloud, a web-based component library management backend set up on the component library backend server, and a component library plugin installed on BIM software.

[0039] The component library plugin is used to establish data structure standards for components. These standards include: component name, specialty, component category, 2D thumbnail, 3D thumbnail, original component file to be converted, and creation logic. It establishes a mapping relationship between the creation logic of components based on the data structure standards and the corresponding modeling interfaces of various BIM software. It analyzes the component creation logic, extracts the 3D and 2D thumbnails of the components in the BIM software, generates the component name, specialty, and component category, and constructs the component represented by the data structure standards. It also uploads the components represented by the data structure standards to the component library backend server. Furthermore, it downloads the reviewed and uploaded components represented by the data structure standards from the component library backend server to the local machine, queries the corresponding BIM software modeling interface and operation sequence through the mapping relationship, calls the BIM software modeling interface according to the operation sequence, and reconstructs the component in the BIM software.

[0040] The component library backend server is used to receive and save components with data structure standard representations sent by component library plugins, and to send components with data structure standard representations that have been reviewed and put on the shelves to component library plugins.

[0041] The component library management backend is used to review, upload, remove, and statistically analyze components whose data structure is represented by a standard and uploaded to the component library backend server.

[0042] The creation logic and modeling interface are the same as described in Example 1.

[0043] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.

Claims

1. A method for constructing a cross-software BIM component library, characterized in that, Includes the following steps: Step S1: Establish the data structure standard for the component. The data structure standard includes: component name, specialty, component category, two-dimensional thumbnail, three-dimensional thumbnail, original file of the component to be transformed, and creation logic. Step S2: Establish the mapping relationship between the creation logic of the data structure standard components and the modeling interfaces of various BIM software, and build component library plugins corresponding to the modeling interfaces of different BIM software. Step S3: Build a cloud-based component library backend server, set up a web-based component library management backend on the component library backend server, and install the component library plugin in the BIM software. Step S4: Select a component in the BIM software with the component library plugin installed. The component library plugin analyzes the component's creation logic, captures the 3D and 2D thumbnails of the component in the BIM software, generates the component's name, specialty, and component category, and generates a component represented by the data structure standard. Upload the component represented by the data structure standard to the component library backend server. The web-based component library management backend reviews and lists the uploaded components. Step S5: The component library plugin downloads the components, which have been reviewed and uploaded to the backend server of the component library, to the local machine according to the data structure standard representation. Through the mapping relationship in step S2 above, it queries the modeling interface and operation sequence of the corresponding BIM software, calls the modeling interface of the BIM software according to the operation sequence, and restores the components in the BIM software.

2. The method for constructing a cross-software BIM component library according to claim 1, characterized in that, The creation logic includes component sketches, outlines, geometric component generation methods, generation parameters, component creation order, and Boolean operation logic; it also includes vertex coordinates, normals, triangles, UV coordinates, geometric transformation matrices, material identifiers, colors, textures, mappings, physical properties, and parameter information for generating components.

3. The method for constructing a cross-software BIM component library according to claim 2, characterized in that, The modeling interface includes interfaces for creating components, legends, sketch constraints, parameters, and materials.

4. The method for constructing a cross-software BIM component library according to claim 3, characterized in that, In step S4, the components represented by the data structure standard are converted into CDI format and uploaded to the component library backend server.

5. The method for constructing a cross-software BIM component library according to claim 4, characterized in that, The component library management backend is used to review, upload, remove, and statistically analyze components whose data structure standards are uploaded to the component library backend server.

6. A cross-software BIM component library construction system, characterized in that, This includes a component library backend server located in the cloud, a web-based component library management backend hosted on the component library backend server, and a component library plugin installed on the BIM software. The component library plugin is used to establish data structure standards for components. These standards include: component name, specialty, component category, 2D thumbnail, 3D thumbnail, original component file to be converted, and creation logic. It establishes a mapping relationship between the creation logic of components with the corresponding modeling interfaces of various BIM software, analyzes the component creation logic, extracts the 3D and 2D thumbnails of the components in the BIM software, generates the component name, specialty, and component category, and constructs the component represented by the data structure standards. It also uploads the components represented by the data structure standards to the component library backend server. Furthermore, it downloads the reviewed and uploaded components represented by the data structure standards from the component library backend server to the local machine, queries the corresponding BIM software modeling interface and operation sequence through the mapping relationship, calls the BIM software modeling interface according to the operation sequence, and reconstructs the component in the BIM software. The component library backend server is used to receive and save components with data structure standard representations sent by component library plugins, and to send components with data structure standard representations that have been reviewed and put on the shelves to component library plugins. The component library management backend is used to review, upload, remove, and statistically analyze components whose data structure is represented by a standard and uploaded to the component library backend server.

Images