CMDB/CMS Use Cases: Change Management and Change Impact Analysis

Change Management and Change Impact Analysis are at the very heart of the CMDB/CMS value set. This includes change management for impact analysis of changes to Configuration Items (CIs) and their associated services, as well as change automation for activating changes (release) management. Many vendors favored one over the other, although Value Leaders did well in both. This category in the radar also included capacity planning and infrastructure optimization in support of service delivery -- an area often requested but until recently not largely supported through CMDB/CMS initiatives.

Other use cases for change management include:

Governance and Compliance: Managing change to support security-related, industry-related and other compliance-driven audits can be even more costly and labor intensive than asset-specific audits. One of EMA’s consulting clients estimates that a CMDB in hindsight could have saved them nearly $5 million in consulting costs.

Service Availability and Performance: EMA estimates that roughly 60% of IT service disruptions come from the impacts of planned or unplanned changes across the application infrastructure.

Data Center Consolidation: With the rise of virtualization in the data center, planning new options for data center consolidation is definitely on the uptake. Mergers and acquisitions can also factor in as a driver for data center consolidation.

Disaster Recovery: Automating change in case of disaster is one of the more pervasive drivers for CMDB/CMS initiatives.

Facilities management and Green IT: Extending the role of IT governance to areas external to traditional IT boundaries (facilities, power, etc.) requires core capabilities for capturing CMS-related interdependencies and exploiting the "logical and physical" extensions of CMS modeling.

Support for Provisioning New Application Services: This can include cloud-related service provisioning potentially via service catalogs and blueprints, as well as more traditionally developed (in-house developed) applications. The CMDB/CMS role in supporting Dev Ops is just now beginning to take on new life -- although it’s not brand new. I’ve seen examples of this use case going back as many as five years.


Figure 3: Change Management and Change Impact Analysis pose a greater foundational set of insights into interdependencies, and so application dependency mapping, configuration, asset management and capacity management are all in black. In many respects, it’s the heart of what CMDB/CMS capabilities are all about.

The following vendors were Value Leaders in EMA’s CMDB/CMS radar:

Axios

Axios received the highest overall score in the radar for Change Management. Among the things that stood out most about assyst were its strong support for third-party integration in discovery combined with a staging area; and its proven integrations with third-party application dependency mapping solutions for service impact analysis -- including those from VMware, BMC, and IBM. Axios also won an award as “Most Balanced CMDB/CMS functionality” across all three use cases.

N(i)2

N(i)2 lead dramatically in Architecture and Integration and Functionality, and was also significantly ahead of average in Deployment and Administration. One way to get a feel for N(i)2’s unique depth are the change management histories it keeps beyond traditional IT technology boundaries—such as: slot occupancy in chassis; rack mounting position, power management, WAN circuit, etc. Although it is highly applicable to enterprises, N(i)2 remains best understood to date by service providers. N(i)2 also won the award for “Most Innovative CMDB/CMS Deployment.”

Numara

Numara FootPrints scored well above the average in Change Management, leading in Cost Advantage, Administration and Deployment, with scores just slightly under in Functionality and Architecture and Integration. According to Numara, Change Management is its fastest ROI and this was borne out by customer interviews as well. However, it should be pointed out that across the broader FootPrints family, change management and lifecycle asset management are so closely intertwined.

ServiceNow

ServiceNow significantly outperformed the vendor average in all areas. It received best overall score in Deployment and Administration, in the top third for Cost Advantage. It was also well in the top half for Architecture and Integration, and in the top third for functionality. This shouldn’t be surprising given its rich automation capabilities (IT Process Automation or runbook plus workflow) combined with its Service-now Discovery and Dependency Mapping. As you may have noticed, this is the second time ServiceNow appears as a value leader.

SunView Software

SunView Software’s ChangeGear scored meaningfully above average in Deployment and Administration, Functionality, and Architecture and Integration. SunView was dramatically ahead in Change Management in Cost Advantage. And indeed, no vendor in EMA’s radar was more optimally tuned to address Change Management in mid-tier and mid-tier enterprise environments where administration and cost are strong counterweights to functionality and architecture.

Click here to read the CMDB/CMS use cases for Asset Management and Financial Optimization

Click here to read the CMDB/CMS use cases for Service Impact Management

Hot Topics

The Latest

Alert Fatigue Is No Longer a Morale Problem, It's a Reliability Risk and a System Failure

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

Most Enterprises Think They Can Switch AI Vendors in a Month ... Most Who've Tried Couldn't

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Your Observability Stack Has a Telemetry Pipeline Problem

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

Operator to Orchestrator: 80% of IT Pros See Shift in Role as AI Permeates Workflows

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

Gartner: 40% of Organizations Deploying AI Will Use AI Observability to Monitor Model Performance by 2028

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Almost Half of AI-Generated Code Fails in Production

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

AI Requires Design, Not Edicts

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

How Intelligent Orchestration Enables Enterprises to Move from AI POC to AI Production

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Reliability Is the New Bottleneck of Innovation

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

5 Takeaways from the Observability Forecast for Retail and eCommerce

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

CMDB/CMS Use Cases: Change Management and Change Impact Analysis

Change Management and Change Impact Analysis are at the very heart of the CMDB/CMS value set. This includes change management for impact analysis of changes to Configuration Items (CIs) and their associated services, as well as change automation for activating changes (release) management. Many vendors favored one over the other, although Value Leaders did well in both. This category in the radar also included capacity planning and infrastructure optimization in support of service delivery -- an area often requested but until recently not largely supported through CMDB/CMS initiatives.

Other use cases for change management include:

Governance and Compliance: Managing change to support security-related, industry-related and other compliance-driven audits can be even more costly and labor intensive than asset-specific audits. One of EMA’s consulting clients estimates that a CMDB in hindsight could have saved them nearly $5 million in consulting costs.

Service Availability and Performance: EMA estimates that roughly 60% of IT service disruptions come from the impacts of planned or unplanned changes across the application infrastructure.

Data Center Consolidation: With the rise of virtualization in the data center, planning new options for data center consolidation is definitely on the uptake. Mergers and acquisitions can also factor in as a driver for data center consolidation.

Disaster Recovery: Automating change in case of disaster is one of the more pervasive drivers for CMDB/CMS initiatives.

Facilities management and Green IT: Extending the role of IT governance to areas external to traditional IT boundaries (facilities, power, etc.) requires core capabilities for capturing CMS-related interdependencies and exploiting the "logical and physical" extensions of CMS modeling.

Support for Provisioning New Application Services: This can include cloud-related service provisioning potentially via service catalogs and blueprints, as well as more traditionally developed (in-house developed) applications. The CMDB/CMS role in supporting Dev Ops is just now beginning to take on new life -- although it’s not brand new. I’ve seen examples of this use case going back as many as five years.


Figure 3: Change Management and Change Impact Analysis pose a greater foundational set of insights into interdependencies, and so application dependency mapping, configuration, asset management and capacity management are all in black. In many respects, it’s the heart of what CMDB/CMS capabilities are all about.

The following vendors were Value Leaders in EMA’s CMDB/CMS radar:

Axios

Axios received the highest overall score in the radar for Change Management. Among the things that stood out most about assyst were its strong support for third-party integration in discovery combined with a staging area; and its proven integrations with third-party application dependency mapping solutions for service impact analysis -- including those from VMware, BMC, and IBM. Axios also won an award as “Most Balanced CMDB/CMS functionality” across all three use cases.

N(i)2

N(i)2 lead dramatically in Architecture and Integration and Functionality, and was also significantly ahead of average in Deployment and Administration. One way to get a feel for N(i)2’s unique depth are the change management histories it keeps beyond traditional IT technology boundaries—such as: slot occupancy in chassis; rack mounting position, power management, WAN circuit, etc. Although it is highly applicable to enterprises, N(i)2 remains best understood to date by service providers. N(i)2 also won the award for “Most Innovative CMDB/CMS Deployment.”

Numara

Numara FootPrints scored well above the average in Change Management, leading in Cost Advantage, Administration and Deployment, with scores just slightly under in Functionality and Architecture and Integration. According to Numara, Change Management is its fastest ROI and this was borne out by customer interviews as well. However, it should be pointed out that across the broader FootPrints family, change management and lifecycle asset management are so closely intertwined.

ServiceNow

ServiceNow significantly outperformed the vendor average in all areas. It received best overall score in Deployment and Administration, in the top third for Cost Advantage. It was also well in the top half for Architecture and Integration, and in the top third for functionality. This shouldn’t be surprising given its rich automation capabilities (IT Process Automation or runbook plus workflow) combined with its Service-now Discovery and Dependency Mapping. As you may have noticed, this is the second time ServiceNow appears as a value leader.

SunView Software

SunView Software’s ChangeGear scored meaningfully above average in Deployment and Administration, Functionality, and Architecture and Integration. SunView was dramatically ahead in Change Management in Cost Advantage. And indeed, no vendor in EMA’s radar was more optimally tuned to address Change Management in mid-tier and mid-tier enterprise environments where administration and cost are strong counterweights to functionality and architecture.

Click here to read the CMDB/CMS use cases for Asset Management and Financial Optimization

Click here to read the CMDB/CMS use cases for Service Impact Management

Hot Topics

The Latest

Alert Fatigue Is No Longer a Morale Problem, It's a Reliability Risk and a System Failure

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

Most Enterprises Think They Can Switch AI Vendors in a Month ... Most Who've Tried Couldn't

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Your Observability Stack Has a Telemetry Pipeline Problem

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

Operator to Orchestrator: 80% of IT Pros See Shift in Role as AI Permeates Workflows

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

Gartner: 40% of Organizations Deploying AI Will Use AI Observability to Monitor Model Performance by 2028

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Almost Half of AI-Generated Code Fails in Production

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

AI Requires Design, Not Edicts

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

How Intelligent Orchestration Enables Enterprises to Move from AI POC to AI Production

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Reliability Is the New Bottleneck of Innovation

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

5 Takeaways from the Observability Forecast for Retail and eCommerce

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...