Stream Flow Maintenance Applications Do Not Create a Precedent Sample Clauses

Stream Flow Maintenance Applications Do Not Create a Precedent. The Lemhi Basin stream flow maintenance applications provided for in this Agreement are based upon the historic practice recognized by the Basin 74 High Flow General Provision, and therefore, are not intended to nor shall be construed as establishing a precedent for issuance of any future water rights in the State of Idaho.
AutoNDA by SimpleDocs

Related to Stream Flow Maintenance Applications Do Not Create a Precedent

  • Routine Maintenance (i) CRC shall be responsible for Routine Maintenance when necessary or desirable to maintain the Shared Assets in a safe operating condition, and to permit and facilitate (A) the performance by CRC of its obligations pursuant to this Agreement, and (B) the use of Shared Assets by the Operators in accordance with this Agreement.

  • Site Maintenance The authorized area shall be maintained in a neat, clean, and safe condition, free of any solid waste, debris, or litter, except as specifically authorized herein.

  • Facility Maintenance Seller shall perform, or cause to be performed, all scheduled and unscheduled maintenance required on the Facilities in order to meet the Warranty Specifications and Performance Standards. In that regard, Seller’s responsibilities hereunder shall include, without limitation, promptly correcting any Bloom System or BOF malfunctions, either by (i) recalibrating or resetting the malfunctioning Bloom System or BOF, or (ii) subject to Section 5.7(b), repairing or replacing Bloom System or BOF components which are defective, damaged, worn or otherwise in need of repair or replacement.

  • Erosion Control Structure Maintenance During the period of this contract, Purchaser shall provide maintenance of soil erosion control structures constructed by Purchaser until they become stabilized, but not for more than 1 year after their construction. Contracting Of- ficer may agree to perform such structure maintenance under B4.218, if requested by Purchaser, subject to agreement on rates. Purchaser shall not be responsible for repair of such structures damaged by other National Forest users whose activities are not a part of Pur- chaser’s Operations.

  • Software Maintenance Subrecipient shall apply security patches and upgrades in a timely manner and keep virus software up-to-date on all systems on which State data may be stored or accessed.

  • Records Maintenance; Access Contractor shall maintain all financial records relating to this Contract in accordance with generally accepted accounting principles. In addition, Contractor shall maintain any other records, books, documents, papers, plans, records of shipments and payments and writings of Contractor, whether in paper, electronic or other form, that are pertinent to this Contract (“Records”) in such a manner as to clearly document Contractor's performance. Contractor acknowledges and agrees that Agency and the Oregon Secretary of State's Office and the federal government and their duly authorized representatives will have access to such financial records and other Records that are pertinent to this Contract, whether in paper, electronic or other form, to perform examinations and audits and make excerpts and transcripts. Contractor shall retain and keep accessible all such financial records and other Records for a minimum of 6 years, or such longer period as may be required by applicable law, following final payment and termination of this Contract, or until the conclusion of any audit, controversy or litigation arising out of or related to this Contract, whichever date is later.

  • Unscheduled Maintenance Unscheduled maintenance may be required to resolve issues that are critical for Customer and/or performance of the Cloud Services. Druva will use its commercially reasonable efforts to notify Customer at least six (6) hours prior to the unscheduled maintenance.

  • Support and Maintenance Where Licensee purchases support and/or maintenance services, Licensee’s initial support and/or maintenance term will begin upon delivery to Licensee of the Licensed Software and continue for one (1) year thereafter (or the length of the term if less than a year for any subscription/term license) unless otherwise specified in the applicable annual support and/or maintenance agreement, Product Order, or other written agreement executed between Licensor and Licensee. Where Licensee purchases support and/or maintenance for any Licensed Software, Licensee hereby agrees that it shall purchase such support and/or maintenance services for all of Licensee’s licensed units of such Licensed Software product. Support and/or maintenance services provided by Licensor will be subject to Licensor’s then current applicable standard annual support and/or maintenance agreement unless otherwise agreed by the parties in writing.

  • Installation and Maintenance Except for the bi‐directional and production metering equipment owned by the City, all equipment on Customer’s side of the delivery point, including the required disconnect device, shall be provided and maintained in satisfactory operating condition by Customer and shall remain the property and responsibility of the Customer. The City will bear no responsibility for the installation or maintenance of Customer’s equipment or for any damage to property as a result of any failure or malfunction thereof. The City shall not be liable, directly or indirectly for permitting or continuing to allow the interconnection of the Facility or for the acts or omissions of Customer or the failure or malfunction of any equipment of Customer that causes loss or injury, including death, to any party.

  • Routine Maintenance Services PM1.03.2-1 Respond immediately to restrict all access to Highway Crossing Infrastructure, as directed by the Province.

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