Effectively Planning for an Enterprise-Scale CMDB Implementation

6,603 views

Published on

Provies a review of why a CMDB is essential to and is the foundation of your BSM strategy. I also outline the known challenges that require planning at the outset of a CMDB initiative. Includes a case study which details the approach and lessons learned in the initial stages of a CMDB rollout for one of the largest financial institutions in North America

1 Comment
2 Likes
Statistics
Notes
  • please send me this file.. cuz i can't download it.
    thanks so much..
    regards,
    chi2_ha2@yahoo.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
6,603
On SlideShare
0
From Embeds
0
Number of Embeds
34
Actions
Shares
0
Downloads
259
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

Effectively Planning for an Enterprise-Scale CMDB Implementation

  1. 1. Case Study: Effectively Planning for an Enterprise-Scale CMDB Implementation <br />Antonio Rolle<br />VP of Professional Services<br />
  2. 2. Objectives<br />Review why a CMDB is essential to and is the foundation of your BSM strategy<br />Outline the known challenges that require planning at the outset of a CMDB initiative<br />Drill down into the approach and lessons learned in the initial stages of a CMDB rollout for one of the largest financial institutions in North America<br />
  3. 3. Agenda<br />Brief Review: The CMDB<br />Known Pitfalls in CMDB Deployments<br />Case Study: Leading Financial Services Enterprise<br />
  4. 4. Brief Review: The CMDB<br />
  5. 5. The Configuration Management Database (CMDB) is at the heart of aligning business with IT.<br />
  6. 6. “<br />”<br />The CMDB should -<br />... (1.) Hold the (a.)relationships between all system components, including incidents, problems, known errors, changes and releases… (b.)information about incidents, known errors and problems, and corporate data about employees, locations and business units... often… (c.)details of servicesand to (2.) relate them to the underlying IT components…and (3.) store inventory details… such as suppliers, cost, purchase date, and renewal date for a license..<br />SOURCE:Office of Government Commerce<br />
  7. 7. “<br />”<br />The CMDB should -<br />... (1.) Hold the (a.)relationships between all system components, including incidents, problems, known errors, changes and releases… (b.)information about incidents, known errors and problems, and corporate data about employees, locations and business units... often… (c.)details of services and to(2.)relate them to the underlying IT components…and (3.) store inventory details… such as suppliers, cost, purchase date, and renewal date for a license..<br />SOURCE:Office of Government Commerce<br />
  8. 8. “<br />”<br />The CMDB should -<br />... (1.) Hold the (a.)relationships between all system components, including incidents, problems, known errors, changes and releases… (b.)information about incidents, known errors and problems, and corporate data about employees, locations and business units... often… (c.)details of services and to (2.) relate them to the underlying IT components…and(3.) store inventory details… such as suppliers, cost, purchase date, and renewal date for a license..<br />SOURCE:Office of Government Commerce<br />
  9. 9. “<br />”<br />The CMDB should -<br />... (1.) Hold the (a.)relationships between all system components, including incidents, problems, known errors, changes and releases… (b.)information about incidents, known errors and problems, and corporate data about employees, locations and business units... often… (c.)details of services and to (2.)relate them to the underlying IT components…and (3.) store inventory details… such as suppliers, cost, purchase date, and renewal date for a license..<br />SOURCE:Office of Government Commerce<br />
  10. 10. Why use a CMDB to do this?<br />1. Control<br />2. Integration<br />3. Decision Support<br />
  11. 11. Reality Check<br />External Factors are Driving our Clients to a CMDB-centric Service Management Architecture<br />Software Providers Are Moving to a CMDB-centric Software Architecture- You Will Soon Have a CMDB Platform, probably more than 1<br />IT “Supply Chain” Efficiency Requirements<br />This is not a Process & Tool initiative, it’s an enterprise wide shift<br />
  12. 12. Known Pitfalls in CMDB Deployments<br />
  13. 13. “<br />”<br />Understanding the relationship between ITIL, IT asset management, and CMDB management will help IT construct and align infrastructure services to business needs.<br />Thomas Mendel, PhD - Forrester Research<br />
  14. 14. 5 Common Questions<br />How wide and how deep should the CMDB be?<br />How should I define a configuration item?<br />How do I decide if I need to federate information? <br />If I do federate, how do I integrate? <br />What is the first step I need to take?<br />
  15. 15. The Big Question<br /> What level of effort and resources will be involved with implementing a CMDB in terms of: <br /> People?<br /> Processes?<br /> Technology?<br />
  16. 16. Common CMDB Implementation Pitfalls<br />Unclear business focus<br />Unrealistic expectations<br />An all-or-nothing approach<br />Running the implementation as an IT project<br />Improper balance between strategic efforts and short-term wins<br />Treating implementation as a one-time project<br />Lack of organizational commitment<br />
  17. 17. Stages in the Building Process<br />Assemble the Project Team & Define the Project<br />Define Requirements & Create IT Service Model Blueprint<br />Select CMDB Solution and Tools<br />Construct & Maintain the CMDB<br />Drive Ongoing Value<br />
  18. 18. Stages in the Building Process<br />Assemble the Project Team & Define the Project<br />Define Requirements & Create IT Service Model Blueprint<br />Select CMDB Solution and Tools<br />Construct & Maintain the CMDB<br />Drive Ongoing Value<br />
  19. 19. Case Study: Leading Financial Services <br />Enterprise<br />
  20. 20. Case Study<br /><ul><li>Company Profile:
  21. 21. Fortune 100 Banking Institution
  22. 22. Over 20 million individual, business and institutional clients served at more than 6,000 retail branches
  23. 23. Reported more than $440 billion in assets managedand administered
  24. 24. 150,000+ employees
  25. 25. Environment:
  26. 26. Remedy Asset Management v5.5
  27. 27. 13+ Remedy Developers
  28. 28. Over 20 Federated Data Sources</li></li></ul><li>Stage 1: Assemble the Project Team & Define the Project<br />Create Project Executive Board<br />Select Project Manager<br />Scope Key Activities<br />Select Project Team<br />Finalize Project Plan<br />
  29. 29. Stage 3: Select CMDB Solution and Tools<br />Select CMDB Solution<br />Plan the CMDB Population<br />Select Tools to Automate CMDB Solution<br />Calculate Project ROI<br />
  30. 30. Stage 3: Select CMDB Solution and Tools<br />Select CMDB Solution<br />Plan the CMDB Population<br />Select Tools to Automate CMDB Population<br />Calculate Project ROI<br />
  31. 31. Stage 1: Assemble the Project Team & Re-Define the Project<br />Create Project Executive Board<br />Select Project Manager<br />Scope Key Activities<br />Select Project Team<br />Finalize Project Plan<br />Our clients like to bring us in as a neutral party when projects cross functional lines<br />
  32. 32. Defining the Activities is Easy…<br />… Building the timelines is a different challenge.<br />You have to get fairly deep, both functionally and technically to accurately establish timelines: build in plenty of time to deal with unknowns<br />Don’t underestimate how badly your timelines can get hosed if you don’t closely gauge (and manage) personnel availability<br />
  33. 33. Internal Resources<br />Your stakeholder list will be larger than you thought possible(!)<br />Obtaining the Information you need and the consensus required is half the battle<br />
  34. 34. External Resources<br />Consider bringing in a firm to partner with you if… <br />You can’t dedicate the right resources to the project<br />You think an outside party might be able to navigate the functional areas more effectively <br />
  35. 35. Stage 2: Defining CMDB Requirements<br />Identify & Review Governance Requirements<br />Review and Select Supporting Best Practices<br />Identify Requirements to Address Potential Problems<br />Identify Inventory & Asset Management Requirements<br />Define Service Catalog Requirements <br />Define CMDB Requirements to Support Other Processes<br />Define CI Level & IT Service Model<br />Define CI Relationships<br />Define CI Attributes<br />Design IT Service Model Blueprint<br />
  36. 36. Identify & Review Governance Requirements<br />Identify Key Governance & Regulatory Stakeholders (SOx, Gramm-Leach-Bliley, FFIEC, Internal/External Auditors)<br />Scope Potential Use of a CMDB (Identify CI’s, Relationships, Fixed Asset Register)<br />Collect and Document Requirements<br />Get Approvals<br />
  37. 37. Review and Select Supporting Best Practices<br />Research Relevant Best Practice Frameworks<br />Select Appropriate Best Practice Frameworks<br />Document Best Practices<br />Check Current Levels of Adherence<br />Publish and Distribute Best Practices<br />
  38. 38. Identify Requirements to Address Potential Problems<br />Review Knowledge Sources<br />Document Potential Problems<br />Identify Root Causes<br />Identify Potential Solutions<br />Document Project Requirements<br />
  39. 39. Identify Inventory & Asset Management Requirements<br />Determine Asset Definition<br />List Asset Categories<br />Identify Owners of Listed Assets<br />Identify Data Inventory Data Requirements<br />Identify Asset Data Requirements<br />Compile Inventory Asset Requirements<br />
  40. 40. Drill Down - Inventory and Asset<br />This project was driven by the Asset Management process area with a focus on:<br />Identification<br />Control<br />Verification & Audit<br />
  41. 41. Define Service Catalog Requirements<br />Identify Key Service Catalog Stakeholders<br />Scope Service Catalog CMDB Use<br />Collect & Document Requirements<br />Publish Approved CMDB Requirements<br />
  42. 42. Define Service Catalog Requirements<br />Identify Key Service Catalog Stakeholders<br />Scope Service Catalog CMDB Use<br />Collect & Document Requirements<br />Publish Approved CMDB Requirements<br />
  43. 43. Define CMDB Requirements to Support Other Processes<br />Identify Stakeholders<br />Discover & Distill Requirements to Support Other Processes<br />Review and Agree on CMDB Requirements to Support Other Processes<br />Publish CMDB Requirements<br />
  44. 44. Drill Down - Process Integration<br />Incident & Problem Management<br />Change Management<br />Asset Management<br />Service Continuity Management<br />20 Federated Data Sources<br />
  45. 45. Define CI Level & IT Service Model<br />Establish Working Group<br />Create A Straw Model Structure<br />Validate Straw Model Structure<br />Document the Structure, Guidelines & Criteria<br />
  46. 46. BMC Atrium CMDB 2.0- Common Data Model<br />
  47. 47. Define CI Relationships<br />Define CI Relationship Types<br />Review & Agree<br />Document Relationship Design<br />
  48. 48. Define CI Attributes<br />Consider Management & Maintenance<br />Review<br />Document<br />
  49. 49. Design IT Service Model Blueprint<br />Document & Validate Blueprint<br />Define Governance, Roles & Procedures<br />Review<br />Publish<br />
  50. 50. Stage 3: Select CMDB Solution and Tools<br />Select CMDB Solution<br />Plan the CMDB Population<br />Select Tools to Automate CMDB Population<br />Calculate Project ROI<br />
  51. 51. Stages in the Building Process<br />Assemble the Project Team & Define the Project<br />Define Requirements & Create IT Service Model Blueprint<br />Select CMDB Solution and Tools<br />Construct & Maintain the CMDB<br />Drive Ongoing Value<br />
  52. 52. Timeline<br />
  53. 53. Lessons Learned<br />Internal & External Perspectivesare Required for Success<br />Large Organizations Are Slow to Adopt Change<br />Project Team Knowledge of ITIL Required<br />Continued Sponsor Engagement is Critical<br />
  54. 54. Next Steps<br />Identify Change Agents, Advocates, Sponsor and potential project team.<br />Identify risks and mitigation plans.<br />Register as a project.<br />Draft CMDB goals/objectives and link to organizational goals.<br />Evaluate process maturity to determine which processes would be affected.<br />Finalize the Service Catalog, formally or informally.<br />Read Malcolm Fry’s book, “Step-by-Step Guide to Building a CMDB”…and other resources.<br />
  55. 55. Discussion <br />Antonio Rolleantonio.rolle@generationetech.comhttp://www.generationETech.com<br />

×