Problems with Base Quantities in several cases
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2024-07-02
01:55 PM
- last edited on
2024-07-05
08:24 PM
by
Laszlo Nagy
We are currently setting up a workflow to measure the sustainability of our planned buildings. The workflow is based on IFC4 Data Exchange, and the LCA-Software is using the BaseQuantites for measurements (there are currently no options to use a custom property). This workflow shed ligth on a few of issues regarding exported data from ArchiCAD:
- Exporting Curtain Walls with the setting "Keep hierarchy"
- As long as we stick to the classic curtain wall the default IfcPlate + IfcMemeber structure all is well.
- Movable elements inside Curtain Walls we'd like to classify as IfcDoor or IfcWindow. These Elements exported as part of a Curtain Wall will not have BaseQuantities.
- We also tend to model certain types of suspended ceilings with the Curtain Wall tool. In which case we would set both the main element and the subelements to IfcCovering CEILING. Resulting again in the subelements being exported without any BaseQuantities at all.
- As long as we stick to the classic curtain wall the default IfcPlate + IfcMemeber structure all is well.
- Exporting IfcRailing modelled with the Wall tool also results in lack of BaseQuantities.
We are currently implementing a workaround that includes some special ArchiCAD classifications for the aforementioned elements that will result in different IfcTypes when exported for model coordination and for the sustainability workflow but it's not ideal. (E.g.: the IfcWindows inside the facade will be IfcPlates when exported for our LCA software).
Operating system used: Windows 11
- Labels:
-
Classifications & Properties