Skip to main content
M
MSR1-Visitor
1-Visitor
October 4, 2010
Question

Moving From Intralink to SmarTeam

  • October 4, 2010
  • 3 replies
  • 1110 views
All,

Can anyone give me any reasons why I should not use SmarTeam to control
Pro/ENGINEER data that is currently being controlled with Pro/Intralink?
My company wants to implement SmarTeam instead of upgrading to PDM/Link.

Thanks,

WEBER AIRCRAFT LLC
SEATS

Mark Swarner
ENGINEER II
2000 Weber Drive - Gainesville - TX - 76240
Tel: (940) 668-4100 x4449
Mark.Swarner@zodiacaerospace.com

3 replies

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
October 4, 2010
6 years ago we had a similar challenge. All the other system sales people said "sure, we can manage Pro/E data. The application engineers at the same time said "no, we can't do that..." to the simplest of our specific requests.

We begged PTC for a simple, objective challenge like below - couldn't get them to do anything, so we made our own. Happy to send you that data set and procedure if you like (was created with Pro/E WF1 and Intralink 3.4; has about 30 files, all relationships but very simple geometry). We had an extensive challenge procedure of about 50 pages; no system except PDMLink even came close to working past a simple demo and failed on step 2. PDMLink failed a few (relative to Intralink 3.x) but those issues have since been resolved via the migration tools.


Simple test that used to be enough to easily show the differences (may not be enough now)

- Set up for Manual numbering for Pro/E data

- Create a small Pro/E data set with:

o Family table part

o Family table assembly including that part

o Drawing of that assembly

o Check all into SmartTeam

o Add an instance to the Family table part and check back in

o Rename (re-number the CAD Document of) the added instance and the generic of the family table using SmartTeam with nothing in Pro/E RAM

- Try to retrieve the Assembly drawing; see everything fall apart


If your company decides to go this way anyway, look for another job - easier than fighting with all the needed troubleshooting of Pro/E data that you'll need to do.

I'm not advertising for PTC; just sensitive to people not having facts in front of them for this discussion - which seems to happen over and over and over.
F
frederick.burke1-Visitor
1-Visitor
October 4, 2010
DANGER WILL ROBINSON DANGER!



1) Never buy a product with the word "Smart" in it... they are
always overcompensating...



Have you ever gotten consistently precise parts from a machine shop with
the name "Precision" in it?



Have you ever gotten consistently quality parts from a machine shop with
the name "Quality" in it?



Avoid desirable adjectives in your products at all costs!!! Remind me to
open a business named



"Crappy Machine". We will obviously do everything perfect the first
time... At least if we don't we



warned you right? "Smart" is for infomercials and people with more money
than they know what to do with.



If they want to burn their money, tell them to do it in the dumpster out
back instead of making your life miserable.



If your product has the word "Team" in it, it is built only to serve
itself and will not get along with any other software.



I would trust it more if they named it "Danger: Explosives" at least
that's honest.



2) PTC decided early on that their relationships were too complex
to be managed.



The purpose of metadata is so the relationships would not have to be
managed.



Every time you pull something from Intralink, it performs a half-launch
of that file and Intralink pulls



everything that the file is asking for. Even with that much lee-way
Intralink has problems. There are



ghosts and broken references that it can't fix. If PTC developed
Intralink with the understanding that their



relationships were unmanageable, how can anyone else hope to manage
their files with any degree



of certainty? Mind you, it has been done before, but not without lots of
pain, anguish, and cash!



Whoever said that giving birth was the most painful process ever, has
never tried to manage PTC



files with a third party file manager... Make sure the salesman says
it's OK before you do it!



The only thing you can bank on is your company's productivity dropping
dramatically!



Fully agree with Mark's "look for another job" comment...



OK... Monday rant done...



Live long and prosper!



Frederick Burke



From: Lockwood,Mike,IRVINE,R&D [
P
ptc-1458451-Visitor
1-Visitor
October 4, 2010
Mark,

Before I did my Pro/I 3.3 to PDMLink 7.0 upgrade, I reviewed SmarTeam,
Teamcenter, and Agile along with PDMLink.

Although all 'said' they could manage Pro/E data, most could not handle
simple things, such as Family Tables, and File name changes. The other item
we looked at was the ability to migrate our Pro/I database into the new
solution, and PTC was the only company that had a proven solution.

Additionally, the SmarTeam Installation/Configuration Engineer told us: "Go
with the PLM solution from the same vendor of your main CAD system."

Good luck in your decision.

-James Jarosz

On Mon, Oct 4, 2010 at 4:00 PM, Mark Swarner <
mark.swarner@zodiacaerospace.com> wrote:

> All,
>
> Can anyone give me any reasons why I should *not* use SmarTeam to control
> Pro/ENGINEER data that is currently being controlled with Pro/Intralink? My
> company wants to implement SmarTeam instead of upgrading to PDM/Link.
>
> Thanks,
> *WEBER AIRCRAFT LLC*
> SEATS [image: logo] *Mark Swarner*
> ENGINEER II 2000 Weber Drive - Gainesville - TX - 76240
> Tel: (940) 668-4100 x4449
> Mark.Swarner@zodiacaerospace.com
>
Terms & ConditionsAccessibility statement