Service View CMDB
There are many reasons why organizations invest in a Service View CMDB (Configuration Management Database). You may want a consolidated view of configuration data mapped to your applications and business services to support ITIL processes like incident, problem, and change management. You may be seeking to leverage a Service View CMDB to support compliance activities, asset management, data center consolidation, enterprise architecture planning, or a number of other project areas.
Regardless of the reasons why you are interested in a Service View CMDB, you have probably heard stories about how they can be difficult to implement and maintain (you may have even experienced this directly yourself).
Getting a working Service View CMDB up and running doesn’t need to be a painful, many month project. And maintaining it doesn’t need to be an effort done by a dedicated team of specialists or a burden on IT staff.
Shortcomings of traditional Service View CMDBs
You can’t get everything you need from a discovery tool. Many CMDB vendors will tell you that hitching your CMDB to a discovery tool is all you need to ensure a complete and accurate CMDB, but there are many configuration settings that discovery tools just can’t discover. What’s more, it takes the experts in your organization to understand and flag which settings are critical to service delivery.
The standard CMDB data model supports configuration data only. When planning changes, resolving incidents, or any of the other reasons for a CMDB, you often need additional information like policy relationships, fragile settings, and best practices to make the best decisions. Other CMDB solutions don’t provide these capabilities without extensive customization (if they can even support them at all).
Traditional CMDBs force users to consume information based on a single defined hierarchy of service dependency relationships. ITinvolve supports global service dependency views that everyone can share as well as personalized views based on roles and functions. In this way, people are able to consume CMDB information based on what matters to them and that means your CMDB will be used.
“We looked at some of the big vendor CMDB packages but they were overkill and would have required additional resources just to keep them up to date.”
Director of Strategic Initiatives
- Leverage the configuration data you already have (from discovery tools, asset management, spreadsheets, an existing CMDB, etc.)
- Bring that information together and visualize it in one place (importing or federating the details as necessary)
- Leverage modern social collaboration capabilities so experts can follow and peer review the existing data (so it’s validated and becomes trusted)
- Have experts fill in the gaps in existing data with the undocumented tribal knowledge only they know (make it easy for them to do so with familiar social collaboration techniques)
- Visually model relationships and dependencies between infrastructure, applications, and business services (based on roles and what’s important to staff so it’s meaningful and useful)
Make your Service View CMDB self-sustaining:
- Connect your change process to ensure approved updates are reflected in the CMDB
- Tie in discovery sources to validate changes were executed as planned and to capture out-of-band configuration changes
- Empower staff to correct information or fill in gaps easily, in real-time as part of daily work like change planning, incident resolution, etc.
Many of our clients have an existing CMDB (or two or more) yet struggle to achieve a consolidated and trusted Service View. ITinvolve works with existing CMDBs to consolidate configuration management data across disparate sources, and provides the visualization and collaborative approach necessary to establish a living, working CMDB for your organization.
We can even work with existing CMDBs bi-directionally, so their accuracy and completeness is enhanced.
If you identify with this situation, we’d like you to know that you can speed up your process and ensure a more accurate risk assessment that avoids many (or even eliminates) unexpected consequences.