Where I used to work (with SolidWorks) we saved everything in a Windows project directory on a shared drive and it was FUBAR until they installed the Enovia PDM system. (Maybe some of you have experience with it.) Everything was ECO controlled and went into the vault. It made things easier for saving files out at each revision since Enovia tracked versions, revisions and the release state of the file(s). All files that were gotten out of the vault were read-only and if a change was needed the file was checked out, changes made, then checked back in at the next revision level before being released to an active state. I'm not saying we need something as expensive (over-priced) as Enovia but didn't Alibre have a vaulting system for a while and would that solve some of the issues that are being discussed? Would it make sense to have a vault and what would it take to re-implement it? It sounds like Lew has a system that works for his needs but you need to be on top of your game to make sure you don't save a new version over the top of an older one. And it sounds like you would end up needing a lot of storage space, especially if all standard hardware gets copied into each project folder. That seems like a lot of duplication of files.