Short Answer
IfcBuildingElementProxy elements are read during IFC import, so they are not lost. However, because a proxy deliberately carries no fixed semantics in IFC, vyzn cannot automatically recognise it as a wall, slab, window, etc.: by default it ends up in the catch-all category "Building element proxy" or "Other" and is not included in the automatic component grouping (wall, slab, roof, window, door, column, beam).
When to Use This
Whenever your IFC model contains elements of the class IfcBuildingElementProxy. Without a mapping, these elements remain in the catch-all category and are not automatically assigned to component categories such as wall, slab, roof, window, door, column or beam.
Step-by-Step Instructions
You have two options:
- Fix it in the authoring model (recommended): Assign the correct IFC class in the authoring model (Revit/ArchiCAD) whenever possible. The mapping in vyzn then applies automatically.
- Map it in the import wizard: In the import wizard, under "Information mapping" in "Custom" mode, assign the elements to the appropriate target component category and its attribute sources.
Expected Result
Proxy elements are also properly taken into account for the life cycle assessment and the evaluations.
Common Mistakes
- Relying on vyzn to classify proxy elements automatically: without a correct IFC class or a manual mapping, they remain in the catch-all category "Building element proxy" or "Other" and are not included in the automatic component grouping.