Procedure for Preparing the Migration

This migration preliminary step consists in generating csv files, one for each V1 (Former Typing) type.

This task shows you how to:

Prepare Migration for baseline behavior

When migrating baseline behavior objects, there is no need for the administrator to specify the mapping scheme between V1 (Former Typing) and V2 (unified typing), i.e. there is no need to modify the csv files. In this mode, all the objects are migrated including the attributes and their values added using the parameterization console.

Prepare Migration for Customer-Specific Environment (CSE)

Before launching the migration, describe the mapping between V1 and V2. To do so, you must declare how the tool will transform the types and attributes created using DMC. This mapping is declared in csv files. For more information, see About the CSV Files Migration.

Before you begin:

When migrating from DMC to Unified Typing, you must first perform a DMC migration before performing the unified typing migration. To perform the DMC migration, you must first activate the FormerTyping mode and follow the steps described below after upgrading the server:

  1. Enable the FormerTyping=1 variable to use DMC.
  2. Perform the DMC migration using DMC.
  3. Remove the variable FormerTyping=1 to activate the unified typing.
  4. Launch the Unified Typing Migration Tool (UTMT) as described in Running the Migration.

  • Steps:
    1. Analyze the current V1 customization and create the V2 customization using Specialize Data Model and Model Customization.

      Notes:
      • Each V1 type must be reviewed along with their attributes and you must decide how to transform existing V1 types and attributes into one or several V2 specialized types and/or extensions and attributes.

        For example, if you have a V1 customization type for VPMRepReference you may have defined several attributes to be used according to the discipline. A sub type of VPMRepReference could have some attributes that are used only for 3DShape, and others for Drawing only. It is the opportunity to create new specialized types, one for 3DShape, one for Drawing with the right set of attributes. Obsolete attributes can be dropped during the migration.

      • Make sure that the target types can be driven by the origin policy.

    2. Generate and fill in your csv files. The names of the files you create match the names of the types to be migrated. For more information, see About the CSV Files Migration.

    Prepare the Data

    This section provides information about electrical rules and fastening batches.

    Use the Data Checker to Run Electrical Rules

    Before launching the migration, you must launch some rules for electrical data.

    Note: For more information about the Data Checker, see Multi-Discipline Collaboration Platform: Data Administration Tools and Techniques: Using the Data Checker.

    1. Use the Data Checker to run the electrical rules.

      Note: The list of the checks that must be run by the Data Checker is located in a rule file specified using the -rulefile option. The available rule file is: DataChecker_Electrical3D_Design_Disciplines.xml

    2. Run the required MQL scripts. For more information, see Server Installation: Migrating between Former Typing and Unified Typing.

    Update Fasteners using Fastener Batches

    Before launching the migration, you must launch some batches for fastening data.

    Notes:
    • For more information about these batches, see 3D Modeling: Multi Discipline Engineering: Fastening: Administration: Preparing the Migration of Bead Fasteners to the Unified Typing Mode, 3D Modeling: Multi Discipline Engineering: Fastening: Administration: Preparing the Migration of Spot Fasteners to the Unified Typing Mode, and 3D Modeling: Multi Discipline Engineering: Fastening: Administration: Preparing the Migration of Fasteners Connections to the Unified Typing Mode.

    • For Weld Fasteners objects, an alias is defined in the corresponding CSV file. This alias has as VPMReference target type. This means that all “Weld Fastener” objects will be migrated to VPMReference. The alias for “Weld Fasteners” objects is NTMigAliasType_VPMReference_WeldBeadFastener.

    Run the following batches:
    • FstSpotV2TypeMigrationBatch (for Spots)
    • CATFstBeadMigrationBatchPLM (for Beads)
    • FstMCXMigrationBatch (for connections)

    Note: For Weld Fasteners objects, an alias is defined in the corresponding CSV file. The target type of this Alias is VPMReference. This means that all Weld Fastener objects will be migrated to VPMReference. The alias of Weld Fasteners objects is NTMigAliasType_VPMReference_WeldBeadFastener.