ITIL培训_中文.ppt

* Introduction Every IT organization has information about its IT infrastructure. Such information is particularly likely to be available after major projects that are generally followed by an audit and impact analysis. However, the art is in keeping the information up-to-date. Configuration management aims to provide reliable and details about the IT infrastructure. Importantly, these details include not just details on specific items in the infrastructure (Configuration Items, or CIs), but how these CIs relate to one another. These relationships form the basis for impact analysis. The processes of Configuration Management include: Check if changes in the IT infrastructure have been recorded correctly, including the relationships between CIs Monitor the status of the IT components Ensure that there is an accurate picture of the versions of Configuration Items (CIs) in existence CMDB与Asset DB的区别：Asset DB偏重于有价值的资产、折旧等的管理，CMDB除了记录资产信息外，还记录一些如变更申请、问题记录、配置信息等详细记录以及他们之间的相互联系。CI，可以是硬件、软件、事件、变更申请、服务水准等，可以大到整个系统，小到一个部件，CI之间的关系有part of ,connect to, use, copy, parent/child * Release Management Introduction Release Management aims to ensure the quality of the production environment, by using formal procedures and checks when implementing new versions. Release management is concerned with implementation, unlike change management that is concerned verification. Release management works closely with configuration management and change management, to ensure that the common CMDB is updated with every release. Release management also ensures that the contents of release in the Definitive Software Library (DSL) are updated. The CMDB also keeps track of hardware specifications, installation instructions, and network configuration. Stocks of hardware, particularly standardized basic configurations, are stored in the Definitive Hardware Store (DHS). However, in general, release management is primarily concerned with software. In large projects in particular, release management shoul