Published by phil on 23 Apr 2009
Pro/INTRALINK data migration to Windchill PDMLink v9.1
We did our Ilink to PDMLink9.1 migration a few weeks back. The wave of hyperactivity associated with the change has passed.
Not much to say on the down side. Just the usual users complaining about change. I also miss the briefcase for multiple change tasks (state changes, and other metadata table changes). Default search configurations seem to change on their own. The upside, however, looks pretty good. Proe/Pdmlink integration/interaction is pretty tight. An update to WS triggers pro to update your session. Check-ins are smooth from inside Pro. Product View is finally useful (viewing, create redlines, etc). Leading wildcard searches are as fast as any other. Deleting an object from CS tells you who and in what WS a user may have the part, and allows you to delete it from their workspace as well. I cannot find any missing key features. Bait and switch still works, but you have to download your old part before opening a session with the new part, otherwise the session will be updated.
Most default behaviors can be set from the Workgroup manager (checkout configurations, collectors (set all but “download” to none)). Key config.pro settings that default the wrong way include:
dm_emulate_ilink_sys_parameters – “yes” (without this all your legacy drawings will open without a revision)
dm_checkout_on_the_fly – “continue” (keeps you from doing a “check out” of all your hardware)
dm_overwrite_contents_on_update – “yes” (if you just want to update metadata, do a CS sync)
dm_upload_objects – “yes” (on save move local cache to server workspace)
Most of our problems are process. PDMLink process flow tools are robust, providing lots of ways to screw up. The more complicated the process, the more ways users can break it.
>>>>>>>>>>Update 5/28/2009
Here are a few more config.pro settings currently in use:
dm_cache_limit 7000
dm_http_compression_level 3
dm_network_threads 5
dm_remember_server yes
let_proe_rename_pdm_objects no


