Change control
378 Avaya Application Solutions IP Telephony Deployment Guide
●
Publishing change control meeting notes and helping communicate changes to
appropriate technology and user groups
●
Helping ensure that only authorized changes are implemented, that changes are
implemented in an acceptable time frame in accordance with business requirements, that
changes are successful, and that no new incidents are created as a result of a change
In addition, the change controller should must metrics for the purpose of improving the change
management process. Metrics can cover any of the following:
●
Volume of change processed per period, category, and risk level
●
Average turnaround time of a change per period, category, and risk level
●
Number of relative changes amended or rejected per period and category
●
Number of relative change backouts by category
●
Number of relative changes that generate new problem incidents
●
Number of relative changes that do not produce the desired business results
●
Number of emergency changes implemented
●
Degree of client satisfaction
Change management team
You should create a change management team that includes representation from networking
operations, server operations, application support, and user groups within your organization.
The team should review all change requests and approve or deny each request based on
completeness, readiness, business impact, business need, and any other conflicts.
The team should first review each change to ensure that all associated documentation is
complete, based on the risk level. The team can then investigate the business impact issues
and business requirements. The final step is to schedule the change. Once a change has been
approved, the change management team is also responsible for communicating the change to
all affected parties. In some cases, user training might also be needed.
Note:
Note:
The change management team does not investigate technical accuracy of the
change. Technical experts who better understand the scope and the technical
details should complete this phase of the change process.
Summary of Contents for Application Solutions
Page 1: ...Avaya Application Solutions IP Telephony Deployment Guide 555 245 600 Issue 3 4 1 June 2005 ...
Page 20: ...About This Book 20 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 21: ...Issue 3 4 1 June 2005 21 Section 1 Avaya Application Solutions product guide ...
Page 22: ...22 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 106: ...Call processing 106 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 124: ...Avaya LAN switching products 124 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 139: ...Issue 3 4 1 June 2005 139 Section 2 Deploying IP Telephony ...
Page 140: ...140 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 186: ...Traffic engineering 186 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 204: ...Security 204 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 228: ...Avaya Integrated Management 228 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 274: ...Reliability and Recovery 274 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 275: ...Issue 3 4 1 June 2005 275 Section 3 Getting the IP network ready for telephony ...
Page 276: ...276 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 356: ...Network recovery 356 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 366: ...Network assessment offer 366 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 367: ...Issue 3 4 1 June 2005 367 Appendixes ...
Page 368: ...Appendixes 368 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 394: ...Access list 394 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 414: ...DHCP TFTP 414 Avaya Application Solutions IP Telephony Deployment Guide ...