High-Level process flow
Issue 3.4.1 June 2005
379
Communication
Once a change is approved, the next step is to communicate details of the change by setting
expectations, aligning support resources, communicating operational requirements, and
informing users. The risk level and potential impact to affected groups, as well as scheduled
network outages as a result of the change, should dictate the communication requirements.
Avaya recommends creating a matrix to help define who will be affected by a change, and what
the potential time out of service might be for each application, user group, or server. Remember
that different groups might require varying levels of detail about the change. For instance,
support groups might receive communication with more detailed aspects of the change, new
support requirements, and individual contacts, while user groups might receive only a notice of
the potential time that the network will be out of service, and a short message that describes the
business benefit.
Implementation team
You should create an implementation team that consists of individuals with the technical
expertise to expedite a change. The implementation team should also be involved in the
planning phase to contribute to the development of the project checkpoints, testing, backout
criteria, and backout time constraints. This team should guarantee adherence to organizational
standards, update DNS and network management tools, and maintain and enhance the tool set
that is used to test and validate the change.
Specifically, the implementation team should fully understand the following testing questions,
and should include them in the change documentation prior to approval by the change control
board:
●
How thoroughly should we test the change?
●
How will we roll out the test?
●
How long will testing last, and at what point can we make the decision that the change is
implemented successfully?
The implementation team should also be fully aware of all backout criteria, time constraints, and
procedures. The team should answer the following questions as part of the change
documentation for high-risk change prior to approval by the change control board:
●
How is the change to be removed?
●
At what point is the decision made to back out of the change?
●
What information should be gathered before backout occurs to determine why the change
needed to be backed out or why it affected the network adversely?
During the implementation of any change, it is crucial to follow the change management team
recommendations on how to make the change. If anything is performed on the network that
deviates from the recommendations, the implementation team should document and present
these steps to the change controller when the change is completed.
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 ...