Hello Roger,
I have been using Solid Edge for 5 years now and we are using Insight for 2 months now. I did the whole setup, from Windows Server 2003, domain controller, SQL Server 2000, SharePoint Portal Server and Insight Server. Being in South Africa mean that local support is somewhat limited unfortunately. It was not easy at first, to say the least, I had to figure a lot out by myself. There is a help file in the program directory of Solid Edge (search for sespimpgde.html) Right now I will probably do the whole setup in 6 hours.
Now the big question, was it worth it? I would have to say yes and here are my reasons:
1. Running a search or where-used takes no more than 4 to 5 seconds thanks to the SQL server.
2. Moving files and folders is a lot easier, without breaking any links.
3. Releasing a huge amount of files with the Life Cycle Assistant is very quick and easy.
4. We have big assemblies, up to 3000 parts. Working from your local cache is more stable and faster. SharePoint Server handles all the checking-in and –out of files from the server to your local cache.
5. Our filename and part number are the same. Insight prevents the creation of duplicate filenames, even if they are not in the same directory.
6. There are no broken links in our database and Insight makes sure it stays that way.
7. Although you have to pay for Windows Server and Windows SQL Server, Insight comes free with Solid Edge.
8. We can now revise a part from within the assembly environment.
I agree with Kenat, one of the biggest tasks is to tidy up your data before adding it to a managed library. You don’t want any duplicate filenames and broken links.
As long as you don’t have a lot of files and are working with relatively small assemblies you can get away without Insight. We got to a point where it became a problem and Insight does make the management of the data easier.
If you have any specific questions regarding the setup, you are welcome to ask me.
Kind regards,
Theodore
Solid Edge V19 SP6 on WinXP SP2