From a LinkedIn discussion: normal .ifc file from Tekla with the rebar option ticked and imported it into MicroStation, from there I exported a .sat file of the rebar and inserted it into Revit. Of course this means you can’t modify it in anyway but if all you need it for is to cut sections then works quite well.
An interesting discussion has been brewing over on LinkedIn about IFC Export from Revit. In my personal experience, the most predictable results come from deleting the IfcExportAs parameter and using the IFC mapping files to force the export result. However, this may not be the best path for data longevity and roundtripping.
Here is one little excerpt from Wawan Solihin: The use of IfcExportAs is more suited for mapping detailed subtype or predefined type of MEP components that are mostly defined by families and often they do not correspond 1-1 nicely with IFC definitions. So instead of getting a generic IfcBuildingElementProxy for a family type that does not have clear mapping to the IFC entity, one can use IfcExporAs to define the IFC type it is intended to be plus its subtype for example IfcSensorType.CO2SENSOR that will create IFC entity IfcDistributionControlElement with type IfcSensorType and predefinedtype=’CO2SESNSOR’ in IFC2x3 (or entity IfcSensor in IFC4). This is just one example. There are other entities in IFC that must have mandatory attribute set, e.g. IfcReinforcingMesh which has several mandatory attributes such as LongitudinalBarNominalDiameter. Unless those attributes are set and Revit IfcExporter knows where to get the relevant information, you will get invalid entity information in IFC.
This can be done with AutoCAD MEP 2015, or Architecture, or similar verticals that have the IFCEXPORT command.
Open AutoCAD MEP
New DWG file
IMPORT -> select SAT file
IFCEXPORT
Open IFC in Revit
The advantage of doing this over importing the SAT directly to a Generic Model family is that the IFC method will result in individual forms for each bit of the SAT file. If there are 1200 forms, you will get 1200 families in Revit. This, in turn, will export to Navisworks with this level of element hierarchy (instead of just one big imported SAT element).
This will also result in higher granularity of clashes when using the converted SAT via IFC method (more forms to clash against).
You probably know that you can attempt to explode a SAT in a Revit family, but I find that sometimes unsupported elements disappear using this method… so I like my way via AutoCAD a bit better at this stage.
I have covered using FBX to access Navisworks data for downstream use. What about KMZ? This format contains lightweight geometry as well as some model structure. It is actually quite difficult to find an easy way to go from KMZ to IFC, or KML to IFC. But, it can be done!
Here’s one method:
Export desired view from Navisworks to KML with “collapse” set to None. This will bring the full model hierarchy with the KML file (see help for more info)
In Revit 2015, you can use the IfcOpeningElement subcategory of Generic Models (and possibly other categories) for a Linked IFC to hide the orange “void” elements that appear in certain situations, as per this image:
Just use the Revit Links Display Settings to “override” settings in Visibility / Graphics (choose custom, and Model Categories tab also custom) to access this subcategory.
Tekla have released a viewer app for iOS that can read IFC files. You will probably use Dropbox to get any large IFC files onto your phone or tablet, but you can also open from email or web.
Free version features • View 3D models in multiple formats: .ifc, .3ds, .obj • Very large models load in mere seconds, tested to more than 2 GB • Zoom, pan and rotate 3D models • Object Outlines and dynamic Shadows to better visualize model geometry and depth • Open files from email, file-share or web • Sample files included and more can be downloaded • Orthogonal view of 3D models – as an alternative to Perspective view • Imperial units display option for Property values (feet &inches)
Of course, you could also append the IFC to Navisworks, then Glue it, and use the BIM 360 Glue app to do something very similar 🙂
Many of us use Tekla BIMsight or Solibri for IFC viewing, but there is another free option: FZK Viewer. It is just a 10mb download, unzip and go.
It has a Walk tool like Navisworks for easy navigation, and it can even export to a number of formats, including: DXF (cool! quick IFC to DXF conversion anyone?) VRML 2 STEP Collada Google Earth CityGML
Additionally, it can open gbXML and GML files. All in all, a handy piece of software to have if you are dealing with IFCs on a daily basis.
Oh, did I mention it can Merge .xyz point cloud files to the scene?
This 2007 research paper by Dr M M Nour gives an overview of IFC and some of the challenges of using it in a collaborative BIM environment. It posits a potential solutions that it calls FIOPE. It also considers IFC model splitting and segregation, and how to handle comparison and IFC file differences.
A few quotes: “This paper addresses the problem of workflow management in collaborative teamwork environments, where multidisciplinary actors and software applications are involved. Design versions or variants may represent different development stages, partial designs or solution alternatives that need to be integrated together. The paper presents a novel approach to splitting and merging IFC sub-models (partial models) at different degrees of granularity away from the schema oriented approaches. It relies on an instance oriented approach (FIOPE) Flexible Instance Oriented Partial Exchange Environment…” “…in order to achieve a lossless information exchange among AEC/FM project members, either the software developers should change their internal data structuring to eliminate irrelevant IFC data loss or the exchange should be limited to partial models that contain application-relevant IFC data. The latter seems to be the most practical solution…”
Revit 2015 has brilliant IFC Link capability – it is fast and accurate, and it even brings in colours for most IFC elements. We can leverage this to quickly create RVT files from IFCs, and then downgrade to other Revit versions if necessary. Here’s how:
Select or create an appropriate Revit IFC template (RTE file) that is clean and has only two phases
Set it at the top of the Template list in Revit 2015 Options – this is the template that will be used when Linking an IFC file. Interestingly, Revit will ignore the IFC Import template dialog setting when Linking.
Link an IFC file into an open project.
Locate the cache version RVT file that Revit created in the same folder as the linked IFC
Copy that RVT somewhere else so you can modify it freely
Open the RVT that Revit created while linking the IFC
Important: Delete the IfcExportAs Project Parameters (there might be more than one). If you don’t, it can cause headaches when exporting.
Use this IFC Export Classes text file for Revit 2015 which pushes everything into IfcBuildingElementProxy. The reason for this is that we want 100% geometry fidelity, but we are not concerned with editability.
When exporting from Revit 2015, choose IFC 2×3 Coordination View 2.0
Import back into a previous version of Revit (keep in mind points above about IFC import templates). The resulting elements will all be in-place Generic Models, with an Import Symbol inside. The file size will likely be pretty big, like 6 times the size of the original IFC.
This method should result in 100% item count fidelity. For my test IFC file: Tekla BIMsight 2772 model items
Revit 2015 2772 model items
Navisworks 2015 2772 model items
Revit 2013 2772 model items
It is obviously not the way to go if you want maximum editability. But if you want maximum fidelity of geometry and reasonable import of IFC colours, this could be an option.
Update: Use this IFC import mapping to get most objects onto Structural Framing category when importing to Revit 2013. Also, when trying to delete orange voids in Revit 2013, you can use a View Filter based on the Reference parameter to hide everything that is not a void. Additionally, the IfcOpeningElement material transparency can be modified to “check” that no other objects are going to be deleted that are actual real model geometry. Screenshots below:
Update 2: Be very wary of purging. It seems in later updates of Revit 2015 that purging these IFC cache files can be destructive and result in deleted geometry – something that purge should never really do. Here is a demonstration of the issue: