*Advanced* IFC Export of Curtain Wall / Revit 2018

[Anonymous]

Hi there,

We need to prepare IFC file with multiple Curtain Walls (none of them are the same). The IFC file has to contain all information about each Curtain Wall / Mullion / Panel. As a result it should be possible to view select any Curtain Wall Mullion/Panel and see both hosted Curtain Wall parameters (such as height, base offset, length etc.) and Curtain Wall Mullion/Panel parameters (glass colour, panel dimensions, profile type, profile dimensions). While the second part can be arranged, the first part (information about the actual Curtain Wall) seems to be complicated.

The list of parameters that has to be included in the IFC file contains:

— Curtain Wall Mark;

— Overall Curtain Wall weight;
— Overall Curtain Wall dimensions;
— Curtain Wall base offset;
— Glazing colour (this is easy, can be specified in Curtain Wall Panels);
— Mullion profile (also simple);
— Glazing dimensions (also simple).
Additionally:
— to include total glazing area of that Curtain Wall, and area of the wall itself.

Is it even possible? If yes, could you please help us?

Many thanks,
Mihails

Preview of the IFC file in the attachment.

[Anonymous]

Hi there,

We need to prepare IFC file with multiple Curtain Walls (none of them are the same). The IFC file has to contain all information about each Curtain Wall / Mullion / Panel. As a result it should be possible to view select any Curtain Wall Mullion/Panel and see both hosted Curtain Wall parameters (such as height, base offset, length etc.) and Curtain Wall Mullion/Panel parameters (glass colour, panel dimensions, profile type, profile dimensions). While the second part can be arranged, the first part (information about the actual Curtain Wall) seems to be complicated.

The list of parameters that has to be included in the IFC file contains:

— Curtain Wall Mark;

— Overall Curtain Wall weight;
— Overall Curtain Wall dimensions;
— Curtain Wall base offset;
— Glazing colour (this is easy, can be specified in Curtain Wall Panels);
— Mullion profile (also simple);
— Glazing dimensions (also simple).
Additionally:
— to include total glazing area of that Curtain Wall, and area of the wall itself.

Is it even possible? If yes, could you please help us?

Many thanks,
Mihails

Preview of the IFC file in the attachment.

[Anonymous]

Did you find out about this? I have a similar case where I want each panel to be separate in the IFC file.

[Anonymous]

Did you find out about this? I have a similar case where I want each panel to be separate in the IFC file.

[adrian.esdaile]

Any answers? This is quite important.

When exporting 'standard' Curtain Walls to IFC the panels are 'hidden' deep within the IFC hierarchy.

A Curtain Wall that is face-based exports the Curtain Panels as individual objects.

Why is there this glaring discrepancy, dare I say A BUG in Revit's handling of an Industry Standard file format (IFC)?

And when will Autodesk ANSWER THIS QUESTION?

[adrian.esdaile]

Any answers? This is quite important.

When exporting 'standard' Curtain Walls to IFC the panels are 'hidden' deep within the IFC hierarchy.

A Curtain Wall that is face-based exports the Curtain Panels as individual objects.

Why is there this glaring discrepancy, dare I say A BUG in Revit's handling of an Industry Standard file format (IFC)?

And when will Autodesk ANSWER THIS QUESTION?

[whp.m.owens]

Hi Mihails,

I realize this is a very old post, and maybe you've moved on from the "issue" or have found a workaround.

I'm not an Autodesk "fanboy" but I am not sure this is a valid complaint. It appears you are using some sort of forge-viewer to view the ifc-information, and the limitation for how the ifc-panels are nested to their containers is limitied.

I tried exporting a curtain-wall with panels to ifc and opened it in solibri. There I could select the individual elements, and see which elements were associated with the wall. Extrapolating information backwards doesn't seem to be possible, at least not with the simple export i tested.

In terms of carrying marks between panels and the walls they are hosted to; the workaround would probably be dynamo. I am a dynamo "fanboy" but also know how irritating it becomes when more than three or four scripts need to be run in order to achive a goal which should probably be more intelligently built-into the core software. This is not an ideal solution, and i haven't looked into it, but i can't imagine that there is a technical limitation to carrying information from the host-facade-wall into the individual components via dynamo.

I can't speak for autodesk, but I can imagine there are two factors at play here:

1. Creating references between objects in the Model uses resources. It might not be a lot, but every bit adds-onto how much computing needs to be done in order to keep information between elements linked. I have similar issues if I want to create parts for layered walls. If I update information in the host family, the information is initially carried over, but needs to be maintained separately afterwards. (Sorry, you can't divide a curtain wall....)

2. Autodesk probably is adopting a strategy of focusing on the core-product while allowing users to leverage the API with add-ins like dynamo and pyrevit. For smaller companies, this might be troublesome of you don't have the resources or luck to find someone who also has one of these skills. If you are a mid-sized or larger firm, you probably are just creating your own tools and solutions to deal with these issues. I can only recommend you learn some dynamo...it's a life-saver for me....

I am not an autodesk rep...just a guy who has been using autodesk products for close to two decades. Actually was searching for a solution to my problem...

Cheers

Matt

[whp.m.owens]

Hi Mihails,

I realize this is a very old post, and maybe you've moved on from the "issue" or have found a workaround.

I'm not an Autodesk "fanboy" but I am not sure this is a valid complaint. It appears you are using some sort of forge-viewer to view the ifc-information, and the limitation for how the ifc-panels are nested to their containers is limitied.

I tried exporting a curtain-wall with panels to ifc and opened it in solibri. There I could select the individual elements, and see which elements were associated with the wall. Extrapolating information backwards doesn't seem to be possible, at least not with the simple export i tested.

In terms of carrying marks between panels and the walls they are hosted to; the workaround would probably be dynamo. I am a dynamo "fanboy" but also know how irritating it becomes when more than three or four scripts need to be run in order to achive a goal which should probably be more intelligently built-into the core software. This is not an ideal solution, and i haven't looked into it, but i can't imagine that there is a technical limitation to carrying information from the host-facade-wall into the individual components via dynamo.

I can't speak for autodesk, but I can imagine there are two factors at play here:

1. Creating references between objects in the Model uses resources. It might not be a lot, but every bit adds-onto how much computing needs to be done in order to keep information between elements linked. I have similar issues if I want to create parts for layered walls. If I update information in the host family, the information is initially carried over, but needs to be maintained separately afterwards. (Sorry, you can't divide a curtain wall....)

2. Autodesk probably is adopting a strategy of focusing on the core-product while allowing users to leverage the API with add-ins like dynamo and pyrevit. For smaller companies, this might be troublesome of you don't have the resources or luck to find someone who also has one of these skills. If you are a mid-sized or larger firm, you probably are just creating your own tools and solutions to deal with these issues. I can only recommend you learn some dynamo...it's a life-saver for me....

I am not an autodesk rep...just a guy who has been using autodesk products for close to two decades. Actually was searching for a solution to my problem...

Cheers

Matt

[whp.m.owens]

Not sure why face-baced exports differently than non-face based.

Maybe there is an ifc-enumeration which allows this type of behavior?

[whp.m.owens]

Not sure why face-baced exports differently than non-face based.

Maybe there is an ifc-enumeration which allows this type of behavior?

[faijanuddinshaikh]

Hey, I'm trying to export my revit model to ifc which has curtain panel pattern based adaptive family. It's an ETFE family but its not exporting right. It only exports the bottom surface for some and top surface for some. Any help would be appreciated, Thank you.

[faijanuddinshaikh]

Hey, I'm trying to export my revit model to ifc which has curtain panel pattern based adaptive family. It's an ETFE family but its not exporting right. It only exports the bottom surface for some and top surface for some. Any help would be appreciated, Thank you.

[whp.m.owens]

IFC 2x3 or IFC4?

If IFC4, try exporting 2x3 and see if you get the sameresults.

Otherwise, check your IFC-Export settings at the global level, especially for sub-categories.

Then check IFC-Export settings at the type and instance level.

[whp.m.owens]

IFC 2x3 or IFC4?

If IFC4, try exporting 2x3 and see if you get the sameresults.

Otherwise, check your IFC-Export settings at the global level, especially for sub-categories.

Then check IFC-Export settings at the type and instance level.

[faijanuddinshaikh]

I was using Revit 2019 to export the model to IFC before but then I tried revit 2024, It exported both surfaces properly. Maybe something changed in new versions. I used the base settings in both except enabling the "export only visible element" setting in both version's exporter dialog.

[faijanuddinshaikh]

I was using Revit 2019 to export the model to IFC before but then I tried revit 2024, It exported both surfaces properly. Maybe something changed in new versions. I used the base settings in both except enabling the "export only visible element" setting in both version's exporter dialog.