Use of Value Engineering Changes by the District Sample Clauses

Use of Value Engineering Changes by the District. All Approved VECPs and negotiated changes will become the property of the District and shall contain no restrictions imposed by the DB Contractor on their use or disclosure. The District retains the right to use, duplicate, and disclose in whole or in part any data necessary for the utilization of the Approved VECP or negotiated change proposal on any other or subsequent projects without any obligation to the DB Contractor. This provision is not intended to deny rights provided by law with respect to patented materials or processes.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Use of Value Engineering Changes by the District

  • Use of Trunk Forecasts Trunk forecasts provided pursuant to this Agreement must be prepared in good faith but are not otherwise binding on CBB or Verizon.

  • Simultaneous Use of Area STATE reserves the right to issue written authorization to others to use the areas of operations, in the determination of STATE, such use will not materially interfere with the operations of PURCHASER. During the period of this contract, STATE reserves the right to sell any products or materials from the areas of operations, provided that the products or materials are not covered by this contract and that removal will not materially interfere with the operations of PURCHASER. PURCHASER shall not interfere with the use of roads by other authorized users. PURCHASER shall not be held liable for any acts, omissions, or neglect of authorized simultaneous users. PAYMENTS AND ACCOUNTABILITY

  • Evaluation of Contractor Performance of the Contractor under this Agreement will be evaluated. The evaluation shall be prepared on Contract/Contractor Evaluation Sheet (STD 4), and maintained in the Agreement file. For consultant agreements, a copy of the evaluation will be sent to the Department of General Services, Office of Legal Services, if it is negative and over $5,000.

  • Construction of Agreement The parties mutually acknowledge that they and their attorneys have participated in the preparation and negotiation of this Agreement. In cases of uncertainty this Agreement shall be construed without regard to which of the parties caused the uncertainty to exist.

  • PROJECT DEFINITIONS The following capitalized terms have the meanings assigned below for purposes of Exhibits A and B.

  • Technical changes The parties agree to make any technical changes that are mutually agreed prior to the going out for ratification. The parties on signing this document acknowledge, subject to any subsequent agreed editorial and technical changes, that this reflects the agreements reached in the settlement of the Primary Principals’ Collective Agreement 2019-2022. Signed in Wellington on 9 August 2019: Xxxxx Xxxxxx Advocate for NZEI Te Riu Roa Xxxx Xxxxxxxxxx Advocate for the Secretary for Education Witnessed: for NZSTA Annex 1

  • COMPLETION OF AGREEMENT The District and the Union agree that this contract is complete. There shall be no additions to or deletions from the content of any Articles and there shall be no Articles added except by mutual agreement by the Board and the Union. In addition, there shall be no further negotiations on any matter that is within or comes within the scope of representation for the duration of the contract except by mutual agreement.

  • Definitions and Abbreviations 12. The following terms and definitions shall apply to this Agreement:

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.