This documentation supports the 19.08 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

Best practices for extending the data model

This section lists the best practices to be followed when extending the data model.

Guidelines for adding attributes and subclasses

If you decide to add attributes or subclasses, follow these guidelines:

  • Perform the work using the Class Manager, an API program, or the cmdbdriver command.  Modifying the BMC CMDB data model requires more than just editing a form, and you might break some functionality. You can use Remedy Developer Studio to modify field layout and labels.


    Never make those changes directly on class forms using Remedy Developer Studio.

  • Because a CMDB gets its value by sharing data among applications, make your extensions as widely useful as possible, so that they can meet multiple needs. Avoid extensions that narrowly cater to one application, even for high-volume uses.
  • Do not create classes more than five database join levels deep. For information about the classes that use joins, see How CMDB data is stored in Remedy forms

Determine whether you want to store configuration data or lifecycle data for the CI in the new attribute. You must add a new attribute to a class to store only configuration data about a CI. To store lifecycle data for a CI, you must add a field on the AST:Attributes form that is installed by Remedy ITSM suite version 8.0 and later. For more information on Adding data to AST:Attributes in relation to CIs, see  Understanding tools and guidelines for extending your asset and CMDB data model Open link .


 In versions prior to 8.0, Remedy ITSM suite extended CI lifecycle data as attributes in BMC CMDB. With multiple datasets, multiple copies of the CI lifecycle data were created and stored in BMC CMDB. However, CI lifecycle data is not discovered and does not have to be reconciled across multiple datasets. Because of this, version 8.0 of Remedy ITSM suite moved the CI lifecycle data out of BMC CMDB and included the data as fields in the Remedy ITSM suite Foundational form, AST:Attributes. When creating the Remedy Asset Management UI, the CMDB2ASSET process joins the BMC CMDB class table and the AST:Attributes table.

The change in the process of storing the CI lifecycle data greatly improves the performance of BMC CMDB, creates only a single instance of CI lifecycle data, and gives control of the CI lifecycle data to the Asset Manager instead of the Configuration Manager. For detailed information about the changes, see Changes to the BMC CMDB for BMC Remedy ITSM Open link .

Naming and numbering rules for new classes and attributes

  • If you create classes or attributes in your data model, use the following guidelines:

    • Item names like Class name, Attribute name, and Dataset name are case sensitive. However, it depends on the case sensitivity for fields configured in the database tables. CMDB inherits the database configuration for case sensitivity.
      Consider the following
      • You have configured unique index for the item names in the database table
      • Case sensitivity configuration in the database is disabled
      • You have created two classes, BMC_Test and BMC_TEST, in CMDB
      In such case, the database will create two class names with a unique index violation exception warning message.
    • Name a new class with a prefix other than BMC_ to identify it as your own, and make the name descriptive.
    • Give an attribute an Attribute Name that is unique across your entire data model.
    • Give attributes a Field ID greater than 536870911 or leave this field blank to automatically generate an ID. 

      Specifying a value greater than 536870911 enables you to create custom Remedy AR System workflow on the field and share the workflow between forms, because you can give the same ID to a field on another form. 

      It is better to give attributes a Field ID that is unique across your entire data model; therefore you should share workflow only between a BMC CMDB form and a form that is not part of BMC CMDB. See the Remedy Action Request System documentation for information about sharing workflow and other benefits of specifying a Field ID. 

      BMC Software reserves numbers 536870911 and lower.

Documentation of data model extensions

Just as you need to occasionally look up information about classes in the Common Data Model (CDM), you will need to look up information about classes and attributes that you create. Enter descriptions for each in the Description fields available in the Class Manager.

You can generate an updated version of BMC CMDB Data Model Help — the HTML Help system that provides information about the data model — to reflect your current data model and to include the descriptions for the classes and attributes that you add.

For instructions on generating updated BMC CMDB Data Model Help with the cdm2html utility, see Creating Data Model Help with the cdm2html utility.

Visibility of data model changes to applications

When you add classes and attributes to your data model, they are not automatically picked up by BMC Software products that use BMC CMDB, such as BMC Impact Solutions or Remedy Asset Management. To use the new classes and attributes with one of these applications, you must customize the application.

Remedy AR System applications

Some Remedy AR System applications, such as Remedy Asset Management, maintain their own set of join forms for viewing and modifying BMC CMDB instance data. After you add a new class, BMC CMDB can generate these join forms for such an application and arrange the fields according to view templates specified by the application. For information about controlling the layout of class forms, see Control of the layout of class forms.

Was this page helpful? Yes No Submitting... Thank you