Parameters-behavior in IFC-export (Instance & Type properties)

teemu.kangasmakiRSGGS — Wed, 18 Jan 2023 10:26:39 GMT

With Revit 2023 there seems to be some new kind of approach how Type-parameters and Instance-parameters translate to IFC-schema?

I couldn´t find any release notes concerning this matter but I can see the difference in our solutions that are trying to utilize the information within the IFC-models. There is no issue with Solibri, it only indicates the difference with normal font (Instance parameter) or italic font (Type parameter) but when we go in some other solutions the struggle begins.

With Revit we demand the use of User Defined Property Sets so we can harmonize the IFC data from different authoring tools. Within UDPS we map Instance & Type properties by IfcEntities. (IfcWindow, IfcSlab, IfcDoor etc.). Like said, in tool like Solibri, we get everything in and in use, but some other tools utilize only Instance-parameters and loose all the parameters coming from Type-parameters.

With brief investigation I´ve come to the conclusion that Instance parameters are mapped to IfcObject and Type-parameters are going to IfcTypeObject. This means that these parameters are mapped to different layer in IFC-hierarchy - Instances higher than Type.

Anyone else encountered this issue? Is there a place where I can configure this mapping? Is there something to adjust within User Defined Property Sets -mapping?

topic Parameters-behavior in IFC-export (Instance & Type properties) in Revit Architecture Forum

Parameters-behavior in IFC-export (Instance & Type properties)