Kunalhasija CMDB & ITIL

2,195 views

Published on

Presentation on ITIL , CMDB , created by me and material taken from various inputs

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,195
On SlideShare
0
From Embeds
0
Number of Embeds
32
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Kunalhasija CMDB & ITIL

  1. 1. Why You Need a Configuration Management Database: Where ITIL ® Fits In Kunal Hasija
  2. 2. Agenda <ul><li>ITIL and the goals for a Configuration Management Database (CMDB) </li></ul><ul><li>It’s all about relationships </li></ul><ul><li>Key CMDB concepts </li></ul><ul><li>Takeaways </li></ul>
  3. 3. The CMDB – What is it? -ITIL Defined- A database that contains all relevant details of each configuration item (CI) and details of the important relationships between configuration items
  4. 4. What is a Configuration Item - (CI)? -ITIL Defined- A component of an infrastructure that is (or is to be) under the control of Configuration Management. CIs may vary widely in complexity, size, and type – from an entire system to a single module
  5. 5. What’s in a CMDB? <ul><li>Configuration items are in a CMDB and they have relationships </li></ul><ul><ul><li>Capture, record, provide status, urgency and the impact of data between CIs </li></ul></ul><ul><ul><li>Information about relationships and their components are captured as CI records </li></ul></ul><ul><ul><li>Ensure IT applications and people are working off of a single “source of record” across your organization </li></ul></ul>
  6. 6. ITIL and the Goal of a Configuration Management Database (CMDB) <ul><li>Account for all the IT assets and configurations within the organization and its services </li></ul><ul><li>Provide accurate information on configurations and their documentation to support all the other Service Management processes </li></ul><ul><li>Provide a sound basis for Incident Management, Problem Management, Change Management and Release Management </li></ul><ul><li>Provide verification of the configuration records against the infrastructure and correct any exceptions </li></ul>
  7. 7. Benefits of Configuration Management <ul><li>Control – Verifying and correcting configuration records gives you a greater degree of control over your infrastructure </li></ul><ul><li>Integration – Integrating all configuration-related IT processes can reduce errors and the number of staff needed to administer your environment </li></ul><ul><li>Decision Support – Making decisions and meeting commitments is easier when you have complete and accurate data, resulting in better resource and performance estimates </li></ul>
  8. 8. It’s the Relationships that Count
  9. 9. ITIL Disciplines and the CMDB
  10. 10. Relationships – Incident Management <ul><li>Automatically populate records </li></ul><ul><li>Provide status of configuration items </li></ul><ul><li>Provide urgency data for priorities </li></ul><ul><li>Provide impact data for priorities </li></ul><ul><li>Provide escalation data </li></ul>
  11. 11. Relationships – Problem Management <ul><li>Automatically populate problem records </li></ul><ul><li>Provide status of configuration items </li></ul><ul><li>Provide risk analysis data for priorities </li></ul><ul><li>Provide ownership data </li></ul><ul><li>Provide data for proactive problem analysis </li></ul>
  12. 12. Relationships – Change Management <ul><li>Show CIs that are in the Change Management process </li></ul><ul><li>Provide risk analysis data </li></ul><ul><li>Show which other components could be affected by a change </li></ul><ul><li>Provide feedback data about customers for changes </li></ul><ul><li>Reflect the new status immediately after a change </li></ul>
  13. 13. Relationships – Release Management <ul><li>Track rollout status </li></ul><ul><li>Keep version details for software </li></ul><ul><li>Provide vital planning data for rollouts </li></ul><ul><li>Provide feedback data about customers for rollouts </li></ul><ul><li>Provide data for financial impact of releases </li></ul>
  14. 14. Relationships – Service Desk <ul><li>Identify CMDB errors </li></ul><ul><li>Use CMDB to record incidents </li></ul><ul><li>Provide proactive notification to the users </li></ul><ul><li>Provide feedback to customers about CMDB changes </li></ul><ul><li>Assist Configuration Management with CMDB audits </li></ul>
  15. 15. Relationships – Service Level Management <ul><li>All SLA components must be in the CMDB </li></ul><ul><li>SLAs can be referenced from CMDB </li></ul><ul><li>Provide underpinning contracts reference point </li></ul><ul><li>Show customer ownership </li></ul><ul><li>CMDB is a vital component for the Service Improvement Program </li></ul>
  16. 16. Data is the Key <ul><li>No matter which service management processes you implement, the data they use will make them effective </li></ul><ul><ul><li>Your configuration data must be accurate, which means it must be updated frequently </li></ul></ul><ul><ul><li>Configurations are constantly changing, so last week’s correct data could be horribly obsolete this week </li></ul></ul><ul><ul><li>Your configuration data must also be available to all of your IT processes, because even the most accurate data is useless if you can’t get to it </li></ul></ul>
  17. 17. Recommended CMDB Approach - Federated <ul><li>Benefits: </li></ul><ul><li>The CMDB can focus its functionality on CIs and their relationships </li></ul><ul><li>The overhead required to provide this functionality is not wasted on data that doesn’t need it </li></ul><ul><li>You don’t have to modify the </li></ul><ul><li>CMDB to hold related data </li></ul><ul><li>You don’t need to undertake several data migrations and integrations </li></ul>
  18. 18. Understanding a Federated CMDB Model <ul><li>Relationships between CIs </li></ul><ul><ul><li>Relationships make the CMDB a powerful decision support tool </li></ul></ul><ul><ul><li>Relationships allow you to understand the dependencies among CIs </li></ul></ul><ul><li>Related Data </li></ul><ul><ul><li>Includes information related to CIs, such as help desk tickets, change events, contracts, Service Level Agreements (SLAs) </li></ul></ul><ul><ul><li>Contains information about your CIs and forms an important part of your IT infrastructure </li></ul></ul>
  19. 19. Key Takeaways <ul><li>Relationships between CIs bring it all together </li></ul><ul><li>CMDB provides a single source of record that can be leveraged by all IT processes </li></ul><ul><li>Configuration Management provides better control, integration and decision support across your organization </li></ul><ul><li>It is critical to ensure the CMDB always provides accurate information about your infrastructure </li></ul><ul><li>A federated CMDB creates an approach that is scalable and maintainable </li></ul>
  20. 20. Thank You <ul><li>Kunal Hasija, Configuration Team Lead </li></ul>

×