Deliberate IfcElementAssembly Type mapping at a component level

[davdelven]

The geometry of an IfcElementAssembly is generally formed from its components. 

As Architects performing our activity globally, the type of projects and their scope have several ways of doing.

The following image shows an example of how Architects in some projects need to build Windows by components instead of a single element mapped to IfcWindow. Considering also the rise of standards such as the Level Of Information Need ( ISO/DIS 7817 - Building information modelling — Level of information need — Concepts and principles ... might provide the backbone of generating geometry and adding information in a more flexible way. 

Image credits: BIMcollab and Menno Mekkes (Netherlands)

Are there some insights on that? I didn't see this on the new public roadmap (which, by the way, I congratulate GS fo

[Abraham Smith]

Brilliant! also add an image of Menno Mekkes that I modified to better explain.

Other options:

IfcCurtainWall->IfcRelDecomposes->IfcDoor / IfcWindow / IfcMember / etc.

IfcGroup->IfcRelAssingToGroup->IfcDoor / IfcWindow / IfcMember / etc.

I would say that the ideal would not be at the component level, rather at the group/system level (IFC project manager window). maybe both.

[davdelven]

We need to move this request and gain more popularity among the community if we really want it as something to be considered in the future or the Ideas Pool roadmap.