Delve into the process of creating clash reports, saving them as viewpoints, and publishing an NWD file that incorporates the clash report with Navisworks. This detailed guide explores each step of the process, offering practical tips and recommendations to streamline your clash report creation workflow.
Key Insights
- The guide recommends changing the report type to 'all tests separate', which, though not mandatory, makes it easier to manage the saved viewpoints, particularly when exporting multiple clash reports for ongoing projects.
- Creating a file system within your saved viewpoints allows you to save multiple clash reports as a record. This process involves creating new folders for the clash reports and sorting them by date to avoid overwriting data.
- By organizing clash tests as viewpoints and saving the file as an NWF, you can subsequently publish your model to a different file extension. The guide underscores the importance of not working in an NWD, as it can potentially disrupt links in the selection tree and prevent updates to the architectural model.
Note: These materials offer prospective students a preview of how our classes are structured. Students enrolled in this course will receive access to the full set of materials, including video lectures, project-based assignments, and instructor feedback.
Welcome back to the Navisworks video series. In this video we'll be looking at how to make clash reports as saved viewpoints and then how to publish an nwd file that contains that clash report. We'll be using the bim361-complete model in your lesson for six folder.
If you don't have clash detective open make sure you toggle that on and we'll be going to the report tab of the clash detective. If you save your file from the last video, which was the video in which we exported a clash report to HTML, then all of your content settings and your other export settings will have remained the same. The only thing different that we have to do this time is to change our report format to as viewpoints.
One other thing that's recommended is to change your report type to all tests separate. You don't have to do this but it makes it fan out much easier in the saved viewpoints under trade. So even if you export it all as combined it's pretty nice to be able to export to report type all tests separate as viewpoints.
If you don't have the saved viewpoints panel open go ahead and open it and then turn off auto hide. Next we'll just go to write report and then you'll see that your clash tests will appear as they're labeled in your clash detective. Because you'll be running multiple clash tests over the coming weeks if this is an ongoing project you'll want to have a file system within your saved viewpoints that allows you to save multiple clash reports as a record.
So just leaving the clash tests as viewpoints in their own folders in the root is not going to work since next time you export it's going to overwrite these. So let's make a new folder for these by right-clicking on the saved viewpoints panel and then go to new folder. Let's call this clash reports.
Learn CAD
- Nationally accredited
- Create your own portfolio
- Free student software
- Learn at your convenience
- Authorized Autodesk training center
This folder will house all of our clash reports. Then we'll make another new folder and call this one today's date. This is going to be the same date as the HTML clash report that we've exported before and then I'm going to select the first clash report folder and then the last one holding down shift so that it selects all of them in between.
Then I'm going to drag those into the today's date folder. You can collapse these if you'd like. Let's take a look at what's under these folders.
So the structural versus plumbing has first of all a reset appearance viewpoint and this is much like the full render and overrides viewpoints that we made and that the only purpose is to reset the appearance of our model. If you hit reset appearance then Naviverse works actually takes whatever you have on screen and changes the appearance back to a default setting. This is because if you go into say the group one viewpoint, I'm not getting the result I want.
Let me try it one more time. Yes, if we go to the group one viewpoint then you'll see that Naviverse works will have overridden the appearance of our model. This is not Clash Detective doing this anymore.
This is now the viewpoint changing our model to dim other and highlighting or changing the colors of our clashed items. When we go to reset appearance then it takes that off and I think that's a pretty ingenious tactic that Autodesk was able to implement in this program. Now that we have our clash tests organized as viewpoints, we can save this file first as an nwf, so just by hitting save, and second we'll be able to publish it to a different file extension.
Let's go to the Naviverse works application button and go to publish. We can call this one BIM 361 Clash Report with today's date. It's probably a different date when you're looking at this video.
Subject we can put anything we want in here. Author you can put your name. Publisher can be your company's name.
Published for copyright keywords, comments, password, all of these fields are optional, but if you would like to have metadata in your file then you can simply fill them out. We'll call this review for lesson four. If you set a password then whoever opens this file in the future will have to enter that password.
This is for security. You can make this file expire and this is a self-destruct function. After a certain date if you set this, if you check expires on after a certain date in here that you set the file will no longer be accessible.
It will exist as if it will be accessible on your hard drive, but when you try to open it will say no. And then hit okay. Naviverse works will give you the save as dialog at this point and we're going to go to our lesson six folder into clash report, the today's date, and then we'll save it in the root directory.
See that's saving as type navisworks nwd. Let's call this one bim361, crash report, today's date. When you use publish your file is not saved as in the same sense that if you were to use the save as button.
We're still in the nwf file. We're not in that published nwd at this point and that's a much safer way to do it because if we were to save this as an nwd file we would then be editing an nwd open file. So that would mean that all of our links in the selection tree would no longer be links.
If architectural for example updated their model we would not be able to update it in the nwd model. So be very careful that you're not working in an nwd. The nwf is the original, the nwd is the copy.
Let's navigate to the clash report folder, today's date, and then we'll see our nwd file. You can double click on the nwd file and your nwd model will open up in navisworks. You'll see that we're now in the bim361 clash report, today's date.nwd, and if we go to save viewpoints you'll see the clash report viewpoints same way that we just left them in our clash detective.
You can compare what is in your save viewpoints report versus your html report. Group two corresponds with group two here, so not only can I have a larger image of what I am talking about in my clash report, but I can see that image in 3D. I can turn on the grids and have a better understanding if I need to update this where this pipe is lying.
I've seen it's on grid line c. The bottom line is that if you use the nwd clash report with the html clash report then you're going to have a much better way of describing the clashes with the trades. When you're done viewing the nwd you do not have to save, you haven't made any changes to the original model, and if you go back to your navisworks nwf model then nothing that you've done in the nwd will have affected it. That concludes clash reporting.
I hope you enjoyed this section.