Checklist CMS CMDB

From IT Process Wiki
Jump to: navigation, search

diese Seite auf Deutschesta página en españolDE - ES - Checklist CMS CMDB - Template CMS CMDB - Configuration Management System (CMS)/ Configuration Management Database (CMDB)


 

ITIL Process: ITIL 2011 Service Transition - Service Asset and Configuration Management

Checklist Category: Templates ITIL 2011 - Service Transition - Most popular ITIL Templates

Source: Checklist "Configuration Management System (CMS)/ Configuration Management Database (CMDB)" from the ITIL Process Map

 

Overview

Checklist CMS CMDB

The Configuration Management System (CMS) is a set of tools and data that is used for collecting, storing, managing, updating, analyzing and presenting data about all configuration items and their relationships. A CMS may manage more than one physical Configuration Management Databases (CMDB). Its underlying structure is defined by the Configuration Model, a logical model of the IT organization’s service assets.

The CMS is used to store information on all Configuration Items (CIs) under the control of Configuration Management.

CIs can be of various types: the CMS almost always covers services and IT infrastructure, but might also cover other item types like policies, project documentation, employees, suppliers, etc.

 


Configuration Model and CI Types

The structure of the CMS is defined by the Configuration Model, which specifies the types of CIs managed through the CMS, including their attributes and relationships. The Configuration Model is often maintained as a (set of) documents or data models. It also manifests itself, for example, in the table structure of the databases used to store configuration information.

The Configuration Model typically defines the following structural aspects of the CMS:

 

CI types and sub-types

CI types and sub-types managed in the CMS, usually in the form of a tree structure as in the following example:

  1. Main types (e.g. Service, Hardware, Software, Document, Staff ...)
  2. Sub-types (e.g. Server, Printer, ... - refinement of the main type into sub-types)
  3. … further sub-types as appropriate

Attributes

(Attributes to be managed for each CI type)

Status values

(allowed status values describing the lifecycle of the CI types)

Relationships between CI types

E.g.

  1. "Is a component of"
  2. "Is associated with"
  3. "Uses"
  4. "Is a new version of"
  5. "Will be replaced by", …

Authorities and controls

  1. CI type owner
  2. Authorities for creating, authorizing, modifying or deleting the CIs of this type, as appropriate, normally assigned as access rights in the CMS and relevant sub-systems
  3. Applicable controls, guidelines and policies (e.g. mechanisms to ensure that only authorized personnel is able to apply changes to the CIs and modify the related CI records in the CMS, or controls/ procedures to ensure the configuration data remain consistent when CIs are added or removed)
  4. Applicable guidelines and policies
  5. Reporting, auditing and verification requirements

 

Configuration Item Records - CI Records

The details of actual CIs ("instances of CI types") are stored in CI Records. The exact set of attributes to be maintained for a CI will vary depending on the CI type at hand, as specified in the Configuration Model.

CI Records typically contain the following information:

 

Identifier

(Unique identifier - ID)

Name

Description

CI owner

(CI owner/ person in charge)

CI type

Manufacturer information

  1. Manufacturer name
  2. Serial number
  3. License number/ reference to license contract

Version information

Location

  1. Physical location, if applicable
  2. Logical location, if applicable (e.g. URL or directory on a fileserver)

Modification history of the CI Record

  1. Date of CI Record creation
  2. Modifications
    1. Date
    2. Person in charge
    3. Description of modification

Status history

(description of the life cycle of a CI with status values, as for example "Undergoing Test", ..., "Active", ..., "Undergoing Maintenance", ..., "Out of Operation", ...)

  1. Present status and version
  2. Status and version history (historical Changes to the status of the CI or Changes planned for the future)
    1. Status change
    2. Description
    3. Time and date of the Change in status

Relationships to other CIs

E.g.

  1. "Is a component of"
  2. "Is associated with"
  3. "Uses"
  4. "Is a new version of"
  5. "Will be replaced by", …
  6. ... including relationships to services supported by the CI.

Licensing information

Document references

  1. Contractual documentation
  2. Operating documentation
  3. User documentation
  4. Emergency-relevant documentation
  5. Other documentation

 

References to Configuration Items (CIs) - Note

CIs are typically referenced from other service management systems.

In an Incident Management system, for example, an Incident Record will contain a reference to one or more affected CIs. So these relationships are recorded in Incident Records rather than the CI records.

 

[ Infobox ]

Link to this page:
Languages: English | Deutsch | español
Image: CMS - CMDB (.JPG)
Author: , IT Process Maps