【正文】 service between thebusiness and ITchanges/projectsy7bamp。xkuG$`!GX9r0ReducetheKnow Errors and risksassociated with the transition of the service3Objective of STToplan and manage the resourcerequired to establish a new or changed \CRT8CProvide clear and prehensive plans thatenable alignmentbetween thebusiness change projectand the service transition plans.3~.v cw8RXto4l0Minimize the unpredicted impacton the production services, operations and support organization,`r Ct?v0a$^C0Increasethecustomer, users and service management staff satisfactionwith the service transition practicesMS cS|4x0Increase proper use of service4Scope of STmanagement and coordinate of the processes, systems and functions to package, build, test and deploy a release into production and establish the service specified in the customer and stakeholder requirements.5exclude from STMinor modifications to the production services and environment5_b Wyzj3Fsn^0Ongoing continual service improvement that do no significantly impact the services or service providers39。 capability to deliver the service.6Value to businessService Transition39。s biggest contribution is to enable the service provider tocope with higher volumes of change without impacting service qualityITPUB個(gè)人空間4?K4X%e9Iu%iResponsiveness to new business and market developmentsh Xw[G1]。xP0Support formergers and acquisitionand transfer of servicesITPUB個(gè)人空間9m6DH YW8i)]Confidence inpliancewith business and governance requirements(e2` d%U J*sGEr0Variance information forplanning and budgeting and productivity informationrelated to the new or changed G(lkIncreasedaccuracy of scope and content for maintained contractsITPUB個(gè)人空間n NQ|{|5@hf Q。TTimely cancellation or changestomaintenance contractswhen ponents are disposed or demissioned.S:b*n^)X39。f2X0Increasedunderstanding of risk during and after a Change.7Utilities and WarrantiesUtility: expect the service to support and the constrains it will removeITPUB個(gè)人空間.{OZL$FMY(lZWarranty: Assurance be provided, meet certain specification: availability, capacity, continue to receive utility, security.8Release policynumbering and naming conversionITPUB個(gè)人空間O4GlP,V)eroles and responsibilityITPUB個(gè)人空間 Eov。u。pK7dUq9\frequencyITPUB個(gè)人空間/[ ^)r`.p0kP*paccepting and grouping changesITPUB個(gè)人空間Y6i D_J6rI6}automate the build, installation and releasing distributionJ @rn7O3ws0configuration baselineR I*{.| ^lU0exit and entry criteriaITPUB個(gè)人空間p7x ~ML8ne1mexit early life support9Typical releaseMajor release: containing large arise of new functionality, eliminate temporary fixes, supersedes minor upgrades, releases and emergency fixes.frVoek3?!G0Minor release: containing small enhancements and fixes, supersedes all emergency fixesITPUB個(gè)人空間@,T。rg Na_Emergency release: correction to known error, high priority business requirement10Scope of CHMThe addition, modification or removal of authorized, planned or supported service or service ponent and its associated documentcu @RK@|+ 11Change sourceStrategy Change Service Strategy/BRMYC(\$C]39。i39。r0Service change Service Design , CSI(n0Ps)JC9Gdg6m?0Corrective Change SO12Change RequestA change request is a formal munication seeking an alternation to one or more configuration items.13Change processtask。 dependencies。 people。 schedule。 escalation14Reason for rejectImpractical。 repeats of earlier RFC。 inplete submission15Emergency changeEmergency change is reserved for changes intended to repair an error in an IT service that is negatively impacting the business to a high degree.16Emergency change authorizationDefined automation levels will exist for an emergency change, and levels of delegated authority must be clearly documented and understood.at4E/bLMP8hyN0ECAB, authority delegated.17Emergency change testingCompletely untested changes should not be implemented if at all avoidable.18Emergency change documentationtemporary records are made。 all records are pleted retrospectively, and earliest possible opportunity.19CMSService Asset and Configuration Management requires the use of a support system knowns as Configuration Management System (CMS):V(O0u){@+mamp。P0CMS maintains the relationship between all service ponents and any related incidents, problems, known errors, change and release documentation.20Secure LibraryA collection of software, electronic or document Cis of known type and status.21Secure StoreA location that warehouses IT assets.22Definitive Media Library (DML)Security library in which the definitive authorized version of all media Cis are stored and protected. It stores master copies of versions that have passed quality assurance checks.23Definitive SparesAn area should be set aside for the secure storage of definitive hardware spare.24Configuration baselineConfiguration of a service, product or infrastructure that has been formally reviewed and agreed on, that thereafter services as the base for further activities.25SnapshotCurrent state of a configuration item or an environment.,y8_2Rsom0 enable problem management。 restore to support security scanning software.26Release and Deployment Management conceptRelease and deployment management aims to build, test and deliver the capability to provide the service specified by service design and that will acplish the stakeholder requirements and deliver the intended objectives.27Purpose of Release and Deployment ManagementDefine and agree plans。ITPUB個(gè)人空間0e q*@.AJ6FQ}!F39。~each release package are patible。2E~7oZO?*q5[0integrity of release package, ponent recorded accurately in CMS。ITPUB個(gè)人空間`9mk A6b*zgrelease and deployment package can be tracked, installed, tested, verified, uninstalled and backed out。!x^YOQz9tC,q0organization and stakeholder change is managed。LPT$iA]9c9uE*Te0record deviation, risks, issues and take corrective action。ITPUB個(gè)人空間amp。Wv39。y