Change in Host's Demand for Energy Services Sample Clauses

Change in Host's Demand for Energy Services. If Host should change its operations that use or benefit from the Energy Services in such a manner that substantially and permanently changes Host's need for and use of the Energy Services, Host shall, to the extent practicable, provide Seller with advance written notice of any such permanent change. If such change increases the demand for Energy Services, then Host and Seller shall discuss whether Seller can, through an expansion of the System, help to meet such increased demand, and shall take any further action as they mutually agree; provided that any expansion of the System must be agreed to in writing by Host. If such change decreases the demand for Energy Services, then Seller shall have the right to redesign the System (including reducing the System's size and/or capacity) or to remove, relocate or reinstall the System or portion(s) thereof as a result of such reduced demand, all at Seller's sole expense. If, however, Seller reasonably determines that the decrease in demand is so substantial that the continued operation of the System is commercially unreasonable and economically unsustainable, then Seller shall have the right to terminate this Agreement, and Article 4.6 shall apply unless Host elects to purchase the System, in which case Article
Sample 1
AutoNDA by SimpleDocs

Related to Change in Host's Demand for Energy Services

  • Developer Compensation for Emergency Services If, during an Emergency State, the Developer provides services at the request or direction of the NYISO or Connecting Transmission Owner, the Developer will be compensated for such services in accordance with the NYISO Services Tariff.

  • Compensation for Additional Services Additional Services shall be compensated as set forth on Exhibit A for the stipulated payment amounts set forth therein. Other Additional Services not set forth on Exhibit A that are required or requested by the Owner shall be compensated as agreed, using the methodology set forth on Exhibit A, prior to the Design Professional undertaking such Additional Services; provided, however, that if such compensation cannot be agreed, the Additional Services shall be performed at the hourly rates set forth and listed in Exhibit B, plus reimbursable expenses pursuant to Article 4.1.3 below, with a limitation as to maximum amount specified.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

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