Professional Documents
Culture Documents
- Premanand Lotlikar
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
Suite 1 Suite 2
– 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
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?
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 need 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
• Inadequate manual systems
• Affect of urgent changes
• Over ambitious schedules
• Management acceptance
• Bypassing the process
Thank you!