Navisworks is a cornerstone tool for Building Information Modeling (BIM) professionals, facilitating comprehensive project reviews and coordination. A crucial aspect of practical Navisworks usage involves understanding and leveraging its file formats, particularly NWD and NWF. These formats play distinct roles in project workflows, impacting how data is stored, shared, and managed. This article delves into the intricacies of NWD (Navisworks Document File) and NWF (Navisworks File Set) formats, exploring their differences, applications, and how they contribute to streamlined project delivery. Whether you’re a seasoned Navisworks expert or a newcomer to the platform, grasping the nuances of these file formats is essential for optimizing your project workflows and maximizing the benefits of BIM.
What is an NWD File?
An NWD file, often called a Navisworks Document File, is a self-contained snapshot of your Navisworks project. Think of it as a frozen time, encapsulating all crucial project data. This includes:
- Loaded Models: The complete 3D geometry from various source files (e.g., Revit, AutoCAD).
- Scene Environment: Lighting, background, and other visual settings.
- Viewpoints: Saved camera angles and perspectives for easy navigation.
- Object Properties: Detailed information about each element in the model.
- Clash Detection Results: Crucial data from clash tests highlighting potential conflicts within the design.
- Markup and Comments: Annotations and notes made during project reviews.
An NWD file is a comprehensive archive of the project’s state at a specific point. This makes it ideal for sharing project reviews with stakeholders who may not access the source files or Navisworks (using the free Navisworks Freedom viewer). Due to the inclusion of all geometry and data, NWD files tend to be larger.
What is an NWF File?
In contrast, an NWF file, or Navisworks File Set, acts as a lightweight index or pointer to your source files. It does not store the 3D geometry itself. Instead, it maintains:
- Links to Source Files: References to the original CAD or BIM files used in the project.
- Viewpoints, Comments, and Markup: Saved views and annotations for project reviews.
- TimeLiner Data: Scheduling and sequencing information for 4D simulations.
- Clash Detective Data: Clash test settings and results without the embedded geometry.
The primary advantage of NWF files is their significantly smaller size. This makes them ideal for collaborative workflows where multiple users need to access and update the project data. When the source files are modified, the NWF file automatically reflects these changes, ensuring everyone is working with the latest information. This dynamic linking makes NWF files essential for ongoing project coordination and clash detection workflows.
Key Differences Summarized
- Data Storage: NWD stores all data, including geometry; NWF stores links to source files.
- File Size: NWD files are larger; NWF files are more diminutive.
- Use Cases: NWD for final project reviews and sharing; NWF for ongoing project coordination and clash detection.
- Updating Source Files: NWD is a snapshot; NWF updates with source file changes.
- Clash Detection: Both store clash detection data, but NWD stores the geometry with the clash data.
Related Blog
BIM and Clash Detection: Using BIM to identify and resolve conflicts early in the process
Read Now!The Importance of Clash Detection and BIM
NWD and NWF file formats are vital in Navisworks’ clash detection capabilities. Clash detection, a core function of BIM, allows project teams to identify and resolve potential conflicts between building systems (e.g., structural, MEP). Utilizing NWF files during the design phase enables continuous clash detection and coordination, ensuring design changes are reflected in the clash results. NWD files, on the other hand, provide a comprehensive record of clash detection results for final project reviews and documentation. By leveraging these file formats, BIM professionals can minimize costly rework and improve project outcomes.
