Low Inflow Protocol Sample Clauses

Low Inflow Protocol. Agree to share the burden of low water availability in accordance with the attached Low Inflow Protocol (see Exhibit B).
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Low Inflow Protocol. The Parties to the Relicensing Settlement Agreement that also have designated roles and responsibilities under the LIP (Appendix A) hereby agree to uphold their respective LIP commitments. In the event that a Party or Parties do not uphold their respective LIP commitments, then any Party, including the Licensee may (but is not required to) invoke the dispute resolution process described in Section 1.3.8 of this Agreement to attempt to resolve issues regarding LIP commitments Assuming the U.S. Geological Survey (USGS) has necessary rights for the License term, the Licensee shall continue to provide 100% funding support during the License term for the maintenance of the following USGS standard flow gages that are used in the LIP to determine the Three-Month Rolling Average Flow: • Yadkin River at Yadkin College (02116500) • South Yadkin River near Mocksville (02118000) • Abbotts Creek at Lexington (02121500) Any substantial increase in funding support due to changes in these flow gages are subject to review by the Licensee with the North Carolina Department of Environment and Natural Resources (NCDENR). The Licensee may review and propose changes in the contractor, location, or equipment associated with these gages. Any changes proposed by the Licensee will require agreement of NCDENR.
Sample 1Sample 2
Low Inflow Protocol. This License Article highlights the responsibilities of the Licensee from Appendix A, “Low Inflow Protocol for the Yadkin-Pee Dee River Hydroelectric Projects” (LIP), of the Yadkin Hydroelectric Project, FERC No. 2197, Relicensing Settlement Agreement.
Sample 1Sample 2
Low Inflow Protocol. Progress Energy agrees to comply with the requirements of the Low Inflow Protocol (LIP) dated February 2007, which was developed as part of the relicensing process. The LIP is attached hereto as Appendix B.
Sample 1
Low Inflow Protocol. Progress Energy will comply with the requirements of the Low Inflow Protocol dated February 2007. Article 109 Implementation Schedule Minimum instream flows will be commenced within 60 days of the effective date of the New License, provided that the new license for the upstream Yadkin Project (Project No. 2197) has been issued prior to or concurrent with this license and that the Yadkin Project has commenced, and continues, the releases specified in Article 101. Article 000 Xxxxx Xxxxxx xx Xxxxxxx Xxxxx When inflows to Xxxxxxx Falls Reservoir are less than approximately 7,400 cfs, Licensee shall maintain a year-round water level regime at Xxxxxxx Falls Lake that allows for fluctuations of up to 6 feet, between elevation 172.1 and 178.1 feet, except for system emergencies and Low Inflow Protocol events. When flashboards are down, an additional 2 feet of drawdown to elevation 170.1 feet is necessary to safely replace the flashboards. During the bass spawning season, April 15 to May 15, Licensee will limit water level changes to 2 feet except when additional reservoir storage is necessary to meet minimum flow release obligations (minimum flow releases will have priority over lake elevations) or if the flashboards fail. In either of the exceptions noted above, Licensee will endeavor to return to normal operations as soon as reasonably practical.
Sample 1

Related to Low Inflow Protocol

  • Communications Protocol The Parties agree to be bound by the terms and conditions of the communications protocol provided for in Schedule “G” (Communications Protocol).

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, Triarch Marketing must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Scheduling Checkout Protocols 35.13.1.1 Both Parties shall require all transaction schedules to be tagged in accord with the NERC tagging standard. For reserve sharing and other emergency schedules that are not tagged, the Parties will enter manual schedules after the fact into their respective scheduling systems.

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Internet Access Data and information may be made electronically accessible to the Company through Internet access to one or more links provided by the Administrator or a sub-administrator (“Web Link”). All rights in Web Link (including text and “look and feel” attributes) are owned by the sub-administrator. Any commercial use of the content or any other aspect of Web Link requires the written permission of the sub-administrator. Use of the Web Link by the Company will be subject to any terms of use set forth on the web site. Web Link and the information (including text, graphics and functionality) in the Web Link is presented “As Is” and “As Available” without express or implied warranties including, but not limited to, implied warranties of non-infringement, merchantability and fitness for a particular purpose. The sub-administrator neither warrants that the Web Link will be uninterrupted or error free, nor guarantees the accessibility, reliability, performance, timeliness, sequence, or completeness of information provided on the Web Link.

  • Service Information Pages Verizon shall include all CBB NXX codes associated with the geographic areas to which each directory pertains, to the extent it does so for Verizon’s own NXX codes, in any lists of such codes that are contained in the general reference portion of each directory. CBB’s NXX codes shall appear in such lists in the same manner as Verizon’s NXX information. In addition, when CBB is authorized to, and is offering, local service to Customers located within the geographic area covered by a specific directory, at CBB’s request, Verizon shall include, at no charge, in the “Customer Guide” or comparable section of the applicable alphabetical directories, CBB’s critical contact information for CBB’s installation, repair and Customer service, as provided by CBB. Such critical contact information shall appear alphabetically by local exchange carrier and in accordance with Verizon’s generally applicable policies. CBB shall be responsible for providing the necessary information to Verizon by the applicable close date for each affected directory.

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