<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Content migration overview</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic3" id="xps10_pagetitle">Content migration overview</div>
      <hr noshade="true"><a name="ndxgenid_roadmap595"></a><a name="ndxgenid_roadmap596"></a><p class="para_topic">Content migration is a separate step from the <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/10qt_migration_4.html#qt_ideas_metadata_migration');return(false);">metadata migration</a>. There are three different environments in which to migrate data from I-deas to NX. These will be presented in the following articles: <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/10qt_migration_11.html');return(false);">CMM Engineering</a>, <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/10qt_migration_11.html#qt_ideas_cmm_enterprise');return(false);">CMM Enterprise</a>, and <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/10qt_migration_11.html#qt_ideas_cmm_native');return(false);">CMM Native</a>. 
      </p>
      <p class="para_topic">The options that control the content migration will be similar in each environment. For example, you can select whether to migrate feature history and/or boundary representations.</p>
      <p class="para_topic">By default, the content migration converts all of the feature history needed to edit the model. In some cases, you might not want to initially migrate the history of all models. You may, for example, choose to initially migrate only the boundary representation of released designs, and remigrate the feature history when required.</p>
      <p class="para_topic">You also select whether the boundary representation (B-Rep) of part models is migrated, and the layer on which to place this object. You will see this the NX history labeled as an &ldquo;unparameterized feature,&rdquo; equivalent to an orphan node in I-deas. This object will be suppressed by default. If there is a problem with any feature during the migration or later editing, this boundary representation can be unsuppressed. It can be used to display the model, or to help when debugging to rebuild the problem feature.</p>
      <p align="center"><img align="bottom" src="graphics/nxmanager/unparameterized1.gif"></p>
      <ol type="1" start="1">
         <li class="condense">Unparameterized Feature B-Rep of model (Suppressed) </li>
      </ol>
      <p class="para_topic">During the migration, the destination layers for entities such as reference geometry and wireframe geometry are controlled by optional settings.</p>
      <p class="para_topic">Another migration option is whether to perform an extra step to verify the fidelity of the new model surfaces compared with the original. This option is off by default, since it will increase the processing time.</p>
      <p class="para_topic">If there is problem with a particular feature during the migration, an unparameterized feature will be created for the specific feature, and joined to the model, as shown below. This may occur for a specific feature that is skipped because it is not yet supported by the migration tools or uses options that do not migrate properly. To modify this feature, it must be rebuilt, and the unparameterized feature can be suppressed or deleted.</p>
      <p align="center"><img align="bottom" src="graphics/nxmanager/unparameterized2.gif"></p>
      <ol type="1" start="1">
         <li class="condense">Unparameterized feature used for a skipped feature (Unsuppressed) </li>
      </ol>
   </body>
</html>