Supported BMC Helix CMDB CDM classes
Related topics
BMC Helix Telco Extensions uses configuration item (CI) data from the BMC.ASSET dataset to perform impact analysis. This data is used to evaluate how degraded or impaired input CIs associated with an incident affect related business services. Before running the impact analysis, you must run the CMDB SmartGraph Sync schedule from the BMC Helix CMDB Portal. For details, see Syncing CIs by using SmartGraph Sync from BMC Helix CMDB.
CI data from a service provider’s network is first transferred to BMC Helix CMDB, where it is normalized and reconciled. A selected subset of this data is then synchronized to a graph database, referred to as the DSM partition, for use in impact analysis.
The following classes from the BMC_BaseElement parent class of the BMC Helix CMDB Common Data Model are supported with BMC Helix Telco Extensions:
Class | Sub-class | Description | Class type type | Required? | Hidden? |
|---|---|---|---|---|---|
BMC_Service |
| This class is the base class for defining the service hierarchy. All services are related to products or resources. | Regular | N | N |
BMC_CustomerFacingService | This class defines the properties of a customer-facing service. For example, a VPN is a customer-facing service, but the sub-services that perform different types of routing between network devices that make up the VPN are examples of resource-facing services. | Categorization | N | N | |
BMC_ResourceFacingService | This class is an abstract class for resource-facing services. The class defines the characteristics of particular services that support the network or infrastructure part of the service. Resource-facing services are internal technical solutions required to support a customer-facing service. For example, a VPN is an example of a customer-facing service. This particular type of VPN may require a Border Gateway Protocol (BGP) to support it. BGP is an example of a resource-facing service. | Categorization | Y | N | |
BMC_Resource |
| This class defines the attributes that fit any of the following descriptions:
| Regular | N | N |
BMC_PhysicalResource | This class serves as an abstract base class for describing the various types of hardware that comprise a product. This class has the following purposes:
| Categorization | N | N | |
| BMC_PhysicalLink | This class is a non-abstract class that represents the connections between hardware entities. This class enables the modeling of wireless and connector-based communication. | Categorization | N | N | |
BMC_LogicalResource |
| This class is an abstract base class for describing different logical aspects of devices, such as device interfaces (DeviceInterfaces) that constitute a product. This class has the following purposes:
| Categorization | N | N |
BMC_NetworkAddress | This class represents the generic concept of a network address. Its subclasses define different types of addresses for different technologies. It serves as a convenient point for sourcing and terminating relationships, eliminating undue duplication of relationships that interact with the subclasses of NetworkAddress. | Categorization | N | N | |
BMC_Protocol | This class is an abstract base class for representing protocols that can be managed. This class serves as a convenient aggregation point for defining how protocols are managed and utilized. | Categorization | N | N | |
BMC_TopologicalLink | This class represents a communication relationship between network entities and indicates the information intended to flow between those network entities. This class always represents a logical relationship. | Categorization | N | N |