Appendix B: Service Solution Change Request Form

Appendix B: Service
Solution Change
Request Form
Information in this document is subject to change without notice. The names of companies,
products, people, characters, and/or data mentioned herein are fictitious and are in no way intended
to represent any real individual, company, product, or event, unless otherwise noted. Complying
with all applicable copyright laws is the responsibility of the user. No part of this document may
be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of Microsoft Corporation. If, however, your only
means of access is electronic, permission to print one copy is hereby granted.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.


2001 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, BackOffice, FrontPage, NetMeeting, Outlook, PowerPoint,
SQL Server, Visio, Visual Studio, Win32, Windows, Windows Media, and Windows NT are either
registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.

Other product and company names mentioned herein may be the trademarks of their respective
owners.

Appendix B: Service Solution Change Request Form 1


Part 1 – Change Request
(To be completed by Requestor.)
In order to analyze the impact a change has on the Microsoft
®
Exchange 2000
organization, we are requesting the following information. Requestors are to
complete page 1 of this form only. This form must be electronically delivered to
the IT Manager. The IT Manager will evaluate this request. Findings will be
presented back to the Steering Committee for acceptance.
Date Submitted to
IT Manager
Change Control
Number

Requestor Email & Phone #

Reason for Change Request:
(Why are we creating this request?)




To place a check mark in the box, right-click the item and then click
Properties
. In the

Properties
box, on the
Alphabetic
tab, modify the setting
for the name Value to True.

Priority Level (Check one):
(When must the change be in place to be successful?)
!
!!
! 1 (Low - change could wait until next release)
!
!!
! 2 (Medium - prefer change in current release)
!
!!
! 3 (High - include change in current release)

Brief Change Description:
(Provide a brief two-three sentence “executive” overview of the change.)



Detailed Change Description:
(Provide full detail of the change to be implemented.)

Note
2 Appendix B: Service Solution Change Request Form


Functional Specification References:
(For example, document name, version number, item reference, and page
number.)



Implications of Not Making the Change:
(How is the project or customer affected if the change is not made? For
example, inaccurate data, inconvenient to customer, etc.)






************* END OF REQUESTOR SECTION **************
Appendix B: Service Solution Change Request Form 3


Part 2 – Change Request Analysis and Approvals
(To be completed by IT Manager and Vendor.)

Date Submitted to Vendor for analysis

Impact Analysis:
System and/or Module Affected:

(What part of the solution is being changed?)



Project Schedule: (How will the change affect the schedule?)



Project Cost (provide cost breakdown):
(How will the change affect the project cost?)



Other Project Areas/Tasks:
(What other areas or tasks for the project will be affected?)