Federated data model
BMC Atrium Configuration Management Database (BMC Atrium CMDB) uses a federated data model, which means that you can keep some data in managed data repositories in lieu of populating BMC Atrium CMDB with all your data. The most common types of federated data are related information and detailed attributes. Related information is information about a configuration item (CI) that does not itself qualify as a CI and therefore should not be stored in a CMDB. Detailed attributes are attributes of CIs stored in BMC Atrium CMDB, but they are attributes that are not important enough to track at the level of a CMDB.
For information about what qualifies as a CI, see Configuration items in an ITIL CMDB.
For related information, your CI records for software instances might link to the URL of an intranet page where the software license is posted, or each CI record might link to information necessary to search a problem database for all problems concerning that CI.
For detailed attributes, the CMDB record for an employee might have a Skills attribute that contains a list of the employee's skills and a Department attribute that contains the employee's department name. It might also link to an HR database where additional attributes, like Salary, that are not really important from a configuration perspective are stored.
Federated data might be stored in a discovery database, a Capacity Management system, an Availability Management system, or other external data stores. You can retrieve federated data and view it with BMC Atrium Explorer, as if it were stored in BMC Atrium CMDB. The BMC federated data model enables you to connect to Java database connectivity (JDBC) compliant databases, CMDBf-compliant CMDBs, and BMC Remedy AR System forms.