Chris Zoog’s recent IFC presentation to the NYC Revit User Group has hit the blog and twitterspheres! With excellent reviews I may add. A full recording has now been posted to YouTube, and some links to reviews below.
More recently (ie. this week), Chris delivered a webcast on the usefulness of IFC for NYC-RUG and gave his permission that it be uploaded to the web. See the whole webcast embedded below:
In the webcast, Chris talks about (among other things):
- history of IFC
- using Grasshopper and Geometry Gym plugins with Revit (see my previous posts)
- Generic Model Adaptive Components used in simulation
- clash detection / code compliance
- Tekla Bimsight
- Solibri Model Checker ( 35:48 )
“Navisworks is ubiquitous but this (Solibri) is the better tool”
- BCF – BIM Collaboration format ( 41:20 )
- the IFCExportAs parameter for non-system families in Revit
- arr-chee-cad ( 57:15 )
It is recommended viewing if you are interested in the current uses of IFC and he also hints at what the future may hold…
Jeffrey Ouellette wrote a summary of the webcast and posted this on Linkedin:
1. Design & Documentation – A set of formal parametric design constraints were developed in Rhino using Grasshopper, tagged with IFC data and then exported as IFC files and imported into Revit. The objects were translated into Revit-native data structures (some better than others). The design work would be VERY difficult, if at all possible, in Revit, so he showed that using a design tool built for such purposes could still exchange the model data with the preferred documentation platform, totally different technologies, using IFC. Granted the connection was based on IFC4….
2. Planning & Design. dRofus is a very powerful web-based, database-centric, planning and facility data management tool. Via IFC exchanges, he showed how owner program requirements, developed most efficiently in dRofus, could be transferred to Revit via IFC2x3. Also designs in Revit could be re-imported into dRofus to compare and verify the model design against the requirements, AUTOMATICALLY!
3. Clash Detection/Coordination. Yes, Revit and Navisworks can talk to each other with a high degree of ease and fidelity now, but he showed how Solibri Model Checker (SMC), an IFC model based BIM tool, can find, report, and share this information in a variety of ways, including sharing model comments between platforms via BCF.
4. Code checking. Using Solibri Model Checker (SMC), a Revit design model is exported via IFC and examined for exiting, occupancy, and critical clearances using logical rules based on code requirements, such as IBC.
5. QA/QC. Beyond just using SMC for code compliance and clash detection, SMC can be used to determine the quality and validity of a BIM, both geometry and data, with rules based on a particular domain or even between domains.
What was most impressive was that it was working, given the reputation for Autodesk’s previous interoperability efforts, but noted recent improvements in support.
“He was able to demonstrate that there was no excuse for being able to use IFC-based workflows TODAY, even with Revit. You just have to learn and do.” Jeffrey Ouellette