BIM COORDINATION
NAVISWORKS
Model Quality Control Check Strategy
Prior to moving onto Navisworks
Make sure to put geometries into correct categories is a prerequisite condition to perform the successful clash detection.
Therefore, establishing a solid Model Quality Control is a key strategy for the success of BIM Coordination.
Model Quality Control must be planned and recorded in BIM Executive Plan. This can be achieved by following checking methods, each method will be performed in different timings and frequencies.
Visual Check
Visual check inspects the sanity of model elements on a daily basis. This can be performed in Revit by users.
Model Integrity / Data Check
The Model integrity/ Data check can validate model weekly (or as per company policy) by using BIM Manual and audit protocol. This check can be accomplished from Revit as well.
Interference Check
The Interference Check detects problems between two building model at major milestones or as per BMP specified. This will be done from Navisworks.
Export Foldering Structure
Originals Folder is being used to keep all sources of files (NWC, exported from Revit) and Original NWF file that contains the appended NWC files.
Issued to Consultants Folder is being used for exporting - Clash Report, Viewpoints, Clash scenarios, NWD file
Issued to Consultants Folder has sub folders. These folders will be named per following convention.
Date of issue (prefix) and the purpose of the issue.
Original Folder has sub folders. These folders will be named per following convention.Date of issue (prefix) and the purpose of the issue.
There will be Clash applied NWF file, exported NWD file, Clash Scenario List (in .xml format) and clash detection report (in .html format preferbly). Also clash viewpoints in separated sub folder.
* 180511_Clash Test List.xml
This is the clash detection scenario file and it has to be included when we are issuing to other dicipline. So that all of diciplines can input their updates into clash scenario once the changes are made. Once the clash detection scenario is fully established, matured and aligned through all diciplines then we only issue NWD file.
Source files from different diciplines.
NWF file created to append all the source file.
* There will be two NWF files in working flow.
One is original (clean) file and the other one which coordinated within clash scenario.
Thery will be contained into separate files.
Clash Detection Workflow
Start Navisworks Manager and append NWC files.
NWC file can be prepared from each dicipline's Native Revit file.
Otherwise other consultant's file can be linked into Main model (Architectural) then batch exported.
When NWC's are all appended into Navisworks environment,
Save as NWF by following naming convention.
Find items by using filters then save to search sets.
Find more items by using filters then save to search sets. Do for Roof, Door, Window, Curtain Walls
You can group the search sets. In this case "AR_ENVELOPE"
Searched and saved "Columns and Framing" from Structural Link. Search sets are ready for clash detection.
*My current window workspace can be exported to other teammates as well.
Set up Multitple Clash Detection Scenario (This will be exported as xml format and shared between diciplines.
In result tab, we will be able to get 3d views of clashing scene. We can put descriptions from review tool and also able to assign the task to specific dicipline.
Write Report function will support many options :
- You may save all the clash scenes as viewpoints into current project file
- You may export clash report as .html format and issue to consultants
- You may export clash report as .xml format and import into external add in such as Revitzo
* You can choose the data to export of your report
* You must visit "Selection Inspector" to setup the asset into Global Unique Information Data (GUID). This is critical otherwise you will always get Element ID of geometry which is quite useless as they changes everytime.
Clash Report exported into "Issued" folder.
The folder "S vs A - Columns, Framing vs Curtain Wall_Enclosure_files" contains all the clashing viewpoints (Clash scenes, see image below).
"S vs A - Columns, Framing vs Curtain Wall_Enclosure.html" file will work simultaeniously within the folder created.
It means that the folder and the html file have to be placed into same location. Otherwise the html file would not work.
*"S vs A - Columns, Framing vs Curtain Wall_Enclosure" is one of clash detection scenario- which means there will be a lot of folders and html files will be included into single issue. Refer to end of this article to find the information about standard clash detection scenario.
* Examplar view of exported report in html format. It will show clash scene and related datas of clashing geometries.
Item GUID will help to address the clashing geometries from the native Revit files.
Clash Detection Scenario - Strategy by Project Phase
