CMDB architecture
A CI is the most granular component that must be managed to deliver an IT service. CIs typically include hardware, software, buildings, people, and formal documentation, such as process documentation and Service Level Agreements (SLAs). A CI must be uniquely identifiable, manageable, have certain attributes associated with it, and can be recorded BMC Helix CMDB.
Information about each CI is recorded in a configuration record within BMC Helix CMDB and maintained throughout its lifecycle. For more information, see the Common-data-model.
The following diagram illustrates a high-level overview of how raw data from multiple discovery service providers flows into BMC Helix CMDB. It highlights the processes performed in CMDB to transform this data into the production dataset (BMC.ASSET) and how this production dataset is utilized by various consuming applications:
BMC Helix CMDB provides a structured approach to managing configuration data and relationships across IT environments. Here's how its components and processes work together:
Step | Task | Description |
---|---|---|
1 | Discovery of Data |
|
2 | Dataset Organization |
|
3 | Normalization and Reconciliation |
|
4 | Production Dataset and Sandbox Dataset: |
|
5 | Consuming Applications |
|
6 | Federated data | BMC Helix CMDB uses a federated data model, linking external data sources to the CMDB without requiring full data import. This provides real-time access to external data while reducing setup and maintenance costs. |
For information about how CMDB is placed along other BMC Helix ITSM apps and REST APIs within the BMC Helix solution architecture, see BMC Helix Service Management deployment architecture.
For more information about the components and features of BMC Helix CMDB, see Product-overview.