HELP! TFS vs. OpenText Document Management System

[Penthesilea]

Hello,

I am implementing Flare as a pilot project in a very large, complex corporate environment. I've been chasing my tail trying to get our content under source control. I want to implement TFS, which the developers are using. A separate, yet powerful group, is implementing OpenText, which is a document management system. They claim that I can use that for version control.

I am desperately trying to make my case against using OpenText http://www.opentext.com/2/global.htm; however, I could use all the ammo I can get in order to go toe-to-toe with IT and upper management.

My arguement thus far is:
- TFS can be linked to Flare using the API.
- TFS is source control for software (ie: xml) development; Document Control Systems is designed for managing final deliverables. (ie: pdfs, word docs)
- OpenText is a small, proprietary software company that may not exist in 3 years; Microsoft will be here.
- Using OpenText for techwriting source control is like killing a flea with a sledgehammer.
- OpenText is a massive enterprise solution that requires consultants for every configuration change. We would be tied to them for better or worse.

Can any of you offer any more thoughts in this regard? Any knockout blows that I'm missing?
Thanks

[RamonS]

The core argument should be that everyone should be allowed to choose the tools that lets them produce the best work. Aside from that, TFS is known to work for Flare, OpenText is a big unknown. Is TFS used for automated builds and automated testing? If yes, then you have another BIG argument for TFS.

[senddangi]

Hi Penthesilea

FYI OpenTEXT is Canada second largest software development company, Now it has global presence, including strong presence in USA, Australia, South Africa, Europe, ASIA, etc

OpenTEXT is specific to Content Management & Business Process Management company. It has strong implementation expertise and business in ECM & BPM.

Please write me for furhter info
bdangi@solusofttech.com