This documentation supports the 19.02 version of Remedy with Smart IT.

To view the latest version, select the version from the Product version menu.

Adding indexes for improving asset search

This topic provides additional suggestions for improving performance based on internal benchmarks and field engagement.

On the Asset Console, depending on the filters you commonly use, you might need to fine tune the performance of Smart IT. To improve performance, you can apply indexes to the fields listed in this topic, which are found to under perform during asset searches.

Best Practice

Along with indexes, performance improvement also depends on the query criteria that are used in conjunction with indexes. Therefore, we recommend that you create composite indexes based on common search patterns, or the typical query patterns used in your organization. For example, consider search patterns for product categorization related fields such as product name, model, and version, or location related fields such as region, site group, and site.

Disclaimer

Effectiveness of indexes depends on the distribution of data and the use of query criteria. To ensure better performance, carefully test the indexes before you implement them in your production environment. 

You can create separate indexes on the fields listed in this topic. You may preferably use BMC Atrium Class Manager for adding indexes on the fields pertaining to BMC.CORE:BMC_BaseElement. The AST:Attributes fields requires BMC Remedy Developer Studio for creating indexes. Creating indexes by using BMC Atrium Class Manager is a handy way, but it is not a mandatory method. You may still create indexes using BMC Remedy Developer Studio, if it is available. Your preference depends on the availability and accessibility to these tools. 

Indexes for searching asset by using Keyword

Field nameForm nameField name and ID
AssetIDAST:AttributesAssetID(210000000)
NameBMC.CORE:BMC_BaseElementName(200000020)

 Indexes for searching assets by using Scanned code

Field nameForm nameField name and ID
TagNumberAST:AttributesTagNumber(260100004)
SerialNumberBMC.CORE:BMC_BaseElementSerialNumber(200000001)

You can create composite indexes on the following fields:

Indexes for searching assets by using Type/Subtype

Field nameForm nameField name and ID
DatasetIdBMC.CORE:BMC_BaseElementDatasetId(400127400)
ClassIdBMC.CORE:BMC_BaseElementClassId(400079600)

Indexes for searching assets by using Product Category/Name

Field nameForm nameField name and ID
TypeBMC.CORE:BMC_BaseElementType(200000004)
ItemBMC.CORE:BMC_BaseElementItem(200000005)
ModelBMC.CORE:BMC_BaseElementModel(240001002)

Depending on the common search pattern followed at your site, you can create separate or composite indexes on the following fields:

Indexes for searching assets by using other available filters

Field nameForm nameField name and ID
RegionBMC.CORE:BMC_BaseElementRegion(200000012)
SiteGroupBMC.CORE:BMC_BaseElementSiteGroup(200000007)
SiteBMC.CORE:BMC_BaseElementSite(260000001)
RoomBMC.CORE:BMC_BaseElementRoom(260000005)
FloorAST:AttributesFloor(260000004)
StatusAST:AttributesAssetLifecycleStatus(7)
ManufacturerBMC.CORE:BMC_BaseElementManufacturerName(240001003)

(Change request tickets only) You can create separate indexes for searching assets by using keywords in the default text field:

Indexes for searching assets by using keywords

Field nameForm nameField name and ID
NameBMC.CORE:BMC_BaseElementName(200000020)
ManufacturerNameBMC.CORE:BMC_BaseElementManufacturerName(240001003)
ModelBMC.CORE:BMC_BaseElementModel(240001002)
Was this page helpful? Yes No Submitting... Thank you

Comments