|
|
- Goal
- To provide a logical model of the IT
Infrastructure by identifying, controlling,
maintaining and verifying versions of all
configuration items in existence
- Why configuration management
- To account for all IT assets
- To provide accurate information to support
other service management processes
- To provide a sound basis for
incident
management,
problem,
change and
release management
- To verify records against infrastructure and
to correct exceptions
- Resonsibilities
- Planning
- Strategy, policy, scope, objectives,
roles and responsibilities
- Configuration management processes,
activities and procedures
- CMDB, relationships with other processes
and third parties
- Tools and other resource requirements
- Identification
- Identification and labelling (CI)
Configuration Items including: ownership,
relationships, versions and identifiers
- Control
- Ensures no CIs are added, modified,
replaced or removed without the appropriate
controlling documentation. eg Request for
Change
- Status Accounting
- The reporting of all current and
historical data concerned with each CI
throughout its lifecycle
- Verification and Audit
- A series of reviews and audits that
verifies the physical existance of CIs, and
checks that they correctly recorded in the
CMDB (Configuration Management Database)
- DSL (Definitive Software Library) is where the
authorised versions of all software CIs are stored
and protected
|
|
|
|
|
|
|