<!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>Understanding JT files</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">Understanding JT files</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('ugtojt/intro.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('ugtojt/intro_rt.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">The JT format is a highly-flexible, CAD-neutral format that can be created from most major MCAD applications, allowing full representation of relevant model information. This format proves very useful for exchanging design data for collaborative product development. </p>
      <p class="para_topic">JT data can be very lightweight, holding little more than facet data or it can be richer and hold associations to the original CAD information, assemblies, product structure, geometry, attributes, metadata and Product Manufacturing Information (PMI). It supports multiple tessellations and level of detail (LOD) generation. </p>
      <p class="para_topic">JT files store geometry in different LODs and hence can handle large assemblies. Each component in a product is stored in a separate file, and in each file there are three or four representations of the component. </p>
      <p class="para_topic">JT data can be contained in a single or multiple files. Each file can contain any relevant JT information. By properly managing the allocation of information to a given physical file, if source data changes, only the JT file corresponding to that information would need to be recreated or updated. </p>
   </body>
</html>