<!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>NX to STEP entity mapping</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_topic4" id="xps10_pagetitle">NX to STEP entity mapping</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('dataexchange/step_settings.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('dataexchange/stepex_adv.html');return(false);">How To</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Options</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/how_do.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><div class="title_division">Step AP203: Entity conversion (NX to STEP)</div>
      <p class="para_division">This topic contains the entity mappings from NX into STEP AP203.</p>
      <p class="para_division">The STEP AP203 standard defines six subsets (conformance classes) of data that can be exchanged using AP203.</p>
      <p class="para_division">These conformance classes are:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item"><b class="uiTerm">Configuration Management</b> (CM) data only
            </p>
         </li>
         <li>
            <p class="para_item">CM plus non topology wireframe and surfaces</p>
         </li>
         <li>
            <p class="para_item">CM plus wireframe with topology</p>
         </li>
         <li>
            <p class="para_item">CM plus manifold surfaces with topology</p>
         </li>
         <li>
            <p class="para_item">CM plus faceted boundary representation solids</p>
         </li>
         <li>
            <p class="para_item">CM plus advanced boundary representation solids</p>
         </li>
      </ol>
      <p class="para_division">While CM data is included in all six classes, for readability purposes, it is included in the following table (1) only. Most of the configuration management data defined in AP203 is intended to be stored in a <b class="uiTerm">Product Data Management</b> (PDM) system, such as the NX product data management system, Teamcenter Integration. However, STEP AP203 product id, product version and product description information stored in NX under specific part and object attribute names can currently be written into a STEP file by the STEP AP203 translator.
      </p>
   </body>
</html>