Common use of Changes in Basic Configuration Clause in Contracts

Changes in Basic Configuration. 2.1.3.1 If, as the result of an Error in the Schematic Design, it becomes apparent that the Basic Configuration of the Project must be materially modified, such modification shall be considered a Necessary Basic Configuration Change and shall be eligible for a Change Order as provided in Section 13.8. 2.1.3.2 If a VE results in a change in Basic Configuration, any cost savings from such VE shall be shared in accordance with Section 22. 2.1.3.3 Developer shall not make any change in the Basic Configuration except as approved by TxDOT and authorized by a Change Order in accordance with Section 13, and subject to the limitations contained in Section 6.10. A Change Order is required regardless of the reason underlying the change and regardless of whether the change increases, decreases or has no effect on Developer’s costs or schedule. 2.1.3.4 Except for a TxDOT-Directed Change (including a Necessary Basic Configuration Change) involving more than $5,000 in additional direct costs or involving a delay to a Critical Path, Developer shall not be entitled to an adjustment in the Price or a Completion Deadline or any other relief for any changes in the Basic Configuration.