Which component will typically store the instances of all organizational configuration items?

A CMDB (Configuration Management Database) is a database that stores information about your IT environment and its components. A  CMDB and the processes that go along with it are the foundation of modern IT – enabling companies to manage information about a variety of IT components at the same time (even if the devices are distributed). In addition to assisting the organization with providing IT services, the CMDB is an essential resource for decision-makers who need the information to improve its cost, quality, and performance

CMDB benefits

A central point of reference for all components of IT infrastructure

Before CMDB, information about IT assets and infrastructure was siloed across different systems and often outdated. With CMDB, all these data are managed in a single system, acting as a centralized reference point where you can easily access it. For example, your CMDB will quickly answer questions like “What IT assets are connected to an employee who was just terminated?” or “How many installations of a certain software product exist on all computers across the organization?” With CMDB, you can easily access the change and deployment history for each CI and measure the total cost of ownership of every IT asset in your company.

Transparent oversight of IT infrastructure for better asset management

An up-to-date CMDB keeps track of all IT infrastructure components within the organization, knowing where they are deployed and who are in charge of them. Lack of this information could expose organizations to the unnecessary risk of unauthorized access to sensitive company data (for example, via improper disposal of old hardware) or non-compliance with software license agreements. CMDB makes all your IT assets visible and trackable. Authorized personnel can access the CMDB to check the status of each item throughout its entire lifecycle and understand its relationships with other items and business services.

Accurate risk management for smooth change management

Changes deployments and implementations pose a significant risk for IT organizations. Unmanaged changes may negatively impact the business. CMDB helps change managers anticipate which configuration items, including employees, systems, software, and business processes, would be affected by an upcoming change, minimize the risk of business disruption, and implement the change smoothly, without service outages.

Integrated data from multiple sources

When information about IT assets is siloed across many different sources, such as spreadsheets, reports, or external databases, it is prone to duplicates and hard to use, especially without understanding its connections with other data about the IT infrastructure. A CMDB can aggregate data from multiple sources into one central repository, mapping each configuration item to other items and services to provide a big picture of the IT infrastructure.

Source of knowledge for continuous process improvement

Since a CMDB contains data on each configuration item, including their change history and relationships with other CIs, the CMDB feeds into the Knowledge Management process to provide insight into how to manage and deploy IT infrastructure components in the most efficient way. Knowledge Management reduces the need to rediscover knowledge, helping IT companies to achieve continuous, data-driven process improvement.

Source of facts for effective incident management

Teams can use the CMDB to track incidents connected to the relevant configuration items whose services they affect. As soon as such an incident ticket is received, the IT operator can immediately access the corresponding CI record in the CMDB and learn everything about the item, including any previous issues of similar incidents. This information feeds directly into the knowledge base, leading to faster incident resolution and a better understanding of which CIs are more costly to support.

Source of information for effective problem management

CMDB helps IT teams identify which classes of assets are problematic and substitute them in time to avoid more incidents in the future. Keeping track of how incidents and problems connect to configuration items allows for easier root-cause analysis, helping discover the source of known issues and find solutions.
Besides the obvious benefits, there are some problems with CMDB implementation. According to Gartner only 25% of companies get value from their CMDB installation.

A configuration management database (CMDB) is an ITIL term for a database used by an organization to store information about hardware and software assets (commonly referred to as configuration items). It is useful to break down configuration items into logical layers.[1] This database acts as a data warehouse for the organization and also stores information regarding the relationships among its assets.[2] The CMDB provides a means of understanding the organization's critical assets and their relationships, such as information systems, upstream sources or dependencies of assets, and the downstream targets of assets.[3]

Purpose and benefits[edit]

The CMDB is a fundamental component of ITIL framework's Configuration Management process. CMDBs are used to keep track of the state of assets such as products, systems, software, facilities, people as they exist at specific points in time, and the relationship between all assets. A CMDB helps an organization understand the relationship between the components of a system and to track their configurations. The maintenance of this information allows for certain actions, such as the reconstruction of assets, to occur at any point in time. CMDBs can also be used for things like impact analysis, root cause analysis, or change management.

CMDB implementations often involve federation – the inclusion of data into the CMDB from other sources – such as asset management, in such a way that the source of the data retains control of the data. Federation is usually distinguished from ETL (extract, transform, load) solutions in which data is copied into the CMDB.

CMDBs can be used for many things, including but not limited to: business intelligence, software and hardware builds, inventory,[4] impact analysis for change management,[5] and incident management.

In the context of ITIL, the use of CMDBs is as part of infrastructure operations and support. The CMDB represents the authorized configuration of the significant components of the IT environment.

Contents[edit]

The CMDB contains and records data that are also called configuration items (CI). It also provides details about the important attributes of CIs and the relationships between them.

CI attributes and data[edit]

Attributes captured by a CMDB vary based on CI category, and can number up to the hundreds. Some examples include:

  • CI Unique Identifier or Identification Code
  • CI Name or Label (often, both long names and short names)
  • CI Abbreviations or Acronyms
  • CI Description
  • CI Ownership (organizations and people)
  • CI Importance

Because attributes are defined by metadata, CMDBs also contain metadata, and thus the concept overlaps with that of a metadata repository, which is also used to more effectively run IT organizations. Configuration management addresses how the data is to be kept up to date. This has historically been a weakness of metadata repositories.

Relationships between CIs[edit]

At a minimum, relationships are often composed of a Source CI that is related to a Target CI. In the case of more advanced relationships, such as semantic relationships, it is desirable to have a descriptor between the Source CI and Target CI that helps provide context. For example, "database" is related as a "Component" of "Application Y". The descriptor is also known as a Predicate.

Configuration item types[edit]

A configuration item type (or CI type) is the data type of the element or configuration item an enterprise wishes to store within the CMDB. At a minimum, all software, hardware, network, and storage CI types are stored and tracked in a CMDB. As enterprises mature, they start to track business CI types in their CMDB, such as people, markets, products, and 3rd party entities such as vendors and partners. This allows the relationships between CIs to become more meaningful and the CMDB to become a stronger source for knowledge management.

CI types are:

  • Hardware
  • Software
  • Communications/Networks
  • Location
  • Documentation
  • People (staff and contractors)

A key success factor in implementing a CMDB is the ability to automatically discover information about the CIs (auto-discovery) and track changes as they happen.

Schematic representations[edit]

CMDB schematic structures, also known as database schemas, take on multiple forms. Two of the most common forms are those of a relational data model and a semantic data model.

Relational data models are based on first-order predicate logic and all data is represented in terms of tuples that are grouped into relations. In the relational model, related records are linked together with a "key", where the key is unique to an entry's data type definition. Such relational models provide declarative methods for specifying data and queries. In other words, users directly state what information the database contains and what information they want from it, and let the database system take care of describing data structures for storing the data and retrieval procedures for answering queries.

Semantic data models typically rely on the resource description framework that maps the relation between a number of things through the use of relationship descriptors, giving context to how things are related to each other.

Challenges[edit]

There are three specific core challenges to creating and maintaining a Configuration Management Database:

  • Relevance: Collecting data throughout each record's or CI's life cycle is necessary. This means putting in processes and tools to collect the most recent changes to data as they occur.
  • Maintenance: Companies face constant change. Data about CIs and the relationships between them are constantly changing. This maintenance is a significant undertaking that is often not planned for or expected. Organisations often find this the greatest challenge.
  • Usability: Most CMDBs are just databases. This means they have no traits, features, or benefits of more complex applications. They lack tools to view data via complex visualizations or tools for advanced discovery. This means that most companies need to invest in an application layer that adds such constructs to their CMDB, which adds a layer of complexity and cost that most companies do not plan for or expect. However, implementing features that ensure the database is up to date or allow it to interact with systems to run commands, apply updates, or deploy new applications extends the functionality and usefulness of the CMDB.

Because of the above reasons, companies usually choose to purchase their CMDBs, rather than designing, building, delivering, and supporting them themselves.

See also[edit]

  • DMTF (CMDBf[6])
  • ITIL

References[edit]

  1. ^ "Configuration items layers".
  2. ^ "What is CMDB (configuration management database)?". TechTarget. July 2017. Retrieved 2019-01-14.
  3. ^ "IT: disconnected from the business?". Axios Systems. 2015-11-10. Retrieved 2019-01-14.
  4. ^ "Whitepaper: Ansible in Depth". Ansible (software). Retrieved 2019-01-14. There are many points of integration that can be used to extend Ansible, including: (...) inventory data retrieved from CMDB systems or cloud sources.
  5. ^ Sauvé, Jacques; Rebouças, Rodrigo; Moura, Antão; Bartolini, Claudio; Boulmakoul, Abdel; Trastour, David (2006). Business-Driven Decision Support for Change Management: Planning and Scheduling of Changes. Springer Berlin Heidelberg. pp. 173–184. doi:10.1007/11907466_15. ISBN 978-3-540-47662-7.
  6. ^ "CMDBf | DMTF". www.dmtf.org. Retrieved 2021-04-21.

  • Collins: Infrastructure management for engineers
  • Guide to CMDB solution design

What component will typically store the instance of all organizational configuration items?

Explanation: Answer option C is correct. The Definitive Media Library (DML) is a secure store that contains the definitive and authorized versions of all software configuration items. It may also contain associated configuration items such as licenses and documentation.

What is there stored in CMDB?

The CMDB is the ServiceNow database that stores information about all technical services. Within the CMDB, the support information for each service offering is stored in a Configuration Item (CI) specific to that service.

Which type of tool is used for configuration management?

Puppet Configuration Tool It is primarily used to configure, manage, and deploy various applications and services. Users can automate provisioning across their IT infrastructure and make rapid changes or mediate urgent issues alongside model-driven automation management.

What is a configuration item in configuration management?

Definition(s): Item or aggregation of hardware, software, or both, that is designated for configuration management and treated as a single entity in the configuration management process.