How Calbro Services extends the data model
Calbro Services wants to track the model year of several of the devices on the network, such as servers, workstations, routers, and so on. Because the model year is a critical piece of information, the administrator wants to include it in the data model.
Working through the preferred means of building the data model, the Calbro Services administrator first considers federating the model year data. This data is not information related to configuration items (CIs), such as incident requests. Neither is it non-critical detailed information about CIs, such as service records. The model year is a critical piece of information about computer equipment used throughout the company, so the administrator discards federation as an option.
Second, the administrator considers using the existing
Item attributes to store the model year data. These attributes are used for classification, and are insufficient for storing model year information.
Third, the administrator considers using an existing BMC Software extension to the data model, but the model year is not included in extensions Calbro Services intends to use.
Next, the administrator considers adding a new attribute to an existing class. The model year is important to different consumers of BMC Atrium Configuration Management Database (BMC Atrium CMDB) data. After referring to BMC Atrium CMDB Data Model Help, the administrator learns that the new attribute could be added to the
BMC_ComputerSystem class. Because each subclass inherits attributes from its superclass, the
BMC_Printer classes could also use the new attribute. The administrator would like the option of tracking the model year of mainframes and printers, and so decides that the best approach is to extend the data model by adding a new attribute to the existing