Today all SMARTEAM customers worldwide are aware that, ENOVIA V6 is at the center of Dassault System’s product strategy for future. The ENOVIA collaborative platform delivers the flexibility, open standards, scalability and industry-specific functionality today’s global enterprise as well as SMB companies. SMARTEAM customers are evaluating various methodologies, approaches and tools for Migration to ENOVIA V6.
Below are key challenges being faced by SMARTEAM Customers when Migration to ENOVIA V6
SmarTV6 is sophisticated migration tool, developed by SteepGraph Systems to migrate SMARTEAM data to V6 for various migration paths
Support for Data Models: PLMDB or SMDemo
For many ENOVIA SMARTEAM customers, particularly those deployed more than 2 years ago, their base data model (the one from which their specific environment was derived) is SmDemo, whereas for other Customers, the basic data model is PLMDB. SmDemo database has specific classes for CATIA, Solidworks, UG and PROE data, whereas PLMDb has same classes for all CAD data.
SmarTV6 supports both the data models and migrates all CAD, Non CAD data that exists in these databases.
SmarTV6 supports migration of Projects, folders and the data in the folders. It maps this data in ENOVIA V6 so that post migration users see similar way of managing the data.
SmarTV6 migrates all CATIA Data that includes,
In ENOVIA V6, data is migrated to Designer Central based data model. The designer central data model supports multi-CAD environment including CATIA V5. When performing migration, the finalization relationships are maintained well based on state of the object. Also, Designer Central for CATIA integration requires that object name and file names are same. To take care of this, renaming features of Designer Central is used.
SmarTV6 migrates all Solidworks Data that includes
In ENOVIA V6, data is migrated to Designer Central based data model. The designer central data model supports multi-CAD environment including Solidworks. When performing migration, the finalization relationships are maintained well based on state of the object. When it comes to files, in SmarTeam, file names are appended with object Id and class id. These are updated as a part of migration.
Also the Designer Central data model requires that, when the Solidworks data is checked in, it should be managed as configurations. This data model is elaborate and complex. SmarTV6 takes care of this aspect very well and create all required objects, relationship to ensure that it complies with Configuration schema of Designer Central. This is very key aspect of the migration of Solidworks data.
SmarTV6 migrates all Documents, Items and BOM to ENOVIA V6. All revisions, versions, profile attributes of the data are migrated well. It creates BOM structure in ENOVIA V6. Post migration, ENOVIA V6’s comprehensive BOM management capabilities can be used for Parts and BOM Management.
When actual migration is run, it is important to get visibility of the migration progress. To provide the up to date progress, Migration Monitoring Console is provided.
SmarTV6 is based on very extensible and scalable framework for migration. The framework has below capabilities to have high throughput of the migration and minimize the migration window.
Workflows in Out-Of-The-Box ENOVIA V6 are different than those in SMARTEAM. The functionality does not one-to-one map between these two platforms. It is important that all SMARTEAM workflow functionality is mapped in ENOVIA V6.
To take care of this, SmarTV6 is bundled with Workflow tool for ENOVIA V6.
Workflow Tool Kit key features include
Supports Workflow Instantiation initiation from:
Workflow Types Supported
Workflow Template Definition Supports:
View the graphical status of Workflow