<!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>What it isn't</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">What it isn't </div>
      <hr noshade="true">
      <ul>
         <li>
            <p class="para_item">Data Translator.</p>
            <p class="para_item">Interoperability is not just a data translator such as IGES, used to transfer data to a foreign CAD system. The receiving system can open the IGES file to use the geometry, but no associativity to the original part model is maintained. Interoperability adds intelligence to the imported geometry by tracking the association between surfaces in the final part to the master part.</p>
         </li>
         <li>
            <p class="para_item">Migration Path.</p>
            <p class="para_item">Interoperability is not a migration path to move the master part from one system to another. Use interoperability to design the master part in one system, and use the geometry associatively in another system.</p>
         </li>
         <li>
            <p class="para_item">Data Management.</p>
            <p class="para_item">Interoperability does not replace or duplicate the functionality of I-deas TDM,I-deas Enterprise, NX Manager, Teamcenter Engineering, or Teamcenter Enterprise. You cannot interchangeably check in and check out the same part to add and modify features in two different systems.</p>
         </li>
         <li>
            <p class="para_item">Round Trip.</p>
            <p class="para_item">Interoperability is not designed as a tool for &quot;round trip&quot; data transfers. It is possible to maintain a master part in one system, add features in a second system, and then open a second interoperability file back in the first system, but the part that made the round trip is really a third part.</p>
            <p align="center"><img align="bottom" src="graphics/roundtrip.gif"></p>
         </li>
      </ul>
   </body>
</html>