【正文】 bureaucracy without promising on controls for implementation of changes Roles and ResponsibilitiesThis section describes roles and responsibilities within Change Management process. Change Requester (ABB, Service Provider)This role is part of current ADONIS process. The Change Requester is the person who creates the change request and submits it for further processing.Major responsibilities include: Change Reports Service Catalogue Management167。 Information on changes to CIs for updates of CMDBKnowledge Management167。 Approvals, Risk Assessment and control of change required to be implemented for problem resolution.Service Asset andConfiguration Management167。 Trigger for Change167。 Report on incidents arising out of the failed changes167。 responsibilities and many other practicalities that will help understand and run Change Management process from operational perspective. This document outlines the operating guidelines for daily activities and processes used by all Change Management stakeholders. AudienceThis document is intended to be used by ABB IS RUN personnel and Service Suppliers. Specifically Service Suppliers will be responsible to align their internal working practices to this document in regards to handling Changes.2. Change Management process DefinitionA Change is defined as the addition, modification or removal of an authorized, planned or supported service or Configuration Item (CI). Changes may occur due to introduction of a new service, modification to an existing service or termination of an existing service in an IT Infrastructure or for fixing a problem in an existing system.Change Management helps organizations understand and work to minimize risks of changes to the IT environment. It is essentially a process for managing the peopleside of change. ScopeChange Management process can be used to track and manage all IT infrastructure changes. A software application change may include enhancements/modifications to existing applications to address identified problems, address business needs or any other requirement. Similarly a hardware change may include changes to puting devices, network ponents, storage devices and other hardware Configuration Items (CI) to replace malfunctioning hardware, increase hardware capacity or other requirements. In other words, changes to all Configuration Items will be governed by this process.  Process Inputs and OutputsUpdated CMDBPIR ReportsApproved and ImplementedChange DocumentationOther ProcessesPIR ReportsBusiness RequirementsChange PoliciesCI Data from CMDBChange Management process Related ProcessesProcess Input to Change Management Output from Change Management Incident Management167。 Workflows 36 ADONIS Level 4 Process Flow 36 SNOW Workflows per change type 373. Reporting (KPIs + SLAs) 494. Tower Specifics 50 EUC 50 EUS 50 Core Software Platform (CSP) 50 Network 505. Stakeholders 506. Templates 50 RFC Template 50 Functional Specification 50 Change Test Results 51 Implementation plan 51 Backup Plan 51 Point of No return details 51 Communication Plan 51 Backout plan 51 CAB Readiness Checklist 51 CAB Agenda amp。ABB IS Service amp。 Supply IntegrationChange ManagementProcess Operations Manual51 / 51Contents1. Introduction 6 Purpose of the document 6 Audience 62. Change Management process 6 Definition 6 Scope 6 Process Inputs and Outputs 7 Related Processes 7 Process Objectives 7 Roles and Responsibilities 8 Principles and Policies 12 Change Types 12 Environment Scope 16 Change Creation 16 Approvals 17 Change Evaluation and Assessment 18 Change Planning 20 Lead Time 24 Change Development 24 Change Testing 24 Change Priority 25 Change Outages 25 Change Freeze 26 Change Advisory Board (CAB) 26 Emergency Change Procedure 32 Post Implementation Review 34 Change Closure 34 Notifications 35 Change Management Process Flows amp。 Minutes 51 Deployment Verification Plan 51 Post Implementation Review 51 Weekly CAB meetings 517. Vocabulary 528. External References 53 Process Policy Document – Change Management 53 Change Management workflows in SNOW 53 Change Management – Stakeholders list 531. Introduction Purpose of the documentThe purpose of this document is to explain Change Management process defined and implemented within ABB IS RUN. It describes definitions, scope, policies, activities, roles amp。 Trigger for Change167。 Approvals, Risk Assessment and control of change required to be implemented for incident resolution.Problem Management167。 Report on problems arising out of the failed changes167。 CI Verification167。 Input for process improvement167。 Service Requests167。 Creating and submitting a Change Request with accurate and detailed level of information Working with the OTL Change Coordinator to resolve any data inconsistencies with the request Testing and verifying Change was implemented according to requestProcess RoleOrganizational RoleServiceNow FieldChange Requester (ABB, Service Provider)Service Providers\ABB IS RUNRequested by OTL Change Coordinator (ABB)This role is part of current ADONIS process. The OTL Change Coordinator is responsible for seeing that Change Manager and other specialists bring the Change to a close.Major responsibilities include:167。 Verifying the supporting documentation acpanying the Change Record is plete167。 Performing Change Assessment (based on questions and answers)167。 Assisting Change Requester with test implementation when required167。 Conducting Post Implementation Review to verify implementation when required167。 Making sure all required stakeholders are notified about the changeProcess RoleOrganizational RoleServiceNow FieldOTL Change Coordinator (ABB)IS Tower Service CoordinatorChange Task Assignment Group/Change Task Assigned To BTL Cha