pro/intralink 9.1 migration & customizations

Pro/INTRALINK 9.1 Migration & Customizations

Olaf Corten(Besi), PLM ManagerRik Schmale(USG Innotiv), Senior Consultant

Agenda

• Introduction Besi• Introduction USG Innotiv• Goals for Besi• Migrating issues• Customizing Workflows• Working with Asia• Results• Demo Workflow

Introduction Besi (1)

• Who is Fico ?– Fico is a product division of BE Semiconductor

Industries N.V.– Founded in 1956– In the nineties subsidiary of BE Semiconductor

Industries– Our Slogan “Good is not good enough”

Besi: From Die Sorting up to Plating

Introduction Besi (2)

Introduction Besi (3)• Where are we located ?

Introduction Besi (4)

• What products does Fico make ?• Molding machines• Trim and Form machines• Singulation machines

Introduction Besi (4)

• How do we use PTC Software at Fico?– Pro/ENGINEER Wildfire 4.0

• Top down design (Layout, skeletons, etc)• Module based configured machines

– Intralink 9.1• Datamanagement• Integration to our PLM (matrix)

Introduction USG Innotiv (1)

• USG Innotiv Product Development– Division of USG Innotiv (1500 people)– Part of USG People(20.000 people)

Development Capacity Consulting Training

Product Development

Introduction USG Innotiv (2)

• PD Consultancy & Training (services)– Market leader Benelux for services of PTC products

• Implementation• Migration• Process• Support

– Certified implementer / migrator of PTC database applications

– Certified Trainer Partner of PTC Products– Certified Service Partner in the Benelux– Pro/ENGINEER,Pro/INTRALINK, PDMLink

Goals for Fico

• One Data Management environment• Windchill platform• Supporting remote sites(Asia)• Sending data to Matrix(PLM)• Working with Intralink 9.1 should be the

same as with Intralink 3.4

One Data Management environment

• Migrating two Intralink 3.4 databases to 9.1– Molding and Trim & Form

• Challenges– More then 500 GB of Pro/ENGINEER data– More then 10.000 mapping and reordering of

subfolders– Different Revision schemes(1,2,..,A,B,..)– More then 6000 duplicates

Managing Duplicates

• What is a duplicate ?– Same Object exists in both databases– Mostly Library components (bolts,nuts,etc)

• How are duplicates handled ?– Mass rename (quick solution)– PTC’s Duplicate Object Manager

How did Fico handle duplicates?

PTC’s Duplicate Object Manager

• Tool to merge duplicates(Equal or Unequal)

• DOM equality criteria– Revisions and Criteria are the same– Dependencies are the same– Family Tables

• DOM unequality criteria– If equality criteria is not met (ex. Extra Instance of a

family table, more versions (A.2,B.1, etc)

PTC’s Duplicate Object Manager Example

Customizing Workflows

• What is a Promotion Request workflow ?• Why do we need more functionality ?• Export Released data to xml format for

Matrix Tool• What does the Matrix Tool do ?• Customized Promotion Request

– Adding extra steps– Written in Java (Windchill J2EE complaint)

Working with Asia

• Fico Tooling is moved here• Performance issues over a WAN• Replication solution

– Standard Windchill technology– Remote File server– Replicates Pro/E data to and back

• WAN optimizer (Riverbed)

Replication setup

• Based on rules– Types(ex. Documents, Pro/ENGINEER files)– Version (ex. Latest, all,etc)

• Scheduling replication• How is the data produced on a replica

send back ?

• 15 times faster with replication• Big improvements with browsing in

folders/workspaces

Performance results Replica

Results

• Succesful migration– Single Intralink 9.1 environment– All duplicated were merged– Very good adoption by Fico (custom training)

• Customizations implemented– Behaviour of Intralink 9.1 is very like the old Intralink

3.4– Sending the right info at the right time to Matrix

• Optimal performance for Asia

Live Demo Workflow

• How is custom workflow implemented ?

Thank you for your attention !

• Questions ?