Building a sustainable CMDB Alvin Deen 7 th June 2016
Agenda The Changing Landscape What is a CMDB vs CMS? Building a Sustainable CMDB
CMDB in the Changing Landscape Traditional IT Efficiently host workloads & services Provide hardened systems & networks Store and manage data Software automates business systems Digital Enterprise Continuously create & deliver new services Manage and mitigate risk Provide real-time insight & understanding Software differentiates products and services
The need for good Configuration Management Wrongdependencies Service dependency maps are often out of date. Too many outages Inaccurate configuration information causes change-induced outages. X Poor compliance Unplanned changes threaten IT services and audit compliance. Longresolution times Inaccurate configuration information slows IT problem resolution. Poor Resource Utilisation Limited visibility of usage and entitlement leads to inefficient purchasing decisions 60% 100% 80% 60% 40% 20% 0% of IT incidents are caused by change. 1 fewer bad changes at a major service provider 4 70% 50% reduction in emergency changes at Kellogg Company 3 50% of staff time freed for high-value activities at Qatar Telecom 4
What is the CMS?
Consumption Layer Strategy & Planning Enterprise Architecture Provisioning & Automation Monitoring & Compliance Incident Problem Change IT Asset Management Configuration Management Management Layer Hardware Asset Management Information Processing Layers Software Asset Management Modelling Reporting State Management Performance Management Query & Analysis Application & Dependency Discovery Data Integration Layer S/W & H/W Utilisation Data Providers Aggregation ITSM MDRs Discovery Inventory
Building a CMDB Four Core Principles
Four Core Principles for Building a CMDB 1. Depth & Breath Transform to a hybrid infrastructure Protect your digital enterprise Maximizing value from your apps and data Empower Enable the workplace data-driven organization productivity Empower Enable the workplace data-driven organization productivity
Change Mgt Problem Mgt ITSCM SAM Depth Incident Mgt Strat & Planning Security EA Breadth HAM
Four Core Principles for Building a CMDB 1. Depth & Breath Transform to a hybrid infrastructure Protect your digital enterprise 2. COP Model Maximizing value from your apps and data Empower Enable the workplace data-driven organization productivity Empower Enable the workplace data-driven organization productivity
Defines the CMDB Governance Model Consumer Defines CMDB Architecture Owner Defines the CMDB Onboarding Process Defines the CMDB Data Strategy Provider
Four Core Principles for Building a CMDB 1. Depth & Breath Transform to a hybrid infrastructure Protect your digital enterprise 2. COP Model 3. Use Cases Maximizing value from your apps and data Empower Enable the workplace data-driven organization productivity Empower Enable the workplace data-driven organization productivity
What is my server dependent on End User impact of System Outage Number of Visio installs Has my server drifted from it s baseline Are there any Incident, Problems, and Events related to a CI What software is installed on my server System impact of taking down a PDU Number of Windows 2003 servers What % of my estate has been patched What are the historical changes to a CI View Configuration of a CI View System Dependencies Enumerate CIs & Assets View Compliance of the estate View CI Health
3. Use Cases
3. Use Cases
Four Core Principles for Building a CMDB 1. Depth & Breath Transform to a hybrid infrastructure Protect your digital enterprise 2. COP Model 3. Use Cases Maximizing value from your apps and data Empower Enable the workplace data-driven organization productivity Empower Enable the workplace data-driven organization productivity 4. Federate / Automate / Aggregate/ Visualise
Federate, Automate, Aggregate Key Principles Federate Maximise existing data sources where they exist (subject to COP) Automate Limit manual involvement to modelling and advanced analytics where possible Aggregate enabling a centralised view of your estate Lower cost of ownership distributed model for data ownership Leads to a sustainable, timely and accurate CMDB Singular source of truth to make informed decisions
Security Incident ITSD System Owners Change Resolver Groups OPs Bridge Consumers Arcsight UCMDB UI UCMDB Browser Config Manager Service Manager OMi Protective Mon. Admin & Power Users Main Users CI Assurance Core Service Mgt Topology Monitoring Medium UCMDB CMDB Universal Discovery General Breadth Asset Manager Goods In Compute Vcenter Virtualised Vmotion Infra Relationships XYZ Storage Storage Aperture Rack & PDU Datacentre Ciscoworks Prime Network Networks NNMi Topology Oracle Grid Control Oracle & SQL DBs Database UD App Relationships Application Dependencies Providers & Owner Example Customer Architecture
Summary
Summary CMDB is a critical tool for IT (more so now than ever) Focus on CMDB inevitably extends to focus for CMS When establishing a CMDB initial focus should be on achieving breadth, then harness COP and Use Cases to develop depth in a manageable way In order for a CMDB to be sustainable it must allow visualisation / ease of consumption, aggregation and importantly automation Ongoing governance and architecture should be driven from the principles of COP
Thank You & Questions