android tv

Interesting post by Ben a while back on the impact of Revit view settings when exporting to Navisworks.  In most cases, this is "logical" - if you can see it, it will get exported, but if you can't see it, then it won't.

However, this doesn't quite hold true for model lines.  Have you ever wanted to export model lines (3d) from Revit and import these into Navis?  Ben suggests this workaround:
Model lines will not be shown in your 3D Navisworks file when brought through from your Revit project. One way to combat this would be to export your Revit file as an .IFC and then bring that file into Navisworks. .IFC brings through model lines but not detail lines through the { IfcAnnotation } Parameter.

 via
http://bimopedia.com/2013/11/25/view-settings-from-revit-into-navisworks/

Its already across the Twitterverse, but in case you missed it:

I am loving Navisworks more with every passing day.  A job doesn't have to be a fully collaborative / coordinated project in order to get benefit from Navis.  Here is a collection of recent information and resources relating to Navisworks.  Hope you find something interesting!

Firstly, a link to the Navisworks updates page.

Navisworks 2014 support for BIM 360 Field http://t.co/SLXs67e1T3
— Autodesk Navisworks (@Navisworks) August 13, 2013

On Revit - Navisworks implementation generally:
"... contractor will import the Revit model into Navisworks and use Navisworks to ‘virtually construct the building’, creating construction sequences to ensure every element slots into place, almost like a jigsaw. Linking the model to packages like Microsoft project will allow digital construction monitoring against the project schedule. This is happening all over the world..."
via
http://revitst.blogspot.in/2013/08/revit-collaboration.html

Using Catalogues in Navisworks Quantification:
http://beyonddesign.typepad.com/posts/2013/08/using-catalogues-in-navisworks-quantification.html

Coordinating Models stored in Vault using Navisworks:

http://beyonddesign.typepad.com/posts/2013/08/managing-your-discipline-and-coordination-models-with-autodesk-vault.html

Up and Running with Autodesk Navisworks 2014
by Deepak Maini

I have been reviewing this book and I really enjoy its content.  It is detailed, comprehensive and easy-to-follow.  Highly recommended for those who are learning Navisworks or those who want to increase their proficiency and efficiency when using Navisworks... More on this book in a future post.


Downloads (via this):
Table of Contents
Tutorial files

Australia / NZ purchase page:
here

Amazon page for the Up and Running book:
http://www.amazon.com/Up-Running-Autodesk-Navisworks-2014/product-reviews/1482605279

Training course by Deepak:
http://www.cadgroup.com.au/community/blog/cadblog/index.php?showentry=330

4D IFC Importer for Navisworks Manage 2014
At this point in time, you can't create products in Navisworks from the API, but if you import the IFC using the native importer (IFC2x3 only), then you can run my IFC enhancer (plugin can be downloaded from http://www.geometrygym.com/downloads ) which can generate the timeliner tasks and identify the ifc products by their unique identifiers.
Download:
ggNavisIFC2014x64 v0.0.02.msi (18th October 2013) Navisworks 2014
New plugin to extract 4d information from IFC files and convert into Navisworks timeliner.

Read more:
http://geometrygym.blogspot.com.au/2013/10/navisworks-4d-ifc.html

2013:
IFC Exporter 2013 (v2.15.1):
http://apps.exchange.autodesk.com/RVT/Detail/Index?id=appstore.exchange.autodesk.com%3aifcexporterforrevit%3aen

IFC Export Alternate UI for Revit 2013 (v1.13):
http://apps.exchange.autodesk.com/RVT/Detail/Index?id=appstore.exchange.autodesk.com%3arevitifcexportalternateui%3aen

---

2014:
IFC Exporter 2014 (v3.7.1):
http://apps.exchange.autodesk.com/RVT/Detail/Index?id=appstore.exchange.autodesk.com%3aifcexporterforrevit2014%3aen


IFC Export Alternate UI for Revit 2014 (v2.5):
http://apps.exchange.autodesk.com/RVT/Detail/Index?id=appstore.exchange.autodesk.com%3arevitifcexportalternateui2014%3aen

---

via email

Some up-to-date info on data exchange between Tekla and Revit, including IFC and SDNF workflows (from revit structure blog):
The main purpose of the IFC import into Tekla is to allow the fabricator to accurately build a model from the consultants Revit model. However, you can convert certain objects from the IFC file to native Tekla objects such as beams, columns, footings etc. This is clearly useful rather than building a model from scratch. I tried this on a few beams and columns and again found no discrepancies with the original Revit Structure 2014 model, however, as you would expect the stairs translated to a bounding box. See the below image including the report.
...
I also imported an IFC model from Tekla to Revit with some fairly good results that are fine for coordination purposes. I would imagine that this may be better in a product such as Navisworks... 
...
The best way to incorporate the analytical model from Tekla to Revit is to transfer the model as CIMsteel (Note that you will need to install the SDNF Import/Export for Autodesk Revit 2014). This gives you the option of transferring the analytical model



Read more:
Revit Structure 2014 and Tekla Structures 19.1 | Autodesk Revit Structure

Following this tweet from Sean:

@djnelson75 @lukeyjohnson that's mysterious, especially since there's nothing for signage and roads STILL doesn't have a use.
— Sean David Burke (@seandburke) September 9, 2013

(which was in response to my post about the Revit Category Guide.)

I was tempted to use the IFC roundtrip method to make some Road families in Revit.  So, here they are for download:

You can't Schedule or Tag them normally, but you can use Material Tags, modify the Category and Subcategories using Object Styles, and view them in the Project Browser.

As always, use these "unsupported" methods with care...

Here are some similar posts:
Convert All Masses (including in-place Mass) to Generic Models via IFC

You can break Revit by making Room families

In-place and Component families of Stair and Railing Category

General - Initialize GUIDOptions so that GUIDUtil.CreateGUID(element) can be used outside of the exporter code. - Remove filterView argument from many functions; used cached value instead. - Various minor optimizations to slightly improve the time to export. New Functionality - (R2014 only) IFC4: Allow export of 0 thickness material layers. - (R2014 only) IFC4: Export IfcFootingType (IFC2x3: use IfcTypeObject instead) for wall-based footings only. - Allow export schedules as custom property sets.  The name of the schedule is the property set name; the column names are the IFC parameter names. - Allow export of solid models, which allow for mixing Brep and extrusion geometries for an entity.  This can result in smaller IFC files. - Export IfcCurtainWallType (IFC2x2: use IfcTypeObject instead). - Export the currently selected non-primary design option when exporting in current view only mode. - Use the base level parameter of an element to determine which level to associate the element to; use geometric containment only for cases where this is no base level. Bug Fixes - Don't export some extraneous local placements. - Don't export type if instance isn't exported for family. - Fix Pset_CoveringCommon: Thickness -> TotalThickness - Generic rework of how instance and type properties are assigned to IFC entities.  If an exported entity has a related type object, then the entity will have the instance properties assigned, and the type object the type properties.  If there is no type object, the exported entity will contain both instance and type properties.  This should also remove any repetition of exported property sets. - Look at all "ZoneName X" shared parameters for a room even if some have no value.  This still assumes that they are sequential (i.e., if there is no "ZoneName 4" shared parameter at all, "ZoneName 5" will not be processed). - Prevent export of IfcPolyLoops with less than 3 vertices. - Properly scale all known Revit parameter types to the units specified for the IFC file.  Note that there are potentially many Revit parameter types that map to one unit type (e.g., PipeSize, WireSize, and Length are both length parameters); we do not create different units for each of these, but instead use the main unit type. - Respect visibility options of curtain wall panels and mullions when exporting in current view only mode. - Use category id as default for IfcCoverings for ceilings, floors, and roofs.

New Functionality - Add UI version number to title of the IFC Export dialog box. - Add option to export schedules as custom property sets.  The name of the schedule is the property set name; the column names are the IFC parameter names. - Add option to export solid models, which allow for mixing BRep and extrusion geometries for an entity.  This can result in smaller IFC files. - Remove option to disable surface styles on export. - Remove option to export advanced swept solids.

via email

Are you interested in using BCF with Revit?  Then checkout the plugin (now upgraded to version 2.1.1) at:
BCF Plugin 2.1 for Revit | Matteo Cominetti

Direct link:
http://matteocominetti.com/d/BCFPlugin2.1.1.exe




You may also be interested in the opensource BCF server project at:
opensourceBIM/BimConsiderationForum-BcfServer · GitHub

2013:

IFC Exporter for Revit 2013 (v2.12):
http://apps.exchange.autodesk.com/RVT/Detail/Index?id=appstore.exchange.autodesk.com%3aifcexporterforrevit%3aen

IFC Export Alternate UI for Revit 2013 (v1.12):
http://apps.exchange.autodesk.com/RVT/Detail/Index?id=appstore.exchange.autodesk.com%3arevitifcexportalternateui%3aen

2014:

IFC Exporter for Revit 2014 (v3.4):
http://apps.exchange.autodesk.com/RVT/Detail/Index?id=appstore.exchange.autodesk.com%3aifcexporterforrevit2014%3aen

IFC Export Alternate UI for Revit 2014 (v2.4):
http://apps.exchange.autodesk.com/RVT/Detail/Index?id=appstore.exchange.autodesk.com%3arevitifcexportalternateui2014%3aen

What’s new for IFC Exporter for Revit v2.12/v3.4:
General (Revit 2014 UR1 Only):
- Added basic support for IFC4 export, corresponding to the Coordination View 2.0 MVD. Please see the Wiki for more details. This requires Revit 2014 Update Release 1 to be installed. Note that currently the ifcXML format for IFC4 is not supported.

Part of knowing What Revit Wants, is also knowing what it Does Not want.  Sometimes, you can push the hack (or workaround) that step or two too far... and the result is unpredictable, buggy and kinda useless.

In the past, I have used various methods to create inplace or component families that are not 'officially' or natively available.  In this particular instance, I used the IFC round trip method to force the creation of an Inplace family with Category set to Rooms.  I also pushed this into a Component (loadable) family.

Great!  I have Room families.  But guess what?   The result is unpredictable, buggy and kinda useless.

In fact, if you open these projects, make some Room Separation lines and then try to place a Room, I would estimate that in 95% of cases, your Revit has already crashed.  The families will not accept a tag, and they won't schedule.  They seem to just sit there, destabilizing your Revit environment.  So why post about it?  Well, basically so that you can add this workaround to the aforementioned list of something that Revit (currently) does not want.

I have provided both 2013 and 2014 versions for your download and testing here:
RVTs that will crash Revit

via email (note that the Sourceforge link for the 2014 UI is recommended over the App Store version):

What’s new for IFC Exporter for Revit 2014 v3.2/ IFC Exporter for Revit 2014 v2.10:

New Functionality: - Add property sets: Pset_ElectricalDeviceCommon, Pset_SwitchingDeviceTypeCommon, Pset_SwitchingDeviceTypeToggleSwitch - Add support for electrical current, electrical voltage, frequency, and positive plane angle units. - Allow Name/ObjectType/Description override for IfcSystem. - Allow using "IfcExportAs" = "DontExport" to remove an individual element or type from the export. - Export DuctLining. - Export Groups, including nested groups, as IfcGroup. - Export electrical systems and connectors. - Export local coordinate system for IfcDistributionPorts. - Export PipeInsulation. Bug Fixes: - Allow MEP zones to export Pset_ZoneCommon, fix 2 property names. - Correct export of parts for Coordination View 2.0. - Correct height of Revit Areas. - Correct material assignment for generic MEP exporter. - Correct units and unit scaling for volumetric flow rate. - Fix export of multi-storey stairs. - Get material for ducts and pipes from system. - Properly associate internal ElementType Revit property sets with IfcElementType, instead of adding to instances. - Properly scale door and window lining properties. - Protect against trying to add a null property to an IfcPropertySet. - Remove extraneous property sets when exporting Rebars. - Remove stale IfcSurfaceStyle and IfcPresentationStyleAssignment handles from caches for some aborted attempts to export items as multiple IfcExtrudedAreaSolid. - Return correct Boolean value for GetBooleanAtribute function.

What’s new for IFC Export Alternate UI for Revit 2014 v2.2/ IFC Export Alternate UI for Revit 2013 v1.10:
- Re-group the custom options into more logical groups.

Ok, this is a bit counter-intuitive but:
If you want to export parameters from Revit to an IFC file, note that the parameters should not be grouped under the category "IFC parameter", but under a different (eg, .. ID data, text) category.

This is because the IFC parameter group is for inbuilt / standard IFC parameters.



via
Autodesk BIM Blog - Tipp f�r IFC-Parameter Export f�r Revit Produkte

via email:

---

What’s new for IFC Exporter for Revit 2013 v2.8:

General: - Clean up code dealing with door and window operation and construction type. - Clean up code dealing with getting Solids from element geometry. - Finalize support for FM Handover view.  The new functionality for this is included in the lists below. - Replace native function call to create some columns as extrusions with .NET code. - Renamed the shared parameters for many entity properties to have "Ifc" at the front. - Sort parameter names on export to minimize changes in IFC file from subsequent exports of the same file. New Functionality: - Add 11 new IFC common parameter sets, including: Pset_AirTerminalTypeCommon, Pset_DistrubutionFlowElementCommon, Pset_FlowTerminalAirTerminal, Pset_SpaceOccupancyRequirements, Pset_PlateCommon, Pset_ReinforcingBar*Common - Add support for IfcLengthMeaure parameter export. - Add support IfcCircleHollowProfileDef; use for extrusions if appropriate. - Add support for Provisions for Voids. - Allow specification and export of a user-defined classification system, instead of just Uniformat. - Allow exporting elements as IfcDiscreteAccessory/IfcDiscreteAccessoryType. - Allow "IfcExportAs" to take both the entity name and the type name in the format "IfcEntityName.TypeName". - Export base quantities for 5 elements: IfcBuildingStorey, IfcCovering, IfcDoor, IfcSpace, IfcWindow.  Some of these were already supported and were just moved from native to .NET. - Export FabricArea and FabricSheet as IfcReinforcingMesh and IfcGroup, respectively.                  - Note: that the default export settings have these set as "Not Exported" - these have to be updated manually to "IfcReinforcingMesh" and "IfcGroup". - Export ceilings as extrusions or BReps if possible, instead of just surface models. - Export surface styles by default for Coordination View 2.0. - Include Ceiling as a room bounding element on export if it is part of only one room. - Stabilise GUIDs for Pset_Building/BuildingStorey/SiteCommon, internal Revit property sets, and slabs in roof containers (only for  the case of an IfcRoof containing a single IfcSlab, however). Bug Fixes: - Changed incorrect "PSet" to correct "Pset" for various parameter set names. - Don't create openings for doors and windows when the host is exported as parts - Don't export RepresentationMap for IfcTypeProduct with 0 items. - Don't ignore an internal Revit parameter on export if it has the same name as a parameter in another group. - Export materials for IfcReinforcementBar; make body representation "AdvancedSweptSolid". - Fix export of grids so that only one IfcShapeRepresentation is created. - Fix export of some extruded columns that were split into separate components by other elements. - Fix issue where classification reference was not exported in non-English versions of Revit. - Make "NosingLength" parameter of PSet_StairFlightCommon IfcLengthMeasure. - Make GetExportTypeFromClassName not reject some unrecognized IFC class names. - Move the local placement of many entities with extrusions and mapped representations for geometry to be closer to the geometry. - Properly export Pset_ZoneCommon for IfcZones. - Properly label some mislabelled IfcOpeningElements as "Opening" or "Recess". - Properly scale door panel properties, window frame properties, and base quantities on export. - Remove incorrect PsetLightFixtureCommon.ArticleNumber property.

What’s new for IFC Export Alternate UI for Revit 2013 v1.8:
- Export surface styles by default for Coordination View 2.0.

Or is it a professional, individual endeavor?  Or both?  Five quick quotes from different parts of the latest JBIM:
When practiced correctly, BIM is meant to support collaboration across the facilities life cycle. BIM is the flow of information through a project, from inception to completion and throughout the entire life cycle of a structure.

Unfortunately, the industry is still developing separate models that are not communicating.

... as projects become bigger and more distributed, some teams struggle with the collaborative aspects inherent to BIM.

The utilization of BIM technology can result in improved occupational safety by connecting the safety issues more closely to construction planning.

IFC4 introduces the concept of material profiles, where axis-based components, such as beams, pipes and ducts, can be described by paths and cross-sections of materials, along with offsets relative to the axis and end points.

The journal seems to contain quite a bit of info on NBIMS,  NBIMS-US and even IFC4.



Heads-up via:
Download BIM Can Be a Team Sport | Journal of Building Information Modeling – Fall 2012 | Bradley BIM

IFC Exporter for Revit 2013 | Autodesk Revit | Autodesk Exchange Apps
or
http://sourceforge.net/projects/ifcexporter/files/2013/IFC%20Exporter%20for%20Revit%202013%20v2.7.0.msi/download

Apparently this is version 2.7.  I may be wrong, but there doesn't seem to be an easy way to check the 'version' on Autodesk Exchange Apps.  If you download the MSI, you can check the properties of the file, where you will see that the digital signature is timestamped:
‎Wednesday, ‎23 ‎January ‎2013 10:39:38 AM

You could also check the IFC Exporter page on Sourceforge:

From the documentation:
The source code for this application is available on open source, at the SourceForge project : http://sourceforge.net/p/ifcexporter/home/Home/
This application is a good complement to the IFC Exporter UI client app, also available on the Exchange store. However, it is not required to get the latest version of that application when installing this application. Nor is it required to use this alternate UI when getting the latest IFC Exporter UI.

More info:
24th January 2013, version 2.7.  Read more at BIM Blog
http://translate.google.com/translate?u=http%3A%2F%2Fbimblog.typepad.com%2Fautodesk_bim_blog%2F2013%2F01%2Fifc-exporter-v27-for-revit-2013.html&hl=en&langpair=auto|en&tbb=1&ie=UTF-8

When I hear 'Chris Zoog', I can't help but think of his 2003 brainchild, the 6 phases of a Revit user...

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:


So here is the breadcrumb of credit--
Created by Chris Zoog, uploaded to Dropbox by theoryshaw, put on Youtube by BenPMalone.

In the webcast, Chris talks about (among other things):

• history of IFC
• using Grasshopper and Geometry Gym plugins with Revit (see my previous posts)
• drofus
• Generic Model Adaptive Components used in simulation
• clash detection / code compliance
• Tekla Bimsight / Solibri Model Checker
• "Navisworks is ubiquitous but this (Solibri) is the better tool"
• BCF - BIM Collaboration format 
• 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...

A summary of the webcast from LinkedIn:
Jeffrey Ouellette • Well, he showed several:

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. My old Kendo sensei would always say, "Don't TRY, just DO". He wanted us to understand the importance of removing the abstract from the shinai (bamboo sword) being an analogy of a metal blade to moving, behaving, reacting to it BEING a real blade. If you merely try, then you fail and give up because you feel there is no consequence. But, if you act as if your life is on the line, then you will only stumble for a while as you get better. 
via
Which file formats? Struggling to decide... | LinkedIn

2gb file
via
IFC Info - ThinkBIM™


Heads-up:

Hi @zoog, @nycrug great presentation on #IFC/OpenBIM, ended up recording it 4 U guys. bit.ly/VKplNF Video's huge though...2gigs. :|
— Ryan Schultz (@theoryshaw) January 16, 2013

@zoog we may have a solution ... Check out link thanks to @theoryshaw sites.google.com/a/revitall.net…
— ThinkBIM™(@revitall) January 16, 2013

A recent post from Eat Your CAD that has been getting some interest on Twitter ... I think more than a bit of it is tongue-in-cheek:
EYC - Addressing the 5 most important BIM questions

Here are a few quotes that tickled me:

1. Adopting BIM is a difficult and often unrewarding task.
2. “Open BIM” is what people on the leading edge are aspiring to and solves all your problems.
3. You’ll be expected to do extra work at a much earlier stage than you would have traditionally at a much lower fee.
4. BIM is based on a 3D model and therefore requires everything to be modelled as an exact copy of the final manufactured building component.
5. the quicker your architects can become qualified in structural engineering, the more benefit you’ll gain from BIM.
6. Mention that your closest competitors have all migrated to Revit and within a short space of time you’ll be promoted and your bosses will be able to smile smugly over their 5-iron and confidently state “We do BIM. What do you think about them apples?”
7. You cannot do BIM if you are a civil engineer, as civil engineers don’t build buildings.
8. To be safe, always leave an empty space at least 300mm clear of another discipline’s object.
9. Model as much detail as you can
10. Add every property that you can to every object

Funny stuff :-)