Enovia to Aras. Marc Young, Managing Partner xlm Solutions

Transcription

1 Enovia to Aras Marc Young, Managing Partner xlm Solutions

2 Enovia to Aras Agenda Introduction Review of Data Model Aras Enovia SmarTeam Enovia V6 / Matrix One Data Migration Strategies Co-Existence Strategies Conclusions / Q&A

3 About xlm Solutions xlm Solutions is a synergized company that is actively lead by its original founders, all of whom are "hands-on" in every aspect of the company operations. xlm possesses some of the best solution expertise in the PLM industry. xlm offers a full range of support and services including strategic value assessment and planning, solution architecture, project management and implementation, customization, data migration, training and support. xlm associates have broad and in-depth knowledge in many advanced and legacy programming languages, database and web technologies, as well as multi-site PLM and collaboration systems. Through dedication to details and sensitivity to client s requirements, xlm has established one of the most satisfied client bases in the business. xlm ensures its high quality and standards by working diligently at customer satisfaction as well as maintaining its expertise at the leading edge of IT and PLM technologies.

4 Aras Data Model Two types of objects Types and Relations Documents Items Users / Security States Workflows / Routes. Table Structure is easy to read Data model can mimic Enovia

5 Enovia Objects to Consider Enovia V6 / MatrixOne Types Documents Items ECOs/ECRs Other Centrals Project Management Supplier / Vendor Info. Fields Policies Lifecycle States Workspaces Lists Security SmarTeam Classes Documents Items Workflows. Field Types Project Folders States Lists Security

6 Data Loading Strategies 1. Pre-Migration Data Analysis Data Clean-up and Process Review Data Formats Data Loading Rules Migration Cost Estimation 2. Data Loading Options Manual Processing ARAS Batch Loader Custom Scripts (executables, add-ins, etc) Combined Manual Processing and Custom Scripting Pre-Developed Data Migration Programs 3. Execution Testing the Migration Process Data Verification Pre-Data Load Planning Production Data Load

7 Things to Consider (For the Migration) How will Aras be implemented? Will it be based on a similar data model as Enovia? Or do we want to rethink and reevaluate how best to deploy the new system? What data is in scope for the migration? Documents, BOM, WF History Data Mapping from Enovia to Aras Change in field types Any translation of data from Enovia to Aras? Maybe Numeric Revisions will be switched to Alpha Revisions Merging of fields CAD File name changes Cut Over Plan Are there any downtime restrictions for the migration? Will there be requirements to data access during the migration? User training and preparation?

8 Data Clean-Up Duplicated part numbers per file Duplicated file names Missing or incorrect file attributes Missing or incorrect file associations or links File revision not current Non-current parts in current assemblies Non-compliance or old revision/versioning scheme

9 Data Loading Options - Manual Processing Enovia Update/Verify Data

10 Data Loading Options - Manual Processing PROS Eliminates migration software development cost and time Data is manually verified during the process for Valid and correct intra- and inter-file relationships (e.g., drawing is linked to the latest revision of model) CONS Need to maintain two PDM systems for an extended period of time Confusion in data physical location Increased processing time for the user in organizing and moving file(s) Only the latest revision is migrated into ARAS

11 Data Loading Options - ARAS Batch Loader Easy tool to use to import objects or relationships Mapping of columns to attributes Configuration options delimiter, log file, Can be extended with Aras API

12 Data Loading Options - Aras Batch Loader PROS Can handle multiple types and relationships (Only one type at a time) Easy for user to populate delimited data Aras loaders will perform integrity checks Log files CONS Only load one table / type at a time May need to code to generate the delimited input to load

13 Data Loading Options Custom Code Best suited for larger data volume migrations Manipulates both meta data and data files simultaneously Data relationships and links may be created programmatically in the system Supports custom logging and error handling Highly suitable for implementing complex data load scenarios Supports all data loading rules Recommend use AML or Direct DB Updates

14 Data Loading Options Custom Code PROS Can handle multiple types and relationships Preset xml/aml format Aras loaders will perform integrity checks Log files CONS Must likely will involve code to generate xml/aml format

15 Data Loading Options - Pre-Developed Data Migration Tools Requires a basic, one-time configuration When properly configured, tool execution requires no operator intervention Most tools support full Migration of revision history Attribute mappings Events logging And more Existing tools Enovia Aras (

16 xlm s Enovia To Aras Migration Toolset Functionality Provide a configurable migration toolset to support Enovia to Aras Migrations Attribute Mappings State Mappings Enovia Class to Aras Type Mappings SmarTeam Project / Folder mapping to Aras The ability to pre and post process data as necessary The ability to handle different data model methodologies between systems The ability to conduct data validation, to verify the data load Conduct large migrations in less than 48 hours An application programming library is available for developing additional migration customizations such as attribute mapping, folder structure creation, filtering, etc

17 Co-Existence Scenario 1 CAD data is managed in Enovia Other PLM Processes are performed in Aras Project Management BOM Management Quality Management Enterprise Workflow Upon action in Enovia CAD Data or View file gets sent to Aras Actions in Aras Can automate release of CAD data in Enovia Actions in Aras Can automate change state (to in work) in Enovia

18 Co-Existence Scenario 2 Some Projects are done in Enovia and new Projects are performed in Aras Push standard common parts from Enovia to Aras Mark ownership attribute on object (only the owner system can change object) Provide ability to push changes of jointly owned objects from one system to the other Provide mechanism to change ownership of object Ability to generate part numbers from one system but use in both systems

19 Testing the Migration Process Test the migration process!!! Mitigate all discovered issues Identify Legacy data issues Missing data files Orphan links and/or blank fields Inconsistent legacy data such as revision schema Bad formats E.g., Attempts to load characters into integer fields Repairing the legacy data Manual clean-up Modify the Aras data model to better accommodate the legacy data Data loading procedural issues e.g., failure to delete all files with a creation date before Document the migration procedure or update the tool to automate the migration process Test again!!!

20 Conclusion With proper planning and testing, moving from Enovia to Aras can go smoothly 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 straightforward manner

21 Thank Questions? you! Marc Young xlm Solutions, LLC