Index design and structured content

Teamcenter maintains a separate index for structured content to ensure search results are always up-to-date. The administrator defines the structures and configurations to index, minimizing response times whenever a user searches for data. The following diagram shows the indexing framework mechanism. The following diagram shows the process that occurs when you create an index for structured content. To define structured content search indexes, you define property constants on structure elements in the Business Modeler IDE to specify the properties to index. The Teamcenter indexer then indexes those properties when it creates or updates the structured content index. You use the same property constants as you use with the basic search in Active Workspace but attach them to structure elements. Changing the structure filters follows the same process as other search filters. You must reindex the structure at regular intervals to ensure that the search results reflect changes to the structure. Manual edits and system operations (for example, release and revise) on structures are reflected only after the indexer processes the changes. Each top level of a structure is indexed for all the specified revision rules and effectivities. For example: Latest Working, Released creates one set of occurrences. Released creates one set of occurrences. Released, Effectivity Milestone 1(1/1/2013) creates one set of occurrences. For best performance, Siemens Digital Industries Software recommends you index only those structures and configurations that are frequently accessed.

Note Whenever there is a change to a revision rule or a saved variant rule (SVR), you must run an index synchronization on the structure. For each searchable revision rule, the system creates a unique set of occurrences that includes all possible variations in the structure (sometimes referred to as a 150% BOM). Each indexed occurrence is stored with a bit mask that identifies the valid variant rule for the occurrence. The variant mask is exported in TC XML format and indexed in the Teamcenter indexer. Teamcenter can then process the bit mask to build a 100% BOM for any given variant rule.

Tip To have the index update the variant mask when new SVRs are added to the index definition, set the PersistFullyExpandedSVR site preference to true before creating the SVRs. The following diagram shows the process that occurs when a user changes index content and Teamcenter updates the index. Teamcenter maintains the indexed status of each structure in the Awb0BOMIndexAdminData business object on the awb0IndexState property.