Service Change Control Procedure. The following provides a detailed process to follow if a change to this Agreement is required: • A Request for Change (“RFC”) will be the exclusive vehicle for communicating any changes. The RFC must describe the change, the reason for the change and the effect the change will have on the services. • The designated contact of the requesting party will review the proposed change and determine whether to submit the request to the other party. • The designated contact of receiving party will review the proposed change and approve it for further investigation or reject it within three (3) business days. The investigation will determine the effect that the implementation of the RFC will have on service targets, service changes and service assumptions related to this Agreement. • Notwithstanding the foregoing, XXXX shall have the right to modify the terms and conditions herein, subject to Section 6.2.
Service Change Control Procedure. The following provides a detailed process to follow if a change to the Jira service is desired: A Service Request will be the vehicle for communicating requests to change the Jira service. The Service Request must describe the change, the rationale for the change and the effect the change will have on the services. The request must be submitted to the HUIT service desk: xxxxxx@xxxxxxx.xxx or 617‐495‐9000. The HUIT service owner will review the proposed change and determine whether to proceed with the request, or notify the user that the requested change will not be implemented and why.
Service Change Control Procedure a. Either party may at any time discuss a Change with the other Party.
