<!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>Entity conversion &ndash; NX to STEP</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">Entity conversion &ndash; NX to STEP</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><p class="para_topic">This topic contains the entity mappings from NX into STEP AP214.</p>
      <p class="para_topic">STEP AP214 currently defines eighteen conformance classes of data that can be exchanged using AP214. Product Management data (AP214 unit of functionality S1; counterpart of AP203 configuration management data) is included in all eight AP214 conformance classes. Most of the product management data defined in AP214 is intended to be stored in a Product Data Management (PDM) system, such as Teamcenter Integration. However, the STEP AP214 Translator can currently write product version and product description information which is stored in NX, under specific part attribute names and STEP AP214 product id, into a STEP file.</p>
      <div class="title_division">NX to AP214 S1 Product Management</div>
      <div class="title_division">SI &ndash; Product Management</div>
      <table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="99*">
            <col span="1" width="150*">
            <col span="1" width="50*">
         </colgroup>
         <tr bgcolor="#C0C0C0" valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_th">NX Part Attribute</p>
            </th>
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_th">STEP Entity.attribute</p>
            </th>
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_th">Notes</p>
            </th>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">PRDCNT_NAME</p>
               <p class="para_td">PRDCNT_DISCIPLINE</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">mechanical_context.name</p>
               <p class="para_td">mechanical_context.discipline_type</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">1</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">APPCNT_APPLICATION</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">application_context.application</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">1</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">PRDCT_ID</p>
               <p class="para_td">PRDCT_NAME</p>
               <p class="para_td">PRDCT_DESCRIPTION</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">product.id</p>
               <p class="para_td">product.name</p>
               <p class="para_td">product.description</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">&ndash;</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">PDFWSS_ID</p>
               <p class="para_td">PDFWSS_DESCRIPTION</p>
               <p class="para_td">PDFWSS_SOURC</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">product_definition_formation_with_specified_source.id</p>
               <p class="para_td">product_definition_formation_with_specified_source.description</p>
               <p class="para_td">product_definition_formation_with_specified_source.make_or_buy</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">&ndash;</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">PRDDFN_ID</p>
               <p class="para_td">PRDDFN_DESCRIPTION</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">product_definition.id</p>
               <p class="para_td">product_definition.description</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">&ndash;</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">PRDFCN_NAME</p>
               <p class="para_td">PRDFCN_LIFE</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">design_context.name</p>
               <p class="para_td">design_context.life_cycle_stage</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">1</p>
            </td>
         </tr>
         <tr bgcolor="#F0F0F0" valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">PRDFSH_NAME</p>
               <p class="para_td">PRDFSH_DESCRIPTION</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">product_definition_shape.name</p>
               <p class="para_td">product_definition_shape.description</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">&ndash;</p>
            </td>
         </tr>
      </table><br><p class="para_division">NOTES</p>
      <table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="36*">
            <col span="1" width="163*">
         </colgroup>
         <tr bgcolor="#F0F0F0" valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Note 1</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">For AP214, product_definition_context is limited to design_context. Both Mechanical_context and design_context will instance Application_context. Mechanical_context is the only available subtype of product_context.</p>
            </td>
         </tr>
      </table><br><div class="title_division">NX to AP214 S2 Element Structure</div>
      <p class="para_division">The processor will handle reference sets in both high level assemblies as well as subassemblies and components. Each NX part file within an assembly will be output as STEP PRODUCT entity. The individual reference sets within the part file will be output as additional STEP SHAPE_DEFINITION_REPRESENTATION (SHDFRP) entities pointing to the same PRODUCT for the NX part. Only references sets used in an active instance will be processed. For example, if a part file has a reference set containing all of the solids, one containing surfaces and one containing wireframe, and the solid refset is the only one instanced into the assembly, then the solid will be the only one processed. If the entire part is instanced into the assembly then all refsets will be processed. The relationship for these SHDFRP entities will follow the recommended procedure for defining the STEP OR conditions. In other words the assembly will view the reference sets as being alternate representations of the same data and will be coded within the STEP file indicating this condition.</p>
      <p class="para_division">AP214 currently has the limitation of only allowing the collectors of geometry to contain one conformance class (solids, surfaces or wireframe). Solids can only contain solid entities etc. Therefore, if a reference set or entire part instance has multiple geometry types, each type will be output as a separate shape_representation linked together through the SHAPE_REPRESENTATION_RELATIONSHIP entity. A generic SHAPE_REPRESENTATION will be linked to the other shapes as well as linked to the PRODUCT for the part using SHDFRP entities. The relationship for these SHDFRP entities will follow the recommended procedure for defining AND conditions indicating that all shape_reps are required to fully define the PRODUCT.</p>
      <div class="title_division">Product structure</div>
      <table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="151*">
            <col span="1" width="281*">
            <col span="1" width="21*">
            <col span="1" width="20*">
            <col span="1" width="21*">
         </colgroup>
         <tr bgcolor="#C0C0C0" valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_th">NX Entity</p>
            </th>
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_th">STEP Entity</p>
            </th>
            <th bgcolor="#c0c0c0" colspan="3" rowspan="1" valign="top">
               <p class="para_th">Notes</p>
            </th>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">part</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Product</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="3" rowspan="1" valign="top">
               <p class="para_td">1, 4</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">reference set</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">shape_definition_repesentation</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="3" rowspan="1" valign="top">
               <p class="para_td">2</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">different geometry types in the same reference set, or part with no reference sets.</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">shape_representation_relationship</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="3" rowspan="1" valign="top">
               <p class="para_td">3</p>
            </td>
         </tr>
         <tr bgcolor="#F0F0F0" valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Assembly/Component part Instance</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Context_dependent_shape_representation</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="3" rowspan="1" valign="top">
               <p class="para_td">&ndash;</p>
            </td>
         </tr>
      </table><br><p class="para_division">NOTES</p>
      <table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="38*">
            <col span="1" width="161*">
         </colgroup>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Note 1</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">For each NX part there will be a basic product structure set of routines output these will be: SHAPE_DEFINITION_REPRESENTATION&rarr; PRODUCT_DEFINITION_SHAPE&rarr;PRODUCT_DEFINITION&rarr;PRODUCT_DEFINITION_FORMATION&rarr;PRODUCT.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Note 2</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Each separately instanced reference set in a component will become a different SHAPE_DEFINITION_REPRESENTATION entity pointing to the SHAPE_REPRESENTATION of the geometry for the reference set, and the PRODUCT_DEFINITION_SHAPE associated to the Product for the NX part.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Note 3</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Each individual reference set, or NX part with no reference set, that contain more than 1 kind of geometry (solid, surface, wireframe), will be output as a specific shape_representation tied together with SHAPE_REPRESENTATION_RELATIONSHIP entities.</p>
            </td>
         </tr>
         <tr bgcolor="#F0F0F0" valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Note 4</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">The name of the NX part file will be placed on the representation_context.id and the product.id entities. In addition, the representation_context.type box will contain either TOP_LEVEL_ASSY or COMPONENT related to the part use.</p>
            </td>
         </tr>
      </table><br></body>
</html>