How the Common Data Model represents service models

The Common Data Model ( CDM) is an extensible class schema that represents CIs and their relationships to each other in an IT enterprise. It is designed to store asset data (as hardware, service management, and user information) and to provide a mechanism for linking that information to provide a complete view of how all the elements of a company are connected and can affect each other.

All service component types (classes) are defined in the BMC Atrium CMDB as part of the CDM. A class is the definition or metadata that describes an object type. The class includes information about the object type, such as attributes, primary key, and so on.

Infrastructure Management classes

Infrastructure Management extends the BMC Atrium CMDB CDM with a predefined set of Infrastructure Management-enabled classes. The asset information you use to define the service model is a subset of all of the configuration data in the CDM. The BMC CMDB Extensions also define attributes that are used only for Infrastructure Management, such as StatusModel and ImpactCostPerSec.

All components in the data model derive from a single subclass, BMC_BaseElement, and all relationships derive from the BMC_BaseRelationship subclass.

The following tables list the main data subclasses to BMC_BaseElement that are associated with service impact management. For a graphical representation of the hierarchy of the Common Data Model, see the Common Data Model Diagram included with BMC Atrium CMDB documentation.

The following table lists the Infrastructure Management qualified subclasses for BMC_Collection, which provides mechanisms for grouping components together into logical elements, including business processes and services.

Infrastructure Management-qualified subclasses of BMC_Collection

The following table lists the Infrastructure Management -qualified classes for BMC_LogicalEntity, which tracks other logical elements of a system, including people, physical plants, and location information. 

 Infrastructure Management-qualified subclasses of BMC_LogicalEntity

The following table lists the Infrastructure Management -qualified classes for BMC_System, which contains the definition of computer systems, mainframes, application systems, and virtual systems. 

 Infrastructure Management-qualified subclasses of BMC_System

The following table lists the Infrastructure Management -qualified classes for BMC_SystemComponent, which stores information about the components that comprise the system. This includes physical components, such as disk drives and monitors; applications, such as Microsoft Word; and other soft elements, such as network drives and file shares. The attributes for BMC_SystemComponent are SystemClassId and SystemName. 

 Infrastructure Management-qualified subclasses of BMC_SystemComponent

The following table lists the Infrastructure Management -qualified classes for BMC_SystemSoftware, a continuation of the BMC_SystemSoftware entry in the following table:

 Infrastructure Management-qualified subclasses of BMC_Software

The following table lists the Infrastructure Management -qualified class for BMC_SystemService, which tracks the services used by systems. The most common services are those used by J2EE application systems, such as J2EE modules. The data model also provides a set of classes for defining relationships among CIs. The attributes for BMC_SystemService are SystemClassId and SystemName. 

 Infrastructure Management-qualified subclass of BMC_SystemService

 Infrastructure Management attributes

Infrastructure Management qualifiers have been added to the attributes listed in the following table.

Infrastructure Management qualified attributes

The definitions of the Infrastructure Management qualifiers are as follows:

• SIM: 300050
• SIM_Internal: 300060
• SIM_ReadWrite: 300070

Related topics

Infrastructure-Management-data-class-descriptions