Here's what I want to do...

[r2dhart]

I have been tasked with implementing a system that will serve three roles for our engineering group.

First, it will replace VSS for our source code control. All of our engineers are familiar with VSS so we don't want to stray too far from that model. Earlier this year we experimented with Subversion but the model was too foreign for the team and we decided to look for another alternative.

Second, we want to use it for internal document control. Mostly things like use case documents, scope documents, software requirements, etc.

Lastly, we want to use it for vendor file control. What I mean by this is that we maintain a rather large library of files that are sent to us by outside vendors and are used in our daily work. We need to be able to track changes to these documents over time and reference older versions or perform comparisons between versions.

From what I have read I believe that Vault could fulfill our needs but I wanted to hear from people who are "in-the-trenches" and have used it for one or more of these purposes. Also, if there is another package I should consider for all or part of this please let me know. I don't have a problem splitting these up, I just thought it would be easier if I could do all three under one umbrella.

Thanks in advance.

r2dhart

[Beth]

I'm not one of the end users, but I believe our product can fulfill your needs. If you would like, you can send an email to support at sourcegear.com (attn: Beth) and I can answer any questions you may have. Also, we have a section where we have customer recommendations here: Vault fans: Post your testimonials here