View Full Version : Navisworks Status Updates and Subcontractor File Revisions
tpovell
2009-07-17, 03:05 PM
The Issue: During the coordination process, subcontractors are posting revised model files on a weekly basis. The file names from week to week are similar except that the version number and date are updated to reflect changes made within the model. When running clash detective I will group clashes (great feature in 2010) and update statuses. Here's the problem. The following week I will need to bring in revised files and the name of the file has changed as mentioned above. Consequently, when running clash detective, all clash groups are lost and the statuses are all reset to new. Is there a way to get Navisworks to recognize a new file as a replacement of a previous file in order to preserve groupings and statuses?
This seems like it would be a common issue but I can't seem to find a solution to the problem. Any feedback would be greatly appreciated. Thanks for your help.
RobertB
2009-07-17, 08:50 PM
Well, don't rename the files. The process is broken, not the program. :wink:
steve.perkio
2009-07-20, 01:51 PM
Post the updated files with the same name in dated zip files.
cjehly
2009-08-14, 08:52 PM
I'm seeing more and more "coordinators" making this EXACT mistake, and having it as a requirement.
The easy way to get around this is to remove the original file, then when it prompts you for the path, point it to the new file with the new (dumb) name.
steve.perkio
2009-08-17, 01:36 PM
Sure that works, but creates work for the MEP Coordination Manager.
Either do the zip file name as mentioned above or store the files in a named folder with the date and have the file name the same.
You could also have a common "working folder" where averyone drops in a copy of their current file (they need overwriting rights) with the same name. that makes it easy for anyone to pull down the current files without digging through a bunch of different files.
Perk
I'm seeing more and more "coordinators" making this EXACT mistake, and having it as a requirement.
The easy way to get around this is to remove the original file, then when it prompts you for the path, point it to the new file with the new (dumb) name.
RobertB
2009-08-17, 03:26 PM
You could also have a common "working folder" where averyone drops in a copy of their current file (they need overwriting rights) with the same name. that makes it easy for anyone to pull down the current files without digging through a bunch of different files.That is exactly what I suggest at BIM kick-off meetings. Having all the neccessary model models in one location dramatically cuts down on the time required to upload/download files by removing the "hunt" for the files.
cjehly
2009-08-27, 04:16 AM
We're all on the same page on this one....
difffering file names in a shared model is NOT a good idea.
spread it around....
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.