


Three years ago, the NWD file format was the standard, and many people didn’t know of other formats that were being used to make things easier. What will change drastically from firm to firm, though, is how the after effects of these meetings are posted to an FTP server, Autodesk Buzzsaw, or something similar. Some save the collision viewpoints as screenshots in a physical paper collision log, to inform each trade of specific objects that need to be moved out of the way, while others might email the group, listing the collisions and the proposed changes and sign-off requests. Some might hold biweekly coordination meetings while others meet weekly. This is standard, and you won’t see much give or take in this particular situation. To collaborate efficiently, the LBC (Lead BIM Coordinator) firm will bring all trades working on the project together for weekly coordination meetings, present the collisions with other trades, share potential problems with installation based on the 3D model they will be flying around in the meeting on a projector or smartboard.

I simply wanted to get you in the mood for the following information on the subject matter. Okay, enough about my love for Navisworks. It flies through 40MB files with 10s of overloaded external references attached like it was a simple 24KB, one-line diagram in AutoCAD®. There is nothing comparable in its class. You could even say that it has become an industry standard, which is rare considering it is a software application (that has dominated the market, nonetheless). Many construction firms are now using Autodesk® Navisworks Manage as a tool for collision detection and coordination collaboration with other trades working on the same project.

Back February 10th, 2012 Know Your Navisworks Files
