1. Application Programming Interface
Access through Application Programming Interface (API) allows direct linkage between the building information model and BIM solutions. Data can be retrieved from BIM models via APIs and integrated into cost estimation software. It is also possible to transfer data back from cost software to BIM; however, any changes in the API require corresponding updates to the applications using it.
If REVIT software is extended with additional plugins to edit component cost information, the quantity calculation depends on the embedded main software. This method can lead to errors in the deduction relationships between components.
2. Open Database Interconnection
Open Database Connectivity (ODBC) is a database access method that is independent of specific database management systems. Exported data can be integrated across various applications. Using ODBC requires a clear understanding of the BIM database structure being accessed. Therefore, a general BIM software like Revit is commonly chosen as the integration platform.
Currently, domestic cost software such as Guanglian Da and Luban can build Revit BIM models, import and identify component types, and calculate component quantities. However, data transmission is one-way, meaning changes made in the cost software cannot be imported back into the BIM model. Additionally, component recognition accuracy is low, which often results in errors.
3. BIM Design Software Output of Component Quantities
Most BIM design software, such as Revit, can directly calculate component quantities and export the results in formats like Excel. Cost engineers can then manually summarize and analyze these quantities.
This approach, however, suffers from low computational efficiency, limited traceability of component quantities, and difficulty in updating quantities when design changes occur. It is best suited for projects with relatively few components and complex artistic shapes.
Must log in before commenting!
Sign Up