1. Configuration Management
Maturity
Michaël Danys (michael.danys@hpe.com)
November 20, 2015

2. Agenda
Introduction
Configuration Management Maturity Levels
–Maturity Levels 0 to 4
–Asset & CI Lifecycle
–Consumer Owner Provider (COP) Model

3. Configuration Management
Maturity

4. CM Maturity levels
Introduction
Asset Mgmt.
The first CI
CMDB
CMS
Modelling &
CI Control
SACM

5. CM Maturity level 0
Asset Management
Overview
–Database for all assets
–Ownership & financial data
–Asset stateAsset
Management
• Difficult to track changes
• No easy way to report incidents
• None or little historical data
Problems, Drivers & Goals

6. Asset & CI Lifecycle
In use
Retire
Reuse /
Dispose
Request
Procure
In Stock
Asset
CI
Operate
Monitor
Support
Incident
Problem
Change

7. CM Maturity level 0.5
The first CI
Asset
Management
Service
Management
Overview
• Not enough depth (Quality & Quantity)
• What is actually running in the organization?
• What is supporting the business?
Problems, Drivers & Goals
• Startup incident, problem & change management
• Copy of relevant assets in SM DB
• History of Incidents, problems and changes

8. CM Maturity level 1
CMDB
Asset
Management
Service
Management
Win
MC
UNIX
MC
Other
MDR
Overview
Problems, Drivers & Goals
• All CI data is decentralized
• No cross-silo relationship
• CI MDR are being queried by different consumers
• Most IT domains have their own CMDB
• Contains detailed and accurate data on their
domain
• ITSM Processes leverage data from these MDR

9. CM Maturity level 2
CMS
Overview
Problems, Drivers & Goals
• Continuous CMS quality improvement
• Controlling company policies & compliancy
• Provide rich data to other processes
• All CI data centralized in one repository
• Focus on quality
• Control over Consumers, Owners and Providers
• Possible to report and analyze the CI landscape
Asset
Management
Service
Management
Win
MC
Discovery
CMS
UNIX
MC
MDR

10. COP Model
Consumer
Who: The person or application requesting data
What: Which CI data does the consumer need
How: In which format should data be provided
Owner
Provider
Who: Person responsible for the CI information
What: Responsible for quality of his data in the CMS
How: Validation of data in the CMS
Who: The person or application providing data
What: Only CI data for which there is a consumer
How: How should the data enter the CMS

11. CM Maturity level 3
Modeling & CI Control
CI Landscape & Modeling Policy & Compliancy
COP Onboarding
Quality >= Quantity
Logical CIs & Relationships
Impact analysis
Control CIs
Standardize IT
Align with company policies
Find deviations and act

12. CM Maturity level 4
Service Asset and Configuration Management (SACM)
Asset
Management
Service
Management
SCCM
CMS
SAP
SM
MDR Discovery
Reuse CMS data in other processes
• Enrich Asset information
• Support complex licensing structures
CMS  SM
• Provide actual CI data for incident, problem &
change mgmt.
• SM interaction to support policy and compliancy
AM  CMS
• AM provides initial information of Assets that are
being deployed in production to the CMS
• CMS enriches the AM world with actual information

13. CMS
CM Maturity level 4
HPE view on SACM
HPE
Asset Mgr.
HPE
Service Mgr.
HPE UD
Discovery
HPE UCMDB
MDR
HPE
Configuration
Manager

14. Thank you
Michael.danys@hpe.com