Beruflich Dokumente
Kultur Dokumente
- Premanand Lotlikar
Agenda
• Introduction
• Objective of CM
• Benefits
• Basic Concepts
• Relationship with other processes
• Activities in CM
• Process Control
• Key Performance Indicators
• Cost
• Possible Problems
Introduction
• Every IT organization has information
about its IT infrastructure
• Art is to keep the information up-to-date
• Information includes not only about
individual component but how they relate
to one another
• If implemented properly, it can provide
information about:
Product Policy
• Which IT components are we currently using?
How many of each version? How long have we
had them?
• What are the current trends in the various
product groups?
• Which IT components can be phased out and
which require upgrading?
• What licenses do we have and are they
adequate?
• Which maintenance contracts should be
reviewed?
Troubleshooting information &
Impact assessment
•Source: OGC
CI example
Basic Concepts
• Configuration Mgmt Database (CMDB)
– Keeps track of all IT components, their
versions and status and the relationships
between them.
Isolated CMDBs
CI # 1
IT Infrastructure Service A
Service B
CI # 2 CI # 3
CI # 4 CI # 6
Module A System 21 Line 1
CI # 7
CI # 5
NIC 12 Line 2
Module B
CI # 8
Modem 5 Line 3
Depth – Level of Breakdown
IT Infrastructure
Module1-1 Module1-2
Level of Detail (Attributes)
ATTRIBUTE DESCRIPTION
CI number/label Unique identification of the CI.
Serial Number Supplier’s identification number in the form of serial number
Model Name Full model name E.g. PIV MMX 933 MHz
Manufacturer Manufacturer of the CI
Category Classification (H/W, S/W, Documentation)
Warranty expiry date Date when warranty expires
Version number Version number of CI
Location Location of CI
Owner responsible Name and designation of the owner or person responsible for the CI
Status Current state of the CI E.g. ‘under test’, ‘live’
Cost Cost of acquisition
Residual value Current value of CI after depreciation
Comment Other comments
RFC Number RFC number open for the CI
Relationships Relationship b/w the CI and other CIs
CI Relationships
• Relationship b/w CIs useful for:
– Diagnosing errors
– Predicting availability of services
• Relationships can be:
– Logical
• Is a copy of: Copy of a standard model
• Relates to: A procedure, SLA, customer area
• Is used by: CI needed for providing a service
– Physical
• Forms part of: FDD forms part of a PC
• Is connected to: PC connected to LAN
• Is needed for: H/w needed to run application
CI Relationships (example)
Baselines
• Snapshot of group of CI’s taken at a specific
point in time
• Baseline can be used as:
– For recording cost information
– Starting point for development and testing of new
configurations
– Back-out if there is are problems with new
configuration after change
– Standard for supplying configurations (E.g. standard
workstation)
Status Accounting
• The process of recording state changes to a CI
• Most common states:
– On order
– Received, pending testing
– Under test
– Installed to production, Operational
– Under repair
– Disposed
• This information is also useful for problem
management, especially for detecting devices
with high incidents of repair or long repair periods
Example CI status monitoring
•Source: OGC
Verification and Audit
• Used to verify if the current situation still
reflects the details in CMDB
• Audits may be carried out in following
situations:
– After implementing a new CMDB
– Before and after major changes
– After disaster recovery
– At any convenient time
Verification and Audit
• Following questions are asked during
audit:
– Are all RFCs recorded in CMDB?
– Is the CMDB still up-to-date? If not, why?
– What is the impact on Change Mgmt?
– Are baseline configurations recorded
correctly?
– Does naming of the new CI’s comply with
naming convention?
Control of CIs
• Only authorized CIs should be recorded in the
CMDB
• The following actions are monitored:
– CI is added
– CI status changes
– CI owner changes
– CI relationship changes
– CI is removed
– CI license renewed or modified
– CI details updated after audit
Process Control
• Critical Success Factors:
– Information in the CMDB should be up-to-date
• Change Mgmt must be strictly enforced
• Stakeholder for information
– Implementation of CMDB must be divided into
correct stages
• Extensive scopes of CM at once generally fails
– Recording must be given to person having not
only the reqd skill but the right attitude!
Key Performance Indicators
• Number of deltas
• No of occasions when configuration was found
unauthorized
• No of occasions when recorded configuration could not
be found
• Time needed to process a request for recording
information
• List of CI’s where more than a given no of
incidents/changes were recorded
• Statistical information about the structure and
composition of IT infrastructure
• Growth data about IT infrastructure
Cost
• Largely depends on the scope and level of the
detail
• Cost include H/w, S/w and personnel cost
• H/w, S/w cost depend on:
– Additional H/w & S/w required and its configuration
– Application and DB design, population, customization
& implementation
– DB maintenance
• Personnel cost depends on the size of the
organization and level of detail of CMDB
Possible Problems
• Wrong CMDB scope or CI level of detail (too
little or too much)
• Inadequate manual systems (paper systems)
• Affect of urgent changes
• Over ambitious schedules (no time to update
CMDB)
• Management acceptance (cost concerns)
• Bypassing the process
Thank you!