Common use of Costs of Changes Clause in Contracts

Costs of Changes. 4.1 The provisions of Schedule 16 (Review Procedure) shall apply PROVIDED THAT the Operator's costs in responding to RFCs and in preparing Change Responses etc. shall be borne by the Operator and shall not constitute Eligible Expenditure for the purposes of Schedule 16 (Review Procedure). 4.2 It is important that implementation costs are planned 'as late as possible' so as to reduce the sunk costs in case of major changes required (say, from Dry Run Feedback). Therefore, the following shall apply: Changes to system requirements prior to Final Preparations Commitment Date Necessary software redevelopment costs and any termination costs from third-party software and services commitments Changes to system requirements after Final Preparations Commitment Date but before Hardware Order Date All above costs plus incidental staff costs (e.g. termination or cross-training costs). Changes to system requirements after Hardware Order Date Costs as agreed through Change Control Procedure

Costs of Changes. 4.1 The provisions of Schedule 16 (Review Procedure) shall apply PROVIDED THAT the Operator's costs in preparing and responding to RFCs and in preparing Change Responses etc. any CRF shall be borne by the Operator and shall not constitute Eligible Expenditure for the purposes of Schedule 16 (Review Procedure). 4.2 It is important that implementation costs are planned 'as late as possible' so as to reduce the sunk costs in case of major changes required (say, from Dry Run Feedback). Therefore, the following shall apply: Changes to system requirements prior to Final Preparations Commitment Date Necessary software redevelopment costs and any termination costs from third-party software and services commitments Changes to system requirements after Final Preparations Commitment Date but before Hardware Order Date All above costs plus incidental staff costs (e.g. termination or cross-training costs). Changes to system requirements after Hardware Order Date Costs as agreed through Change Control Procedure

Costs of Changes. 4.1 The provisions of Schedule 16 17 (Review Procedure) shall apply PROVIDED THAT the Operator's costs in responding to RFCs and in preparing Change Responses etc. shall be borne by the Operator and shall not constitute Eligible Expenditure for the purposes of Schedule 16 17 (Review Procedure). 4.2 It is important that implementation costs are planned 'as late as possible' so as to reduce the sunk costs in case of major changes required (say, from Dry Run Feedback). Therefore, the following shall apply: Changes to system requirements prior to Final Preparations Commitment Date Necessary software redevelopment costs and any termination costs from third-party software and services commitments Changes to system requirements after Final Preparations Commitment Date but before Hardware Order Date All above costs plus incidental staff costs (e.g. termination or cross-training costs). Changes to system requirements after Hardware Order Date Costs as agreed through Change Control Procedure