It really depends on what you want to do and how much legacy data you have.
Sharepoint is designed for version tracking of MS documents, that's it. It doesn't handle any other file types well. EDS/UGS created Insight, a front end to Sharepoint; or in other terms, a middleware between Sharepoint and Solid Edge, that makes it appear that Sharepoint can handle Solid Edge data.
Sharepoint is also designed to allow others search for and view documents easier. Problem is, the search function works on metadata and therefore if you have legacy data without metadata, either you have to add it in, one file at a time, or not use Sharepoint with it.
Sharepoint uses a webspace, a URL that is used to create a Network Place, as its file store. If you have legacy applications, like we do, that do not recognize a website as a file store, then you can't use Sharepoint. Well, you can, but the workflow to get it to function properly is something that none of your users will be happy with and therefore work very hard at circumventing.
Give Sharepoint a few more releases while MS figures out what direction they want to go with it. v2 is completely different than v1 and rather than having two different systems: Sharepoint Portal Server (SPS) and Sharepoint Team Services (STS); they now have three: SPS, STS, and Windows Sharepoint Services (WSS). Which do you install and which is going to be around next release so the migration path isn't like starting over as it is with SPS v1 to v2.
--Scott
For some pleasure reading, try FAQ731-376