Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
x2 what Mr. Stewart said. That is the tool our consultant used and the architecture we had in Intralink 3.3 was duplicated in Windchill 10.0
Hi David,
Regarding mutiple intralinks/Windchill or multiple CAD implementation. It is not impossible. But, the can be issues is the filename uniqueness is OOTB and if you already implemented ProjectLink. There has been many discussions in PTCUser with different titles, such as
There is a very high probability that you will have the same filenames from the 2 systems that really different models. Most common practices is to rename/renumber them but that could be abusiness issue since it really based on IPs of 2 different companies. The common one is the default numbering convention of ProE 123.prt. But, there are instances that they may have numbering (filename + extension) conflicts.
We've been asking PTC constantly to just change/add the database unique index to for the filename:
Instead, the uniqueness is built into the WGM code. We've been asking PTC to remove the code and just depend on the database index. It is better for performance and instantly prevenative.
There are so many cases where we have to import/migrate customer data like AML/AVL with different orgid's principles. It wouldamazing to have a workspaces allowed to point to a different orgid principle to designate the ownership of the files. Once checked in, all the member links will take over for the collectors of the files and not just the file names with the baselines as well. Thus, communication with customer/vendor data with their nomenclature/numbering/filenaming is seamless. Even exporting it back and viewing it in ProjectLink doesn't create any confusion.
It is still a outstanding issue that is being looked at by PTC, but it requires work just to remove the code. Yes there is a chance to add to a workspace of different CAD tool or ORGID, but only then should the WGM complain of a uniqueness issue for that one ProE session. That use case is different than a migration and multi-CAD. It's for a single ProE workspace session that behaves like if all files are just placed in 1 hard drive folder.
Good luck,
Patrick
In Reply to David Haigh:
When we migrated from Intralink to Windchill, many years ago now, folders and such were mapped into Products and sub-folders to match the organization we had in Intralink.
Now that we are looking at migrating from two different Windchill servers into a single Windchill server, we are being told by the vendor that they can't do that.
I'm not clear on if this is a limitation in the migration software PTC supplies, or if this is just laziness on the part of the vendor.
We are being told they can make us a file that would be a "decoder" ring so we could put the stuff back into folders if we want.
Right, like I want a large number of designers having to move files into folders to get back to what we originally had.
1. Can someone tell me if this is possible or not. I don't really care how hard it is for the vendor. Is it possible.
2. Next, if it is possible, how hard is it?
3. And how would it be done?
David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550