Configuration Management (ITSM)

src: www.itsmprocesses.com

Configuration Management ( CM ) is the ITIL Information Technology Infrastructure Library (ITIL) version 2 and the IT Services Management (ITSM) process that tracks all of the individual Configuration Items (CIs) can be as simple as one server, or as complex as the entire IT department. In large organizations, configuration managers can be assigned to supervise and manage CM processes. In ITIL version 3, this process has been renamed to Asset and Configuration Management Services .

Video Configuration Management (ITSM)

Item konfigurasi

A configuration item (CI) is an IT asset or combination of IT assets that may depend on and/or have relationships with other IT processes. A CI will have possible hierarchical attributes and relationships that will be assigned by the configuration manager in the CM database.

Attribute

1. Technical - Data describing CI capabilities including software versions and model numbers, hardware and manufacturer specifications and other technical details such as network speed and data storage size. The keyboard, mouse, and cable are considered consumables.
2. Ownership - Part of the management of financial assets, ownership attributes record date of purchase, warranty, location and person responsible for CI. Identification numbers such as code and bar types, such as software, hardware, and documentation are also attributes of ownership.
3. Relationships - The relationship between hardware items (eg printers), software (e.g., drivers), and users (ie Alice).

Maps Configuration Management (ITSM)

Configuration database management

The fundamental component of CM is a CM database (CMDB) that has CI information and is used to understand CI relationships and keep track of their configuration and more

src: www.ontario.ca

Activity

Information in CMDB is used for five basic activities:

1. Planning : The CM plan covers the next three to six months in detail, and the next twelve months outline. These are reviewed at least twice a year and will include strategies, policies, scope, objectives, roles and responsibilities, CM processes, activities and procedures, CMDB, relationships with other processes and third parties, and the tools and number of CI categories tracked in CMDB define scope . Details of CI information are depth .
2. Identification : Selection, identification and labeling of all CIs that make lists of parts of each CI in the system. This includes the recording of information about CI, including hardware and software versions, documentation, ownership and other unique identifiers. CIs should be recorded at the level of detail justified by business needs, usually to an "independent change" level. This includes defining the CI relationship in the system.
3. Controls : This provides assurance that only authorized and identifiable CIs are received and recorded from the receipt until they are removed. This ensures that no CIs are added, modified, replaced or deleted without proper controlling documentation, e.g. Approved request for CI Change, updated specification. All CIs will be under Change Management control (ITSM).
4. Monitoring : Connect with each CI throughout its lifecycle. This allows changes to the CI and tracking their records through various statuses, e.g. ordered, received, tested, aired, repaired, withdrawn, or discarded.
5. Verification : Reviews and audits verifying the physical presence of CI, and checking that they are recorded correctly in the CMDB and component list. This includes the Release Management verification process (ITSM) and CM documentation before changes are made to the environment.

src: i.ytimg.com

See also

• Configuration management
• Company architecture
• IT Governance
• Management of IT services
• IT portfolio management
• Microsoft Operations Framework (MOF)

Source of the article : Wikipedia