Change Request Process. In the event that circumstances warrant a change to accomplish the Statement of Work as defined in Paragraph 2, a Change Request shall be submitted that includes the following: The name of the person requesting the change, a summary of the required change, the start date for the change, the reason and necessity for change, the urgency level for the change, the elements to be altered, the impact of the change, the staffing plan associated with the change, the impact on the schedule for implementing the change, the cost impact, the risk assessment and a recommended approach to the change.
Change Request Process. The following describes the process to be used by the parties for minor modifications to the Services.
1. Cingular submits change request, in the form attached as Exhibit I (“Change Request”).
2. InfoSpace reviews Change Request and returns a high level time/cost estimate and Work Order within mutually agreed timeframe.
3. Cingular and InfoSpace jointly review the requirements.
4. InfoSpace creates detailed use cases and functional specifications (and returns another estimate if necessary) within mutually agreed timeframe.*
5. Cingular and InfoSpace jointly review and refine use cases and functional specifications (including test cases and test plans).*
6. If necessary, InfoSpace revises Work Order, and Cingular signs Work Order giving final approval for development based on the final specifications.*
7. Upon approval of the Work Order, Cingular provides Infospace with a Cingular Purchase Order in the form attached as Exhibit J (“Purchase Order”)
8. InfoSpace countersigns Work Order and development begins.
9. Changes are placed in demo for Cingular’s testing/review.
10. Changes are pushed to production, only upon written approval from Cingular. * These steps may not be required for all change requests (for example: minor copy changes or replacing ads of the same size).
Change Request Process. If the Minister requests the Vendor to perform a Service or to produce Materials which the Vendor considers outside the scope of this Contract, the Vendor shall immediately, upon noticing such scope deviation or potential scope deviation, send a Change Request to the Minister.
Change Request Process. 17.1 If the Contractor is of the opinion that some aspect of the Services or the Materials will fall outside the scope of this Contract, or, the existing SOW requires an extension to complete the necessary deliverables, the Contractor shall immediately, upon noticing such scope deviation or potential scope deviation, notify the Centre to authorize the initiation of the Change Request process. Changes to any contract will be within allowable limits as depicted in provincial guidelines for the hiring of external consultants.
17.2 The Change Request form (template) provided by the Centre is included in Exhibit D.
17.3 If the Centre considers the Services or Materials specified in the Change Request outside the scope of this Contract, the Centre may:
a) Decide not to have the tasks completed; or
b) request the Contractor to complete some or all of the tasks at a mutually agreed upon cost under separate contract.
Change Request Process. Any Party may request changes in a Specification or a Statement of Work during a Project. Without undue delay upon receipt of such a request from a Customer, or concurrent with its own request, Contractor shall evaluate the requested changes and inform Customers of the effects associated with such changes, including the effects on non-recurring engineering costs, prices and the applicable Milestone Plan schedule and to Contractor’s best knowledge at the time of change request any third party Intellectual Property licenses that are required as a result of the change. If the changes requested by the Customer are technically unfeasible or technically or commercially unreasonable for Contractor, then Contractor shall reasonably substantiate this unfeasibility or unreasonableness and may decline the change; otherwise, the Parties shall negotiate in good faith to find a mutually acceptable solution to implement the changes, agree on the non-recurring engineering costs therefore and amend the respective Exhibit Set accordingly. Any amendment of the Milestone Plan proposed by Contractor for the implementation of the change shall be in accordance with additional time periods reasonably necessary for Contractor to implement the change and any amendment to the non-recurring engineering costs and price proposed by Contractor shall be consistent with Contractor’s pricing as applied to similar Services and/or Deliverables under the original Project unless a need for a different pricing due to change in Contractor’s cost basis is reasonably substantiated by Contractor.
Change Request Process. 10.1 Any material change to the Services that may be requested by the Customer (the “Change(s)”) shall be dealt with in accordance with the Change Request procedure below:
i. the Customer will provide Xxxx with a written request detailing the proposed Change (the “Change Request”).
ii. If Xxxx is satisfied to proceed, it will provide the Customer with a response detailing the implications of the proposed Change and a breakdown of the associated costs.
iii. the Customer must then notify Xxxx within thirty (30) Business Days if it wants to proceed with the Change whereby Xxxx will commence the associated work.
10.2 The Change Request will be incorporated and amend the original SOW(s). Xxxx will not be liable for any inadequate Customer requirements and additional costs will be charged on time and materials basis.
10.3 Xxxx may, at its discretion, charge for the time it spends assessing a Change Request or SOW from the Customer on a time and materials basis.
Change Request Process. 33 Indoctrination.......................................................33 ----------------------------------------------------------------------------- Page 2 Revised: April 13, 1999 > INTRODUCTION
Change Request Process. October 30, 2001 1 of 3
15.2.6.1 If federal or state laws, rules, regulations, policies or guidelines are adopted, promulgated, judicially interpreted or changed, or if contracts are entered into or changed, the effect of which is to alter the ability of either party to fulfill its obligations under this contract, the parties will promptly negotiate in good faith, using the process outlined in Article
Change Request Process. In the event that circumstances warrant a change to accomplish the Scope of Work as described above, a Change Request shall be submitted that meets the following criteria:
Change Request Process. General Principles
4.1 The Service Provider and TfL shall conduct discussions relating to any proposed Changes in good faith.
4.2 The Service Provider shall ensure that, if required by TfL, its Change Manager attends every Review Meeting and presents:
(A) a complete list and detailed descriptions of all outstanding, new and anticipated:
(1) Change Control Requests such list to indicate which relate to Additional Services and which relate to Changes; and
(2) Internal Changes raised by the Service Provider, together with details as to when each was issued or is to be issued and their current status; and
(B) a report on resources deployed in relation to Changes during the period since the previous Review Meeting including such detail as TfL may reasonably request.
4.3 The Service Provider shall prioritise Change Control Requests and Internal Changes as TfL may require, acting reasonably, on the basis that any prioritised Schedule 9 –Change Control Request Procedure and Changes Change Control Requests and Internal Changes must serve to assist and improve the overall operation of the Services.
4.4 The Service Provider will use its reasonable endeavours to suggest Changes from time to time that would result in a benefit to TfL.
