BMC Configuration Management Database (BMC CMDB) helps you source, store, monitor, and manage the data related to configuration items (CIs) like IT hardware and software, printers, servers, air conditioners, and so on, including the relationships among them. This data helps you understand your environment better.
Data flow in BMC CMDB
From a high level, the following video (11:48) shows you the end-to-end steps that are required to take your data into production with BMC Atrium Core — from a third-party source to your production dataset in BMC Configuration Management Database (BMC CMDB).
This video is recorded using the earlier version of BMC Atrium Core but the principles are relevant.
Data flow in BMC CMDB
Data providers, such as discovery applications, put data into BMC CMDB, where it is partitioned into separate datasets. This data is then brought together into a consolidated production dataset that you use as the single, reliable source of reference for your IT environment. Consuming applications, such as Remedy IT Service Management (Remedy ITSM), BMC Asset Management, BMC Service Level Management, applications represented in Business Service Management, and more, use the data in the production dataset.
The BMC CMDB user interface attempts to provide a unified experience to the various workflows and tasks that one needs to perform when monitoring and managing a CMDB.
ITIL processes and BMC CMDB
ITIL standardizes the processes that IT departments use to manage IT hardware and software, such as Problem Management, Incident Management, and Change Management. These standard processes ensure the availability of the critical IT services that sustain a business, like banking systems, ordering systems, and manufacturing systems. Additionally, ITIL Service Asset and Configuration Management needs reliable data about components in the IT environment and needs to understand the impact to key business services when changes occur in that environment.
Central to ITIL processes that involve maintaining and managing information about thousands of pieces of hardware and software is the configuration management database. The data in the BMC CMDB feeds the applications that perform ITIL processes.
Discovery applications help identify various systems in the network and obtain information about them that is relevant to the CMDB. Applications such as BMC BladeLogic Client Automation Configuration Discovery provide data to the Integrator. Applications such as BMC Discovery provide data directly to the Import dataset.
The Integrator is an integration engine that enables you to transfer data from external data stores to BMC CMDB classes.
A dataset is a local grouping of data. An import dataset is data in its unprocessed form and cannot be used for ITIL processes until it is normalized and reconciled.
Normalization is the imposition of standards or regulations as defined in the product catalog. The normalization engine standardizes, corrects, and cleans up the data drawn from various discovery sources.
- Updating the name and version information for products and suites based on the definitions in the product catalog.
- Setting impact relationships that define dependencies between CIs.
- Setting attributes that are customized for specific use cases.
Reconciliation is the process in which data from different discovery sources is checked and corrected to maintain consistency while also making sure there is no duplication of data.
This reliable data helps you understand the environment and the impact to key business services when changes occur in this environment.
Any changes that need to be made to the production dataset are first tried out in the sandbox dataset. If the implementation is successful, only then are they moved to the production dataset. The sandbox provides a safety mechanism that prevents unintended changes to your production dataset.
Federated data is data stored outside BMC CMDB, but linked to CIs so that it is accessible through BMC CMDB. The most common types of federated data are related information and detailed attributes.
Roles with respect to the product, key responsibilities, and documentation
The following diagram explains the various product roles, their key responsibilities, how that relates to the various ITSM components, along with various areas of the documentation to find that information.