<!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>Transferring I-deas models to NX</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_topic2" id="xps10_pagetitle">Transferring I-deas models to NX </div>
      <hr noshade="true">
      <p align="center"><img align="bottom" src="graphics/ideas2ug.gif"></p>
      <p class="para_topic">Part geometry can be associatively transferred from I-deas using interoperability. The geometry of the part and its history will be transferred into NX. </p>
      <p class="para_topic">Assemblies can also be transferred using interoperability. The exported exchange package file will contain all the subassemblies and parts required for the assembly. The assembly will be transferred using the orientations from the active assembly configuration.</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">
                  <p class="para_tip_body">Tips </p>
               </div>
            </td>
         </tr>
      </table>
      <ul>
         <li>
            <p class="para_item">Set the desired configuration as active before performing the export. Only this orientation will be output to the exchange file. </p>
         </li>
         <li>
            <p class="para_item">Before exporting any part, you should perform simple diagnostic checks. Use Part Diagnostics to make sure the part has no geometry errors. Use Info to check how many volumes the part contains. Also, examine the history tree to make sure there are no yellow or red nodes indicating warnings or errors.</p>
         </li>
      </ul>
      <p class="para_topic">After performing these basic checks, check the part into a library. Interoperability exports parts from the library, not from the model file. If the NX user can access I-deas Team Data Manager libraries directly, you don't need to do anything else. Otherwise, create an exchange package file to be opened in NX.</p>
      <p class="para_topic">To create an exchange package file:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">Check the part into a library. (Do not use the  <em>Keep to Modify</em> option).
            </p>
         </li>
         <li>
            <p class="para_item">Choose  <em>File &rarr; Interoperate...</em></p>
         </li>
         <li>
            <p class="para_item">Select the part to export.</p>
         </li>
         <li>
            <p class="para_item">Select the file type:  <em>Unigraphics xpk</em>.
            </p>
         </li>
         <li>
            <p class="para_item">Enter the destination file name.</p>
         </li>
         <li>
            <p class="para_item">Click on  <em>Export</em>.
            </p>
         </li>
      </ol>
      <p class="para_topic">The resulting file will package together the part with additional information about the origin of the file used for tracking. When this exchange file is imported into NX, the part it contains will be given an NX part filename based on the original I-deas part name. Any characters in the I-deas part name not allowed in NX part filenames will be converted to underscores, &quot;_&quot;.</p>
      <p class="para_topic">The exchange package file can be sent to the NX user as an e-mail attachment or by a direct file transfer. </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">
                  <p class="para_tip_body">It is recommended that the name of the exchange file identify the name and possibly the version of the part it contains. For example, exchange files for two versions of an I-deas part called Engine Block might be &quot;Engine_Block_v1.xpk&quot; and &quot;Engine_Block_v2.xpk.&quot; </p>
               </div>
            </td>
         </tr>
      </table>
      <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"> If a pruned assembly is selected for export, empty parts with no geometry will be exported for each pruned part in the assembly. These parts can later be updated associatively using interoperability. Assembly feature geometry is not exported. The geometry for the part will be exported ignoring the additional assembly feature change. If a harness assembly is exported, only the instance of the harness subassembly is exported. Harness-specific geometry is not exported.</p>
               </div>
            </td>
         </tr>
      </table>
      <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"> You must check the model into the library to transfer it with Interoperability. If you also keep the model in you model file, don't modify it in the model file before exporting an exchange package file.</p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_topic">When the I-deas part is modified, check it into the library and repeat the procedure to create another version of the exchange file. Notify the NX user that a new file is available.</p>
   </body>
</html>