Wondering whether to get vault or not

[Anonymous]

Our company does not do a lot of design work itself, we are a manufacturing company that has a bunch of project engineers, so we do not have much of a need to organize a ton of part files.  We mainly deal with prints, and sometimes models, received from customers.  We get a lot of designs for parts in many different formats, whether it comes from solidworks, unigraphics, inventor, or .cal, .pdf, .tiff and so on.  Then, because they are coming from different companies, the way they are labeled varies a lot when looking at redacted prints, different revisions and so on.  So my question is this, would it be benefitial to our company to get vault to organize these files?  We already have a server that mainly organizes the files in a decent fasion, but does vault help make sense of various versions of things when imported?  Can vault help rename files in an orderly fasion?

[olearya]

I have seen a number of customers use Vault as a sort of distribution tool in the past where documents are supplied by a number of external contractors and consolidated and managed in a single location.

In these cases the compelling reason to implement Vault is the ability for users to:

1) Quickly and easily search data (not just file name but document properties, title blocks or even full text) 

2) View read only copies of documentation (weblient access in Vault Collaboration) 

3) Simply control view and edit file access via document states and folders

4) It will also permit rename and edit properties while maintaining dependencies

5) It will of course also allow you to track history of file versions of revisions

Hope this helps.