Can you do this in SmarTeam? Marc Young xLM Solutions www.xlmsolutions.com

Typical SmarTeam Requests Security per object, per field Database Clean up Multi-Site Data Migration / Extraction Dynamic Workflow Assignments / Flowcharts Reporting Integration to other system Batch Processing (Printing) 3D Geometric Searching Part Number Generators Logging / Audits Data Migrations 3D Experience Migrations ….

Security Out of the box Security – Class, Group, Operation Project Level Security – Role Based Object Level security – Customization On Retrieve Hook Field Level Security Other types of security?

Database Cleanup Over time additional un needed data can accumulate in SmarTeam Do you really need Checked In Objects? Delete Checked In Data Batch tool to find and delete Script to Delete on Release Delete Orphan file in Vault, Objects with out files Delete Orphan objects not linked to any other object Delete data in tables – Notes, Conflict Log Every time a lifecycle operation happens a record gets written to this table Data clean up will save Disks pace Increase performance

Multi-Site Add / Remove Sites (Remove Replication) Database Upgrades Need to handle unique keys Vault Need to deal with Mirror Vaults Database Upgrades Single Site upgrade –re do replication Upgrade in and Propagate Oracle Upgrades Re do replication / Upgrade Oracle in place SmarTeam V5-6R2015 changes Oracle Monitoring Errors Connections Links Moving from Oracle to SQL or Oracle to SQL

Workflow Assignments / Notification No way to Dynamically assign users to Nodes This could be based on: Project File Type Class Part Number ….. Controlling Flow Chart Nodes Send a custom email upon approval / Workflow completion

Reporting Running a Query – Populate into Excel API level reports SQL level reports Working with a reporting engine Common Reports - Workflow Reports

Integration ERP, Another PLM System, …. Smarteam Gateway API Direct connect CAD Integrations Outlook SharePoint Web Services XML / Neutral data format (export / Import)

Batch Processing SmarTeam Regulatory Compliance Module DRL Tools Custom Batch Processing Tool Common Tools Convert to PDF / Neutral format Print all drawings in an assembly Sending alerts based on workflows / dates in SmarTeam Sending data to vendors 3DVIA Sync

3D Geometric Searching VPM, LCA, Enovia V6 – Specialized in this functionality Does not exist in SmarTeam out of the box 3D Position Matrix can be exported from most CAD systems and stored in SmarTeam From the 3D CAD matrix 3D search can be done.

Pat Number Generation Ability to build more intelligent part numbers Common Scenario, user picks prefix next available counter in concatenated with prefix

Auditing / Logging in SmarTeam Regulatory Compliance – provides auditing capabilities Can also be done via API Who has edited an object Who has copied out a file, view a file, view a profile card Who has deleted an object Can work with other products like Community Workspace

Data Extraction Database - SQL Queries APIs Files Fast More control of how data is formatted Files Dealing with multiple revisions data conversion

Data Migrations (1/2) What to migrate Cad Documents Workflows Catia V5 to V5 or to V6 Documents Workflows Projects / Folders Items Lookup tables Data Manipulation Not always one to one mapping Change fields Types Structure

Data Migrations (2/2) Enovia V6 Other systems Out of the box Tools MQL Enovia APIs Adaplets Other systems Extract data to neutral format Use ‘other’ system tools for import

Migration Methods, Technologies & Tools 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 10000 files or so) Uses V6 API – slower migration ENOVIA V6 Adaplet - Partially Automated – several 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.

Migration Content Considerations (Data, Mappings, Names, Folders, Toolbox, etc.) - Data Model 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. File renames in some systems are stored in the database and not in physical file in the vault. Before migrating it to V6 there needs to be a clean up process that updates the renamed files in all where used references in the vault. Consider implementing OOTB data model in SLW (i.e. policies, life cycle states, etc.) – safer.

Migration Process, Methodology & Best Practices for 3D Experience Install and test out of the box V6 CAD 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: http://www.xlmsolutions.com/wp-content/uploads/2012/09/Migrating-to-ENOVIA-V6-White-Paper.pdf 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

SmarTeam to Enovia V6 Migration Objectives The ability to conduct large data migration over a reasonable time frame The ability to pre and post process data as necessary The ability to handle different data model methodologies between systems Data validation Data Migration Process methodology

What have you done with SmarTeam? What do you want to do? Lets Discuss…

Script Presentation is available at: http://www.xlmsolutions.com Questions? Thank You! Script Presentation is available at: http://www.xlmsolutions.com Marc Young xLM Solutions, LLC. 248-926-5932 myoung@xlmsolutions.com