【導(dǎo)讀】inferred.owners.What’sNew?

　　

【正文】 ter experts across all the SMFs, the processes within infrastructure engineering are delegated and performed by various roles across the MOF Team Model role clusters。 the specific coordination role for IE is carried out by the infrastructure engineering manager within the Infrastructure Role Cluster, which is examined in more depth in the Roles and Responsibilities section later in this document. 8 Infrastructure Engineering Scope The Infrastructure Engineering SMF affects all standardized practices within an IT anization. These standards and policies may originate from any other SMF in any MOF Process Model quadrant. The SMF is flexible in its scope, with the extent of IT standardization to be determined by the implementing anization. Infrastructure engineering is not about control or micromanaging. It‘s about defining mon ponents that affect many groups and projects and facilitating the widespread application of these mon ponents. To this end, controlling every single ponent within even a small infrastructure environment is impractical. Over and above the challenge of obtaining and collating all of the relevant information, the costs and resources involved in maintaining and updating the information would be prohibitive. Therefore, choices must be made concerning the desired scope of infrastructure to be managed. This decisionmaking process requires that each category be evaluated for its direct relevance to meeting business needs, its dependencies on other categories, and the degree to which other categories depend on it. As with a CMDB, best practice calls for managing only those categories that: ? Are necessary for the effective operation of the business. ? Support the enablement and delivery of IT services. ? Are mon ponents across IT teams and projects that will save time and money if standardized for the whole. These same criteria may be applied to creating standards or policies for the change or management of the infrastructure。 centralized management of some infrastructure ponents is simply not practical or beneficial. Balancing this, it should be noted that the proliferation of multiple, seemingly inconsequential technologies—for example, remote management or scripting tools—can eventually amount to a significant operations management burden and cost. Furthermore, multiple technologies can impose additional security risks since additional work ports may need to be opened to acmodate them. In considering the scope within which to standardize, it is critical to consider these factors. Appendix A provides a list of typical IT infrastructure ponents to which standards and policies are applied. The decision to include a category within the IE scope should be reviewed at periodic intervals to ensure that resources are being allocated to useful activities. Capabilities An anization that implements this SMF should have the anizational capabilities in place to be able to plete and maintain the following: ? Discover current standards and policies. ? Define categories of standards, processes, and policies that align with their IT anizational structure. ? Define an effective suite of standards, processes, and policies for mon IT activities. ? Implement and maintain a change management process. ? Apply the standards and policies for design, development, and deployment tasks. The breadth and depth of the standards and policies that are developed and applied may vary from anization to anization depending upon the maturity level to which other MOF service management functions have been adopted. Service Management Function 9 Key Definitions Change Initiation Review. The Change Initiation Review is the first milestone within the MOF Process Model and marks the beginning of an investment of resources from IT operations in instigating a change to the infrastructure. This review is held at the beginning of the change management process (closely synchronized with the Project Plan Approved MSF milestone) to evaluate the alignment of the requested change with IT policies or standards related to it. The guidance and infrastructure control processes managed by IE provide a key input to the Change Initiation Review as they ensure that any proposed change has utilized the policies and standards for the defined category to be changed. Infrastructure category. A grouping of elements of the infrastructure with a monality—for instance, hardware, desktop, work ponents, or buildings. Infrastructure engineering manager. A specific role within the Infrastructure Role Cluster in the MOF Team Model. The individual responsible for the management, implementation, and review of the IE process. Coordinates and manages the relationships with those responsible for other SMFs and OMRs. Infrastructure environment. The defined operational target for inclusion within the infrastructure engineering management process, which must be defined at the outset when implementing IE principles. Policy. A defined process or set of procedures within a particular infrastructure category. For example, policies might be established for: ? Managing the outsourcing of a service. ? Hardware purchasing processes. ? Managing change approvals. ? Managing wireless security parameters. ? Procuring a vendor. ? Messaging security. ? Guiding developers in procuring IT environmental requirements outside of established policies or standards. The policies in place will ensure that the infrastructure plies with the overall strategy and accepted procedures of the anization. Standard. A standard within this SMF is defined as a set of criteria or configurations applied within a category. Whereas policies are frequently processes applied to human activities, standards are frequently lists of requirements that apply to technologies. Examples of standards created for specific categories mi