Frank Menendez Alcon Research. Ltd Best Practices for Creating and Managing CAD-Centric Product Structure in PDMLink 9.1 Frank Menendez Alcon Research. Ltd

Brief History of PTC’s MCAD Tools at Alcon 1994: Implemented Pro/E. One of several MCAD tools. PDM system is Team Center CMS 1998: All new projects developed using Pro/E (for MCAD) 2000: Implemented Intralink 3.1 for ALL product data Pro/Engineer, legacy CAD, MS Word, artwork, etc. 2000: First use of Top-Down Design for surgical console product development 2001: Installed Division ProductView (PV) server, integrated with Intralink 3 server Pro/E drawings are published PV Clients are used to print/view/collaborate on Pro/E drawings 2004: Buyer planners use drawing overlay - Changes clearly identified in color with little effort – checkers use it as well

Brief History of PTC’s MCAD Tools at Alcon 2002: Published Pro/E Drawings become “Official” copies used for business State dependent PV Watermarks replace “red” stamp No need to stored hard copies with “red” stamp in cabinets 2004: Published Pro/E 3D Models used for collaboration 2004: Paperless Product Development (R&D) PV used for design check, design reviews. Annotations used in place of “red-lines” Drawing Overlay used for drawing check and communicating changes to suppliers PV used for collaboration with other departments (mfg, marketing, etc.) 2005: Tech writers leverage PV images instead of requesting images from Pro/E users 2004: Buyer planners use drawing overlay - Changes clearly identified in color with little effort – checkers use it as well Usage extended … Tech writers taught to obtain images from ProductView as needed No more requesting from Pro/Engineer users Increased use of annotations during design reviews; virtually no paper now Doc control down to 4 people, 1/3 of the original file cabinets Watermarked prints for all quotes; all tied to specific iterations w/no additional effort Windchill implemented Migrated from Intralink 3.4 Invested in Doc Collaboration Option Can now publish Word documents just like Pro/Engineer Drawings Scanned all remaining paper drawings and documents (80,000) and added to Windchill

Brief History of PTC’s MCAD Tools at Alcon 2005: First use of PV Composer for collaborating on Process Assemblies 2007: Migrated from Intralink 3.4 to Windchill 8.0 Used for storing Pro/E, MS Office, etc. Use Doc Collaboration Option for publishing MS Office docs Scanned all remaining paper drawings and stored in Windchill 2008: Paperless Manufacturing (eliminate errors, reduce $, improve CE) Electronic Viewing of Assembly Instructions using Process Assemblies and ProductView (w/ Composer) R&D/Mfg/Quality/Tech Services define 3D Assembly Instructions (PV Composer) earlier in development Assembly drawings created only AFTER all input provided 95% reduction in assembly drawing-level changes 2004: Buyer planners use drawing overlay - Changes clearly identified in color with little effort – checkers use it as well Usage extended … Tech writers taught to obtain images from ProductView as needed No more requesting from Pro/Engineer users Increased use of annotations during design reviews; virtually no paper now Doc control down to 4 people, 1/3 of the original file cabinets Watermarked prints for all quotes; all tied to specific iterations w/no additional effort Windchill implemented Migrated from Intralink 3.4 Invested in Doc Collaboration Option Can now publish Word documents just like Pro/Engineer Drawings Scanned all remaining paper drawings and documents (80,000) and added to Windchill

Brief History of PTC’s MCAD Tools at Alcon 2008: PV and Pro/PROCESS used for training production personnel Self-paced training, cross-functional training 2009: Upgraded to Windchill 9.0 Implemented Product Structure (PS) for some existing products and some new product development First libraries and then products Key attributes and lifecycle info stored in Windchill using PS 2010: Upgraded to Windchill 9.1 Implemented Product Structure for all new product development Product data in Windchill found more easily Product Teams “run” with PS ProductView client installed on ~ 900 computers, 18 facilities No more a concept of “document control” (no longer needed) Continued refinement of usage, processes with upgrade to Windchill 9.0, then 9.1

Product Structure at Alcon…..Today Leverage one WTPart view only Design View only (no Manufacturing or other views) As-Designed BOM’s (“official” BOM still resides in ERP) Authored by R&D w/ input from Operations Future: Operations to leverage Manufacturing view Equivalency links Other MPMLink Tools Pro/E Authored CAD documents Limited to Workgroup Manager for Wildfire Leverage all link types…by use case No more a concept of “document control” (no longer needed) Continued refinement of usage, processes with upgrade to Windchill 9.0, then 9.1

Product Structure at Alcon…..Today Mostly OOTB solutions – only two minor “customizations” Single-Level BOM Report (add allowable subs, Multi-Level BOM report (for upgraded 9.0 to 9.1 system) Disabled Manufacturing view Due to not leveraging manufacturing views…yet In enumerated list for views (do not remove) OIR for wt.part.WTPart Changed auto numbering to manual numbering Add view.id attribute value with the value = Design ProductView client installed on ~ 900 computers, 18 facilities No more a concept of “document control” (no longer needed) Continued refinement of usage, processes with upgrade to Windchill 9.0, then 9.1

What we will cover….. Focus is on Accurate CAD-driven product structure Three new link types Closing the gap between CAD and accurate product structure Key info on new functionality (and some old) PDM Actions: Revise, Promote, etc. Some Key Preferences Import from Spreadsheet Exporting BOM’s to Excel

What we will not repeat from 2008….. Already covered in 2008 PTC/User Presentation Administrator Best Practices Tips on training including training documentation CAD Document templates Part Centric vs. CAD centric Owner and Content links explored in detail Configuring Windchill for CAD-Centric PS (exhaustive) Administering WTPart Number and Name rules Administering WTPart Revision Attribute mapping (on parts and usage links) from CAD Configuring Auto Associate Configuring BOM Notes Configuring certain Table Views for users

What we will not repeat from 2008….. Already covered in 2008 PTC/User Presentation User Best Practices Tips in Windchill 8.0 and 9.0 to create accurate CAD-driven PS Creating/breaking associations between CAD and WTParts Tips on Promoting and Revising Revise and the As Stored Configuration Leveraging Auto Associate, Associate, Disassociate Bulk Loading tips (not import from spreadsheet) Leveraging BOM Notes and WTPart Usage Link Attributes Building PS for PCBA’s: Pro/E and ECAD WGM Data Productivity / Performance Best Practices

Differences between CAD and PS Some Reasons More than one CAD Model used to describe a single P/N E.g.: Flexible components (cables) when “Component Flexibility” is not applicable More than one CAD package being used (HDIC) Quantities don’t match Actual QTY value and/or UOM for QTY ERP BOM’s contain components not represented by CAD. For example, cable spools

CAD-Driven Product Structure Ideal Situation – not always possible

Multiple CAD Models Describe Same P/N Example – Flexible Components Several routed configurations of the same cable part number within the same assembly

Multiple CAD Models Describe Same P/N Example – Simplified Versions Used in Upper Level Structure is built upon check-in of Xyz.asm Envelope Part assembled in place of CAD subassembly

Example: Flexible Components Cable shown exists in 6 different assemblies in 3 products, all routing is different and must be shown correctly on all assemblies

Three “Roles” of link between CAD & WTPart Structure – CAD Doc member link used for Part Structure Update parent structures for upper level assemblies (look up) Limited to Image links (2x) and Owner WTPart can have Image links to Multiple CAD docs “Drive” structure within the assembly itself (look down) Limited to Owner (only one CAD Doc) Attributes – CAD Doc attributes mapped to WTPart Can have more than one CAD Doc drive attributes of one part – BE CARFEUL!!! Representations – CAD Doc viewable transferred to WTPart Can have more than one CAD Doc drive viewables of one part – BE CARFEUL – leverage setting the default representation!!!

Understanding “Structure” Role by Link Type Owner /Image Contribute to Parent Structure Above Look Up Both Contribute to Parent Structure Requires Owner Link here Structure is CAD-Driven

Understanding “Structure” Role by Link Type Only Owner Link “Drives” Structure Below Owner Link “Looks down” to Drive Structure Look Down Requires either Owner or Image Link here Image Link does not Drive Structure Look Down

New Link Types Summarized (Cont.) Link Type to CAD Drives Structure Below Contributes to Parent Structure Maps Attributes Maps Viewables Examples for Usage Owner Yes Primary Pro/E model used to drive structure Contributing Image No Flexible components, other CAD files, CAD Doc attributes mapped Image Flexible components, other CAD files, envelope parts Contributing Content Drawing, other CAD files, mapped attributes Content Drawing, other CAD files, use for collector

Number of Possible Links to CAD by Type Link Type to CAD Part iterates w/ CAD Doc Number of Possible Links Owner Y 1 Contributing Image Image N No limit Contributing Content Content Violations will cause check in failures

The New Link Types Summarized Content link gives you a reference to leverage for Collection capability, finding documentation, etc.

Setting the Link Type: Auto Associate To Create the WTPart(s) or Associate to Existing Perform in Workgroup Manager Workspace Select One or More CAD Docs

Setting the Link Type: Edit Associate To Associate to Existing Perform in Workgroup Manager Workspace Select One WTPart and Multiple CAD Docs Cannot select more than one WTPart

Technical Issues with New Link Types Product Structure Table View reports WTParts by link type Try to use CAD Doc with only one link type in the assemblies whenever possible Assembling CAD Docs with Contributing Image, Image and Owner links to the same WTPart in the same assembly results in structure as shown

Technical Issues with New Link Types Note: This functionality has many purposes. Some of which may have not been addressed here and may provide good reason to separate the occurrences by link type

Keep Find Numbers Consistent

Example: Flexible Components (cont.) Teach Users to leverage Contributing links only when mapping attributes and/or viewables is required

Example: Flexible Components (cont.) Note: The BOM will appear correctly in the Multi-Level BOM Reports

Mapping Attributes from Multiple CAD Models to a Single WTPart System is setup to prevent contention Leverage CAD Doc Templates to control the attributes mapped (contributed) to the WTPart Leverage associations accordingly (contributing links) Map attributes by link type using Preferences

Timing of WTPart Creation Easiest to coordinate at time of object creation Leverage earlier on for Product Development anyway Ensures part structures are built properly without having to “retrofit” More difficult after CAD models are Released CAD models usually iterated (see slide 21) A must when using State-Based versioning

Auto Associate and State-Based Versioning Revision Matches, but not State Good reason to create WTParts at initial creation of object

Single Level BOM and New Link Types Sorting by Find Number

Single Level BOM and New Link Types Sorting by Find Number Perform as Site Admin and make change to Default view for all users

Single Level BOM and New Link Types Sorting by Find Number

Saving BOM Reports to Excel Workaround for all Reports

Saving BOM Reports to Excel Workaround for all Reports Generate Report Select File, Save As from browser. Save to Single File Open the Archive file (*.mht)

Saving BOM Reports to Excel Workaround for all Reports

Saving BOM Reports to Excel Workaround for all Reports

Exporting Structures to Excel Now you can use Import from Spreadsheet to import into another or same Windchill system We leverage this often for PCBA BOM updates outside the ECAD WGM

Optimize Use of Edit BOM UI Problem Statement: Sorting by Find Number or Part Number not possible

Optimize Use of Edit BOM UI One Solution: Sorting by Line Number Requires Line Number to be equal to Find Number Note: It is possible to customize Windchill and Pro/E so that Windchill Find Numbers are mapped with Pro/E Item Numbers (Pro/REPORT)

“Gotchas” with Calculated Content Links Automatic Linking of WTParts to Drawings Issue for Multi-model drawings and Owner links to CAD Do you ever add more than one model to a drawing? Problem Statement: Each drawing the CAD model is associated to (in Pro/E) will automatically have Calculated Content link CAD model must have Owner link to WTPart Calculated Content link not automatically collected during Revise / Promote operations, even when Collector preferences are set to All

“Gotchas” with Calculated Content Links Problems that Can Occur Drawings can be associated to incorrect versions of WTParts While the new version is in WIP, the existing Released version of the WTPart will point to the incorrect latest version of the Drawing Revise to New View Version drops those drawing links Manually created Content links do not Accidental revising of wrong drawing Revising from the WTPart and then collecting will collect all associated drawings Must train users!!

“Gotchas” with Calculated Content Links Problems that Can Occur Revising from the WTPart requires collecting the drawing from the Owner linked CAD Model This will collect all associated drawings Problem for Multi-model drawings Must train users!! It is also possible to have more than one version of the same WTPart associated to a single drawing version

“Gotchas” with Calculated Content Links Best Practices #1 for us: Manually create Content Links between Drawings and WTParts Limited to Describing CAD Doc Calculated links used for multi-model drawings with different part number Revise all CAD objects with same number along with WTPart Possible cause for concern with new Checkout and Revise functionality in Windchill 9.1 and Pro/E I have not tested this yet

“Gotchas” with Calculated Content Links Preference Need to do more research on this From initial testing, Preference did not change behavior (regardless of container level) Note: There may be good reason for this behavior outside automating the links to all drawings

Revise Best Practices Know how links transition to the New Version Revise all describing CAD Docs with the WTPart at the SAME TIME Revising for Calculated links is different for all other CAD link types Calculated links will “float” All others will drop the link if not revised with the WTPart Alternate: Revise from Drawing and then collect from WTPart Since Promote is simply a change to existing version, these rules do not apply

Revise New Revisions of WTParts and Associated Docs Only Owner linked WTParts get revised when: Revising from PSE Revising from WS Revising from Pro/E (Revise and Check out – new for WF4) The following associated documents do NOT get revised with those operations WTDocs WTRefDocs Other CAD links that are not owner Problem: New Revision of WTPart no longer associated to documents (except Ref Docs)

BOM Notes Alternative Leverage the WTPart Usage Attribute Modify assembly only to edit (not component) Similar to BOM Notes Not a separate business object Different from BOM Notes

Import from Spreadsheet Changes from 9.0 Trace Code is mandatory for BOM’s WTPart usage link attributes can be loaded Use Attribute Name (from Att Mgr) Find Number, Number and Trace code must be TEXT format type KISS: Add apostrophe Gotta love the validation menu pick Only checks for correct Import sheet and header info only

Import from Spreadsheet Required Fields for Part Import Type Name Number Trace Code Required Fields for Structure Import Action (Add/Update/Delete) Level

Import from Spreadsheet Structure Import Ref Designators must be comma separated Ranges with dashed okay, but separate them with commas Number of Ref Designators must match Quantity Include F/N and Line Number Remember that sorting best practice? Can’t duplicate Number, Find Number, or Ref Des.

Import from Spreadsheet: Ref Designators More on Reference Designators Spaces are not permitted – must be commas Must do in order to show occurrences correctly and get QTY’s correct as well

Attributes Mapped from CAD Docs to WTParts Attributes mapped from Designated Parameters in Pro/E models Controlled by Preferences Limited to Owner and Contributing Links WTParts with multiple links Last CAD Doc checked in “wins” Latest iteration dependent upon last CAD model checked in Attributes on indiv. CAD docs that represent the same part number must be identical – their values

Designated Parameters in Pro/E Only Mapped attributes can be designated Check in failures will occur Stated error message: Attributes in CAD Doc are not part of type definition Must consider when working with legacy data Does not include ModelCheck attributes Gatekeeper still works as intended

Alternate Rename Process that Preserves History Outside of Rename History report Leveraged for tabulations Create new CAD Doc templates in Pro/E WS Create New CAD model with WTPart at correct revision Does not support state-based versioning – must use Set State Demo

Part to Document association logic

Limits on UOM for WTParts UOM for Quantity Must be EACH For CAD Documents with Owner, Image links Quantity value must be real number for EACH Workaround – leverage the second level of UOM control for QTY’s in Windchill At the part level – w/ owner links – you must use EACH At the assembly level, change the UOM for a component independent from the default UOM for component Assembly cannot have Owner to WTPart

Please feel free to contact me Frank.Menendez@alconlabs.com