Hello,
I would like to export a group of HVAC components (e.g. air terminals) as IfcSystem (IfcDistributionSystem would be best but is apparently not possible) without all the duct segments and fittings.
When I only have the air terminals grouped into a duct system, this does not export as IfcSystem.
As soon as I create the detailed duct layout, I do get an IfcSystem in the resulting IFC.
How would you explain this behaviour? Is there a way I can export the system and the IfcRelAssignsToGroup relationship without creating a detailed duct layout?
Best regards,
AB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I've understood correctly, this sounds like some behaviour reported to me a month ago. If connectors on mechanical equipment aren't connected, the system isn't assigned.
I did implement a fix to enable this, which the source is available here. https://github.com/jmirtsch/IFC-For-Revit/commit/728af901f7177721e4f741cde4aec3a505729c9c This should be merged into the official exporter project at some point in time soon, but if you want to test the WIP release it is available.
Cheers,
Jon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We need to be able to apply IfcSystems to all IFC2X3 elements to aggregate freely, not only IfcDistributionElements that are (needs to be..) connected. To my knowledge this is not currently possible and is a real limitation.
For IFC4, we will naturally need IfcBuildingSystem and IfcDistributionSystem too.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sure, so this "connected" limitation is what my proposed fix addresses, elements no longer need to be connected. You can get advance access to this by building the plugin from my github repository, or I am providing installers here: https://drive.google.com/drive/folders/12vnErYwHFCZ8GzCJ_z4yEp0KxTSBrnEe?usp=sharing
At the moment this is Revit 2018 but others can be built on demand. Note this is not an official release and has not necessarily gone through any Autodesk QA that the official releases have and you might be advised to wait for real project application. If you do find any issues, you can report them here or to me/Angel.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
JonM, thank you so much for your answer and for the plugin! Would it be easy for you to build it also for Revit 2017? I would be even more endebted to you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please note, I have adopted an alternative approach to the different versions of revit, using branches. My 2017 branch is an adaptation of 2018 repository, rather than an extension of changes to the source forge 2017 folder. I did study the differences in the source forge folders, and don't expect problems with my approach.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I would like to export a group of HVAC components (e.g. air terminals) as IfcSystem (IfcDistributionSystem would be best but is apparently not possible) without all the duct segments and fittings.
When I only have the air terminals grouped into a duct system, this does not export as IfcSystem.
As soon as I create the detailed duct layout, I do get an IfcSystem in the resulting IFC.
How would you explain this behaviour? Is there a way I can export the system and the IfcRelAssignsToGroup relationship without creating a detailed duct layout?
Best regards,
AB
Hi AB,
If I've understood correctly, this sounds like some behaviour reported to me a month ago. If connectors on mechanical equipment aren't connected, the system isn't assigned.
I did implement a fix to enable this, which the source is available here. https://github.com/jmirtsch/IFC-For-Revit/commit/728af901f7177721e4f741cde4aec3a505729c9c This should be merged into the official exporter project at some point in time soon, but if you want to test the WIP release it is available.
Cheers,
Jon
We need to be able to apply IfcSystems to all IFC2X3 elements to aggregate freely, not only IfcDistributionElements that are (needs to be..) connected. To my knowledge this is not currently possible and is a real limitation.
For IFC4, we will naturally need IfcBuildingSystem and IfcDistributionSystem too.
Sure, so this "connected" limitation is what my proposed fix addresses, elements no longer need to be connected. You can get advance access to this by building the plugin from my github repository, or I am providing installers here: https://drive.google.com/drive/folders/12vnErYwHFCZ8GzCJ_z4yEp0KxTSBrnEe?usp=sharing
At the moment this is Revit 2018 but others can be built on demand. Note this is not an official release and has not necessarily gone through any Autodesk QA that the official releases have and you might be advised to wait for real project application. If you do find any issues, you can report them here or to me/Angel.
JonM, thank you so much for your answer and for the plugin! Would it be easy for you to build it also for Revit 2017? I would be even more endebted to you.
Sure, I've built the installer but unfortunately ran out of time to test it (Revit 2017 isn't on this computer). If you try it, let me know if you see problems. https://drive.google.com/drive/folders/1T0MtwogoaPCw0SdV91DpIeUYStgpjLl3?usp=sharing
There is a branch for 2017 WIP, https://github.com/jmirtsch/IFC-For-Revit/tree/WIP_Release2017
Please note, I have adopted an alternative approach to the different versions of revit, using branches. My 2017 branch is an adaptation of 2018 repository, rather than an extension of changes to the source forge 2017 folder. I did study the differences in the source forge folders, and don't expect problems with my approach.
The plugin solves the issue and I do not see any problem. Thank you so much, JonM!