1. SolidWorks Migration to ENOVIA V6
Ilan Madjar
xLM Solutions LLC.

2. Overview
About Dassault Systemes ENOVIA V6 (“ENOVIA V6”) & 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. About ENOVIA V6 & SOLIDWORKS Integration
ENOVIA V6 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

4. Main ENOVIA V6 Centrals Centrals: Accelerators:
Engineering – Engineering Change and BOM
Designer – CAD / Document Management
Program – Project / Program Management
Supply & Sourcing– Access to Suppliers and Vendors
Quality - CAPA
Variant Configuration - xx ….
Accelerators:
Aerospace & Defense Program management and experience
Apparel …
Over 30 in Dassault Systems Web site. Can be implemented separately, in bundles or incrementally which enables a simpler phased implementation approach while taking advantage of a rich portfolio.
Can be implemented together or separately or incrementally.

5. About ENOVIA V6 & SOLIDWORKS Integration
True Multi tier application.
App server – JAR files, JSP, property files, xml, configuration files etc. App servers are configured individually. Web server can work with multiple app server for balancing, etc.
Web server – apache (free one), could be web logic, websphere, etc.
Distributed File servers (Stores). F has to go with A.
Single Database (Oracle,SQL Server, DB2. See DS official documentation for more details).

6. About ENOVIA V6 & SOLIDWORKS Integration
DEK (1/2)
MS Windows explorer as client – user friendly and short learning curve.
Developed by DS R&D (Designer central) and SOLIDWORKS R&D (the client side behavior and data model) – the best of both worlds.

7. About ENOVIA V6 & SOLIDWORKS Integration
DEK(2/2)
Built on top of the Designer Central Module
Has a server and client components in addition
ENOVIA V6 – 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 SolidWorks data to all other aspects of PLM)

8. About ENOVIA V6 & SOLIDWORKS Integration
Designer Central
ENOVIA V6 gateway into integrating with other applications
Mechanical CAD Software
CATIA V4 and V5, SOLIDWORKS, Pro/ENGINEER, Inventor, AutoCAD, 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 V6/SOLIDWORKS R&D teams.
Client Workspace Service
Applet
plugin
Common UI
CAD
Browser
Windows Explorer

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
Database based PLM\PDM systems such as ENOVIA SMARTEAM, SOLIDWORKS EPDM,DBWORKS,ADEPT, Microsoft SharePoint, 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”)
Similar considerations as in database based system with additional downtime for extracting the data

10. Typical Source Systems To Migrate Out Of
(2/2)
Source System/Characteristics and Skills
Traverse files to Extract Data
Reengineer Source Database \ Data Model
Full History
Windows file based
X(Con)
Pro
Con
Database based(SMARTEAM,EPDM…)
X(Pro)
File based PDM (WG)
X – Valid or in effect characteristic per source system
Windows file base – Full history is possible if revision is concatenated to either file names or folders, but is not practical in most cases.

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

12. Migration Methods, Technologies & Tools (SW Data)
(1/2)
Manual
Good for small data set – Lengthy process
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 (export\import), especially for large data sets (more than files or so)
Uses V6 API – slower migration
ENOVIA V6 Adaplet - Partially Automated – multiple automated 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
Spinner has additional license cost
Allows you to grow with data – by extracting existing schema and compare to upgraded environment’s schema.
Spinner – Easier to incorporate data model changes although it is a manual tedious process.
Spinner – escape characters where as in adaplet we anyways handle it on lower level.

13. Using V6 Adaplet
Adaplet example. Same import process apply to multiple possible source system.

14. Migration Methods, Technologies & Tools
(2/2) – Pros & Cons
Methodology \ Requirements\Pre-requisites
Lower Downtime per Larger # of files
Need to know source data model / APIs
Need to know ENOVIA V6 SW Integration data model or API
Additional Attributes /logic
Full History
Manual
Con
Pro
Automated (custom program)
X (Pro)
X (Con)
ENOVIA V6 Adaplet
XX Pro)
X – Valid or in effect characteristic per source system
All options can allow to grow with the data in V6 post migration if programmed right.

15. 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 V6 – combines name, revision and type.
Name can be a number generator OR file name
Object name in V6 cannot support certain characters and therefore a cleanup process will most likely be required in the meta data and physical files.
Consider implementing OOTB data model in SLW (i.e. policies, life cycle states, etc.) – safer.

16. Data Model Types ENOVIA V6 SOLIDWORKS Types and Relations: V6 Policy
SWComponentFamily,SWVersionComponentFamily,SWAssemblyFamily,SWVersionAssemblyFamily, SWDrawing
SWComponentInstance,SWVerionComponentInstance,SWAssemblyInstance,SWVersionAssemblyInstance, SWVersionDrawing
Assembly/Component Family/Instance and drawing types all have latest and active relations, version of, instance of, Finalized, version to version sub component, sub component, etc. (only partial list of relations and not actual names).
V6 Policy
Governs Business Types
Relations
Life cycle state
Store
Permission
Strongly recommend not to touch out of the box SLW types
Relations above - only a partial list of relations

17. 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>2012X)
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 2014X FP1448*
*check with Dassault Systemes through your VAR
Floating Objects Only - really defeats the purpose of using SLW and what makes it so usable.
Floating and Hybrid are aligned more with database based source systems like SMARTEAM, for example.

18. 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.
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.
Some source PDM systems like SMARTEAM can allow a loose , less restrictive behaviors in some cases, where as V6 SLW is more rigid – impact data cleanup.

19. 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 V6 SLW is more rigid
Toolbox
DEK currently does not have the same level of support for Toolbox as some other SolidWorks 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.
Some source PDM systems like SMARTEAM can allow a loose , less restrictive behaviors in some cases, where as V6 SLW is more rigid – impact data cleanup.

20. Migration Content Considerations
Provide a solution/service offering based on proven methodology which facilitates the migration of data from legacy SOLIDWORKS data to V6.
Handle the different data models between legacy system and ENOVIA V6 including inventing family, instance / version and relation objects for SOLIDWORKS data.
Allows the customer to grow with new ENOVIA V6 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 V6.
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).

21. Migration Process, Methodology & Best Practices
Install and test out of the box V6 SOLIDWORKS Integration with test licenses first
Due Diligence
Review legacy system
Identify data to migrate
Mappings & data reorganization
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
Migrating to ENOVIA V6 White paper:
Implement and stick to the OOTB data model for V6 & SW integration as much as possible
Ensure end customer signs off on data validation in addition to generating migration logs
Test environment should mimic production as much as possible

22. Conclusion
With proper planning and testing, moving SOLIDWORKS data from any legacy system to ENOVIA V6 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

23. Thank You! Questions To obtain a copy of the presentation or email me.
Ilan Madjar
xLM Solutions, LLC.