Production Environment
The production environment move element freeze standard requires that:- No application changes affecting the move element to be moved are implemented for a two-week period prior
and one-week period after the move element implementation date. - No infrastructure changes affecting the move element to be moved are implemented for a four-week period
prior and one-week period after the move element implementation date.
In addition it is desirable that any application changes be implemented in time to have been executed successfully in
production.
This generally would mean the following:
- For changes that impact monthly processing, no changes should be made after the month-end execution
proceeding the move element transition date. - For changes that impact weekly processing, no changes should be made after the weekly processing
immediately proceeding the move element transition date. - For changes that impact daily processing, no changes should be made for two weeks prior to the move
element transition date.
Example:If a move element is scheduled to move on 3/17, any application changes affecting month-end processing
should be implemented in time to process for February month end. If the application change cannot make the February
month-end implementation, it should be held and implemented after 2/24.
Quality Assurance and Development Environment
The QA and Development Environment move element freeze standard requires that:
- No application changes affecting the move element to be moved are implemented for a three-day period prior
and three-day period after the move element implementation date. Any changes made during the two-week
period prior to the move must be documented and given to the WPM for inclusion in the Move Control Book
prior to the move occurring. This way issues caused by normal development will not be mistaken for move
issues. - No infrastructure changes affecting the move element to be moved are implemented for a four-week period
prior and one-week period after the move element implementation date.
Appeal Process
In cases where the move freeze policy presents unusual hardships for the business, an appeal process is available. Any
change requests falling within the standard move-freeze period require prior approval by the Data Center Relocation
Steering Committee. Information to be presented to the Steering Committee for them to consider a change within the
freeze period includes: - Explanation of the move element, the move approach, and the level of complexity
- Explanation of the requested change and primary business contact
- Increased risk associated with implementing the change during the freeze period
•Εffect on the business of holding the change - Benefits associated with completing the change during the freeze period
Questions concerning the freeze should be directed to the individual Work Plan Managers and then to their vice
presidents for initial resolution. Issues that cannot be resolved through the Work Plan Manager should be documented
and raised to the Data Center Relocation project manager (John Bennett). If not resolvable, the project manager will
raise the issue to the Data Center Relocation steering committee and if necessary to Greg Clancy.
Move Element Freeze Communication Responsibility
Work Plan Managers are responsible for communicating to affected technology and business area management the
freeze periods associated with each move element. The freeze dates will also be posted on the Data Center Relocation
Web site. Any freeze period issues must be communicated to the Work Plan Manager and, if necessary, to the Data
Center Relocation project manager (John Bennett).
EXHIBIT 9 Move Element Freeze Policies
Case Study IV-2 • FastTrack IT Integration for the Sallie Mae Merger 623