Hi Guys,
We are about to try and start using vault but have already built up a large number of solidworks assemblies and we are trying to work out the best way to manage the transfer process to vault
By rights we should have started using vault at the same time we started using solidworks but that didnt happen.
The way i see it the best thing to do would be to methodically pack and go each existing assembly to the local working folder before tansfering it into vault, we would leave all the existing stuff in pre-vault folder structure on the network and mark up the files with superceeded or something.
Because its going to take a fair bit of time to get everything transferred into vault we are going to find ourselves insituations where common parts that are already checked into vault may also need to be referenced to by non vault assemblies.
Is there any way to do this
Cheers
James.
James,
I'm not, by any stretch of the imagination, a PDM expert. I just surf here to try and lean a bit about it, as none of the rest of us is very expert either. (The guy who actually took the extra half day training left the company several years ago and we have never gotten sufficiently scared to train someone else.) So take any advice with a hefty dose of salt.
If you are using a working folder, then your method of pack and go before transfer seems like the right thing to do. We have done this by projects. I don't see where there is much of a problem with common parts that are checked into the vault being part of the assemblies that are not yet checked in, unless you make changes to the common parts. (Most of our common parts are fasteners that don't get changed, or at least, not very often.) It seems like you could check out the parts, make the changes, and then check them back into the vault. You could then search for the files in your "outside" folder structure and replace the old files with your new ones.
I'm probably missing something.
Jerry Steiger