<!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>STEP AP214 Entity conversion (STEP 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_topic4" id="xps10_pagetitle">STEP AP214 Entity conversion (STEP to NX)</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">As explained in the Introduction, AP214 currently defines eighteen conformance classes of data, which 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. The STEP AP214 translator can process some STEP AP214 product id, version and description information into NX part attributes.</p>
      <div class="title_division">AP214 S1 Product management to NX &ndash; S1: Product management data</div>
      <table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="99*">
            <col span="1" width="136*">
            <col span="1" width="64*">
         </colgroup>
         <tr bgcolor="#C0C0C0" valign="top">
            <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">NX Part 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">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">PRDCNT_NAME</p>
               <p class="para_td">PRDCNT_DISCIPLINE</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">application_context.application</p>
            </td>
            <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">1</p>
            </td>
         </tr>
         <tr valign="top">
            <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">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">&ndash;</p>
            </td>
         </tr>
         <tr valign="top">
            <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">PDFWSS_ID</p>
               <p class="para_td">PDFWSS_NAME</p>
               <p class="para_td">PDFWSS_SOURCE</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">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">PRDDFN_ID</p>
               <p class="para_td">PRDDFN_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">design_context.name</p>
               <p class="para_td">design_context.discipline_type</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">PRDFCN_NAME</p>
               <p class="para_td">PRDFCN_DISCIPLINE</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">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">PRDFSH_NAME</p>
               <p class="para_td">PRDFSH_DESCRIPTION</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">&ndash;</p>
            </td>
         </tr>
      </table><br><table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="39*">
            <col span="1" width="160*">
         </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><p class="para_division">Product (element) structure will be utilized to generate NX part files and assemblies of those part files. There will be a NX part file for each PRODUCT entity within the STEP file. It is possible to have several shape_representations pointing to the same PRODUCT through SHAPE_DEFINITION_REPRESENTATION and SHAPE_REPRESENTATION_RELATIONSHIP entities. Each of these shape_representations, associated through SHAPE_DEFINITION_REPRESENTATION entities, will be put in a different reference set within the NX part file.</p>
      <p class="para_division">If these shape representations are used in assembly mapping, then the reference set will be used to set up the NX instance. In this way, you will be able to change which piece of the geometry is used in the interactive <b class="uiTerm">Assemblies Navigation Tool</b> (ANT). Shape_representations related through the SHAPE_REPRESENTATION_RELATIONSHIP entity will be placed in the same reference set. See <a class="links" href="javascript:void(0)" onclick="top.popUpPage('assemblies/index.html?goto=assemblies/01topic_1.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Assemblies Help</a> for further information on the ANT and reference set use. These changes will mean that all representations of a PRODUCT will be found in the same part file separated into different reference sets.
      </p>
      <p class="para_division">STEP files found without PRODUCT structure entities are invalid STEP files, but will be processed as much as possible. All geometry will be placed into a single NX part file with each SHAPE_REPRESENTATION going into a reference set. An assembly part file will then be created instancing each reference set as a separate occurrence. In this way, you can interactively pick which data to include and exclude in the file through activating and deactivating the reference sets in the ANT. This is the best that can be done with a file lacking PRODUCT structure entities.</p>
      <div class="title_division">Product structure</div>
      <table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="99*">
            <col span="1" width="134*">
            <col span="1" width="66*">
         </colgroup>
         <tr bgcolor="#C0C0C0" valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_th">STEP Entity</p>
            </th>
            <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">Notes</p>
            </th>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Product</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Part file</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">1, 2</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Shape_definition_representation</p>
            </td>
            <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">3</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Shape_represenation_relationship</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Geometry</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">4</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Context_dependant_shape_representation&rarr;Representation_relationship&rarr;Representation_relationship_with_transfrom</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Assembly / Component instance</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">5</p>
            </td>
         </tr>
         <tr bgcolor="#F0F0F0" valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Mapped_Item&rarr;Representation_map&rarr;Shape_representation</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Assembly / Component instance</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="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">The STEP file data is assumed to be in millimeter length units and radian angle units if a geometric_representation_context entity construct is not present in the STEP file or there is problems processing said geometric_representation_context entity construct. The link between the geometry and the PRODUCT will be through the 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">The name of the generated part will be derived in 2 ways. It will first be taken from the representation_context.id value pointed at by the shape_representation. If product structure is included in the file and a product entity is included, then the name will be changed to that on the product.id entity.</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 separate SHAPE_DEFINITION_REPRESENTATION entity pointing to the same PRODUCT, will become reference sets in the NX Part with each reference set being the geometry associated with the pointed to SHAPE_REPRESENTATION.</p>
            </td>
         </tr>
         <tr 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">This entity links different types of geometry to the same product. Therefore this will not generated specific NX entities, but the shape_representations related will place different types of geometry in the same reference set/ NX part combination.</p>
            </td>
         </tr>
         <tr bgcolor="#F0F0F0" valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Note 5</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">There will be a complex entity made up of Representation_relationship (RPRRLT), Representation_relationship_with_transform (RRWT) and Shape_representation_relationship. The SHRPRL entities points to the two related shape_representations. The RRWT points to a transformation entity indicating the positioning of the component to the assembly.</p>
            </td>
         </tr>
      </table><br></body>
</html>
