Changes to Schematic Design and Schematic ROW Sample Clauses

Changes to Schematic Design and Schematic ROW. Developer acknowledges and agrees that the requirements 19 and constraints set forth in the Contract Documents and in the Governmental 20 Approvals, as well as Site conditions, will impact Developer’s ability to revise the 21 concepts contained in the Schematic Design. Developer, however, may modify the 22 Schematic Design without ADOT’s prior written approval if the proposed modification:
AutoNDA by SimpleDocs
Changes to Schematic Design and Schematic ROW. 6.3.3.1 DBT acknowledges and agrees that the requirements and constraints set forth in the Contract Documents and in the Governmental Approvals, as well as Site conditions, will impact DBT’s ability to revise the concepts contained in the Schematic Design. DBT, however, may modify the Schematic Design without KYTC’s prior written approval if the proposed modification: (a) Meets the requirements of Exhibit 3 (Technical Provisions); (b) Requires no revision, modification or amendment to the NEPA Approval; (c) Does not constitute a Design Exception; and 6.3.3.2 Does not deviate from the design concepts included in the Proposal. DBT may rely on the Schematic ROW limits, and acknowledges that it is feasible to design and develop the Basic Project Configuration within said Schematic ROW limits. 6.3.3.3 DBT acknowledges that the Schematic Design is preliminary and subject to refinement through the Final Design process, and that DBT is not entitled to an increase in the Contract Price, a Completion Deadline adjustment or any other Claim in connection with changes in the Schematic Design.
Changes to Schematic Design and Schematic ROW. 25 (a) Developer acknowledges and agrees that the requirements and constraints set 26 forth in the Contract Documents and in the Governmental Approvals, as well as 27 Site conditions, will impact Developer’s ability to revise the concepts contained in 28 the Schematic Design. Developer, however, may modify the Schematic Design 29 without ADOT’s prior written approval if the proposed modification: 30 (i) Meets the requirements of the Technical Provisions; (ii) Requires no revision, modification or amendment to the NEPA Approval, 32 as determined in accordance with Section DR 420.2.6.1 of the Technical 33 Provisions; (iii) Does not constitute a Design Exception or Design Variance; and
Changes to Schematic Design and Schematic ROW. 6.4.3.1 Developer acknowledges and agrees that the requirements (a) Meets the requirements of the Technical Provisions; (b) Requires no revision, modification or amendment to 2.6.1 of the Technical Provisions; Variance; and in the Proposal. (d) Does not constitute a Design Exception or Design Does not deviate from the design concepts included 6.4.3.2 Developer may rely on the Schematic ROW limits, as shown 6.4.3.3 Developer acknowledges that the Schematic Design is
Changes to Schematic Design and Schematic ROW. 20 6.4.3.1 Developer acknowledges and agrees that the requirements 21 and constraints set forth in the Contract Documents and in the Governmental Approvals, 22 as well as Site conditions, will impact Developer’s ability to revise the concepts contained 23 in the Schematic Design. Developer, however, may modify the Schematic Design without 24 ADOT’s prior written approval if the proposed modification: 25 Meets the requirements of the Technical Provisions; 26 Requires no revision, modification or amendment to 27 the NEPA Approval, as determined in accordance with Section DR 420.2.6.1 of the 28 Technical Provisions; 29 Does not constitute a Design Exception or Design 30 Variance; and 31 Does not deviate from the design concepts included in 32 the Proposal. 33 6.4.3.2 Developer may rely on the Schematic ROW limits, as shown 34 on the Schematic Design, and that it is feasible to design and develop the Basic 35 Configuration within said Schematic ROW limits. Accordingly, Developer shall have the 36 right to certain relief due to Necessary Schematic ROW Changes, to the extent provided 1 in Section 14.4.1; provided, however that Developer acknowledges that “feasible to 2 design and develop the Basic Configuration” is not intended to mean or be limited to 3 Developer’s design approach set forth in its Proposal or Developer’s preferred design

Related to Changes to Schematic Design and Schematic ROW

  • Schematic Design Documents In accordance with the approved Preliminary Design and Construction Schedule and based upon approval of and comments made by the Owner regarding the Concept Design Studies, the Design Professional shall prepare and submit to the Owner Schematic Design Documents, including drawings and outline specifications. These documents shall represent a further development of the approved design concept, providing additional detail and specificity regarding the intended design solution. Typically, all such documents shall be drawn to scale, indicating materials and assemblies, as appropriate, to convey the design intent and to illustrate the Project’s basic elements, scale and relationship to the Site. All major pieces of furniture and equipment to be fixed or supplied by the CM/GC shall be illustrated to scale. (See ASTM Standard Practice E 1804-02, August 2007, Sections 6.3, 8.2 and 8.3 for guidance on information which is generally developed in Schematic Design.)

  • Schematic Design See Section 2, Part 1, Article 2.1.4, Paragraph 2.1.4.2.

  • Schematic Design Phase 1.2.1 Based on the mutually agreed upon Program of Requirements, Amount Available for the Construction Contract and the Project Schedule, the Architect/Engineer shall prepare sufficient alternative approaches utilizing BIM for design and construction of the Project to satisfy Owner’s project requirements and shall, at completion of this phase, submit Schematic Design Documents derived from the model in accordance with the BIM Execution Plan, “Facility Design Guidelines” and any additional requirements set forth in Article 15. The Architect/Engineer shall review alternative approaches to design and construction for the Project as they are being modeled at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by the Owner within the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Schematic Design. The Architect/Engineer shall provide the Construction Manager with a compact disc containing documents and data files derived from the model to assist the Construction Manager in fulfilling its responsibilities to the Owner. 1.2.2 Architect/Engineer shall provide all services necessary to perform the services of this phase (preparation of model(s), relevant data, decision support model views and Schematic Design Documents) including, without limitation, unless otherwise approved by Owner, the preparation and prompt delivery of all items specified in the BIM Execution Plan and “Facility Design Guidelines”. 1.2.3 Architect/Engineer shall work closely with Owner in preparation of schematic drawings and shall specifically conform to Owner’s requirements regarding aesthetic design issues. 1.2.4 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments. 1.2.5 Before proceeding into the Design Development Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Schematic Design documents and approval of the Architect/Engineer’s preliminary Estimated Construction Cost and schedule. 1.2.6 The Architect/Engineer shall participate in a final review of the Schematic Design Documents and model(s) with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. Prior to the Owner’s approval of the Schematic Design Documents, the Architect/Engineer shall incorporate such changes as are necessary to satisfy the Owner’s review comments, any of which may be appealed for good cause.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

  • Construction; References; Captions Since the Parties or their agents have participated fully in the preparation of this Agreement, the language of this Agreement shall be construed simply, according to its fair meaning, and not strictly for or against any Party. Any term referencing time, days or period for performance shall be deemed calendar days and not work days. All references to Consultant include all personnel, employees, agents, and subconsultants of Consultant, except as otherwise specified in this Agreement. All references to City include its elected officials, officers, employees, agents, and volunteers except as otherwise specified in this Agreement. The captions of the various articles and paragraphs are for convenience and ease of reference only, and do not define, limit, augment, or describe the scope, content or intent of this Agreement.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • Amendments - Changes/Extra Work The Subrecipient shall make no changes to this Contract without the County’s written consent. In the event that there are new or unforeseen requirements, the County has the discretion with the Subrecipient’s concurrence, to make changes at any time without changing the scope or price of the Contract.‌ If County-initiated changes or changes in laws or government regulations affect price, the Subrecipient’s ability to deliver services, or the project schedule, the Subrecipient will give County written notice no later ten (10) days from the date the law or regulation went into effect or the date the change was proposed and Subrecipient was notified of the change. Such changes shall be agreed to in writing and incorporated into a Contract amendment. Said amendment shall be issued by the County-assigned Contract Administrator, shall require the mutual consent of all Parties, and may be subject to approval by the County Board of Supervisors. Nothing herein shall prohibit the Subrecipient from proceeding with the work as originally set forth or as previously amended in this Contract.

  • Annexes, Appendices and Footnotes The annexes, appendices and footnotes to this Agreement constitute an integral part of this Agreement.

  • LIST OF SCHEDULES AND EXHIBITS Schedules

  • Incorporation of Exhibits, Annexes, and Schedules The Exhibits, Annexes, and Schedules identified in this Agreement are incorporated herein by reference and made a part hereof.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!