3 DS COMSOLIDWORKS Dassault Systmes Confidential Information 2116

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 1 SOLIDWORKS Migration to ENOVIA V 6 and the 3 D Experience Platform Marc Young and Ilan Madjar x. LM Solutions LLC. www. xlmsolutions. com

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 2 Overview • About Dassault Systemes ENOVIA V 6 (“ENOVIA V 6”) & SOLIDWORKS Integration (“DEK”, previously referred to as “SLW”) • Typical source systems to migrate out of • Implementation Data Models for DEK • Migration methods, technologies & tools • Migration content considerations (Data, mappings, names, folders, Toolbox etc. ) • Migration process, methodology and best practices

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 3 About ENOVIA V 6 & SOLIDWORKS Integration ENOVIA V 6 (1/2) • ENOVIA V 6 provides global collaborative innovation, online creation and collaboration, a single PLM platform for IP management, a life-like experience, ready-to -use PLM business processes • User Governance - Requirements Management, Portfolio Configuration, Program Management, Decision Support Business Intelligence, and Compliancy(Materials, IP, Life Sciences…) • Engineer/Designer - Tools for designers, product engineers, manufacturing professionals and other innovators collaborating on product development. • Supply Chain - The Global Sourcing domain allows companies to leverage supply chain capabilities throughout the product lifecycle and make their suppliers an integral part of product development. Within Global Sourcing are these sub-processes: Supply Chain Network, Collaborative Sourcing, and Supplier Performance Monitoring • Reviewer - ENOVIA solutions for all users to search and review data, to participate in approval processes and to collaborate with other users. • IT/Admin -solutions designed for those responsible for administering the ENOVIA server and refining its business rules and data to meet the business requirements

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 Main ENOVIA V 6 Centrals: Accelerators: • Engineering – Engineering Change and BOM • Designer – CAD / Document Management • Aerospace & Defense Program management and experience • Program – Project / Program Management • Apparel • Supply & Sourcing– Access to Suppliers and Vendors • … • Quality - CAPA • Over Variant - xx Web site. Can be implemented separately, in bundles 30 in. Configuration Dassault Systems incrementally which enables a simpler phased implementation approach while • or…. taking advantage of a rich portfolio. 4

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 5 About ENOVIA V 6 & SOLIDWORKS Integration http: //www. 3 ds. com/fileadmin/PRODUCTS/ENOVIA/PDF/WHITE-PAPERS/PCSWhitepaper-0807_final_July_29. pdf

6 3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 About ENOVIA V 6 & SOLIDWORKS Integration DEK (1/2)

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 7 About ENOVIA V 6 & SOLIDWORKS Integration DEK(2/2) • Built on top of the Designer Central Module • Has a server and client components in addition • ENOVIA V 6 – SOLIDWORKS provides the following functionality • • • Check In and out Promote through a lifecycle Access to workspaces / folders EBOM Sync Linking of data to all other objects / centrals with in ENOVIA (i. e. gateway of Solid. Works data to all other aspects of PLM)

• ENOVIA V 6 gateway into integrating with other applications • Mechanical CAD Software • CATIA V 4 and V 5, SOLIDWORKS, Pro/ENGINEER, Inventor, Auto. CAD, Microstation • Electrical CAD Software • Zuken, Mentor Graphics, Cadence, Xilinx, Veribest, Altera • Note: Some integrations are developed by third parties. DEK was developed by Dassault Systemes ENOVIA V 6/SOLIDWORKS R&D teams. Browser CAD Windows Explorer Com mon UI 3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 8 About ENOVIA V 6 & SOLIDWORKS Integration Designer Central Applet plugin Client Workspace Service

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 9 Typical Source Systems To Migrate Out Of (1/2) • Windows file based - folder structure on local machines and / or on the network • When Automated - May take longer downtime due to the need to traverse through physical files and properties. • More difficult to process full history when file names and folder structure is used to manage history • Databased PLMPDM systems such as ENOVIA SMARTEAM, SOLIDWORKS EPDM, DBWORKS, ADEPT, Microsoft Share. Point, etc. • Faster data extraction assuming the source database system as master • Requires understanding of the source systems data model • File based PDM systems – mainly SOLIDWORKS WORKGROUP(“WG”)

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 10 Typical Source Systems To Migrate Out Of (2/2) Source Reengineer Source System/Characteristics Traverse files to and Skills Extract Database Data Model Windows file based Databased(SMARTEAM, EPD M…) File based PDM (WG) Full History X(Con) Pro Con Pro X(Con) X(Pro) • X – Valid or in effect characteristic per source system

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 11 Implementation Data Model • Out of the box DEK only installation. • OCDx – One Click Deployment Experience – for an easy, administration and deployment to production • Custom Data Model • Cloud - not available yet for SW* * Check with Dassault Systemes for additional current details.

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 13 Migration Methods, Technologies & Tools (SW Data) (1/2) • Manual • Good for small data set • No support for full history migration • Automated • JPOs, MQL and Tcl scripts - Requires comprehensive understanding of both source and target systems data model and possible source system APIs • • Strongly recommended to break it down to two steps (exportimport), especially for large data sets (more than 10000 files or so) • Uses V 6 API – slower migration. ENOVIA V 6 Adaplet - Partially Automated – severalautomated steps to extract and later import the data into ENOVIA • Requires comprehensive understanding of both source and target systems data model and possible source system APIs and SQL knowledge • • Direct DB updates methodology – fast Spinner Partially Automated • Requires comprehensive understanding of both source and target systems data model and the Spinner tool itself • Data needs to be programmatically extracted into spinner • Additional fee • Uses V 6 API – slower migration

14 3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 Using V 6 Adaplet

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 15 Migration Methods, Technologies & Tools (2/2) – Pros & Cons Need to know ENOVIA V 6 SW Lower Methodology Downtime Need to know Integration Additional Requirements per Larger # source data model or pre-requisites of files model / APIs API Attributes /logic Manual Automated (custom program) ENOVIA V 6 Adaplet Full History Con Pro Con X (Pro) X (Con) X (Pro) XX Pro) X (Con) X (Pro) • X – Valid or in effect characteristic per source system All options can allow to grow with the data in V 6 post migration if programmed right.

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 16 Migration Content Considerations (Data, Mappings, Names, Folders, Toolbox, etc. ) Data Model • Mappings • • Types Relations Attributes Life cycle states • Workspaces and global folders • Avoid managing excessive amount of files per folder or a very complex (deep) folders’ structures. • Object Uniqueness in V 6 – combines name, revision and type. • • • Name can be a number generator OR file name Object name in V 6 cannot support certain characters and therefore a cleanup process will most likely be required in the meta data and physical files. File renames in some systems like EPDM is store in the database and not in physical file in the vault. Before migrating it to V 6 there needs to be a clean up process that updates the renamed files in all where used references in the vault.

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 17 Data Model Types • ENOVIA V 6 SOLIDWORKS Types and Relations: • SWComponent. Family, SWVersion. Component. Family, SWAssembly. Family, SWVersion. Asse mbly. Family, SWDrawing • SWComponent. Instance, SWVerion. Component. Instance, SWAssembly. Instance, SWVersion. A ssembly. Instance, SWVersion. Drawing • Assembly/Component Family/Instance and drawing types all have latest and active relations, version of, instance of, Finalized, version to version sub component, etc. (only partial list of relations and not actual names). • V 6 Policy • • • Governs Type Relations Life cycle state Store Permission

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 22 Migration Content Considerations Data Model • • Comprehensive Model – Everything is linked to global folders and available to users based on their roles and permission (available through all versions of SOLIDWORKS Integration>2012 X) • The most intuitive model for the SOLIDWORKS Integration • May impact performance if a large number of folders is needed • May need to “invent” missing folder links if those do not exist in the legacy system (for example SMARTEAM). Floating Objects Only - Files are managed in a local view folder which is not exposed to others through global folders. A concept of individual private working directory. • • Might have better search performance. Aligned more with some legacy systems behavior Does not inflate number of folders. Hybrid – Available in 2014 X FP 1448* • • • Might have better search performance. Aligned more with some legacy systems behavior Does not inflate number of folders. *Check with Dassault Systemes through your VAR

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 23 Migration Content Considerations SW Data (1/2) • Management of SWX File Properties within ENOVIA • Consideration of how current practices of managing SWX file props is required. ENOVIA has the capability of mapping SWX custom properties, as well as, mapping SWX configuration specific properties. The mechanisms of the two mappings are independent in that the custom properties mapping does not automatic apply to configuration specific file properties. • Single Default Config vs. Full Configurations • Upon file check-out and subsequent opening a file within SWX: Be prepared to offer the users an automated means of adding, rearranging, and generally managing the new and existing SWX file properties. • Update model and drawing templates in support of the file properties management practice. • A review of how the revision annotation within the drawing title block is warranted. ENOVIA supplies two attributes to the CAD Administrator in management of the drawing revision. One ENOVIA attribute manages the revision (A, B, C, etc) while another manages the version (A. 01, A. 02, A. 03, etc). A review of current Configuration Management practices and how to best adopt ENOVIA revision scheme is required.

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 24 Migration Content Considerations SW Data (2/2) • Use of SWX Configurations • Keep the number of configurations within any given file to a minimum. This offers much better performance within ENOVIA. • Use of Virtual Components: • ENOVIA OOTB will create a record within the database representing the vcomp. Via a configuration change vcomps will be ignored by ENOVIA when checking in the assembly model. • Some source PDM systems like SMARTEAM can allow a loose , less restrictive behaviors in some cases, where as V 6 SLW is more rigid • Toolbox • DEK currently does not have the same level of support for Toolbox as some other Solid. Works platforms. However through configuration of the integration data model it is possible to manage Toolbox parts. • Create sub type for the Component and Component Instance and respective policy.

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 25 Migration Content Considerations • Provide a solution/service offering based on proven methodology which facilitates the migration of data from legacy SOLIDWORKS data to V 6. • Handle the different data models between legacy system and ENOVIA V 6 including inventing family, instance / version and relation objects for SOLIDWORKS data. • Allows the customer to grow with new ENOVIA V 6 functionality • No migration data into a corner that cannot be expanded. • Migrated data will appear in the same manner as if it were created new in ENOVIA V 6. • We believe in the ~70%/30% generic tools/Services • Conduct large data migration over a reasonable time frame • Goal is to be able to load any size database in reasonable time frame (normally a weekend timeframe or • • • long weekend for large migration). Single Migration – Recommended – faster transformation, no extra cost of developing migration solution or maintaining two systems in parallel, but may take extra time for migration downtime. Migration in Delta – Rule of thumb, implement only if absolutely necessary(for example very large number of concurrent users). Consider Hardware improvements (SSD drives for database, more memory on database machine, multiple drives for better IO).

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 26 Migration Process, Methodology & Best Practices Process • Install and test out of the box V 6 SOLIDWORKS Integration with test licenses first • Due Diligence Migrating to ENOVIA V 6 White paper: • Review legacy system http: //www. xlmsolutions. com/wp • Identify data to migrate content/uploads/2012/09/Migrating-to-ENOVIA-V 6 -White • Mappings & data reorganization Paper. pdf • Concerns • Cut over plan & working process for duration of cut over plan. • Test Environment • Pick the best technology and develop migration solution • Run two to four test cycles a needed and based on the volume of data • Data validation – only you can validate your data • Plan for production roll out and set users expectation. • Run production migration

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 27 Conclusion • With proper planning and testing, moving SOLIDWORKS data from any legacy system to ENOVIA V 6 can go smoothly • Pick the best migration tools for your needs and according to your budget • Follow the documented procedures • Allocate buffer time for any issues • Prepare to support users in the new system • Devil is in the details. Make sure to fully understand requirements, data sets, limitations and technology being used and most importantly set the right expectations • Anything is possible; most data migration scenarios can be accomplished in a relatively straightforward manner

3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014 28 Thank You! Questions To obtain a copy of the presentation or email me. Marc Young x. LM Solutions, LLC. 248. 926. 5932 myoung@xlmsolutions. com Ilan Madjar x. LM Solutions, LLC. 516. 792. 6974 imadjar@xlmsolutions. com

29 3 DS. COM/SOLIDWORKS © Dassault Systèmes | Confidential Information | 2/1/16 | ref. : 3 DS_Document_2014