CMDB

What is CMDB?

A: A Configuration Management Database (CMDB) is a centralized repository used to store configuration information of IT assets and services in an organization. It is an essential part of IT Service Management (ITSM), providing a structured approach to managing IT environments.

What is the purpose of CMDB?

A: A CMDB provides a centralized database for managing and storing configuration data about IT assets and services, assisting organizations in tracking their configurations and relationships.

Is a CMDB recommended for ITIL?

A: Yes, a CMDB is highly recommended for organizations implementing ITIL as it improves the efficiency, control, and accuracy of service management in a structured manner.

What is the difference between Asset Management and CMDB?

A: The difference includes:

Asset Management	CMDB
Asset management involves the management of physical or virtual resources owned by an organization. Examples: Hardware, Software	A Configuration Management Database (CMDB) is a centralized repository used to store configuration information of IT assets and services in an organization.
It focuses on financial aspects like purchasing, depreciation, and cost tracking.	It focuses on the configurations and relationships between IT components.
It manages individual assets.	It includes data on how assets interact and support IT services.
Assets, including hardware, software, and infrastructure, are valuable organizational resources that support and enable business operations.	A Configuration Item (CI) is any component within an IT environment (e.g., hardware, software, or services) that is tracked and managed through the Configuration Management Database (CMDB).

What challenges are associated with maintaining a CMDB?

A: Common challenges include:

• Data accuracy: Keeping the information up-to-date can be difficult if changes in the IT environment are not reflected in the CMDB.
• Complexity: Managing large amounts of data, especially in complex environments, requires careful planning and consistent processes.
• Tool integration: Ensuring smooth integration with other IT systems and processes is crucial for the effective functioning of the CMDB.

Do I need a separate license for CMDB?

A: Yes.

What is stored in the CMDB?

A: The CMDB (Configuration Management Database) stores detailed information about Configuration Items (CIs), which can include hardware, software, systems, and services used in an organization. It tracks configurations, relationships between CIs, and their dependencies. The CMDB also records associations with: critical business services, assets, departments, users, and other related data necessary for effectively managing IT services.

What types of assets or configuration items (CIs) are stored in a CMDB?

A: A CMDB can store various types of configuration items (CIs) such as:

• Hardware (servers, routers, workstations)
• Software (applications, operating systems)
• Network components
• Virtual machines
• Documentation (policies, configurations)
• Services and dependencies between components

Who are the key users?

A: Key users include those associated with service delivery and management, both within and outside the organization.

What is a discovery pattern?

A: A discovery pattern is a predefined or custom set of instructions that automatically scans the network to identify, classify, and collect detailed information about both configuration items (CIs) and assets within an organization’s IT environment.

What is the difference between the classification and discovery pattern?

A: Classification pattern identifies the attributes of the device like OS or kernel. A Discovery pattern uses the results of classification and, based on the set conditions, discovers the device as a CI or asset.

Can I create an Asset from CI and vice-versa?

A: Yes, using the Sync Rule feature, you can create an Asset from a CI and vice versa. For more details, refer to: Sync Rule

Can I map the CI status with Asset status? How?

A: Yes, the CI Asset Status Mapping feature allows you to link the asset and CI lifecycle status. When an asset moves through its life cycle (e.g., from procurement to being in use), it transitions into the CI lifecycle. For example, once an asset is "In Use," its status as a Configuration Item (CI) begins, where it can be marked as 'Operational' or 'Non-Operational'. As the asset continues its journey (e.g., undergoing maintenance or being retired), the CI status changes accordingly, ensuring both lifecycles are synchronized.

Can a CMDB be used for cloud infrastructure?

A Yes, modern CMDBs can track and manage both on-premise and cloud-based assets.

What are the various ways to create CI?

A You can add a CI in multiple ways:

• Discovery: You can create a CI via agent-based or agentless discovery.
• Manually: You can create a CI manually using the Create New > Add CI option from the portal.
• Sync Rule: You can create a CI based on the sync rule configured in the Asset type. This sync rule will execute based on the Workflow.

How do I manage Configuration Item (CI) Types in CMDB?

A: CI Types define the kind of Configuration Item added to the portal. You can manage predefined and custom CI types, including adding sub-CI types up to five levels deep. This feature also allows you to design CI forms, create sync rules to automate asset-CI synchronization, and define suggested relationships between CI types. For more details, refer to: CI Type

How do I manage Configuration Item (CI) Statuses in CMDB?

A: CI Status indicates the progress of CI tickets at each stage of their lifecycle. You can manage default and custom statuses, including adding, editing, re-ordering, and setting a default status. A key feature is the ability to map CI status values to asset statuses, ensuring synchronization between CIs and their associated assets. For more details, refer to: CI Status

How do I manage Configuration Item (CI) Groups in CMDB?

A: CI Groups allow you to categorize and organize Configuration Items into logical collections, enhancing searchability and technician workflow. You can create, edit, and delete CI groups, assign owners, add notification emails, and associate CIs with specific groups from the CI list or details page. For more details, refer to to: CI Group

How do I implement custom rules for Configuration Items (CIs) in CMDB?

A: CI Custom Rules allow you to enforce organizational compliance and control changes to CI attributes. These rules ensure that any modifications to CI components, such as hardware or software, are supported by appropriate comments or require approval, enhancing data integrity and security. For more details, refer to: CI Custom Rules