configuration160management(编辑修改稿)

configuration160management(编辑修改稿)内容摘要：

manager. The role that is responsible for managing the activities of the configuration management process for the IT anization. The role also selects, assigns responsibilities to, and trains the configuration management staff. 4 Processes and Activities This chapter provides a detailed discussion of the processes and activities that occur in the Configuration Management SMF. Process Flow Summary Configuration management is graphically represented in the form of a process flow diagram (Figure 1) that identifies the activities needed to successfully manage and control key ponents of an IT infrastructure. Figure 1. Configuration management process flow This highlevel overview can be further broken down into a number of detailed activities and process flows, which are summarized below. Together these detailed activities and process flows provide a prehensive blueprint for the configuration management process. 8 C onfiguration Management Establish Configuration Items Assuming the need to track and control changes to an IT ponent, the process of adding an item to the CMDB involves first deciding upon the appropriate level of detail necessary to track and control change. Next, configuration items (CIs) are created in the database to permit management of ponents at this level. One of the key benefits configuration management provides, in addition to asset management, is the modeling of relationships between IT ponents. These relationships need to be identified and connections built between configuration items in order to model the realworld situation. For example, a workstation is made up of a desktop puter, operating system, and applications, and the workstation is connected to and uses the work. The proper understanding and documentation of relationships between IT ponents makes it possible to perform detailed impact analysis on a proposed change. Access Configuration Items After information about IT ponents and relationships has been added to the CMDB, it can then be used by other SMFs. Change management, for example, uses the relationships defined within the CMDB to determine the impact of a change on other ponents within the IT environment. Problem management uses the CMDB as a resource to identify which CIs are the root cause of incidents, and so on. Change Configuration Items As release management begins to make changes to IT ponents, corresponding changes must be made to the CMDB. Without accurate and uptodate information, the value of configuration management is lost. Wherever possible, this process should be done automatically. The amount of information and the frequency of change make manual data entry impractical for all but the smallest anizations. Review Configuration Items The accuracy of the information stored in the CMDB is crucial to the success of the Change Management and Incident Management SMFs, as well as other service management functions. A review process that ensures that the database accurately reflects the production IT environment needs to be established. Note A more fundamental review should also be carried out at periodic intervals to establish whether the information in the CMDB is relevant to the business and is being managed at the correct level of detail. Setup Activities Prior to initiating the configuration management process flow activities described above, a number of detailed setup and planning activities must be pleted in order to use configuration management effectively. Service Management Function 9 The following process flow identifies these activities and the sequence in which they should be performed. Figure 2. Setup activities for configuration management Onetime configuration management setup activities necessarily precede the daily, ongoing configuration management process and involve a great deal of decision making and planning. Setup activities begin with deciding upon specific aims and objectives (the purpose) the anization intends to achieve by establishing a configuration management process. Issues to be considered include the scope of the IT environment to be managed and the level at which it needs to be managed. Participants in the discussions of purpose should include representatives from all parts of the anization that will be affected, and business relevance should be a guiding factor in making decisions. A second major setup activity involves identifying the entire set of IT ponents that exist within the agreed management boundaries. This leads to more decisions: determining the subsets of these ponents that need to be managed. With very few exceptions, all the information necessary to manage the selected IT ponents needs to be stored in a CMDB hosted in a database product. Building the CMDB is the third major setup activity. It includes building table definitions and creating outline reports. An anization may have one or more CMDBs. Finally, setup also 10 C onfiguration Management includes design and development tasks that are specifically related to use of the CMDB. Policies and procedures for using the database, such as designing security and access restrictions and developing maintenance routines (which include backup and recovery procedures), must be established. Only after these have been acplished can the database be populated. Configuration management setup activities typically involve all of the MOF Team Model role clusters. Their involvement varies, however, based on the particular role cluster, as shown in Table 1. Table 1. Involvement of MOF Team Model Role Clusters in Setup Activities Role Cluster Involvement in Setup Activities Infrastructure Actively involved in all setup activities, including all decisionmaking and technical involvement in building the CMDB. Normally provides resources to plete this activity. Operations Provides oper。