Using NX based cacheless search

If you use NX, it calculates the bounding box for a part and stores it in Teamcenter as a UGPART-BBOX named reference in a UGMASTER dataset. Teamcenter reads the bounding box information from the UGPART-BBOX form. NX can also be configured to create TruShape data for the part and store it as a Trushape-Data named reference in the UGMASTER dataset.

The accuracy of the search depends on the cell size you configure in NX. A small cell size provides more accurate search results, but the TruShape files are larger and the response times, slower.

If you import existing NX assemblies, set the QS_NX_RELATION_POST_ACTION_ENABLED preference to True and Teamcenter creates the necessary bounding box data automatically.

In many deployments, it might not be necessary to use Dispatcher because you can use some other mechanism to create and update search indexes. However, you must update search indexes periodically. The indexer must always be up and running. Spatial search indexes are generated from the bounding boxes. That is, bounding boxes are an input to the search index. Teamcenter Integration for NX creates bounding boxes. It cannot create search indexes. Advanced NX features such as datum points, weld points, and deformable components are available on both JT and NX datasets.

Apart from NX, for CAD integrations, such as CATIA, Solid Edge, and Pro/ENGINEER (Pro E), the JT-based integration is used to generate the bounding boxes from JT parts. For these integrations, you must install a dispatcher-based translator (JTTOBBOXTSO).

Use the create_or_update_bbox_and_tso utility with the JTTOBBOX+JTTOTSO option selected to generate bounding box data that includes advanced NX features. You can then run the qsearch_process_queue utility Dispatcher service to create the corresponding search index.

On high performance hardware with a well-tuned database, Teamcenter can create bounding boxes for 10,000 parts to 20,000 parts per hour from NX data.