Table of Contents
Advertisement
Change control
Implementation
If the process of assigning risk and documentation occurs before the implementation, the actual
implementation should be straightforward. Beware of the potential for changes to come from
multiple support personnel without their knowing about each other's changes. This scenario can
lead to increased potential time out of service and misinterpretation of the problem.
Test and evaluation
In this phase, the person who initiated the change is responsible for ensuring that the
emergency change had the desired affect and if not, restarting the emergency change process.
Steps to take in the investigation of the change include the following:
Observe and document the impact of the change on the problem.
Observe and document any foreseen or unforeseen side effects of the change.
Determine whether the problem is resolved, and if so, make sure all necessary
documentation and network management updates occur to properly reflect the change.
If the change is unsuccessful, back out, and continue the emergency change process until
the problem is resolved or a workaround is in place.
Once the change is deemed successful, send all emergency change documentation to the
change controller for review and documentation by the change control team. The change
controller and change review team should perform a post mortem on the problem to determine
potential improvements to prevent future emergency changes of this type. You should also send
the information to engineering or architecture groups for review, and allow them the opportunity
to change solution templates, standard software versions, or network designs to better meet the
goals or requirements of your organization.
384 Avaya Application Solutions IP Telephony Deployment Guide
Advertisement
Table of Contents
