The ultimate goal of these tools and workflow is to improve MEP BIM coordination communication with project teams. The Navisworks add-in provides a means to automate clash metrics progress reporting, visualize clash data, and make model data meaningful and accessible for various project stakeholders. This workflow requires Autodesk Navisworks Manage, Microsoft Power BI, and Navisworks API to access the desired Clash Detective data for exporting. The tools and workflow are designed to have Navisworks Manage coupled with Microsoft Power BI to deliver multiple interactive visual reports in Power BI. However, this respository focuses on the Navisworks API add-in. The included Power BI template is only for reference and testing.
Environment setup regarding application development logistics.
-
IDE:
- Visual Studio 2019
-
Framework:
- .NET Framework 4.7.2
-
Language:
- C#
-
Output Type:
- Dynamic-link Library (DLL)
-
Additional Library Packages Implemented:
- Navisworks API
- Autodesk.Navisworks.Api
- Autodesk.Navisworks.Automation
- Autodesk.Navisworks.Clash
- navisworks.gui.roamer
- AdWindows
- Microsoft.Office.Interop.Excel
- Navisworks API
Application features and specs for Navisworks Manage add-in
-
Software Required
- Navisworks Manage 2019
- Microsoft Power BI
-
Navisworks Model Preparation & Clash Detective Setup Requirements
- Models appended need to be solids (not polymesh)
- Consistent model file naming convention
- Defined Focus Zones
- Active Grid System must be set to Grid System that includes boundaries of Floor Plan used in Reports
- Setup rules for clash tests to eliminate false positives
- Cannot Compact Clashes
- Always Update "All Clash"
-
User Interface
- User to specify focus zone for data being exported
- User to specify project disciplines (ability to save project discipline list and be loaded for future exports)
- User to specify repository location for data output (Excel file type) to be saved
Overall workflow from Navisworks Manage to Power BI
- The Clash Data Exporter add-in has two modules:
- Clash Test - Exports specific Clash Detective data and writes in Excel spreadsheet
- Total Objects by Discipline - Exports total objects in open model by discipline for producing metrics in Excel spreadsheet
- User prompted to specify focus zone associated with exported data and project disciplines
- Power BI Reports
- Projects are created using a template: Project_Name-Clash_Matrics_Template_V2.pbit
- Create new project using template: File --> Import --> Power BI template
- Select exported Clash Data location generated from the add-in for ClashData and TotalObjects parameters
- Videos links to examples of the Power BI report functionality
- Projects are created using a template: Project_Name-Clash_Matrics_Template_V2.pbit
Below highlights specific API features implemented to access and export specific Clash Detective Data
- How API is mapped to data in Clash Detective UI for OPEN clashes
- How API is mapped to data in Clash Detective UI for CLOSED clashes
- How API is mapped to model files in Selection Tree UI
- Export from Clash Test module
- Export from Total Objects by Discipline module
- Clone or download project.
- Open ClashData.sln in Visual Studio 2019.
- Ensure that the library packages stated in Getting Started are installed and referenced.
- The application can then be run in debug mode.
- Go to Debug/Release location and copy the files and folder below.
- Create a ClashData folder in Local_Drive:...\Autodesk\Navisworks Manage 2019\Plugins
- Paste copied files and folders to ClashData folder
- Open Navisworks Manage 2019 to execute and test add-in.
- Tools and Workflow described here are based on AU 2019 Presentation: Visualizing Clash Metrics in Navisworks with Power BI - Carlo Caparas
- Customizing Autodesk® Navisworks® 2013 with the .NET API - Simon Bee
- Navisworks .NET API 2013 new feature – Clash 1 - Xiaodong Liang
- Navisworks .NET API 2013 new feature – Clash 2 - Xiaodong Liang
- API Docs - Guilherme Talarico
- Power BI Documentation - Microsoft Corporation