<!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 process</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 process</div>
      <hr noshade="true"><a name="ndxgenid_roadmap598"></a><p class="para_topic">Content Migration Manager (CMM) migrates I-deas data within the <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/03topic_9.html');return(false);">Teamcenter</a> environment. The basic concepts used to migrate data are described here. For more specific information on specific options, see the help provided with the application.
      </p>
      <p align="center"><img align="bottom" src="graphics/nxmanager/tce_start.gif"></p>
      <p class="para_topic">To use CMM, first move your I-deas data into Teamcenter either by converting the I-deas TDM installation to Teamcenter or by importing I-deas data into Teamcenter using an I-deas library package file.</p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/tip.gif" alt="Tip" title="Tip"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_tip"><a name="ndxgenid_roadmap599"></a><p class="para_tip_body">To import an I-deas library package file into Teamcenter, use the menu <b class="uiTerm">Import</b> &rarr; <b class="uiTerm">From TDM</b>.
                  </p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_topic">Teamcenter can manage both I-deas and NX data in the same environment. <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/03topic_8.html');return(false);">Teamcenter Integration</a> is the interface to NX. When data is migrated from I-deas to NX, one <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/03topic_11.html');return(false);">item revision</a> will contain both the I-deas and the NX data. Older item revisions will contain just the I-deas data, and new item revisions will contain just the NX data.
      </p>
      <p class="para_topic">In the figure below, items are labeled (1) and the item revision is labeled (2). This particular item revision contains an I-deas part (3). You will select the item revision (2) to migrate. After the migration, this item revision will contain both the I-deas part and the migrated NX .prt file (4).</p>
      <p align="center"><img align="bottom" src="graphics/nxmanager/item2.gif"></p>
      <p class="para_topic">You should normally pick the highest level parent to migrate, such as a drawing of an assembly. The drawing, the assembly, and any components it contains will be migrated together depending on the options you set.</p>
      <p class="para_topic">Use the <b class="uiTerm">Content Migration Manager</b> application in Teamcenter to perform the migration. 
      </p>
      <p class="para_topic">After completing the migration, a report providing details of the migration status will be stored for the item revision. This report describes how each I-deas modeling feature was <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/10qt_migration_9.html');return(false);">mapped</a> into NX features.
      </p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">During the migration, a log file is generated which may be useful for troubleshooting.</p>
               </div>
            </td>
         </tr>
      </table><a name="qt_ideas_cmm_enterprise"></a><div class="title_division">CMM Enterprise</div><a name="ndxgenid_roadmap600"></a><p align="center"><img align="bottom" src="graphics/nxmanager/teamcenter_enterprise.gif"></p>
      <p class="para_division">Content Migration Manger (CMM) Enterprise will migrate I-deas data within the Teamcenter Enterprise environment. This migration environment will typically only be used by large companies using Teamcenter Enterprise.</p><a name="qt_ideas_cmm_native"></a><div class="title_division">CMM Native</div><a name="ndxgenid_roadmap601"></a><a name="ndxgenid_roadmap602"></a><p class="para_division">Content Migration Manager (CMM) Native migrates I-deas data directly from I-deas TDM into native .prt files to use in NX. This article describes basic migration concepts. For specific options to set and the process to follow, see the separate documentation distributed with the application.</p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/warning.gif" alt="Warning" title="Warning"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_warning">
                  <p class="para_warning_body">This migration method is not recommended for most sites, because the metadata from TDM will be discarded. Migrated data will be stored in unmanaged .prt files in a specified folder. Using this method:</p>
                  <ul>
                     <li>
                        <p class="para_warning_body">You will loose the ability to search for files by attributes. All migrated files will be placed in a folder, and can be opened only by file name. Since a unique .prt filename will be constructed from the library name, item name, and item part number, the files may become hard to manage if a large number of files are migrated.</p>
                     </li>
                     <li>
                        <p class="para_warning_body">There will be no data management system to prevent you from deleting or renaming files required by other drawings, assemblies, or ACF (Associative Copy) features.</p>
                     </li>
                     <li>
                        <p class="para_warning_body">You may be limited in your ability to use some of the <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/07qt_assemblies_26.html');return(false);">interpart relationships</a> described in this road map without a data management system to control the related files.
                        </p>
                     </li>
                  </ul>
                  <p class="para_warning_body">This method should only be used for pilot projects as part of your migration planning, or by small individual sites that elect to run NX in native mode without any data management system.</p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_division">Since this application migrates data from the I-deas TDM installation, only items checked into a library can be migrated.</p>
      <p class="para_division">To begin the migration, select the menu:</p>
      <ul class="unmarkedList">
         <li>
            <p class="para_item"><b class="uiTerm">Tools</b> &rarr; <b class="uiTerm">Content Migration Manager - Native</b></p>
         </li>
      </ul>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">This application will need to be installed at your site to enable the menu in NX.</p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_division">The <b class="uiTerm">Content Migration Manager Native</b> dialog box will be used to perform the migration.
      </p>
      <p align="center"><img align="bottom" src="graphics/nxmanager/cmm_native_dialog1.gif"></p>
      <p class="para_division">First, you will need to configure access to the I-deas TDM installation and set other options for the migration.</p>
      <ul class="unmarkedList">
         <li>
            <p class="para_item"><img align="bottom" src="graphics/icons/icon_specify_config_opt.gif" border="0"> <b class="uiTerm">Specify Configuration Options</b></p>
         </li>
      </ul>
      <p class="para_division">Next, you will select the parts, assemblies, and drawings to migrate from the I-deas TDM installation. </p>
      <ul class="unmarkedList">
         <li>
            <p align="center"><img align="bottom" src="graphics/nxmanager/tdm_browser.gif"></p>
            <ol type="1" start="1">
               <li class="condense">I-deas Installation</li>
               <li class="condense">Project</li>
               <li class="condense">Library</li>
               <li class="condense">Parts</li>
               <li class="condense">Assemblies</li>
               <li class="condense">Drawings</li>
            </ol>
         </li>
      </ul>
      <p class="para_division">During the migration, an information report will be displayed.</p>
      <ul class="unmarkedList">
         <li>
            <p class="para_item"><img align="bottom" src="graphics/icons/icon_start_migration.gif" border="0"> <b class="uiTerm">Start Migration</b></p>
         </li>
      </ul>
      <p align="center"><img align="bottom" src="graphics/nxmanager/migrate_log.gif"></p>
      <p class="para_division">After the migration is complete, a detailed report for each item will give complete details including how each I-deas modeling feature was <a class="links" href="javascript:void(0)" onclick="top.openFile('roadmap/10qt_migration_9.html');return(false);">mapped</a> into NX features. Display this report by right-clicking the item in the <b class="uiTerm">Content Migration Manger Native</b> dialog box.
      </p>
      <p class="para_division">See also:</p>
      <ul>
         <li>
            <p class="para_item">For more specific help on installing and running this application, see the help file distributed with the product.</p>
         </li>
      </ul>
   </body>
</html>