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.