Setting up Smart Discovery Indexing > Generating bounding boxes and TruShape files
Generate Teamcenter bounding boxes and TruShape files for NX datasets
Process flow to generate Teamcenter bounding boxes and TruShape (TSO) files if the CAD application is NX:
- Set preferences to generate bounding boxes and TSO files.
- Upgrade legacy transforms to PLM XML transforms.
- Generate NX bounding boxes.
- Generate TSO files for NX datasets.
- Generate Teamcenter bounding boxes from NX bounding boxes.
The NX bounding box is stored in Teamcenter in a UGPART-BBOX file, and the TSO data is stored in the Trueshape-Data file. Both files are attached to the UGMASTER dataset.
Note: JT datasets are required to create the bounding boxes and TruShape for items of the type Spatial Zone or its sub-types. NX datasets are ignored for this. If JT datasets are absent, no results appear.
Ensure that Dispatcher is running to create the bounding boxes and TruShape automatically from JT datasets. Otherwise, create them manually using the create_or_update_bbox_and_tso utility with the dataset ID.
Upgrade legacy transforms to PLM XML transforms
Procedure
Find all legacy transforms by running the
qsearch_process_queueutility:qsearch_process_queue -u=<user_id> -p=<password> -g=<group> -list_legacy_transforms -outfile=c:\temp\legacytransforms.txtUpgrade the legacy transforms by running the
nxmgr_upgrade_transformsutility:nxmgr_upgrade_transforms -u=<user_id> -p=<password> -g=<group> -bypass=yes -i=c:\temp\legacytransforms.txt -upgrade_release=yesEnsure that all transforms are upgraded by running the
qsearch_process_queueutility again with the-list_legacy_transformsoption.
Generate NX bounding boxes
Procedure
Find all NX datasets that do not have the UGPARTBBOX file by running the
create_or_update_bbox_and_tsoutility:create_or_update_bbox_and_tso -u=<user_id> -p=<password> -g=<group> -translation_mode=NXBBOXFORM -mode=query -output_dir=c:\temp\ugpart_bboxThis utility generates a list of files that are saved in the location specified in
-output_dir. Use these files as the input (-i) in therun_tc_publishing_utility.batutility.Generate the NX bounding boxes by first setting the
QSEARCH_update_enabledpreference to False and then running therun_tc_publishing_utility.batutility, located inUGII_BASE_DIR\NXMANAGER(whereUGII_BASE_DIRis the folder where NX is installed):run_tc_publishing_utility.bat -u=<user_id> -p=<password> -g=dba -i="!file!" -record_pa=yes -log="!file!_refile.txt"
Generate TSO files for NX datasets
Procedure
In NX, click File > Utilities > Custom Defaults.
In the Customer Defaults dialog box, click Assemblies > Site Standards, and select the True Shape tab.
Set the cell size and cell units, and click Generate Component Shape Representations on Save.
TSO files are generated upon every save. The default cell size in NX is 0.0 mm. A cell size of 3 mm is recommended for a more accurate spatial search.
Generate the TSO files for the existing NX dataset by running the
run_tc_publishing_utility.batutility, located inUGII_BASE_DIR\NXMANAGER:run_tc_publishing_utility.bat -u=<user_id> -p=<password> -g=dba -i="!file!" -publish_tr=yes -record_pa=yes -log="!file!_refile.txt"
Generate Teamcenter bounding boxes from NX bounding boxes
You can generate bounding boxes for all data in the Teamcenter database. Although this is the recommended method, it is time-consuming. If you do not wish to wait for all data to be indexed, you can proceed and generate bounding boxes and TSO files for a specific structure.
Generate bounding boxes and TSO files for all data: query the Teamcenter database first to find out how many bounding boxes must be processed for the entire database, then create the bounding boxes using the NX bounding box data:
create_or_update_bbox_and_tso -u=<user_id> -p=<password> -g=dba -translation_mode=NXBBOXTOBBOX -mode=query+process
Generate bounding boxes and TSO files for a specific structure: query the Teamcenter database first to find the structure indexed using Smart Discovery Indexing, then create the bounding box:
create_or_update_bbox_and_tso -u=<user_id> -p=<password> -g=dba -translation_mode=NXBBOXTOBBOX -mode=query+process -product=<product_item_id>
If Multi-Field Key (MFK) is used to uniquely identify a structure:
create_or_update_bbox_and_tso -u=<user_id> -p=<password> -g=dba -translation_mode=NXBBOXTOBBOX -mode=query+process -product=%#MFK#%,=item_id=<product_item_id>,object_type=<item_or_its_sub_type>
For detailed information about the create_or_update_bbox_and_tso utility and its arguments, run create_or_update_bbox_and_tso -h on the Teamcenter command prompt.
Source: https://docs.sw.siemens.com/en-US/doc/282219420/PL20251212545240207.structure_discovery_admin/xid1972398 · retrieved 2026-07-11