Checklist CMS CMDB

<seo metakeywords="itil cms, cms itil cms cmdb, itil cms cmdb" metadescription="Template CMS/ CMDB Configuration Management System/ Configuration Management Database. The CMS is a coherent logical model of the IT organization’s ..." />

DE - 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: Checklists ITIL Service Transition

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

 

The Configuration Management System (CMS) is set of tools and data that is used for collecting, storing, managing, updating, analyzing and presenting data about all configuration items and their relationships, typically made up of several Configuration Management Databases (CMDB) as physical sub-systems. Its underlying structure is defined by the Configuration Model, a coherent logical model of the IT organization’s service assets, including their attributes and relationships.

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, ...

Configuration Items are characterized by their attributes (recorded in the CI’s Configuration Record) and their relationships to other CIs.

 

Depending on the type of Configuration Item, typical attributes of a CI Record include:

 

1. Unique identifier
2. Name
3. Description
4. Responsibilities and Controls
   1. CI owner/ person in charge
   2. Authorities for creating, authorizing, modifying or deleting the CI, as appropriate
   3. Applicable controls and guidelines (e.g. controls/ procedures to ensure the configuration data remain consistent when CIs are added or removed or when CI states change, or controls/ procedures to ensure the contents of the CMS are in line with certain quality criteria)
   4. Reporting, auditing and verification requirements
5. CI type, for example
   1. Main type (e.g. Service, Hardware, Software, Document, Staff ...)
   2. Sub-type (e.g. Server, Printer, ... - refinement of the main type into sub-types)
6. Manufacturer information
   1. Manufacturer name
   2. Serial number
   3. License number/ reference to license contract
7. Version
8. Modification history of the CI Record
   1. Date of creation
   2. Modifications
   3. Description of modification
   4. Date
   5. Person in charge
9. Location
   1. Physical location, if applicable
   2. Logical location, if applicable (e.g. fileserver directory)
10. 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
11. Relationships to IT services
12. Relationships to other CIs, e.g.
    1. Is a component of
    2. Is associated with
    3. Uses
    4. Is a characteristic of
    5. Is a new version of
    6. Will be replaced by
13. Relationships to other data objects within Service Management
    1. Incident Records
    2. Problem Records
    3. Known Errors
    4. Change Records
14. License details
15. Document references
    1. Applicable policies and guidelines
    2. Contractual documentation
    3. Operating documentation
    4. User documentation
    5. Emergency-relevant documentation
    6. Other documentation