CMDB in the NOC: Voices from the trenches
EMA on Management
By
Dennis Drogseth
,
Network World
, 04/21/2008
- Share/Email
- Tweet This
- Print
In my last column, I described the growing evidence that CMDB Systems (as in ITIL v3’s Configuration Management System) are beginning to support network
operations teams as well as more traditional service desk and data center adopters. I made the analogy between the CMDB Systems
of the present and future, and the NOC War Room single pane of glass – as IT organizations evolve to combine change management
control with performance management and service assurance. This would enable IT to manage processes for reconfiguring critical
network and systems devices while providing good dynamic visibility into actual configuration changes, service performance
and service impact.
Once you see CMDB Systems in that light, it’s easier to make the bridge to the so-called War Room.
And given that premise, here are a few “voices from the trenches” taken from consulting and research over the last two years,
including right up into the present.
One of the most compelling testimonies is in fact two years old, as an infrastructure-wide deployment, including network management,
consolidated monitoring tools and health desk capabilities in a large financial services organization that charged for its
IT support to multiple financial services companies:
“Our CMDB was an attempt to achieve world-class availability and at the same time control costs. With a $1 million in downtime
for our whole ecosystem, and supporting 6,000 transactions a second, we reduced MTTR [mean time to recovery] by 70% through
the CMDB initiative.”
In this case, data was accessed based on carefully defined “trusted sources” so that conflicting views of the same device
or device attribute weren’t guaranteed to lead to a finger-pointing exercise. Consistent sources enabled better dialog and
collaboration in resolving cross-domain issues. And the biggest challenge was, as usual, not technological but political.
Another voice from the trenches comes from an management service provider with responsibility for managing network and other
devices across multiple organizations:
“Over the past three years, we’ve tied the CMDB in the change process, and then made sure that it would be supportive of our
financial processes and financial systems. Over the course of the last three years we successfully disputed $2.5 million out
of a $9 million spend.”
Partner Content
Blue Stripe Software
www.bluestripe.com/
Improving Application Performance Troubleshooting
Diagnosing why an application is slow is hard, at times taking days or weeks to isolate and resolve. This paper explains the challenges involved using current management tools, provides a 'wish list' for application management and analysis, and explains the need for an application system-wide approach that monitors entire applications, not components.
Download Whitepaper
Virtual Vigilance: Managing Application Performance in Virtual Environments
This paper highlights the impact of virtualization on application performance. "Managing Application Performance in Virtual Environments" states: "Best-in-Class organizations are predominately taking actions around improving visibility across both physical and virtual systems, assessing the business impact of application performance and understanding interdependencies of applications in virtualized environments."
Download Whitepaper
Application Service Requests: The Missing Link for Pragmatic ITSM
Forrester Research analyst Glenn O'Donnell and BlueStripe co-founder Vic Nyman discuss a breakthrough approach to application problem management. Learn the new approach for ITSM problem management, which provides: Rapid isolation of application slow-downs to specific components for quick problem resolution, 24/7 monitoring for proactive notification of potential issues before end users are impacted and much more.
Register for Webcast
Comments (1)
Maturity in the NOC compared to other IT silosBy ronaldxbartels on April 21, 2008, 3:25 pmDennis, your follow up article is different to the first one. In the first article I was amused that you assumed NOC workers to be bumpkins and cowboys, so it was...
Reply | Read entire comment
View all comments