This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

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

Modeling business entities

This data modeling information describes how to model business entities in BMC Atrium CMDB. The information uses the Common Data Model (CDM) and extensions to that model, and explores recommended practices for using new entities effectively.

This data modeling information illustrates how to use the classes that BMC provides for the BMC Atrium CMDB to model a particular business entity, focusing on how you use the entire model rather than on general information about a class or attribute. Although descriptions of classes and attributes are provided to give you context when determining how to model CIs, detailed information such as syntax and the type of attribute is not specified. For that level of information, see the BMC Atrium CMDB Data Model Help.


This information is intended for configuration managers, application administrators, asset analysts, and related IT professionals.

About Atrium CMDB

The BMC Atrium Configuration Management Database (CMDB) enables you to store and manage information about products and services that are in your environment. The BMC Atrium CMDB uses the term class to describe a configuration item (CI) or relationship classification. Each CI is partially classified using some common attributes that describe the base class (BMC_BaseElement ). Specific details about each class of CI are described by attributes of subclasses of BMC_BaseElement. Relationships are also modeled as a base relationship class (BMC_BaseRelationship ) with subclasses for different types of relationships.

As a provider of BMC Atrium CMDB data, BMC Atrium Discovery products can discover large amounts of configuration data for use by data consumers. BMC Atrium Discovery products are natural enablers for the creation of service models because they can discover many of the components, or CIs, that ultimately make up the service models. These components include:

  • Computer systems (including servers, routers, physical and virtual systems, and operating systems)
  • Applications
  • Software servers (including specialized elements such as SAP, Siebel, and mainframe infrastructure components)
  • Databases
  • Business process definitions
  • Network elements


In many cases you will be modeling an entity using classes from the CDM, but you might also model part of that same entity using an extension to the CDM. For models that require extensions to the CDM, the term data model is used. This information is organized so that the entities are introduced first in each section, including the recommended practice for that implementation. Any classes and attributes that can be included in the deployment of these business entities in an IT infrastructure are described in an architectural diagram. Where appropriate, recommendations are provided for setting specific attributes for a given class.

Attributes are defined as either key or additional. Key attributes are those that BMC recommends that you populate for a given class to model a specific CI. Additional attributes are optional attributes that you can populate to further classify a CI or relationship.

Differentiating Name and ShortDescription attributes

A common misconception is that the caption for the CI on user interfaces and reports is represented by the Name attribute, when it is actually the ShortDescription attribute. In the data modeling diagrams, the names that appear are not from the Name attribute, they are the ShortDescription attribute (which is usually just a user interface caption). Also, in modeling recommendations, ShortDescription is the more user-friendly label, and should always be provided and set with a value that makes sense to an end user.

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