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.

Getting started

The following topics help you to get started with the BMC Atrium CMDB product documentation. 

If you are a system administrator and looking for information on installing or upgrading the product, you should navigate to the BMC Remedy ITSM Deployment documentation. 

Characteristics of BMC Atrium CMDB

Many databases could be considered a CMDB; however, it is important to understand the required mechanics to deliver a true CMDB implementation. To begin with, you must be able to import data into the CMDB so it can be represented, managed, and exposed to the processes that will consume the data. In BMC Atrium CMDB, the Atrium Integrator extracts, transforms, and loads the data into the CMDB data model. The BMC Atrium CMDB also provides a dataset functionality to load data into distinct datasets, allowing you to keep your data structure organized and simplifying working with multiple data sources.

After the data loaded is into the source dataset, it must then be normalized, especially when you have multiple datasets. This stage of the data import allows for data to be transformed so that if you have multiple data sources, the data is cleaned and common terminology is applied. Normalization also allows you to set default values, such as impact values and so on, where data may be missing.

After we have our data (which is in a dataset for each source and has been normalized), we then have common terms and values stored in the Product Catalog. The next most important thing is to take the multiple datasets and construct a good, solid production dataset, which is where the reconciliation process plays an important role. Reconciliation allows us to build rules that identify data found across multiple datasets and then merge the data into our production dataset.

The result of reconciliation processing gives us our production dataset, which is referenced by the consuming processes and is used to support those processes within the overall business.


  • The BMC Remedy ITSM suite consumes the production dataset; the individual source datasets are not exposed to any applications.
  • The data that resides in the CMDB is owned by some other applications; the CMDB owns relationships between data. 

Another important factor to note about the BMC Atrium CMDB is that it has a shallow but wide data repository. The discovery tools discover a very large amount of data from your environment; however, all that data when brought in BMC Atrium CMDB need not contain entire details about the discovered data. The details should include only key information that helps you to make critical connections and maintain connectivity to your business, service, or processes. 

To summarize, BMC Atrium CMDB enables you to normalize the data to common terminology, and reconcile the data from multiple sources into a production dataset (also called the final or the golden dataset) that conforms to a common model so data can be referenced and consumed in a common way across processes, regardless of the source.

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