PDMLink Migration

[peppinu]

Does anyone have any experience with migrating an INTRALINK database to PDMLink? What are the problems? Do group, accesses and the sort needs to be re-done per folder again in PDMLink?

Joe Borg

 

[looslib]

Yes, it is a entirely new method.

What version of Intralink are you migrating from?
How many files in Intralink?

When we migrated 50K files from Intralink 3.3 to PDMLink7, we used a migration tool.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
Sr IS Technologist
L-3 Communications

 

[peppinu]

Ben
We have about 300K files but with purging we reduced that to about 200K. Our Ilink is 3.3 and we intend to go to PDMLink 8.
Our concern is the access rights and the authorizations we have in Ilink. Do these get transfered? We have about 580 top level folders each containing 5 sub-folders in which we have different users accessing them. It would be a nightmare to have to redo all these.

Joe Borg

 

[looslib]

Acces control rules are setup diferently in PDMLink, so yes you do have to rethink the whole process.
Also, the Product structure of PDMLink is different than the folder structure of Intralink.

Have you taken the Business Administration class for PDMLink? The business rules for setting up Products and access control are covered in that training.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
Sr IS Technologist
L-3 Communications

 

[pdmlink]

Has anyone who has or is in the process of implementing PDMlink been able to increase Pro/Engineers functionality vs as compared to using Pro/e with Intralink.
I have been tasked with creating a wishlist of increased automation between Pro/e and PDMlink. Below are a couple of examples I came up with and I was wondering if some of you had more. Any websites would help as well. Thanks!

3.1.1 Part numbers assigned to all fabricated and commercial off the shelf (COTS) are requested from the Drawing and Database Number Request Tool(DAD)imbedded in PDMlink. The part numbers would be linked to PDMlink and assigned to the pertinent PDMlink attribute values and the Pro/engineer part and assembly parameter values.

3.1.2 All DAD tool inputs relating to pertinent program attributes (contract number, etc) are automatically assigned to the “CAD document” within PDMlink.

3.1.3 The DAD tool attribute values assigned to PDMlink are dependent on which type of part was assigned a number i.e. fabricated or COTS.

3.1.4 Access all military and commercial specs from within the PDMlink browser.

3.1.5 Specifications and related information associated with the COTS part documentation is retrieved from all pertinent vaults including the “Military and Industry Standards Part and Vendor Database”. The associated documents are displayed in a GUI and the option to retrieve or dismiss each related document is available at the time of part creation.

3.1.6 PDMlink has the ability to cross-reference the supply chain for manufacturers and suppliers based on the type of fabricated or COTS part being specified. A GUI would appear with multiple options for pre-selection of pre-filtered vendors of choice from its approved vendor’s lists. This would relate to some of the function that parts engineering had in the past.

3.1.7 Any attributes with multiple value options are displayed in a pull down menu for easy pick and place.

3.1.8 PDMlink knows it is a fabricated part being created and prompts the user for materials/density and finishes via a comprehensive list of each in a pull down menu. This would be an optional approach to material and finish assignments and Pro/e material and finish assignments would remain the second option.

3.1.9 PDMlink is the only tool for adding Pro/e attribute/parameter values to parts. Standardizing this process would eliminate the ambiguity between Pro/engineer parameter input and PDMlink attribute input. Possibly eliminates the need to designate and undesignate.