Once the clashes pertaining to our first issue are out of the main group, you will turn off the selection filter and select the Main group again with “Hide Other” on. You will now notice that you can’t see the issue you just focused on because it is no longer in your main group, but that’s great because you don’t want to see the same issue again—you’ve already marked it. With the first issue separate, you can move on to the next issue and never have to worry about duplicate clashes popping up in your coordination meetings. The process is simple; we are taking our ocean of clashes and localizing it into a lake of clashes that we can view without dimmed objects slowing down our computers. Then we are taking individual pools of clashes and separating them out until we are left with the sludge of false positives that we can then discard.
write a report you need to be very careful about your “Isolation” settings. Any isolation you have selected as well as any section cuts you have turned on will be applied to all the new viewpoints you write using reports. After the viewpoints have been made, you get a folder with the clash test name and inside it a “Reset Appearance” view and then a folder with the grouped clashes. When you select the folder it will go to whatever view you had saved for your group in the clash detective and it will have any isolation settings you had.
PRODUCT FOCUS
Navisworks Manage 2013
REPORTING Now we have all our clashes organized and we are ready for our coordination meeting. Because we have each issue separated, we can quickly move from issue to issue during the meeting, redlining and tagging along the way. Because we have grouped our issues separately, when we write a report we can select “Group Headers Only.” This is telling Navisworks that we only want to see the grouped folders as viewpoints and not the thousands of clashes we have inside those folders. With the service packs installed, Navisworks will bring over redlines and tags into those new viewpoints.
Figure 5: Viewpoints written as a report save their visibility attributes.
We write reports as viewpoints because they can be viewed in Navisworks Freedom. Being free, we expect all our trades to use it so they can go over everything that was covered in our coordination meetings and hopefully have those issues resolved in time for the next meeting.
Figure 4: Writing a report as viewpoints.
Navisworks 2013 has given us a new feature with reporting, but you have to be careful when using it. You have always been able to create a report using viewpoints, but those viewpoints would be saved without any “Hide/Required” attributes. Not anymore. Autodesk has made us a little more dangerous—now when you January 2013
Mark Hunter is a BIM Manager for C.W. Driver, a large general contractor in Southern California. The firm is highly regarded throughout the design and construction industry for implementation of BIM innovations on each project, and for creating customized software plugins to increase the efficiency of the latest software releases. Mark enjoys coordination, believe it or not, and is always looking for better ways to be efficient. He can be reached at mhunter@cwdriver.com, or at 909945-1919. www.augiworld.com
39