IMAGINiT Building Solutions Blog

NEW Home for the IMAGINiT Building Solutions Blog

We truly enjoy writing blog posts and sharing them. But that’s not all we do. Our new blog site lives on the IMAGINiT Resource Center. 

The IMAGINiT Resource Center offers a searchable index of our older posts, on-demand webcasts, tips and tricks, case studies, whitepapers, and more.

Content from our amazing technical team will continue! We hope you’ll join us: https://resources.imaginit.com/building-solutions-blog 

BIM 360 Coordination and Navisworks Issues

We have seen a significant shift to the use of cloud-based technology, and more specifically in the construction world with BIM 360. Yet, while this shift is taking place, there is no denying the importance of maintaining desktop-based software. The good news is, these two environments are not in competition with one another, but in most circumstances intended to work together. This gives us the power and functionality of our desktop software AND the ubiquitous access to our information. We can use online based tools to further enhance our use of the information developed with our desktop applications. Whether that is in the form of instant access, team communication, or full project collaboration. For some time now this symbiotic relationship has evolved from as simple as a connection to the Autodesk Exchange inside Revit, to A360 and Collaboration for Revit (C4R), to now the BIM 360 and the multitude of connections both built into Autodesk software or installed as a plugin.

I could write pages about the different aspects available to connect information between desktop software and a cloud based platform, but this post is about one simple yet powerful feature now available between BIM 360 and Navisworks. There is now a plugin available that allows you to open your models from your BIM 360 coordination space directly in Navisworks. This will allow you to work on and see the Issues created in BIM 360, directly in Navisworks. And it works both ways, meaning it is bidirectional. You can create and manage Issues in Navisworks and those issues are available in BIM 360. All Issue activity is synchronized and coordinated between your desktop Navisworks application and the cloud-based BIM 360 project environment.

One small caveat! You do need to download and install the latest version of the BIM 360 Desktop Connector. You can then download and install BIM 360 Issues.exe (Click Here to Download). Okay, maybe another, this is only available in Navisworks 2019 service pack 1 & 2020.  Unfortunately, it’s not available for Navisworks 2021 as of this BLOG post.   

Once downloaded and installed, all you need to do is open an .NWD file you have published to a project in BIM 360. It’s that simple The Navisworks ribbon will now include a BIM 360 Issues tab where you can coordinate issues between Navisworks and BIM 360.

Oh, and by the way, this works in Navisworks Manage or Simulate. Overall, this is just one step in the direction of better and more efficient coordination and communication.

Navisworks Navigation Trick

One of the tasks of a BIM manager is to coordinate and review a building during the construction phase. Navisworks give us the ability to visualize a building through 3D geometry, but sometimes too much 3D gets in the way.

Problem:

If you are auditing the MEP, the architectural elements obscure your view of other elements. To picture the Mechanical, Electrical, Plumbing, or Fire protection elements, you spend a lot of time selecting and hiding the architectural elements’ categories; such as walls, floors, doors, windows, ceilings. You still need to know where those architectural elements are, right? You could create several selection sets of different architectural elements and set their transparencies high enough to see “through” them. But then you get a wire-type visibility mode that is still difficult to interpret.

Solution:

Before you export your architectural Revit model out to an NWC, export each one of the floor plans as a 2D DWG, with only walls, doors, windows, room names and numbers visible. Import that DWG floor plan in to your Navisworks model at the correct elevation + 1”. The 1” keeps the CAD file from having the “Moiré Effect” ( a visual perception that occurs when viewing a set of lines or dots that is superimposed on another set of lines or dots).

Now you can navigate in the model with ease, not bumping into walls or doors. You won’t have to hide architectural elements to see the services in the floors, walls or ceilings. During the review, it’s good to know your location in the building at any time. Now, just look down! This works well when transitioning between clash results too.

BIM Learning Session: Clash Detection Using Revit and Navisworks

by Nicholas Bowley

During our latest online user group meetings, we recorded an instructional demonstration on how to perform clash detection in Revit and Navisworks.  We discuss the pros and cons of each program and provided some tips for navigation the models and organizing your reports.

IMAGINiT clients can view the on-demand session on the ProductivityNOW Portal. Everyone is welcome to attend our free webinars and upcoming BIM Learning Sessions.

Have the clashes tell you where they are instead of searching for them.

Fig 1 - Revit 3D View      

Revit		Navisworks Manage
- Clash against categories		- Clash against specific geometry
- Clash against sections		- Isolate clashing geometry
- Working in native software		- Create hard or clearance clashes
- Navigate 3D views to find clashes		- Navigate 3D views to find clashes
- Export report		- Clash against space and time
		- Move from clash to native software
		- Apply colors to systems
		- Create sets based on rules
		- Track clash results against previous clashes
		- Create markups on clash results
		- Generate reports and outputs that can be shared.

Fig 2 - Navisworks 3D View

 

Watch the tutorial for more information.

Missing Elements when Appending/Linking Revit models into Navisworks

By Nicholas Bowley, IMAGINiT Building Solutions

There are several methods or Appending a Revit model into Navisworks. The method that is most efficient is debatable and often a compromise between performance and manual effort, unless you have IMAGINiT Clarity which can export .nwc (Navisworks Cache) automatically by schedule or on demand.

Navisworks has the ability to link in a Revit model directly by “appending” the .rvt file. The advantage to this method is that as you resolve clashes or make changes you can save the Revit file and click Refresh in Navisworks. It also eliminates much of the manual effort of exporting NWC files repeatedly.

If you have tried this method you have likely had the problem when linking Revit into Navisworks, Revit elements are missing. To solve or avoid this problem you need to understand and check the settings in Navisworks.

1. Click on the Application Menu  and go to the Options in the lower right.

2. Click on File Readers then Revit

3. There are several options and settings you should review and understand.

4. To resolve the problem of missing Revit Elements, check the Convert settings. There are three options; Navisworks View, First 3D View, and Entire Project.

a. By using Navisworks View the program will only import views that contain the word “Navis” in the name and it will only import Elements contained in those views.

b. Entire Project will bring in all of the Elements and 3D Views in the Revit Project you wish to Append.

Leveraging the Navisworks View by setting up named views in the Revit model or changing the setting to Entire Project should resolve the problem of Missing Elements when Appending/Linking Revit into Navisworks.

BIM 360 Glue: Issue exporting NWCs from BIM 360 Revit Add-in

By Carl Storms, IMAGINiT Building Solutions

I had a client point out this issue to me. They tried to export a Revit file to BIM 360 Glue, using the NWC option in the “Glue” feature in the BIM 360 Revit Add-in. It was a Revit 2014 model exported from a 3D view. The project has two Revit links loaded. They set their Navisworks Exporter 2014 to convert linked files but after exporting to Glue, none of the links had been exported.

I did some testing and found that like my client said you cannot upload a Revit file with links to Glue using “Glue” in the BIM 360 Revit Add-in using a NWC format and have the links visible. I tested this in 2014, 2015, and 2016 and it would not work in any of them.

You can get the links to show if you “Glue” it with the DWF file format in all three versions (2014, 2015, 2016).

While looking for a possible solution in the BIM 360 Glue forum I discovered that this is a known issue for Autodesk.

“Just for clarification, the settings of the NWC Export and the Glue plug-in are independent. As a quick update, the error you are experiencing is a Revit issue which is currently being addressed.

We understand that this is a critical issue for our Glue customers, the team are doing their best to fix and release an update that solves this issue. I will certainly post an update in this forum once I receive a time frame as to when this will be resolved.” (Source Link)

The above was posted on Mar. 27th 2015, and as of today there has been no resolution posted.

The work around is to export the model as NWC from Revit using the export as NWC feature under the application menu, not by using the BIM 360 Add-in in the Ribbon.

Make sure when you do this that “convert link files” is selected in the Navisworks Exporter for the version of Revit you are using.

Then you can manually upload the NWC file to your BIM 360 Glue project and the links will be visible in that version within BIM 360 Glue.

 

It’s an extra step, but it does work.

Here is a screen shot (below) of what the file looks like when exported using the BIM 360 Add-in for Revit. The two linked files are not part of the model.

Here is a screen shot (below) of the same model that was exported using the NWC export feature under the application menu in Revit. The two linked files are now part of the model, and visible.

 

Navisworks Quantification 2015 Unit Problems and Fixes

By Veredith Keller, IMAGINiT Building Solutions

When you create a Project for Quantification, you select the catalog content to import, and you specify project settings, such as measurement units. A project is a collection of files and takeoff items that you use to produce detailed material quantities. Units can be set up for the project and for each property.
There are times you may want to change a property unit after you set up the project. This can be done by changing the units with a formula.
When you first open a file in Quantification, the Project Setup Wizard is displayed. This is where you specify Measurement Units and the catalog you want to use for organizing your takeoff data. You can integrate all the common catalogs you use for takeoff before you begin Quantification.

When you choose Next you can select a Unit from the drop down for each property.

Note: ModelVolume is set up for Cubic Feet.

When finished with the setup, from the Quantification Workbook, choose Item Catalog.

From the Item Catalog dialog box choose a group name and pick New Item  and give it a name.

Note: the Item Catalog for Volume is set up for Cubic Feet.

From the Selection Tree, drag items to the Item in the Quantification Workbook.
In this example all the Foundation - 12” Concrete walls are counted.

Note: in the WBS the total Volume is Cubic Feet.

Change the Volume to Cubic Inches; choose from the unit drop down Cubic Inches.

The Problem: when you change the unit to Cubic Inches the number does not change.

You can change this to read correctly, but you need to change the Formula. This can be done in the Item Catalog or in the Workbook.

Example in Workbook: Change the formula by choosing by line under Volume and type in the formula on the Function line.

Example in Item Catalog: under the Formula column type in the formula.

Note: If you set this up initially when creating a Project for Quantification from the ”Project Setup Wizard”, you can change the units from the drop down for each property and do not need to change the formula.

As seen in the example below ModelVolume is set for Cubic Inches.

 

 

 

Clarity 2015 - and have you met Matt or Beau?

You may have seen the recent IMAGINiT Clarity 2015  and Clarity Connect 2015 new release information that has been making its way around, but do you know two of the biggest forces behind the planning and development of IMAGINiT Clarity?

Meet Beau Turner, Director of Business Development, and Matt Mason, Director of Software Development. You may recognize them from other events like Autodesk University or the Revit Technology Conference, and we've used them to help put together a quick informational video about what this Clarity software is all about (below). Take a look and if this seems like it might be something that would be worthwhile to you, give is a shout and let us know how we can communicate with you best.

If you browse through this blog a little, you'll notice that there are some other informational posts in here about Clarity and SSL, and other tips and tricks on how to get around in the program.

Enjoy!

joe

 

Revit Wall Sweeps and Navisworks

We were running into an issue recently where a Revit 2014 wall sweep was not making its way into Navisworks 2014. The results varied a little depending on how the sweep was placed, but suffice it to say, the wall sweeps just weren't making the transition.

Veredith Keller, Senior Solutions Consultant with IMAGINiT, came up with the following solution that I thought we should share:

The solution involves using Revit to create parts from the walls during the Navisworks export process. To do this, in Revit select your wall with sweeps and from the Modify|Walls ribbon panel choose “Create Parts”

Now, for Navisworks to read these "parted" walls correctly, you need to adjust some additional settings - in Revit if you are exporting from Revit, in Navisworks if you are directly reading the RVT file. To get to the Revit export setting, Click on the "Navisworks settings" button in the NWC export dialog and turn on the option for "Convert construction parts".

For the Navisworks side of things (if you are directly reading the Revit model), navigate to Options / File Readers / Revit and make sure that the checkbox for “Convert construction parts” is turned on.

By default neither of these options are turned on.

Hopefully this helps, and remember to have fun!

 

Navisworks 2014 vs QTO 2013... what's up?

There have been a few questions coming our way about Navisworks 2014 and Autodesk Quantity Takeoff (QTO) 2013. Those questions have provided a nice opportunity to get out a blog post on some general Q&A about the two.

As you might have noticed, there are two different release years listed with the software above. Autodesk has not and is not releasing a 2014 version of QTO. Instead, Autodesk is building 3D quantification features into Navisworks Simulate 2014 and Navisworks Manage2014.

 

If you think about it, when you consider that Navisworks is the software that assembles information from all sorts of places into one evaluation and analysis location – where better to perform quantity takeoffs? In this Navisworks quantification environment, you are able to pull quantities from objects that were generated from a “BIM Platform” that provides object properties (ex. Revit) or non-BIM platforms that don’t provide object properties. The UI for this is something like QTO running in a Timeliner style interface. It needs to be wide and probably best to be docked at the bottom or top of your screen.

 

(Click image above to enlarge)

In slightly more detail, the quantification features in Navisworks that emulate features from QTO include:

Item and resource catalogs

• Import or create item and resource catalogs
• Associate items with resources
• Use formulas in catalogs
• Export catalogs

Model takeoff

• Automated takeoff from object parameters
• Manual takeoff for modeled objects
• Virtual takeoff for non-modeled objects

Change Analysis

Workbook

• Quantification reporting
• Export to Microsoft Excel spreadsheet software

You’ll notice that nothing above reflects a 2D takeoff workflow. This workflow is still supported though Autodesk Quantity Takeoff, and if you have a license of QTO (on its own or through a suite), you still have access to this software and its capabilities. Additionally, while there is a comprehensive API for Navisworks that supports integration with non-Autodesk estimation software, those plugins have not been created… yet. At this point, getting quantification information from Navisworks into other estimation software would be exporting from Navisworks through Microsoft Excel and into the 3rd party software.

I’ll also say that it seems like the quantification process in Navisworks seems to be a fair bit faster than it is in QTO. Probably more complete too since it is able to pull information from multiple modeling sources that might not have been able to be brought into QTO.

So now what?

All of the information above is what is, but the real question we want answered is what does it mean? (Please keep in mind that everything written here is opinion and attempts at prediction. Nothing is based off of knowledge or insider information.)

It would seem to me that QTO is going to remain as-is for the foreseeable future.  Updates will be made as needed to maintain functionality with current Autodesk software releases, and there might be an opportunity to enhance the 2D takeoff features of QTO as time moves on. However, it would appear that the focus of development for 3D or Model takeoff has migrated over to Navisworks.

Anyone who has QTO as a stand-alone product can continue working as they are today, but if you do 3D takeoffs, you will need to keep an eye on the developments of Quantification in Navisworks. At some point, you will probably want to make the transition from one to the other.  If you have QTO through a suite (and have that software on subscription), you will have access to both the Navisworks 2014 quantification workflow and the QTO 2013 workflow.

We can also make a comparison to Ecotect Analysis and Revit / Vasari. Ecotect Analysis still exists today for building analysis and can do a number of wonderful things, but its features haven’t been updated in years. Most of the critical features of Ecotect (and that is a subjective statement) have made their way to Autodesk Vasari, Revit, or both, but not everything. Revit and Vasari are quite obviously the platform for future analysis capabilities, but Ecotect is still out there if and when needed.

Hopefully everything written above helps to clear any confusion or questions that might exist about how QTO and Navisworks overlap and may be developed going forward – if I failed here, or even if I didn’t – reach out to us and we can help with whatever might be on your mind!

and don’t forget to have fun!

Joe