Using NWD file for clash detection

[jbaumann]

Are there any inherent drawbacks to using a .nwd file for clash detection? I have a sub-contractor that is providing .nwd updates weekly. Is anyone using nwd files for clash detection regularly?

[RobertB]

A lot of us are using NWD files for clash detection because it puts the responsibility for making sure the Navisworks model is complete on the firms producing the models. Otherwise, if the clash coordinator is the one creating the Navisworks models from the original conent models you can only hope that all the required software and object enablers are installed on the coordinator's workstation.

[jbaumann]

Otherwise, if the clash coordinator is the one creating the Navisworks models from the original conent models you can only hope that all the required software and object enablers are installed on the coordinator's workstation.

Good point. Thanks for the quick reply.

[Teresa.Martin]

Good point. Thanks for the quick reply.

But....it does not update as you get the updated datasets...That is why for a working week to week clash test, usually and NWF is better.

Best regards,

[Ferroequine]

That is why for a working week to week clash test, usually and NWF is better
Curious, why so long between NWD publishes? We produce an NWD of our entire plant every morning, and it is not a small plant.

[Teresa.Martin]

I was not saying you only publish once a week, I was referring to once a week big room meetings and field coordination. You can publish as frequently as necessary.

[mtcdesign]

The best option regardless of who published the NW file is an .NWC file, to ensure automatic update of unchanged information just make sure the file name is the same as the extg one. Then all you will need to do is re-run the CD with the updated file.

In my firm I implemented a procedure to maintain file naming for this exact reason, we now save archive files with dates and the most current file always has the same name.

[steve.perkio]

I disagree.
nwc files can be accidently overwritten by editing the similarly named cad file locally (assuming that you have attached the dwg) and can create issues.

Appending nwd's to the nwf doesn't seem to affect the information at all, and puts all ownership issues on the person supplying the file (coordinator).


The best option regardless of who published the NW file is an .NWC file, to ensure automatic update of unchanged information just make sure the file name is the same as the extg one. Then all you will need to do is re-run the CD with the updated file.

In my firm I implemented a procedure to maintain file naming for this exact reason, we now save archive files with dates and the most current file always has the same name.

[mtcdesign]

I disagree.
nwc files can be accidently overwritten by editing the similarly named cad file locally (assuming that you have attached the dwg) and can create issues.

Appending nwd's to the nwf doesn't seem to affect the information at all, and puts all ownership issues on the person supplying the file (coordinator).

Ahh, still using CAD... We use Revit only. Therefore, an .NWC is the best option for Revit. I agree with you that if you load a .DWG it could be an issue with overwriting files. I should have been more clear that this is the best option from Revit.

[hkossila]

We ask for NWCs from our subs because at some point in near past (and maybe I'm remembering wrong) you needed to have a navisworks license to nwdout, and some of the subs don't have navis. I seem to recall getting a navsis exporter on the subscription site that did not require a license, but it was for nwcout. A lot of our subs use autocad based ad ons. Well anyway, we have been having some issues with nwcs not updating, nwcs changing to dwgs in the selection tree and then not updating, etc. I'm wondering if maybe it's related to this nwc/nwd debate, nwc's being a cache file. Autodesk has actually recreated this issue and is trying to figure out the cause, any thoughts from others? I think I'll start a new thread on this.

[steve.perkio]

Ahh, still using CAD... We use Revit only. Therefore, an .NWC is the best option for Revit. I agree with you that if you load a .DWG it could be an issue with overwriting files. I should have been more clear that this is the best option from Revit.

It's odd, out on the west coast all coordination is perforned with AutoCad based products by the MEP trades.

The building model, steel, and usually the fire sprinkler come from Revit or other programs, but it seems that a lot of the discussions here (and other sites) assume that (either) everyone uses Revit, or overlook the fact that there are other phases to construction and that we haven't made the jump to Revit because it's not ready for the level of modeling that we require for 3D (some call it BIM) construction trade coordination.

Perhaps a lot of the discussions are between design team Engineers as opposed to trade coordination by tradesmen.

We even see projects that mandate Revit from start to completion (3D Bim Coordination) but most of them (nation wide) end up being coordinated with AutoCad and Navis as mentioned above.


We specialize in Healthcare and other types of construction may vary.
Perk