Configuration Management Database (CMDB)
A Configuration management database (CMDB) is a repository that is designed to store many of the components of an information system. A CMDB contains data describing managed resources like computer systems and application software and/or process artifacts like incident, problem and change records, and the relationships among these entities. In the context of ITIL (Information Technology Infrastructure Library http://www.itil-officialsite.com/home/home.asp), a CMDB represents the authorized configuration of the significant components of the IT environment. A key goal of CMDB is to help an organization understand the relationships between different components and track their configuration. The CMDB is a fundamental component of the ITIL framework's Configuration Management process. CMDB implementations may integrate with change management, knowledge management and/or authorization.
The CMDB module with the Tracker, Wiki, Search and Report components is a flexible framework for
- Incident Management,
- Problem Management,
- Knowledge Management,
- Asset management,
- Change Management,
- Service Desk and
Configuration Management Database (CMDB) ITIL defines a CMDB as a database used to store Configuration Records throughout their Lifecycle. The Configuration Management System maintains CMDBs, and each CMDB stores Attributes of CIs (Configuration Items), and Relationships with other CIs.
Configuration Item (CI) A Configuration Item is an entity in a configuration management solution such as a CMDB. ITIL defines a CI as any component that needs to be managed in order to deliver an IT Service. Information about each CI is recorded in a Configuration Record within the Configuration Management System and is maintained throughout its Lifecycle by Configuration Management. CIs are under the control of Change Management. CIs typically include IT Services, hardware, software, buildings, people, and formal documentation such as Process documentation and SLAs.
The codeBeamer CMDB functions similarly to Trackers, but CMDB maintains Configuration Items organized in categories, instead of issues organized in Trackers.
See related information Trackers,Reports (Vintage),State Transitions
Two project level permissions can be used to control whether project members in a specific role can see the CMDB module, and if they are able to create and customize configuration item categories:
If you wish to edit these permissions, select the Members tab in the project, then select Edit in the tool-tip menu beside the role that you wish to edit.
You can create and customize a CMDB Category in the same way as a Tracker. Workflows are also available. Please see the document links, above.
Configuration items always have specific field default values and access permissions per defined item status, even if no workflow is active.
Using a Configuration Management Database in conjunction with the ability to link issues with configuration items gives you new possibilities to improve transparency and traceability.