#203 - Mapping of Solibri components to IFC entity types

Maximilian

for rule #203 we import the rules via Excel. We use the IFC standard and make a translation for our German customers (when “Door” return “Tür”,…).

We keep finding elements (e.g. Distribution Control Element, Electric Distribution Point, Actuator,…) for which we cannot find corresponding components in Solibri.
Therefore my question: keeps someone a list with all components that are supported by Solibri?

hlg

I assume that the Java API completely enumerates the Solibri component types: https://solibri.github.io/Developer-Platform/9.12.1/javadoc/com/solibri/smc/api/model/ComponentType.html

There are a number of component types that don’t trivially map to IFC by naming convention, but most of them can be guessed:

Assembly :       IfcElementAssembly?
Cable :          IfcCable*
CableCarrier:    ?
Ceiling:         ?
Compartment:     ?
Duct:            IfcDuct*
ElectricHeater:  IfcSpaceHeater?
FireCompartment: IfcFireSuppressionTerminal?
Floor:           ?
GasTerminal :    IfcGasTerminalType?
Layer:           ?
Model:           ?
Opening:         IfcOpeningElement?
Pipe:            IfcPipe*
SpaceBoundary:   IfcRelSpaceBoundary?
Unknown:         fallback for everything else?

I would be glad if someone can help to complete this list of not directly matched component types.

A number of (concrete) IFC entity types are not reflected as component type and I would expect them to map to the corresponding Solibri component type of the closest IFC supertype. IfcDistributionControlElement for example does not map by name to a Solibri component type, but its supertype IfcDistributionElement does. So does IfcObject, but it would be further away in terms of inheritance. Can anyone confirm this?

I was also wondering which IFC objects actually appear as components, likely these are any entities of type IfcObjectDefinition (with all subtypes)?