Criticality

Updated on 16 May 2024
1 Minute to read

Article summary

Did you find this summary helpful?

Thank you for your feedback

Criticality refers to the degree of importance or significance of a configuration item (CI) within an organization's IT infrastructure or business processes.

By understanding the criticality of various components, organizations can make informed decisions about maintenance, upgrades, incident response, and disaster recovery.

Let's explore the following Use Case for configuring Criticality!

Use Case User persona:Application Designer	Solution
John, the app designer wants an element that ensures efficient management of IT incidents and minimizes downtime in IT infrastructure supporting servers, networking equipment, databases, applications, and user devices.	John can configure Criticality under CMDB configuration and categorize their CIs into different criticality levels based on their impact on business operations and services. He can define four levels: 'High', 'Medium', and 'Low'. Based on this, IT team can manage its software development and deployment processes more effectively, maintaining a balance between stability and innovation.

Configure Criticality

To configure Criticality, perform the following steps:

Select CMDB > Criticality.
Figure: Define Criticality
Configure the Criticality for CMDB.
Figure: Configuration screen
Specify the Tenant (ex: Information Technology), Criticality Name as Low, Medium or High, Sort Order as 1 or 2 or 3 and check the Active. The screenshot for field values under the Criticality is shown below.
Figure: Criticality
Click Save to submit the configuration. The configured list of Criticality appears as shown below.
Figure: Criticality list

Was this article helpful?

What's Next

Environment

Table of contents