Collaboration with other software
About model and data exchange with 3rd party solutions: Revit, Solibri, dRofus, Bluebeam, structural analysis solutions, and IFC, BCF and DXF/DWG-based exchange, etc.

IFC link, unlink

Anonymous
Not applicable
Is there a way to "unlink" an IFC file from an archicad file. The IFC file generated in Revit by the structural engineer has brought with is several added stories and wreaked havoc several of the plan views, specifically roof and site plans. Any thoughts are appreciated. My hope for now is to just eliminate the IFC model information from the file.

Thanks!
7 REPLIES 7
Laszlo Nagy
Community Admin
Community Admin
You may have to manually repair that file by deleting those created Stories, deleting those created Layers and IFC elements.
For the future if may be a better idea to import the IFC into a new file, then place that file in your porject as a Hotlinked Module.
Generally, IFCs are best used as Reference Models, where the Architect, Structural Engineer, MEP Engineer, etc. all work on their own model and use the others' models only as Reference model.
You can read the ARCHICAD Guide for more information about this:

http://helpcenter.graphisoft.com/guides/archicad-18-int-reference-guide/interoperability/multidiscip...
Loving Archicad since 1995 - Find Archicad Tips at x.com/laszlonagy
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac27
KenMcN
Contributor
laszlonagy wrote:
…For the future if may be a better idea to import the IFC into a new file, then place that file in your porject as a Hotlinked Module.
Does that sidestep the problem when third party files have different story settings from the host?
I thought the linked model would always move its elements up or down to match the stories in the main file, usually making a mess of the model.

We've got this problem with a development as the Revit users have added stories to suit themselves, meaning that we can no longer just bring their model into ours.

I've tried converting it into a library object but can't position it accurately (can't snap to anything), so thinking that we may have to go to Solibri to continue to work with a federated model. Not great.

Kenny
V25 & 26 (fully patched); Mac Ventura, MacBook Pro M1 Max
Laszlo Nagy
Community Admin
Community Admin
Even if you open the IFC in another file and Hotlink that, you will still have to deal with the problem of different Story structures just as you would in case of any other hotlinked module.
Loving Archicad since 1995 - Find Archicad Tips at x.com/laszlonagy
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac27
Anonymous
Not applicable
With regards to the issue of additional Revit levels these additional levels can be toggled off at the Revit users end prior to exporting the IFC file.

Simply view either an Elevation or Section within the Revit model and uncheck the Building Story attribute. This will stop the additional structural levels from being exported with the IFC file.
KenMcN
Contributor
Marcus_Scott wrote:
With regards to the issue of additional Revit levels these additional levels can be toggled off at the Revit users end prior to exporting the IFC file.

Simply view either an Elevation or Section within the Revit model and uncheck the Building Story attribute. This will stop the additional structural levels from being exported with the IFC file.
Don't want to hijack this thread, but in our case the other architects have said that because these are 'real' stories and not 'reference' stories they don't have the option to turn them off. So does this apply to all stories irrespective of how they have been made? Hope so!
V25 & 26 (fully patched); Mac Ventura, MacBook Pro M1 Max
Tim Ball
Expert
Surely this kind of thing should be agreed as part of the project BIM protocol. It's a nonsense to be working with different storey setups! You should not have any unreal storeys in a building, they either exist or they don't!
Tim Ball

AC26, iMac

User since V5
KenMcN
Contributor
Tim wrote:
Surely this kind of thing should be agreed as part of the project BIM protocol. It's a nonsense to be working with different storey setups! You should not have any unreal storeys in a building, they either exist or they don't!
Yes, it was "agreed" in the BIM Protocol a long time ago, however the Technical Architect is also the BIM Manager and has decided that their interpretaton of a failry general description of the floor levels alows them to do this.

The new stories are areas where the FFL is different to the main block of accommodation, so technically they do exist, just not for every 'block' that makes up a very complicated development. No real option to divide them into totaly separate files as they overlap so much.

Frustrating.
V25 & 26 (fully patched); Mac Ventura, MacBook Pro M1 Max