See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/332240839

Navisworks Hacks for Efficient Workflows

Conference Paper · November 2017

CITATIONS READS
0 15,534

1 author:

Joseph Huang
Northwestern University
25 PUBLICATIONS   53 CITATIONS   

SEE PROFILE

Some of the authors of this publication are also working on these related projects:

BIM to XR Workflows View project

Scan to BIM Workflows View project

All content following this page was uploaded by Joseph Huang on 06 April 2019.

The user has requested enhancement of the downloaded file.

ES123128
Navisworks Hacks for Efficient Workflows
Joseph Huang
Stantec

Raghavendra Bhat
Stantec

Learning Objectives
 Learn how to plan your clash detective strategy and discover the purpose of
tasking on BIM Execution Plan
 Understand the big picture – review the big items first and reduce tolerances in
steps
 Learn how to set clash templates and search sets in Navisworks and clearance
zones in Revit
 Learn how to view clash groups from Navisworks Manage as shared views in BIM
360 Glue

Description
Clash detection and coordination, though not an entirely new concept, has gained traction in
recent years. It is a process of discovering the areas or elements that could possibly clash – or,
in other words, occupy the same space. It helps to reveal design conflicts before construction.
However, most projects we have been involved with or have observed do not allocate enough
budget for this process, and people still use a conventional 2D-drawing review method for
quality assurance / quality control. This class will cover best practices of model clash review
during the design phases and methods of tracking the revised/approved status. Today’s
challenge is how to manage the clashes efficiently besides just locating the clashes, because
most tools identify the clash location precisely. Moreover, with recent technologies like virtual
reality (VR) and augmented reality (AR), we can simulate the walk-through experience for better
communication with clients and team members.

Speakers
Joseph Chuen-huei Huang is Principal Architect / BIM Practice Leader at MWH, now part of
Stantec. He has more than 20 years of professional experience in the AEC industry and has
served as the BIM Manager for numerous large scale projects including the Panama Canal
Third Set of Locks. His project experience ranges from vertical construction to large-scale
infrastructure, where he has successfully integrated BIM into project design and construction
phases. Besides that, he is the author of Participatory Design for Prefab House: Using Internet
and Query Approach of Customizing Prefabricated Houses, and presents BIM-related topics
regularly to universities and global industry groups at international conferences like AU, SAME,
ACADIA, eCAADe, and CADDRIA. He is a licensed architect registered in Illinois, an AIA

Page 1
professional member, and holds a PhD degree in Architecture from the Illinois Institute of
Technology.

Raghavendra Bhat is a Building Information Modeling (BIM) leader at MWH now part of Stantec,
providing integrated project delivery expertise utilizing Autodesk, Inc., software. Bhat has over
12 years of professional experience working in the architecture, engineering, and construction
(AEC) industry using BIM technology on a wide variety of international and local projects (for
example, federal government, public works, wet infrastructure, and skyscrapers). Bhat has also
mentored, trained, developed standard guidelines and project standard templates.

Page 2
Contents
Navisworks Overview .................................................................................................................... 5 
BIM Execution Plan ....................................................................................................................... 5 
Tip #1: Model Requirements for Coordination (LOD) ............................................................................... 5 
Tip #2: Quality Control Check Plan ............................................................................................................ 5 
Tip #3: Coordination Analysis Strategy ..................................................................................................... 6 
Tip #4: Clash Review Workflow ................................................................................................................. 7 
Clash Types .................................................................................................................................. 7 
Type #1: Hard ............................................................................................................................................ 7 
Type #2: Clearance (+ Point Cloud data & Clearance Zone in Revit) ........................................................ 8 
Type #3: Duplicates ................................................................................................................................. 10 
Type #4: Soft (between moving components – using TimeLiner & Animator) ....................................... 10 
Best Practices ............................................................................................................................. 10 
Tip #1: Set Clash Rules and Templates (search sets & selection sets) .................................................... 10 
Tip #2: Clash the BIG stuff first and reduce tolerances in steps ............................................................. 13 
Tip #3: Grouping the Clash Results ......................................................................................................... 13 
Tip #4: Clash Report Formatting with your Company’s Logo ................................................................. 14 
Tip #5: Switchback between Navisworks and Revit ................................................................................ 16 
Tip #6: Dynamo for Navisworks & Clash Sphere Generator Plugin ........................................................ 17 
Tip #7: Compare Two Versions of the Model ......................................................................................... 18 
Tip #8: Selection Inspector & DataTools ................................................................................................. 18 
Tip #9: Visualization (A360 Cloud Render & Ray Trace Rendering) ........................................................ 21 
Tip #10: Quantification ........................................................................................................................... 22 
Tip #11: BIM 360 Glue Shared Views with Navisworks ........................................................................... 23 
Challenges and New Opportunities ............................................................................................ 25 
Case #1: Cut Openings ............................................................................................................................ 25 
Case #2: Parallel Clashing between Objects (“half‐embedded”) ............................................................ 26 
Case #3: Egress Path 3D Checking........................................................................................................... 26 
Case #4: Model not based on the Specs or Fabrication Details .............................................................. 27 
Case #5: Issue Tracking ........................................................................................................................... 28 
Case #6: Unusual Behavior & Workaround ............................................................................................ 28 
Case #7: Autodesk Point Layout within Navisworks ............................................................................... 29 

Page 3
Moving Forward .......................................................................................................................... 31 
Technology #1: Virtual Reality ................................................................................................................ 31 
Technology #2: Augmented Reality / Mixed Reality ............................................................................... 32 
Technology #3: Machine Learning / Artificial Intelligence ...................................................................... 34 

Page 4
Navisworks Overview
Autodesk Navisworks Manage is best described as a model aggregator that is designed to bring
together 3D models and their associated design data into a single working environment for
design review, coordination analysis, simulation and presentation. Navisworks has some
specialized tools like Clash Detective, TimeLiner, Animator, Quantification Workbook, etc. A
highly optimized 3D geometry engine which allows this composite virtual project model to be
interactively reviewed, visualized and analyzed in various ways in order to validate the design
and provide predictability for construction and operation.

It is also important to understand what Navisworks is not. Navisworks does not provide any
ability to create model 3D elements or modify the data in your design models. It does not have
any facility for working with 2D elements. Within the Navisworks workflows, the authoring of
design data is completely separate from the review, analysis and coordination of that data. The
primary focus of this class is about the best practices of model clash review with some tips and
tricks, challenges and new opportunities.

BIM Execution Plan

A BIM execution plan is a comprehensive document (or a collection of documents) that contains
all agreed upon processes for collaborating in BIM. This document is intended as a reference
during the project and a record at completion outlining protocols, relationships, responsibilities,
standards, model/data requirements, BIM uses, and outcomes.

Tip #1: Model Requirements for Coordination (LOD)

The most important aspect of design coordination process is planning, but a lot of people under-
estimate its complexity. Typically, we define WHO will model WHAT content and WHEN it will
be modeled in the BIM Execution Plan and develop a Model Element Table. Level of
Development (LOD) describes the various levels to which elements in a model will be
developed throughout the life of the project. The LOD Specification by BIMForum, the US
chapter of buildingSMART International is a good reference standard (http://bimforum.org/LOD).

It is critical to state the minimal size of a design object required to be modeled in the BIM
Execution Plan, so the models can have sufficient details to be analyzed during clash review.
Also, the team should agree on the approach of modeling and checking clearance zones such
as space requirements for accessibility and operation & maintenance access zones. Some
rule-based design review software (e.g. Solibri Model Checker) can check for various spatial
conditions in a generic way. In our best practice, we model that zone along with the component
(e.g. mechanical equipment) in Revit and treat it as a loadable family with some parameters to
control its visibility. Then, we can easily run clash review with “hard clash type” in Navisworks.

Tip #2: Quality Control Check Plan

Running interference check to discover the areas or elements which occupy the same space is
part of the quality control process to reveal the design conflicts before construction. The table
on next page shows four different levels of quality control checks, and we normally include this
in the project BIM Execution Plan.

Page 5
 QUALITY CONTROL CHECKS

Tip #3: Coordination Analysis Strategy

During the BIM Execution Planning process, the BIM manager and discipline leads should
develop a coordination schedule with analysis strategy (“System A” vs. “System B”) for clash
review. The content varies from vertical construction to wet infrastructure. Typically, we
perform clash review during the major milestones. Some design-build projects may need a
weekly clash review after 30%. The table below is one of our examples.

COORDINATION ANALYSIS STRATEGY

Page 6
Tip #4: Clash Review Workflow
Here is the recommendation of Design Coordination Review workflow by Navisworks. The first
part is weekly (or daily) “Design Review” led by the Project Engineer/Architect with BIM
Manager’s help. The intent is to visually check the design in a big picture (sometimes Revit is
too slow to navigate with all linked models turned on). The second part is running clash review
during major milestones (30%-60%-90% or weekly/bi-weekly depends on the project). We
saved all the grouped clash items as Viewpoints in Navisworks and provide the published
format, NWD file to the team to be easily viewed in Navisworks Freedom (viewer). We also
published the clash report in HTML (Tabular) format and converted that as a PDF (single
document with all images embedded). We uploaded all the clash review data (NWD, HTML,
associated image folder, PDF) to our Common Data Environment (e.g. BIM 360 Team,
ProjectWise) for the different needs of the audiences (e.g. project team, manager, contractor,
and client).

NAVISWORKS MODEL REVIEW WORKFLOW

Clash Types
Type #1: Hard
A clash in which the geometry of selection A intersects that of selection B by a distance of more
than the set tolerance.

Page 7
Type #2: Clearance (+ Point Cloud data & Clearance Zone in Revit)
A clash in which the geometry of selection A may or may not intersect that of selection B, but
comes within a distance of less than the set tolerance. Below are the settings for Clearance
Type with Tolerance: 3 feet.

CLEARANCE CLASH TYPE EXAMPLE

On Projects where we need to have certain access clearance for equipment, we pre-define or
hard code a subcategory within the equipment family. It is merely a plain mass extrusion that
defines the access zone requirement. We attach a pre-defined Clearance Zone material to it
which actually makes it transparent and identifiable easily for all other disciplines when installing
other elements around it, thus avoiding the access violation.

NOTE: For mechanical equipment that have connectors assigned and those that will be
included in the piping systems, avoid adding the clearance zone within the family as it will
change the color of Clearance Zone to match the Pipe system assigned color. In this case, we
use a loadable Clearance Zone family which is flexible and can be overlaid on any of the
installed equipment to avoid the additional effort of editing the base family.

Because these zones are associated with a special Sub-Category “Clearance Zones” the VG
can be easily controlled within Revit and we can use the clearance Sub-Category value to
create a Search Set based on a rule in Navisworks. In this way, we can easily run clash review
with “hard clash type”.

Page 8
 CLEARANCE SPACE REQUIRED FOR CLEARANCE SPACE REQUIRED AROUND
DOORS THE EQUIPMENT

PLAN VIEW - CLEARANCE ZONES AS SEEN IN THE NAVISWORKS MODEL

In order to perform clash detection on point cloud, there are two items to make sure you set
correctly. First, in the selection set, please make sure to click the Points button. Second, from

Page 9
the Type list in the setting area, you must choose Clearance. In the Tolerance edit box, enter
0.04 Inches or 0.001 Meters depending on weather your project model/scans are in imperial or
metric. (A point is an infinitely small area of space, with a dimension of ZERO in all axes. In
order for Navisworks Manage to do a "hard clash", the object would have to be *exactly* on the
surface of whatever is being tested - something that is highly unlikely. Using the "clearance
clash" checks for anything within the specified distance of the point.)

POINT CLOUD CLASH REVIEW SETTINGS

Type #3: Duplicates
A clash in which the geometry of selection A is the same as that of selection B, located within a
distance of between zero and the set tolerance. A tolerance of zero would therefore only detect
duplicate geometry in exactly the same location.
Type #4: Soft (between moving components – using TimeLiner & Animator)
From time to time, people got confused and used the term “soft clash” for “clearance check”.
Clearance clashes are not the same as “soft” clashes. Clearance clashes detect for static
geometry coming within a distance of other geometry, whereas soft clashes detect potential
clashes between moving components. Clash Detective supports soft clash checking when you
link it to Object Animation.

Best Practices
Tip #1: Set Clash Rules and Templates (search sets & selection sets)
Setting clash rules and templates may streamline the clash review process. However, one size
cannot fit all, especially when applying the rules. We need to be very careful to back check the
results after we applied any rules and clash review templates.

Example of creating a new rule to ignore the clashes between two Sets
1. Click “New” to create a new rule:

Page 10
 CLASH DETECTIVE – RULES SETTING

2. From “Rule Templates” list, select “Specified Selection Sets” and choose the set
from the “Rule Editor” drop-down menu.

CLASH DETECTIVE – RULES EDITOR

3. After applying “Ignore Clashes Between Concrete (set) and Conduits (set)” rule, all of
the clash results following this rule will become “Resolved” status (yellow color).
Normally, we won’t print the Approved and Resolved clash results in the report.

Page 11
 THE RESULT AFTER APPLYING THE RULES
Import & Export Clash Test as XML
We can recycle the clash test for the next project if the test selection is based on Search
Sets. Navisworks allows us to export and import clash test as XML format, and we can
create a company-wide standard clash review test (or customized one for each business
line/project type).

IMPORT/EXPORT THE CLASH TEST (XML)

Page 12
 Selection Sets vs. Search Sets
Selection Sets : are “static groups” of items. It usually involves some manually
“Hide Items” and can only be used on current project.
Search Sets : are “dynamic groups” of items generated by “key word search” in
“Find Items”. Search Sets can be Import/Export and reuse for multiple projects.

EXAMPLE OF A SEARCH SET (“HANDRAIL”)

Tip #2: Clash the BIG stuff first and reduce tolerances in steps
We use this strategy during the early phase of a project, and make sure that the “big” things
don't clash. Sometimes, you may find some surprise like the elevator and stair cores are
intersecting. We use this method to reveal the “issues” and refine the design instead of
resolving the interference “problems”. We also use this strategy to prioritize the clash review
tests. Generally speaking, the structural work like underground pipes, tunnels, sewers, or
existing structure that cannot be touched or moved. Then you can move through the disciplines
to the work that can be more easily and cheaply changed.

Tip #3: Grouping the Clash Results

Grouping the clash results is the way to make the lengthy clash results look more organized.
Each group name displays as a bold text “header” in the HTML (Tubular) clash report, and we
can see the overall clash view by clicking the “group” in Navisworks Manage. The best practice
of group naming convention is concise but descriptive. Examples like:
 Cut Openings (can be ignored if the openings are small; depends on the location)
 Clearance
 Equipment
 Pipe_Steel Beam (note: Under “Process Mechanical vs. Structure” clash test, we name
the clash group as “P’s sub-system vs S’s sub-system”)
 Duplicated Steel Column (model mistake)

Page 13
 EXAMPLE OF GROUPING CLASH RESULTS

Tip #4: Clash Report Formatting with your Company’s Logo

There are many different clash report format options available in Navisworks. HTML (Tabular)
is a nice format to illustrate all information within limited space. You may play around the
settings to reveal only the required contents. As I mentioned earlier, we also saved all the clash
results as Viewpoints in Navisworks and provide the NWD file to the team for review.

CLASH REPORT FORMAT OPTIONS CLASH REPORT EXAMPLE

You can easily replace the default “Autodesk Navisworks” logo with your company’s logo (or the
client/project-specific logo) by overwriting the “logo.jpg” in the HTML support image folder. See
example here (no need to call the original Autodesk Navisworks logo as “logo_backup.jpg”):

Page 14
 JPEG FILES IN HTML SUPPORT IMAGE FOLDER

Also, there is a “hidden” setting to change the exported image resolution and file formats from
the HTML clash report with the following steps:

1. Click the Application Button (big green N).

2. Hold down the Shift key, and then select Options.
3. Browse to the Registry -> Clash Detection -> Reports node of the options.
4. For Image Export, change to the desired image height and width.
5. For Image Export Plugin change the value from lcodpexjpg (.JPG) to lcodpexpng (.PNG) if
needed.

CHANGE IMAGE RESOLUTION AND FILE FORMAT

Page 15
Tip #5: Switchback between Navisworks and Revit
1. Open Revit application, the same version of Revit you used for exporting out the NWC to
Navisworks.
2. Click Add-Ins tab > External Tools > Navisworks SwitchBack to enable it.
3. In Navisworks Manage, Clash Detective window, on the Results tab, you can click the
SwitchBack button.

SWITCHBACK SETTING IN REVIT SWITCHBACK SETTING IN NAVISWORKS

4. Revit will load the relevant project, find and select the item, and zoom to it. If
SwitchBack was unsuccessful with the selected object, and you receive an error
message, try selecting further up the Selection Tree in Autodesk Navisworks.

THE RESULTS OF APPLYING SWITCHBACK

5. Note: If you try to use SwitchBack and the RVT file is not in the same location as when it
was saved, a dialog box will appear asking you to browse to the RVT file. When using
SwitchBack for the first time to load a Revit file, a 3D view based on the chosen
projection view mode is created in Autodesk Navisworks. The next time SwitchBack is

Page 16
 used to load a Revit file, the same projection view mode loads, unless the projection
view mode is changed in Autodesk Navisworks.

Tip #6: Dynamo for Navisworks & Clash Sphere Generator Plugin
What if your subs/consultants don’t have Navisworks Manage to utilize the SwitchBack function
or review the grouped clash results easily? The screencast link below shows an alternative
solution to use Navisworks, Excel and Dynamo to represent clash positions in Revit.

https://knowledge.autodesk.com/support/revit-products/learn-
explore/caas/screencast/Main/Details/9cfe3fad-3432-4d07-9110-c4a14a7af2c4.html

The Clash Sphere Generator Revit plugin by BIM One (now part of BIM Track platform) acts
exactly the same function if you are not familiar with Dynamo visual programming tool. Once
the report is exported by Navisworks in XML format, the tool is able to read locations and create
clash spheres in Revit. Each sphere is identified by an identification number stored in the report
which makes it easier to track and solve using Revit schedules. This file can be a new linked
RVT model for reference, and the project team can see and resolve all interference issues
directly inside the discipline model.

CLASH SPHERE GENERATOR UI THE RESULT OF APPLYING CLASH SPHERE GENERATOR

Download link: http://www.bimone.com/en/Apps

Instruction video: https://www.youtube.com/watch?v=R8zaCCUfVdA

NOTE: How to find the clash items in Revit model and resolve it? There are several options: (1)
By visual check with grids reference in Navisworks Freedom/Simulate/Manage; (2) By Element
IDs from the Clash Report and search that in Revit; (3) By using the Switch Back function
between Navisworks and Revit; (4) By Dynamo script (exported Navisworks clash result XML +
Clash Sphere dyn + Revit family); (5) BIM One – Clash Sphere Generator plugin for Revit.

Page 17
Tip #7: Compare Two Versions of the Model
This is a useful feature in Navisworks but not many people know or utilize it. When working in a
multi-disciplinary team, on a BIM project for example, you may be notified that a model file has
been updated. However, it may not be obvious what has changed between the previous
version of the file and the new one. The Compare Tool in Navisworks enables you to look for
differences between any two items that you select in the Selection Tree window. The items can
be files, layers, instances, groups, or just geometry.

To compare two versions of the model:

1. Open the first file that you want to compare in Autodesk Navisworks.
2. Click Home tab > Project panel > Append drop-down > Append, locate the second file,
and click Open.
3. Hold down CTRL key, and select both files in the Selection tree.
4. Click Home tab > Tools panel > Compare.
5. In the Compare dialog box, the Find Differences In area, select the check boxes for all
required options.
6. When the comparison is finished, the results can be highlighted in the Scene View. The
following color-coding is used by default:
 Original Colors. Matched items.
 Red. Items with differences.
 Yellow. The first item contains things not found in the second item.
 Cyan. The second item contains things not found in the first item.
You can save the comparison results as selection sets with automatic comments
describing the found differences in more detail.

THE RESULT OF APPLYING MODEL VERSION COMPARE

Tip #8: Selection Inspector & DataTools

To connect an external database to Navisworks the following workflow can be used.

Page 18
 Select the required elements using Predefined “Sets” and Open selection inspector (See
pointers “1 & 2” on image below).
 Using “Quick property definition” have the properties added that needs to be exported
out. Make sure you have the property>GUID added (See pointers “3 & 4” on image
below).
 Use the export to CSV option from top right in selection Inspector (See pointer “5”).

THE SETTINGS OF DATATOOLS IN NAVISWORKS

 Open CSV and add additional Properties/columns & save as XLSX.

 Open “Data Tools” form “Item Tools” ribbon (See pointer “1” on image below).
 Create new DataTools Links (See pointer “2” on image below).

Page 19
 Select ODBC Driver - Microsoft Excel Drivers.
 For Setup - select the XLS just saved.
 For SQL setup: SELECT * FROM [name of XLSX$] WHERE "GUID"=%prop("Item",
"GUID"); (See pointer “6” on image below).
 For Fields: add in the column names exactly as in excel. Save and close. (See pointer
“7” on image below).

THE SETTINGS OF DATATOOLS IN NAVISWORKS

Now when in Navisworks as you select the actuator you should be able to see a new tab
“Actuator Data” listing all the properties from the Excel file. When you publish NWD to BIM
360 Glue, the info gets carried along!

Page 20
 NAVISWORKS PROPERTIES – ACTUATOR DATA
Tip #9: Visualization (A360 Cloud Render & Ray Trace Rendering)
Autodesk 360 rendering is available since Navisworks 2015. Rendering options in the cloud are
faster and offer many types – still image, interactive panorama, solar study, color-coded
illuminance, lighting analysis, turn table, and stereo panorama. You can easily scan the QR
code or share the URL to your clients for them to experience it with a cardboard VR headset.

Viewpoints, with daylight or interior lights, can be rendered “on the cloud” and files stored and
reviewed on the Render Gallery. You will receive an email notification when the rendering task
is completed and no longer have to wait for Navisworks to complete a rendering. Submit a view
and continue to work. Images can also be downloaded if you need local copies.

A360 CLOUD RENDERING SETTINGS IN NAVISWORKS

Page 21
 A360 CLOUD RENDERING WEBSITE
Tip #10: Quantification
The Quantification Workbook is another core module of Navisworks where you can create a
highly accurate quantity takeoff based on the combined multiple 3D source files. It also works
with 2D takeoffs from a DWF sheet set. For more details, please see Autodesk Navisworks -
Getting Started with Quantification with some tutorial videos.

https://knowledge.autodesk.com/support/navisworks-products/learn-
explore/caas/CloudHelp/cloudhelp/2017/ENU/Navisworks-Manage/files/GUID-65A4E7A6-24E6-
4551-B7E4-4B117D66B5E6-htm.html

THE EXAMPLE OF QUANTIFICATION WORKBOOK IN NAVISWORKS

Page 22
Tip #11: BIM 360 Glue Shared Views with Navisworks
Navisworks has taken a major step forward with real-time BIM collaboration in the cloud since
2016 version. Within Navisworks, you can open, append, and align BIM 360 Glue project
models and then save as a merged model in BIM 360 Glue. As soon as the merged model is
saved in Navisworks, it is available immediately in the cloud for project team review,
collaboration, and coordination workflows using BIM 360 Glue desktop, BIM 360 Glue web, and
BIM 360 Glue mobile. You can also open models from BIM 360 Glue and use advanced
analysis tools, such as the enhanced quantification features, in Navisworks. Once you save
your work, data will be available for other Navisworks-connected BIM 360 Glue users.

These two products have distinct strengths that satisfy the needs of different project
participants. A comparison of the two products as below:

 BIM 360 Glue: Cloud-based coordination and collaboration solution that connects the
entire project team – internal and external, and streamlines project review and
coordination workflows.

 Navisworks Manage: A feature rich BIM project review toolset for the power user to help
perform advanced clash detection, quantification, 4D/5D analysis and construction
simulation.

AUTODESK NAVISWORKS AND BIM 360 GLUE SIDE-BY-SIDE COMPARISON

However, there is no way to group the clash results in BIM 360 Glue and any clash
groups saved in Navisworks Manage directly cannot be read in Glue. There is a
workaround to take the saved clash groups as Viewpoints and “sync” them as Shared
Views back to BIM 360 Glue with the following steps:

 From Navisworks, open the BIM 360 Glue model in which you want to run the clashes.
 Navisworks Clash Detective > Write Report > Report Format: As Viewpoints (Everything
or Group Headers Only)

Page 23
 Open BIM 360 Share Views from Navisworks BIM 360 tab and highlight the “Group
Header” from the Saved Viewpoints. Then click “New” in BIM 360 Share Views. It’s
good to rename the shared view to be more descriptive like including the clash test
name (e.g. Building #, STR vs. MECH).

THE EXAMPLE OF CREATING SHARED VIEWS BY CLASH GROUP HEADER IN NAVISWORKS

 Anytime you create a new Shared View, Navisworks will “auto-synchronize” the view
back to BIM 360 Glue Views > Shared Views even you didn’t save the model. You and
your team members will receive an email notification (activity ‘alert’) about a new view
has been created. Furthermore, we can use the Markups tool with some comments and
notify the project members about the clash result.

Page 24
 THE EXAMPLE OF APPLYING SHARED VIEWS IN BIM 360 GLUE

Challenges and New Opportunities

Case #1: Cut Openings
Based on my clash review experience, “cut openings” is the number one common clash result
generated by Navisworks because we normally don’t model the holes for pipes and conduits
penetrating the concrete slabs and walls. Depending on the project BIM Execution Plan’s
agreement, typically we don’t specify the openings for any pipes under a 3” diameter. However,
these clashes impact not only material takeoffs but also structural calculations as well. With this
in mind, we should carefully check every place where ducts, pipes, cable trays, or conduits meet
building elements such as walls, floors, ceilings, roofs, beams, etc.

Revit has some simple tools to build the void families along with MEP objects (e.g. louver) when
applying to the structural elements (e.g. wall). We also can use Shaft/Opening functionality
from Revit to make an opening manually. This method of placing openings is very time
consuming and you will have to manually move or recreate each individual opening if the design
has been changed.

AGACAD’s Cut Opening Revit add-ins can make holes around MEP systems automatically (the
free version doesn’t work with linked Revit models). By utilizing the HTML file generated by
Revit Interference Check, it identifies the locations of clash point of two elements to place a
void. After the HTML file has been browsed from your computer, you will get all the needed
cells to fill data about the opening: Opening Shape and Opening Cut Offset. After this is done,
save a combination of your clash report and configuration of openings as an XML file, which
contains each opening with its size, cut offset, depth, joining distance, etc. Users can then insert
openings with a click. If there is any repositioning of elements in the project, Cut Opening
detects it and gives a report of project changes. The software also detects host, dimension, and
position changes, and then the user can accept changes.

THE EXAMPLE OF CUT OPENINGS IN NAVISWORKS

Page 25
 THE INTERFACE OF AGACAD’S CUT OPENING PROFESSIONAL

Case #2: Parallel Clashing between Objects (“half-embedded”)

“Parallel Clash” is a term I invented to describe the situation where the pipes are not embedded
inside of the concrete or penetrate through the wall or floor. Most of the time, the pipes are
placed on the wrong level (or the floor or wall on the wrong location). This type of clash result is
better to be grouped, so we can easily review all “parallel clash” once by clicking the group
header either from the clash detection window or the saved viewpoints. Engineers will review
and make a decision to move the clashed items.

“PARALLEL CLASH” EXAMPLE

Case #3: Egress Path 3D Checking

From time to time, I observed some mistakes about the disconnection between the Fire, Life,
and Safety (FLS) drawing sheets and the actual final design plans. Some architects treat the
FLS sheets as “diagrams” to meet the minimal code requirements for getting the permit.
However, when we apply the “3D Egress Man/ Egress Path” Revit family

Page 26
(http://revitoped.blogspot.com/2007/01/egress-path.html) to the design model and review it in
3D, we found some serious issues. This is not a typical hard clash but it impacts our life if we
don’t design it right.

Instruction video about making a quick egress path family:

https://knowledge.autodesk.com/support/revit-products/learn-
explore/caas/screencast/Main/Details/e68d40f9-e622-492b-b6c3-decddb36758e.html

3D EGRESS PATH CLASH REVIEW EXAMPLE

Case #4: Model not based on the Specs or Fabrication Details

Sometimes we found the clash (or avoid the clash) in some detailed area but cannot 100%
verify this is a valid clash because our model is not based on the specifications with the
fabrication details (like shop drawings). This is very common when we do the design-bid-build
project delivery. We may put some contingency and do not put objects tightly, or rely on the
contractor to deal with that on site.

EXAMPLE OF THE HANDRAIL NOT MODELED BASED ON THE SPECS

Page 27
Case #5: Issue Tracking
How to handle an efficient issue tracking is really a challenge. It’s easy to find the clashes by
Navisworks, but not easy to resolve the conflicts among the disciplines in a timely manner.
Traditionally, people use an Excel spreadsheet to document all the clash items with comments,
and manually “cross out” the item once we resolve the clash. CASE (now WeWork) has
developed an Issue Tracker tool (https://github.com/WeConnect/issue-tracker) based on the
software developer’s QA/QC workflow.

Revizto Issue Tracker (https://help.revizto.com/user_manual/issue_tracker.html) is another

powerful task tracking system that allows teams to collaborate on cloud projects in real time –
assign issues, generate reports, and send email notifications.

EXAMPLES OF DIFFERENT ISSUE TRACKING METHODS

Case #6: Unusual Behavior & Workaround
We found some “unusual behavior” (maybe not a bug) in Navisworks and we would like to share
the workaround. The model elements changed (e.g. size, shape) when exporting the model
from Revit to Navisworks. Sometimes it’s enlarged or totally changed its geometry and Element
ID. The workaround is to rename the Revit family and re-import into the project to have a new
Element ID and GUID. These issues have been reported to the Autodesk Enterprise Premium
Support and Development Team. We just need to pay more attention to these details especially
when we involve complex projects.

EXAMPLE OF THE ENLARGED PIPE FITTING IN NAVISWORKS

Page 28
Case #7: Autodesk Point Layout within Navisworks
Autodesk Point Layout is a construction layout software that helps bring greater model accuracy
to the field. It is ideal for anyone who needs to conduct a layout on the job site. It creates
points on almost any objects and exports point locations to a total station. It helps not only do
the layout in the field but also helps in quality assurance to check and make sure the element is
installed as per the coordinated model.

Use the add-on to add control points & export to a CSV or directly to BIM 360 Field.

AUTODESK POINT LAYOUT ADD-ON FOR NAVISWORKS: ADD CONTROL POINTS INTO THE MODEL

DATA EXPORTED TO EXCEL

Page 29
Take coordinated 3D model-based layout to the field with the BIM 360 Layout iPad app
(requires a subscription to BIM 360 Glue cloud-based BIM collaboration software).

DIRECTLY EXPORT TO BIM360 FIELD

BIM 360 FIELD ISSUE EDITOR

Autodesk Point tool add-on also installs in Revit and AutoCAD.

AUTODESK POINT LAYOUT ADD-ON FOR REVIT

Features:

Page 30
  Create points (setout points)
 Export setout points to Total Station
 Import Field Conditions
 Perform QA/QC by comparing
 Slab Analysis
 Cloud Analysis feature can be used for verifying the accuracy of the As-built models in
comparison to the point clouds captured.

By specifying the maximum face deviation we can get a heat map (as shown from the
screenshot image below). It helps to identify the areas in the model that do not match the as-
built conditions. From the image we can see the columns, pads and door locations are clearly
displaced and not matching with the actual as-built. This can be a very good tool to verify the
as-built conditions & get them incorporated.

VERIFYING THE AS-BUILT CONDITIONS BY AUTODESK POINT LAYOUT

Moving Forward
Technology #1: Virtual Reality
 Virtual Reality (VR), also known as immersive multimedia or computer-simulated reality,
is a computer technology that replicates an environment, real or imagined, and simulates
a user's physical presence and environment to allow for user interaction. Most up-to-
date virtual realities are displayed either on a computer monitor or with a virtual reality
headset (also called head-mounted display), and some simulations include additional
sensory information and focus on real sound through speakers or headphones targeted
towards VR users. Some advanced haptic systems now include tactile information,
generally known as force feedback in medical, gaming and military applications.
 Example: Software – Autodesk Revit Live, Stingray, Fuzor, Revizto, Enscape, etc.;
Hardware – Oculus Rift, HTC Vive, Samsung Gear VR, etc.

Page 31
 It can be a good supplement for clash detection especially when checking the clearance
with a “human scale”, user’s perspective.
 A great opportunity for the owner is to train people during the operation and
maintenance phase to familiarize them with all the basics before involving anything that
would be dangerous in a simulated virtual facility.

VIRTUAL REALITY EXAMPLE (FUZOR + OCULUS RIFT)

Technology #2: Augmented Reality / Mixed Reality

 Augmented Reality (AR) is a live direct or indirect view of a physical, real-world
environment whose elements are augmented (or supplemented) by computer-generated
sensory input such as sound, video, graphics or GPS data.
 Examples: InfraWorks 360 iPad App, AR-Media with QR code and logo scanning,
Google Project Tango, Pokémon Go 
 To use Augmented Reality from InfraWorks 360 Mobile App:
https://knowledge.autodesk.com/search-
result/caas/CloudHelp/cloudhelp/2014/ENU/InfraWorks-MobileApp/files/GUID-
98459B25-3543-4335-AD72-A51C3250F2AB-htm.html
 Mixed Reality (MR), sometimes referred to as hybrid reality, is the merging of real and
virtual worlds to produce new environments and visualizations where physical and digital
objects co-exist and interact in real time. Mixed reality takes place not only in the
physical world or in the virtual world, but is a mix of reality and virtual reality,
encompassing both augmented reality and augmented virtuality.
 Example: Microsoft HoloLens, potential usages like design communication with a full-
scale digital markup, job site punch list coordination, RFI filing.
 Unlike Oculus Rift (Virtual Reality) and Google Glass (Augmented Reality), HoloLens is
combining the virtual world and real world, which is enhanced with holograms. The user
can see the real world like a laptop’s screen and the surrounding space while navigating
the digital model/scene in front of any defined location during the same time.
 Imagine taking your HoloLens to the job site and connecting to a wireless cloud service,
you can scan the space with your BIM model overlay. Moreover, you can actually place
new equipment into the real environment from a catalogue of holograms/objects, then
connecting them in-situ with pipework, valves and instrumentation.
 MWH, now part of Stantec in UK has done some amazing development so far to explore
various potentials to our daily practice. Some remarkable achievements include bringing

Page 32
 non-graphical data from external databases into the graphical interface for asset
management and overlapping the design model into the existing facility before
construction.

ASSET MANAGEMENT WITH VOICE COMMANDS BY HOLOLENS

 By using Visual Live 3D plugin for Navisworks and Revit (available from Autodesk App
Store), we can publish our models directly to HoloLens with HoloLive app (free from
Microsoft Store), and position the model to the right coordinate system using the QR
code marker/survey control in the field or you can visualize it with smaller scale using the
scale tool in HoloLive app.

VISUAL LIVE 3D PLUGIN FOR NAVISWORKS

 Creating a BIM workflow diagram could be a good way to learn and document the
process of using multiple software applications and output formats. The diagram below
shows a variety of applications to “translate” design models from BIM platforms to the
AR/VR wearable devices.

Page 33
 FROM DESIGN MODEL TO VIRTUAL REALITY / AUGMENTED REALITY

Technology #3: Machine Learning / Artificial Intelligence

At the end of this class, I want to challenge the attendees and Autodesk developers to think:
Can we apply machine learning/ artificial intelligence to Navisworks clash review process?
Oftentimes, when I see the results of new clash items automatically “jumping” into the existing
clash groups, I wonder what the logic is behind it. Can we teach Navisworks software about the
“pattern” of grouping things? It would save a lot of time if the software can do a quick grouping
of the clash results after we define the logic. What else can we improve Navisworks? Please
go to Autodesk Community, Navisworks Forums / Ideas (aka: Idea Station) to contribute your
thoughts and creative or crazy ideas. https://forums.autodesk.com/t5/navisworks/ct-p/4

EXAMPLE OF MACHINE LEARNING (CLASH-TO-GROUP AUTO FILE) IN NAVISWORKS

Page 34

View publication stats