<!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>Options</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">Options</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('translatoruser/step214_export_adv.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Options</p>
            </td>
         </tr>
      </table><br><div class="title_division">STEP entity names</div>
      <p class="para_division">The <b class="uiTerm">Long/Short STEP File Entity Name</b> option allows you to specify in what form STEP file entity names are to be output to the STEP file. Generating short names could significantly decrease the size of the STEP file generated. Short names are the abbreviated versions of STEP entity names. If you don't have a need to read the STEP file short names may be appropriate for you. You can find the STEP short names in <a class="links" href="javascript:void(0)" onclick="top.popUpPage('dataexchange/index.html?goto=dataexchange/title_page.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Data Exchange Help</a>. The <b class="uiTerm">Postprocessing</b> (<b class="uiTerm">STEP&rarr;NX</b>) function can process STEP files with long or short STEP entity names without any necessary user intervention.
      </p>
      <div class="title_division">Validation properties</div>
      <p class="para_division">The <b class="uiTerm">Validation Properties</b> option allows you to specify whether to output any functionality specified in the new proposed geometric validation properties modular extension to AP214. The default is off. If you are interested in exchanging AP214 validation properties modular extension information with a receiving system, you should verify whether the STEP AP214 postprocessor of the receiving system of interest, can process and will do anything with AP214 validation properties modular extension information, if said information is present in a STEP file. If so, you could try turning this <b class="uiTerm">Validation Properties</b> option on. Validation property information is output to the STEP file for each solid and each part (volume, area and center of gravity (x, y, and z)). You can check this information after importing the STEP file to help validate a satisfactory translation.
      </p>
      <p class="para_division">Besides outputting validation properties information to the STEP AP214 file, the schema name GEOMETRIC_VALIDATION_PROPERTIES_MIM will add to the FILE_SCHEMA entity in the header section of the STEP AP214 file. This is the schema name agreed upon by PDES Inc., which is responsible for implementation of AP214 in the production world. This AP214 validation properties modular extension information imports into NX via the STEP AP214 translator postprocessing function, without any interaction required. The STEP file validation properties information associated with the solids will convert into entity (object) attributes of type float (double) attached to the corresponding solid bodies created in NX. The STEP file validation properties information associated with the parts, will convert into part attributes of type string attached to the corresponding parts created in NX. The AP214 validation properties modular extension information will not round-trip back into NX.</p>
      <p class="para_division">Corresponds to default file option: AP214_VALPROPS_EXT.</p>
      <div class="title_division">External References</div>
      <p class="para_division"><b class="uiTerm">External References</b> is a new functionality added in the STEP <b class="uiTerm">Advanced Settings</b> tab page. When you check the <b class="uiTerm">Export Assembly as External References</b> check box the <b class="uiTerm">Export Component as</b> title appears with a list menu having STEP and NX as options.
      </p>
      <p class="para_division"><b class="uiTerm">Export Components As &ndash; STEP | NX</b></p>
      <p class="para_division">Bi-directional basic STEP external references support (top-level assembly STEP file with component references to STEP files or CAD model files instead of one big assembly STEP file) is added to the NX 5 STEP AP203 and AP214 translators. This includes bi-directional support of a top-level assembly STEP file, which contains all of the assembly structure with the leaf node components in the top-level assembly STEP file represented by external references to:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">STEP: other STEP files (NX data converted to STEP as part of the translation)</p>
         </li>
         <li>
            <p class="para_item">NX: NX part files.</p>
         </li>
      </ol>
      <p class="para_division">On export, any non-leaf node component geometry that actually lives in any of the intermediate (non-leaf) node component parts or in the top-level assembly part would end up as geometry in the top-level assembly STEP file just like when the entire assembly is all in a single STEP file. If you turn on the <b class="uiTerm">Product Structure Only</b> option, then this intermediate geometry will not be exported. In the case of importing STEP external references, the NX STEP translators will have to continue properly importing non-leaf node geometry as it currently does, without regression.
      </p><a class="endOfDocLinks" href="step214_exp_parameters.html">Parameters</a><br></body>
</html>
