I've posted about SmarTeam in the past and have hands on knowledge of what a nightmare the software can be (or used to be). My company purchased it in spring of 1999 and we gave it a heck of a run for almost a full year. I was tagged as the resident "guru" and spent at least an hour everyday on the telephone with the Application Engineers and Tech Support from SmarTeam itself. Being that their U.S. office is located in MA where my own company is located (not to mention SolidWorks headquarters) we also had people down trying to resolve all of the problems that were encountered over the course of our problematic year.
Bottom line, it turned out to be so much trouble that management decided to dump a very significant investment in time and money in favor of NO PDM SOFTWARE AT ALL. I have to admit that I was skeptical when they chose that route but believe it or not in many aspects this works better (at least for our group).
Anyhow regardless of all that one would want to believe that the product has improved since I last dealt with it hands-on. However, I have to echo the sentiments of other contributors to this thread and encourage you to look into PDM/Works who has a far superior reputation to SmarTeam overall (even among all of the VARs that I know). I've recently heard through the grapevine that SolidWorks actually has acquired PDM/Works so that ought to give an indication of the software's high esteem. Although in fairness SmarTeam has the same parent company as SolidWorks so there's a "family" connection there too.
What I know about SmarTeam is that it is a sophisticated and complex piece of software and when I used it very prone to bugs, errors, and other nasty behavior. Also at the time we had the full-blown version versus the dictatorial and non-customizable SolidWorks-centric version of the software. The majority of the problems that arose with SmarTeam were with the SolidWorks integration and vaulting functionality of the package. These impacted our design efforts quite significantly when we attempted to roll it out within the design engineering group after pilot testing. Basically it screwed up so much that we had much difficulty getting any actual work done and I had a line of whining engineers, designers, and drafters at my desk almost everyday when I arrived at the office. And you probably don't even want to know what it was like when I took a day off!
Anyhow I could go on for a very long time about this (if I haven't already) so here's what I'd like to impart in closing if you're seriously looking at SmarTeam.
1. You're going to need someone in the engineering design group to administer full-time. (DON'T BUY INTO ANYTHING THEY TRY TO SELL YOU THAT CONTRADICTS THIS OR YOU WILL REGRET IT.... I PROMISE!)
2. Put your best CAD guy on the implementation team. No offense intended to engineers but a designer or drafter with exceptionally strong SolidWorks skills (i.e. understands "manual" file management of solid models) will work best in most cases in my opinion as opposed to an engineer who might not necessarily eat, sleep and breathe SolidWorks. It's all the better if they understand programming, database, and networking concepts as well.
3. Plan on a fairly lengthy implementation/pilot period (I'd plan on 3-6 months at least).
4. Get management "buy-in." PDM software can't be perceived as a "choice" by the people using it. If it is you'll be sunk until management throws a public beating on any dissidents.
5. Formal training and standards regarding how to use the software are key as well. Everyone needs to know how to work with PDM in the same manner as the next person.
SmarTeam hopefully has improved in the years since I last dealt with it however regardless of that I encourage you to check out as many PDM packages as possible before deciding.
Please post additional questions if you'd like.
Best Regards,
Chris G.